Skip to content

feat: add awi bec vms to realm register#12

Merged
wakonig merged 1 commit intomainfrom
feature/awi_dev_machines
Sep 11, 2025
Merged

feat: add awi bec vms to realm register#12
wakonig merged 1 commit intomainfrom
feature/awi_dev_machines

Conversation

@wakonig
Copy link
Copy Markdown
Member

@wakonig wakonig commented Sep 11, 2025

No description provided.

Copilot AI review requested due to automatic review settings September 11, 2025 07:57
@codecov
Copy link
Copy Markdown

codecov Bot commented Sep 11, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@wakonig wakonig merged commit 2fdc230 into main Sep 11, 2025
11 checks passed
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new realm configuration for AWI BEC development virtual machines to the developer machines deployment configuration. It introduces a new PSI_office_BEC_VM realm with six development VMs (awi-bec-dev-01 through awi-bec-dev-06) managed by the unx-bec_core group.

  • Adds PSI_office_BEC_VM realm configuration with unx-bec_core as the manager group
  • Configures six AWI BEC development VMs with consistent naming and access patterns
  • All VMs are configured with identical access permissions for the unx-bec_core group

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment on lines +69 to +70
awi-bec-dev-01.psi.ch:
name: AWI BEC Development VM 01
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Copilot uses AI. Check for mistakes.
Comment on lines +76 to +77
awi-bec-dev-02.psi.ch:
name: AWI BEC Development VM 02
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Copilot uses AI. Check for mistakes.
Comment on lines +83 to +84
awi-bec-dev-03.psi.ch:
name: AWI BEC Development VM 03
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Copilot uses AI. Check for mistakes.
Comment on lines +69 to +110
awi-bec-dev-01.psi.ch:
name: AWI BEC Development VM 01
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-02.psi.ch:
name: AWI BEC Development VM 02
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-03.psi.ch:
name: AWI BEC Development VM 03
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-04.psi.ch:
name: AWI BEC Development VM 04
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-05.psi.ch:
name: AWI BEC Development VM 05
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-06.psi.ch:
name: AWI BEC Development VM 06
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Suggested change
awi-bec-dev-01.psi.ch:
name: AWI BEC Development VM 01
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-02.psi.ch:
name: AWI BEC Development VM 02
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-03.psi.ch:
name: AWI BEC Development VM 03
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-04.psi.ch:
name: AWI BEC Development VM 04
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-05.psi.ch:
name: AWI BEC Development VM 05
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
awi-bec-dev-06.psi.ch:
name: AWI BEC Development VM 06
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
# Define a common VM deployment structure using YAML anchor
awi-bec-dev-common: &awi_bec_dev_vm
description: Development machine in the office network
deployment_access:
- unx-bec_core
experiment_access:
- unx-bec_core
# Use the anchor for each VM, overriding the name field
awi-bec-dev-01.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 01
awi-bec-dev-02.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 02
awi-bec-dev-03.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 03
awi-bec-dev-04.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 04
awi-bec-dev-05.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 05
awi-bec-dev-06.psi.ch:
<<: *awi_bec_dev_vm
name: AWI BEC Development VM 06

Copilot uses AI. Check for mistakes.
Comment on lines +97 to +98
awi-bec-dev-05.psi.ch:
name: AWI BEC Development VM 05
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Copilot uses AI. Check for mistakes.
Comment on lines +104 to +105
awi-bec-dev-06.psi.ch:
name: AWI BEC Development VM 06
Copy link

Copilot AI Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The configuration contains significant code duplication across all six VMs. Each VM has identical structure with only the number changing. Consider using a template or loop structure if the YAML processor supports it, or document why identical configurations are necessary for maintainability.

Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants