os-collect-config ec2 collector should attempt config-drive before nova metadata server
Bug #1619074 reported by
Steve Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Steve Baker |
Bug Description
overcloud nodes are booted with a functioning config-drive, and cloud-init uses this for boot configuration.
However the os-collect-config ec2 collector fetches the same data from the nova metadata server. If the ec2 collector is treated as immutable as per bug 1619072 then config-drive can be used as the data source instead of the nova metadata server.
This can result in a significant reduction in complexity - the openstack-nova-api service can be switched off on the undercloud and routing to 169.254.169.254 removed.
Changed in tripleo: | |
assignee: | nobody → Steve Baker (steve-stevebaker) |
Changed in tripleo: | |
milestone: | newton-rc1 → newton-rc2 |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
To post a comment you must log in.
Sounds reasonable, although I'd like to check the impact of disabling the metadata server - AFAIK there are actually two sets of metadata served via the magic metadata IP, the ec2 stuff and the native key/value pairs, the latter we may want to keep because we expose the sever metadata property in t-h-t (and it can be updated).
Regardless, the occ optimization seems worthwhile