makes sense @swen. if you don't want the user to be aware of the placements policies.
On Thu, Feb 1, 2024 at 10:20 AM <[email protected]> wrote: > > Hi Daan, > > thx for your input. I would not say I want to migrate a VM while scaling, I > would see it the other way around. I want to change the service offering and > this will include the need to migrate the VM. But at the end both > descriptions have the same result. :-) > I will open an issue for an Improvement Request for this. > > Regards, > Swen > > -----Ursprüngliche Nachricht----- > Von: Daan Hoogland <[email protected]> > Gesendet: Donnerstag, 1. Februar 2024 09:57 > An: [email protected] > Betreff: Re: Migrate a VM to another compute offering > > what you try to do , without explicitly mentioning it, Sven is to migrate the > VM while scaling?I had a quick look but migrate APIs don't give an easily > answer either. Sounds like a > https://github.com/apache/cloudstack/issues/new/choose to me ;) > > On Wed, Jan 31, 2024 at 9:35 AM <[email protected]> wrote: > > > > Hi all, > > > > > > > > we are using 2 compute offerings, called offering1 and offering2. Both > > offerings are "Custom constrained" with similar values for cpu and memory. > > Both offerings are using the same disk offering. > > > > The only difference is that offering1 used host tag "group1" and > > offering2 uses host tag "group2". My goal is to live scale (migrate) a > > vm from > > offering1 to offering2 via UI. When VM is running and I click the "Scale VM" > > icon I only see offering1 in the popup window. > > > > When the VM is stopped and I click on the "Scale VM" icon, I only see > > offering1 and other offerings using the same host tag. In both cases I > > am unable to see offering2. > > > > > > > > Is my goal even possible without altering db directly? > > > > > > > > Regards, > > > > Swen > > > > > -- > Daan > > -- Daan
