On Fri, Mar 29, 2019 at 1:24 AM Andrija Panic <[email protected]> wrote:
> Hi, > > you don't have to re-apply (nor there is such thing) same offering to a VM > (you could change to other offering and back to original one - but that > doesn't change a thing) - when VM is booted, some parameters are read from > it's offering and applied acordingly (while some parameters might be cloned > from the disk_offering / service_offering table to the vm_instance table > during VM creation - but this doesn't apply for network rate) > > Depending on hypervisor, it should be enoughto just stop and start VM - > that would trigger the update of network rate for that VM. > I'm personally not sure if 0 means unlimited, worth trying with very high > value (i.e.99999) - anyway, try to confirm on hypervisor level if the new > value is applied > > Andrija > > On Thu, 28 Mar 2019 at 21:33, Fariborz Navidan <[email protected]> > wrote: > > > Hello, > > > > I have custom service offering with custom cpu and memory. I have > modified > > the offering's network rate to be set to 0 for unlimited bandwidth. > > CloudStack's native UI does not allow to change service offering of a VM > > due to a bug. How can I re-apply the service offering to VMs deployed > with > > it via cloudmonkey? > > > > Thanks > > > > > -- > > Andrija Panić >
