/srv/irclogs.ubuntu.com/2014/08/15/#cloud-init.txt

=== harlowja is now known as harlowja_away
harmwsmoser: when may we expect a new version of ci to be released? i've got some important fixes in https://code.launchpad.net/~harmw/cloud-init/freebsd that I'd like in before I go for it and upload a real port to the freebsd ports system11:54
smoserharmw, i dont have a strong plan for a release, but we can get your code merged in.15:05
harmwok, well, I'd like a version bump in some form to allow me to build with the merged code :)15:06
harmwbtw, i've submitted the dependencies that aren't currently in freebsd ports earlier today15:07
harmw2 packages, but still15:07
=== praneshp_ is now known as praneshp
=== harlowja_away is now known as harlowja
harmwsmoser: https://code.launchpad.net/~harmw/cloud-init/freebsd/+merge/23102420:32
harmwharlowja: those fbsd initscripts from sean were a bit wacky I'm afraid :p20:33
smoserharmw, thanks for being awesome.20:34
harlowjayo yo20:34
harlowjaharmw haha20:35
harlowjaharmw u getting it up into freebsd repos i see, woot20:35
harmwharlowja: yes, I already did the jsonpatch and jsonpointer ports. Someone from the fbsd project needs to commit them, after that they're live20:36
harlowjacool20:36
harmwI'm now working on the cloud-init port, but that a little more complicated20:37
harmwthough thats because of all these new packaging tools I need to learn :p20:37
harlowja:)20:39
harmwbtw, if either one of you knows someone on the neutron crew20:40
harmwhave them work out https://review.openstack.org/#/c/77471/ :p20:40
harmwit's abandoned20:40
harmwwhich is sad20:41
harlowjamark killed it, haha20:41
harlowjai can bug mark about it i guess (he's on my team)20:41
harmwhehe20:41
harmwI think it's Randy (who created the code) who needs to fix something now though, but still :p20:42
harlowjaya, if person doesn't fix the code, not sure what i can do :-P20:44
harlowja*or keep pushing the review discussion/fixes...20:44
devicenullIs there a list somewhere of what metadata cloud-init relies on from the ec2 metadata source?21:06
harlowjadevicenull unsure what that means ;)21:09
devicenullright, that kinda incomprehensible21:09
harlowjathe metadata api is pretty generic that ec2 can expose, cloudinit will just extract all the resources on demand21:10
harlowjahttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/ec2_utils.py#L40 is the code that does this21:10
devicenullso, what I'm looking for is a list of what metadata cloud-init relies on to actually do things.  I'm writing an implementation of the ec2 metadata service for our software21:10
harlowjabut the initial fetch from ec2 defines what subsequent keys are fetched...21:10
harlowjaso i'd say the key items that it uses are block-device-mapping21:11
harlowjassh-keys21:11
harlowjaand userdata (of course)21:11
harlowjahttp://docs.aws.amazon.com/AWSEC2/2008-05-05/DeveloperGuide/index.html?AESDG-chapter-instancedata.html21:11
harlowjaavailability-zone also (although this is less used)21:12
harlowjaand the hostname ones21:12
devicenullokay, thanks!21:12
harlowja'ami-launch-index' will be used, although its optional21:12
harlowjaand of course instance-id21:12
devicenullI'm thinking the safest way to go is to provide as many of the values as possible21:12
devicenulland that are relevant to us21:12
harlowjayup21:13
harlowjathose i would call the main key ones21:13
harlowjassh-keys can be empty21:13
harlowjai'd make sure yours provides, userdata, instance-id, block-device ones and ssh-keys (although u can return ssh-keys as empty)21:14
devicenullok21:14
harlowjaand the hostname ones although cloud-init will skip those if its not there21:14
harlowjaand try to find the hostname by other mechanisms21:14
harlowjahttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/__init__.py#L45 is the basic datasource21:14
harlowjathat modules and all that get access to21:14
harlowjamethods there expose some of the above21:14
devicenullah, ok that's handy21:15
harlowjahttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/__init__.py#L164 (for example has the hostname logic)21:15
harlowjahttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/tools/mock-meta.py might be useful for u too21:16
harlowjahttp://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/tools/mock-meta.py#L192 (probably this function most useful)21:16
devicenullahha21:33
devicenullyea that last one is very useful21:33
devicenullso the network/* paths aren't used?21:37
devicenullbtw is there an actual better debug option?  even with --debug, I don't actually get any info on what cloud-init is doing21:54
devicenulljust some internal debug21:54
harlowjadevicenull network/* paths?22:02
devicenullnetwork/interfaces/macs/mac/device-number22:24
devicenullfrom http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html22:24
harlowjahmmm devicenull that seems newer than what cloudinit knows about22:33
harlowjaat least i didn't know that existed22:34
harlowjadevicenull anyway, cloud-init will read that, but it doesn't appear used yet afaik22:34
harlowjadevicenull as for debug, u should be able to get debug logs in /var/log/cloud-init.log22:35
harlowjacan also adjust the logging levels to do this to22:35
harlowjawhen starting an instance22:35
harlowjadepending on what cloud-init version u have this is easier/harder22:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!