davidjumani commented on issue #5202: URL: https://github.com/apache/cloudstack/issues/5202#issuecomment-884850858
If I'm understanding this correctly, other existing pvlans (in vmware) were created as isolated in cloudstack as that's the only one that was supported at that time. If that's right, updating the isolated pvlans to community ones in the db via an upgrade path is not a good idea. Assuming there are isolated pvlans created in VMware and correctly created as isolated pvlans in cloudstack, a db upgrade would change them to community ones which is incorrect. Imo, since full-fledged pvlans is a new feature, the user will need to manually upgrade it, or allow editing the pvlan via the update API (which is risky as KVM supports pvlans as well, and updating it will require reapplying the appropriate ovs rules on all the hosts for every vm on that network) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
