Configuring Network Access Control List

Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 78832 invoked by uid 99); 1 Oct 2015 14:04:12 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2015 14:04:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 9383CE154B; Thu, 1 Oct 2015 14:04:12 +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, 01 Oct 2015 14:04:48 -0000 Message-Id: <5335df759e2044379591c4e837e37330@git.apache.org> In-Reply-To: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> References: <70dce7e46df64989b9cdbc3fddef9604@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [38/51] [partial] cloudstack-docs git commit: Remove all old docbook files http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-acl.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-acl.xml b/en-US/configure-acl.xml deleted file mode 100644 index 3ac2b74..0000000 --- a/en-US/configure-acl.xml +++ /dev/null @@ -1,287 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Configuring Network Access Control List - Define Network Access Control List (ACL) on the VPC virtual router to control incoming - (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By - default, all incoming traffic to the guest networks is blocked and all outgoing traffic from - guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing - traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must - create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL - service is supported. -

- About Network ACL Lists - In &PRODUCT; terminology, Network ACL is a group of Network ACL items. Network ACL items - are nothing but numbered rules that are evaluated in order, starting with the lowest numbered - rule. These rules determine whether traffic is allowed in or out of any tier associated with - the network ACL. You need to add the Network ACL items to the Network ACL, then associate the - Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple - VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier - can be associated with only one ACL. - The default Network ACL is used when no ACL is associated. Default behavior is all the - incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network - ACL cannot be removed or modified. Contents of the default Network ACL is: - - - - - - - - - - Rule - Protocol - Traffic type - Action - CIDR - - - - - 1 - All - Ingress - Deny - 0.0.0.0/0 - - - 2 - All - Egress - Deny - 0.0.0.0/0 - - - - -

- Creating ACL Lists - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - In the left navigation, choose Network. - - - In the Select view, select VPC. - All the VPCs that you have created for the account is listed in the page. - - - Click the Configure button of the VPC. - For each tier, the following options are displayed: - - - Internal LB - - - Public LB IP - - - Static NAT - - - Virtual Machines - - - CIDR - - - The following router information is displayed: - - - Private Gateways - - - Public IP Addresses - - - Site-to-Site VPNs - - - Network ACL Lists - - - - - Select Network ACL Lists. - The following default rules are displayed in the Network ACLs page: default_allow, - default_deny. - - - Click Add ACL Lists, and specify the following: - - - ACL List Name: A name for the ACL list. - - - Description: A short description of the ACL list - that can be displayed to users. - - - - -

- Creating an ACL Rule - - - Log in to the &PRODUCT; UI as an administrator or end user. - - - In the left navigation, choose Network. - - - In the Select view, select VPC. - All the VPCs that you have created for the account is listed in the page. - - - Click the Configure button of the VPC. - - - Select Network ACL Lists. - In addition to the custom ACL lists you have created, the following default rules are - displayed in the Network ACLs page: default_allow, default_deny. - - - Select the desired ACL list. - - - Select the ACL List Rules tab. - To add an ACL rule, fill in the following fields to specify what kind of network - traffic is allowed in the VPC. - - - Rule Number: The order in which the rules are - evaluated. - - - CIDR: The CIDR acts as the Source CIDR for the - Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from - or to the IP addresses within a particular address block, enter a CIDR or a - comma-separated list of CIDRs. The CIDR is the base IP address of the incoming - traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0. - - - Action: What action to be taken. Allow traffic or - block. - - - Protocol: The networking protocol that sources - use to send traffic to the tier. The TCP and UDP protocols are typically used for data - exchange and end-user communications. The ICMP protocol is typically used to send - error messages or network monitoring data. All supports all the traffic. Other option - is Protocol Number. - - - Start Port, End - Port (TCP, UDP only): A range of listening ports that are the destination - for the incoming traffic. If you are opening a single port, use the same number in - both fields. - - - Protocol Number: The protocol number associated - with IPv4 or IPv6. For more information, see Protocol - Numbers. - - - ICMP Type, ICMP - Code (ICMP only): The type of message and error code that will be - sent. - - - Traffic Type: The type of traffic: Incoming or - outgoing. - - - - - Click Add. The ACL rule is added. - You can edit the tags assigned to the ACL rules and delete the ACL rules you have - created. Click the appropriate button in the Details tab. - - -

- Creating a Tier with Custom ACL List - - - Create a VPC. - - - Create a custom ACL list. - - - Add ACL rules to the ACL list. - - - Create a tier in the VPC. - Select the desired ACL list while creating a tier. - - - Click OK. - - -

- Assigning a Custom ACL List to a Tier - - - Create a VPC. - - - Create a tier in the VPC. - - - Associate the tier with the default ACL rule. - - - Create a custom ACL list. - - - Add ACL rules to the ACL list. - - - Select the tier for which you want to assign the custom ACL. - - - Click the Replace ACL List icon. - - - - - replace-acl-icon.png: button to replace an ACL list - - - The Replace ACL List dialog is displayed. - - - Select the desired ACL list. - - - Click OK. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-guest-traffic-in-advanced-zone.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-guest-traffic-in-advanced-zone.xml b/en-US/configure-guest-traffic-in-advanced-zone.xml deleted file mode 100644 index fb66850..0000000 --- a/en-US/configure-guest-traffic-in-advanced-zone.xml +++ /dev/null @@ -1,79 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Configure Guest Traffic in an Advanced Zone - These steps assume you have already logged in to the &PRODUCT; UI. To configure the base - guest network: - - - In the left navigation, choose Infrastructure. On Zones, click View More, then click the - zone to which you want to add a network. - - - Click the Network tab. - - - Click Add guest network. - The Add guest network window is displayed: - - - - - - networksetupzone.png: Depicts network setup in a single zone - - - - - Provide the following information: - - - Name. The name of the network. This will be - user-visible - - - Display Text: The description of the network. This - will be user-visible - - - Zone: The zone in which you are configuring the - guest network. - - - Network offering: If the administrator has - configured multiple network offerings, select the one you want to use for this - network - - - Guest Gateway: The gateway that the guests should - use - - - Guest Netmask: The netmask in use on the subnet the - guests will use - - - - - Click OK. - - -

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-package-repository.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-package-repository.xml b/en-US/configure-package-repository.xml deleted file mode 100644 index bf4ac47..0000000 --- a/en-US/configure-package-repository.xml +++ /dev/null @@ -1,69 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Configure package repository - &PRODUCT; is only distributed from source from the official mirrors. - However, members of the CloudStack community may build convenience binaries - so that users can install Apache CloudStack without needing to build from - source. - - - If you didn't follow the steps to build your own packages from source - in the sections for or - you may find pre-built - DEB and RPM packages for your convenience linked from the - downloads - page. - - - These repositories contain both the Management Server and KVM Hypervisor packages. - -

- DEB package repository - You can add a DEB package repository to your apt sources with the following commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are being built at this time. - Use your preferred editor and open (or create) /etc/apt/sources.list.d/cloudstack.list. Add the community provided repository to the file: -deb http://cloudstack.apt-get.eu/ubuntu precise 4.2 - We now have to add the public key to the trusted keys. - $ wget -O - http://cloudstack.apt-get.eu/release.asc|apt-key add - - Now update your local apt cache. - $ apt-get update - Your DEB package repository should now be configured and ready for use. -

- RPM package repository - There is a RPM package repository for &PRODUCT; so you can easily install on RHEL based platforms. - If you're using an RPM-based system, you'll want to add the Yum repository so that you can install &PRODUCT; with Yum. - Yum repository information is found under /etc/yum.repos.d. You'll see several .repo files in this directory, each one denoting a specific repository. - To add the &PRODUCT; repository, create /etc/yum.repos.d/cloudstack.repo and insert the following information. - -[cloudstack] -name=cloudstack -baseurl=http://cloudstack.apt-get.eu/rhel/4.2/ -enabled=1 -gpgcheck=0 - - Now you should be able to install CloudStack using Yum. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-public-traffic-in-an-advanced-zone.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-public-traffic-in-an-advanced-zone.xml b/en-US/configure-public-traffic-in-an-advanced-zone.xml deleted file mode 100644 index 7a61cd3..0000000 --- a/en-US/configure-public-traffic-in-an-advanced-zone.xml +++ /dev/null @@ -1,25 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Configure Public Traffic in an Advanced Zone - In a zone that uses advanced networking, you need to configure at least one range of IP - addresses for Internet traffic. -

\ No newline at end of file http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-snmp-rhel.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-snmp-rhel.xml b/en-US/configure-snmp-rhel.xml deleted file mode 100644 index bd227ff..0000000 --- a/en-US/configure-snmp-rhel.xml +++ /dev/null @@ -1,86 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Configuring SNMP Community String on a RHEL Server - The SNMP Community string is similar to a user id or password that provides access to a - network device, such as router. This string is sent along with all SNMP requests. If the - community string is correct, the device responds with the requested information. If the - community string is incorrect, the device discards the request and does not respond. - The NetScaler device uses SNMP to communicate with the VMs. You must install SNMP and - configure SNMP Community string for a secure communication between the NetScaler device and the - RHEL machine. - - - Ensure that you installed SNMP on RedHat. If not, run the following command: - yum install net-snmp-utils - - - Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler - device. - - - Map the community name into a security name (local and mynetwork, depending on where - the request is coming from): - - Use a strong password instead of public when you edit the following table. - - # sec.name source community -com2sec local localhost public -com2sec mynetwork 0.0.0.0 public - - Setting to 0.0.0.0 allows all IPs to poll the NetScaler server. - - - - Map the security names into group names: - # group.name sec.model sec.name -group MyRWGroup v1 local -group MyRWGroup v2c local -group MyROGroup v1 mynetwork -group MyROGroup v2c mynetwork - - - Create a view to allow the groups to have the permission to: - incl/excl subtree mask view all included .1 - - - Grant access with different write permissions to the two groups to the view you - created. - # context sec.model sec.level prefix read write notif - access MyROGroup "" any noauth exact all none none - access MyRWGroup "" any noauth exact all all all - - - - - Unblock SNMP in iptables. - iptables -A INPUT -p udp --dport 161 -j ACCEPT - - - Start the SNMP service: - service snmpd start - - - Ensure that the SNMP service is started automatically during the system startup: - chkconfig snmpd on - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-usage-server.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-usage-server.xml b/en-US/configure-usage-server.xml deleted file mode 100644 index 83bed07..0000000 --- a/en-US/configure-usage-server.xml +++ /dev/null @@ -1,104 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Configuring the Usage Server - To configure the usage server: - - Be sure the Usage Server has been installed. This requires extra steps beyond just installing the &PRODUCT; software. See Installing the Usage Server (Optional) in the Advanced Installation Guide. - Log in to the &PRODUCT; UI as administrator. - Click Global Settings. - In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters. - In Actions, click the Edit icon. - Type the desired value and click the Save icon. - Restart the Management Server (as usual with any global configuration change) and also the Usage Server: - # service cloudstack-management restart -# service cloudstack-usage restart - - - The following table shows the global configuration settings that control the behavior of the Usage Server. - - - - - Parameter Name - Description - - - - - enable.usage.server - Whether the Usage Server is active. - - - usage.aggregation.timezone - Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT: - usage.stats.job.exec.time = 00:15 -usage.execution.timezone = PST -usage.aggregation.timezone = GMT - - Valid values for the time zone are specified in - Default: GMT - - - - usage.execution.timezone - The time zone of usage.stats.job.exec.time. Valid values for the time zone are specified in - Default: The time zone of the management server. - - - - usage.sanity.check.interval - The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range. If any issue is found, the alert ALERT_TYPE_USAGE_SANITY_RESULT = 21 is sent. - - - usage.stats.job.aggregation.range - The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run. - There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. &PRODUCT; assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. &PRODUCT; assumes this “midnight to midnight” is relative to the usage.execution.timezone. - Default: 1440 - - - - usage.stats.job.exec.time - The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter “10:30”. - If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time. - Default: 00:15. - - - - - - For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings: - - enable.usage.server = true - usage.execution.timezone = America/New_York - usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time. - usage.stats.job.aggregation.range = 1440 - - With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New_York) time zone. - Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage - Server will ignore the data between midnight and 2 AM. That data will be included in the - next day's run. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-virtual-router.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-virtual-router.xml b/en-US/configure-virtual-router.xml deleted file mode 100644 index 8740c0c..0000000 --- a/en-US/configure-virtual-router.xml +++ /dev/null @@ -1,36 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Configuring the Virtual Router - You can set the following: - - IP range - Supported network services - Default domain name for the network serviced by the virtual router - Gateway IP address - How often &PRODUCT; fetches network usage statistics from &PRODUCT; virtual routers. If you want to collect traffic metering data from the virtual router, set the global configuration parameter router.stats.interval. If you are not using the virtual router to gather network usage statistics, set it to 0. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-vpc.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-vpc.xml b/en-US/configure-vpc.xml deleted file mode 100644 index e0e2ee9..0000000 --- a/en-US/configure-vpc.xml +++ /dev/null @@ -1,37 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Configuring a Virtual Private Cloud - - - - - - - - - - - - - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-vpn-vpc.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-vpn-vpc.xml b/en-US/configure-vpn-vpc.xml deleted file mode 100644 index fecb5b5..0000000 --- a/en-US/configure-vpn-vpc.xml +++ /dev/null @@ -1,156 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Configuring Remote Access VPN in VPC - On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access - VMs present in the VPC by using the Remote VPN connection. The VPN client can be present - anywhere except inside the VPC on which the user enabled the Remote Access VPN service. -

- Enabling or Disabling Remote Access VPN for a VPC - - - Log in as a user or administrator to the &PRODUCT; UI. - - - In the left navigation, click Network. - - - In the Select view, select VPC. - All the VPCs that you have created for the account is listed in the page. - - - Click the Configure button of the VPC. - For each tier, the following options are displayed: - - - Internal LB - - - Public LB IP - - - Static NAT - - - Virtual Machines - - - CIDR - - - The following router information is displayed: - - - Private Gateways - - - Public IP Addresses - - - Site-to-Site VPNs - - - Network ACL Lists - - - - - In the Router node, select Public IP Addresses. - The IP Addresses page is displayed. - - - Click Source NAT IP address. - - - Click the Enable VPN button. - - - - - vpn-icon.png: button to enable VPN - - - Click OK to confirm. The IPsec key is displayed in a pop-up window. - To disable, click the Disable VPN button. - - - - - disable-vpnvp.png: button to disable VPN - - - - - Now, continue with . - - -

- Adding Remote Access VPN Users - - - Click the Source NAT IP. - - - Select the VPN tab. - - - Add the username and the corresponding password of the user you wanted to add. - - - Click Add. - - - Repeat the same steps to add the VPN users. - - -

- Removing Remote Access VPN Users - - - Click the Source NAT IP. - - - Select the VPN tab. - - - Locate the user you want to remove. - - - Click Delete User. - - - - - remove-user.png: button to remove a VPN user - - - - - Repeat the same steps to remove the VPN users. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-vpn.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-vpn.xml b/en-US/configure-vpn.xml deleted file mode 100644 index f389f30..0000000 --- a/en-US/configure-vpn.xml +++ /dev/null @@ -1,53 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Configuring Remote Access VPN - To set up VPN for the cloud: - - Log in to the &PRODUCT; UI as an administrator or end user. - In the left navigation, click Global Settings. - Set the following global configuration parameters. - - remote.access.vpn.client.ip.range – The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server. - remote.access.vpn.psk.length – Length of the IPSec key. - remote.access.vpn.user.limit – Maximum number of VPN users per account. - - To enable VPN for a particular network: - - Log in as a user or administrator to the &PRODUCT; UI. - In the left navigation, click Network. - Click the name of the network you want to work with. - Click View IP Addresses. - Click one of the displayed IP address names. - Click the Enable VPN button. - - - - - AttachDiskButton.png: button to attach a volume - - - The IPsec key is displayed in a popup window. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configure-xenserver-dom0-memory.xml ---------------------------------------------------------------------- diff --git a/en-US/configure-xenserver-dom0-memory.xml b/en-US/configure-xenserver-dom0-memory.xml deleted file mode 100644 index 0a02d3e..0000000 --- a/en-US/configure-xenserver-dom0-memory.xml +++ /dev/null @@ -1,29 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Configure XenServer dom0 Memory - Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see Citrix Knowledgebase Article.The article refers to XenServer 5.6, but the same information applies to XenServer 6 -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/configuring-projects.xml ---------------------------------------------------------------------- diff --git a/en-US/configuring-projects.xml b/en-US/configuring-projects.xml deleted file mode 100644 index af1fc53..0000000 --- a/en-US/configuring-projects.xml +++ /dev/null @@ -1,32 +0,0 @@ - - - -%BOOK_ENTITIES; -]> -

- Configuring Projects - Before &PRODUCT; users start using projects, the &PRODUCT; administrator must set - up various systems to support them, including membership invitations, limits on project - resources, and controls on who can create projects. - - - -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/console-proxy.xml ---------------------------------------------------------------------- diff --git a/en-US/console-proxy.xml b/en-US/console-proxy.xml deleted file mode 100644 index b7aa2c9..0000000 --- a/en-US/console-proxy.xml +++ /dev/null @@ -1,71 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Console Proxy - The Console Proxy is a type of System Virtual Machine that has a role in presenting a - console view via the web UI. It connects the user’s browser to the VNC port made available via - the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a - console connection. - Clicking on a console icon brings up a new window. The AJAX code downloaded into that window - refers to the public IP address of a console proxy VM. There is exactly one public IP address - allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then - proxies the connection to the VNC port for the requested VM on the Host hosting the guest. - . - - The hypervisors will have many ports assigned to VNC usage so that multiple VNC sessions - can occur simultaneously. - - - The VNC traffic never goes through the guest virtual IP, and there is no need to enable VNC - within the guest. - The console proxy VM will periodically report its active session count to the Management - Server. The default reporting interval is five seconds. This can be changed through standard - Management Server configuration with the parameter consoleproxy.loadscan.interval. - Assignment of guest VM to console proxy is determined by first determining if the guest VM - has a previous session associated with a console proxy. If it does, the Management Server will - assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. - Failing that, the first available running Console Proxy VM that has the capacity to handle new - sessions is used. - Console proxies can be restarted by administrators but this will interrupt existing console - sessions for users. - Prior to &PRODUCT; version 4.3, the console viewing functionality used a dynamic DNS service - under the domain name realhostip.com. This domain name assists in providing SSL security to - console sessions. A public IP address is assigned to the console proxy. To avoid browser - warnings for mismatched SSL certificates, the URL for the new console window was set to the form - of https://aaa-bbb-ccc-ddd.realhostip.com. Customers viewed this URL during the console session - creation. &PRODUCT; included the realhostip.com SSL certificate in the console proxy VM. Because - &PRODUCT; cannot know the DNS records of customers' public IPs prior to shipping the software, a - dynamic DNS server is run that is authoritative for the realhostip.com domain. It mapped the - aaa-bbb-ccc-ddd part of the DNS name to the IP address aaa.bbb.ccc.ddd on lookups. This allowed - the browser to correctly connect to the console proxy's public IP, where it then expects and - receives a SSL certificate for realhostip.com, and SSL is set up without browser - warnings. - The realhostip.com domain has now been depreciated. As an alternate, &PRODUCT; provides a - new mechanism based on global settings to help administrators set up secure connections across - various deployment environments. See for information on setting - up own domain, then customize the URL of your console session to reflect your own domain - name. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/convert-hyperv-vm-to-template.xml ---------------------------------------------------------------------- diff --git a/en-US/convert-hyperv-vm-to-template.xml b/en-US/convert-hyperv-vm-to-template.xml deleted file mode 100644 index df38823..0000000 --- a/en-US/convert-hyperv-vm-to-template.xml +++ /dev/null @@ -1,69 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Converting a Hyper-V VM to a Template - To convert a Hyper-V VM to a XenServer-compatible &PRODUCT; template, you will need a standalone XenServer host with an attached NFS VHD SR. Use whatever XenServer version you are using with &PRODUCT;, but use XenCenter 5.6 FP1 or SP2 (it is backwards compatible to 5.6). Additionally, it may help to have an attached NFS ISO SR. - For Linux VMs, you may need to do some preparation in Hyper-V before trying to get the VM to work in XenServer. Clone the VM and work on the clone if you still want to use the VM in Hyper-V. Uninstall Hyper-V Integration Components and check for any references to device names in /etc/fstab: - - From the linux_ic/drivers/dist directory, run make uninstall (where "linux_ic" is the path to the copied Hyper-V Integration Components files). - Restore the original initrd from backup in /boot/ (the backup is named *.backup0). - Remove the "hdX=noprobe" entries from /boot/grub/menu.lst. - Check /etc/fstab for any partitions mounted by device name. Change those entries (if any) to - mount by LABEL or UUID. You can get that information with the blkid command. - - The next step is make sure the VM is not running in Hyper-V, then get the VHD into XenServer. There are two options for doing this. - Option one: - - Import the VHD using XenCenter. In XenCenter, go to Tools>Virtual Appliance Tools>Disk Image Import. - Choose the VHD, then click Next. - Name the VM, choose the NFS VHD SR under Storage, enable "Run Operating System Fixups" and choose the NFS ISO SR. - Click Next, then Finish. A VM should be created. - - Option two: - - Run XenConvert, under From choose VHD, under To choose XenServer. Click Next. - Choose the VHD, then click Next. - Input the XenServer host info, then click Next. - Name the VM, then click Next, then Convert. A VM should be created. - - Once you have a VM created from the Hyper-V VHD, prepare it using the following steps: - - Boot the VM, uninstall Hyper-V Integration Services, and reboot. - Install XenServer Tools, then reboot. - Prepare the VM as desired. For example, run sysprep on Windows VMs. See . - - Either option above will create a VM in HVM mode. This is fine for Windows VMs, but Linux VMs may not perform optimally. Converting a Linux VM to PV mode will require additional steps and will vary by distribution. - - Shut down the VM and copy the VHD from the NFS storage to a web server; for example, mount the NFS share on the web server and copy it, or from the XenServer host use sftp or scp to upload it to the web server. - In &PRODUCT;, create a new template using the following values: - - URL. Give the URL for the VHD - OS Type. Use the appropriate OS. For PV mode on CentOS, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServer. - Hypervisor. XenServer - Format. VHD - - - - The template will be created, and you can create instances from it. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/cpu-sockets.xml ---------------------------------------------------------------------- diff --git a/en-US/cpu-sockets.xml b/en-US/cpu-sockets.xml deleted file mode 100644 index 2fd592d..0000000 --- a/en-US/cpu-sockets.xml +++ /dev/null @@ -1,51 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Reporting CPU Sockets - &PRODUCT; manages different types of hosts that contains one or more physical CPU sockets. - CPU socket is considered as a unit of measure used for licensing and billing cloud - infrastructure. &PRODUCT; provides both UI and API support to collect the CPU socket statistics - for billing purpose. The Infrastructure tab has a new tab for CPU sockets. You can view the - statistics for CPU sockets managed by &PRODUCT;, which in turn reflects the size of the cloud. - The CPU Socket page will give you the number of hosts and sockets used for each hypervisor - type. - - - Log in to the &PRODUCT; UI. - - - In the left navigation bar, click Infrastructure. - - - On CPU Sockets, click View all. - The CPU Socket page is displayed. The page shows the number of hosts and CPU sockets - based on hypervisor types. - CPU sockets are displayed for XenServer version 6.2 and beyond, KVM, Hyper-V and VMware - hypervisors. - This feature is not available for XenServer versions prior to 6.2 as they don't support - retrieving CPU socket information. Additionally, this feature is not supported for - Baremetal. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-bare-metal-template.xml ---------------------------------------------------------------------- diff --git a/en-US/create-bare-metal-template.xml b/en-US/create-bare-metal-template.xml deleted file mode 100644 index 0ee4c11..0000000 --- a/en-US/create-bare-metal-template.xml +++ /dev/null @@ -1,45 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Creating a Bare Metal Template - Before you can create a bare metal template, you must have performed several other installation and setup steps to create a bare metal cluster and environment. See Bare Metal Installation in the Installation Guide. It is assumed you already have a directory named "win7_64bit" on your CIFS server, containing the image for the bare metal instance. This directory and image are set up as part of the Bare Metal Installation procedure. - - Log in to the &PRODUCT; UI as an administrator or end user. - In the left navigation bar, click Templates. - Click Create Template. - In the dialog box, enter the following values. - - Name. Short name for the template. - Display Text. Description of the template. - URL. The directory name which contains image file on your CIFS server. For example, win7_64bit. - Zone. All Zones. - OS Type. Select the OS type of the ISO image. Choose other if the OS Type of the ISO is not listed or if the ISO is not bootable. - Hypervisor. BareMetal. - Format. BareMetal. - Password Enabled. No. - Public. No. - Featured. Choose Yes if you would like this template to be more prominent for users to select. Only administrators may make templates featured. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-linux-template.xml ---------------------------------------------------------------------- diff --git a/en-US/create-linux-template.xml b/en-US/create-linux-template.xml deleted file mode 100755 index 156a0ac..0000000 --- a/en-US/create-linux-template.xml +++ /dev/null @@ -1,41 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - - - - -

- Creating a Linux Template - Linux templates should be prepared using this documentation in order to prepare your linux VMs for template deployment. For ease of documentation, the VM which you are configuring the template on will be referred to as "Template Master". This guide currently covers legacy setups which do not take advantage of UserData and cloud-init and assumes openssh-server is installed during installation. - - - An overview of the procedure is as follow: - - Upload your Linux ISO. For more information, see . - Create a VM Instance with this ISO. For more information, see . - Prepare the Linux VM - Create a template from the VM. For more information, see . - - - -

- http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-new-projects.xml ---------------------------------------------------------------------- diff --git a/en-US/create-new-projects.xml b/en-US/create-new-projects.xml deleted file mode 100644 index 7696c9e..0000000 --- a/en-US/create-new-projects.xml +++ /dev/null @@ -1,37 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - - -

- Creating a New Project - &PRODUCT; administrators and domain administrators can create projects. If the global configuration parameter allow.user.create.projects is set to true, end users can also create projects. - - Log in as administrator to the &PRODUCT; UI. - In the left navigation, click Projects. - In Select view, click Projects. - Click New Project. - Give the project a name and description for display to users, then click Create Project. - A screen appears where you can immediately add more members to the project. This is optional. Click Next when you are ready to move on. - Click Save. - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-passive-vpn-vpc.xml ---------------------------------------------------------------------- diff --git a/en-US/create-passive-vpn-vpc.xml b/en-US/create-passive-vpn-vpc.xml deleted file mode 100644 index 3c1646e..0000000 --- a/en-US/create-passive-vpn-vpc.xml +++ /dev/null @@ -1,56 +0,0 @@ - - -%BOOK_ENTITIES; -]> - -

- Site-to-Site VPN Connection Between VPC Networks - &PRODUCT; provides you with the ability to establish a site-to-site VPN connection between - &PRODUCT; virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this - functionality, users can deploy applications in multiple Availability Zones or VPCs, which can - communicate with each other by using a secure Site-to-Site VPN Tunnel. - This feature is supported on all the hypervisors. - - - Create two VPCs. For example, VPC A and VPC B. - For more information, see . - - - Create VPN gateways on both the VPCs you created. - For more information, see . - - - Create VPN customer gateway for both the VPCs. - For more information, see . - - - Enable a VPN connection on VPC A in passive mode. - For more information, see . - Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the - Disconnected state. - - - Enable a VPN connection on VPC B. - Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, - in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate - the connection, VPC B virtual router should not be in passive mode. - The VPN connection is shown in the Disconnected state. - Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state. - - -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-template-from-existing-vm.xml ---------------------------------------------------------------------- diff --git a/en-US/create-template-from-existing-vm.xml b/en-US/create-template-from-existing-vm.xml deleted file mode 100644 index 35788fd..0000000 --- a/en-US/create-template-from-existing-vm.xml +++ /dev/null @@ -1,56 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Creating a Template from an Existing Virtual Machine - Once you have at least one VM set up in the way you want, you can use it as the prototype for other VMs. - - Create and start a virtual machine using any of the techniques given in . - Make any desired configuration changes on the running VM, then click Stop. - Wait for the VM to stop. When the status shows Stopped, go to the next step. - Click Create Template and provide the following: - - Name and Display Text. These will be shown in the UI, so - choose something descriptive. - OS Type. This helps &PRODUCT; and the hypervisor perform - certain operations and make assumptions that improve the performance of the - guest. Select one of the following. - - If the operating system of the stopped VM is listed, choose it. - If the OS type of the stopped VM is not listed, choose Other. - If you want to boot from this template in PV mode, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServere: - Note: Generally you should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other. - - - Public. Choose Yes to make this template accessible to all - users of this &PRODUCT; installation. The template will appear in the - Community Templates list. See . - Password Enabled. Choose Yes if your template has the - &PRODUCT; password change script installed. See . - - Click Add. - - The new template will be visible in the Templates section when the template creation process - has been completed. The template is then available when creating a new VM. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-template-from-snapshot.xml ---------------------------------------------------------------------- diff --git a/en-US/create-template-from-snapshot.xml b/en-US/create-template-from-snapshot.xml deleted file mode 100644 index d968422..0000000 --- a/en-US/create-template-from-snapshot.xml +++ /dev/null @@ -1,28 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Creating a Template from a Snapshot - - If you do not want to stop the VM in order to use the Create Template menu item (as described in ), you can create a template directly from any snapshot through the &PRODUCT; UI. -

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-templates-overview.xml ---------------------------------------------------------------------- diff --git a/en-US/create-templates-overview.xml b/en-US/create-templates-overview.xml deleted file mode 100644 index 900165f..0000000 --- a/en-US/create-templates-overview.xml +++ /dev/null @@ -1,37 +0,0 @@ - - -%BOOK_ENTITIES; -]> - - -

- Creating Templates: Overview - &PRODUCT; ships with a default template for the CentOS operating system. There are a variety of ways to add more templates. Administrators and end users can add templates. The typical sequence of events is: - - Launch a VM instance that has the operating system you want. Make any other desired configuration changes to the VM. - Stop the VM. - Convert the volume into a template. - - There are other ways to add templates to &PRODUCT;. For example, you can take a snapshot - of the VM's volume and create a template from the snapshot, or import a VHD from another - system into &PRODUCT;. - The various techniques for creating templates are described in the next few sections. - -