Return-Path: X-Original-To: apmail-cloudstack-commits-archive@www.apache.org Delivered-To: apmail-cloudstack-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DE0F11692 for ; Thu, 20 Feb 2014 15:08:47 +0000 (UTC) Received: (qmail 73608 invoked by uid 500); 20 Feb 2014 15:08:03 -0000 Delivered-To: apmail-cloudstack-commits-archive@cloudstack.apache.org Received: (qmail 73413 invoked by uid 500); 20 Feb 2014 15:07:56 -0000 Mailing-List: contact commits-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 commits@cloudstack.apache.org Received: (qmail 73109 invoked by uid 99); 20 Feb 2014 15:07: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, 20 Feb 2014 15:07:50 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id 81AFC9295B5; Thu, 20 Feb 2014 15:07:49 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: sebgoa@apache.org To: commits@cloudstack.apache.org Date: Thu, 20 Feb 2014 15:08:17 -0000 Message-Id: <2e5ef0fc6e6d4ee9b3bd38dbdb05205b@git.apache.org> In-Reply-To: <87c45e9d3dc84b7a9089f31b406a1c54@git.apache.org> References: <87c45e9d3dc84b7a9089f31b406a1c54@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [30/32] refactor docs repo http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-provider.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-provider.xml b/archive/nicira/en-US/plugin-niciranvp-provider.xml new file mode 100644 index 0000000..8694478 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-provider.xml @@ -0,0 +1,36 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ Enabling the service provider + The Nicira NVP provider is disabled by default. Navigate to the "Network Service Providers" configuration of the physical network with the STT isolation type. Navigate to the Nicira NVP provider and press the "Enable Provider" button. + CloudStack 4.0 does not have the UI interface to configure the Nicira NVP plugin. Configuration needs to be done using the API directly. + + + + + + nvp-physical-network-stt.png: a screenshot of an enabled Nicira NVP provider + + + +
\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-revisions.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-revisions.xml b/archive/nicira/en-US/plugin-niciranvp-revisions.xml new file mode 100644 index 0000000..b58d333 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-revisions.xml @@ -0,0 +1,59 @@ + + +%BOOK_ENTITIES; +]> + + + + + Revision History + + + + 0-0 + Wed Oct 03 2012 + + Hugo + Trippaers + hugo@apache.org + + + + Documentation created for 4.0.0-incubating version of the NVP Plugin + + + + + 1-0 + Wed May 22 2013 + + Hugo + Trippaers + hugo@apache.org + + + + Documentation updated for &PRODUCT; 4.1.0 + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-tables.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-tables.xml b/archive/nicira/en-US/plugin-niciranvp-tables.xml new file mode 100644 index 0000000..615f349 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-tables.xml @@ -0,0 +1,106 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ Database tables + The following tables are added to the cloud database for the Nicira NVP Plugin + + nicira_nvp_nic_map + + + + id + auto incrementing id + + + logicalswitch + uuid of the logical switch this port is connected to + + + logicalswitchport + uuid of the logical switch port for this nic + + + nic + the &PRODUCT; uuid for this nic, reference to the nics table + + + +
+ + + external_nicira_nvp_devices + + + + id + auto incrementing id + + + uuid + UUID identifying this device + + + physical_network_id + the physical network this device is configured on + + + provider_name + NiciraNVP + + + device_name + display name for this device + + + host_id + reference to the host table with the device configuration + + + +
+ + + nicira_nvp_router_map + + + + id + auto incrementing id + + + logicalrouter_uuid + uuid of the logical router + + + network_id + id of the network this router is linked to + + + +
+ + + nicira_nvp_router_map is only available in &PRODUCT; 4.1 and above + + +
\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-troubleshooting.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-troubleshooting.xml b/archive/nicira/en-US/plugin-niciranvp-troubleshooting.xml new file mode 100644 index 0000000..02b0655 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-troubleshooting.xml @@ -0,0 +1,28 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + + + Troubleshooting the Nicira NVP Plugin + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-ui.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-ui.xml b/archive/nicira/en-US/plugin-niciranvp-ui.xml new file mode 100644 index 0000000..8b1bbad --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-ui.xml @@ -0,0 +1,26 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ Configuring the Nicira NVP plugin from the UI + In CloudStack 4.1.0-incubating the Nicira NVP plugin and its resources can be configured in the infrastructure tab of the UI. Navigate to the physical network with STT isolation and configure the network elements. The NiciraNvp is listed here. +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-usage.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-usage.xml b/archive/nicira/en-US/plugin-niciranvp-usage.xml new file mode 100644 index 0000000..9f04c38 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-usage.xml @@ -0,0 +1,33 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + + + Configuring the Nicira NVP Plugin + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-uuidreferences.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-uuidreferences.xml b/archive/nicira/en-US/plugin-niciranvp-uuidreferences.xml new file mode 100644 index 0000000..cb5f1ca --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-uuidreferences.xml @@ -0,0 +1,30 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ UUID References + The plugin maintains several references in the &PRODUCT; database to items created on the NVP Controller. + Every guest network that is created will have its broadcast type set to Lswitch and if the network is in state "Implemented", the broadcast URI will have the UUID of the Logical Switch that was created for this network on the NVP Controller. + The Nics that are connected to one of the Logical Switches will have their Logical Switch Port UUID listed in the nicira_nvp_nic_map table + All devices created on the NVP Controller will have a tag set to domain-account of the owner of the network, this string can be used to search for items in the NVP Controller. + +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-vpc.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-vpc.xml b/archive/nicira/en-US/plugin-niciranvp-vpc.xml new file mode 100644 index 0000000..a43c5fa --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-vpc.xml @@ -0,0 +1,30 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + + + Using the Nicira NVP plugin with VPC + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-vpcfeatures.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-vpcfeatures.xml b/archive/nicira/en-US/plugin-niciranvp-vpcfeatures.xml new file mode 100644 index 0000000..a8d8194 --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-vpcfeatures.xml @@ -0,0 +1,28 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ Supported VPC features + The Nicira NVP plugin supports &PRODUCT; VPC to a certain extent. Starting with &PRODUCT; version 4.1 VPCs can be deployed using NVP isolated networks. + It is not possible to use a Nicira NVP Logical Router for as a VPC Router + It is not possible to connect a private gateway using a Nicira NVP Logical Switch +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-vpcnetworkoffering.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-vpcnetworkoffering.xml b/archive/nicira/en-US/plugin-niciranvp-vpcnetworkoffering.xml new file mode 100644 index 0000000..141006e --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-vpcnetworkoffering.xml @@ -0,0 +1,81 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ VPC Network Offerings + The VPC needs specific network offerings with the VPC flag enabled. Otherwise these network offerings are identical to regular network offerings. To allow VPC networks with a Nicira NVP isolated network the offerings need to support the Virtual Networking service with the NiciraNVP provider. + In a typical configuration two network offerings need to be created. One with the loadbalancing service enabled and one without loadbalancing. + + VPC Network Offering with Loadbalancing + + + + Service + Provider + + + + + VPN + VpcVirtualRouter + + + DHCP + VpcVirtualRouter + + + DNS + VpcVirtualRouter + + + Load Balancer + VpcVirtualRouter + + + User Data + VpcVirtualRouter + + + Source NAT + VpcVirtualRouter + + + Static NAT + VpcVirtualRouter + + + Post Forwarding + VpcVirtualRouter + + + NetworkACL + VpcVirtualRouter + + + Virtual Networking + NiciraNVP + + + +
+ +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/en-US/plugin-niciranvp-vpcoffering.xml ---------------------------------------------------------------------- diff --git a/archive/nicira/en-US/plugin-niciranvp-vpcoffering.xml b/archive/nicira/en-US/plugin-niciranvp-vpcoffering.xml new file mode 100644 index 0000000..292621e --- /dev/null +++ b/archive/nicira/en-US/plugin-niciranvp-vpcoffering.xml @@ -0,0 +1,38 @@ + + +%BOOK_ENTITIES; + +%xinclude; +]> + +
+ VPC Offering with Nicira NVP + To allow a VPC to use the Nicira NVP plugin to provision networks, a new VPC offering needs to be created which allows the Virtual Networking service to be implemented by NiciraNVP. + This is not currently possible with the UI. The API does provide the proper calls to create a VPC offering with Virtual Networking enabled. However due to a limitation in the 4.1 API it is not possible to select the provider for this network service. To configure the VPC offering with the NiciraNVP provider edit the database table 'vpc_offering_service_map' and change the provider to NiciraNvp for the service 'Connectivity' + It is also possible to update the default VPC offering by adding a row to the + 'vpc_offering_service_map' with service 'Connectivity' and provider 'NiciraNvp' + + + + + + nvp-physical-network-stt.png: a screenshot of the mysql table. + + + When creating a new VPC offering please note that the UI does not allow you to select a VPC offering yet. The VPC needs to be created using the API with the offering UUID. +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/nicira/publican.cfg ---------------------------------------------------------------------- diff --git a/archive/nicira/publican.cfg b/archive/nicira/publican.cfg new file mode 100644 index 0000000..2e3696d --- /dev/null +++ b/archive/nicira/publican.cfg @@ -0,0 +1,28 @@ +# Publican configuration file for CloudStack Complete Documentation Set +# Contains all technical docs except release notes +# Config::Simple 4.58 +# Tue May 29 00:57:27 2012 +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information# +# regarding copyright ownership. The ASF licenses this file +# 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 +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +xml_lang: en-US +type: Book +docname: CloudStack_Nicira_NVP_Guide +brand: cloudstack +chunk_first: 1 +chunk_section_depth: 1 +condition: install http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Author_Group.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Author_Group.xml b/archive/qig/en-US/Author_Group.xml new file mode 100644 index 0000000..432ef6f --- /dev/null +++ b/archive/qig/en-US/Author_Group.xml @@ -0,0 +1,32 @@ + + +%BOOK_ENTITIES; +]> + + + + + + + Apache + CloudStack + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Book_Info.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Book_Info.xml b/archive/qig/en-US/Book_Info.xml new file mode 100644 index 0000000..98cbcb4 --- /dev/null +++ b/archive/qig/en-US/Book_Info.xml @@ -0,0 +1,52 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Quick Install Guide + Prescriptive instructions for deploying Apache CloudStack + Apache CloudStack + 4.2.0 + 0 + 0 + + + This guide is designed to provide a strict environment to guarantee + a higher degree of success in initial deployments of Apache CloudStack. + All of the elements of the environment will be provided to you. + Apache CloudStack is capable of much more complex configurations, + but they are beyond the scope of this document. + + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Chapter.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Chapter.xml b/archive/qig/en-US/Chapter.xml new file mode 100644 index 0000000..4adf63c --- /dev/null +++ b/archive/qig/en-US/Chapter.xml @@ -0,0 +1,53 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Test Chapter + + This is a test paragraph + +
+ Test Section 1 + + This is a test paragraph in a section + +
+ +
+ Test Section 2 + + This is a test paragraph in Section 2 + + + + listitem text + + + + +
+ +
+ http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Environment.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Environment.xml b/archive/qig/en-US/Environment.xml new file mode 100644 index 0000000..e48b405 --- /dev/null +++ b/archive/qig/en-US/Environment.xml @@ -0,0 +1,258 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Environment + + Before you begin, you need to prepare the environment before you install CloudStack. + We will go over the steps to prepare now. + +
+ Operating System + + Using the CentOS 6.4 x86_64 minimal install ISO, you'll need to install CentOS + on your hardware. The defaults will generally be acceptable for this installation. + + + Once this installation is complete, you'll want to connect to your freshly + installed machine via SSH as the root user. Note that you should not allow root + logins in a production environment, so be sure to turn off remote logins once you + have finished the installation and configuration. + +
+ Configuring the network + + By default the network will not come up on your hardware and you + will need to configure it to work in your environment. Since we + specified that there will be no DHCP server in this environment + we will be manually configuring your network interface. We will + assume, for the purposes of this exercise, that eth0 is the only network + interface that will be connected and used. + + + Connecting via the console you should login as root. Check the + file /etc/sysconfig/network-scripts/ifcfg-eth0, + it will look like this by default: + +DEVICE="eth0" +HWADDR="52:54:00:B9:A6:C0" +NM_CONTROLLED="yes" +ONBOOT="no" + + + + Unfortunately, this configuration will not permit you to connect to the network, + and is also unsuitable for our purposes with CloudStack. We want to + configure that file so that it specifies the IP address, netmask, etc., as shown + in the following example: + + + Hardware Addresses + You should not use the hardware address (aka MAC address) from our example + for your configuration. It is network interface specific, so you should keep the + address already provided in the HWADDR directive. + + + +DEVICE=eth0 +HWADDR=52:54:00:B9:A6:C0 +NM_CONTROLLED=no +ONBOOT=yes +BOOTPROTO=none +IPADDR=172.16.10.2 +NETMASK=255.255.255.0 +GATEWAY=172.16.10.1 +DNS1=8.8.8.8 +DNS2=8.8.4.4 + + + IP Addressing + Throughout this document we are assuming that you will + have a /24 network for your CloudStack implementation. This can be any + RFC 1918 network. However, we are assuming that you will match the + machine address that we are using. Thus we may use + 172.16.10.2 and because + you might be using the 192.168.55.0/24 network you would use + 192.168.55.2 + + + Now that we have the configuration files properly set up, we need to run a + few commands to start up the network + # chkconfig network on + # service network start +
+
+ Hostname + + Cloudstack requires that the hostname be properly set. If you used the default + options in the installation, then your hostname is currently set to + localhost.localdomain. To test this we will run: + # hostname --fqdn + At this point it will likely return: + localhost + To rectify this situation - we'll set the hostname by editing the + /etc/hosts file so that it follows a similar format to this example: +127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 +::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 +172.16.10.2 srvr1.cloud.priv + + + After you've modified that file, go ahead and restart the network using: +# service network restart + Now recheck with the hostname --fqdn command and ensure that it returns + a FQDN response +
+
+ SELinux + At the moment, for CloudStack to work properly SELinux must be + set to permissive. We want to both configure this for future boots and modify it + in the current running system. + + To configure SELinux to be permissive in the running system we need to run + the following command: + # setenforce 0 + + To ensure that it remains in that state we need to configure the file + /etc/selinux/config to reflect the permissive state, + as shown in this example: + + +# This file controls the state of SELinux on the system. +# SELINUX= can take one of these three values: +# enforcing - SELinux security policy is enforced. +# permissive - SELinux prints warnings instead of enforcing. +# disabled - No SELinux policy is loaded. +SELINUX=permissive +# SELINUXTYPE= can take one of these two values: +# targeted - Targeted processes are protected, +# mls - Multi Level Security protection. +SELINUXTYPE=targeted + + +
+
+ NTP + NTP configuration is a necessity for keeping all of the clocks in your cloud + servers in sync. However, NTP is not installed by default. So we'll install and + and configure NTP at this stage. Installation is accomplished as follows: + + # yum -y install ntp + The actual default configuration is fine for our purposes, so we merely need to + enable it and set it to start on boot as follows: + # chkconfig ntpd on + # service ntpd start +
+
+ Configuring the CloudStack Package Repository + + We need to configure the machine to use a CloudStack package repository. + + The below repository is not an official Apache CloudStack project repository + + The Apache CloudStack official releases are source code. As such there are no + 'official' binaries available. The full installation guide describes how to take + the source release and generate RPMs and and yum repository. This guide attempts + to keep things as simple as possible, and thus we are using one of the + community-provided yum repositories. + + + + To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo and insert the following information. + +[cloudstack] +name=cloudstack +baseurl=http://cloudstack.apt-get.eu/rhel/4.1/ +enabled=1 +gpgcheck=0 + +
+
+
+ NFS + + Our configuration is going to use NFS for both primary and secondary + storage. We are going to go ahead and setup two NFS shares for those + purposes. We'll start out by installing + nfs-utils. + + # yum install nfs-utils + + We now need to configure NFS to serve up two different shares. This is handled comparatively easily + in the /etc/exports file. You should ensure that it has the following content: + + +/secondary *(rw,async,no_root_squash) +/primary *(rw,async,no_root_squash) + + + You will note that we specified two directories that don't exist (yet) on the system. + We'll go ahead and create those directories and set permissions appropriately on them with the following commands: + + +# mkdir /primary +# mkdir /secondary + + CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. + In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf + is uncommented and set as follows: + Domain = cloud.priv + Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs + +LOCKD_TCPPORT=32803 +LOCKD_UDPPORT=32769 +MOUNTD_PORT=892 +RQUOTAD_PORT=875 +STATD_PORT=662 +STATD_OUTGOING_PORT=2020 + + Now we need to configure the firewall to permit incoming NFS connections. + Edit the file /etc/sysconfig/iptables + + +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 111 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 111 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 2049 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 32803 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 32769 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 892 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 892 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 875 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 875 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 662 -j ACCEPT +-A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 662 -j ACCEPT + + Now you can restart the iptables service with the following command: + + # service iptables restart + We now need to configure nfs service to start on boot and actually start it on the host by + executing the following commands: + +# service rpcbind start +# service nfs start +# chkconfig rpcbind on +# chkconfig nfs on + +
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Management.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Management.xml b/archive/qig/en-US/Management.xml new file mode 100644 index 0000000..8c6040f --- /dev/null +++ b/archive/qig/en-US/Management.xml @@ -0,0 +1,99 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Installation of the management server + + Now it is time to start installing CloudStack's management server + and some of the related components. + +
+ Database Installation and Configuration + + We'll start out by installing MySQL and configuring + some options to ensure CloudStack runs well. + + + To install MySQL run the following command: + # yum -y install mysql-server + + With MySQL installed we need to make + a few configuration changes to /etc/my.cnf. + Specifically we need to add the following options to the [mysqld] section: + +innodb_rollback_on_timeout=1 +innodb_lock_wait_timeout=600 +max_connections=350 +log-bin=mysql-bin +binlog-format = 'ROW' + + + + Now that MySQL is properly configured we can + start it and configure it to start on boot as follows: + +# service mysqld start +# chkconfig mysqld on + + + +
+ +
+ Installation + We are now going to install the management server. We do that by executing the following command: + # yum -y install cloud-client + + With the application itself installed we can now setup the database, we'll do that with the following command + and options: + + # cloudstack-setup-databases cloud:password@localhost --deploy-as=root + When this process is finished, you should see a message like "CloudStack has successfully initialized the database." + + Now that the database has been created, we can take the final step in setting up the management server by issuing the following command: + # cloudstack-setup-management +
+
+ System Template Setup + CloudStack uses a number of system VMs to provide functionality for + accessing the console of virtual machines, providing various networking + services, and managing various aspects of storage. This step will + acquire those system images ready for deployment when we bootstrap + your cloud. + + + Now we need to download the system VM template and deploy that to the + share we just mounted. The management server includes a script to properly + manipulate the system VMs images. + + # /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F + + + That concludes our setup of the management server. We still need to + configure CloudStack, but we will do that after we get our hypervisor + set up. + +
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Overview.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Overview.xml b/archive/qig/en-US/Overview.xml new file mode 100644 index 0000000..31915f5 --- /dev/null +++ b/archive/qig/en-US/Overview.xml @@ -0,0 +1,93 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Overview + + Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, + and by definition they have a plethora of options, which often lead to confusion + for even experienced admins who are newcomers to building cloud platforms. + The goal for this runbook is to provide a straightforward set of instructions + to get you up and running with CloudStack with a minimum amount of trouble. + +
+ What exactly are we building? + + This runbook will focus on building a CloudStack cloud using KVM with + CentOS 6.4 with NFS storage on a flat layer-2 network utilizing + layer-3 network isolation (aka Security Groups), and doing it all + on a single piece of hardware. + + + KVM, or Kernel-based Virtual Machine is a virtualization technology + for the Linux kernel. KVM supports native virtualization atop + processors with hardware virtualization extensions. + + + Security Groups act as distributed firewalls that control access + to a group of virtual machines. + +
+
+ High level overview of the process + + Before we actually get to installing CloudStack, we'll start with + installing our base operating system, and then configuring that to act + as an NFS server for several types of storage. We'll install the + management server, download the systemVMs, and finally install the agent + software. Finally we'll spend a good deal of time configuring the entire + cloud in the CloudStack web interface. + +
+
+ Prerequisites + + To complete this runbook you'll need the following items: + + + + At least one computer which supports hardware virtualization. + + + + + The + + CentOS 6.4 x86_64 minimal install CD + + + + + + A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and + none of the computers running CloudStack will have a dynamic address. Again this is done for + the sake of simplicity. + + + + +
+ +
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Preface.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Preface.xml b/archive/qig/en-US/Preface.xml new file mode 100644 index 0000000..d6ba80e --- /dev/null +++ b/archive/qig/en-US/Preface.xml @@ -0,0 +1,33 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Preface + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/Revision_History.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/Revision_History.xml b/archive/qig/en-US/Revision_History.xml new file mode 100644 index 0000000..1ff4d77 --- /dev/null +++ b/archive/qig/en-US/Revision_History.xml @@ -0,0 +1,42 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Revision History + + + + 0-0 + Fri Jun 28 2013 + + + Initial creation of book by publican + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/config.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/config.xml b/archive/qig/en-US/config.xml new file mode 100644 index 0000000..7ff7a72 --- /dev/null +++ b/archive/qig/en-US/config.xml @@ -0,0 +1,177 @@ + + +%BOOK_ENTITIES; +]> + + + + + + Configuration + + As we noted before we will be using security groups to provide isolation + and by default that implies that we'll be using a flat layer-2 network. + It also means that the simplicity of our setup means that we can use the + quick installer. + +
+ UI Access + + To get access to CloudStack's web interface, merely point your + browser to http://172.16.10.2:8080/client + The default username is 'admin', and the default password is 'password'. + You should see a splash screen that allows you to choose several options + for setting up CloudStack. You should choose the + option. + + + You should now see a prompt requiring you to change the password for + the admin user. Please do so. + +
+
+ Setting up a Zone + + A zone is the largest organization entity in CloudStack - and we'll be creating one, this + should be the screen that you see in front of you now. And for us there are 5 pieces of + information that we need. + + + Name - we will set this to the ever-descriptive 'Zone1' for our cloud. + + + Public DNS 1 - we will set this to '8.8.8.8' for our cloud. + + + Public DNS 2 - we will set this to '8.8.4.4' for our cloud. + + + Internal DNS1 - we will also set this to '8.8.8.8' for our cloud. + + + Internal DNS2 - we will also set this to '8.8.8.4' for our cloud. + + + + + Notes about DNS settings + + CloudStack distinguishes between internal and public DNS. Internal + DNS is assumed to be capable of resolving internal-only + hostnames, such as your NFS server’s DNS name. Public DNS is + provided to the guest VMs to resolve public IP addresses. You can + enter the same DNS server for both types, but if you do so, you + must make sure that both internal and public IP addresses can + route to the DNS server. In our specific case we will not use any + names for resources internally, and we have indeed them set to look + to the same external resource so as to not add a namerserver setup + to our list of requirements. + + +
+
+ Pod Configuration + Now that we've added a Zone, the next step that comes up is a prompt + for information regading a pod. Which is looking for 4 items. + + + Name - We'll use Pod1 for our cloud. + + + Gateway - We'll use 172.16.10.1 as our gateway + + + Netmask - We'll use 255.255.255.0 + + + Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20 + + + Guest gateway - We'll use 172.16.10.1 + + + Guest netmask - We'll use 255.255.255.0 + + + Guest start/end IP - We'll use 172.16.10.30-172.16.10.200 + + + +
+
+ Cluster + Now that we've added a Zone, we need only add a few more items for configuring the cluster. + + + Name - We'll use Cluster1 + + + Hypervisor - Choose KVM + + + + You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed. + + + Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server. + + + Username - we'll use 'root' + + + Password - enter the operating system password for the root user + + + +
+ Primary Storage + With your cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: + + + Name - We'll use 'Primary1' + + + Server - We'll be using the IP address 172.16.10.2 + + + Path - Well define /primary as the path we are using + + + +
+
+ Secondary Storage + If this is a new zone, you'll be prompted for secondary storage information - populate it as follows: + + + NFS server - We'll use the IP address 172.16.10.2 + + + Path - We'll use /secondary + + + + Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize. +
+
+ + +
+ http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/kvm.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/kvm.xml b/archive/qig/en-US/kvm.xml new file mode 100644 index 0000000..91ed9d5 --- /dev/null +++ b/archive/qig/en-US/kvm.xml @@ -0,0 +1,142 @@ + + +%BOOK_ENTITIES; +]> + + + + + + KVM Setup and installation + + KVM is the hypervisor we'll be using - we will recover the initial setup + which has already been done on the hypervisor host and cover installation + of the agent software, you can use the same steps to add additional KVM + nodes to your CloudStack environment. + +
+ Prerequisites + + We explicitly are using the management server as a compute node as well, + which means that we have already performed many of the prerequisite steps + when setting up the management server, but we will list them here for + clarity. Those steps are: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + You shouldn't need to do that for the management server, of course, but + any additional hosts will need for you to complete the above steps. + +
+ +
+ Installation + Installation of the KVM agent is trivial with just a single command, but afterwards we'll need to configure a few things. + # yum -y install cloud-agent +
+ KVM Configuration + We have two different parts of KVM to configure, libvirt, and QEMU. +
+ QEMU Configuration + + KVM configuration is relatively simple at only a single item. We need to + edit the QEMU VNC configuration. This is done by editing + /etc/libvirt/qemu.conf and ensuring the following + line is present and uncommented. + vnc_listen=0.0.0.0 + +
+
+ Libvirt Configuration + + CloudStack uses libvirt for managing virtual machines. Therefore it + is vital that libvirt is configured correctly. Libvirt is a dependency + of cloud-agent and should already be installed. + + + + In order to have live migration working libvirt has to listen + for unsecured TCP connections. We also need to turn off libvirts + attempt to use Multicast DNS advertising. Both of these settings + are in /etc/libvirt/libvirtd.conf + + Set the following paramaters: + listen_tls = 0 + listen_tcp = 1 + tcp_port = "16059" + auth_tcp = "none" + mdns_adv = 0 + + + Turning on "listen_tcp" in libvirtd.conf is not enough, we have to change the parameters as well: + On RHEL or CentOS modify /etc/sysconfig/libvirtd: + Uncomment the following line: + #LIBVIRTD_ARGS="--listen" + On Ubuntu: modify /etc/init/libvirt-bin.conf + Change the following line (at the end of the file): + exec /usr/sbin/libvirtd -d + to (just add -l) + exec /usr/sbin/libvirtd -d -l + + + Restart libvirt + In RHEL or CentOS: + $ service libvirtd restart + In Ubuntu: + $ service libvirt-bin restart + + +
+
+ KVM configuration complete + + That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI + for the actual configuration of our cloud. + +
+
+
+
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/qig.ent ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/qig.ent b/archive/qig/en-US/qig.ent new file mode 100644 index 0000000..3b1649a --- /dev/null +++ b/archive/qig/en-US/qig.ent @@ -0,0 +1,22 @@ + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/en-US/qig.xml ---------------------------------------------------------------------- diff --git a/archive/qig/en-US/qig.xml b/archive/qig/en-US/qig.xml new file mode 100644 index 0000000..00dd2e4 --- /dev/null +++ b/archive/qig/en-US/qig.xml @@ -0,0 +1,36 @@ + + +%BOOK_ENTITIES; +]> + + + + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/qig/publican.cfg ---------------------------------------------------------------------- diff --git a/archive/qig/publican.cfg b/archive/qig/publican.cfg new file mode 100644 index 0000000..368ba5d --- /dev/null +++ b/archive/qig/publican.cfg @@ -0,0 +1,28 @@ +# Publican configuration file for CloudStack Complete Documentation Set +# Contains all technical docs except release notes +# Config::Simple 4.58 +# Tue May 29 00:57:27 2012 +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information# +# regarding copyright ownership. The ASF licenses this file +# 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 +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +xml_lang: en-US +type: Book +docname: qig +brand: cloudstack +chunk_first: 1 +chunk_section_depth: 1 +condition: install http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/vxlan/en-US/Author_Group.xml ---------------------------------------------------------------------- diff --git a/archive/vxlan/en-US/Author_Group.xml b/archive/vxlan/en-US/Author_Group.xml new file mode 100644 index 0000000..1184c50 --- /dev/null +++ b/archive/vxlan/en-US/Author_Group.xml @@ -0,0 +1,31 @@ + + +%BOOK_ENTITIES; +]> + + + + + + + Apache + CloudStack + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/vxlan/en-US/Book_Info.xml ---------------------------------------------------------------------- diff --git a/archive/vxlan/en-US/Book_Info.xml b/archive/vxlan/en-US/Book_Info.xml new file mode 100644 index 0000000..e063e23 --- /dev/null +++ b/archive/vxlan/en-US/Book_Info.xml @@ -0,0 +1,47 @@ + + +%BOOK_ENTITIES; +]> + + + + + + &PRODUCT; Guide + Revised August 9, 2012 10:48 pm Pacific + Apache CloudStack + 4.3.0 + 1 + + + + Complete technical documentation of &PRODUCT;. + + + + + + + + + + + + http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/bcf67dd6/archive/vxlan/en-US/CloudStack_VXLAN_Guide.ent ---------------------------------------------------------------------- diff --git a/archive/vxlan/en-US/CloudStack_VXLAN_Guide.ent b/archive/vxlan/en-US/CloudStack_VXLAN_Guide.ent new file mode 100644 index 0000000..f31c407 --- /dev/null +++ b/archive/vxlan/en-US/CloudStack_VXLAN_Guide.ent @@ -0,0 +1,22 @@ + + + + + +