[
https://issues.apache.org/jira/browse/CLOUDSTACK-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113590#comment-14113590
]
Murali Reddy commented on CLOUDSTACK-6750:
------------------------------------------
Problem;
-----------
A VM can be launched in a network, where network is created in one zone, but VM
is being launched in different zone. This can be possible if the network
supports ability to stretch across the zones. A new capability 'strechedl2' is
added for the 'connectivity' service. If a network is created with network
offering which has 'strechedl2' capability enabled for the 'connectivity'
service enabled, then network can be stretched to different zone than one in
which it is created. However 'Connectivity' service provider specified in the
network offering need to be enabled in the zone to be able to extend the
network. So if the 'Connectivity' service provider is not enabled in the zone
then VM deployment and extending network to new zone should fail. But as
reported this is not happening which needs to be fixed.
Root Cause Analysis:
--------------------------
Root cause of the bug is that this scenario is not though when the feature
implemented.
Proposed Solution:
------------------------
Add a validation check to ensure the 'Connectivity' service provider is enabled
in the zone before extending the network to a new zone.
QA steps:
-------------
Disable connectivity service provider in the zone, and verify that when you a
extend a network created in a different zone to the zone in which connectivity
service provider is disables, deploy VM should fail.
Conversely when 'Connectivy' service provider is enabled then extending the
network to new zone which has connectivity service provider is enabled should
succeed.
> [OVS] With stretched network deploying vm in a ovs disabled zone does not
> fail
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6750
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6750
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> e6961fd21bb6d793302c234d0f409f66dc498072
> Reporter: Sanjeev N
> Assignee: Murali Reddy
> Priority: Critical
> Labels: DEV_REVIEWED, ovs
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> [OVS] With stretched network deploying vm in a ovs disabled zone does not
> fail
> Steps to reproduce:
> ================
> 1.Bring up CS with two advanced zones say z1 & z2 using xen clusters
> Create physical networks in both the zones with GRE isolation
> 2.Create network offering with virtual network and ovs as the provider and
> with StretchedL2Subnet enabled
> 3.Create guest network with above offering in zone z2
> 4.Deploy vm in the above network in z2
> 5.Disable ovs service providers in zone z1
> 6.Now deploy vm in z1 with stretched network created in z2
> Result:
> ======
> VM deployment was successful in z1 even though ovs provider was disabled.
> Also ovs bridge and tunnel ports were created on both the hosts in z1&z2
> Expected Result:
> ==============
> VM deployement in z1 with ovs network created in z2 should fail since ovs
> service provider is disabled in z1
--
This message was sent by Atlassian JIRA
(v6.2#6252)
