Cyclecloud
179
Total Pages
160
Linux-Friendly Pages
19
Pages with Bias
10.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
86 issues found
Showing 26-50 of 86 flagged pages
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments and tools. All examples, prerequisites, and configuration steps assume Windows infrastructure (Active Directory, Windows Server, PowerShell scripts, Windows Scheduled Tasks). Linux compute nodes are explicitly not supported, and there are no Linux equivalents or examples provided. The CLI tool is a PowerShell script (.ps1) and is referenced only in the context of Windows paths and usage.
Recommendations
- Add information about Linux support plans, or clarify the roadmap for Linux integration.
- Provide equivalent examples and instructions for Linux environments if/when supported.
- Mention alternative tools or workflows for Linux users, or explicitly state the lack of support.
- If possible, develop and document cross-platform CLI tools (e.g., Python or shell scripts) rather than Windows-only PowerShell scripts.
- Ensure that prerequisites and infrastructure sections mention Linux options or limitations in parity with Windows.
- Include a comparison table or section outlining feature differences between Windows and Linux clusters.
Create Pull Request
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows mild Windows bias: Windows paths are listed before Linux paths in installation details, and Windows-specific limitations (e.g., 'forever' option for HealthCheck only on Windows, 'run_on_shutdown' not supported on Windows) are noted, but Linux equivalents are not always explained in equal detail. There are no PowerShell examples, but Windows tools and patterns are mentioned first or exclusively in some cases. Linux-specific features (e.g., udev rules, bash scripts) are referenced but not highlighted with examples.
Recommendations
- List Linux and Windows paths in parallel, or alternate which is listed first.
- Provide explicit Linux examples or notes where Windows-specific limitations are mentioned (e.g., clarify what options are available for HealthCheck on Linux).
- Add more Linux-specific usage examples, such as bash script registration for 'run_on_shutdown'.
- Highlight Linux features (like udev rules) with brief explanations or examples.
- Ensure parity in describing both platforms' behaviors and limitations for each command.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cluster-references/node-nodearray-reference.md
...lecloud/cluster-references/node-nodearray-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific features (such as Hybrid Benefit licensing and Secure Boot) are mentioned explicitly and sometimes before Linux equivalents. There is a lack of Linux-specific examples or guidance, and some attributes (e.g., KeyPairLocation) are ambiguous about Linux/Windows parity. No PowerShell or Windows CLI examples are present, but Windows licensing and features are referenced more often than Linux-specific ones.
Recommendations
- Add explicit Linux examples, such as specifying SSH keys, Linux-specific image attributes, and Linux VM configuration patterns.
- Balance the mention of Windows features (Hybrid Benefit, Secure Boot, VTPM) with equivalent Linux features, or clarify when features are Windows-only.
- For attributes like KeyPairLocation, clarify usage for both Linux and Windows nodes, and provide examples for each.
- Include sample templates or attribute tables that highlight Linux-specific scenarios (e.g., custom Jetpack installation, Linux Marketplace images).
- Where Windows features are described, add notes about Linux alternatives or indicate if the feature is not applicable to Linux.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/install-cyclecloud-cli.md
...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides installation instructions for both Linux and Windows, but Windows-specific tools (PowerShell, Windows Explorer) and patterns (right-click, double-click) are described in detail. Windows prerequisites (Python installation) are mentioned before Linux, and Windows installation steps use graphical actions and PowerShell scripts, while Linux instructions use standard shell commands. The Windows section is slightly more detailed in describing user actions, and PowerShell is highlighted as the main scripting tool for Windows.
Recommendations
- Provide parity in example detail: For Linux, include graphical extraction instructions (e.g., using a file manager) if Windows uses Explorer.
- Mention Linux tools first when describing prerequisites, or present both platforms together.
- Offer a Linux equivalent for the PowerShell install script (e.g., a bash script), and clarify if double-clicking is possible in Linux desktop environments.
- Include MacOS installation instructions if supported.
- Balance the depth of instructions for both platforms, ensuring neither is described with more detail or priority.
- Where possible, use cross-platform commands or note differences explicitly.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/mount-disk.md
...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Device assignment is described in terms of Azure Logical Unit Numbers (LUN) with a reference to a PowerShell module, but no equivalent Linux tooling or example is provided. The mention of Azure portal and Windows-centric terms (e.g., 'blade') occurs before any Linux-specific configuration details. While the configuration examples use Linux-style mountpoints and filesystems (ext4, xfs), there are no explicit Linux command-line examples (e.g., using 'lsblk', 'mount', or 'fdisk'), nor is there guidance for Linux users on how to verify or troubleshoot mounts. The documentation does mention LVM options for Linux, but only in the configuration table, not in the main text or examples.
Recommendations
- Add explicit Linux command-line examples for mounting, formatting, and verifying volumes (e.g., using 'lsblk', 'mount', 'fdisk', 'mkfs').
- Provide Linux equivalents for device assignment and management, such as referencing '/dev/sdX' naming conventions and tools like 'udev' or 'parted'.
- Include troubleshooting steps for Linux users (e.g., checking mount status, reviewing '/etc/fstab', inspecting logs).
- Balance references to Azure portal and PowerShell with Azure CLI and Linux shell commands.
- Expand the LVM section with practical Linux configuration examples and usage patterns.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md
...main/articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Active Directory (a Windows-centric authentication method) and providing configuration examples specifically for Windows users (e.g., DOMAIN\user format). There is no mention of Linux-specific authentication patterns (such as sssd, nslcd, or PAM integration), nor are there examples for Linux-based LDAP configurations or command-line tools. The Entra ID section references SSH keys and UIDs/GIDs for Linux clusters, but does not provide Linux-specific setup instructions or examples. Overall, Windows tools and patterns are mentioned first and in more detail, while Linux equivalents are missing or only briefly referenced.
Recommendations
- Add Linux-specific examples for LDAP authentication, including configuration details for common Linux tools (e.g., sssd, nslcd, PAM).
- Provide sample user formats for Linux environments (e.g., uid=user,ou=users,dc=example,dc=com) alongside Windows DOMAIN\user formats.
- Include instructions for configuring authentication via the Linux command line, not just GUI-based steps.
- Mention Linux authentication best practices and integration points (such as /etc/ldap.conf, /etc/sssd/sssd.conf, or PAM modules).
- Ensure parity in troubleshooting steps and lockout recovery for both Windows and Linux environments.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/connect-to-node.md
...lob/main/articles/cyclecloud/how-to/connect-to-node.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page provides connection instructions for both Linux and Windows nodes, but Windows-specific tools and patterns (RDP, Microsoft RDP client) are mentioned explicitly and with more detail. Windows connection methods (RDP tunnel, automatic RDP client launch) are described, while Linux equivalents (e.g., X11 forwarding, graphical desktop access) are not. The examples for connecting to services focus on Windows Remote Desktop, with no parallel Linux graphical access example. The documentation references Microsoft RDP client by name, but does not mention Linux alternatives or provide parity in graphical connection instructions.
Recommendations
- Include examples for connecting to Linux graphical desktops (e.g., X11 forwarding, VNC) alongside Windows RDP examples.
- Mention Linux-compatible RDP clients (e.g., Remmina, rdesktop, FreeRDP) when discussing RDP connections.
- Provide parity in instructions for accessing services on Linux nodes (e.g., tunneling for web interfaces, databases, or graphical desktops).
- Avoid mentioning Windows tools (such as Microsoft RDP client) exclusively; list cross-platform alternatives where appropriate.
- Ensure that Linux connection patterns (e.g., SSH with agent forwarding, graphical desktop access) are described with the same level of detail as Windows methods.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally mentions Windows and Linux paths and behaviors, but often lists Windows first (e.g., installation paths, command locations). Some features (such as 'run_on_shutdown') are described as unsupported for Windows, but Linux-specific usage is not elaborated. There are references to Windows tools and concepts (e.g., custom script extension, Windows instance metadata) without equivalent Linux details or examples. No PowerShell-specific examples are present, but Linux shell usage is implied rather than explicitly shown. Overall, the documentation is not strongly Windows-biased, but does show a tendency to mention Windows first and lacks Linux-specific examples and parity in some feature explanations.
Recommendations
- Alternate the order of Windows and Linux mentions, or list Linux first where appropriate.
- Provide explicit Linux shell examples (e.g., bash commands, systemd integration) where commands or features differ.
- Clarify Linux-specific behaviors for features that are not supported on Windows (e.g., 'run_on_shutdown'), including example scripts and usage scenarios.
- Include references to Linux instance metadata and equivalents when mentioning Windows-specific features.
- Ensure that all features and commands have clear documentation for both platforms, highlighting any differences in usage or behavior.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack, which is a Windows-based HPC solution. All configuration steps, prerequisites, and tooling (such as the azhpcpack.ps1 CLI) are Windows-specific, with no mention of Linux support, Linux node configuration, or equivalent Linux tools. Examples and instructions reference Windows technologies (Active Directory, PowerShell scripts, Windows Scheduled Tasks) and do not provide Linux alternatives or parity.
Recommendations
- Explicitly state the lack of Linux support and provide a roadmap or timeline for future Linux compatibility.
- Add documentation for Linux-based HPC solutions that can be integrated with CycleCloud, such as SLURM or PBS, and link to those guides.
- If/when Linux support is added, provide equivalent Linux examples, tooling, and configuration steps alongside Windows instructions.
- Mention Linux alternatives for Active Directory integration (e.g., LDAP, FreeIPA) and certificate management.
- Offer cross-platform CLI tools or document how Linux users can manage clusters, even if only partial functionality is available.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/release-notes/8-5-0.md
...s/blob/main/articles/cyclecloud/release-notes/8-5-0.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 as new features before Linux equivalents. There is explicit mention of Windows tools (HPC Pack), while Linux features (e.g., Slurm, Ubuntu 22) are mentioned later and with less detail. No Linux-specific examples or tools (such as OpenHPC or Linux-specific configuration patterns) are provided, and there is no parity in example depth or ordering.
Recommendations
- List Linux features (e.g., Ubuntu 22 support, Slurm RESTd) before or alongside Windows features to avoid ordering bias.
- Provide equivalent Linux tool references (e.g., OpenHPC, Linux health check tools) when mentioning Windows-specific tools like HPC Pack.
- Include explicit examples or configuration notes for Linux environments, matching the detail given for Windows.
- Ensure parity in documentation depth for both Windows and Linux, including troubleshooting and feature highlights.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md
...main/articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/connect-to-node.md
...lob/main/articles/cyclecloud/how-to/connect-to-node.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/add-disk.md
...-docs/blob/main/articles/cyclecloud/how-to/add-disk.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/user-authentication.md
...main/articles/cyclecloud/how-to/user-authentication.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/healthcheck.md
...cs/blob/main/articles/cyclecloud/how-to/healthcheck.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/scheduled-events.md
...ob/main/articles/cyclecloud/how-to/scheduled-events.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/release-notes/8-5-0.md
...s/blob/main/articles/cyclecloud/release-notes/8-5-0.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority
View Details →
Detected Bias Types
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.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides both SSH (Linux) and RDP (Windows) connection methods, but Windows-specific instructions and tools (RDP, Microsoft RDP client) are mentioned explicitly and sometimes before Linux equivalents. There are detailed instructions for connecting to Windows VMs via RDP tunnels, but no equivalent examples for Linux GUI access (e.g., X11 forwarding). The documentation assumes SSH for Linux but does not provide Linux-specific GUI access examples, and the RDP client is described for macOS/Windows but not for Linux.
Recommendations
- Add explicit Linux/macOS examples for GUI access (e.g., X11 forwarding) to match the detail given for Windows RDP.
- Mention Linux-compatible RDP clients (e.g., Remmina, rdesktop) when discussing RDP connections.
- Ensure examples for connecting to Linux nodes are as detailed as those for Windows nodes, including troubleshooting tips and alternate authentication methods.
- Present Linux and Windows instructions in parallel sections or side-by-side, rather than focusing on Windows first.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, especially in the Active Directory section, which uses Windows-centric terminology (e.g., DOMAIN\user) and examples. Windows authentication patterns are described first and in detail, while Linux-specific authentication scenarios (such as LDAP) are mentioned but lack concrete examples or guidance. There is no mention of Linux tools or command-line configuration, and the only console command shown is generic. The documentation assumes familiarity with Windows environments and does not provide parity for Linux/macOS users in terms of examples or troubleshooting steps.
Recommendations
- Provide Linux/macOS-specific examples for LDAP authentication, including sample distinguished names (DNs) and configuration patterns.
- Include guidance for configuring authentication using Linux command-line tools (e.g., ldapsearch, kinit) or configuration files.
- Balance examples by showing both Windows (DOMAIN\user) and Linux (user@domain.com, cn=user,dc=example,dc=com) authentication formats.
- Add troubleshooting steps and screenshots for Linux environments where applicable.
- Clarify that the authentication methods are cross-platform and provide explicit instructions for non-Windows users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides connection instructions for both Linux and Windows nodes, but Windows-specific tools (RDP, Microsoft RDP client) and patterns are mentioned explicitly and sometimes before Linux equivalents. There is a notable emphasis on Windows workflows (RDP tunneling, Microsoft RDP client) and some examples are tailored to Windows users, with less detail for Linux/macOS users regarding graphical remote access. Linux SSH workflows are described, but Windows examples (RDP) are given more prominence and detail.
Recommendations
- Provide explicit Linux/macOS instructions for graphical remote access (e.g., using xrdp, Remmina, or rdesktop) alongside Windows RDP examples.
- Ensure Linux/macOS tools are mentioned with equal prominence and detail as Windows tools.
- Present examples for both platforms side-by-side, or clearly label which examples apply to which OS.
- Avoid assuming Microsoft RDP client availability on macOS; suggest alternatives for Linux/macOS users.
- Add troubleshooting notes for Linux/macOS users connecting to Windows nodes (e.g., RDP client setup, firewall rules).
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides configuration examples exclusively for Windows images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest'), with no equivalent examples for Linux images. Although the list of supported images includes several Linux distributions, the practical usage examples and instructions focus solely on Windows, making it less clear for Linux users how to specify their images.
Recommendations
- Add configuration examples for Linux images (e.g., Ubuntu, AlmaLinux, SLES) alongside Windows examples.
- Present both Windows and Linux examples in parallel or alternate their order to avoid Windows-first bias.
- Clarify that the same configuration patterns apply to Linux images and provide explicit sample values for Linux.
- Include notes or sections addressing any Linux-specific considerations (e.g., Jetpack usage, image labels).
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides configuration examples exclusively for Windows images, such as 'cycle.image.win2022' and Windows Server URNs, without showing equivalent examples for Linux images. The initial examples and explanations focus on Windows, and there are no sample configurations for Linux distributions, despite their availability in the supported images table.
Recommendations
- Add configuration examples for popular Linux images (e.g., Ubuntu, AlmaLinux, SLES) alongside Windows examples to demonstrate parity.
- Alternate the order of examples so that Linux images are shown first or equally with Windows images.
- Include sample URNs and resource IDs for Linux images in the documentation.
- Explicitly mention that the same configuration patterns apply to Linux images, with concrete examples.
Cyclecloud
Download Cluster Projects and Templates
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by highlighting Microsoft HPC Packβa Windows-specific job schedulerβamong the available templates, and linking to a Windows PowerShell-based overview for HPC Pack. The HPC Pack entry is listed before several Linux-native schedulers, and its description and logo link to Windows-centric resources. No explicit Linux bias is present, but Linux tools are described in a more generic way, without platform-specific links or instructions.
Recommendations
- Provide equal platform-specific details for Linux-native schedulers (e.g., link to Slurm, Grid Engine, HTCondor official documentation).
- Avoid linking to Windows/PowerShell documentation in the main table unless Linux equivalents are also provided.
- Ensure the order of templates does not implicitly prioritize Windows tools; consider alphabetical or usage-based ordering.
- Add explicit examples or instructions for importing and using Linux-native templates, if any platform-specific steps exist.