cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-9903) Allow mechanism to change/deallocate VLAN id held by an existing network
Date Thu, 04 May 2017 07:30:04 GMT
Rohit Yadav created CLOUDSTACK-9903:
---------------------------------------

             Summary: Allow mechanism to change/deallocate VLAN id held by an existing network
                 Key: CLOUDSTACK-9903
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9903
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
            Reporter: Rohit Yadav
             Fix For: Future


VLAN id/ranges can be dedicated to an account. However, if a vlan id/range is released for
the account that vlan id may be held by an existing network owned by that account.

The restartNetwork API has a cleanup option that cleans up old network elements such as VR,
but does not de-allocate or switches to a new vlan id.  For an existing network, provide an
API or mechanism to remove/change vlan id for that network. For example, a way to pass option
to de-allocate the held vlan id or specify a new vlan id in the restartNetwork API.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message