Difference: CloudMetaDataProblems (1 vs. 4)

Revision 42013-07-12 - mhp

Line: 1 to 1

META TOPICPARENT	name="CanarieProjectNEP52"

If clouds would follow this standard it would make it easier to contextualize images: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html

Line: 10 to 10

Also, it should be strongly recommended that each OpenStack cloud change the default .novalocal suffix to something site-specific. \ No newline at end of file

Added:

>
>

EC2 meta-data should return the hostname for private IPs, not the ip address in the hostname field. in nova.conf

ec2_private_dns_show_ip=false

Revision 32013-07-09 - rptaylor

Line: 1 to 1

META TOPICPARENT	name="CanarieProjectNEP52"

If clouds would follow this standard it would make it easier to contextualize images: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html

Line: 9 to 9

http://169.254.169.254/latest/meta-data/local-ipv4 contains the public IP

Deleted:

<
< Also, it would be preferable if each OpenStack cloud changed the default .novalocal suffix to something site-specific.

\ No newline at end of file

Added:

>
> Also, it should be strongly recommended that each OpenStack cloud change the default .novalocal suffix to something site-specific.

\ No newline at end of file

Revision 22013-07-09 - rptaylor

Line: 1 to 1

META TOPICPARENT	name="CanarieProjectNEP52"

Changed:

<
< If clouds would follow this standard it would make it easier to contextulize images:

>
> If clouds would follow this standard it would make it easier to contextualize images:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html

Line: 9 to 9

http://169.254.169.254/latest/meta-data/local-ipv4 contains the public IP

Added:

>
> Also, it would be preferable if each OpenStack cloud changed the default .novalocal suffix to something site-specific.

\ No newline at end of file

Revision 12013-07-09 - igable

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="CanarieProjectNEP52"

If clouds would follow this standard it would make it easier to contextulize images: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html

Common problem with finding the public IP of the machine:

http://169.254.169.254/latest/meta-data/public-ipv4 is empty although VMs have public IPs
http://169.254.169.254/latest/meta-data/local-ipv4 contains the public IP

View topic | History: r4 < r3 < r2 < r1 | More topic actions...