-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Task to create tunelo-calico network/subnet #290
Conversation
Added a task in the k3s playbook to create the tunelo-calico network and the tunelo-calico subnet that are both necessary for the management of hub and spoke ports and the proper functioning of tunelo.
kolla_toolbox: | ||
module_name: os_network | ||
module_args: | ||
auth: "{{ openstack_auth }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add project: "{{ keystone_admin_project }}"
|
||
- name: Create tunelo-calico subnet | ||
kolla_toolbox: | ||
module_name: os_subnet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add project: "{{ keystone_admin_project }}"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would leave the "{{ physical_network_calico }}" and "{{ physical_network_tunelo }}" hardcoded for now.
I'll add templating for them when I refactor the post-deploy network creation, as it's not useful before then. (can't make two different flat networks on the same physnet, so need to template everything else)
Otherwise LGTM
1e774ac
to
85bb025
Compare
Added a task in the k3s playbook to create the tunelo-calico network and the tunelo-calico subnet that are both necessary for the management of hub and spoke ports and the proper functioning of tunelo.