You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by se...@apache.org on 2015/10/01 16:04:46 UTC
[36/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/creating-vms.xml
----------------------------------------------------------------------
diff --git a/en-US/creating-vms.xml b/en-US/creating-vms.xml
deleted file mode 100644
index 86d05d3..0000000
--- a/en-US/creating-vms.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="creating-vms">
- <title>Creating VMs</title>
- <para>Virtual machines are usually created from a template. Users can also create blank virtual
- machines. A blank virtual machine is a virtual machine without an OS template. Users can attach
- an ISO file and install the OS from the CD/DVD-ROM.</para>
- <note>
- <para>You can create a VM without starting it. You can determine whether the VM needs to be
- started as part of the VM deployment. A request parameter, startVM, in the deployVm API
- provides this feature. For more information, see the Developer's Guide</para>
- </note>
- <para>To create a VM from a template:</para>
- <orderedlist>
- <listitem>
- <para>Log in to the &PRODUCT; UI as an administrator or user.</para>
- </listitem>
- <listitem>
- <para>In the left navigation bar, click Instances.</para>
- </listitem>
- <listitem>
- <para>Click Add Instance.</para>
- </listitem>
- <listitem>
- <para>Select a zone.</para>
- </listitem>
- <listitem>
- <para>Select a template, then follow the steps in the wizard. For more information about how
- the templates came to be in this list, see <xref linkend="working-with-templates"/>.</para>
- </listitem>
- <listitem>
- <para>Be sure that the hardware you have allows starting the selected service offering.</para>
- </listitem>
- <listitem>
- <para>Click Submit and your VM will be created and started.</para>
- <note>
- <para>For security reason, the internal name of the VM is visible only to the root
- admin.</para>
- </note>
- </listitem>
- </orderedlist>
- <para>To create a VM from an ISO:</para>
- <note>
- <para>(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in
- the template or added after the VM is created. The PV drivers are necessary for essential
- management functions such as mounting additional volumes and ISO images, live migration, and
- graceful shutdown.</para>
- </note>
- <orderedlist>
- <listitem>
- <para>Log in to the &PRODUCT; UI as an administrator or user.</para>
- </listitem>
- <listitem>
- <para>In the left navigation bar, click Instances.</para>
- </listitem>
- <listitem>
- <para>Click Add Instance.</para>
- </listitem>
- <listitem>
- <para>Select a zone.</para>
- </listitem>
- <listitem>
- <para>Select ISO Boot, and follow the steps in the wizard.</para>
- </listitem>
- <listitem>
- <para>Click Submit and your VM will be created and started.</para>
- </listitem>
- <!-- <listitem><para>(Oracle VM only) After ISO installation, the installer reboots into the operating system. Due to a known issue in OVM, the reboot will place the VM in the Stopped state. In the &PRODUCT; UI, detach the ISO from the VM (so that the VM will not boot from the ISO again), then click the Start button to restart the VM.</para></listitem> -->
- </orderedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/customizing-dns.xml
----------------------------------------------------------------------
diff --git a/en-US/customizing-dns.xml b/en-US/customizing-dns.xml
deleted file mode 100644
index c24bad8..0000000
--- a/en-US/customizing-dns.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="customizing-dns">
- <title>Customizing the Network Domain Name</title>
- <para>The root administrator can optionally assign a custom DNS suffix at the level of a network, account, domain, zone, or entire &PRODUCT; installation, and a domain administrator can do so within their own domain. To specify a custom domain name and put it into effect, follow these steps.</para>
- <orderedlist>
- <listitem><para>Set the DNS suffix at the desired scope</para>
- <itemizedlist>
- <listitem><para>At the network level, the DNS suffix can be assigned through the UI when creating a new network, as described in <xref linkend="add-additional-guest-network"/> or with the updateNetwork command in the &PRODUCT; API.</para></listitem>
- <listitem><para>At the account, domain, or zone level, the DNS suffix can be assigned with the appropriate &PRODUCT; API commands: createAccount, editAccount, createDomain, editDomain, createZone, or editZone.</para></listitem>
- <listitem><para>At the global level, use the configuration parameter guest.domain.suffix. You can also use the &PRODUCT; API command updateConfiguration. After modifying this global configuration, restart the Management Server to put the new setting into effect.</para></listitem>
- </itemizedlist></listitem>
- <listitem><para>To make the new DNS suffix take effect for an existing network, call the &PRODUCT; API command updateNetwork. This step is not necessary when the DNS suffix was specified while creating a new network.</para></listitem>
- </orderedlist>
- <para>The source of the network domain that is used depends on the following rules.</para>
- <itemizedlist>
- <listitem><para>For all networks, if a network domain is specified as part of a network's own configuration, that value is used.</para></listitem>
- <listitem><para>For an account-specific network, the network domain specified for the account is used. If none is specified, the system looks for a value in the domain, zone, and global configuration, in that order.</para></listitem>
- <listitem><para>For a domain-specific network, the network domain specified for the domain is used. If none is specified, the system looks for a value in the zone and global configuration, in that order.</para></listitem>
- <listitem><para>For a zone-specific network, the network domain specified for the zone is used. If none is specified, the system looks for a value in the global configuration.</para></listitem>
- </itemizedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/database-replication.xml
----------------------------------------------------------------------
diff --git a/en-US/database-replication.xml b/en-US/database-replication.xml
deleted file mode 100644
index 8ca8071..0000000
--- a/en-US/database-replication.xml
+++ /dev/null
@@ -1,144 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="database-replication">
- <title>Database Replication (Optional)</title>
- <para>&PRODUCT; supports database replication from one MySQL node to another. This is achieved using standard MySQL replication. You may want to do this as insurance against MySQL server or storage loss. MySQL replication is implemented using a master/slave model. The master is the node that the Management Servers are configured to use. The slave is a standby node that receives all write operations from the master and applies them to a local, redundant copy of the database. The following steps are a guide to implementing MySQL replication.</para>
- <note><para>Creating a replica is not a backup solution. You should develop a backup procedure for the MySQL data that is distinct from replication.</para></note>
- <orderedlist>
- <listitem><para>Ensure that this is a fresh install with no data in the master.</para></listitem>
- <listitem>
- <para>Edit my.cnf on the master and add the following in the [mysqld] section below datadir.</para>
- <programlisting>
-log_bin=mysql-bin
-server_id=1
- </programlisting>
- <para>The server_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc.</para>
- </listitem>
- <listitem>
- <para>Restart the MySQL service. On RHEL/CentOS systems, use:</para>
- <programlisting>
-# service mysqld restart
- </programlisting>
- <para>On Debian/Ubuntu systems, use:</para>
- <programlisting>
-# service mysql restart
- </programlisting>
- </listitem>
- <listitem>
- <para>Create a replication account on the master and give it privileges. We will use the "cloud-repl" user with the password "password". This assumes that master and slave run on the 172.16.1.0/24 network.</para>
- <programlisting>
-# mysql -u root
-mysql> create user 'cloud-repl'@'172.16.1.%' identified by 'password';
-mysql> grant replication slave on *.* TO 'cloud-repl'@'172.16.1.%';
-mysql> flush privileges;
-mysql> flush tables with read lock;
- </programlisting>
- </listitem>
- <listitem><para>Leave the current MySQL session running.</para></listitem>
- <listitem><para>In a new shell start a second MySQL session.</para></listitem>
- <listitem>
- <para>Retrieve the current position of the database.</para>
- <programlisting>
-# mysql -u root
-mysql> show master status;
-+------------------+----------+--------------+------------------+
-| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
-+------------------+----------+--------------+------------------+
-| mysql-bin.000001 | 412 | | |
-+------------------+----------+--------------+------------------+
- </programlisting>
- </listitem>
- <listitem><para>Note the file and the position that are returned by your instance.</para></listitem>
- <listitem><para>Exit from this session.</para></listitem>
- <listitem>
- <para>Complete the master setup. Returning to your first session on the master, release the locks and exit MySQL.</para>
- <programlisting>
-mysql> unlock tables;
- </programlisting>
- </listitem>
- <listitem>
- <para>Install and configure the slave. On the slave server, run the following commands.</para>
- <programlisting>
-# yum install mysql-server
-# chkconfig mysqld on
- </programlisting>
- </listitem>
- <listitem>
- <para>Edit my.cnf and add the following lines in the [mysqld] section below datadir.</para>
- <programlisting>
-server_id=2
-innodb_rollback_on_timeout=1
-innodb_lock_wait_timeout=600
- </programlisting>
- </listitem>
- <listitem>
- <para>Restart MySQL. Use "mysqld" on RHEL/CentOS systems:</para>
- <programlisting>
-# service mysqld restart
- </programlisting>
- <para>On Ubuntu/Debian systems use "mysql."</para>
- <programlisting>
-# service mysql restart
- </programlisting>
- </listitem>
- <listitem>
- <para>Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps.</para>
- <programlisting>
-mysql> change master to
- -> master_host='172.16.1.217',
- -> master_user='cloud-repl',
- -> master_password='password',
- -> master_log_file='mysql-bin.000001',
- -> master_log_pos=412;
- </programlisting>
- </listitem>
- <listitem>
- <para>Then start replication on the slave.</para>
- <programlisting>
-mysql> start slave;
- </programlisting>
- </listitem>
- <listitem>
- <para>Optionally, open port 3306 on the slave as was done on the master earlier.</para>
- <para>This is not required for replication to work. But if you choose not to do this, you will need to do it when failover to the replica occurs.</para>
- </listitem>
- </orderedlist>
- <section id="database-failover">
- <title>Failover</title>
- <para>This will provide for a replicated database that can be used to implement manual failover for the Management Servers. &PRODUCT; failover from one MySQL instance to another is performed by the administrator. In the event of a database failure you should:</para>
- <orderedlist>
- <listitem><para>Stop the Management Servers (via service cloudstack-management stop).</para></listitem>
- <listitem><para>Change the replica's configuration to be a master and restart it.</para></listitem>
- <listitem><para>Ensure that the replica's port 3306 is open to the Management Servers.</para></listitem>
- <listitem><para>Make a change so that the Management Server uses the new database. The simplest process here is to put the IP address of the new database server into each Management Server's /etc/cloudstack/management/db.properties.</para></listitem>
- <listitem>
- <para>Restart the Management Servers:</para>
- <programlisting>
-# service cloudstack-management start
- </programlisting>
- </listitem>
- </orderedlist>
- </section>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dates-in-usage-record.xml
----------------------------------------------------------------------
diff --git a/en-US/dates-in-usage-record.xml b/en-US/dates-in-usage-record.xml
deleted file mode 100644
index dc2f072..0000000
--- a/en-US/dates-in-usage-record.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<!-- 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.
--->
-
- <section id="dates-in-usage-record">
- <title>Dates in the Usage Record</title>
- <para>Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2).</para>
- <para>Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated.</para>
- <para>For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent.</para>
- <para>There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation.</para>
- </section>
-
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/db-ha.xml
----------------------------------------------------------------------
diff --git a/en-US/db-ha.xml b/en-US/db-ha.xml
deleted file mode 100644
index 72fab64..0000000
--- a/en-US/db-ha.xml
+++ /dev/null
@@ -1,220 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="db-ha">
- <title>Database High Availability</title>
- <para>To help ensure high availability of the databases that store the internal data for
- &PRODUCT;, you can set up database high availability. This covers both the main &PRODUCT;
- database and the Usage database. High availability is achieved using the MySQL connector
- parameters and two-way high availability. Tested with MySQL 5.1. </para>
- <section id="db-ha-howto">
- <title>How to Set Up Database High Availability</title>
- <para>Database high availability in &PRODUCT; is provided using the MySQL high availability
- capabilities. The steps to set up high availability can be found in the MySQL documentation
- (links are provided below). It is suggested that you set up two-way high availability, which
- involves two database nodes. In this case, for example, you might have node1 and node2. In
- Asynchronous high availability configuration, not more than two database nodes are supported. </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/event-replica.png"/>
- </imageobject>
- <textobject>
- <phrase>event-replica.png: high availability</phrase>
- </textobject>
- </mediaobject>
- <para>References:</para>
- <itemizedlist>
- <listitem>
- <para><ulink url="http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html"
- >http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html</ulink></para>
- </listitem>
- <listitem>
- <para><ulink
- url="https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server"
- >https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server</ulink></para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="dbha-consider">
- <title>Database High Availability Considerations</title>
- <itemizedlist>
- <listitem>
- <para>To clean up bin log files automatically, perform the following configuration in the
- <filename>my.cnf</filename> file of each MySQL server:</para>
- <para><property>expire_logs_days=10</property> : Number of days to keep the log
- files.</para>
- <para>
- <property>max_binlog_size=100M</property>: The maximum size of each log file.</para>
- </listitem>
- <listitem>
- <para>To change the bin log files location, use the
- <property>log-bin=/var/lib/mysql/binlog/bin-log</property> property in the
- <filename>my.cnf</filename> file of each MySQL server.</para>
- </listitem>
- <listitem>
- <para>If two Management Servers happen to connect to two different database HA (split
- brain), modify the following properties in db.properties of the slave: </para>
- <itemizedlist>
- <listitem>
- <para><property>auto_increment_increment = 10</property>: Instruct the MySQL node to
- auto increment values by 10 instead of default value 1.</para>
- </listitem>
- <listitem>
- <para><property>auto_increment_offset = 2</property>: Instruct the MySQL node what is
- the starting point of the auto increment column value to be start with. The second
- property is relevant only when split brain occurs on a fresh setup.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </section>
- <section id="db-ha-configure">
- <title>Configuring Database High Availability</title>
- <para>To control the database high availability behavior, use the following configuration
- settings in the file /etc/cloudstack/management/db.properties.</para>
- <para><emphasis role="bold">Required Settings</emphasis></para>
- <para>Be sure you have set the following in db.properties:</para>
- <itemizedlist>
- <listitem>
- <para>db.ha.enabled: set to true if you want to use the high availability feature.</para>
- <para>Example: db.ha.enabled=true</para>
- </listitem>
- <listitem>
- <para>db.cloud.slaves: set to a comma-delimited set of slave hosts for the cloud database.
- This is the list of nodes set up with high availability. The master node is not in the
- list, since it is already mentioned elsewhere in the properties file.</para>
- <para>Example: db.cloud.slaves=node2,node3,node4</para>
- </listitem>
- <listitem>
- <para>db.usage.slaves: set to a comma-delimited set of slave hosts for the usage database.
- This is the list of nodes set up with high availability. The master node is not in the
- list, since it is already mentioned elsewhere in the properties file.</para>
- <para>Example: db.usage.slaves=node2,node3,node4</para>
- </listitem>
- </itemizedlist>
- <para><emphasis role="bold">Optional Settings</emphasis></para>
- <para>The following settings must be present in db.properties, but you are not required to
- change the default values unless you wish to do so for tuning purposes:</para>
- <itemizedlist>
- <listitem>
- <para>db.cloud.secondsBeforeRetryMaster: The number of seconds the MySQL connector should
- wait before trying again to connect to the master after the master went down. Default is 1
- hour. The retry might happen sooner if db.cloud.queriesBeforeRetryMaster is reached
- first.</para>
- <para>Example: db.cloud.secondsBeforeRetryMaster=3600</para>
- </listitem>
- <listitem>
- <para>db.cloud.queriesBeforeRetryMaster: The minimum number of queries to be sent to the
- database before trying again to connect to the master after the master went down. Default
- is 5000. The retry might happen sooner if db.cloud.secondsBeforeRetryMaster is reached
- first.</para>
- <para>Example: db.cloud.queriesBeforeRetryMaster=5000</para>
- </listitem>
- <listitem>
- <para>db.cloud.initialTimeout: Initial time the MySQL connector should wait before trying
- again to connect to the master. Default is 3600.</para>
- <para>Example: db.cloud.initialTimeout=3600</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="aync-conf">
- <title>Asynchronous Configuration for Database High Availability</title>
- <para>The MySQL configuration to support DB HA in MySQL server is goes into the
- <filename>/etc/my.cnf</filename> file and configuration slightly varies between master and
- slave.</para>
- <section id="master-conf">
- <title>Master Configuration</title>
- <programlisting>[mysqld]
-datadir=/var/lib/mysql
-socket=/var/lib/mysql/mysql.sock
-# Disabling symbolic-links is recommended to prevent assorted security risks
-symbolic-links=0
-# Settings user and group are ignored when systemd is used.
-# If you need to run mysqld under a different user or group,
-# customize your systemd unit file for mysqld according to the
-# instructions in http://fedoraproject.org/wiki/Systemd
-server-id=1
-default-storage-engine=InnoDB
-character-set-server=utf8
-transaction-isolation=READ-COMMITTED
-log-bin=mysql-bin
-innodb_flush_log_at_trx_commit=1
-sync_binlog=1
-binlog-format=ROW
-#Bin logs cleanup configuration
-expiry_logs_days=10
-max_binlog_size=100M
-
-[mysqld_safe]
-log-error=/var/log/mysqld.log
-pid-file=/var/run/mysqld/mysqld.pid</programlisting>
- </section>
- <section id="slave-conf">
- <title>Slave Configuration</title>
- <programlisting>[mysqld]
-datadir=/var/lib/mysql
-socket=/var/lib/mysql/mysql.sock
-# Disabling symbolic-links is recommended to prevent assorted security risks
-symbolic-links=0
-# Settings user and group are ignored when systemd is used.
-# If you need to run mysqld under a different user or group,
-# customize your systemd unit file for mysqld according to the
-# instructions in http://fedoraproject.org/wiki/Systemd
-server-id=2
-default-storage-engine = InnoDB
-character-set-server = utf8
-transaction-isolation = READ-COMMITTED
-log-bin=mysql-bin
-innodb_flush_log_at_trx_commit=1
-sync_binlog=1
-binlog-format=ROW
-#Parameters to solve split brain problem
-<emphasis role="bold">auto_increment_increment=10
-auto_increment_offset=2</emphasis>
-#Bin logs cleanup configuration
-expiry_logs_days=10
-max_binlog_size=100M
-[mysqld_safe]
-log-error=/var/log/mysqld.log
-pid-file=/var/run/mysqld/mysqld.pid</programlisting>
- </section>
- </section>
- <section id="db-ha-limitations">
- <title>Limitations on Database High Availability</title>
- <para>The following limitations exist in the current implementation of this feature.</para>
- <itemizedlist>
- <listitem>
- <para>Slave hosts can not be monitored through &PRODUCT;. You will need to have a separate
- means of monitoring.</para>
- </listitem>
- <listitem>
- <para>Events from the database side are not integrated with the &PRODUCT; Management Server
- events system.</para>
- </listitem>
- <listitem>
- <para>MySQL 5.1 supports only Asynchronous high availability; therefore, there is a chance
- of data inconsistency while server is down. </para>
- </listitem>
- </itemizedlist>
- </section>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dedicated-ha-hosts.xml
----------------------------------------------------------------------
diff --git a/en-US/dedicated-ha-hosts.xml b/en-US/dedicated-ha-hosts.xml
deleted file mode 100644
index 89c721f..0000000
--- a/en-US/dedicated-ha-hosts.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="dedicated-ha-hosts">
- <title>Dedicated HA Hosts</title>
- <para>One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:</para>
- <itemizedlist>
- <listitem><para>Make it easier to determine which VMs have been restarted as part of the &PRODUCT; high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.).</para></listitem>
- <listitem><para>Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes.</para></listitem>
- </itemizedlist>
- <para>The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, "ha_host"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs.</para>
- <note><para>If you set ha.tag, be sure to actually use that tag on at least one host in your cloud. If the tag specified in ha.tag is not set for any host in the cloud, the HA-enabled VMs will fail to restart after a crash.</para></note>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/default-account-resource-limit.xml
----------------------------------------------------------------------
diff --git a/en-US/default-account-resource-limit.xml b/en-US/default-account-resource-limit.xml
deleted file mode 100644
index 5134e50..0000000
--- a/en-US/default-account-resource-limit.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="default-account-resource-limit">
- <title>Default Account Resource Limits</title>
- <para>You can limit resource use by accounts. The default limits are set by using global
- configuration parameters, and they affect all accounts within a cloud. The relevant
- parameters are those beginning with max.account, for example: max.account.snapshots.</para>
- <para>To override a default limit for a particular account, set a per-account resource limit.</para>
- <orderedlist>
- <listitem><para>Log in to the &PRODUCT; UI.</para></listitem>
- <listitem><para>In the left navigation tree, click Accounts.</para></listitem>
- <listitem><para>Select the account you want to modify. The current limits are displayed. A value of -1 shows
- that there is no limit in place.</para></listitem>
- <listitem><para>Click the Edit button.<inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/edit-icon.png"/>
- </imageobject>
- <textobject>
- <phrase>editbutton.png: edits the settings</phrase>
- </textobject>
- </inlinemediaobject></para></listitem>
- </orderedlist>
-
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/default-template.xml
----------------------------------------------------------------------
diff --git a/en-US/default-template.xml b/en-US/default-template.xml
deleted file mode 100644
index 16442c3..0000000
--- a/en-US/default-template.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="default-template">
- <title>The Default Template</title>
- <para>&PRODUCT; includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates.</para>
- <para>The root password for the default template is "password".</para>
- <para>A default template is provided for each of XenServer, KVM, and vSphere. The templates that are downloaded depend on the hypervisor type that is available in your cloud. Each template is approximately 2.5 GB physical size.</para>
- <para>The default template includes the standard iptables rules, which will block most access to the template excluding ssh.</para>
- <programlisting># iptables --list
-Chain INPUT (policy ACCEPT)
-target prot opt source destination
-RH-Firewall-1-INPUT all -- anywhere anywhere
-
-Chain FORWARD (policy ACCEPT)
-target prot opt source destination
-RH-Firewall-1-INPUT all -- anywhere anywhere
-
-Chain OUTPUT (policy ACCEPT)
-target prot opt source destination
-
-Chain RH-Firewall-1-INPUT (2 references)
-target prot opt source destination
-ACCEPT all -- anywhere anywhere
-ACCEPT icmp -- anywhere anywhere icmp any
-ACCEPT esp -- anywhere anywhere
-ACCEPT ah -- anywhere anywhere
-ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
-ACCEPT udp -- anywhere anywhere udp dpt:ipp
-ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
-ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
-ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
-REJECT all -- anywhere anywhere reject-with icmp-host-
-</programlisting>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/delete-event-alerts.xml
----------------------------------------------------------------------
diff --git a/en-US/delete-event-alerts.xml b/en-US/delete-event-alerts.xml
deleted file mode 100644
index c0d5671..0000000
--- a/en-US/delete-event-alerts.xml
+++ /dev/null
@@ -1,87 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="delete-event-alerts">
- <title>Deleting and Archiving Events and Alerts</title>
- <para>&PRODUCT; provides you the ability to delete or archive the existing alerts and events that
- you no longer want to implement. You can regularly delete or archive any alerts or events that
- you cannot, or do not want to resolve from the database.</para>
- <para>You can delete or archive individual alerts or events either directly by using the Quickview
- or by using the Details page. If you want to delete multiple alerts or events at the same time,
- you can use the respective context menu. You can delete alerts or events by category for a time
- period. For example, you can select categories such as <emphasis role="bold"
- >USER.LOGOUT</emphasis>, <emphasis role="bold">VM.DESTROY</emphasis>, <emphasis role="bold"
- >VM.AG.UPDATE</emphasis>, <emphasis role="bold">CONFIGURATION.VALUE.EDI</emphasis>, and so on.
- You can also view the number of events or alerts archived or deleted.</para>
- <para>In order to support the delete or archive alerts, the following global parameters have been
- added:</para>
- <itemizedlist>
- <listitem>
- <para><emphasis role="bold">alert.purge.delay</emphasis>: The alerts older than specified
- number of days are purged. Set the value to 0 to never purge alerts automatically.</para>
- </listitem>
- <listitem>
- <para><emphasis role="bold">alert.purge.interval</emphasis>: The interval in seconds to wait
- before running the alert purge thread. The default is 86400 seconds (one day).</para>
- </listitem>
- </itemizedlist>
- <note>
- <para>Archived alerts or events cannot be viewed in the UI or by using the API. They are
- maintained in the database for auditing or compliance purposes.</para>
- </note>
- <section id="permissions-events">
- <title>Permissions</title>
- <para>Consider the following:</para>
- <itemizedlist>
- <listitem>
- <para>The root admin can delete or archive one or multiple alerts or events.</para>
- </listitem>
- <listitem>
- <para>The domain admin or end user can delete or archive one or multiple events.</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="del-archive">
- <title>Procedure</title>
- <orderedlist>
- <listitem>
- <para>Log in as administrator to the &PRODUCT; UI.</para>
- </listitem>
- <listitem>
- <para>In the left navigation, click Events.</para>
- </listitem>
- <listitem>
- <para>Perform either of the following:</para>
- <itemizedlist>
- <listitem>
- <para>To archive events, click Archive Events, and specify event type and date.</para>
- </listitem>
- <listitem>
- <para>To archive events, click Delete Events, and specify event type and date.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>Click OK.</para>
- </listitem>
- </orderedlist>
- </section>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/delete-reset-vpn.xml
----------------------------------------------------------------------
diff --git a/en-US/delete-reset-vpn.xml b/en-US/delete-reset-vpn.xml
deleted file mode 100644
index 2fe85d2..0000000
--- a/en-US/delete-reset-vpn.xml
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="delete-reset-vpn">
- <title>Restarting and Removing a VPN Connection</title>
- <orderedlist>
- <listitem>
- <para>Log in to the &PRODUCT; UI as an administrator or end user.</para>
- </listitem>
- <listitem>
- <para>In the left navigation, choose Network.</para>
- </listitem>
- <listitem>
- <para>In the Select view, select VPC.</para>
- <para>All the VPCs that you have created for the account is listed in the page.</para>
- </listitem>
- <listitem>
- <para>Click the Configure button of the VPC to which you want to deploy the VMs.</para>
- <para>The VPC page is displayed where all the tiers you created are listed in a
- diagram.</para>
- </listitem>
- <listitem>
- <para>Click the Settings icon.</para>
- <para>For each tier, the following options are displayed:</para>
- <itemizedlist>
- <listitem>
- <para>Internal LB</para>
- </listitem>
- <listitem>
- <para>Public LB IP</para>
- </listitem>
- <listitem>
- <para>Static NAT</para>
- </listitem>
- <listitem>
- <para>Virtual Machines</para>
- </listitem>
- <listitem>
- <para>CIDR</para>
- </listitem>
- </itemizedlist>
- <para>The following router information is displayed:</para>
- <itemizedlist>
- <listitem>
- <para>Private Gateways</para>
- </listitem>
- <listitem>
- <para>Public IP Addresses</para>
- </listitem>
- <listitem>
- <para>Site-to-Site VPNs</para>
- </listitem>
- <listitem>
- <para>Network ACL Lists</para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>Select Site-to-Site VPN.</para>
- <para>The Site-to-Site VPN page is displayed.</para>
- </listitem>
- <listitem>
- <para>From the Select View drop-down, ensure that VPN Connection is selected.</para>
- <para>All the VPN connections you created are displayed.</para>
- </listitem>
- <listitem>
- <para>Select the VPN connection you want to work with.</para>
- <para> The Details tab is displayed.</para>
- </listitem>
- <listitem>
- <para>To remove a VPN connection, click the Delete VPN connection button<inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/remove-vpn.png"/>
- </imageobject>
- <textobject>
- <phrase>remove-vpn.png: button to remove a VPN connection</phrase>
- </textobject>
- </inlinemediaobject></para>
- <para>To restart a VPN connection, click the Reset VPN connection button present in the
- Details tab.<inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/reset-vpn.png"/>
- </imageobject>
- <textobject>
- <phrase>reset-vpn.png: button to reset a VPN connection</phrase>
- </textobject>
- </inlinemediaobject></para>
- </listitem>
- </orderedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/delete-templates.xml
----------------------------------------------------------------------
diff --git a/en-US/delete-templates.xml b/en-US/delete-templates.xml
deleted file mode 100644
index f9351da..0000000
--- a/en-US/delete-templates.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="delete-templates">
- <title>Deleting Templates</title>
- <para>Templates may be deleted. In general, when a template spans multiple Zones, only the copy that is selected for deletion will be deleted; the same template in other Zones will not be deleted. The provided CentOS template is an exception to this. If the provided CentOS template is deleted, it will be deleted from all Zones.</para>
- <para>When templates are deleted, the VMs instantiated from them will continue to run. However, new VMs cannot be created based on the deleted template.</para>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/deleting-vms.xml
----------------------------------------------------------------------
diff --git a/en-US/deleting-vms.xml b/en-US/deleting-vms.xml
deleted file mode 100644
index 97245c8..0000000
--- a/en-US/deleting-vms.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="deleting-vms">
- <title>Deleting VMs</title>
- <para>Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines.</para>
- <para>To delete a virtual machine:</para>
- <orderedlist>
- <listitem><para>Log in to the &PRODUCT; UI as a user or admin.</para></listitem>
- <listitem><para>In the left navigation, click Instances.</para></listitem>
- <listitem><para>Choose the VM that you want to delete.</para></listitem>
- <listitem><para>Click the Destroy Instance button. <inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/destroy-instance.png"/>
- </imageobject>
- <textobject>
- <phrase>Destroyinstance.png: button to destroy an instance</phrase>
- </textobject>
- </inlinemediaobject>
- </para></listitem>
- </orderedlist>
- </section>
-
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dell62xx-hardware.xml
----------------------------------------------------------------------
diff --git a/en-US/dell62xx-hardware.xml b/en-US/dell62xx-hardware.xml
deleted file mode 100644
index 8bc7770..0000000
--- a/en-US/dell62xx-hardware.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="dell62xx-hardware">
- <title>Dell 62xx</title>
- <para>The following steps show how a Dell 62xx is configured for zone-level layer-3 switching.
- These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2
- switch is connected to Ethernet port 1/g1.</para>
- <para>The Dell 62xx Series switch supports up to 1024 VLANs.</para>
- <orderedlist>
- <listitem>
- <para>Configure all the VLANs in the database.</para>
- <programlisting>vlan database
-vlan 200-999
-exit</programlisting>
- </listitem>
- <listitem>
- <para>Configure Ethernet port 1/g1.</para>
- <programlisting>interface ethernet 1/g1
-switchport mode general
-switchport general pvid 201
-switchport general allowed vlan add 201 untagged
-switchport general allowed vlan add 300-999 tagged
-exit</programlisting>
- </listitem>
- </orderedlist>
- <para>The statements configure Ethernet port 1/g1 as follows:</para>
- <itemizedlist>
- <listitem>
- <para>VLAN 201 is the native untagged VLAN for port 1/g1.</para>
- </listitem>
- <listitem>
- <para>All VLANs (300-999) are passed to all the pod-level layer-2 switches.</para>
- </listitem>
- </itemizedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dell62xx-layer2.xml
----------------------------------------------------------------------
diff --git a/en-US/dell62xx-layer2.xml b/en-US/dell62xx-layer2.xml
deleted file mode 100644
index 1c0eea0..0000000
--- a/en-US/dell62xx-layer2.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-<!-- 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.
--->
-<section id="dell62xx-layer2">
- <title>Dell 62xx</title>
- <para>The following steps show how a Dell 62xx is configured for pod-level layer-2
- switching.</para>
- <orderedlist>
- <listitem>
- <para>Configure all the VLANs in the database.</para>
- <programlisting>vlan database
-vlan 300-999
-exit</programlisting>
- </listitem>
- <listitem>
- <para>VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch.</para>
- <programlisting>interface range ethernet all
-switchport mode general
-switchport general allowed vlan add 300-999 tagged
-exit</programlisting>
- </listitem>
- </orderedlist>
- <para>The statements configure all Ethernet ports to function as follows:</para>
- <itemizedlist>
- <listitem>
- <para>All ports are configured the same way.</para>
- </listitem>
- <listitem>
- <para>All VLANs (300-999) are passed through all the ports of the layer-2 switch.</para>
- </listitem>
- </itemizedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/deployment-architecture-overview.xml
----------------------------------------------------------------------
diff --git a/en-US/deployment-architecture-overview.xml b/en-US/deployment-architecture-overview.xml
deleted file mode 100644
index 835898c..0000000
--- a/en-US/deployment-architecture-overview.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="deployment-architecture-overview">
- <title>Deployment Architecture Overview</title>
- <para>
- A &PRODUCT; installation consists of two parts: the Management Server
- and the cloud infrastructure that it manages. When you set up and
- manage a &PRODUCT; cloud, you provision resources such as hosts,
- storage devices, and IP addresses into the Management Server, and
- the Management Server manages those resources.
- </para>
- <para>
- The minimum production installation consists of one machine running
- the &PRODUCT; Management Server and another machine to act as the
- cloud infrastructure (in this case, a very simple infrastructure
- consisting of one host running hypervisor software). In its smallest
- deployment, a single machine can act as both the Management Server
- and the hypervisor host (using the KVM hypervisor).
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/basic-deployment.png" />
- </imageobject>
- <textobject><phrase>basic-deployment.png: Basic two-machine deployment</phrase></textobject>
- </mediaobject>
- <para>
- A more full-featured installation consists of a highly-available
- multi-node Management Server installation and up to tens of thousands of
- hosts using any of several advanced networking setups. For
- information about deployment options, see the "Choosing a Deployment Architecture"
- section of the &PRODUCT; Installation Guide.
- </para>
- <xi:include href="management-server-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="cloud-infrastructure-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="networking-overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/detach-move-volumes.xml
----------------------------------------------------------------------
diff --git a/en-US/detach-move-volumes.xml b/en-US/detach-move-volumes.xml
deleted file mode 100644
index 8922db1..0000000
--- a/en-US/detach-move-volumes.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="detach-move-volumes">
- <title>Detaching and Moving Volumes</title>
- <note>
- <para>This procedure is different from moving volumes from one storage pool to another as described in <xref linkend="vm-storage-migration"/>.</para></note>
- <para/>
- <para>A volume can be detached from a guest VM and attached to another guest. Both &PRODUCT;
- administrators and users can detach volumes from VMs and move them to other VMs.</para>
- <para>If the two VMs are in different clusters, and the volume is large, it may take several
- minutes for the volume to be moved to the new VM.</para>
- <!-- <para>If the destination VM is running in the OVM hypervisor, the VM must be stopped before a new volume can be attached to it.</para> -->
- <orderedlist>
- <listitem>
- <para>Log in to the &PRODUCT; UI as a user or admin.</para>
- </listitem>
- <listitem>
- <para>In the left navigation bar, click Storage, and choose Volumes in Select View.
- Alternatively, if you know which VM the volume is attached to, you can click Instances,
- click the VM name, and click View Volumes.</para>
- </listitem>
- <listitem>
- <para>Click the name of the volume you want to detach, then click the Detach Disk button. <inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/detach-disk-icon.png"/>
- </imageobject>
- <textobject>
- <phrase>DetachDiskButton.png: button to detach a volume</phrase>
- </textobject>
- </inlinemediaobject>
- </para>
- </listitem>
- <listitem>
- <para>To move the volume to another VM, follow the steps in <xref linkend="attaching-volume"
- />.</para>
- </listitem>
- </orderedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/devcloud-usage-mode.xml
----------------------------------------------------------------------
diff --git a/en-US/devcloud-usage-mode.xml b/en-US/devcloud-usage-mode.xml
deleted file mode 100644
index bc211ce..0000000
--- a/en-US/devcloud-usage-mode.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="devcloud-usage-mode">
- <title>DevCloud Usage Mode</title>
- <para>DevCloud can be used in several different ways:</para>
- <orderedlist>
- <listitem>
- <para>Full sandbox. Where &PRODUCT; is run within the DevCloud instance started in Virtual Box.</para>
- <para>In this mode, the &PRODUCT; management server runs within the instance and nested virtualization allows instantiation of tiny VMs within DevCloud itself. &PRODUCT; code modifications are done within DevCloud.</para>
- <para>The following diagram shows the architecture of the SandBox mode.</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/DevCloud.png" scale="50"/>
- </imageobject>
- <textobject>
- <phrase>DevCloud.png: Schematic of the DevCloud SandBox architecture</phrase>
- </textobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>A deployment environment. Where &PRODUCT; code is developed in the localhost of the developer and the resulting build is deployed within DevCloud</para>
- <para>This mode was used in the testing procedure of &PRODUCT; 4.0.0 incubating release. See the following screencast to see how: <ulink url="http://vimeo.com/54621457">http://vimeo.com/54621457</ulink></para>
- </listitem>
- <listitem>
- <para>A host-only mode. Where DevCloud is used only as a host. &PRODUCT; management server is run in the localhost of the developer</para>
- <para>This mode makes use of a host-only interface defined in the Virtual Box preferences. Check the following screencast to see how: <ulink url="http://vimeo.com/54610161">http://vimeo.com/54610161</ulink></para>
- <para>The following schematic shows the architecture of the Host-Only mode.</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/DevCloud-hostonly.png" scale="50"/>
- </imageobject>
- <textobject>
- <phrase>DevCloud-hostonly.png: Schematic of the DevCloud host-only architecture </phrase>
- </textobject>
- </mediaobject>
- </listitem>
- </orderedlist>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/devcloud.xml
----------------------------------------------------------------------
diff --git a/en-US/devcloud.xml b/en-US/devcloud.xml
deleted file mode 100644
index 6778187..0000000
--- a/en-US/devcloud.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="devcloud">
- <title>DevCloud</title>
- <para>DevCloud is the &PRODUCT; sandbox. It is provided as a Virtual Box appliance. It is meant to be used as a development environment to easily test new &PRODUCT; development. It has also been used for training and &PRODUCT; demos since it provides a <emphasis>Cloud in a box</emphasis>.</para>
- <note>
- <para>DevCloud is provided as a convenience by community members. It is not an official &PRODUCT; release artifact.</para>
- <para>The &PRODUCT; source code however, contains tools to build your own DevCloud.</para>
- </note>
- <warning>
- <para>DevCloud is under development and should be considered a Work In Progress (WIP), the wiki is the most up to date documentation:</para>
- <para><ulink url="https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud"></ulink></para>
- </warning>
- <xi:include href="devcloud-usage-mode.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="building-devcloud.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/developer-getting-started.xml
----------------------------------------------------------------------
diff --git a/en-US/developer-getting-started.xml b/en-US/developer-getting-started.xml
deleted file mode 100644
index 1456028..0000000
--- a/en-US/developer-getting-started.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-
-<!-- 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.
--->
-
- <section id="getting-started">
- <title>Getting Started</title>
- <para>
- To get started using the &PRODUCT; API, you should have the following:</para>
- <itemizedlist>
- <listitem><para>URL of the &PRODUCT; server you wish to integrate with.</para></listitem>
- <listitem><para>Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you.</para></listitem>
- <listitem><para>Familiarity with HTTP GET/POST and query strings.</para></listitem>
- <listitem><para>Knowledge of either XML or JSON.</para></listitem>
- <listitem><para>Knowledge of a programming language that can generate HTTP requests; for example, Java or PHP.</para></listitem>
- </itemizedlist>
- </section>
-
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/developer-introduction.xml
----------------------------------------------------------------------
diff --git a/en-US/developer-introduction.xml b/en-US/developer-introduction.xml
deleted file mode 100644
index 9d54f31..0000000
--- a/en-US/developer-introduction.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<chapter id="developer-introduction">
- <title>Introduction to the &PRODUCT; API</title>
- <xi:include href="roles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="api-reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <xi:include href="developer-getting-started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</chapter>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/disable-enable-zones-pods-clusters.xml
----------------------------------------------------------------------
diff --git a/en-US/disable-enable-zones-pods-clusters.xml b/en-US/disable-enable-zones-pods-clusters.xml
deleted file mode 100644
index 7d52ae7..0000000
--- a/en-US/disable-enable-zones-pods-clusters.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="disable-enable-zones-pods-clusters">
- <title>Disabling and Enabling Zones, Pods, and Clusters</title>
- <para>You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default.</para>
- <para>To disable and enable a zone, pod, or cluster:</para>
- <orderedlist>
- <listitem><para>Log in to the &PRODUCT; UI as administrator</para></listitem>
- <listitem><para>In the left navigation bar, click Infrastructure.</para>
- </listitem>
- <listitem><para>In Zones, click View More.</para>
- </listitem>
- <listitem><para>If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button.<inlinemediaobject>
- <imageobject>
- <imagedata fileref="./images/enable-disable.png" />
- </imageobject>
- <textobject><phrase>enable-disable.png: button to enable or disable zone, pod, or cluster.</phrase></textobject>
- </inlinemediaobject>
- </para></listitem>
- <listitem><para>If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster.</para></listitem>
- <listitem><para>Click the Compute tab.</para>
- </listitem>
- <listitem><para>In the Pods or Clusters node of the diagram, click View All.</para>
- </listitem>
- <listitem><para>Click the pod or cluster name in the list.</para></listitem>
- <listitem><para>Click the Enable/Disable button.
- <inlinemediaobject><imageobject>
- <imagedata fileref="./images/enable-disable.png" />
- </imageobject></inlinemediaobject></para></listitem>
- </orderedlist>
- </section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/disk-volume-usage-record-format.xml
----------------------------------------------------------------------
diff --git a/en-US/disk-volume-usage-record-format.xml b/en-US/disk-volume-usage-record-format.xml
deleted file mode 100644
index c15d979..0000000
--- a/en-US/disk-volume-usage-record-format.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<!-- 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.
--->
-
-<section id="disk-volume-usage-record-format">
- <title>Disk Volume Usage Record Format</title>
- <para>For disk volumes, the following fields exist in a usage record.</para>
- <itemizedlist>
- <listitem><para>account – name of the account</para></listitem>
- <listitem><para>accountid – ID of the account</para></listitem>
- <listitem><para>domainid – ID of the domain in which this account resides</para></listitem>
- <listitem><para>zoneid – Zone where the usage occurred</para></listitem>
- <listitem><para>description – A string describing what the usage record is tracking</para></listitem>
- <listitem><para>usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)</para></listitem>
- <listitem><para>usagetype – A number representing the usage type (see Usage Types)</para></listitem>
- <listitem><para>rawusage – A number representing the actual usage in hours</para></listitem>
- <listitem><para>usageid – The volume ID</para></listitem>
- <listitem><para>offeringid – The ID of the disk offering</para></listitem>
- <listitem><para>type – Hypervisor</para></listitem>
- <listitem><para>templateid – ROOT template ID</para></listitem>
- <listitem><para>size – The amount of storage allocated</para></listitem>
- <listitem><para>startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record</para></listitem>
- </itemizedlist>
- </section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dns-dhcp.xml
----------------------------------------------------------------------
diff --git a/en-US/dns-dhcp.xml b/en-US/dns-dhcp.xml
deleted file mode 100644
index 2359e83..0000000
--- a/en-US/dns-dhcp.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="dns-dhcp">
- <title>DNS and DHCP</title>
- <para>The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone.</para>
-</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/domains.xml
----------------------------------------------------------------------
diff --git a/en-US/domains.xml b/en-US/domains.xml
deleted file mode 100644
index f348fe8..0000000
--- a/en-US/domains.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-
-<section id="domains">
- <title>Domains</title>
- <para>If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password.</para>
- </section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/dynamic-compute-offerings.xml
----------------------------------------------------------------------
diff --git a/en-US/dynamic-compute-offerings.xml b/en-US/dynamic-compute-offerings.xml
deleted file mode 100644
index dde791b..0000000
--- a/en-US/dynamic-compute-offerings.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
-%BOOK_ENTITIES;
-]>
-
-<!-- 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.
--->
-<section id="dynamic-compute-offerings">
- <title>Custom Compute Offering</title>
- <para>&PRODUCT; provides you the flexibility to specify the desired values for the number of CPU,
- CPU speed, and memory while deploying a VM. As an admin, you create a Compute Offering by
- marking it as custom, and the users will be able to customize this dynamic Compute Offering by
- specifying the memory, and CPU at the time of VM creation or upgrade. Use this offering to
- deploy VM by specifying custom values for the dynamic parameters. </para>
- <para>Dynamic Compute Offerings can be used in following cases: deploying a VM, changing the
- compute offering of a stopped VM and running VMs, which is nothing but scaling up. To support
- this feature a new field, Custom, has been added to the Create Compute Offering page in the UI.
- If the Custom field is checked, the user will be able to create a custom Compute Offering.
- During VM deployment you can specify desired values for number of CPU, CPU speed, and memory.
- See <xref linkend="creating-compute-offerings"/> for more information on this.</para>
- <para>To support this feature, usage events has been enhanced to register events for dynamically
- assigned resources. Usage events are registered when a VM is created from a custom compute
- offering, and upon changing the compute offering of a stopped or running VM. The values of the
- parameters, such as CPU, speed, RAM are recorded. </para>
-</section>