cloudbase-init

cloudbase-init should prefer local datasources over remote datasources

Bug #1671491 reported by Alain Swanson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloudbase-init
Incomplete
Undecided
Unassigned

Bug Description

When cloudbaseinit.metadata.services.configdrive.ConfigDriveService is enabled, the presence of a config drive should be checked for (and if found, used) BEFORE other datasources (i.e. cloudbaseinit.metadata.services.httpservice.HttpService) are attempted. Remote datasources should not be attempted if a local datasource is found.

In order words, local datasources should always be preferred over remote datasources.

This is not the behavior as observed in cloud base-init-0.9.9.

Revision history for this message
Adrian Vladu (avladu) wrote :

Hello,

The http metadata sources are by default preferred over the local ones because they have more capabilities than the local ones (posting user passwords, communicating to the cloud middleware the instance status).

Currently, cloudbase-init supports only one metadata source per run, and in OpenStack scenarios, where you might have config-drive and http metadata available, the http metadata is preferred for the reasons mentioned above.

Of course, the metadata sources are configurable, and you can change them if needed. In your case, you need to set in the cloudbase-init configuration file, in the DEFAULT section:

    metadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveService,cloudbaseinit.metadata.services.httpservice.HttpService

Thank you,
Adrian Vladu

Adrian Vladu (avladu)
Changed in cloudbase-init:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.