Re: [Engine-devel] Cloud-Init integration
Hey Greg I'm not saying not to use cloud-init I just wanted to point out that one downside to cloud-init it that it is a fairly heavy package with a fair number of dependancies. Just something to keep in mind if requiring it to be built into launching instance. Joe On Mar 29, 2013, at 3:14 AM, Laszlo Hornyak wrote: > Hi Greg, > > Cool feature :) Some questions: > - Maybe the IP (and probably the hostname) should be enforced to be unique on > the same network? Or at least warning if duplicates found? > - Let's say if the IP is set by cloud-init, then you may also have it in the > guest agent info if the guest agent is installed. This may make life a bit > more difficult for the developers who build on rest-api. Is there a nice > solution for this? > - for authorized keys, it would be a pain to copy-paste the public key each > time you install a guest. Could a default be stored let's say in the user's > data? > - the hostname set for the guest could default to the VM name? > > Thank you, > Laszlo > > - Original Message - >> From: "Greg Padgett" >> To: "engine-devel" >> Sent: Friday, March 29, 2013 12:35:23 AM >> Subject: [Engine-devel] Cloud-Init integration >> >> Hi Everyone, >> >> I'd like to propose a feature we've been doing some investigation >> into, >> which is to integrate cloud-init support into oVirt. >> >> Cloud-init is used to help provision new Linux systems by setting the >> hostname, ip, ssh keys, timezone, injecting files, and more. It's >> used by >> OpenStack (amongst others) now, and has a lot of features that may be >> helpful to our users. >> >> Details are still evolving, but for more info please see the wiki >> page: >> >> http://www.ovirt.org/Features/Cloud-Init_Integration >> >> All feedback is welcome! >> >> Thanks, >> Greg >> ___ >> Engine-devel mailing list >> Engine-devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> > ___ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] VM Payload feature
On Jan 22, 2012, at 3:09 AM, Oved Ourfalli wrote: > > > - Original Message - >> From: "Ayal Baron" >> To: "Oved Ourfalli" >> Cc: engine-devel@ovirt.org >> Sent: Thursday, January 19, 2012 4:05:08 PM >> Subject: Re: [Engine-devel] VM Payload feature >> >> >> >> - Original Message - >>> Hey all, >>> >>> Continuing the discussion about Aeolus instance data injection to a >>> VM >>> (http://lists.ovirt.org/pipermail/engine-devel/2012-January/000423.html) >>> we propose a new VM Payload feature. >>> >>> The following wiki page contains a description page of the feature. >>> http://www.ovirt.org/wiki/Features/VMPayload >>> >>> Please read and review. >>> There are several approaches there, and we wish to head your >>> opinions >>> and thoughts about them. >>> >>> Once we agree on an approach, we will start designing. >> >> Permanent payload availability requires determining where the payload >> is stored. >> Makes sense to me to store it together with the VM disks on the >> storage domain, but that requires the small object store which will >> not be available in the coming version (payloads can be large and >> keeping them in the DB and passing over the net every time the VM is >> run doesn't make much sense). >> > I guess we can start with storing it in the database, with some size > limitation, and move it to the storage domain later on. > >> Wrt availability, I don't see a reason to exclude attaching both a CD >> and a payload via another CD at the same time (i.e. multiple >> devices). >> >>> >>> Thank you, >>> Oved >>> ___ >>> Engine-devel mailing list >>> Engine-devel@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/engine-devel >>> >> ___ >> Engine-devel mailing list >> Engine-devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/engine-devel >> My perspective is that of the end user, the instance retrieving the data. From a functional standpoint I would like to see similar performance to what EC2 provides. AWS EC2 user data is limited to 16K. This limit applies to the data in raw form, not base64 encoded form. see: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html I am concerned about the 512k limit as mentioned in the notes of: http://www.ovirt.org/wiki/Features/VMPayload "if the content of the file is bigger the 512K it will pass an nfs share for vdsm to fetch the file/s" Please confirm: - Will it be possible to pass user data to larger than 512k? - If so what will the instance need to do in order to retrieve user-data bigger than 512k. - What will the MAX size supported for the user-data? Thank you. Joe VLcek ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
