You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Gian Paolo Buono <gi...@gesca.it> on 2017/04/27 05:28:59 UTC
Vpc increase resources
Hi all,
Can i increase, obvious reboot, the resource (cpu/ram) of a online vpc ?
Thanks
GPB
Re: Vpc increase resources
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Glad you got it sorted.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 30/04/2017, 21:39, "Gian Paolo Buono" <gi...@gesca.it> wrote:
Hi,
I have resolved, to change the Vpc Offering is necessary shutdown the vpc.
regards
On 04/30/2017 08:47 PM, Gian Paolo Buono wrote:
> Hi Dag,
> thank you very much, the first 3 point are ok but I can not find how to edit the point 4 to change the VPC offering and also I can not assign the new system offering in the VPC Offering but can assign in Network Offerings.
> Regards
>
> On 04/27/2017 11:57 AM, Dag Sonstebo wrote:
>
> Hi Gian Paolo,
>
> As a general rule of thumb you can not edit service offerings in CloudStack. There are unsupported workarounds if you start looking in the CloudStack DB (service offering table) but in the case of the VPC this is probably not something you want to do since both isolated networks and VPC networks use the same service offerings by default.
>
> So – the correct way of doing this is to create new service offerings. For networks the relationship is Network/VPC > Network offering > System offering, i.e. the CPU / RAM spec you get is only indirectly linked to your network.
>
> So, to increase the CPU/RAM for your VPC network you need to:
>
> 1) Create a new VPC virtual router system offering with your upgraded CPU / RAM levels.
> 2) Copy all settings from your current VPC default offering.
> 3) Create a new VPC network offering, but pointing this to the new VPC VR system offering you created in step 1.
> 4) In your VPC tier use the edit function to assign your newly created VPC offering.
>
> As always – give this a test in a non production environment before relying on it in production.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 27/04/2017, 06:28, "Gian Paolo Buono" <gi...@gesca.it> wrote:
>
> Hi all,
> Can i increase, obvious reboot, the resource (cpu/ram) of a online vpc ?
>
> Thanks
> GPB
>
>
>
>
> Dag.Sonstebo@shapeblue.com<ma...@shapeblue.com>
> http://mail01.gesca.it:32224/?dmVyPTEuMDAxJiZjZjdjY2FlNWI4ZmI5Nzk5Nz01OTA2MzE2Ql82NDg4NF8zMjdfMSYmMGJiZDllMzNlNzc1N2M3PTEyMjMmJnVybD13d3clMkVzaGFwZWJsdWUlMkVjb20=<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
>
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: Vpc increase resources
Posted by Gian Paolo Buono <gi...@gesca.it>.
Hi,
I have resolved, to change the Vpc Offering is necessary shutdown the vpc.
regards
On 04/30/2017 08:47 PM, Gian Paolo Buono wrote:
> Hi Dag,
> thank you very much, the first 3 point are ok but I can not find how to edit the point 4 to change the VPC offering and also I can not assign the new system offering in the VPC Offering but can assign in Network Offerings.
> Regards
>
> On 04/27/2017 11:57 AM, Dag Sonstebo wrote:
>
> Hi Gian Paolo,
>
> As a general rule of thumb you can not edit service offerings in CloudStack. There are unsupported workarounds if you start looking in the CloudStack DB (service offering table) but in the case of the VPC this is probably not something you want to do since both isolated networks and VPC networks use the same service offerings by default.
>
> So – the correct way of doing this is to create new service offerings. For networks the relationship is Network/VPC > Network offering > System offering, i.e. the CPU / RAM spec you get is only indirectly linked to your network.
>
> So, to increase the CPU/RAM for your VPC network you need to:
>
> 1) Create a new VPC virtual router system offering with your upgraded CPU / RAM levels.
> 2) Copy all settings from your current VPC default offering.
> 3) Create a new VPC network offering, but pointing this to the new VPC VR system offering you created in step 1.
> 4) In your VPC tier use the edit function to assign your newly created VPC offering.
>
> As always – give this a test in a non production environment before relying on it in production.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 27/04/2017, 06:28, "Gian Paolo Buono" <gi...@gesca.it> wrote:
>
> Hi all,
> Can i increase, obvious reboot, the resource (cpu/ram) of a online vpc ?
>
> Thanks
> GPB
>
>
>
>
> Dag.Sonstebo@shapeblue.com<ma...@shapeblue.com>
> http://mail01.gesca.it:32224/?dmVyPTEuMDAxJiZjZjdjY2FlNWI4ZmI5Nzk5Nz01OTA2MzE2Ql82NDg4NF8zMjdfMSYmMGJiZDllMzNlNzc1N2M3PTEyMjMmJnVybD13d3clMkVzaGFwZWJsdWUlMkVjb20=<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
>
Re: Vpc increase resources
Posted by Gian Paolo Buono <gi...@gesca.it>.
Hi Dag,
thank you very much, the first 3 point are ok but I can not find how to edit the point 4 to change the VPC offering and also I can not assign the new system offering in the VPC Offering but can assign in Network Offerings.
Regards
On 04/27/2017 11:57 AM, Dag Sonstebo wrote:
Hi Gian Paolo,
As a general rule of thumb you can not edit service offerings in CloudStack. There are unsupported workarounds if you start looking in the CloudStack DB (service offering table) but in the case of the VPC this is probably not something you want to do since both isolated networks and VPC networks use the same service offerings by default.
So – the correct way of doing this is to create new service offerings. For networks the relationship is Network/VPC > Network offering > System offering, i.e. the CPU / RAM spec you get is only indirectly linked to your network.
So, to increase the CPU/RAM for your VPC network you need to:
1) Create a new VPC virtual router system offering with your upgraded CPU / RAM levels.
2) Copy all settings from your current VPC default offering.
3) Create a new VPC network offering, but pointing this to the new VPC VR system offering you created in step 1.
4) In your VPC tier use the edit function to assign your newly created VPC offering.
As always – give this a test in a non production environment before relying on it in production.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 27/04/2017, 06:28, "Gian Paolo Buono" <gi...@gesca.it> wrote:
Hi all,
Can i increase, obvious reboot, the resource (cpu/ram) of a online vpc ?
Thanks
GPB
Dag.Sonstebo@shapeblue.com<ma...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: Vpc increase resources
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Gian Paolo,
As a general rule of thumb you can not edit service offerings in CloudStack. There are unsupported workarounds if you start looking in the CloudStack DB (service offering table) but in the case of the VPC this is probably not something you want to do since both isolated networks and VPC networks use the same service offerings by default.
So – the correct way of doing this is to create new service offerings. For networks the relationship is Network/VPC > Network offering > System offering, i.e. the CPU / RAM spec you get is only indirectly linked to your network.
So, to increase the CPU/RAM for your VPC network you need to:
1) Create a new VPC virtual router system offering with your upgraded CPU / RAM levels.
2) Copy all settings from your current VPC default offering.
3) Create a new VPC network offering, but pointing this to the new VPC VR system offering you created in step 1.
4) In your VPC tier use the edit function to assign your newly created VPC offering.
As always – give this a test in a non production environment before relying on it in production.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 27/04/2017, 06:28, "Gian Paolo Buono" <gi...@gesca.it> wrote:
Hi all,
Can i increase, obvious reboot, the resource (cpu/ram) of a online vpc ?
Thanks
GPB
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue