On 13 Jun 2014, at 15:17, Koen Vanoppen wrote:
> > The cloud-init integration was a little flaky when I was using it,
>
> > when it was introduced in 3.3 - definitely
> ...
>
> Indeed. We are now using 3.4 and in works much better. And indeed the root
> password option also works now! :-)
> An
> The cloud-init integration was a little flaky when I was using it,
> when it was introduced in 3.3 - definitely
...
Indeed. We are now using 3.4 and in works much better. And indeed the root
password option also works now! :-)
And we can add a domain IF we type domain after every VM that has to
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
The cloud-init integration was a little flaky when I was using it,
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.
Just passing a full cloud-init config into the bot
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 s
5 matches
Mail list logo
