diff options
author | Scott Moser <smoser@ubuntu.com> | 2016-03-21 22:30:56 -0400 |
---|---|---|
committer | Scott Moser <smoser@ubuntu.com> | 2016-03-21 22:30:56 -0400 |
commit | 4f2065ad569355d5d0bc54176bde6b8e55047341 (patch) | |
tree | 0008ea8f19816c882f52dee82079776317982210 /tests | |
parent | 1b91b7cee6f2d4a2a7ddaf5f963225f0d36d1963 (diff) | |
parent | 8968f570787c0889f2c8b363e208e018903b63fa (diff) | |
download | vyos-cloud-init-4f2065ad569355d5d0bc54176bde6b8e55047341.tar.gz vyos-cloud-init-4f2065ad569355d5d0bc54176bde6b8e55047341.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
sources:
DataSourceAzure (check dmi data)
DataSourceConfigDrive (check dmi data)
DataSourceNocloud (check the seeded data or kernel command line)
DataSourceOpenstack (check dmi data)
LP: #1553815
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions