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.
On Mar 29, 2013, at 3:14 AM, Laszlo Hornyak wrote:
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?
----- Original Message -----
> From: "Greg Padgett" <gpadgett(a)redhat.com>
> To: "engine-devel" <engine-devel(a)ovirt.org>
> 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
> 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
> All feedback is welcome!
> Engine-devel mailing list
Engine-devel mailing list