<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 5 February 2014 16:13, Mark Gergely <span dir="ltr"><<a href="mailto:gergely.mark@sztaki.mta.hu" target="_blank">gergely.mark@sztaki.mta.hu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Dear All,</div><div>
<br></div><div>i suggest that there should be a configuration variable in the econe-server.conf file which influences this behavior. We really got used to the way it worked previously, that every image could be listed or started through the EC2 server regardless of the image upload method or tags.</div>
<div>i propose that if the describe_only_ec2_images variable is true, then it should work like in 4.4.1, if it is false, then it should list every image which is not a snapshot or an ebs volume.</div><div>Tell me what you think, if it looks fine for you, then i can prepare a patch.</div>
</div></blockquote><div><br></div><div>I have created a ticket to add this option in future releases:</div><div><a href="http://dev.opennebula.org/issues/2710">http://dev.opennebula.org/issues/2710</a></div><div><br></div>
<div>Thank you for your feedback </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><br></div><div>All the best,</div><div>Mark Gergely</div><div>MTA SZTAKI LPDS</div><div><div class="h5"><br><div><div>On 05 Feb 2014, at 15:08, Daniel Molina <<a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Hi <span style="font-family:Calibri,sans-serif;font-size:14px">Hyunwoo,</span><div class="gmail_extra"><br><br><div class="gmail_quote">On 5 February 2014 13:20, Hyun Woo Kim <span dir="ltr"><<a href="mailto:hyunwoo@fnal.gov" target="_blank">hyunwoo@fnal.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>Hi, </div>
<span>
<div>
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div><br>
</div>
<div>I have recently deployed ON 4.4 and have been testing EC2 (econe-) commands.</div>
<div><br>
</div>
<div>First I could do econe-upload successfully.</div>
<div>The new image can be seen with oneimage list command,</div>
<div>but econe-describe-images just shows an empty list.</div>
<div>(This command is working in our ON 3.2 EC2 system).</div>
<div><br>
</div>
<div>What has changed? Or am I missing a configuration step?</div></div></div></span></div></blockquote><div><br></div><div>In one 4.4, after using econe-upload or just to make an OpenNebula image available through econe, the econe-register is necessary. This command will include the EC2_AMI=YES tag in the template and then it will be listed in the describe-images command and you will be able to use it through the ec2 api.</div>
<div><br></div><div>More information on the one-4.4 changes can be found here:</div><div><a href="http://docs.opennebula.org/stable/release_notes44/compatibility.html#ec2-server" target="_blank">http://docs.opennebula.org/stable/release_notes44/compatibility.html#ec2-server</a><br>
</div><div><br></div><div>Cheers</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<span><div><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div><br>
</div>
<div>Thanks very much</div>
<div>Hyunwoo </div>
<div>FermiCloud Project</div>
<div><br>
</div>
</div>
</div>
</span>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>--<br></div>Daniel Molina<br>Project Engineer<br>OpenNebula - Flexible Enterprise Cloud Made Simple<br><a href="http://www.opennebula.org/" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula</div>
</div></div>
_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</blockquote></div><br></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>--<br></div>Daniel Molina<br>Project Engineer<br>OpenNebula - Flexible Enterprise Cloud Made Simple<br>
<a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:dmolina@opennebula.org" target="_blank">dmolina@opennebula.org</a> | @OpenNebula</div>
</div></div>