summaryrefslogtreecommitdiff
path: root/cloudinit/mergers
diff options
context:
space:
mode:
authorScott Moser <smoser@ubuntu.com>2016-03-21 21:47:24 -0400
committerScott Moser <smoser@ubuntu.com>2016-03-21 21:47:24 -0400
commit0964b42e5117cce640a8ba9102a76fa54a698898 (patch)
tree7dcd74e20a78d71a76ca4027c32677e3e586bc40 /cloudinit/mergers
parent1b91b7cee6f2d4a2a7ddaf5f963225f0d36d1963 (diff)
downloadvyos-cloud-init-0964b42e5117cce640a8ba9102a76fa54a698898.tar.gz
vyos-cloud-init-0964b42e5117cce640a8ba9102a76fa54a698898.zip
quickly check to see if the previous instance id is still valid
This adds a check in cloud-init to see if the existing (cached) datasource is still valid. It relies on support from the Datasource to implement 'check_instance_id'. That method should quickly determine (if possible) if the instance id found in the datasource is still valid. This means that we can still notice new instance ids without depending on a network datasource on every boot. I've also implemented check_instance_id for the superclass and for 3 classes: DataSourceAzure (check dmi data) DataSourceOpenstack (check dmi data) DataSourceNocloud (check the seeded data or kernel command line) LP: #1553815
Diffstat (limited to 'cloudinit/mergers')
0 files changed, 0 insertions, 0 deletions