=== cpaelzer is now known as cpaelzer_afk
=== tmclaugh[work]_ is now known as tmclaugh[work]
=== smatzek_ is now known as smatzek
[17:46] <smatzek> smoser:  If bzr is going to be locked down soon, I'm wondering if we can get a small doc fix done under https://bugs.launchpad.net/cloud-init/+bug/1531582 to save people time and confusion.
=== cpaelzer_afk is now known as cpaelzer
[20:42] <harlowja> smoser ping
[20:42] <harlowja> press red-button to close off bzr
[20:42] <harlowja> please sign here
[20:42] <harlowja> _______
[20:42] <harlowja> (or else)
[20:42] <harlowja> lol
[22:03] <jeffawang> hey guys, is the order of execution deterministic for multipart configurations? Let me know if this isn't the right place to ask
[22:09] <harlowja> jeffawang unsure, do u mean order of reading (configurations don't really execute)
[22:14] <jeffawang> @harlowja: After all the configurations are merged, how is the order of execution determined? I have some scripts and some cloud-configs (with packages, yum_repos, and runcmd), and I'd like to make sure these are run in the right order, such that it goes repos -> packages -> runcmd -> scripts
[22:15] <harlowja> so that's typically defined by the order of the modules keys in said config
[22:15] <harlowja> ie https://github.com/openstack/cloud-init/blob/0.7.x/config/cloud.cfg#L25 (the order of init modules)
[22:16] <jeffawang> ahh, perfect. thanks for the prompt and useful reply @harlowja :)
[22:16] <harlowja> np