Skip to content

fix(utils): domain alignment compliance - Galaxy structure, role documentation, and status integration - #5138

Merged
Venu-p1 merged 2 commits into
dell:issue-4849-omnia-modernizationfrom
Venu-p1:fix/domain-alignment
Sep 4, 2026
Merged

fix(utils): domain alignment compliance - Galaxy structure, role documentation, and status integration#5138
Venu-p1 merged 2 commits into
dell:issue-4849-omnia-modernizationfrom
Venu-p1:fix/domain-alignment

Conversation

@Venu-p1

@Venu-p1 Venu-p1 commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

PR Description

Description of the Solution

Summary: Improves utils domain compliance with Galaxy collection standards by adding missing directory structure, role documentation, and domain status writer integration across all playbooks. This addresses key findings from the domain alignment report.

Changes

Galaxy Structure

  • Added plugins/module_utils/README.md - Documentation for future module utilities
  • Added containers/README.md - Documentation for future container assets
  • Added vars/README.md - Documentation for domain-level variables

Role Documentation

  • Added roles/collect_install_os_credentials/README.md - Documents credential collection lifecycle, security features, and usage
  • Added roles/validate_install_os_config/README.md - Documents configuration validation logic, execution modes, and NFS path handling

Domain Integration

  • Integrated utils_status_writer role across all 6 playbooks for domain-level status tracking
  • Added execution start/end time tracking to all playbooks
  • Fixed status writer conditional logic to handle successful playbook execution
  • Added comment in utils.yml explaining utils domain does not support standard lifecycle tags (validate, credentials, prepare, execute) as it's a utility domain rather than deployment domain

Signed-off-by: venu <236371043+Venu-p1@users.noreply.github.com>
@Venu-p1 Venu-p1 changed the title Fix/domain alignment fix(utils): domain alignment compliance - Galaxy structure, role documentation, and status integration Sep 3, 2026
…ions

- Update status file path to project-specific output directory
- Change status file format from domain/status to utility/overall_status
- Update validation logic to check for correct field names
- Ensure omnia-cli can read and display utils domain status correctly

This fixes the issue where omnia-cli showed "no status" for utils domain
even though status files were being written to incorrect location/format.

Signed-off-by: venu <236371043+Venu-p1@users.noreply.github.com>
@Venu-p1
Venu-p1 merged commit e4f64f5 into dell:issue-4849-omnia-modernization Sep 4, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants