=== cpaelzer_ is now known as cpaelzer [14:40] smoser: is anyone meeting today? [14:49] natorious, bah [14:49] i'm not really supposed to be working [14:49] Canonical gets national holidays off [14:50] right on. So, I've been thinking about the state of things. Perhaps getting moderator access would be helpful for progress on 2.0 [14:55] moderator access? natorious ? [14:59] so I can help contribute to others merge requests in gerrit. I have some other merge requests to push up still too. Did a bit of work around adding a subprocess check_output derivative and started on some network_config for linux [14:59] I'd also broke out some distro namespaces on a branch to get that going [15:02] I'm not sure their would be immediate gain but, at least I could add value to promoting dev help on the project [15:08] also did a bit of work getting windows to detect config drive partitions using ctypes from stdlib [15:09] all those more or less depend on the two merge requests that are already in so if there is something needed w/ them, do let me know [19:11] hi, if a cloud-config yaml has runcmd and packages, are packages installed before or after the commands? [19:12] I have packages: - git and runcmd: - git clone ... [19:13] I better switch to cloud-init bash script? [19:19] manuq: it depends on the order you have them defined in your /etc/cloud/cloud.cfg file [19:20] the default upstream config has package-update-upgrade-install running before runcmd [19:20] but, there is also bootcmd which runs before them as part of early boot [19:21] I'd think you'd get better results from using the cloud-init modules than just passing in a bash script content file [19:22] but if your not into leveraging all the other modules and only need to run simple commands, that might be a better option [19:23] natorious, that's an excellent answer, thanks [19:23] most of the distros should have the same upstream ordering but, its possible that the package creator could change it [19:23] np