cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-4294) After upgrade of CloudStack to 4.2, support old vswitch type in existing clusters if user changes the vswitch backend to another type of vSwitch
Date Tue, 13 Aug 2013 12:25:47 GMT
Sateesh Chodapuneedi created CLOUDSTACK-4294:
------------------------------------------------

             Summary: After upgrade of CloudStack to 4.2, support old vswitch type in existing
clusters if user changes the vswitch backend to another type of vSwitch
                 Key: CLOUDSTACK-4294
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4294
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VMware
    Affects Versions: 4.2.0
            Reporter: Sateesh Chodapuneedi
            Assignee: Sateesh Chodapuneedi
            Priority: Critical
             Fix For: 4.2.0


In cloudstack deployed with VMware clusters, If user upgrades to 4.2 and would like to leverage
dvSwitch as network backend for virtual networks without disturbing existing clusters there
needed some mechanism that helps a cluster remember it's existing vswitch type. This helps
existing cluster continues to use the vswitch type which is being used before switching the
backend to other type of vswitch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message