[02:07] Odd_Bloke, i'd apprecate your reading https://code.launchpad.net/~sankaraditya/cloud-init/topic-stanguturi-vmware-support/+merge/288452 also [02:08] for stanguturi === Guest38484 is now known as mfisch === mfisch is now known as Guest13749 [10:13] hi! is it possible to define the address where cloud-init connects manually? [10:13] I have a problem in openstack, that it is trying to connect with http instead of https and because of that the conection fails.. [10:14] it tries to connect where? [10:14] (hint: it provides this information in the log) [10:15] well it tried to connect to http://169.254.169.254/2009-04-04/meta-data/instance-id instead it should connect to: https://169.254.169.254/2009-04-04/meta-data/instance-id [10:16] I'm just trying to undestand where the address is told in the configs? [10:19] why do you think so? the EC2 metadata service does not use https [10:20] I have an openstack and it is configured to use https for metadata service [10:20] We have our private cloud running, and there was some updates to it, and the metadata service stopped working.. [10:21] how did you configure that? [10:21] or not the metadata service stopped working.. the metadata service is answering on https but for some reason the cloud-init tries to connect http. [10:22] This is suse cloud 5, and suse has done the configs.. [10:22] I'm just trying to figure out how cloud-init works [10:22] basically if update comes to suse cloud, chef will automatically provision the updates to cloud nodes and controllers [10:23] look into the neutron metadata proxy config [10:23] and i see no knob to make serve https [10:24] It worked before, so somehow they managed to do it :) It breaked yesterday evening after the updates [10:24] I have a support request open, but I would like to know how it works, for just in case. [10:26] yes there is htts -option: nova_metadata_protocol = http(StrOpt) Protocol to access nova metadata, http or https [10:27] as neutron adds an explicit and unconfigurable redirect from 169.254.169.254:80 to the metadata proxy, i doubt that this was ever https [10:27] wrong side [10:27] this is the neutron metadata proxy (used for the EC2 endpoint) speaking to nova [10:27] yes it was, because I checked from the logs before.. Before cloud-init connected to https [10:28] i'm pretty sure it did not, as http://169.254.169.254 is hardcoded in cloud-init [10:29] maybe it is doing somekind of redirect to https, but in the instance logs I checked that it was https [10:30] well. so what is your problem now? that an alledged redirect got missing? [10:31] well the problem is that it does not work :) [10:31] cloud-init does not connect to metadata service correctly [10:32] then fix your metadata service [10:34] okay thanks.. But itäs good to know that address is hardcoded to cloud-init [14:02] skoude, the address is "well known" [14:02] but you can probably configure it, let me see. The thing you can't do to my knowledge is tell cloud-init where it is without modifying an image. [14:05] skoude, http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-datasources.txt [14:06] the openstack metadata service (datasource['OpenStack']) should have the same configuration options as the Ec2 datasource [14:07] and you could give it a list of urls in 'metadata_urls' [14:07] the default is [14:07] (DEF_MD_URL) is ["http://169.254.169.254"] === Guest13749 is now known as mfisch === mfisch is now known as Guest88074 === Guest88074 is now known as mfisch [21:11] rharper, magicalChicken around ? [21:11] here [21:11] wanted to share where i was with the cloud-inti networing [21:11] http://paste.ubuntu.com/15351009/ [21:12] so in that branch, i can basically seed that network config (line 10-23) [21:13] * jgrimm rides along [21:13] so in container the networking comes up fine [21:13] but https://github.com/lxc/lxd/issues/1747 [21:14] means that lxc's user-data / metadata get read instead of mine [21:14] but that woudl be work aroundable and i think woudl work if lxc wasnt fighting me [21:16] http://paste.ubuntu.com/15351044/ [21:16] that shows the results in it too. [21:16] stanguturi, ^ [21:16] nice [21:17] that is what i'm workign on to get networking configuration from a "local" data source into the instance. [21:18] harlowja_at_home, wonder if you made any progress on openstack networkign ? [21:22] rharper, if you could try to get that intergrated with what you have for testing, and send me a mail on how to go from there, i'd appreciate it. [21:22] i have to run for the night. [21:22] stanguturi, i pointed you at that because we'd like for vmware's data to get into instance that general way also,. [21:36] smoser: yeah [23:03] hi all [23:03] got confused completely, need some heads up [23:03] i have cloud-init with NoCloud datasource [23:04] iso image created, and VM is picking it up [23:04] from docs i found that if instance-id is changed then cloud-init will reload user-data [23:05] but nothing happens [23:55] nobody ?