incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-969) api: zone response lists vlan in it as "vlan range of zone" but the vlan belongs to physical network
Date Sun, 13 Jan 2013 08:30:12 GMT
Prasanna Santhanam created CLOUDSTACK-969:
---------------------------------------------

             Summary: api: zone response lists vlan in it as "vlan range of zone" but the
vlan belongs to physical network
                 Key: CLOUDSTACK-969
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-969
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API
    Affects Versions: 4.0.0
            Reporter: Prasanna Santhanam
            Priority: Minor
             Fix For: 4.1.0


While looking through CLOUDSTACK-968 I notice that the ZoneResponse.java still contains the
vlan that used to be part of 2.2. This vlan now belongs to the PhysicalNetworkResponse.java.
Right now shows up in Marvin's response classes for createZoneResponse

public class ZoneResponse extends BaseResponse {
 . ..

    @SerializedName(ApiConstants.VLAN) @Param(description="the vlan range of the zone")
    private String vlan;
..
}

public class PhysicalNetworkResponse extends BaseResponse {
...
    @SerializedName(ApiConstants.VLAN) @Param(description="the vlan of the physical network")
    private String vlan;

...
}


On Fri, Jan 11, 2013 at 10:50 AM, Marcus Sorensen <shadowsor@gmail.com>wrote

It seems that if I set a vlan range for a zone, marvin attempts to
set that vlan range for every physical network defined for the zone. So the
first one succeeds, the second one fails. The vlan property should be moved
up to be a member of the physical network as far as marvin is concerned.
We're in the process of making changes that allow you to use the same vlan
numbers on different physical networks anyway, since it's possible that you
can have completely separate infrastructure on each nic

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message