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 51-75 of 86 flagged pages
Cyclecloud
Plan your CycleCloud Workspace for Slurm Deployment
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page shows a bias towards Windows-centric Azure tools and patterns. It references Azure Bastion (primarily used for RDP/SSH access, often in Windows environments), VPN Gateway, and ExpressRoute, but does not mention Linux-native access patterns or tools (such as SSH jumphosts, OpenVPN, or WireGuard). There are no examples or guidance for Linux users, such as using SSH keys, configuring Linux firewalls, or Linux-based bastion hosts. The documentation assumes Azure-native solutions, which are often more familiar to Windows administrators.
Recommendations
- Add examples and guidance for Linux users, such as SSH key management, configuring SSH access via Linux bastion hosts, or using OpenVPN/WireGuard for secure connectivity.
- Mention Linux-native tools and patterns alongside Azure Bastion and VPN Gateway, and clarify how Linux users can access and manage CycleCloud resources.
- Provide sample commands or configuration snippets for both Windows (PowerShell, Azure CLI) and Linux (bash, Azure CLI) environments.
- Explicitly state Linux compatibility and best practices for firewall/NSG rules, filesystem mounts (NFS, Lustre), and authentication workflows.
- Ensure parity in troubleshooting and support references for both Windows and Linux users.
Create Pull Request
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-centric job schedulerβamong the available templates, with its logo linking to a PowerShell-based documentation page. This Windows tool is listed before several Linux-native schedulers (HTCondor, LSF, OpenPBS, Slurm), and its description emphasizes Microsoft technologies. No explicit Linux command-line examples are provided, but the CycleCloud CLI example is platform-neutral.
Recommendations
- Ensure equal prominence for Linux-native schedulers by rotating or randomizing the order of template listings, or grouping by platform.
- Provide explicit Linux usage examples alongside any Windows-specific instructions, especially where platform-specific tools (like HPC Pack) are mentioned.
- Clarify platform compatibility for each template, indicating whether it is Windows-only, Linux-only, or cross-platform.
- Avoid linking directly to Windows/PowerShell documentation unless a Linux equivalent is also provided.
Cyclecloud
Plan your CycleCloud Workspace for Slurm Deployment
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Azure Bastion (a Windows-centric remote access tool) and VPN Gateway, without mentioning Linux-native alternatives or providing Linux-specific access patterns. There are no examples or instructions for connecting from Linux workstations, nor are Linux command-line tools (such as SSH or OpenVPN) discussed. The documentation also omits details on how Linux users might interact with the CycleCloud Workspace for Slurm deployment, focusing instead on Azure-native solutions that are more familiar to Windows administrators.
Recommendations
- Add examples for connecting to the CycleCloud Workspace from Linux clients, such as using SSH tunneling or OpenVPN.
- Mention Linux-native remote access tools and patterns alongside Azure Bastion and VPN Gateway.
- Provide parity in instructions for both Windows and Linux users, including command-line examples for Linux.
- Clarify whether Azure Bastion and VPN Gateway support Linux clients and, if so, provide step-by-step guidance for Linux users.
- Include references to Linux documentation or external resources for remote access and authentication.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias: all configuration examples use Windows images, and the initial image references are exclusively for Windows Server versions. There are no equivalent examples for Linux images, despite Linux images being supported and listed in the table. This may lead Linux users to feel underrepresented or unclear about how to specify Linux images.
Recommendations
- Provide configuration examples using Linux images (e.g., Ubuntu, AlmaLinux, SLES) alongside Windows examples.
- Alternate the order of examples so that Linux and Windows images are both shown first in different sections.
- Explicitly mention that the same configuration patterns apply to Linux images, with concrete examples.
- Ensure that notes and guidance (such as custom image handling) reference both Linux and Windows use cases where applicable.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Windows Server support and HPC Pack support before Linux equivalents, and by specifically mentioning Windows tools (HPC Pack) without providing comparable Linux alternatives or examples. There is no mention of Linux-specific cluster managers (other than Slurm), nor are Linux examples or tools given equal prominence.
Recommendations
- List Linux distributions and cluster managers (e.g., Ubuntu, CentOS, Slurm, GridEngine) alongside or before Windows equivalents to ensure parity.
- Provide examples or notes for Linux-specific tools and workflows where Windows tools (like HPC Pack) are mentioned.
- Include explicit references to Linux support in feature lists, such as supported OS versions and cluster types.
- Ensure that documentation sections do not prioritize Windows features or tools unless there is a technical reason.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing only Windows-based examples for specifying images (e.g., 'cycle.image.win2022', Windows URNs, and Windows DataCenter labels) and omitting equivalent Linux examples in the code snippets. Although the table lists both Linux and Windows images, the instructional content and examples prioritize Windows, leaving Linux users without clear guidance on specifying Linux images.
Recommendations
- Include code examples for specifying Linux images (e.g., AlmaLinux, Ubuntu, SLES) alongside Windows examples.
- Alternate the order of examples so that Linux images are presented first or equally with Windows images.
- Provide explicit URN and label examples for popular Linux distributions in the documentation.
- Add notes or sections clarifying any Linux-specific considerations or best practices for image selection.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/plan-your-deployment.md
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure Bastion (a Windows-oriented remote access tool) and VPN Gateway, without mentioning Linux-native alternatives or SSH-based access patterns. There are no examples or instructions for Linux users (e.g., SSH tunneling, Linux Bastion hosts, or Linux command-line tools), and the documentation does not provide parity for Linux-centric workflows.
Recommendations
- Include instructions and examples for Linux users, such as SSH tunneling from Linux/Mac clients to the CycleCloud VM.
- Mention Linux Bastion host deployment as an alternative to Azure Bastion, with links to relevant documentation.
- Provide examples of accessing Slurm and CycleCloud resources using Linux command-line tools.
- Clarify that Azure Bastion and VPN Gateway are cross-platform, but offer guidance for Linux-specific configurations and troubleshooting.
- Add parity in documentation for Linux authentication and connectivity patterns, such as using OpenSSH, and reference Linux-native tools where appropriate.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The release notes mention Windows Server 2019 and 2022 support and HPC Pack 2019 before Linux equivalents, and specifically call out Windows technologies (Windows Server, HPC Pack) without providing similar detail for Linux. While Ubuntu 22 support is mentioned, it appears later and with less emphasis. No Linux-specific tools or distributions (other than Ubuntu) are highlighted, and there are no Linux/Powershell command examples, but the overall framing gives Windows technologies priority.
Recommendations
- List Linux distribution support (e.g., Ubuntu, CentOS, RHEL) alongside or before Windows support.
- Highlight Linux HPC tools (e.g., OpenHPC, Warewulf, etc.) if supported, similar to the mention of HPC Pack for Windows.
- Provide parity in feature announcements, ensuring Linux features are described with equal detail and prominence.
- Include examples or references for both Windows and Linux where relevant (e.g., installation, configuration).
- Consider a dedicated section for Linux-specific improvements if Windows-specific features are called out.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays mild Windows bias by highlighting Microsoft HPC Packβa Windows-specific job schedulerβand linking to its PowerShell documentation, while Linux-oriented tools (e.g., Slurm, HTCondor, Grid Engine) are listed without equivalent platform-specific guidance or links. The HPC Pack entry appears before several Linux-native schedulers, and the only external documentation link is to a Windows/PowerShell resource.
Recommendations
- Add links to official documentation for Linux-native schedulers (e.g., Slurm, HTCondor, Grid Engine) similar to the HPC Pack entry.
- Include examples or references for importing templates on Linux systems, if any platform-specific steps exist.
- Ensure parity in external documentation links for both Windows and Linux tools.
- Consider ordering the template types alphabetically or by popularity, rather than placing Windows tools before Linux equivalents.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/plan-your-deployment.md
...rticles/cyclecloud/how-to/ccws/plan-your-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page shows a bias toward Windows-centric Azure tools and patterns. It exclusively references Azure Bastion, VPN Gateway, and ExpressRoute for remote access, which are more commonly used in Windows environments and does not mention Linux-native access methods (such as SSH directly or via jump hosts). There are no examples or guidance for Linux users (e.g., SSH, OpenVPN, or Linux CLI tools), and no Linux-specific configuration or troubleshooting steps are provided.
Recommendations
- Include examples for connecting to CycleCloud Workspace from Linux systems, such as using SSH or OpenVPN.
- Provide instructions for configuring Linux-based jump hosts or bastion hosts, alongside Azure Bastion.
- Mention Linux CLI tools (e.g., az CLI, ssh) and provide sample commands for common tasks.
- Add troubleshooting tips for Linux users, such as handling SSH keys, firewall rules, and VPN client setup.
- Ensure parity in documentation by listing Linux options before or alongside Windows/Azure-specific tools.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias: all configuration examples use Windows images (e.g., 'cycle.image.win2022', 'MicrosoftWindowsServer:WindowsServer:2022-datacenter-g2:latest'), and there are no equivalent examples for Linux images. Although the table lists Linux images as available, the practical usage examples exclusively reference Windows, potentially leading Linux users to feel unsupported or less prioritized.
Recommendations
- Add configuration examples using popular Linux images (e.g., Ubuntu, AlmaLinux, SLES) alongside or before Windows examples.
- Alternate the order of examples to sometimes show Linux first, or provide parallel examples for both platforms.
- Explicitly mention that all image types (Windows and Linux) can be specified using the same parameters.
- Include a note or section clarifying Linux support and providing guidance for common Linux scenarios.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/configure-open-ondemand.md
...cles/cyclecloud/how-to/ccws/configure-open-ondemand.md
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/ccws/open-ondemand-add-users.md
...cles/cyclecloud/how-to/ccws/open-ondemand-add-users.md
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/common-issues/staging-resources.md
...articles/cyclecloud/common-issues/staging-resources.md
Medium Priority
View Details →
Detected Bias Types
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.
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
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/download-cluster-templates.md
...main/articles/cyclecloud/download-cluster-templates.md
Medium Priority
View Details →
Detected Bias Types
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.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/images.md
...ocs/azure-docs/blob/main/articles/cyclecloud/images.md
Medium Priority
View Details →
Detected Bias Types
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.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux environments, specifying installation paths and supported features for each. However, there is a slight Windows-first bias in some sections (e.g., installation paths listed with Windows first), and some examples or feature notes are Windows-specific (such as the HealthCheck 'forever' option and run_on_shutdown command not being supported on Windows). There are no PowerShell-only examples or exclusive use of Windows tools, but Linux-specific usage patterns (such as systemd or bash scripting) are referenced without detailed Linux examples.
Recommendations
- List Linux paths and features before or alongside Windows equivalents to avoid implicit prioritization.
- Provide explicit Linux command-line examples where feature behavior differs (e.g., show a bash script example for run_on_shutdown).
- Clarify feature parity and differences in a dedicated section/table for quick reference.
- Where commands or features are not supported on Windows, offer alternative approaches or explicitly state Linux usage.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides authentication setup instructions for built-in, Active Directory, LDAP, and Entra ID methods. In the Active Directory section, Windows-centric patterns (DOMAIN\user) are described first and illustrated, with Windows user examples shown before UPN (user@domain.com) patterns. However, the overall instructions are platform-neutral, and Linux authentication scenarios (LDAP, Entra ID with SSH keys) are covered. There are no PowerShell-only examples, Windows-only tools, or missing Linux equivalents.
Recommendations
- In the Active Directory section, clarify that both Windows (DOMAIN\user) and UPN (user@domain.com) formats are supported equally, and provide explicit Linux/macOS login examples if relevant.
- Add a note in the Active Directory section that Linux/macOS users typically use UPN (user@domain.com) format, and mention any platform-specific considerations for authentication.
- Ensure screenshots and examples alternate or include both Windows and Linux/macOS user scenarios where applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides authentication setup instructions for Azure CycleCloud, including built-in, Active Directory, LDAP, and Entra ID methods. In the Active Directory section, Windows authentication patterns (DOMAIN\user) are described first and highlighted in the example, with no mention of Linux authentication patterns (e.g., user@domain.com) or Linux-specific considerations. However, the overall instructions are platform-neutral, and the LDAP and Entra ID sections mention Linux clusters and SSH keys.
Recommendations
- In the Active Directory section, explicitly mention Linux authentication patterns (e.g., user@domain.com) and clarify that both Windows and Linux users can authenticate using UPN format.
- Add examples or notes for Linux/macOS users where authentication patterns or tools differ (e.g., clarify that DOMAIN\user is typical for Windows, while user@domain.com is common for Linux/macOS).
- Ensure screenshots and examples show both Windows and Linux authentication scenarios where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Active Directory (a Windows-centric technology) before LDAP, and the AD example uses Windows-style username formats (EXAMPLE\username) without showing Linux-style equivalents. However, the page does provide LDAP and Entra ID instructions, and the built-in authentication is cross-platform. No PowerShell or Windows-only tools are referenced, and Linux clusters are explicitly mentioned in the Entra ID section.
Recommendations
- When describing Active Directory authentication, include Linux-style username formats (e.g., user@domain.com) and clarify how Linux users can authenticate.
- Provide explicit examples for LDAP authentication that reference typical Linux environments or directory structures.
- Ensure screenshots and examples do not exclusively show Windows conventions (e.g., backslash in usernames), or add Linux/macOS equivalents.
- Consider mentioning any platform-specific caveats for authentication methods, especially for Linux clusters.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Windows image examples first in all code snippets, with Windows image names and URNs shown before any Linux equivalents. While the table of supported images includes both Linux and Windows options, the example usage is Windows-centric, and Linux image configuration is not demonstrated.
Recommendations
- Add equivalent Linux image examples (e.g., AlmaLinux, Ubuntu) in all code snippets alongside or before Windows examples.
- Alternate the order of examples to avoid always presenting Windows first.
- Provide explicit Linux-focused configuration guidance, such as specifying Ubuntu or AlmaLinux images using ImageName and Image.
- Include notes or tips relevant to Linux images, such as Jetpack usage or differences in status reporting.
Cyclecloud
Install the Command Line Interface
...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
Low 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 details (such as PowerShell scripts and Windows Explorer usage) are described in greater depth. The Windows installation section mentions PowerShell and Windows Explorer tools explicitly, while the Linux section uses standard shell commands. The prerequisites section gives a direct link for installing Python on Windows, but does not provide equivalent guidance for Linux/macOS. Windows instructions are presented after Linux, but with more detailed steps and tool references.
Recommendations
- Provide equivalent detail for Linux/macOS users, such as mentioning common extraction tools (e.g., Archive Manager, tar) and how to run the installer from a GUI if desired.
- Include a direct link or brief instructions for installing Python on Linux/macOS, not just Windows.
- Offer a Linux/macOS example for verifying the CLI is in the PATH (e.g., echo $PATH, which cyclecloud).
- If possible, mention cross-platform alternatives to PowerShell scripts (e.g., bash scripts) and clarify any differences in installer behavior.
- Consider listing Linux/macOS instructions first if the majority of users are expected to be on those platforms.