[22:12] <mfisch> smoser: would it be possible to pass-in a TENANT_ID (with some changes to cloud-init)?
[22:13] <harlowja> mfisch what type of cloud are u using, if the cloud doesn't provide the tenant-id in a accessible way to cloud-init, then makes it impossible for cloud-init to know about it
[22:14] <mfisch> openstack nova
[22:14] <mfisch> and I'm not sure it is being provided
[22:14] <mfisch> if it is, I'd like to help enable it, it will let me do some better tagging with landscape
[22:14] <harlowja> i don't think it is :-/
[22:14] <mfisch> I was hoping I could do tagging in landscape by tenant
[22:15] <mfisch> makes it easier for me to separate stuff
[22:15] <harlowja> agreed
[22:15] <mfisch> well if not, I'll just work on getting landscpae registration functional at all
[22:15] <mfisch> right now it's choking
[22:15] <harlowja> i know i've made a patch that does provide it, but i haven't upstreamed it yet 
[22:15] <mfisch> harlowja: I found smoser's sample config, you're saying that wont work?
[22:16] <harlowja> mfisch so that would probably be via user-data, which would work
[22:16] <harlowja> the other nicer way is to just have openstack write it (since it obviously knows the userid/tenantid)
[22:17] <harlowja> mfisch http://paste.openstack.org/show/63128/
[22:17] <harlowja> its nothing complicated
[22:17] <harlowja> i should just upstream that sometime
[22:18] <harlowja> then it shows up in metadata (accessible then via everywhere in cloud-init)
[22:19] <harlowja> maybe someone has already even upstreamed that, i haven't checked
[22:19] <mfisch> looking now
[22:19] <mfisch> thats easier to fix than cloud-init in 12.04 actually
[22:19] <harlowja> yup
[22:19] <harlowja> cloud-init already reads the metadata and exposes it as a dict, these are just 2 new keys
[22:20] <harlowja> *and harmless keys (so i wouldn't expect anyone to complain about it upstream)
[22:20] <mfisch> is instance_id passed in there
[22:20] <mfisch> probably this guy
[22:20] <mfisch> instance_metadata.InstanceMetadata(instance,
[22:20] <harlowja> ya, thats there
[22:20] <harlowja> metadata has 'instance-id' key afaik
[22:20] <harlowja> or uuid
[22:20] <harlowja> one of those 
[22:20] <mfisch> makes sense
[22:21] <mfisch> you push it up, I'll +1 it 
[22:21] <harlowja> :)
[22:21] <harlowja> k, let me see
[22:21] <mfisch> I have a good use case for it
[22:22] <mfisch> harlowja: if you do it, ping me
[22:22] <harlowja> k
[22:22] <mfisch> now back to getting base landscape working
[22:22] <harlowja> in progress, sh9ouldn't be long
[22:22] <harlowja> just gotta figure out where that code moved to, lol
[22:22] <mfisch> line 2512
[22:23] <mfisch> one more dumb question, it looks like the INSTANCE_ID is lost for "runcmd", its only there for bootcmd
[22:23] <harlowja> hmm
[22:23] <mfisch> so I guess I'll dump it to a file there and pull it back out?
[22:23] <harlowja> mfisch are u using config-drive or ec2 datasource in cloudinit?
[22:23] <harlowja> that will actually change what metadata is avail afaik
[22:23] <mfisch> so this is a dumb answer but I don't know
[22:23] <harlowja> k
[22:23] <mfisch> just starting playing with this a few hours ago
[22:24] <mfisch> I believe the logs say ec2
[22:24] <harlowja> ah, then this patch might not help 
[22:24] <mfisch> found data source: DataSourceEc2
[22:24] <mfisch> what decides the datasource?
[22:24] <mfisch> this is on a RHEL system, not what I'm deploying on
[22:24] <harlowja> cloud-init, but openstack has a config which actually decides it
[22:24] <mfisch> if that matters
[22:24] <mfisch> oh I can hack that
[22:24] <harlowja> cloud-init will serach for one
[22:25] <harlowja> let me check, the code paths are 2 different paths for the different pieces in openstack
[22:26] <harlowja> ya, let me see, i think it might work
[22:26] <med_> hey smoser.
[22:26]  * med_ was asked to join
[22:27] <mfisch> med_: I'm talking with harlowja actually
[22:27]  * med_ sees harlowja but no utlemming
[22:27] <med_> xlnt
[22:27] <mfisch> med_: our poc is using ec2 datasource, what implications will that have for something like the landscape config working?
[22:28] <med_> Hmmm. I think I've mentioned this at one point or another, I don't know jack about landscape.
[22:28] <med_> lame excuse but haven't had time to dig into it.
[22:28] <med_> Not sure why it would matter for cloud-init-y stuff.
[22:28] <mfisch> we're also discussing the other question of how to add a TENANT_ID into the data passed from nova, harlowja has a patch for nova
[22:30] <med_> cool beans
[22:44] <harlowja> mfisch  https://review.openstack.org/72018
[22:45] <harlowja> feel free to add comment with your use-case, incase the nova reviewrs say this is dumb
[22:45] <harlowja> it does appear that without altering the ec2 format though i can't add this change into that part of the code :(
[22:45] <harlowja> so its either https://code.launchpad.net/~harlowja/cloud-init/ds-openstack needs to merge or u might have to switch to using the config-drive option
[22:45] <harlowja> http://docs.openstack.org/grizzly/openstack-compute/admin/content/config-drive.html
[22:46] <harlowja> lets see how much the nova people complain :-p
[22:48] <mfisch> harlowja: looking
[22:52] <mfisch> harlowja: and I assume that cloud-init can parse from the config-drive in lieu of ec2
[22:52] <harlowja> mfisch ya
[22:53] <harlowja> https://code.launchpad.net/~harlowja/cloud-init/ds-openstack  will use the more native openstack metadata endpoint
[22:53] <harlowja> *unifying that code in cloud-init (since its the same data exposed via the metadata rest endpoint and the config drive)
[22:53] <mfisch> that may not help us until 14.04 I'd imagine
[22:53] <harlowja> correct
[22:54] <harlowja> cfgdrive though does work
[22:54] <harlowja> and should be in most modernish versions of cloud-init
[22:54]  * harlowja not sure when ubuntu started shipping the version that had it
[22:54] <mfisch> I can look
[22:54] <harlowja> *canonical, not ubuntu
[22:54] <harlowja> that company, haha
[22:55] <mfisch> I suspect that I'll be happy to get partially there and then happier when 14.04 comes out
[22:55] <harlowja> sure
[22:56] <med_> config drive just works
[22:56] <mfisch> med_: is it default enabled on ubuntu?
[22:57] <med_> We've also got to to worry about cloudbase-init (for Win images)
[22:57] <med_> 'default enabled on ubuntu' ? For config drive? It's an openstack thing
[22:57] <med_> not sure what you mean by default enabled.
[22:57] <med_> or do you mean does cloud-init grok config drive? Yes, it does.
[22:58] <mfisch> force_config_drive=True
[22:58] <mfisch> looks like we have it enabled
[22:59] <harlowja> ah, cool
[22:59] <harlowja> u should be able to check inside a vm
[22:59] <harlowja> blkid 
[22:59] <harlowja> will tell u 
[22:59] <harlowja> something like 'LABEL="config-2" UUID="5B88-2F2F" TYPE="vfat" '
[22:59] <mfisch> right
[22:59] <mfisch> that system with it enabled is not fully working atm, I think I may have another one though
[23:00] <med_> config drive has been in precise since at least Feb 2012
[23:00] <harlowja> k
[23:00] <harlowja> ya, i forget when it appeared
[23:00] <harlowja> smoser might remember
[23:00] <med_> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/857378
[23:01] <med_> to make OVF work with cloud-init
[23:01] <harlowja> k, so should be fine i think