<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Dear All,<br><br>I made available a service that implements the EC2 metadata protocol. For more information, please see:<br><br><a href="http://docs.aws.amazon.com/AWSEC2/2008-08-08/DeveloperGuide/AESDG-chapter-instancedata.html" target="_blank">http://docs.aws.amazon.com/AWSEC2/2008-08-08/DeveloperGuide/AESDG-chapter-instancedata.html</a><br><br>The main benefit is that you can get instance meta-data from inside the machine, most notably the user-data and public keys.<br>And because it is compatible with EC2, you can use cloud-init or other tools without any modification(*).<br><br>https://help.ubuntu.com/community/CloudInit<br><br>You can find the code and instructions on the following link:<br><br><font style="font-size: 12pt;" face="Calibri" size="3"><span style="font-size:12pt"><span dir="ltr"><a href="https://bitbucket.org/ricardoduarte/opennebula-metadata" target="_blank">https://bitbucket.org/ricardoduarte/opennebula-metadata</a></span></span></font><br><br>The code reuses the /var/lib/one/.one/ec2_auth credentials.<br><br>Please let me know if you find any bug.<br>I plan to write a small guide with examples on how to use it with cloud-init.<br><br>Regards,<br>Ricardo<br><br>(*) while cloud-init itself does not need any modification, you have to make sure the instance has a valid IP before cloud-init runs, either by having DHCP or by running the context scripts before cloud-init.<br>One simple way to ensure that, with Ubuntu, is to add the following to /etc/init/one-context.conf<br><br># /etc/init/one-context.conf - opennebula context script<br># contextualizes instance<br><br>start on starting cloud-init-nonet<br><br>task<br><br>exec /etc/init.d/vmcontext<br><br> </div></body>
</html>