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

1 files changed, 2 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index 0ec4f49e..b08665b0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -92,6 +92,8 @@
  - doc: mention label for nocloud datasource must be 'cidata' [Peter Hurley]
  - ssh_pwauth: fix module to support 'unchanged' and match behavior
    described in documentation [Chris Cosby]
+ - quickly check to see if the previous instance id is still valid to
+   avoid dependency on network metadata service on every boot (LP: #1553815)
 
 0.7.6:
  - open 0.7.6