Skip to content

Conversation

@dandrushko
Copy link
Contributor

Network verification tests performing the following tests:

  • Get all configured OpenNebula networks
  • Creates VM at each OpenNebula network
  • pings from each VM default gateway
  • resolves external host using configured DNS server
  • pings external host

@tinova tinova requested review from Aletibazo and ArnauGabrielAtienza and removed request for tinova January 19, 2026 15:48
- hosts: "{{ frontend_group | d('frontend') }}"
roles:
- role: validation

Copy link
Contributor

Choose a reason for hiding this comment

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

No need for this playbook, the validation role is already invoked in the main validation.yml playbook

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The basic idea is to run those optional networkings tests in scope of generic validation framework. So those tests are part of the validation role

ansible.builtin.include_tasks:
file: "{{ role_path }}/tasks/networks_verification.yml"
when: validation.networks_verification

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we should create a specific role for this network task and change the validation role into a different name like services. Just a suggestion.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this relates to the comment above: The basic idea is to run those optional networkings tests in scope of generic validation framework. So those tests are part of the validation role originally. However not a big deal to split them out.

@dandrushko
Copy link
Contributor Author

@ArnauGabrielAtienza , @roamingengineer311 please review the latest commit per discussion we had

@balazsbme balazsbme removed their request for review January 23, 2026 14:59
Copy link
Contributor

Choose a reason for hiding this comment

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

I haven't tested it yet, but i suggest to move everything to main.yml since role looks like completed and if we want to add something we will add to the code of a main.yml

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done in the latest commit

@dandrushko
Copy link
Contributor Author

@ArnauGabrielAtienza , @Aletibazo, please review

@roamingengineer311
Copy link
Contributor

image

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