[12:35] <smoser> joy https://github.com/testing-cabal/mock/issues/259
[12:35] <smoser> curent tox doesn't support 2.6
[12:35] <smoser> er... mock. not tox
[12:48] <openstackgerrit> Daniel Watkins proposed stackforge/cloud-init: Pin mock at 1.0.1.  https://review.openstack.org/209036
[12:50] <Odd_Bloke> smoser: ^ fixes that.
[12:51] <smoser> yeah, but that kinda sucks
[12:51] <Odd_Bloke> True.
[12:51] <smoser> i'm not sure but iknow that some recent version of mock actually had a bunch of fixes
[12:52] <smoser> that broken lots of bad tests.
[12:53] <Odd_Bloke> https://github.com/testing-cabal/mock/commit/a6367a9a2b6166d7d032ec91288294ec47177649
[12:53] <Odd_Bloke> Looks like it might be re-supported, actually.
[12:53] <smoser> nice
[12:59] <openstackgerrit> Scott Moser proposed stackforge/cloud-init: add ReportingEventStack  https://review.openstack.org/209045
[12:59] <smoser> Odd_Bloke, your thoughts on that are appreciated.
[13:29] <arnaud_orange1> h gyus
[13:29] <arnaud_orange1> hi guys
[13:30] <Odd_Bloke> smoser: Looking at it now.
[13:30] <Odd_Bloke> arnaud_orange1: o/
[13:30] <arnaud_orange1> until ubuntu 14.04 I was using a metadata file like this one:
[13:30] <arnaud_orange1> http://paste.ubuntu.com/12000034/
[13:31] <arnaud_orange1> but with ubuntu cloud image 15.04 it does not work anymore
[13:31] <arnaud_orange1> the /etc/network/interfaces file is well configured
[13:31] <arnaud_orange1> but the network is not going up
[13:32] <arnaud_orange1> for info, i am providing the meta-data and user-data in a /dev/vdb drive
[13:32] <arnaud_orange1> is there any new way to configure network with datasourcenocloud on ubuntu 15.04?
[14:32] <doesntunderstand> I'm looking for some clarification. Although user-data and meta-data are different, meta-data can be assigned through user-data correct?
[14:35] <smatzek> doesntunderstand: no, not really.
[14:36] <smatzek> this is what userdata can have:  http://cloudinit.readthedocs.org/en/latest/topics/format.html and as mentioned yesterday, it can provide input to the various modules at the 3 stages.
[14:37] <smatzek> metadata, at least from Openstack provides these items:  system hostname, VM UUID, SSH public named key injection if you're passing a key name on the OpenStack create server request, and a pointer to the network configuration.
[14:37] <smatzek> the pointer to the network configuration may only be there if you're using config drive, I'm not 100% sure on that.
[14:38] <doesntunderstand> so meta-data can only be assigned from the datasource interface?
[14:38] <smatzek> let's change the conversation, what are you trying to do, what problem are you trying to solve?
[14:43] <doesntunderstand> I'm just trying to understand how all the pieces work together. I'm not currently trying to solve any problem.
[14:45] <smoser> cloud-init reads some things (such as hostname) from meta-data
[14:45] <smoser> but the user can override those values in user-data.
[14:46] <smoser> it would e a nice featureto allow user data to specifically patch over any meta-data generically. but that doesn't happen now.
[14:47] <doesntunderstand> Ah, thanks for clearing that up for me
[15:57] <arnaud_orange1> is there any way to reboot a cloud VM and réinitialise the cloud-config to simulate a first boot?
[16:50] <smatzek> arnaud_orange1: depends what you want to do.  You can simulate a first boot or if you're interested in re-running a particular stage you can do different steps.  To simulate a first-boot do:  "Modify the instance ID found in /var/lib/cloud/data/instance-id and then rename the corresponding directory in /var/lib/cloud/instances/ to the new instance ID, then reboot the VM to have cloud-init re-execute your module."
[16:51] <smatzek> or you could just delete the instances directory and the instance-id file and reboot, depends if you want to keep the old instances directory around for some reason
[16:51] <arnaud_orange1> smatzek: ok tahnks
[17:05] <smoser> arnaud_orange1, rm -Rf /var/lib/cloud && sudo reboot
[17:06] <smoser> will do pretty much what you want
[17:12] <doesntunderstand> Is the default frequency for modules once-per instance?
[17:13] <harlowja> i think so doesntunderstand , from what i remember
[17:16] <doesntunderstand> Alright, that makes sense with what I've been seeing
[17:31] <harlowja> ya, unless overriden by the module, once-per-instance
[22:59] <clouduser_> Hi All. I'm trying to provide static ip configuration in cloud-config as shown in below but it doesn't work. can anyone help.
[22:59] <clouduser_> http://paste.openstack.org/show/407229/
[23:00] <clouduser_> I also tried with to bring down the interfaces and restart using "bootcmd"
[23:10]  * harlowja didn't think anyone processed 'network-interfaces' yaml sections
[23:10] <harlowja> not in the cloud-init version i know of