[
https://issues.apache.org/jira/browse/CLOUDSTACK-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699310#comment-14699310
]
ASF subversion and git services commented on CLOUDSTACK-8737:
-------------------------------------------------------------
Commit 479733f9feb10e1660fe3262a511c838ca0d0212 in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=479733f ]
Merge pull request #701 from koushik-das/CLOUDSTACK-8737
CLOUDSTACK-8737: Remove out-of-band VR reboot code based on persistent VR
configuration changes
Removed out-of-band VR reboot code
Refer to the discussion on dev list
(http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201506.mbox/%3cac13e3c1-3719-4b48-a35d-dbc4ba704...@schubergphilis.com%3e)
* pr/701:
CLOUDSTACK-8737: Remove out-of-band VR reboot code based on persistent VR
configuration changes Removed out-of-band VR reboot code
Signed-off-by: Remi Bergsma <git...@remi.nl>
> Remove out-of-band VR reboot code based on persistent VR configuration changes
> ------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8737
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8737
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.6.0
>
>
> VR reboot was required to reprogram rules in case it was stopped and started
> outside of CS. With persistent VR configuration changes (added in 4.6) the
> rules are persisted across a stop-start of VR. So no need to do VR reboot.
> Refer to the following discussion on dev list.
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201506.mbox/%3cac13e3c1-3719-4b48-a35d-dbc4ba704...@schubergphilis.com%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
