Return-Path: X-Original-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E1096DE81 for ; Thu, 7 Mar 2013 11:08:52 +0000 (UTC) Received: (qmail 58976 invoked by uid 500); 7 Mar 2013 11:08:52 -0000 Delivered-To: apmail-incubator-cloudstack-commits-archive@incubator.apache.org Received: (qmail 58773 invoked by uid 500); 7 Mar 2013 11:08:50 -0000 Mailing-List: contact cloudstack-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-commits@incubator.apache.org Received: (qmail 58761 invoked by uid 99); 7 Mar 2013 11:08:50 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 11:08:50 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 1A412831315; Thu, 7 Mar 2013 11:08:50 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: radhika@apache.org To: cloudstack-commits@incubator.apache.org X-Mailer: ASF-Git Admin Mailer Subject: git commit: refs/heads/master - Revert "cloudstack-850" Message-Id: <20130307110850.1A412831315@tyr.zones.apache.org> Date: Thu, 7 Mar 2013 11:08:50 +0000 (UTC) Updated Branches: refs/heads/master 320ab0a96 -> a8b5440bf Revert "cloudstack-850" This reverts commit 320ab0a968ab56faba930c3eb9843ae129e9e2d5. Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/a8b5440b Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/a8b5440b Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/a8b5440b Branch: refs/heads/master Commit: a8b5440bf4c9638383e52c701b59ed9d68391893 Parents: 320ab0a Author: Radhika PC Authored: Thu Mar 7 16:37:30 2013 +0530 Committer: Radhika PC Committed: Thu Mar 7 16:37:30 2013 +0530 ---------------------------------------------------------------------- docs/en-US/advanced-zone-guest-ip-addresses.xml | 11 +- docs/en-US/networks.xml | 3 - docs/en-US/reserved-ip-addresses-non-csvms.xml | 163 ------------------ 3 files changed, 4 insertions(+), 173 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/a8b5440b/docs/en-US/advanced-zone-guest-ip-addresses.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/advanced-zone-guest-ip-addresses.xml b/docs/en-US/advanced-zone-guest-ip-addresses.xml index 269ec59..fbc6144 100644 --- a/docs/en-US/advanced-zone-guest-ip-addresses.xml +++ b/docs/en-US/advanced-zone-guest-ip-addresses.xml @@ -11,7 +11,9 @@ to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY @@ -20,11 +22,6 @@ under the License. -->
- Advanced Zone Guest IP Addresses - When advanced networking is used, the administrator can create additional networks for use - by the guests. These networks can span the zone and be available to all accounts, or they can be - scoped to a single account, in which case only the named account may create guests that attach - to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The - administrator may provision thousands of these networks if desired. Additionally, a part of the - IP address space can also be reserved for non-&PRODUCT; VMs and servers. + Advanced Zone Guest IP Addresses + When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired.
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/a8b5440b/docs/en-US/networks.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/networks.xml b/docs/en-US/networks.xml index 4959583..8305769 100644 --- a/docs/en-US/networks.xml +++ b/docs/en-US/networks.xml @@ -31,12 +31,10 @@ - - @@ -45,7 +43,6 @@ - http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/a8b5440b/docs/en-US/reserved-ip-addresses-non-csvms.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/reserved-ip-addresses-non-csvms.xml b/docs/en-US/reserved-ip-addresses-non-csvms.xml deleted file mode 100644 index 7d385ff..0000000 --- a/docs/en-US/reserved-ip-addresses-non-csvms.xml +++ /dev/null @@ -1,163 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -
- IP Reservation in Isolated Guest Networks - In Isolated guest networks, a part of the guest IP address space can be reserved for - non-&PRODUCT; VMs or physical servers. To do so, you configure a range of Reserved IP addresses - by specifying the CIDR when a guest network is in Implemented state. If your customers wish to - have non-&PRODUCT; controlled VMs or physical servers on the same network, they can share a part - of the IP address space that is primarily provided to the guest network. - In an Advanced zone, an IP address range or a CIDR is assigned to a network when the network - is defined. The &PRODUCT; virtual router acts as the DHCP server and uses CIDR for assigning IP - addresses to the guest VMs. If you decide to reserve IP ranges for non-&PRODUCT; purposes, you - can specify a part of the IP address range or the CIDR that should only be allocated by the DHCP - service of the virtual router to the guest VMs created in &PRODUCT;. The remaining IPs in that - network are called Reserved IP Range. When IP Reservation is configured, the administrator can - add additional VMs or physical servers that are not part of &PRODUCT; to the same network and - assign them the Reserved IP addresses. &PRODUCT; guest VMs cannot acquire IPs from the Reserved - IP Range. -
- IP Reservation Considerations - Consider the following before you reserve an IP range for non-&PRODUCT; machines: - - - IP Reservation can be applied only when the network is in Implemented state. - - - No IP Reservation is done by default. - - - Guest VM CIDR you specify must be a subset of the network CIDR. - - - Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist - outside the Guest VM CIDR. - You cannot apply IP Reservation if any VM is alloted with an IP address that is - outside the Guest VM CIDR. - - - To reset an existing IP Reservation, specify the new value for the Guest VM CIDR in - the CIDR field. - For example, the following table describes three scenarios of guest network - creation: - - - - - - - - - - Case - CIDR - Network CIDR - Reserved IP Range for Non-&PRODUCT; VMs - Description - - - - - 1 - 10.1.1.0/24 - None - None - No IP Reservation. - - - 2 - 10.1.1.0/26 - 10.1.1.0/24 - 10.1.1.64 to 10.1.1.254 - IP Reservation configured by the UpdateNetwork API with - guestvmcidr=10.1.1.0/26 or enter 10.1.1.0/26 in the CIDR field in the - UI. - - - 3 - 10.1.1.0/24 - None - None - Removing IP Reservation by the UpdateNetwork API with - guestvmcidr=10.1.1.0/24 or enter 10.1.1.0/24 in the CIDR field in the UI. - - - - - - - -
-
- Limitations - - - The IP Reservation is not supported if active IPs are found outside the Guest VM CIDR. - - - - Upgrading network offering which causes a change in CIDR (such as upgrading an - offering with no external devices to one with external devices) IP Reservation becomes - void if any. Reconfigure IP Reservation in the reimplemented network. - - -
-
- Best Practices - Apply IP Reservation to the guest network as soon as the network state changes to - Implemented. If you apply reservation soon after the first guest VM is deployed, conflict is - less likely to occur while applying reservation. -
-
- Reserving an IP Range - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - In the left navigation, choose Network. - - - Click the name of the network you want to modify. - - - In the Details tab, click Edit. - - - - - edit-icon.png: button to edit a network - - - The CIDR field changes to editable one. - - - In CIDR, specify the Guest VM CIDR. - - - Click Apply. - Wait until the Network CIDR and the Reserved IP Range are displayed in the Details - page. - - -
-