[jira] [Resolved] (CLOUDSTACK-686) Allow for same vlan on different physical nics

["Kishan Kavala (JIRA)" <ji...@apache.org>]

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

Kishan Kavala resolved CLOUDSTACK-686.
--------------------------------------

    Resolution: Fixed

Schema changes:
commit 33b87d898596098c70dfe0f017351aa1b904fefe
                
> Allow for same vlan on different physical nics
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-686
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-686
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.0
>            Reporter: Marcus Sorensen
>            Assignee: Kishan Kavala
>             Fix For: 4.1.0
>
>
> There was an email chain about this on the dev list... subject was "same vlan on different nics". Would like to adjust the contstraint in table op_dc_vnet_alloc named i_op_dc_vnet_alloc__vnet__data_center_id to allow for the same vlan number to be used on different physical nics, by changing the unique  from just 'vnet','data_center_id' to 'vnet','physical_network_id','data_center_id'.
> This can be handy for example if you run out of vlans and have the capability to bring up a second layer 2 domain on a different physical nic, or have two customers, each with their own router, creating guest networks on different physical nics and want to use the same IP.
> I'm not comfortable with updating the schema myself, as I don't understand all of the upgrade process around it.
> With this change, I'd also like to have 11fe086adab8e790018343252ed08aac9a27b1c6 rolled back (CLOUDSTACK-226). It was added to work around this database constraint. I can do this portion if someone can work with me on the database change.

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