Cyclecloud

354
Total Pages
325
Linux-Friendly Pages
29
Pages with Bias
8.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

52 issues found
Showing 1-25 of 52 flagged pages
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack (a Windows-only technology), Active Directory, and Windows Server. All examples, tools, and configuration steps reference Windows environments, with no mention of Linux or macOS equivalents. The CLI tool described is a PowerShell script (.ps1), and autoscaling is implemented as a Windows Scheduled Task. Linux compute nodes are explicitly not supported, and there are no Linux/macOS instructions or alternatives provided.
Recommendations
  • Clearly state at the top that Linux/macOS are not supported if that is the case, and provide guidance for users seeking cross-platform HPC solutions.
  • If/when Linux support is added, provide equivalent examples, CLI tools, and configuration steps for Linux environments.
  • Reference alternative HPC solutions for Linux users (e.g., SLURM, PBS, etc.) and link to relevant documentation.
  • If partial Linux support exists (e.g., for head node or management), document those scenarios and provide Linux-specific instructions.
  • Consider providing a roadmap or status update for Linux support if it is planned.
GitHub Create Pull Request
Cyclecloud Microsoft HPC Pack Integration ...cs/azure-docs/blob/main/articles/cyclecloud/hpcpack.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, focusing exclusively on Microsoft HPC Pack clusters with Windows Server technologies. All examples, tools, and configuration steps assume a Windows environment, with references to PowerShell scripts, Windows Scheduled Tasks, and Active Directory. Linux compute nodes are explicitly not supported, and there are no Linux/macOS equivalents or examples provided.
Recommendations
  • Clearly state Windows-only support at the top of the documentation.
  • If Linux support is planned, provide a roadmap or timeline.
  • Add a comparison table highlighting feature gaps between Windows and Linux.
  • Include links or references to Linux-based HPC solutions for users seeking alternatives.
  • If partial Linux support exists (e.g., for head node or management tools), provide Linux-specific instructions and examples.
GitHub Create Pull Request
Cyclecloud Cluster Template Reference - Nodes ...lecloud/cluster-references/node-nodearray-reference.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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/TPM) are described in detail, and Windows is mentioned first or as the default in several places (e.g., HybridBenefitLicense defaults to Windows_Server). There is a lack of Linux-specific examples or parity in some advanced attributes (e.g., Secure Boot, TPM, Hybrid Benefit), and no explicit Linux command-line or configuration examples are provided. Some attributes and notes are Windows-centric, and Linux equivalents or considerations are not always mentioned.
Recommendations
  • Include explicit Linux examples and use cases alongside Windows ones, especially for attributes that have OS-specific behavior.
  • Clarify which attributes are applicable to Linux, Windows, or both, and document any differences in behavior or requirements.
  • Provide Linux-first or at least Linux-equal ordering in attribute tables and examples, especially for features like Secure Boot, TPM, and licensing.
  • Add Linux-specific troubleshooting notes or references where Windows-specific features are discussed.
  • Ensure that all OS-specific features (e.g., Hybrid Benefit) are described with equal detail for Linux distributions that support similar features (such as RHEL/SLES BYOS).
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by prioritizing Active Directory (a Windows-centric technology) in both order and detail, providing examples and terminology specific to Windows (e.g., DOMAIN\user), and referencing Windows authentication patterns before mentioning LDAP (which is more cross-platform). There are no explicit Linux or OpenLDAP configuration examples, and the only Linux-specific mention is in the context of SSH keys for cluster nodes, which is brief and lacks setup details.
Recommendations
  • Add explicit examples for configuring LDAP with OpenLDAP servers, including sample settings and user formats typical for Linux environments.
  • Provide authentication examples using Linux tools (e.g., ldapsearch, shell commands) alongside GUI instructions.
  • Balance the order of presentation by discussing LDAP and Linux authentication patterns before or alongside Active Directory.
  • Include screenshots or configuration samples from Linux environments, not just Windows/Active Directory.
  • Clarify user formats for Linux/LDAP (e.g., uid=username,ou=users,dc=example,dc=com) in addition to Windows formats.
  • Expand the section on SSH key management for Linux clusters with step-by-step instructions and examples.
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. Windows paths and behaviors are often mentioned before Linux equivalents (e.g., installation directories), and some features are described as Windows-only or unsupported on Windows without providing Linux-specific guidance. There are references to Windows tools and patterns (e.g., custom script extension, Windows paths), but Linux-specific examples, commands, or troubleshooting steps are generally missing or less emphasized.
Recommendations
  • Alternate the order of Windows and Linux references, or present Linux examples first where appropriate.
  • Provide explicit Linux command-line examples, including shell commands and file paths, especially for features that differ between platforms.
  • Clarify platform-specific limitations and offer Linux alternatives or workarounds when a feature is Windows-only.
  • Include troubleshooting steps and usage notes for both Windows and Linux environments.
  • Add more detail about Linux system integration (e.g., systemd service management, permissions, SELinux/AppArmor considerations) where relevant.
GitHub Create Pull Request
Cyclecloud Install the Command Line Interface ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows installation instructions for the CycleCloud CLI, but Windows-specific details (such as PowerShell scripts and GUI-based extraction) are given equal prominence. The Windows installation section references Windows Explorer and PowerShell, while the Linux section uses standard shell commands. The prerequisites section mentions installing Python for Windows, but assumes Linux/Mac users already have Python. There is a slight Windows-first bias in the prerequisites and the use of Windows tools (Explorer, PowerShell) without mentioning Linux equivalents for GUI extraction or scripting.
Recommendations
  • Provide parity in scripting examples: For Windows, offer command-line installation instructions (e.g., using Command Prompt or PowerShell commands to unzip and run the installer), not just GUI-based steps.
  • Mention Linux GUI alternatives for extracting zip files, such as using Nautilus or Archive Manager, to match the Windows Explorer example.
  • In the prerequisites, explicitly mention how to verify or install Python on Linux and Mac, not just Windows.
  • Ensure that both platforms have equal detail and clarity in their instructions, and avoid assuming prior knowledge for one platform over the other.
  • If PowerShell scripts are provided for Windows, consider providing Bash scripts for Linux where appropriate.
GitHub Create Pull Request
Cyclecloud Projects ...-docs/blob/main/articles/cyclecloud/how-to/projects.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references specs as Python, shell, or PowerShell scripts, but does not provide any concrete examples for Linux shell scripts or Linux-specific usage. The only explicit environment variable path examples are for Linux, but there are no corresponding Windows paths. There is no mention of Linux tools or patterns, and PowerShell is mentioned as a script type without parity for bash or other Linux shells. The documentation does not provide Linux-first or Linux-specific examples, and the CLI commands shown are platform-neutral but lack explicit Linux context.
Recommendations
  • Add explicit Linux shell script examples alongside PowerShell examples.
  • Provide Linux-specific file path examples (e.g., /var/log, /home/user) and contrast with Windows equivalents (e.g., C:\ClusterInit\...).
  • Mention bash or other Linux shells as supported script types wherever PowerShell is referenced.
  • Include Linux CLI usage patterns, such as using environment variables, permissions, and file system conventions.
  • Ensure that Linux tools and workflows are described with equal prominence to Windows/PowerShell ones.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows documentation links before or instead of Linux equivalents, especially in the section describing disk types for CycleCloud 8 and above. There are no explicit Linux or cross-platform command-line examples (e.g., Linux mount or format commands), and the links for disk types point to Windows-specific Azure docs. No PowerShell examples are present, but the lack of Linux CLI examples and the preference for Windows documentation indicate a bias.
Recommendations
  • Replace or supplement Windows-specific documentation links with Linux equivalents, especially in the 'Disk types' section (e.g., link to /azure/virtual-machines/linux/disks-types).
  • Provide Linux command-line examples for mounting and formatting disks (e.g., using 'lsblk', 'mkfs', 'mount').
  • Ensure parity in documentation references and examples for both Windows and Linux users.
  • Clarify any OS-specific behaviors or requirements for managed disks, and link to both Windows and Linux guides where relevant.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/cycleserver-configuration-reference.md ...cles/cyclecloud/cycleserver-configuration-reference.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation references both Linux and Windows in default values, but the overall structure and examples are minimal and do not provide Linux-specific usage patterns or command-line examples. The mention of the configuration file location is Linux-specific, but there are no equivalent details for Windows (e.g., file path, editing instructions). There are no examples of how to edit or manage the configuration file on either platform, but the lack of Linux command-line examples (such as using nano, vi, or systemctl) is notable. The documentation also lists Windows defaults after Linux in the table, but does not provide parity in operational guidance.
Recommendations
  • Add explicit instructions and examples for editing the configuration file on both Linux (e.g., using nano or vi) and Windows (e.g., using Notepad or PowerShell).
  • Include the default file path for the configuration file on Windows systems.
  • Provide examples of how to restart the CycleServer service after configuration changes on both Linux (e.g., systemctl) and Windows (e.g., using the Services MMC or PowerShell).
  • Ensure that any references to platform-specific defaults are accompanied by operational guidance for both platforms.
  • Consider adding a section that summarizes platform differences and best practices for both Linux and Windows users.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses on configuring Open OnDemand with Azure CycleCloud, but it demonstrates Windows bias by referencing Microsoft Entra ID (a Microsoft-specific authentication provider), using terminology and patterns familiar to Windows/Azure users, and omitting any Linux-specific configuration steps or examples. There are no references to Linux authentication providers, command-line configuration, or alternative tools. The workflow is described entirely through the CycleCloud web portal, which is a GUI-centric approach typical of Windows environments.
Recommendations
  • Include Linux-specific authentication options, such as configuring Open OnDemand with LDAP, Kerberos, or other open-source identity providers.
  • Provide command-line examples for updating configuration files directly on the Open OnDemand VM (e.g., editing YAML or shell scripts), not just through the web portal.
  • Mention and document equivalent Linux tools or workflows for managing clusters and authentication.
  • Clarify whether the instructions apply to both Windows and Linux-based clusters, and provide parity in examples and screenshots.
  • Add troubleshooting steps or notes relevant to Linux environments, such as SELinux, systemd, or file permissions.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/use-spot-instances.md .../main/articles/cyclecloud/how-to/use-spot-instances.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Windows Links Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently linking to Windows-specific Azure Spot VM documentation before Linux equivalents, referencing Windows documentation for core concepts (Spot VMs, pricing, eviction policy), and omitting Linux-specific configuration or usage examples. Linux links are only present in secondary contexts, and there are no Linux/Powershell command examples or explicit Linux tool references.
Recommendations
  • Provide equal prominence to Linux documentation links (e.g., link to both /azure/virtual-machines/windows/spot-vms and /azure/virtual-machines/linux/spot-vms where relevant).
  • Include Linux-specific examples or configuration snippets, especially if there are differences in how Spot VMs are managed or evicted on Linux VMs.
  • Mention Linux tools or patterns for handling scheduled events and eviction notifications (e.g., systemd services, shell scripts) alongside any Windows/Powershell approaches.
  • Ensure that references to Azure features (Spot pricing, eviction policy, scheduled events) include both Windows and Linux documentation, or use platform-neutral links when possible.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
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 (RDP, Microsoft RDP client) and examples are mentioned explicitly and sometimes before Linux equivalents. There are detailed instructions for setting up RDP tunnels for Windows, but no equivalent examples for connecting to Linux graphical desktops (e.g., via X11 forwarding or VNC). The documentation references Microsoft RDP client for macOS and Windows, but does not mention Linux RDP clients or alternatives. Overall, the page assumes familiarity with Windows tools and workflows, and omits Linux-specific graphical connection patterns.
Recommendations
  • Include examples for connecting to Linux graphical desktops, such as X11 forwarding (e.g., 'ssh -X') or VNC tunnels.
  • Mention Linux-compatible RDP clients (e.g., 'remmina', 'xfreerdp') when discussing RDP connections.
  • Provide parity in graphical connection instructions for both Linux and Windows nodes.
  • When describing connection methods, present Linux and Windows options side-by-side, rather than focusing on Windows tools first.
  • Clarify that SSH-based connections are standard for Linux nodes, and provide troubleshooting tips for common Linux SSH issues.
GitHub Create Pull Request
Cyclecloud https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/cyclecloud/how-to/cluster-templates.md ...b/main/articles/cyclecloud/how-to/cluster-templates.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Windows-specific Azure VM documentation (e.g., linking to /azure/virtual-machines/windows/spot-vms) and using Windows-centric machine types (Standard_D4v3, H16r) in examples. There are no explicit Linux or cross-platform command-line examples, nor are Linux-specific VM documentation or machine types referenced. The documentation does mention Ubuntu images in lookup tables, but the overall pattern is to present Windows-related concepts and tools first or exclusively.
Recommendations
  • Include links to both Windows and Linux Azure VM documentation when discussing features like Spot VMs.
  • Provide example machine types for Linux workloads (e.g., Standard_D2s_v3, Standard_B2ms) alongside Windows types.
  • Add explicit Linux-centric examples or references (such as using Linux images, SSH keys, or Linux-specific configuration patterns) where applicable.
  • Ensure that any referenced documentation or tooling is cross-platform or that Linux alternatives are mentioned with equal prominence.
  • Clarify that CycleCloud supports both Windows and Linux clusters, and provide guidance for each where differences exist.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux First Linux Tools
Summary
The documentation provides detailed Linux-centric examples and paths (e.g., Bash scripts, Linux file paths), while Windows-specific instructions, examples, or PowerShell equivalents are missing. Linux is consistently mentioned first, and only Linux scripting (Bash) is demonstrated. Windows support is referenced in passing, but without concrete examples or guidance.
Recommendations
  • Add equivalent Windows/PowerShell HealthCheck script examples, including file paths and script placement instructions.
  • Provide step-by-step instructions for creating and deploying HealthCheck scripts on Windows VMs.
  • Clarify any differences in script support or behavior between Linux and Windows, and ensure both platforms are equally represented in examples and guidance.
  • Include screenshots or command-line examples for Windows where GUI or CLI actions are shown for Linux.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides installation instructions for both Linux and Windows, but there is a noticeable Windows bias. Windows prerequisites and installation steps are described in detail, including references to Windows Explorer, PowerShell scripts, and GUI actions (right-click, Extract All), while Linux instructions use standard shell commands. The Windows section mentions specific tools (PowerShell, Command Prompt) and GUI patterns before their Linux equivalents. The prerequisites section explicitly calls out the need to install Python for Windows, while assuming Linux/Mac users already have Python. The CLI initialization and usage instructions are platform-neutral.
Recommendations
  • Provide equivalent Linux instructions for extracting the zip file using GUI tools (e.g., GNOME Files, KDE Dolphin) for parity with Windows Explorer steps.
  • Mention Linux shell alternatives to PowerShell for script execution, and clarify how to run install.sh with different shells if needed.
  • Include Mac-specific installation steps if supported, or clarify platform support.
  • Balance the prerequisites section by linking to Python installation guides for Linux and Mac, not just Windows.
  • Ensure that command-line examples are presented for both platforms in parallel, and avoid assuming Windows users prefer GUI actions while Linux users prefer CLI.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Device assignment is described using Azure Logical Unit Numbers (LUN) and references a PowerShell module link, which is a Windows-centric tool. No Linux-specific device assignment examples (such as using /dev/sdX or udev rules) are provided. The mention of Azure portal navigation and resource blades is also more familiar to Windows users. While the configuration examples use Linux-style mountpoints and filesystems, there is no explicit parity for Linux device management or command-line tooling.
Recommendations
  • Add Linux-specific device assignment examples (e.g., referencing /dev/sdX, using udev, or lsblk).
  • Include links to Azure CLI documentation alongside PowerShell references.
  • Provide explicit Linux command-line examples for mounting, formatting, and managing volumes.
  • Clarify that the configuration applies to both Windows and Linux nodes, and highlight any differences.
  • Mention Linux tools (e.g., parted, mkfs, cryptsetup) where appropriate.
GitHub 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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows mild Windows bias by listing Windows paths and behaviors before Linux equivalents, referencing Windows-specific features and limitations, and omitting Linux-specific command examples or details in some sections. While Linux is supported and mentioned, Windows is often presented first or with more detail.
Recommendations
  • Alternate the order of Windows and Linux references so that Linux is presented first in some sections.
  • Provide Linux-specific command examples where behaviors differ (e.g., for HealthCheck options, run_on_shutdown).
  • Include more details about Linux init scripts, service management, and integration points, similar to the detail given for Windows.
  • Clarify any Linux-specific behaviors or limitations, not just Windows-specific ones.
  • Ensure parity in documentation for both platforms, including troubleshooting steps, environment variables, and file locations.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric authentication methods (Active Directory) and examples (e.g., DOMAIN\user), mentioning Windows tools and patterns (Active Directory, Entra ID) before Linux equivalents, and omitting Linux-specific authentication examples or guidance (such as integration with OpenLDAP, sssd, or PAM). There are no Linux command-line examples or references to Linux-native tools for authentication management.
Recommendations
  • Add Linux-focused authentication examples, such as integrating with OpenLDAP or using sssd for LDAP/AD authentication.
  • Provide Linux command-line examples for managing authentication settings, such as using curl or CLI tools to configure CycleCloud.
  • Include Linux username formats and authentication patterns (e.g., uid/gid, user@domain, or POSIX account examples) alongside or before Windows examples.
  • Mention Linux-native tools and workflows for user management and authentication, not just GUI-based or Windows-centric approaches.
  • Ensure parity in troubleshooting steps, such as how to reset authentication or recover access from a Linux environment.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. It exclusively references Windows Server technologies, Active Directory, and Windows-specific tools (such as PowerShell scripts and Windows Scheduled Tasks). There are no Linux examples or equivalents, and Linux compute nodes are explicitly not supported. All configuration and operational guidance assumes a Windows-centric workflow.
Recommendations
  • Add explicit statements about Linux support plans and timelines, if any.
  • Provide Linux-based examples or clarify that Linux is not currently supported.
  • If possible, develop and document Linux-compatible tools or workflows for cluster management.
  • Mention Linux alternatives (e.g., cloud-init, Linux-based schedulers) where relevant, even if not supported, to guide cross-platform users.
  • Ensure that any future updates include parity for Linux environments, including CLI tools and automation scripts.
GitHub Create Pull Request
Cyclecloud Connecting to a Cluster Node ...lob/main/articles/cyclecloud/how-to/connect-to-node.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides instructions for connecting to both Linux and Windows cluster nodes, but Windows-specific tools and workflows (RDP, Microsoft RDP client) are mentioned explicitly and sometimes before Linux equivalents. There are detailed examples for setting up RDP tunnels for Windows nodes, but no equivalent examples for Linux graphical access (e.g., X11 forwarding). The documentation references the Microsoft RDP client for macOS and Windows, but does not mention Linux RDP clients or alternatives. Linux SSH access is described, but the focus is on command-line access, not graphical workflows.
Recommendations
  • Add explicit examples for Linux graphical access (e.g., X11 forwarding via SSH) alongside RDP examples for Windows.
  • Mention Linux-compatible RDP clients (such as Remmina, rdesktop, or FreeRDP) when discussing RDP connections.
  • Ensure that instructions for connecting to cluster nodes are presented in a balanced way, with Linux and Windows examples given equal prominence.
  • Where possible, provide side-by-side examples for both Linux and Windows workflows (e.g., connecting via SSH for Linux, connecting via RDP for Windows).
GitHub Create Pull Request
Cyclecloud Install the Command Line Interface ...n/articles/cyclecloud/how-to/install-cyclecloud-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides installation instructions for both Linux and Windows, but Windows-specific guidance (such as using Windows Explorer, PowerShell scripts, and references to Windows environment variables) is more detailed and uses Windows terminology. The Windows installation steps mention PowerShell and graphical extraction, while the Linux steps use standard shell commands. The prerequisite section specifically links to Windows Python installation, while noting Linux/Mac typically have Python installed. Windows examples and tools (Explorer, PowerShell) are described in more depth, and Windows is often mentioned first.
Recommendations
  • Provide parity in detail for Linux/macOS installation steps, including troubleshooting and environment setup.
  • Include macOS-specific instructions, as only Linux and Windows are covered.
  • Offer CLI-based extraction and installation steps for Windows (e.g., using PowerShell or Command Prompt), not just graphical methods.
  • Present Linux/macOS and Windows instructions in parallel, rather than Windows-first ordering.
  • Add links to Python installation for Linux/macOS, not just Windows.
GitHub Create Pull Request
Cyclecloud User Authentication ...main/articles/cyclecloud/how-to/user-authentication.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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-specific sign-in examples (EXAMPLE\username), and referencing Windows authentication patterns before Linux equivalents. There is little mention of Linux authentication tools or examples (e.g., OpenLDAP, sssd, PAM), and no Linux-specific configuration guidance is provided. The Entra ID section references Linux clusters, but only in the context of SSH key management, not authentication setup.
Recommendations
  • Add Linux/OpenLDAP-specific configuration examples and terminology (e.g., uid, cn, ou).
  • Provide Linux authentication patterns (e.g., username formats, PAM integration) alongside Windows examples.
  • Include step-by-step instructions for configuring LDAP authentication with common Linux servers.
  • Present examples for both Windows and Linux environments in parallel, rather than focusing on Windows first.
  • Reference Linux tools and utilities (e.g., ldapsearch, sssd) where appropriate.
GitHub Create Pull Request
Cyclecloud Jetpack Reference ...cs/azure-docs/blob/main/articles/cyclecloud/jetpack.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux First Linux Tools
Summary
The documentation is generally neutral or slightly Linux-biased. All command-line examples use Linux/Unix shell syntax, and paths are shown for both Windows and Linux, but Linux is listed first in most cases. There are no PowerShell or Windows Command Prompt examples, and some commands (e.g., run_on_shutdown) are explicitly unsupported on Windows. Linux-specific tools and concepts (e.g., bash scripts, udev rules) are mentioned, while Windows equivalents are not discussed.
Recommendations
  • Add Windows-specific command-line examples using PowerShell or Command Prompt syntax where appropriate.
  • Clarify which commands and features are supported on Windows vs. Linux, and provide alternatives or workarounds for Windows users.
  • Include information about Windows equivalents for Linux-specific features (e.g., how to register shutdown scripts on Windows, if possible).
  • Ensure that both Windows and Linux paths, tools, and workflows are presented with equal prominence.
GitHub Create Pull Request
Cyclecloud Connecting to a Cluster Node ...lob/main/articles/cyclecloud/how-to/connect-to-node.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both SSH (Linux/macOS) and RDP (Windows) connection methods, but Windows-specific tools and workflows (RDP, Microsoft RDP client) are mentioned explicitly and sometimes before Linux equivalents. There is a detailed example for connecting to Windows VMs (RDP tunnel), but no equivalent example for connecting to Linux graphical desktops (e.g., X11 forwarding). The documentation assumes familiarity with Windows tools and does not offer parity for Linux desktop access.
Recommendations
  • Provide explicit examples for connecting to Linux graphical desktops (e.g., X11 forwarding via SSH) alongside the RDP tunnel example for Windows.
  • Mention Linux/macOS remote desktop tools (e.g., Remmina, xrdp, VNC) where appropriate.
  • Ensure that instructions for SSH connections and tunnels are presented before or alongside Windows-specific instructions.
  • Clarify which steps apply to Linux/macOS and which to Windows, and avoid assuming the user is on Windows unless necessary.
  • Add notes or sections for Linux/macOS users on how to access graphical environments, if relevant.
GitHub Create Pull Request
Cyclecloud Volume Mount ...ocs/blob/main/articles/cyclecloud/how-to/mount-disk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page is generally platform-neutral in its configuration examples, focusing on Azure CycleCloud's INI-style syntax. However, there is a notable Windows bias in the 'Devices' section, where Azure device assignment is described using Logical Unit Numbers (LUN) and a link to a PowerShell module is provided. The mention of the Azure portal and its blades also reflects a Windows-centric approach. Linux-specific tooling and patterns (such as device naming conventions, mounting commands, or references to /dev paths) are not discussed, and there are no explicit Linux command-line examples. The LVM options are mentioned in the configuration table, but without Linux-specific guidance or parity in example walkthroughs.
Recommendations
  • Add Linux-specific examples for device assignment, such as referencing /dev/sdX or using udev rules.
  • Include sample Linux mount commands (e.g., mount, mkfs.ext4) and show how the configuration maps to actual Linux operations.
  • Provide parity in documentation by linking to both Windows and Linux tools for device management (e.g., PowerShell and Linux CLI).
  • Clarify how the configuration interacts with Linux systems, especially for advanced features like RAID and encryption (e.g., mdadm, cryptsetup).
  • Explicitly state platform differences where relevant, such as how device naming or mounting may differ between Windows and Linux.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →