[
https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129408#comment-14129408
]
Nitin Mehta edited comment on CLOUDSTACK-5685 at 9/11/14 12:07 AM:
-------------------------------------------------------------------
Basically the logic is something like this
Kelven has made VirtualNetworkApplianceManagerImpl.java (router's Manager)
listener to vm's state transitions.
So whenever a state transition happens and if it is a VR and old state =
stopped and new state = running and the event which triggered is out of band
(FollowAgentPowerOnReport) then reboot the router through CS which would
result in reprogramming the rules as well.
was (Author: nitinme):
Basically the logic is something like this
Keleven has made VirtualNetworkApplianceManagerImpl.java (router's Manager)
listener to vm's state transitions.
So whenever a state transition happens and if it is a VR and old state =
stopped and new state = running and the event which triggered is out of band
(FollowAgentPowerOnReport) then reboot the router through CS which would
result in reprogramming the rules as well.
> [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in
> state detected by cloudstack resulting in VR not bieng programmed with any
> rules.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5685
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5685
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: Kelven Yang
> Fix For: 4.4.0
>
>
> [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in
> state detected by cloudstack resulting in VR not being programmed with any
> rules.
> PreReq:
> Have few Vms deployed using Cloudstack.
> Have PF,Static NAT,LB and Egress rules programmed for the Vms.
> Steps:
> Outside of Cloudstack, Reboot VR.
> After the successful reboot of VR , there are no rules being programmed in
> the VR for the Vms.
> Currently , VM sync does not detect any change of state in the router when
> router is rebooted. So there is no way for CS to know that the router needs
> to be reprogrammed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
