cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6205) VPC: when network is created in Setup state (with vlan specified), it never gets plugged to the VPC VR after restart
Date Fri, 14 Mar 2014 19:06:44 GMT


ASF subversion and git services commented on CLOUDSTACK-6205:

Commit d9e1c9c5025ba9d8f7083dacea92938a2b379827 in cloudstack's branch refs/heads/master from
[;h=d9e1c9c ]

CLOUDSTACK-6205: VPC VR start - skip private gateway when create Guest nics as the nic for
the private gateway is being created separately


> 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:
>             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

View raw message