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 76-86 of 86 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally platform-neutral and focuses on Azure CycleCloud's configuration syntax, which applies to both Linux and Windows nodes. However, there is a subtle Windows bias: references to device assignment use Azure LUNs and link to a PowerShell module, and the concept of LUNs is more familiar to Windows users. Additionally, the documentation refers to the Azure portal and its blades, which are more commonly used by Windows administrators. Linux-specific tools, patterns, or examples (such as mounting with /etc/fstab or using mount/umount commands) are not mentioned, and the only references to Linux are in the context of LVM configuration attributes, which are described after general options.
Recommendations
- Add explicit Linux mounting examples, such as showing how the configuration maps to /etc/fstab entries or mount commands.
- Include references to Linux tools (e.g., lsblk, blkid, mount, umount) and describe how device assignment works on Linux.
- Provide parity in documentation by mentioning both Windows and Linux workflows for device identification and mounting.
- Clarify that Azure LUNs are used for both Windows and Linux, and provide links to Linux documentation where appropriate.
- Reorder sections so Linux-specific configuration attributes (vg_name, lv_name) are not listed last, or highlight their importance for Linux users.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux, but there is a subtle Windows bias: Windows paths are listed before Linux in installation details, Windows-specific limitations are called out, and links to Azure metadata reference Windows first. Some commands (e.g., jetpack run_on_shutdown) are Linux-only, but this is noted. However, there are no explicit Linux shell or systemd examples, and the documentation does not provide parity in showing Linux-specific usage patterns or troubleshooting steps.
Recommendations
- List Linux paths and examples before or alongside Windows equivalents to avoid Windows-first ordering.
- Provide explicit Linux shell and systemd usage examples where relevant (e.g., how to run Jetpack commands in bash, how to check Jetpack service status on Linux).
- Include troubleshooting steps or notes for Linux users, such as log locations, permissions, or service management.
- Reference Linux Azure metadata documentation when mentioning VM metadata.
- Clarify any differences in behavior or limitations for Linux users, not just Windows.
Low 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-specific features. Windows tools (HPC Pack) are highlighted, while Linux equivalents are not mentioned. Although Ubuntu 22 support for Slurm is noted, Windows features are listed earlier and with more detail.
Recommendations
- List Linux and Windows features in parallel or alternate order to avoid Windows-first bias.
- Mention Linux equivalents to Windows tools (e.g., OpenHPC, Slurm, or other Linux HPC stacks) when referencing Windows-specific tools like HPC Pack.
- Provide equal detail for Linux support (e.g., specify supported Linux distributions and versions alongside Windows).
- Include examples or links for Linux-specific installation and usage where Windows tools are referenced.
Low 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-specific features, and highlight Windows tools (HPC Pack) without equivalent Linux alternatives. Linux features (e.g., Ubuntu 22, Slurm RESTd) are mentioned, but Windows elements are listed first and with more detail, suggesting a subtle Windows bias.
Recommendations
- List Linux and Windows features in parallel or alternate order to avoid Windows-first impression.
- Provide equivalent detail for Linux features (e.g., mention supported Linux distributions and management tools).
- If Windows tools like HPC Pack are mentioned, also highlight Linux alternatives (e.g., Slurm, GridEngine) with equal prominence.
- Explicitly state Linux/macOS compatibility for new features where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Azure-specific tooling and patterns (such as Logical Unit Numbers (LUN) and Disk Encryption Sets) that are managed primarily through the Azure portal and PowerShell modules. The mention of device assignment refers to a PowerShell module link, and Azure-specific terminology is used throughout. However, the configuration examples and filesystem references (ext4, xfs, LVM) are Linux-centric, and there are no explicit PowerShell or Windows-only code samples. Linux configuration options are described, but Windows equivalents (such as NTFS, Windows mount points, or disk management) are not covered, nor are Linux examples shown first.
Recommendations
- Add explicit Linux CLI examples (e.g., using mount, mkfs, mdadm, cryptsetup) for manual volume management.
- Clarify how device assignment and disk encryption steps map to Linux workflows (e.g., udev rules, LVM commands).
- Provide parity by including links to Linux documentation or tools where Azure/PowerShell modules are referenced.
- If Windows support is intended, add NTFS and Windows mount point configuration examples, or clarify platform limitations.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias, particularly in the Active Directory section, which uses Windows-centric terminology (DOMAIN\user) and examples. Windows authentication patterns are described first, and the AD example is tailored to Windows environments. There are no explicit Linux/Powershell-only examples, but Linux-specific details (such as LDAP configuration for Linux domains or Kerberos integration) are missing, and Windows patterns are presented before Linux alternatives.
Recommendations
- Add Linux-centric examples for LDAP authentication, such as using typical Linux usernames or referencing integration with Linux-based directory services.
- Include notes or examples for non-Windows AD environments, such as Samba or FreeIPA.
- Balance examples by showing both Windows (DOMAIN\user) and Linux (user@domain.com) authentication patterns side by side.
- Clarify that AD and LDAP can be used in both Windows and Linux environments, and provide guidance for Linux administrators.
- Ensure screenshots and terminology are not exclusively Windows-focused.
Cyclecloud
Download Cluster Projects and Templates
...main/articles/cyclecloud/download-cluster-templates.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by referencing Microsoft HPC Pack (a Windows-only scheduler) and linking to a PowerShell-based overview for it, while other cluster types are cross-platform. The HPC Pack entry appears before Linux-native schedulers like Slurm and OpenPBS, and the only external documentation link is to a Windows/PowerShell page. However, the CLI example and most content are platform-neutral.
Recommendations
- Add explicit Linux/macOS instructions or links for template usage and scheduler setup.
- Provide parity in external documentation links for Linux-native schedulers (e.g., Slurm, OpenPBS).
- Ensure Linux examples or references appear before or alongside Windows-specific ones.
- Clarify platform compatibility for each scheduler/template in the table.
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 tools and patterns (Windows Explorer, PowerShell, right-click context menu) are described in more detail and with more emphasis. The Windows installation section uses GUI-based steps and PowerShell scripts, while the Linux section uses standard shell commands. The prerequisites section mentions installing Python for Windows, but does not provide equivalent guidance for Linux/macOS users, assuming Python is already present.
Recommendations
- Provide explicit Python installation instructions or verification steps for Linux/macOS users, not just Windows.
- Offer command-line installation steps for Windows (e.g., using PowerShell to unzip and run the installer) to match the Linux CLI approach.
- Present Linux/macOS and Windows instructions in parallel, or clarify that both platforms are equally supported.
- Include troubleshooting tips for both platforms, not just certificate issues for wget (Linux).
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux, but several sections show Windows bias. Windows paths and installation details are listed before Linux equivalents, and some features (e.g., 'jetpack run_on_shutdown') are not supported on Windows but this is mentioned only after the Linux example. References to Azure metadata link to Windows-specific documentation. There are no explicit Linux command-line examples (e.g., using sudo or shell differences), and Windows tools/paths are often mentioned first.
Recommendations
- Present Linux and Windows paths/examples side-by-side or alternate which is listed first.
- Provide explicit Linux command-line examples where relevant (e.g., using sudo, shell differences).
- Link to both Windows and Linux versions of Azure documentation when referencing features like metadata.
- Clearly indicate feature parity and limitations for both platforms up front, not only in notes after examples.
- Add examples or notes for Linux-specific usage (e.g., systemd integration, permissions).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page presents Windows image examples first in all code snippets and lists Windows images before Linux equivalents in several places. While Linux images are supported and listed, the ordering and example selection prioritize Windows, which may subtly signal Windows as the default or preferred platform.
Recommendations
- Provide Linux-based examples alongside or before Windows examples in code snippets.
- Alternate the order of operating systems in tables and examples to avoid implicit prioritization.
- Explicitly state that Linux images are equally supported and provide guidance for common Linux scenarios.
- Include example usages for popular Linux distributions (e.g., Ubuntu, AlmaLinux) in the same detail as Windows.
Cyclecloud
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/disable-autoscaling.md
...main/articles/cyclecloud/how-to/disable-autoscaling.md
Low Priority
View Details →
Detected Bias Types
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.