Created by Joshua Harlow on 2012-08-26 and last modified on 2012-08-31
Get this branch:
bzr branch lp:~harlowja/cloud-init/launch-index-work
Only Joshua Harlow can upload to this branch. If you are Joshua Harlow please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Joshua Harlow

Recent revisions

642. By Joshua Harlow on 2012-08-31

Update with the number of items discarded (useful for testing).

641. By Joshua Harlow on 2012-08-29

Don't use walk and handle the walking ourselves to
ensure that we recreate all child messages correctly
if they also contain submessages, ensuring that
we don't flatten the message list when we previously
used walk.

640. By Joshua Harlow on 2012-08-28

For the userdata 'post-filtering' add in a new folder that
can contain filters that serve this purpose only and add in
the initial launch-index filter and replace the code in
the datasource class that previously did this.

639. By Joshua Harlow on 2012-08-27

Update so that the content types searched for launch-index
variable has a little more meaning and by default look in
metadata for 'launch-index' and have ec2 instead look for
a different variable (thus allowing more datasources to just work).

638. By Joshua Harlow on 2012-08-27

Ensure when an archive is exploded and if it contains the
'launch-index' key that we copy that key over to the right
header (which will then be used later when assigning the
'real' header when the message is attached)

637. By Joshua Harlow on 2012-08-27

Fix tests running and add in a check on the content type
before we look into the payload as well as make the skip
test a function that the datasource module can also use.

636. By Joshua Harlow on 2012-08-26

Don't use the processed userdata if nothing is there.

635. By Joshua Harlow on 2012-08-26

Add the capability to understand and filter on
userdata based on a launch-index (or leave userdata
alone if none is provided by the datasource). This
works by doing the following.

1. Adjusting the userdata processor to attempt to
   inject a "Launch-Index" header into the messages
   headers (by either taking a header that already exists
   or by looking into the payload to see if it exists
2. Adjust the get_userdata ds function to apply a filter
   on the returned userdata (defaulting to false) that
   will now use the datasources get_launch_index value
   to restrict the 'final' message used in consuming
   user data (the same behavior if not existent).
3. Further down the line processes that use the 'resultant'
   userdata now will only see the ones for there own launch
   index (ie cloud-config will be restricted automatically
   and so on) and are unaffected (although they can now
   ask the cloud object or the datasource for its launch index
   via the above new ds method.

634. By Scott Moser on 2012-08-24

add support for the config-drive-v2 datasource

config-drive-v2 was implemented in openstack at
https://review.openstack.org/#/c/11184/ . This adds support to
cloud-init for reading that.

633. By Scott Moser on 2012-08-23

add support for creating initial users and groups

Added "userless" mode to cloud-init for handling the creation of the users
and the default user on Ubuntu. The end goal of this is to remove the need
for the 'ubuntu' user in the cloud images and to allow individuals to
choose the default user name.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.