how to change VPC offering of an existing VPC?

[sbrueseke]

I need to change the VPC offering of an existing VPC. As far as I see, this is not possible via UI (at least in 4.19). I found an api call migrateVPC which should do what I need to do.
https://cloudstack.apache.org/api/apidocs-4.19/apis/migrateVPC.html

But I do not get the call right. I use cloudmonkey adn getting this error:
"jobprocstatus": 0,
"jobresult": {
"errorcode": 431,
"errortext": "Failed to migrate VPC as the specified tierNetworkOfferings is not complete"

I do not understand how to format tiernetworkofferings parameter to get it working. Let's say we have 2 networks, called net1 and net2. How do I need to format the api call to migrate the VPC to another offering?

regards,
Swen

[shwstppr]

@sbrueseke can you try adding something like the following to the API call,

tierNetworkOfferings[0].networkId=<ID_OF_net1> tierNetworkOfferings[0].networkOfferingId=<ID_OF_NETWORK_OFFERING_FOR_net1> tierNetworkOfferings[1].networkId=<ID_OF_net2> tierNetworkOfferings[1].networkOfferingId=<ID_OF_NETWORK_OFFERING_FOR_net2>

Based on the API description I see it is meant to migrate a VPC to a new physical network so I'm not sure if it will work if the physical network is the same

[sbrueseke]

thx for the reply! I already did this and it did not work. So maybe it is not possible to use this api call to change a VPC offering if using the same physical network. Any idea how to change a VPC offering?

[shwstppr]

@sbrueseke I don't see any other API/operation changing offering for a VPC. Something we can try adding in future for updateVpc API.

[sbrueseke]

is there a use case for this? We run into this problem, because when using redundant VR in a VPC with a lot of traffic, the default VR service offering is just not enough with 1 cpu and 512mb memory.
Sure, we can change the serive offering for an individual VR when shutting it down and changing the offering via UI, but when restarting a VPC with cleanup is enabled, then the new VRs getting the default service offering again.
What are others doing, when you need to add more routing power to an already existing VPC?

[sbrueseke]

yes, exactly. In the end I need the redundant VRs to use another service offering with more cpu and memory.

[weizhouapache]

@sbrueseke
I do not think there is an API to do it.

maybe you can the following as a workaround.

• create system service offering for domainrouter
• create vpc offering with the service offering
• update vpc.vpc_offering to the id of vpc offering
• restart vpc with cleanup

[sbrueseke]

"update vpc.vpc_offering to the id of vpc offering" in db, correct?

[weizhouapache]

"update vpc.vpc_offering to the id of vpc offering" in db, correct?

correct. for example

update vpc set vpc_offering_id=246 where id=339;

[sbrueseke]

It looks like this workaround is doing the offering change. After performing a clean vpc restart, the VR do use the new offering.

[weizhouapache]

good
it would be good to have an API doing it