Merge ~joschi36/cloud-init:use-data-server-dns-entry into cloud-init:master
Proposed by
Joshua Hügli
Status: | Merged |
---|---|
Approved by: | Ryan Harper |
Approved revision: | cfb75bbc71a5c620d2a65a749e1ba440c1c43837 |
Merge reported by: | Chad Smith |
Merged at revision: | 9662a8791e53bac40a3a37aa3f5bee3076f7d447 |
Proposed branch: | ~joschi36/cloud-init:use-data-server-dns-entry |
Merge into: | cloud-init:master |
Diff against target: |
47 lines (+20/-2) 1 file modified
cloudinit/sources/DataSourceCloudStack.py (+20/-2) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ryan Harper | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Joshua Hügli (community) | Approve | ||
Scott Moser | Needs Information | ||
Dan Watkins | Pending | ||
Review via email: mp+371807@code.launchpad.net |
Commit message
add data-server dns entry as new metadata server detection
Description of the change
This Merge Requests adds a new preferred way to detect the metadata server address in CloudStack.
CloudStack has in it's Virtual Routers a DNS Server with a DNS entry that directs to the metadata server called 'data-server'. Only the Virtual Router which has a metadata server available will have this record. Therefore it should be the first method to try. If this one fails it goes next to detection via DHCP lease, and then falls back to the default gateway.
To post a comment you must log in.
test would be nice.