<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DISCUSS][PROPOSAL] Support for standard metadata/userdata URL
Would it not work to assign the address 169.254.169.254 on the VR?
Erik
Den torsdag 6. august 2015 skrev Chiradeep Vittal <
chiradeep
>"
mailto:dev@cloudstack.apache.org>>
Date: Thursday, August 6, 2015 at 9:17 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DISCUSS][PROPOSAL] Support for standard metadata/userdata URL
BTW
Would it not work to assign the address 169.254.169.254 on the VR?
Erik
Den torsdag 6. august 2015 skrev Chiradeep Vittal <
chiradeep.vit...@citrix.com> følgende:
> Today the metadata / userdata server is retrieved by the guest from
> http:///latest/meta-data and
> http:// of DHCP server>/latest
BTW you can speed up cloud-init to look for CloudStack first/only by
overriding the datasource_list. The way I do it is by adding a file in my
templates to the /etc/cloud/cloud.cfg.d directory with only CloudStack in
it:
echo "datasource_list: [ CloudStack ]" >
etc/cloud/cloud.cfg.d/90_datasource
Today the metadata / userdata server is retrieved by the guest from
http:///latest/meta-data and
http:// of DHCP server>/latest/user-data
This of course has been inspired by the EC2 standard[1]
http://169.254.169.254/latest/
While this works and has been incorporated into cloud-init [2], there ar