[jira] [Commented] (CLOUDSTACK-7191) On restartNetwork destroy the VR immediatley, instead of cleanup the rules then destroy

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 816eb63e972be6a1eaa20667e461d24882b3ee47 in cloudstack's branch refs/heads/4.3 from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=816eb63 ]

CLOUDSTACK-7191:On restartNetwork destroy the VR immediatley, instead of
cleanup the rules then destroy

fix adds a provision to specify if cleanup is needed on network on
shutdown. VR is marked as to not to require network rules clean up on
network shutdown as the VR is destroyed and recreated.

ran the simulator tests that test network life cycle

(cherry picked from commit 67876b215ef5217b3d306b3642a38a3708a30494)
Signed-off-by: Rohit Yadav <ro...@shapeblue.com>


> On restartNetwork destroy the VR immediatley, instead of cleanup the rules then destroy
> ---------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7191
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7191
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.5.0
>
>
> RestartNetwork is implemented with below logical steps
>    
>    - clean up network rules on the provider (implemented by shutdownNetworkResources)
>   - shutdown the providers for the network
>  - implement all providers for the network
> - reprogram the rules
> step #1 is unnecessary in case the provider is appliance based like virtual router. so at present even for the VR significant amount of time is consumed to clean up the rules. This step is unnecessary as appliance will get destroyed any ways in next step.
> During upgrades in an environments with large number of networks with VR as the only provider, it will take significant time.
> This bug should ensure cleanup of rules is done only if required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)