Template management

[S . Brüseke - proIO GmbH]

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 workflows for that?

One big downside of that is that (as far as I understand CS) our primary 
storage (we are using XenServer) is getting filled up with templates. CS is not 
deleting a template until all VMs created by this template are expunged. Can 
somebody confirm this?

I am really interested in other solutions and workflows, so please shoot. :-)

Mit freundlichen Grüßen / With kind regards,

Swen



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Move resources from project to default view or other projects

[Natalia Costas Lago]

Dear all,


I have seen from the list archives that time ago a VM or template from a 
project cannot be moved to a different project or default view.


Is that still the current situation?

I have several VMs running under a project (and also templates) that 
need to be reasigned... how can I do that?



Thank you in advance,

Kind regards,


--

Natalia Costas Lago
Senior Communications Technician
Galicia Supercomputing Centre (CESGA)
(CESGA on Twitter   | CESGA on Facebook 
)


Avenida de Vigo, s/n (Campus Vida)
15705 Santiago de Compostela - SPAIN

E-mail: nata...@cesga.es
Cell: +34 981 56 98 10 (ext. 237)
Fax: +34 981 59 46 16
Web: https://www.cesga.es/

[IMPORTANTE] La información contenida en este mensaje y
sus posibles documentos adjuntos es privada y confidencial
y está dirigida únicamente a su destinatario/a. Si usted no
es el/la destinatario/a original de este mensaje, por favor
elimínelo. La distribución o copia de este mensaje no está
autorizada.

Re: Template management

[Rene Moser]

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 responsibility to keep systems up to date anyway.
2. Using cfg management and/or cloud-init is more than easy to update
systems.

Regards
René

Re: Using mariadb as management database

[Vibol Vireak]

I'm updating my question. Any hope ?

2017-01-17 18:12 GMT+07:00 Vibol Vireak :

> Hello, Everyone.
>
> I'm testing and installing cloudstack working fine. But after i receive
> change note from 4.5.2
>
> Link referrer http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/en/4.5.2/about.html
>
> On the section improvements said
>
> Use of MariaDB as cloudstack management server database
>
> When i try to install cloudstack management version 4.5 using cloudstack
> repos on ubuntu 14.04
>
> First apt install mariadb-server
> then apt install cloudstack-management
>
> ---
> The following packages have unmet dependencies:
>  cloudstack-management : Depends: mysql-client
> ---
>
> It look like cloudstack are not fully support mariadb as well.
>
> Testing with separate management server and database server is working
> fine.
>
> Thank you for all help
>

Re: Dedicated IP range for SSVM/CPVM

[Rene Moser]

https://issues.apache.org/jira/browse/CLOUDSTACK-9750

Re: Template management

[Dag Sonstebo]

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 the problem you describe is something that hits most people who want 
to do monthly template updates, and as you hint at it can really only be 
managed with sufficiently sized storage pools, and if possible – by using 
things like thin provisioning and deduplication, etc.

Other solutions would rely on you either running a managed infrastructure where 
you provide an automated patching mechanism with e.g. Ansible /  Puppet / Chef 
/ etc. – but this would in most cases mean you have to plan patching with all 
your customers – something I doubt you want to do.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 19/01/2017, 09:04, "S. Brüseke - proIO GmbH"  wrote:

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 workflows for that?

One big downside of that is that (as far as I understand CS) our primary 
storage (we are using XenServer) is getting filled up with templates. CS is not 
deleting a template until all VMs created by this template are expunged. Can 
somebody confirm this?

I am really interested in other solutions and workflows, so please shoot. 
:-)

Mit freundlichen Grüßen / With kind regards,

Swen



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind 
nicht gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in 
error) please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden. 





dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

AW: Template management

[S . Brüseke - proIO GmbH]

@Dag: Thanks for the confirmation and for the link.

@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 
connection?

Does 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 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 responsibility to keep systems up to date anyway.
2. Using cfg management and/or cloud-init is more than easy to update systems.

Regards
René


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: Template management

[Dag Sonstebo]

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 paying for 
a lot of unnecessary bandwidth. You would instead make sure you have internal 
cloned patch repositories which you synchronize hourly/daily  - which means all 
user VMs only pull patches on the internal network. You could even “eat your 
own dogfood/drink your own champagne” and host this on one of the accounts in 
the same CloudStack infrastructure – then simply set up connection on the 
public network. That way the update traffic isn’t ever leaving your switches 
per se.

Not sure how AWS etc. do this, but they have deep pockets…

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 19/01/2017, 13:31, "S. Brüseke - proIO GmbH"  wrote:

@Dag: Thanks for the confirmation and for the link.

@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 
connection?

Does 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 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 responsibility to keep systems up to date anyway.
2. Using cfg management and/or cloud-init is more than easy to update 
systems.

Regards
René


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind 
nicht gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in 
error) please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden. 





dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: AW: Template management

[Rene Moser]

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 
> connection?

I understand, my comment was more like for the topic "how others do it". ;)

Regards
René

AW: Template management

[S . Brüseke - proIO GmbH]

Hi Dag,

how can I provide connection to an internal repo for all networks in my CS 
installation by default?

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,

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 paying for 
a lot of unnecessary bandwidth. You would instead make sure you have internal 
cloned patch repositories which you synchronize hourly/daily  - which means all 
user VMs only pull patches on the internal network. You could even “eat your 
own dogfood/drink your own champagne” and host this on one of the accounts in 
the same CloudStack infrastructure – then simply set up connection on the 
public network. That way the update traffic isn’t ever leaving your switches 
per se.

Not sure how AWS etc. do this, but they have deep pockets…

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 19/01/2017, 13:31, "S. Brüseke - proIO GmbH"  wrote:

@Dag: Thanks for the confirmation and for the link.

@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 
connection?

Does 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 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 responsibility to keep systems up to date anyway.
2. Using cfg management and/or cloud-init is more than easy to update 
systems.

Regards
René


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind 
nicht gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in 
error) please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden. 





dag.sonst...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 



- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in error) 
please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden. 

Re: Template management

[Dag Sonstebo]

Hi Swen,

Assuming you are using advanced zones my idea below would involve:

1) Create a patching account in your CloudStack environment.
2) Spin up your repo clone boxes in this account – and configure these with 
some sort of nightly synch with the RHEL / Ubuntu / CentOS / etc yum etc 
repositories.
3) On the public IP address for the patching account configure firewalling / 
NATing to allow anyone from the same public IP range to access the repo boxes.
4) Configure a DNS entry for this IP address on the DNS servers used by your 
CloudStack infrastructure.
5) Configure cloud-init or similar to check for updates on the DNS server name 
– either on reboot or with a cron type job on a specific date of the month.

Just one idea, there will be many ways to do this. The synched repo boxes don’t 
need to be hosted in CloudStack, they could just be hosted externally on an IP 
address accessible from your public range.
The other thing is you probably want your end users to be able to opt in or out 
of this mechanism, so you may want to put in place some user key/values to 
control this. If you wanted you could also rig up some automation where the VM 
is snapshot’ed prior to patching so users have a rollback point.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 19/01/2017, 14:09, "S. Brüseke - proIO GmbH"  wrote:

Hi Dag,

how can I provide connection to an internal repo for all networks in my CS 
installation by default?

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,

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 paying for 
a lot of unnecessary bandwidth. You would instead make sure you have internal 
cloned patch repositories which you synchronize hourly/daily  - which means all 
user VMs only pull patches on the internal network. You could even “eat your 
own dogfood/drink your own champagne” and host this on one of the accounts in 
the same CloudStack infrastructure – then simply set up connection on the 
public network. That way the update traffic isn’t ever leaving your switches 
per se.

Not sure how AWS etc. do this, but they have deep pockets…

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 19/01/2017, 13:31, "S. Brüseke - proIO GmbH"  
wrote:

@Dag: Thanks for the confirmation and for the link.

@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 
connection?

Does 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 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 responsibility to keep systems up to date anyway.
2. Using cfg management and/or cloud-init is more than easy to update 
systems.

Regards
René


- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main

USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, 
informieren Sie bitte sofort den Absender und vernichten Sie diese 
Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind 
nicht gestattet. 

This e-mail may contain confidential and/or privileged information. 
If you are not the intended recipient (or have received this e-mail in 
error) please notify 
the sender immediately and destroy this e-mail.  
Any unauthorized copying, disclosure or distribution of the material in 
this e-mail is strictly forbidden. 

  

Secondary storage 0KB in dashboard.

[조대형]

Permalink 
Raw Message
Hi, All


I have install cloudstack 4.7on new centos 6.xwith latest kernel. I manage
to make cloudstack management up and running. I have success adding primary
storage . When I try to add secondary storage from same nfs server,
from dashboard it show 0 KB. But using same nfs same server no problem on
primary. I'm still confused.
Any solutions?

Re: Move resources from project to default view or other projects

[Rafael Weingärtner]

I do not think this feature was added yet.

On Thu, Jan 19, 2017 at 3:25 AM, Natalia Costas Lago 
wrote:

>
> Dear all,
>
>
> I have seen from the list archives that time ago a VM or template from a
> project cannot be moved to a different project or default view.
>
> Is that still the current situation?
>
> I have several VMs running under a project (and also templates) that need
> to be reasigned... how can I do that?
>
>
> Thank you in advance,
>
> Kind regards,
>
>
> --
> 
> Natalia Costas Lago
> Senior Communications Technician
> Galicia Supercomputing Centre (CESGA)
> (CESGA on Twitter   | CESGA on Facebook <
> https://www.facebook.com/profile.php?id=10707537407>)
>
> Avenida de Vigo, s/n (Campus Vida)
> 15705 Santiago de Compostela - SPAIN
>
> E-mail: nata...@cesga.es
> Cell: +34 981 56 98 10 (ext. 237)
> Fax: +34 981 59 46 16
> Web: https://www.cesga.es/
> 
> [IMPORTANTE] La información contenida en este mensaje y
> sus posibles documentos adjuntos es privada y confidencial
> y está dirigida únicamente a su destinatario/a. Si usted no
> es el/la destinatario/a original de este mensaje, por favor
> elimínelo. La distribución o copia de este mensaje no está
> autorizada.
>



-- 
Rafael Weingärtner