[16:35]  * sputnik13 is confused
[16:35] <sputnik13> is cloud-init maintained in bzr or git?
[16:39] <smoser> 0.7 is in bzr, but harlowja wants to move it to git.
[16:39] <smoser> 2.0 is git
[16:46] <sputnik13> yay git :)
[16:46]  * sputnik13 is lazy and doesn't want to learn another tool if he can help it
[16:46] <sputnik13> :)
[16:47] <sputnik13> woot, taskflow in cloud-init?
[16:51] <smoser> thats proposed
[16:51] <sputnik13> taskflow all the things :)
[16:58] <sputnik13> hmm, no growpart in 2.0
[17:11] <harlowja> sputnik13 2.0 is a WIP :-P
[17:11] <harlowja> smoser is 0.7 in git yet :-P
[17:12] <smoser> sputnik13, no much in 2.0
[17:13] <harlowja> but sputnik13  u are gonna make 2.0 more super!
[17:13] <harlowja> i just know it
[17:19] <harlowja> i believe
[17:19] <harlowja> lol
[22:19] <harlowja> sputnik13 talking to a coworker internally, i heard that IPA may be doing/getting LVM support
[22:19] <harlowja> *ironic IPA
[22:20] <harlowja> although i guess u are thinking of LVM outside of ironic
[22:27] <sputnik13> ipa?
[22:27] <sputnik13> indian pale ale?
[22:27] <sputnik13> pale ales are not my thing
[22:30] <sputnik13> weird, I'm getting errors about unable to find resizer for 'growpart'
[22:30] <sputnik13> when specifying 'growpart' as the 'mode'
[22:30] <harlowja> lol
[22:30] <harlowja> https://wiki.openstack.org/wiki/Ironic-python-agent
[22:30] <harlowja> that thing i think
[22:31] <sputnik13> using cloud-init 0.7.6~bzr976 on debian
[22:31] <sputnik13> http://paste.openstack.org/show/473637/
[22:32] <sputnik13> ^ is in /etc/cloud/cloud.cfg.d/00_growpart
[22:33] <sputnik13> and getting this in cloud-init.log
[22:33] <sputnik13> http://paste.openstack.org/show/473638/
[22:43] <harlowja> sputnik13 i suppose https://github.com/stackforge/cloud-init/blob/0.7.x/cloudinit/config/cc_growpart.py#L49 ?
[22:45] <harlowja> i guess https://github.com/stackforge/cloud-init/blob/0.7.x/cloudinit/config/cc_growpart.py#L84 broken?
[22:45] <harlowja> sputnik13 ^
[22:45] <harlowja> seems to be searching for r"--update\s+"
[22:45] <harlowja> in the output of --help
[22:45] <harlowja> not sure why
[22:50] <sputnik13> that is most odd
[23:04] <sputnik13> smoser any clues?
[23:04] <sputnik13> re ^
[23:05] <sputnik13> harlowja smoser what do you think about extending growpart to handle resizing lvm logical volumes as well?
[23:05] <sputnik13> or should it actually be a separate module that handles lvm?
[23:06] <harlowja> unsure, either is fine with me, not sure what is better
[23:33] <sputnik13> well it definitely shouldn't be resizefs, that part I'm pretty sure of
[23:33] <sputnik13> :)
[23:33] <sputnik13> I kind of like having it as a separate thing so that conceptually you have growpart that deals with "physical" partitions
[23:33] <sputnik13> physical partitions in virtual disks, heh
[23:33] <sputnik13> :)
[23:34] <sputnik13> and some lvm handler thing that handles logical volumes
[23:34] <sputnik13> and resizefs is still concerned only with filesystems
[23:34] <sputnik13> keeps the three independent
[23:34] <harlowja> sounds super to me
[23:34] <harlowja> :-P
[23:35] <sputnik13> hah
[23:53] <sputnik13> ugh
[23:53]  * sputnik13 is confuzd
[23:53] <sputnik13> I swear it was loading my /etc/cloud/cloud.cfg.d/00_growpart before when growpart had no --upgrade in the help output
[23:54] <sputnik13> but now that growpart has --upgrade in the help output (I hacked it in) it's acting like 00_growpart isn't there
[23:58] <harlowja> :-/
[23:58] <harlowja> not running the module?