cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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 Mon, 19 Aug 2013 16:00:49 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743935#comment-13743935
] 

ASF subversion and git services commented on CLOUDSTACK-4294:
-------------------------------------------------------------

Commit f8899f2d12713a7bba24666e3229311cc95a336c in branch refs/heads/4.2 from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f8899f2 ]

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

While upgrading to 4.2, the type of vswitch being used by each cluster is persisted to cluster_details
table. This helps if user want to change the type of vswitch used in a zone or entire cloud
later on but leave existing cluster continue to use old vswitches. Hence even after modifying
the type of vswitch at cloud level (by modifying global configuration parameters) or modifying
the type vswitch at zone level (by modifying the traffic label) would not disturb operation
of existing clusters.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>

                
> 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