Hi there,
Upgrading 4.11.0 to 4.11.1 we found an interesting problem in our (well played)
staging infrastructure.
During SSVN provisioning, a somewhat "premium" configuration is detected (well
we're using noredist since ... ever?).
So the SSVM is configured with
That setting is part of a property file of
cloudstack-plugin-hypervisor-vmware.
Most likely you are using a system build with noredist.
In that case you also need a systemvm build that way.
Kind Regards,
Frank
On Tue, Jul 10, 2018 at 12:16 PM Stephan Seitz
wrote:
> Hi there,
>
> Upgrading
Thanks for your feedback! Do you know how to build the systemvmtemplate w/
noredist? I didn't find
anything regarding that in tools/appliance, also cwiki keeps quiet about that.
Thanks!
Stepnan
Am Dienstag, den 10.07.2018, 07:38 -0700 schrieb Frank Maximus:
> That setting is part of a property
You are right Rafael, I was not clear with the "*(KVM)*". The idea would be
to update others as well ;)
2018-07-10 16:34 GMT-03:00 Rafael Weingärtner :
> That looks a good idea, to at least, update the current default template
> that we ship in. However, we should update not only the KVM
That looks a good idea, to at least, update the current default template
that we ship in. However, we should update not only the KVM template, but
also XenServer and VMware, right?
Can we host image for these operating systems? The CentOS 5.5 images are
being hosted at
how about the macchinina images as build in? At least for development those
are very convenient.
On Tue, Jul 10, 2018 at 9:59 PM, Gabriel Beims Bräscher <
gabrasc...@gmail.com> wrote:
> You are right Rafael, I was not clear with the "*(KVM)*". The idea would be
> to update others as well ;)
>
>
Hello,
I would like to propose updating our current default VM template "CentOS
5.5(64-bit) no GUI (KVM)" to a newer version (e.g. CentOS 7). I also think
that we could benefit from a wider set of templates offering also Debian,
Ubuntu, and Fedora.
Cheers,
Gabriel.
