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] [Assigned] (CLOUDSTACK-4440) CloudStack should handle native VMware HA for virtual routers
Date Fri, 11 Jul 2014 09:35:05 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sateesh Chodapuneedi reassigned CLOUDSTACK-4440:
------------------------------------------------

    Assignee: Sateesh Chodapuneedi

> CloudStack should handle native VMware HA for virtual routers
> -------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4440
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4440
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc, Management Server
>    Affects Versions: 4.5.0
>            Reporter: Kirk Kosinski
>            Assignee: Sateesh Chodapuneedi
>            Priority: Minor
>              Labels: ha, networking, virtualrouter, vmware, vsphere
>
> Currently when a virtual router is rebooted by native VMware HA in vSphere, it will lose
its network and iptables configuration and cause connectivity problems for VMs. Resolving
this requires manual intervention by the CloudStack administrator; the router must be rebooted,
or the network restarted.
> This behavior is not ideal and will prolong downtime caused by an HA event, and there
is no point for the non-functional virtual router to even be running. CloudStack should handle
this situation gracefully by reconfiguring a virtual router that is successfully rebooted
by VMware HA. 
> In the meantime this limitation should be documented.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message