----- Laszlo Hornyak <lhornyak(a)redhat.com> 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?
If we will persist it then we can
warn for duplicated, but looks like cloud init is mainly used for one time initialization,
so in that case we won't persist it, thus we won't have this information in the
- 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
Can you elaborate on that? What would be hard on developers?
- 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
We might store those in the engine, allowing users to select one they have permissions on.
Not sure we would do it in the first phase, though.
- the hostname set for the guest could default to the VM name?
That can indeed be nice.
----- 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