[01:20] <smoser> harlowja_at_home, around ?
[01:20] <smoser> http://paste.ubuntu.com/15248500/
[01:48] <smoser> gudge
[01:48] <smoser> fudge
[05:10] <harlowja_at_home> extra fudge please
[05:10] <harlowja_at_home> markerlib
[05:10] <harlowja_at_home> wtf is that
[05:10] <harlowja_at_home> ha
[05:19] <smoser> harlowja_at_home, its fixed. python-virtualenv upgrade fixed it
[05:19] <smoser> it came in a couple hours before i lost a couple hours
[05:51] <harlowja_at_home> u lost a couple of hours in space
[05:51] <harlowja_at_home> lol
[16:20] <esierrap> hi
[16:21] <esierrap> why my script in /var/lib/cloud/scripts/per-once doesnt run at first boot?
[16:21] <esierrap> i have the module in /etc/cloud/cloud.cfg
[16:30] <smatzek> esierrap.  per-once runs once ever.  It won't run on first boots if you snapshot/boot snapshot.
[16:30] <smatzek> you might want per-instance instead
[16:33] <smoser> thanks smatzek
[19:12] <smoser> rharper, thoughts ?
[19:12] <smoser> https://code.launchpad.net/~smoser/cloud-init/trunk.disable-clouddinit/+merge/287580
[19:12] <smoser> the thing i'm not sure of is if i like the single 'touch /etc/cloud/cloud-init.disabled'
[19:12] <smoser> rather than
[19:13] <smoser> echo "disabled" > /etc/cloud/cloud-init.somethinghere
[19:13] <smoser> simplicity is nice, but the 'disabled' string as configuration option means that i could also have
[19:13] <smoser>  'no-modify-net'
[19:13] <smoser> or something to that effect
[19:15] <smoser> but then that quickly goes into the realm of cloud.cfg
[19:32] <rharper> smoser: we can certainly do the latter overtime;  unless you have more than a few in mind I'd prefer the simpler one;  one simple switch
[19:38] <smoser> rharper, well, the reason for the string.
[19:39] <smoser> is that i can then have the contents of that file have the same as cloud-init=<value> on the command line.
[19:39] <smoser> and then on that command line, i can say something liike: cloud-init=no-dynamic-net
[19:42] <rharper> we can do both, right ?
[19:43] <smoser> i think it just gets confusing then.
[19:43] <smoser> you can do this or that or the other thing.
[19:43] <smoser> pick the right one
[19:51] <rharper> assuming the presence of the disabled file would negate the other options entirely; the file is like a big simple switch
[19:54] <smoser> right. but it sa boolean.
[19:54] <smoser> and i have  already a desire for a 3 way switch.
[19:54] <smoser> on, off, static-networking
[19:55] <rharper> sure; I'm saying we can do both; I don't think it's confusing;  one big on/off, and if it's on; then you can also do other stuff;
[19:55] <rharper> or delay the use of the content control
[19:55] <rharper> if I see disabled file, then we don't run;  that's a patch and will keep working;  we can introduce the content switch (on,off,no-net) at a later time
[19:56] <rharper> and it still works with our without the .disabled switch
[19:58] <rharper> smoser: I;m find with the n-way switch; if we want to introduce the big off hammer later, we can also do that as well
[19:58] <rharper> or not at all