From issues-return-88245-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Fri Jan 5 11:09:09 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D7CF218077B for ; Fri, 5 Jan 2018 11:09:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C7E1F160C3C; Fri, 5 Jan 2018 10:09:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1940F160C27 for ; Fri, 5 Jan 2018 11:09:08 +0100 (CET) Received: (qmail 77398 invoked by uid 500); 5 Jan 2018 10:09:08 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 77389 invoked by uid 500); 5 Jan 2018 10:09:08 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 77386 invoked by uid 99); 5 Jan 2018 10:09:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 10:09:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BFF07C24C7 for ; Fri, 5 Jan 2018 10:09:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Xb-SoEZnN4BX for ; Fri, 5 Jan 2018 10:09:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A55F25F6C8 for ; Fri, 5 Jan 2018 10:09:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id F2EF3E25C5 for ; Fri, 5 Jan 2018 10:09:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A49AB240F2 for ; Fri, 5 Jan 2018 10:09:01 +0000 (UTC) Date: Fri, 5 Jan 2018 10:09:01 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9889) Dedicate guest vlan range to a domain MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9889?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16312832#comment-16312832 ]=20 ASF GitHub Bot commented on CLOUDSTACK-9889: -------------------------------------------- blueorangutan commented on issue #2102: CLOUDSTACK-9889 Dedication of guest= vlan range to a domain URL: https://github.com/apache/cloudstack/pull/2102#issuecomment-353342521 =20 =20 Packaging result: =E2=9C=96centos6 =E2=9C=96centos7 =E2=9C=96debian. JID= -1452 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. =20 For queries about this service, please contact Infrastructure at: users@infra.apache.org > Dedicate guest vlan range to a domain > -------------------------------------- > > Key: CLOUDSTACK-9889 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-988= 9 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Reporter: subhash yedugundla > > List of scenarios covered > *Dedication of guest Vlan range* > Admin should be allowed dedicate guest vlan ranges to a domain > While dedicating a guest Vlan range > If the range overlaps with any of the existing dedicated range then exten= d the existing dedicated range > Otherwise add it as a new dedicated guest Vlan range > If the range doesn=E2=80=99t exist in the system then the request should = fail > If any of the vlan in the range is in use by a network that belongs to a = different account of different domain then the request should fail > *Releasing guest Vlan range* > Admin should be allowed to release a dedicated guest vlan range that is d= edicated to a domain back to the system pool > If the range is not dedicated to the domain then the request should fail > Even If one/more of the Vlans belonging to the range is in use by a netwo= rk the range should be released back to the system pool > The vlans that are in use should continue to be in use by the network > *Network implementation* > If the network belongs to an account that has a dedicated range of Vlans = then a Vlan from the account's dedicated range should be allocated to the n= etwork > If an account uses up all of its dedicated Vlan=E2=80=99s the next networ= k being created for the account should be assigned a Vlan that belongs to t= he domain pool > Otherwise, a Vlan should be allocated from the free pool i.e. Vlan range = belonging to the zone > *Network creation* > If a Vlan id is specified and if this id belongs to a dedicated Vlan rang= e of a different account/domain then the creation should fail > If a Vlan id is specified and if this id belongs to the system pool but t= he network owner has a range of dedicated range of vlans then the creation = should fail > *Domain deletion* > Guest Ip ranges and vlans dedicated to the domain should be released back= to the free pool=20 > *Account deletion* > When an account is deleted, the IP ranges and vlans associated with the a= ccount should be moved to system pool. -- This message was sent by Atlassian JIRA (v6.4.14#64029)