=== zz_natorious is now known as natorious === natorious is now known as zz_natorious === minfrin_ is now known as minfrin === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious === natorious is now known as zz_natorious === openstackgerrit_ is now known as openstackgerrit === openstackgerrit_ is now known as openstackgerrit [12:35] joy https://github.com/testing-cabal/mock/issues/259 [12:35] curent tox doesn't support 2.6 [12:35] er... mock. not tox [12:48] Daniel Watkins proposed stackforge/cloud-init: Pin mock at 1.0.1. https://review.openstack.org/209036 [12:50] smoser: ^ fixes that. [12:51] yeah, but that kinda sucks [12:51] True. [12:51] i'm not sure but iknow that some recent version of mock actually had a bunch of fixes [12:52] that broken lots of bad tests. === alexpilotti_ is now known as alexpilotti [12:53] https://github.com/testing-cabal/mock/commit/a6367a9a2b6166d7d032ec91288294ec47177649 [12:53] Looks like it might be re-supported, actually. [12:53] nice [12:59] Scott Moser proposed stackforge/cloud-init: add ReportingEventStack https://review.openstack.org/209045 [12:59] Odd_Bloke, your thoughts on that are appreciated. [13:29] h gyus [13:29] hi guys [13:30] smoser: Looking at it now. [13:30] arnaud_orange1: o/ [13:30] until ubuntu 14.04 I was using a metadata file like this one: [13:30] http://paste.ubuntu.com/12000034/ [13:31] but with ubuntu cloud image 15.04 it does not work anymore [13:31] the /etc/network/interfaces file is well configured [13:31] but the network is not going up [13:32] for info, i am providing the meta-data and user-data in a /dev/vdb drive [13:32] is there any new way to configure network with datasourcenocloud on ubuntu 15.04? [14:32] 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] doesntunderstand: no, not really. [14:36] 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] 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] 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] so meta-data can only be assigned from the datasource interface? [14:38] let's change the conversation, what are you trying to do, what problem are you trying to solve? [14:43] I'm just trying to understand how all the pieces work together. I'm not currently trying to solve any problem. [14:45] cloud-init reads some things (such as hostname) from meta-data [14:45] but the user can override those values in user-data. [14:46] 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] Ah, thanks for clearing that up for me === rangerpbzzzz is now known as rangerpb [15:57] is there any way to reboot a cloud VM and réinitialise the cloud-config to simulate a first boot? === zz_natorious is now known as natorious === natorious is now known as zz_natorious [16:50] 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] 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] smatzek: ok tahnks [17:05] arnaud_orange1, rm -Rf /var/lib/cloud && sudo reboot [17:06] will do pretty much what you want [17:12] Is the default frequency for modules once-per instance? [17:13] i think so doesntunderstand , from what i remember [17:16] Alright, that makes sense with what I've been seeing [17:31] ya, unless overriden by the module, once-per-instance === rangerpb is now known as rangerpbzzzz === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious [22:59] 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] http://paste.openstack.org/show/407229/ [23:00] 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] not in the cloud-init version i know of