davidjumani edited a comment on issue #5202:
URL: https://github.com/apache/cloudstack/issues/5202#issuecomment-885370657


   > sorry, That will leave people with disfunctional environments. -1
   
   Reasons why I'm against adding anything to the upgrade path :
   1. It is a bad assumption that all pvlans created in vmware are community 
and correspondingly created as isolated in cloudstack. There could be admins 
who created isolated pvlans in vmware and cloudstack. Changing all isolated 
pvlans to community will break the correctly working functionality
   2. Pvlans were created as community in vmware and correspondingly created as 
isolated in cloudstack (knowing that community wasn't supported at the time. 
That's kinda on the admin)
   3. Pvlans are also created on Xen and KVM (implemented via OVS) and altering 
it in the db via an upgrade path will break their functionality
   4. This update is probably a niche case, especially considering 2
   
   That being said, any admin who feels that there is a mismatch between what 
is existing on vmware and cloudstack should manually update it.
   
   


-- 
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]


Reply via email to