Gesendet: Montag, 23. Januar 2017 12:28
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen,
Keep in mind what you are doing during this process – the migration
effectively merges the disk chain for each VM to a single bigger disk, which
will now ta
: Montag, 23. Januar 2017 12:28
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen,
Keep in mind what you are doing during this process – the migration effectively
merges the disk chain for each VM to a single bigger disk, which will now take
up a lot more space
mailto:dag.sonst...@shapeblue.com]
Gesendet: Donnerstag, 19. Januar 2017 15:34
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen,
Assuming you are using advanced zones my idea below would involve:
1) Create a patching account in your CloudS
lt?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com]
Gesendet: Donnerstag, 19. Januar 2017 14:41
An: users@cloudstack.apache.org
Betreff: Re: Template management
lt?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Dag Sonstebo [mailto:dag.sonst...@shapeblue.com]
Gesendet: Donnerstag, 19. Januar 2017 14:41
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen again
On 01/19/2017 02:31 PM, S. Brüseke - proIO GmbH wrote:
> @Rene: Of course it is the user's responsibility, but we want to provide a VM
> with the latest updates each time you deploy a new VM. :-) I know that
> cloud-init can do this on boot, but what if the network has no internet
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen,
If you wanted to do this on boot with cloud-init or a similar mechanism you
would actually engineer the solution such that an internet connection wasn’t
required. If you have every VM updating over the internet you end up
anuar 2017 11:03
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi Swen
On 01/19/2017 10:04 AM, S. Brüseke - proIO GmbH wrote:
> I am really interested in other solutions and workflows, so please
> shoot. :-)
We decided to not
anybody know how AWS or DigitalOcean is handling this?
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Rene Moser [mailto:m...@renemoser.net]
Gesendet: Donnerstag, 19. Januar 2017 11:03
An: users@cloudstack.apache.org
Betreff: Re: Template management
Hi
Hi Swen
On 01/19/2017 10:04 AM, S. Brüseke - proIO GmbH wrote:
> I am really interested in other solutions and workflows, so please shoot. :-)
We decided to not doing or minimize (1-2 updates per year) templates
updates for "system updates" for two main reasons:
1. It is the user's
Hi Swen,
You are correct – templates are not housekept on primary storage until all VMs
utilizing them have been deleted (have a look at this blog post if you want to
know a bit more about XenServer disk chains -
http://www.shapeblue.com/recovery-of-vms-to-new-cloudstack-instance/ ).
In short
Hey guys,
I have a question regarding templates and how you manage these in you CS
installation.
We are planning to create a new template for Debian, CentOS and Ubuntu each
month to keep them up2date, because we have a short lifecycle for servers. Does
anybody do the same or has other
12 matches
Mail list logo