Cyclecloud

167
Total Pages
152
Linux-Friendly Pages
15
Pages with Bias
9.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (18)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing Windows-style username formats (DOMAIN\user), and referencing Windows authentication patterns without equivalent Linux-focused examples. While LDAP and Entra ID are mentioned, there is a lack of explicit Linux authentication scenarios, examples, or command-line instructions (e.g., for Linux PAM, SSH integration, or Linux user mapping). The only mention of Linux is in the context of SSH keys for cluster nodes, but this is not given the same prominence or step-by-step detail as the Windows/AD sections.
Recommendations:
  • Add explicit Linux authentication examples, such as integrating with Linux PAM, local /etc/passwd, or SSSD.
  • Provide step-by-step instructions for configuring LDAP authentication from a Linux client perspective, including sample Linux user formats and command-line tools.
  • Include Linux username formats (e.g., user@domain.com, uid-based logins) alongside Windows formats in all relevant sections.
  • Balance the order of presentation so that Linux/LDAP authentication is described with equal prominence and detail as Active Directory.
  • Reference Linux tools (e.g., ldapsearch, kinit, ssh) and provide troubleshooting steps for Linux environments.
  • Clarify that CycleCloud supports both Windows and Linux authentication scenarios equally, and provide parity in screenshots and configuration walkthroughs.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/configure-open-ondemand.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation focuses exclusively on configuration steps through the Azure CycleCloud web portal, which is a GUI-based workflow commonly associated with Windows environments. There are no command-line examples or instructions for Linux users, nor are Linux-native tools or patterns (such as editing configuration files via SSH or using Linux shell commands) mentioned. This may disadvantage users who prefer or require Linux-based workflows.
Recommendations:
  • Add equivalent Linux command-line instructions for configuring Open OnDemand with CycleCloud, such as using SSH to access the VM and editing configuration files directly.
  • Include examples of how to perform the same configuration steps using Linux shell commands or scripts.
  • Mention Linux-native tools and workflows alongside the web portal method, ensuring parity for users who operate primarily in Linux environments.
  • Explicitly state that the web portal is cross-platform, if applicable, and clarify any OS-specific requirements.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/disable-autoscaling.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation page does not provide any examples or instructions for disabling or enabling autoscaling, and there is no mention of Linux or cross-platform considerations. The absence of examples, especially Linux-specific ones, suggests a lack of parity.
Recommendations:
  • Add step-by-step instructions for disabling and enabling autoscaling on both Windows and Linux platforms.
  • Include command-line examples for both PowerShell (Windows) and Bash (Linux).
  • Explicitly mention any platform-specific differences or requirements.
  • Ensure that Linux tools and workflows are given equal prominence to Windows equivalents.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/open-ondemand-add-users.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation focuses exclusively on user management via the CycleCloud web portal, a Microsoft-centric tool, without mentioning or providing examples for Linux-native user management methods (e.g., command-line tools like useradd or adduser). There are no Linux command-line instructions or references, and the workflow assumes the use of Microsoft Entra ID and CycleCloud, both of which are more common in Windows-centric environments.
Recommendations:
  • Include alternative instructions for adding users using standard Linux command-line tools (e.g., useradd, adduser) for environments where CycleCloud is not used or for administrators who prefer CLI.
  • Provide examples or references for managing users directly on Linux clusters, including how to synchronize with Microsoft Entra ID if applicable.
  • Clarify whether the described process is required or optimal for Linux-based clusters, or if there are Linux-native alternatives.
  • Add a section comparing CycleCloud-based user management with traditional Linux user management to help users choose the best approach for their environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/connect-to-node.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation provides both SSH (Linux) and RDP (Windows) connection methods, but Windows-specific tools and workflows (such as the Microsoft RDP client and RDP tunneling) are described in more detail. There are explicit instructions for launching the Microsoft RDP client on Windows and OSX, but no equivalent details for Linux RDP clients. Additionally, when discussing connecting to services, the only concrete example given is for Windows Remote Desktop, with no Linux service examples provided.
Recommendations:
  • Include explicit examples of connecting to Linux services (e.g., tunneling to a web server or database on a Linux VM) to balance the Windows RDP example.
  • When describing RDP access, mention and provide example commands for popular Linux RDP clients (such as Remmina or rdesktop) alongside Windows and OSX.
  • Ensure that instructions for launching remote desktop clients are provided for all major platforms, not just Windows and OSX.
  • Consider alternating the order of Windows and Linux examples, or presenting them in parallel, to avoid a 'windows_first' perception.
  • Where possible, provide parity in depth and detail for both Windows and Linux workflows throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page lists several cluster template types, and the only project with a Microsoft-specific/Windows-specific tool is 'HPC Pack', which is a Windows-only job scheduler. Additionally, the link for HPC Pack points to a PowerShell documentation page, and it is listed before several Linux-native schedulers (HTCondor, LSF, OpenPBS, Slurm). However, the CLI example given is cross-platform and there are examples for Linux-native schedulers as well. There are no explicit PowerShell commands or Windows-only instructions, but the presence and placement of HPC Pack and its PowerShell link indicate a mild Windows bias.
Recommendations:
  • Ensure that Linux-native schedulers (e.g., Slurm, OpenPBS) are given equal prominence in the table, possibly by ordering them alphabetically or by usage popularity.
  • Provide links to Linux documentation or usage guides for each scheduler, not just for the Windows-specific HPC Pack.
  • If referencing Windows tools (like HPC Pack), also provide equivalent Linux tool references or clarify platform support for each template.
  • Avoid linking directly to PowerShell documentation unless a Linux equivalent is also provided.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/staging-resources.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation references the Azure portal GUI (a web interface commonly used by Windows users) for checking settings, and does not provide any command-line examples (such as Azure CLI or PowerShell) for Linux users. There are no Linux-specific instructions or parity in tooling guidance.
Recommendations:
  • Include Azure CLI commands to check if Hierarchical namespace is enabled (e.g., using 'az storage account show').
  • Provide both PowerShell and Bash/Azure CLI examples for managing permissions and checking storage account settings.
  • Mention that the Azure portal is cross-platform, but explicitly offer command-line alternatives for users who prefer or require non-GUI workflows.
  • Add troubleshooting steps or examples relevant to Linux environments, such as checking permissions or environment variables from a Linux shell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/add-disk.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows documentation links before or instead of Linux equivalents in the disk types section, and by omitting any Linux-specific commands or examples for mounting or formatting disks. While the initial link to managed disks points to a Linux page, subsequent references (especially for disk types) use Windows documentation. There are no examples of Linux CLI commands or tools (e.g., fdisk, mkfs, mount), nor is there any mention of Linux-specific patterns for disk management.
Recommendations:
  • Ensure that all Azure documentation links reference both Linux and Windows pages equally, or prefer Linux links when the context is Linux-heavy (as with CycleCloud).
  • Provide Linux command-line examples for mounting and formatting disks (e.g., using fdisk, mkfs, mount) directly in this documentation or as inline examples.
  • Mention Linux disk management tools and patterns alongside any references to Windows tools or documentation.
  • If referencing both OSes, present Linux and Windows options side by side, or clarify when instructions are OS-agnostic.
  • Review and update the 'Further reading' section to include direct links to Linux disk management documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-cyclecloud-cli.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation shows mild Windows bias by mentioning Windows prerequisites and installation steps before Linux equivalents in some sections, and by providing more detailed instructions for Windows-specific tools (e.g., PowerShell, Windows Explorer). However, Linux installation steps are present and reasonably detailed.
Recommendations:
  • Present Linux and Windows instructions in parallel or in a consistent order (e.g., Linux first, then Windows, or vice versa, but consistently).
  • Provide equivalent detail for both platforms, including command-line examples for both Linux and Windows (e.g., show PowerShell commands alongside bash commands).
  • Avoid assuming the user is on Windows in prerequisite sections; instead, provide platform-neutral guidance or clearly separate platform-specific steps.
  • Where possible, mention cross-platform tools and patterns, and avoid Windows-specific terminology unless necessary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing login examples using Windows-style DOMAIN\username formats, and referencing Windows authentication patterns. There are no explicit Linux or OpenLDAP examples, and Linux-specific authentication patterns are only briefly mentioned in the context of Entra ID and SSH keys, with no equivalent detail or step-by-step guidance for Linux environments.
Recommendations:
  • Add explicit Linux/OpenLDAP configuration examples, including sample settings and login formats (e.g., uid=username,ou=users,dc=example,dc=com).
  • Provide Linux-centric authentication scenarios and troubleshooting tips, such as integration with PAM or sssd.
  • Balance the order of presentation by introducing LDAP (and Linux authentication) before or alongside Active Directory.
  • Include screenshots or configuration walkthroughs for Linux environments, not just Active Directory.
  • Clarify that both Windows and Linux authentication patterns are supported, and provide parity in documentation depth for each.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/healthcheck.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Windows Example Linux First Linux Tools
Summary:
The documentation provides detailed Linux-specific examples (including a Bash script and references to Linux file paths and tools), while Windows is only mentioned in passing with no equivalent example or detailed instructions. Linux tools and patterns are described first and in greater detail, and Windows support is described as limited (Python scripts only), but without practical guidance or examples.
Recommendations:
  • Add a Windows-specific HealthCheck script example (e.g., in Python), showing placement and execution on Windows VMs.
  • Include Windows file paths and instructions alongside Linux ones when describing where to place scripts and how to configure HealthCheck.
  • Clarify any differences in behavior or configuration between Linux and Windows, and provide parity in documentation structure and detail.
  • Where Linux tools or commands are referenced (e.g., Bash, /proc/uptime), provide Windows equivalents or note their absence.
  • Consider presenting both Linux and Windows instructions/examples side-by-side to avoid implicit prioritization.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/scheduled-events.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Powershell Heavy
Summary:
The documentation provides both Linux and Windows script examples, but Windows paths and script types are consistently mentioned alongside or before Linux equivalents. Windows-specific details (e.g., C:\cycle\jetpack\scripts, .bat scripts) are given equal prominence, and there is an implicit assumption of Windows familiarity (e.g., referencing .bat files, Windows paths) without offering Linux-specific guidance or troubleshooting. No Linux-specific tools or patterns are highlighted, and there are no Linux-first examples.
Recommendations:
  • Provide Linux-first examples or alternate between Linux and Windows in examples and explanations.
  • Include Linux-specific troubleshooting tips or notes, such as permissions for .sh scripts or SELinux considerations.
  • Highlight Linux tools or commands (e.g., using chmod to ensure scripts are executable) where appropriate.
  • Where both platforms are mentioned, consider leading with Linux examples if the primary audience is likely to use Linux.
  • Add a section summarizing differences or best practices for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest', 'Windows 2022 DataCenter') and omitting equivalent Linux-based examples. While the table of available images includes both Linux and Windows options, the configuration examples exclusively reference Windows, which may mislead users into thinking Windows is the primary or preferred platform.
Recommendations:
  • Add parallel Linux-based examples (e.g., using 'cycle.image.ubuntu22' or 'almalinux-8') alongside Windows examples in all configuration code blocks.
  • Alternate the order of examples or provide both Windows and Linux examples together to demonstrate parity.
  • Explicitly state that all example patterns apply equally to Linux images, and show this with sample URNs or labels for Linux distributions.
  • Consider including a short section or note highlighting Linux image usage, especially for common distributions like Ubuntu or CentOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/release-notes/8-5-0.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 (a Windows-specific HPC solution) as notable features, while Linux equivalents or details are only briefly mentioned (e.g., Ubuntu 22 support for Slurm) and not highlighted equally. There are no Linux-specific tools or distributions mentioned with the same prominence, and no Linux command-line or usage examples are provided.
Recommendations:
  • Highlight Linux support with equal prominence as Windows (e.g., mention supported Linux distributions in the same section as Windows Server).
  • If mentioning Windows-specific HPC tools (like HPC Pack), also mention Linux alternatives (e.g., OpenHPC, Slurm) and their support status.
  • Provide examples or links for both Windows and Linux where relevant (e.g., installation instructions, supported OS lists).
  • Ensure that new features or resolved issues affecting Linux are described with the same detail as those for Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Windows First
Summary:
The documentation page lists several cluster templates, and among them, the Microsoft HPC Pack (a Windows-specific job scheduler) is featured prominently with a direct link to PowerShell documentation. This is the only template in the table that links to a Windows-specific technology and documentation, while the others are cross-platform or Linux-centric. The HPC Pack entry is also placed before several Linux-native schedulers, which may suggest a Windows-first bias.
Recommendations:
  • Ensure that all scheduler templates (Windows and Linux) are presented with equal prominence and in a neutral order (e.g., alphabetical or by popularity).
  • Avoid linking to Windows/PowerShell documentation unless equivalent Linux documentation is also provided.
  • If referencing Windows-specific tools like HPC Pack, provide context about platform compatibility and offer Linux alternatives or equivalents in the same section.
  • Consider adding explicit Linux usage examples or links for each template, especially where Windows tools are mentioned.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First Windows Tools Powershell Heavy
Summary:
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack, which only supports Windows nodes. All configuration, prerequisites, and tooling (such as the azhpcpack.ps1 CLI) are Windows-specific, with no mention of Linux support, Linux-based alternatives, or cross-platform considerations. Windows tools, patterns, and terminology are used throughout, and Linux is only mentioned to state that Linux compute nodes are not supported.
Recommendations:
  • Clearly state at the beginning that the integration is Windows-only and that Linux support is not available, to set expectations.
  • If Linux support is planned, include a roadmap or reference to alternative solutions for Linux clusters (e.g., CycleCloud integration with Slurm or other Linux schedulers).
  • Where possible, provide parity in documentation by referencing Linux-based HPC solutions and how they can be integrated with CycleCloud.
  • If any cross-platform features exist (such as Azure Key Vault or Managed Identities), provide Linux command-line examples (e.g., using Azure CLI or bash scripts) alongside PowerShell/Windows examples.
  • Avoid using only Windows file paths and PowerShell scripts; if the CLI or tooling is Windows-only, explicitly state this and suggest alternatives for Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page shows a Windows-first bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest', 'Windows 2022 DataCenter') and omitting equivalent Linux examples. While the table lists both Linux and Windows images, the configuration snippets and guidance focus exclusively on Windows, with no Linux or cross-platform parity in the examples.
Recommendations:
  • Provide Linux-based examples alongside Windows examples for specifying images using ImageName, URN, and labels (e.g., use 'cycle.image.ubuntu22' and 'Canonical:0001-com-ubuntu-server-focal:20_04-lts:latest').
  • Alternate the order of examples or present both Windows and Linux examples together to avoid implicit prioritization.
  • Include a note or section explicitly addressing Linux image usage and any platform-specific considerations.
  • Ensure that all configuration snippets and usage instructions demonstrate both Windows and Linux scenarios for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/jetpack.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a mild Windows bias by listing Windows paths and behaviors before Linux equivalents, referencing Windows-specific features and limitations, and failing to provide Linux-specific command examples or details where relevant. Some features are described as unsupported on Windows, but Linux-specific usage is not elaborated. There is also a lack of Linux-specific troubleshooting or usage notes, and no Linux shell or scripting examples are provided.
Recommendations:
  • Alternate the order of Windows and Linux references, or list Linux first where it is the primary platform.
  • Provide Linux-specific command examples, especially for features not supported on Windows (e.g., 'jetpack run_on_shutdown').
  • Include Linux shell scripting examples where relevant (e.g., registering shutdown scripts, log file locations, service management).
  • Add troubleshooting notes or caveats for Linux environments, such as permissions, systemd integration, or SELinux/AppArmor considerations.
  • Clarify any differences in behavior or requirements between Windows and Linux, especially for environment variables, file paths, and service management.
  • Ensure that documentation for features that are Linux-only (or have different behavior on Linux) is as detailed as for Windows.