[00:01] <copumpkin> okay, I'm seeing something super puzzling
[00:02] <copumpkin> when my cc_copumpkin_custom_crap runs at instance startup, cloud.datasource.metadata only contains a subset of the stuff it contains when I run it interactively later after boot
[00:02] <copumpkin> on the same machine
[00:03] <copumpkin> oh!
[00:04] <copumpkin> it's hardcoded to request an older version of the metadata :(
[00:05] <copumpkin> ARGH, it's the version right before the one that has the feature I want
[00:05] <copumpkin> 2011-01-01 introduced the network hierarchy, and cloud-init explicitly asks for 2009-04-04
[00:05] <copumpkin> smoser: is there an easy way to override DataSourceEc2's api_ver from my cloud-init config?
[13:07] <smoser> copumpkin, we can probably move to the nwere version...
[13:07] <copumpkin> yeah, they only ever seem to add to it
[13:08] <copumpkin> my really elegant solution right now is to patch cloud-init in place before I snap the image ;)
[13:08] <smoser> right. it should be just that one string, right ?
[13:08] <smoser> i'm not opposed to something that checks and is able to use a newer version
[13:08] <smoser> but if we bump the version we have to be able to fall back
[13:08] <copumpkin> yep! super simple sed
[13:08] <copumpkin> fall back how?
[13:09] <smoser> as other clouds impersonate ec2 and likely dont' have newer YYYY-MM-DD
[13:09] <copumpkin> oh, hmm
[13:09] <copumpkin> didn't know that
[13:09] <smoser> its very common to impersonate ec2
[13:09] <smoser> :)
[13:11] <copumpkin> aha
[13:11] <copumpkin> although if we just bump it up to the 2011 date
[13:11] <copumpkin> that's still pretty ancient
[13:11] <copumpkin> I wonder if there are impersonators who impersonate one particularly ancient version but not the one right afterwards
[13:11] <copumpkin> "we have a policy to only replicate APIs that are 6 or more years old, and yours is only 5 years old"
[13:11] <copumpkin> :P
[13:11] <smoser> copumpkin, yeah, what i think i'd do is read the old one, and if its present then go looking for new ones.
[13:12] <copumpkin> oh, that makes sense
[13:12] <smoser> and i'd just jump fro 2009 to whatever is most recent.
[13:12] <smoser> there is an index too
[13:12] <smoser> if you just get the metadata/ i think you get a list of versions
[13:13] <smoser> but since we never got that before we'd then be adding some new expectation, which probably does work.
[16:36] <harlowja> smoser u review my stuff yet, shall i merge it
[16:37] <harlowja> i will be around to fix shit if i broke it :-P
[16:37] <harlowja> (which of course it does not)
[16:37] <harlowja> (obviously)
[16:38] <smoser> harlowja, reading...
[16:38] <smoser> i will review today.
[19:29] <konetzed> Hay anyone know how to get cloud-init to set hostnames via reverse dns or will i need to write a custom module for that?
[20:00] <rtheis> How do I request a revert of https://github.com/openvswitch/ovs/commit/b00bdc728e7a0ae697b4fc59a4f9958b688c6789 ?  networking-ovn gate is failing because ovs-bugtool.in fails flake8
[20:01] <rtheis> sorry wrong channel