[jira] [Resolved] (CLOUDSTACK-968) marvin: vlan should be an attribute of the physical_network and not the zone

["Prasanna Santhanam (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanna Santhanam resolved CLOUDSTACK-968.
-------------------------------------------

    Resolution: Fixed

commit 8d3cbc82d80eb0c4ead6f68377157fd477fe2d76
Author: Prasanna Santhanam <ts...@apache.org>
Date:   Sat Jan 12 14:38:14 2013 +0530

    marvin: fixes for handling multiple phy. networks
    
    zones do not qualify for vlans but phy networks should carry the
    underlying vlan information. moving the vlan down to physical_network
    in configGenerator.py.
    
    also the sandbox example has been corrected to reflect this change
    and includes an illustration of using traffic types with labels.
    
    Signed-off-by: Prasanna Santhanam <ts...@apache.org>
    Reported-By: Marcus Sorenson <ml...@apache.org>

                
> marvin: vlan should be an attribute of the physical_network and not the zone
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-968
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-968
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Test Tools
>    Affects Versions: 4.0.0
>            Reporter: Prasanna Santhanam
>            Assignee: Prasanna Santhanam
>              Labels: marvin
>             Fix For: 4.1.0
>
>
> On Fri, Jan 11, 2013 at 10:50 AM, Marcus Sorensen <sh...@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