I've seen this before and as a workaround I've changed it with CloudMonkey who 
handles this better.
Try from CM to see if you can change it.

Rgds
Patrick

-----Original Message-----
From: Sanjeev N [mailto:sanj...@apache.org] 
Sent: vendredi 10 juillet 2015 07:58
To: users@cloudstack.apache.org
Subject: Re: Change network offering without changing CIDR

We should be able to change the network offering without changing cidr and 
without stopping vms. If it is not then it is a bug.

On Fri, Jul 10, 2015 at 1:13 AM, Nux! <n...@li.nux.ro> wrote:

> Well, it looks like it requires all VMs to be in stopped state.
> Isn't it possible to change the current working network to fit 
> whatever needs you are after?
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Gerolamo Valcamonica" <cloudst...@overweb.it>
> > To: users@cloudstack.apache.org
> > Sent: Tuesday, 7 July, 2015 15:20:24
> > Subject: Change network offering without changing CIDR
>
> > Hi everybody,
> > i'm using Cloudstack 4.3 with KVM
> >
> > I'd like to change network offering on a client network.
> > So i created a new Network offering based on 
> > DefaultIsolatedNetworkOfferingWithSourceNatService
> > Now i can go to my client network -> edit -> select
> > DefaultIsolatedNetworkOfferingWithSourceNatService2 -> apply
> >
> > A popup alerts me:
> > "Do you want to keep the current guest network CIDR unchanged?"
> >
> > If i select "NO" i got this error: "All user vm of network of 
> > specified id should be stopped before changing CIDR!"
> >
> > If i select "YES" i got this error: "Cannot specify this nework 
> > offering change and guestVmCidr at same time. Specify only one."
> >
> > CIDR is: 10.10.1.0/24
> >
> > So the question is:
> > can I change a network offering without changing CIDR and / or 
> > rebooting VMs?
> >
> > As alternative question: how can change max bandwith only on a 
> > specific user network already using my infrastructure?
> >
> > Thanks!
> >
> > --
> > Gerolamo Valcamonica
>

Reply via email to