<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 22, 2012, at 3:09 AM, Oved Ourfalli wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><br>----- Original Message -----<br><blockquote type="cite">From: "Ayal Baron" <<a href="mailto:abaron@redhat.com">abaron@redhat.com</a>><br></blockquote><blockquote type="cite">To: "Oved Ourfalli" <<a href="mailto:ovedo@redhat.com">ovedo@redhat.com</a>><br></blockquote><blockquote type="cite">Cc: <a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a><br></blockquote><blockquote type="cite">Sent: Thursday, January 19, 2012 4:05:08 PM<br></blockquote><blockquote type="cite">Subject: Re: [Engine-devel] VM Payload feature<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">----- Original Message -----<br></blockquote><blockquote type="cite"><blockquote type="cite">Hey all,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Continuing the discussion about Aeolus instance data injection to a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">VM<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">(<a href="http://lists.ovirt.org/pipermail/engine-devel/2012-January/000423.html">http://lists.ovirt.org/pipermail/engine-devel/2012-January/000423.html</a>)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">we propose a new VM Payload feature.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The following wiki page contains a description page of the feature.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.ovirt.org/wiki/Features/VMPayload">http://www.ovirt.org/wiki/Features/VMPayload</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Please read and review.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">There are several approaches there, and we wish to head your<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">opinions<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and thoughts about them.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Once we agree on an approach, we will start designing.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Permanent payload availability requires determining where the payload<br></blockquote><blockquote type="cite">is stored.<br></blockquote><blockquote type="cite">Makes sense to me to store it together with the VM disks on the<br></blockquote><blockquote type="cite">storage domain, but that requires the small object store which will<br></blockquote><blockquote type="cite">not be available in the coming version (payloads can be large and<br></blockquote><blockquote type="cite">keeping them in the DB and passing over the net every time the VM is<br></blockquote><blockquote type="cite">run doesn't make much sense).<br></blockquote><blockquote type="cite"><br></blockquote>I guess we can start with storing it in the database, with some size limitation, and move it to the storage domain later on.<br><br><blockquote type="cite">Wrt availability, I don't see a reason to exclude attaching both a CD<br></blockquote><blockquote type="cite">and a payload via another CD at the same time (i.e. multiple<br></blockquote><blockquote type="cite">devices).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Thank you,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Oved<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Engine-devel mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Engine-devel mailing list<br></blockquote><blockquote type="cite"><a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br></blockquote><blockquote type="cite"><a href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br></blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div><br><div><br></div><div><br></div><div>My perspective is that of the end user, the instance retrieving the data.</div><div><br></div><div>From a functional standpoint I would like to see similar performance to</div><div>what EC2 provides. AWS <span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; font-size: 12px; ">EC2 user data is limited to 16K. This limit</span></div><div><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; font-size: 12px; ">applies to the data </span><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; font-size: 12px; ">in raw form, not base64 encoded form.</span></div><div><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; font-size: 12px; ">see: </span></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif"><a href="http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html">http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html</a></font></div><div><br></div><div>I am concerned about the 512k limit as mentioned in the notes</div><div>of: <a href="http://www.ovirt.org/wiki/Features/VMPayload">http://www.ovirt.org/wiki/Features/VMPayload</a></div><div>"<span class="Apple-style-span" style="font-family: sans-serif; font-size: 13px; line-height: 19px; ">if the content of the file is bigger the 512K it will pass an nfs</span></div><div><span class="Apple-style-span" style="font-family: sans-serif; font-size: 13px; line-height: 19px; ">share for vdsm to fetch the file/s"</span></div><div><br></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif">Please confirm:</font></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif">- Will it be possible to pass user data to larger than 512k?</font></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif">- If so what will the instance need to do in order </font><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; ">to retrieve</span></div><div><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; "> user-data bigger than 512k.</span></div><div><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; ">- What will the MAX size supported for the user-data?</span></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif">Thank you.</font></div><div><font class="Apple-style-span" face="verdana, arial, sans-serif"> Joe VLcek</font></div><div><span class="Apple-style-span" style="font-family: verdana, arial, sans-serif; font-size: 12px; "><br></span></div></body></html>