cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-6205) VPC: when network is created in Setup state (with vlan specified), it never gets plugged to the VPC VR after restart
Date Wed, 05 Mar 2014 22:00:44 GMT
Alena Prokharchyk created CLOUDSTACK-6205:
---------------------------------------------

             Summary: VPC: when network is created in Setup state (with vlan specified), it
never gets plugged to the VPC VR after restart
                 Key: CLOUDSTACK-6205
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6205
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.3.0
            Reporter: Alena Prokharchyk
            Assignee: Alena Prokharchyk
            Priority: Blocker
             Fix For: 4.3.0


1. VPC Isolated Guest network in Setup state (vlan is specified at the moment of creation
by the Root admin), doesn’t get replugged to the VPC VR upon its restart. Happens when the
network is created in Setup State (with Vlan specified)
2. When new VM starts up in this non-plugged network, network gets plugged, but the LB rules
are not getting programmed on the VR for this network/vm


Root cause for #1 - when the code forms the nics for the Guest networks, it considers only
networks in Implemented state:
List<? extends Network> guestNetworks = _vpcMgr.getVpcNetworks(vpcId);
for (Network guestNetwork : guestNetworks) {
if (guestNetwork.getState() == Network.State.Implemented) {
We should add one more condition - the network can be as well in setup state.

 #2 is obviously caused by #1. When VR gets restarted, following happens:
All guest networks in Implemented/Setup state from this VPC supposed to re-plugged to the
VR
All networking rules should be set for all the networks that got plugged.
If there was some network in non-implemented/non-setup state, its rules will not get applied.
They will get applied later as a part of network implement. So once #1 is fixed, the LB rules
issue will get fixed as well.



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

Mime
View raw message