High Performance Computing
24
Total Pages
12
Linux-Friendly Pages
12
Pages with Bias
50.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
48 issues found
Showing 1-25 of 48 flagged pages
High Performance Computing
Identity management configuration
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Windows-centric identity management solutions such as Active Directory Domain Services and Microsoft Entra ID. There are no mentions of Linux-native identity management tools (e.g., LDAP, FreeIPA, NIS), nor are there examples or resources for configuring identity management on Linux-based HPC clusters. All examples and external resources provided reference Windows technologies, and Windows tools are mentioned first and exclusively.
Recommendations
- Add sections describing Linux-native identity management solutions such as LDAP, FreeIPA, or NIS, and how they can be integrated into HPC environments.
- Provide example configurations or migration steps for Linux-based clusters, including authentication and user management.
- Include resources and links to documentation for Linux identity management tools.
- Balance the order of presentation so that both Windows and Linux solutions are introduced with equal prominence.
Create Pull Request
High Performance Computing
Identity management configuration
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-centric identity management tools such as Active Directory Domain Services and Microsoft Entra ID. It does not mention or provide examples of Linux-native identity management solutions (e.g., LDAP, FreeIPA, NIS), nor does it offer Linux command-line or configuration examples. All references, examples, and resources are centered on Windows technologies, which may alienate users operating Linux-based HPC clusters.
Recommendations
- Include Linux-native identity management tools such as OpenLDAP, FreeIPA, or NIS in the 'Tools and services' section.
- Provide example configurations or references for integrating Linux systems with identity management (e.g., using sssd, nsswitch.conf, or PAM modules).
- Add links to documentation or blog posts about authenticating Linux users in HPC clusters, both with and without integration to Active Directory.
- Present both Windows and Linux options side-by-side, or at least mention Linux alternatives, to ensure parity and inclusivity for cross-platform environments.
High Performance Computing
Network access configuration
...formance-computing/lift-and-shift-step-1-networking.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Azure bias by exclusively referencing Azure-specific tools (Bastion, VPN Gateway, Network Security Groups, DNS Private Resolver) and providing example steps that assume use of the Azure portal, which is most commonly used in Windows environments. There are no examples or guidance for Linux-specific tools, CLI usage, or cross-platform command-line approaches. No mention is made of SSH, Linux firewall tools, or Linux-native networking patterns.
Recommendations
- Include Linux-specific examples, such as using SSH to connect to VMs without public IPs, and configuring network access via Linux command-line tools.
- Provide CLI-based instructions (e.g., Azure CLI, PowerShell, Bash) for provisioning and accessing VMs, highlighting cross-platform compatibility.
- Mention Linux firewall tools (e.g., iptables, firewalld, ufw) and how they interact with Azure Network Security Groups.
- Add guidance for configuring DNS and VPN access from Linux environments, including relevant commands and troubleshooting steps.
- Balance references to Azure portal with equivalent steps for users on Linux or macOS systems.
High Performance Computing
Identity management configuration
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-centric identity management solutions, specifically Active Directory Domain Services and Microsoft Entra ID. There is no mention of Linux-native identity management tools (such as LDAP, FreeIPA, or SSSD), nor are there any examples or guidance for configuring identity management in Linux-based HPC environments. All examples and resources point to Windows tools and workflows.
Recommendations
- Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD, and describe how they can be integrated into HPC environments.
- Provide example configurations or workflows for Linux-based clusters, including user and group management, authentication, and integration with cloud services.
- Add resources and links to documentation for Linux identity management tools and best practices.
- Ensure that both Windows and Linux options are presented in parallel, with clear guidance for each platform.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-identity.md
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-centric identity management solutions, specifically Active Directory Domain Services and Microsoft Entra ID, without mentioning or providing examples for common Linux-based alternatives (such as LDAP, FreeIPA, or SSSD). All examples and resources are centered around Windows tools, and there are no Linux-specific instructions or parity in guidance.
Recommendations
- Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD in the 'Tools and services' section.
- Provide example setups for Linux-based clusters, including integration with Linux authentication systems.
- Add resources and links to documentation for Linux identity management tools.
- Ensure that best practices and performance considerations address both Windows and Linux environments.
- When referencing blog posts or guides, include at least one that demonstrates Linux-based identity management integration in HPC environments.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-identity.md
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page focuses exclusively on Windows-centric identity management tools such as Active Directory Domain Services and Microsoft Entra ID, with no mention of Linux-native alternatives (e.g., LDAP, FreeIPA, or SSSD). All examples and resources reference Windows-based solutions, and there are no Linux-specific or cross-platform identity management patterns provided.
Recommendations
- Include Linux-native identity management solutions such as OpenLDAP, FreeIPA, or SSSD in the 'Tools and services' section.
- Provide example setups or references for integrating Linux clusters with identity management, such as authenticating Linux nodes using LDAP or FreeIPA.
- Add resources and links to documentation for Linux-based identity management tools and best practices.
- Ensure that examples and recommendations are balanced, presenting both Windows and Linux options where applicable.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-3-storage.md
...performance-computing/lift-and-shift-step-3-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Azure-specific tools and patterns (such as Azure AD, RBAC, and SMB/NTLMSSP) are emphasized, and Windows-centric protocols (SMB) and tools (AzCopy) are mentioned before or more prominently than their Linux equivalents. While Linux/NFS examples are present, there is a lack of parity in command-line examples for Linux tools (e.g., rsync is only briefly mentioned in best practices, not in detailed steps or examples), and Windows/SMB mounting is described in more detail. There are no PowerShell-specific examples, but the overall focus is on Azure-native and Windows-friendly approaches.
Recommendations
- Provide Linux-native command-line examples (e.g., rsync, scp, or Linux AzCopy usage) alongside or before Windows/Azure tools.
- When describing mounting procedures, offer both Linux and Windows client instructions (e.g., show how to mount Azure Files on Windows using PowerShell or 'net use', and on Linux using 'mount -t cifs').
- Include explicit Linux authentication and access control guidance (e.g., using Linux PAM, Kerberos, or LDAP with Azure AD integration) to balance the focus on Azure AD/RBAC.
- Mention open-source or cross-platform alternatives to Azure Data Factory and AzCopy, such as Apache NiFi, rclone, or native Linux scripting.
- Ensure that Linux/NFS and Windows/SMB examples are given equal prominence and detail in all setup and deployment sections.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-job-scheduler.md
...mance-computing/lift-and-shift-step-2-job-scheduler.md
High Priority
View Details →
Detected Bias Types
Windows Missing
Linux First
Missing Windows Example
Summary
The documentation demonstrates a Linux-first bias, as all job scheduler examples (Slurm commands, shell scripts) are provided exclusively in Bash and for Linux environments. There are no Windows or PowerShell examples, nor is there mention of Windows-native HPC schedulers or Windows-specific deployment patterns. The documentation assumes a Linux-based workflow throughout.
Recommendations
- Add equivalent PowerShell examples for deploying and configuring job schedulers via CycleCloud on Windows nodes.
- Include examples of job submission using Windows-native tools or demonstrate how to submit jobs from a Windows environment (e.g., using PowerShell or Windows Subsystem for Linux).
- Mention whether CycleCloud and the supported schedulers (Slurm, PBSPro, etc.) can be deployed on Windows compute nodes, and if not, clarify this limitation.
- If Windows-based HPC schedulers (such as Microsoft HPC Pack) are supported, provide guidance or references for their configuration and migration.
- Explicitly state OS compatibility for each scheduler and provide parity in examples for both Linux and Windows where possible.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-networking.md
...formance-computing/lift-and-shift-step-1-networking.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates bias by focusing exclusively on Azure-native tools (such as Bastion and VPN Gateway) that are commonly accessed via the Azure Portal or Windows-centric workflows. There are no examples or mentions of Linux command-line tools (e.g., SSH, scp, Linux VPN clients), nor are there any Linux-specific configuration steps or considerations. The example steps for setup and deployment assume use of the Azure Portal and Bastion, which are more familiar to Windows administrators, and do not provide parity for Linux users or CLI-based workflows.
Recommendations
- Include example steps for connecting to VMs using SSH from a Linux or macOS terminal, not just via Bastion or the Azure Portal.
- Mention and provide examples of using Azure CLI and/or PowerShell for network configuration, ensuring both Windows and Linux command-line workflows are covered.
- Reference Linux-native VPN clients and tools for connecting to Azure VPN Gateway, such as strongSwan or OpenVPN.
- Add a section or callout for Linux administrators, highlighting any differences or best practices for Linux-based HPC environments.
- Ensure all example commands and screenshots are cross-platform or provide both Windows and Linux variants.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-overview.md
...erformance-computing/lift-and-shift-step-2-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by prioritizing Windows-centric technologies (such as Active Directory) and Azure-specific tools for identity and node health checks, without providing equivalent Linux-native alternatives or examples. There is a lack of explicit Linux-focused tools, patterns, or examples, especially in areas like identity management and monitoring, which are critical in HPC environments that often run on Linux.
Recommendations
- For identity management, mention and provide examples for Linux-native solutions such as FreeIPA, OpenLDAP, or SSSD, and discuss their integration with cloud environments.
- In the monitoring and node health check sections, include references to widely-used Linux tools (e.g., Nagios, Prometheus, Ganglia, collectd) and how they can be adapted for cloud-based HPC clusters.
- When discussing quick start setups, provide both Windows/Azure-centric and Linux-native workflows or scripts, ensuring parity in guidance.
- Explicitly mention and provide examples for Linux-based job schedulers and their cloud migration (e.g., Slurm on Azure or other clouds), including any differences in setup or automation.
- Balance references to Azure-specific tools (like Bicep) with cross-platform or Linux-preferred automation tools (such as Terraform, Ansible, or shell scripting).
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-identity.md
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively references Windows-centric identity management tools such as Active Directory Domain Services and Microsoft Entra ID. There are no mentions or examples of Linux-native or cross-platform identity management solutions (e.g., LDAP, FreeIPA, or SSSD). All examples and resource links focus on Windows tools, with no parity for Linux environments.
Recommendations
- Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD as alternatives or complements to Active Directory.
- Provide example setups and configuration steps for Linux-based HPC clusters, not just those using Active Directory.
- Add resource links to documentation for Linux identity management tools and integration guides.
- Present both Windows and Linux options in parallel, rather than focusing exclusively on Windows tools.
- If possible, include a comparison table of identity management options for both Windows and Linux environments.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-monitor.md
...performance-computing/lift-and-shift-step-2-monitor.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively focusing on Azure-native tools and workflows, with all examples and instructions tailored to the Azure portal and Azure CLI. There is no mention of Linux-native monitoring tools (such as collectd, sysstat, or native Prometheus deployments), nor are there examples for on-premises Linux environments or cross-platform CLI alternatives. The only script example is a Bash script using the Azure CLI, but it is still Azure-specific. There are no references to Powershell, but the overall approach assumes Azure as the primary platform, which may not address the needs of Linux/HPC administrators seeking parity with traditional Linux monitoring stacks.
Recommendations
- Include examples of integrating traditional Linux monitoring tools (e.g., collectd, sysstat, Nagios, Ganglia) with Azure Monitor or Grafana.
- Provide alternative setup instructions for environments where Azure CLI is not available, such as using native Linux tools or open-source Prometheus/Grafana deployments.
- Add explicit Linux-native monitoring workflow examples, such as configuring node exporters, using systemd service checks, or leveraging SSH-based health checks.
- Mention and compare Azure-native tools with their Linux/open-source equivalents, and provide guidance for migrating or integrating existing Linux monitoring setups.
- Clarify that while Azure tools are recommended, the guidance can be adapted for hybrid or non-Azure Linux environments.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-identity.md
...erformance-computing/lift-and-shift-step-2-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning Windows-centric identity management tools (Active Directory Domain Services, Microsoft Entra ID) and providing no mention or examples of Linux-native identity management solutions (such as LDAP, FreeIPA, or SSSD). All examples and resources are focused on Windows technologies, with no Linux equivalents or guidance provided.
Recommendations
- Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD alongside Active Directory and Entra ID.
- Provide example configurations or references for integrating Linux HPC clusters with identity management systems.
- Add resources and links to documentation for Linux identity management tools and their integration with Azure or hybrid environments.
- Ensure that best practices and tool recommendations are platform-neutral or provide parity between Windows and Linux options.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-job-scheduler.md
...mance-computing/lift-and-shift-step-2-job-scheduler.md
High Priority
View Details →
Detected Bias Types
Windows Missing
Linux First
Missing Windows Example
Summary
The documentation page demonstrates a bias toward Linux environments, particularly Slurm, with all example commands and job submission scripts using Linux shell syntax and Linux-native tools. There are no Windows or PowerShell examples, nor is there mention of Windows-native job schedulers or Windows-specific configuration patterns. The documentation assumes a Linux-based HPC environment throughout.
Recommendations
- Add examples for deploying and configuring job schedulers on Windows-based compute nodes, if supported by CycleCloud.
- Include PowerShell equivalents for job submission and scheduler configuration commands.
- Mention Windows-native HPC schedulers (such as Microsoft HPC Pack) if relevant, or clarify their support status.
- Provide guidance on integrating Windows workloads or mixed-OS clusters if supported by the platform.
- Explicitly state OS requirements and compatibility for each scheduler and tool discussed.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-overview.md
...erformance-computing/lift-and-shift-step-2-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Windows-centric technologies such as Active Directory for identity management and Azure-specific node health checks. While some Linux-relevant tools (e.g., Slurm, spack, easybuild) are mentioned, there is a lack of Linux-specific examples or parity in recommendations, especially for identity and monitoring. The document also references Azure and Bicep (Microsoft-centric), with no equivalent Linux-native or cross-platform alternatives highlighted or explained.
Recommendations
- For identity management, mention and provide examples for Linux-native solutions such as FreeIPA, OpenLDAP, or SSSD, and discuss their integration with cloud environments.
- When recommending monitoring and node health checks, include open-source, cross-platform tools (e.g., Nagios, Prometheus, Ganglia) and describe how they can be used in cloud HPC clusters.
- Balance references to Azure and Bicep with examples using Terraform, Ansible, or other cross-platform Infrastructure as Code tools, and provide Linux-based quick start setups.
- Ensure that for every Windows-centric tool or pattern mentioned (e.g., Active Directory, Azure-specific features), an equivalent Linux or open-source alternative is described, with guidance on usage.
- Add explicit Linux command-line or configuration examples alongside any Windows/Azure examples to ensure parity and inclusivity for Linux users.
High Performance Computing
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-3-storage.md
...performance-computing/lift-and-shift-step-3-storage.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Azure-specific tools and services (such as Azure Files, Azure Active Directory, and RBAC) are emphasized, and Windows-centric protocols (SMB, CIFS) and tools (AzCopy, Azure Data Box) are mentioned prominently. While Linux/NFS examples are included, Windows tools and patterns are often mentioned first or exclusively, and there is a lack of parity in providing Linux-native alternatives or examples for some scenarios (e.g., no Linux-native command-line data transfer tools like scp/rsync are discussed in detail). The documentation assumes Azure as the only platform and does not address cross-platform or Linux-first workflows in depth.
Recommendations
- Provide Linux-native command-line examples for data transfer (e.g., using rsync, scp, or sftp) alongside AzCopy.
- When mentioning protocols, list NFS (Linux/UNIX) before or alongside SMB/CIFS (Windows), and provide equal detail for both.
- Include examples of configuring storage access and permissions using Linux-native identity and access management tools (e.g., POSIX ACLs, LDAP) in addition to Azure AD/RBAC.
- Offer guidance for integrating with non-Azure, open-source, or Linux-based storage solutions to support hybrid or multi-cloud scenarios.
- Explicitly state when a tool or protocol is cross-platform, and clarify any Windows-specific limitations or requirements.
- Balance the order and depth of examples so that Linux and Windows users receive equal attention and actionable guidance.
High Performance Computing
Network access configuration
...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on Azure-native tools and workflows for network access configuration, such as Azure Bastion and VPN Gateway, without providing examples or guidance for Linux/macOS users or mentioning platform-specific access methods (e.g., SSH from Linux/macOS terminals). There are no PowerShell-specific examples, but the absence of Linux/macOS command-line or tool references creates a subtle Windows/Azure portal bias.
Recommendations
- Add explicit examples for accessing Azure VMs using SSH from Linux/macOS terminals.
- Include CLI-based instructions (e.g., using Azure CLI on Linux/macOS) alongside portal-based steps.
- Mention platform-agnostic tools and workflows, such as OpenSSH, and clarify that Bastion can be accessed from any OS.
- Provide parity in examples by showing both portal and command-line approaches for network configuration.
High Performance Computing
Monitoring configuration
...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on Azure-native monitoring tools and workflows, with all examples and step-by-step instructions referencing the Azure portal and Azure CLI. There is no mention of Windows-specific tools like PowerShell, but the documentation does not provide any Linux/macOS-specific examples, nor does it reference Linux monitoring tools or patterns. The only script example uses Bash and Azure CLI, which is cross-platform, but the overall guidance assumes users are operating in the Azure ecosystem, which may be more familiar to Windows administrators. There is no explicit Windows bias, but Linux parity is lacking in terms of examples and alternative tool references.
Recommendations
- Include examples of integrating native Linux monitoring tools (e.g., collectd, sysstat, Nagios, or custom scripts) with Azure Monitor, Grafana, or Prometheus.
- Provide instructions for configuring monitoring using Linux command-line tools and workflows, such as using systemd timers or cron jobs for health checks.
- Mention how to deploy and manage Prometheus and Grafana on Linux VMs outside of Azure Managed services.
- Add references to Linux-specific documentation or community resources for HPC monitoring.
- Clarify that Azure CLI and Bash scripts are cross-platform and provide any necessary notes for Linux/macOS users (e.g., authentication differences, package installation).
High Performance Computing
Network access configuration
...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation focuses exclusively on Azure-native tools (Bastion, VPN Gateway, Network Security Groups, DNS Private Resolver) for network access configuration, which are platform-agnostic but the example steps and workflow are implicitly Windows-centric. There are no examples or guidance for Linux/macOS users, such as SSH tunneling, CLI usage, or alternative connection methods. The documentation does not mention Linux-specific patterns or tools, nor does it provide parity in example commands or workflows for non-Windows environments.
Recommendations
- Add example steps for connecting to VMs using SSH from Linux/macOS terminals, including CLI commands.
- Include guidance on using Azure CLI or PowerShell for both Windows and Linux environments.
- Mention alternative connection methods (e.g., SSH tunneling) for users who do not use Bastion.
- Provide examples of configuring network rules using CLI tools available on Linux/macOS.
- Clarify that Azure Bastion and VPN Gateway are platform-agnostic, and show how to use them from Linux/macOS.
High Performance Computing
Identity management configuration
...erformance-computing/lift-and-shift-step-2-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Windows-centric identity management solutions, namely Active Directory Domain Services and Microsoft Entra ID. There is no mention of Linux-native identity management tools (such as LDAP, FreeIPA, or SSSD), nor are any Linux/macOS-specific configuration examples provided. All examples and resource links pertain to Windows technologies, creating a notable bias toward Windows environments.
Recommendations
- Include Linux-native identity management solutions such as LDAP, FreeIPA, or SSSD in the 'Tools and services' section.
- Provide example setups for authenticating Linux HPC cluster nodes, including integration with Linux-based identity management systems.
- Add resource links to documentation for Linux identity management tools and best practices.
- Balance examples and guidance between Windows and Linux platforms, or clearly indicate platform-specific instructions.
High Performance Computing
Monitoring configuration
...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on Azure-native monitoring tools and workflows, which are largely platform-agnostic, but the step-by-step instructions and UI references are tailored to the Azure Portal (web interface) and do not mention Linux-specific command-line alternatives or open-source monitoring tools commonly used in Linux HPC environments. The only script example provided is a Bash script using the Azure CLI, which is cross-platform, but there are no Linux-specific monitoring tool examples (e.g., collectd, sysstat, Nagios) or instructions for integrating native Linux tools with Azure services. All examples and workflows assume use of Azure's web UI or Azure CLI, with no mention of Powershell, but also no explicit Linux-first guidance.
Recommendations
- Include examples of integrating native Linux monitoring tools (e.g., collectd, sysstat, Nagios, Munin) with Azure Monitor, Grafana, or Prometheus.
- Provide Linux command-line workflow examples for setting up monitoring, such as using systemd timers, cron jobs, or shell scripts for health checks.
- Add documentation for configuring monitoring using Linux configuration files and automation tools (e.g., Ansible, Chef, Puppet) in addition to Azure Automation.
- Explicitly mention that Azure CLI and Bash scripts are cross-platform and provide guidance for running these on Linux systems.
- Offer parity by including screenshots or instructions for Linux desktop environments where relevant (e.g., accessing Grafana dashboards from Linux browsers).
High Performance Computing
End-to-end lift and shift architecture overview
.../high-performance-computing/lift-and-shift-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes the lift and shift process for HPC environments to Azure, but it lacks explicit examples or references to Linux-specific tools, patterns, or commands. While it mentions job schedulers common in Linux HPC (Slurm, PBS, LSF), the guidance and quick start recommendations focus on Azure-specific tools (CycleCloud) without providing parity for Linux-native deployment or management approaches. No Linux CLI or shell examples are given, and there is no mention of Linux-specific configuration or troubleshooting steps. The structure and recommendations implicitly prioritize Windows/Azure management paradigms over Linux-native ones.
Recommendations
- Include Linux shell (bash) examples for common administrative tasks (e.g., cluster deployment, monitoring, troubleshooting).
- Provide guidance on integrating Linux-native tools (such as Ansible, shell scripts, or Linux CLI utilities) for cluster management alongside Azure tools.
- Add references to Linux-based deployment templates or automation scripts (for example, Terraform or ARM templates tailored for Linux clusters).
- Explicitly mention Linux OS considerations for HPC workloads, including configuration, security, and performance tuning.
- Ensure that any quick start or best practice guides include Linux-centric options and examples, not just Azure/Windows-focused solutions.
High Performance Computing
Monitoring configuration
...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on Azure-native monitoring tools and workflows, with all examples and step-by-step instructions referencing the Azure portal, Azure CLI, and Azure services. There is no mention of Windows-specific tools (such as PowerShell), but the documentation does not provide any Linux-specific examples, nor does it reference Linux-native monitoring tools or workflows (e.g., systemd, collectd, syslog, native Prometheus installs). The only script example uses Azure CLI (which is cross-platform), but there is no explicit Linux parity or guidance for Linux users or clusters. The documentation assumes the use of Azure-managed services and does not address scenarios where Linux tools or open-source alternatives might be preferred or required.
Recommendations
- Add Linux-native monitoring examples, such as configuring Prometheus directly on Linux HPC nodes, using collectd, syslog, or systemd for health checks.
- Include sample scripts for health checks using bash and Linux utilities (e.g., top, free, systemctl) alongside Azure CLI examples.
- Mention open-source alternatives and how they can be integrated with Azure services, especially for users migrating from Linux-based on-premises clusters.
- Provide guidance for configuring monitoring on Linux VMs, including agent installation and troubleshooting steps specific to Linux.
- Clarify which steps are platform-agnostic and which require adaptation for Linux environments, ensuring parity in instructions for both Windows and Linux users.
High Performance Computing
End-to-end lift and shift architecture overview
.../high-performance-computing/lift-and-shift-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes the lift and shift process for HPC environments in a platform-neutral way, mentioning common HPC job schedulers (Slurm, PBS, LSF) that are typically Linux-based. However, there is evidence of Windows bias: Azure-specific tools and products are referenced (e.g., CycleCloud) without mention of Linux-native deployment patterns or open-source alternatives. There are no explicit Linux command-line or configuration examples, and no mention of Linux-specific tools or best practices for migration, despite the fact that most HPC environments are Linux-based.
Recommendations
- Include Linux-specific examples for deployment, configuration, and migration steps (e.g., bash scripts, Linux CLI commands).
- Mention open-source or Linux-native orchestration tools (such as Ansible, Terraform, or native Slurm deployment guides) alongside Azure CycleCloud.
- Provide parity in documentation by listing both Windows and Linux approaches for common administrative tasks.
- Reference Linux monitoring and management tools (e.g., Ganglia, Nagios) when discussing monitoring and health checks.
- Add links to official documentation for Linux-based HPC environments and migration guides.
High Performance Computing
Network access configuration
...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing setup and deployment examples using the Azure Portal and Bastion, which are most commonly associated with Windows workflows. There are no Linux-specific examples, CLI commands, or references to SSH, which are standard for Linux environments. The tools and patterns described (Azure Bastion, VPN Gateway, Network Security Groups) are presented in a generic way but the example steps focus on portal-based access, which is typically Windows-centric and omits Linux command-line or SSH-based approaches.
Recommendations
- Add Linux-specific examples, such as using SSH to connect to VMs via Bastion or VPN Gateway.
- Include Azure CLI or PowerShell examples for both Windows and Linux users.
- Mention Linux tools and workflows (e.g., OpenSSH, scp, Linux firewall configuration) alongside Azure portal instructions.
- Provide parity in step-by-step guides for both Windows and Linux environments, ensuring that Linux administrators have clear instructions.
- Explicitly state cross-platform compatibility of Azure Bastion and other services, and link to documentation for Linux users.