On 12 Jun 2014, at 05:11, Andrew Lau wrote:
The cloud-init integration was a little flaky when I was using it,
when it was introduced in 3.3 - definitely
I ended up not using any of the inbuilt oVirt options (eg. hostname,
root password). Root password never worked for me as it'd force a
reset on first login.. defeating the purpose.
yes. This has been fixed since (IIRC in 3.4, maybe a bit later, not sure)
I'm not aware of any further issues with cloud-init recently…it should be fine
there's always room for some enhancements…but pretty much you can add whatever is
missing in a custom config section (also for windows sysprep) today
Thanks,
michal
Just passing a full cloud-init config into the bottom section worked
for me, so for your case just define the hostname there instead.
On Tue, May 27, 2014 at 9:33 PM, Koen Vanoppen <vanoppen.koen(a)gmail.com> wrote:
> Hi Guys,
>
> It's bin a while :-). Luckily :-).
>
> I have a quick question. Is there a way to change the default .localdomain
> for the FQDN in ovirt?
> I would be handy if we just had to fill in the hostname of our vm (we are
> using 3.4, with the cloud-init feature) and he automatically adds our domain
> in stead of .localdomain.
>
> Kind regards,
>
> Koen
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users