Various multinode fixes and features #411
Conversation
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
4afb67e to
9c50bdb
Compare
This change allows ansible facts to be used in group_vars/*/network-interfaces, which can be used to select the default network interface. This means different flavors and images can be used without needing to manually change the interface. It also reduces the MTU of all networks except external.
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
9c50bdb to
ba70aa7
Compare
Alex-Welsh
changed the title
Alex-Welsh
changed the title
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
57c377f to
fb15500
Compare
This fix sets seed_enable_snat and fixes the external IP of the seed which (in conjunction with an update to the multinode openstack configuration to set the gateway on the external subnet) allows VMs to reach the internet.
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
fb15500 to
aa72bfa
Compare
|
This PR is twinned with this change for the multinode openstack configuration which uses the seed as the gateway on the external subnet. |
| - name: Configure VXLAN | ||
| hosts: controllers,compute,seed,storage | ||
| gather_facts: false | ||
| gather_facts: true |
There was a problem hiding this comment.
There is potential for some incorrect behaviour here, since facts are gathered as the bootstrap user using the system python interpreter, some facts may be incorrect. In general we disable fact gathering during the user & venv bootstrap phase of host configure to avoid this. I think this is mostly an issue when using fact caching, but I can't remember all the details.
Let's try it like this, but keep an eye out for odd owner/permissions issues.
| @@ -0,0 +1,2 @@ | |||
| external_ips: | |||
| alex-mn-seed: 192.168.38.3 No newline at end of file | |||
There was a problem hiding this comment.
This isn't going to work if you change the cluster name...
There was a problem hiding this comment.
yeah, painfully obvious once I actually thought about it. Is there some magic way of getting the name of the seed in Kayobe or will it need to be terraform templated?
There was a problem hiding this comment.
Possibly you could use {{ groups['seed'][0] }} as the key, but I don't think the ip-allocation playbook would handle this.
I think currently terraform does not know about the IP subnets in this config, and it should probably stay that way.
Alternatively we could rely on the fact that kayobe seed host configure runs first and will grab this IP.
There was a problem hiding this comment.
Possibly you could use
{{ groups['seed'][0] }}as the key, but I don't think the ip-allocation playbook would handle this.
I gave that a go but it doesn't seem to template properly. Surprisingly it didn't error out but it also didn't apply the change.
I think we may just have to assume it's on 192.168.38.3 and change either the kayobe or openstack configuration if the environment is different
releasenotes/notes/add-monitoring-to-multinode-958603f026edbc7c.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/add-vm-overcloud-support-92baa7c2ce87ac1d.yaml
Outdated
Show resolved
Hide resolved
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
3e4a82a to
467153c
Compare
Alex-Welsh
force-pushed
the
multinode_vm_overcloud
branch
from
467153c to
ac6f534
Compare
|
Closing this PR and swtiching target to stackhpc/xena |
No description provided.