date:20151001

[1/2] git commit: updated refs/heads/master to 996c2f6

2015-10-01 Thread remi

Repository: cloudstack
Updated Branches:
  refs/heads/master 3ded3e900 -> 996c2f6dd


CLOUDSTACK-8924: Removed duplicate test from test_scale_vm.py


Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/33bdfc77
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/33bdfc77
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/33bdfc77

Branch: refs/heads/master
Commit: 33bdfc773a39d7ff245fb4f50299a7b6cc0391ef
Parents: 3ded3e9
Author: sanjeev 
Authored: Wed Sep 30 15:23:30 2015 +0530
Committer: sanjeev 
Committed: Wed Sep 30 15:23:30 2015 +0530

--
 test/integration/smoke/test_scale_vm.py | 76 +---
 1 file changed, 2 insertions(+), 74 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/33bdfc77/test/integration/smoke/test_scale_vm.py
--
diff --git a/test/integration/smoke/test_scale_vm.py 
b/test/integration/smoke/test_scale_vm.py
index 0a0f415..e4d7b40 100644
--- a/test/integration/smoke/test_scale_vm.py
+++ b/test/integration/smoke/test_scale_vm.py
@@ -118,7 +118,7 @@ class TestScaleVm(cloudstackTestCase):
 return
 
 @attr(hypervisor="xenserver")
-@attr(tags=["advanced", "basic"], required_hardware="true")
+@attr(tags=["advanced", "basic"], required_hardware="false")
 def test_01_scale_vm(self):
 """Test scale virtual machine
 """
@@ -202,76 +202,4 @@ class TestScaleVm(cloudstackTestCase):
 'Running',
 "Check the state of VM"
 )
-return
-
-@attr(tags=["advanced", "basic"], required_hardware="false")
-def test_02_scale_vm_without_hypervisor_specifics(self):
-# Validate the following
-# Scale up the vm and see if it scales to the new svc offering and is
-# finally in running state
-
-#VirtualMachine should be updated to tell cloudstack
-#it has PV tools
-#available and successfully scaled. We will only mock
-#that behaviour
-#here but it is not expected in production since the VM
-#scaling is not
-#guaranteed until tools are installed, vm rebooted
-
-self.virtual_machine.update(
-self.apiclient,
-isdynamicallyscalable='true')
-
-self.debug("Scaling VM-ID: %s to service offering: %s and state %s" % (
-self.virtual_machine.id,
-self.big_offering.id,
-self.virtual_machine.state
-))
-
-cmd = scaleVirtualMachine.scaleVirtualMachineCmd()
-cmd.serviceofferingid = self.big_offering.id
-cmd.id = self.virtual_machine.id
-self.apiclient.scaleVirtualMachine(cmd)
-
-list_vm_response = VirtualMachine.list(
-self.apiclient,
-id=self.virtual_machine.id
-)
-self.assertEqual(
-isinstance(list_vm_response, list),
-True,
-"Check list response returns a valid list"
-)
-
-self.assertNotEqual(
-list_vm_response,
-None,
-"Check virtual machine is in listVirtualMachines"
-)
-
-vm_response = list_vm_response[0]
-self.assertEqual(
-vm_response.id,
-self.virtual_machine.id,
-"Check virtual machine ID of scaled VM"
-)
-
-self.debug(
-"Scaling VM-ID: %s from service offering: %s to new service\
-offering %s and the response says %s" %
-(self.virtual_machine.id,
- self.virtual_machine.serviceofferingid,
- self.big_offering.id,
- vm_response.serviceofferingid))
-self.assertEqual(
-vm_response.serviceofferingid,
-self.big_offering.id,
-"Check service offering of the VM"
-)
-
-self.assertEqual(
-vm_response.state,
-'Running',
-"Check the state of VM"
-)
-return
+return
\ No newline at end of file

[2/2] git commit: updated refs/heads/master to 996c2f6

2015-10-01 Thread remi

Merge pull request #900 from sanju1010/scale_vm

CLOUDSTACK-8924: Removed duplicate test from test_scale_vm.pyPlease go through 
CS-8924 for more details.

* pr/900:
  CLOUDSTACK-8924: Removed duplicate test from test_scale_vm.py

Signed-off-by: Remi Bergsma 


Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/996c2f6d
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/996c2f6d
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/996c2f6d

Branch: refs/heads/master
Commit: 996c2f6ddec57fd5a644f6454911a1e303cc7d8f
Parents: 3ded3e9 33bdfc7
Author: Remi Bergsma 
Authored: Thu Oct 1 13:26:41 2015 +0200
Committer: Remi Bergsma 
Committed: Thu Oct 1 13:26:41 2015 +0200

--
 test/integration/smoke/test_scale_vm.py | 76 +---
 1 file changed, 2 insertions(+), 74 deletions(-)
--

Build failed in Jenkins: cloudstack-apidocs-master #2373

2015-10-01 Thread Apache Jenkins Server

See 

Changes:

[sanjeev] CLOUDSTACK-8924: Removed duplicate test from test_scale_vm.py

--
[...truncated 1733 lines...]
Aborted

Results :

Tests run: 91, Failures: 0, Errors: 0, Skipped: 3

[JENKINS] Recording test results
[JENKINS] Archiving disabled
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[4.841s]
[INFO] Apache CloudStack . SUCCESS [2.198s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [2.157s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [9.480s]
[INFO] Apache CloudStack Utils ... SUCCESS [19.424s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.257s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [5.201s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [4.357s]
[INFO] Apache CloudStack API . SUCCESS [11.446s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [4.007s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [3.271s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.244s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [3.896s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [2.188s]
[INFO] Apache CloudStack Core  SUCCESS [19.637s]
[INFO] Apache CloudStack Agents .. SUCCESS [5.431s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [3.477s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [1.820s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [10.804s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [3.663s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [2.522s]
[INFO] Apache CloudStack Server .. FAILURE [25.969s]
[INFO] Apache CloudStack Usage Server  SKIPPED
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SKIPPED
[INFO] Apache CloudStack Cloud Services .. SKIPPED
[INFO] Apache CloudStack Secondary Storage ... SKIPPED
[INFO] Apache CloudStack Secondary Storage Service ... SKIPPED
[INFO] Apache CloudStack Engine Storage Component  SKIPPED
[INFO] Apache CloudStack Engine Storage Volume Component . SKIPPED
[INFO] Apache CloudStack Engine Storage Image Component .. SKIPPED
[INFO] Apache CloudStack Engine Storage Data Motion Component  SKIPPED
[INFO] Apache CloudStack Engine Storage Cache Component .. SKIPPED
[INFO] Apache CloudStack Engine Storage Snapshot Component  SKIPPED
[INFO] Apache CloudStack Cloud Engine API  SKIPPED
[INFO] Apache CloudStack Cloud Engine Service  SKIPPED
[INFO] Apache CloudStack Plugin POM .. SKIPPED
[INFO] Apache CloudStack Plugin - API Rate Limit . SKIPPED
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SKIPPED
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SKIPPED
[INFO] Apache CloudStack Plugin - API SolidFire .. SKIPPED
[INFO] Apache CloudStack Plugin - API Discovery .. SKIPPED
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SKIPPED
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SKIPPED
[INFO] Apache CloudStack Plugin - Explicit Dedication Processor  SKIPPED
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner  
SKIPPED
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Implicit Dedication Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Skip Heurestics Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Host Allocator Random .. SKIPPED
[INFO] Apache CloudStack Plugin - Dedicated Resources  SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM  SKIPPED
[INFO] Apache CloudStack Plugin - Open vSwitch ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor XenServer ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor KVM . SKIPPED
[INFO] Apache CloudStack Plugin - RabbitMQ Event Bus . SKIPPED
[INFO] Apache CloudStack Plugin - In Memory Event Bus  SKIPPED
[INFO] Apache CloudStack Plugin - Kafka Event Bus  SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor Baremetal ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor UCS . SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor Hyper-V . SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM3 ... SKIPPED
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer  SKIPPED
[INFO] Apache CloudStack Plugin - Network Internal Load Balancer  SKIPPED

Build failed in Jenkins: cloudstack-apidocs-master #2374

2015-10-01 Thread Apache Jenkins Server

See 

--
[...truncated 1735 lines...]
Aborted

Results :

Tests run: 91, Failures: 0, Errors: 0, Skipped: 3

[JENKINS] Recording test results
[JENKINS] Archiving disabled
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache CloudStack Developer Tools - Checkstyle Configuration  SUCCESS 
[2.700s]
[INFO] Apache CloudStack . SUCCESS [1.103s]
[INFO] Apache CloudStack Maven Conventions Parent  SUCCESS [0.992s]
[INFO] Apache CloudStack Framework - Managed Context . SUCCESS [8.800s]
[INFO] Apache CloudStack Utils ... SUCCESS [16.802s]
[INFO] Apache CloudStack Framework ... SUCCESS [0.190s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [4.782s]
[INFO] Apache CloudStack Framework - Configuration ... SUCCESS [4.125s]
[INFO] Apache CloudStack API . SUCCESS [9.767s]
[INFO] Apache CloudStack Framework - REST  SUCCESS [2.527s]
[INFO] Apache CloudStack Framework - IPC . SUCCESS [3.087s]
[INFO] Apache CloudStack Cloud Engine  SUCCESS [0.186s]
[INFO] Apache CloudStack Cloud Engine API  SUCCESS [3.644s]
[INFO] Apache CloudStack Framework - Security  SUCCESS [2.137s]
[INFO] Apache CloudStack Core  SUCCESS [17.266s]
[INFO] Apache CloudStack Agents .. SUCCESS [4.467s]
[INFO] Apache CloudStack Framework - Clustering .. SUCCESS [3.417s]
[INFO] Apache CloudStack Framework - Event Notification .. SUCCESS [1.745s]
[INFO] Apache CloudStack Cloud Engine Schema Component ... SUCCESS [9.164s]
[INFO] Apache CloudStack Framework - Jobs  SUCCESS [3.527s]
[INFO] Apache CloudStack Cloud Engine Internal Components API  SUCCESS [2.489s]
[INFO] Apache CloudStack Server .. FAILURE [25.431s]
[INFO] Apache CloudStack Usage Server  SKIPPED
[INFO] Apache CloudStack Cloud Engine Orchestration Component  SKIPPED
[INFO] Apache CloudStack Cloud Services .. SKIPPED
[INFO] Apache CloudStack Secondary Storage ... SKIPPED
[INFO] Apache CloudStack Secondary Storage Service ... SKIPPED
[INFO] Apache CloudStack Engine Storage Component  SKIPPED
[INFO] Apache CloudStack Engine Storage Volume Component . SKIPPED
[INFO] Apache CloudStack Engine Storage Image Component .. SKIPPED
[INFO] Apache CloudStack Engine Storage Data Motion Component  SKIPPED
[INFO] Apache CloudStack Engine Storage Cache Component .. SKIPPED
[INFO] Apache CloudStack Engine Storage Snapshot Component  SKIPPED
[INFO] Apache CloudStack Cloud Engine API  SKIPPED
[INFO] Apache CloudStack Cloud Engine Service  SKIPPED
[INFO] Apache CloudStack Plugin POM .. SKIPPED
[INFO] Apache CloudStack Plugin - API Rate Limit . SKIPPED
[INFO] Apache CloudStack Plugin - Storage Volume default provider  SKIPPED
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider  SKIPPED
[INFO] Apache CloudStack Plugin - API SolidFire .. SKIPPED
[INFO] Apache CloudStack Plugin - API Discovery .. SKIPPED
[INFO] Apache CloudStack Plugin - ACL Static Role Based .. SKIPPED
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor  SKIPPED
[INFO] Apache CloudStack Plugin - Explicit Dedication Processor  SKIPPED
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner  
SKIPPED
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Implicit Dedication Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Skip Heurestics Planner  SKIPPED
[INFO] Apache CloudStack Plugin - Host Allocator Random .. SKIPPED
[INFO] Apache CloudStack Plugin - Dedicated Resources  SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM  SKIPPED
[INFO] Apache CloudStack Plugin - Open vSwitch ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor XenServer ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor KVM . SKIPPED
[INFO] Apache CloudStack Plugin - RabbitMQ Event Bus . SKIPPED
[INFO] Apache CloudStack Plugin - In Memory Event Bus  SKIPPED
[INFO] Apache CloudStack Plugin - Kafka Event Bus  SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor Baremetal ... SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor UCS . SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor Hyper-V . SKIPPED
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM3 ... SKIPPED
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer  SKIPPED
[INFO] Apache CloudStack Plugin - Network Internal Load Balancer  SKIPPED
[INFO] Apache CloudStack Framework - Spring Life Cycle ... SKIPPED
[INFO] Apache CloudStack

[18/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/writing-new-documentation.xml
--
diff --git a/en-US/writing-new-documentation.xml 
b/en-US/writing-new-documentation.xml
deleted file mode 100644
index 7557359..000
--- a/en-US/writing-new-documentation.xml
+++ /dev/null
@@ -1,100 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Writing &PRODUCT; Documentation
-&PRODUCT; documentation is written in DocBook xml format. Each guide 
defined with a publican configuration file refers to a DocBook 
book. 
-These books are defined in xml files in docs/en-US, for instance if 
we look at the Developers guide, its configuration file contains:
-
-xml_lang: en-US
-type: Book
-docname: Developers_Guide
-brand: cloudstack
-chunk_first: 1
-chunk_section_depth: 1
-
-The docname key gives you the basename of the 
DocBook file located in the en-US directory that contains the description of 
the book.
-Looking closely at Developers_Guide.xml we see that it contains 
book tags and several references to other xml files. These 
are the chapters of the book, currently they are:
-
-
-
-All these xml files are written in DocBook format.
-
-DocBook format is well http://www.docbook.org/tdg5/en/html/docbook.html";>documented, 
refer to the documentation for any questions about DocBook tags
-
-When writing documentation, you therefore need to located the 
book,chapter and section of the content you want to write/correct.
-Or create a new book,chapter,section.
-You will then learn much more about DocBook tagging. In order to 
write this chapter about documentation, I added the 
working-with-documentation.xmlfile describing a chapter in 
the Developer book and I created several sections within that chapter like 
so:
-
-
-
-
-Note the id witin the chapter tag, it represents the basename of the 
xml file describing the chapter.
-For translation purposes it is important that this basename be less 
than 50 characters long.
-
-This chapter also refers to xml files which contains each section. 
While you could embed the sections directly in the chapter file and as a matter 
of fact also write the chapters within a single book file. Breaking things up 
in smaller files at the granularity of the section, allows us to re-use any 
section to build different books.
-For completeness here is an example of a section:
-
-
-
-Happy Publicating and DocBooking.
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/xenserver-maintenance-mode.xml
--
diff --git a/en-US/xenserver-maintenance-mode.xml 
b/en-US/xenserver-maintenance-mode.xml
deleted file mode 100644
index b947278..000
--- a/en-US/xenserver-maintenance-mode.xml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-XenServer and Maintenance Mode
-For XenServer, you can take a server offline temporarily by using 
the Maintenance Mode feature in XenCenter. When you place a server into 
Maintenance Mode, all running VMs are automatically migrated from it to another 
host in the same pool. If the server is the pool master, a new master will also 
be selected for the pool. While a server is Maintenance Mode, you cannot create 
or start any VMs on it.
-To place a server in Maintenance 
Mode:
-
-In the Resources pane, select the server, then do one 
of the following:
-
-Right-click, then click Enter Maintenance Mode on 
the shortcut menu.
-
-On the Server menu, click Enter Maintenance 
Mode.
-   
- 
-Click Enter Maintenance Mode.
-
-The server's status in the Resources pane shows when all running VMs 
have been successfully migrated off the server.
-To take a server out of Maintenance 
Mode:
-
-In the Resources pane, select the server, then do one 
of the following:
-
-Right-click, then click Exit Maintenance Mode 
on the shortcut menu.
-
-On the Server menu, click Exit Maintenance 
Mode.
-
- 
-Click Exit Maintenance Mode.
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/xenserver-topology-req.xml
--
diff --git a/en-US/xenserver-topology-req.xml b/en-US/xenserver-topology-req.xml
deleted file mode 100644
index 12b9b07..000
--- a/en-US/xenserver-topology-req.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  XenServer Topol

[20/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/vm-snapshots.xml
--
diff --git a/en-US/vm-snapshots.xml b/en-US/vm-snapshots.xml
deleted file mode 100644
index 07cb5b5..000
--- a/en-US/vm-snapshots.xml
+++ /dev/null
@@ -1,178 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Virtual Machine Snapshots
-  (Supported on VMware and XenServer)
-  In addition to the existing &PRODUCT; ability to snapshot individual VM
-volumes, you can take a VM snapshot to preserve all the VM's data volumes 
as well as
-(optionally) its CPU/memory state. This is useful for quick restore of a 
VM. For example, you
-can snapshot a VM, then make changes such as software upgrades. If 
anything goes wrong, simply
-restore the VM to its previous state using the previously saved VM 
snapshot. 
-  The snapshot is created using the hypervisor's native snapshot 
facility. The VM snapshot includes
-not only the data volumes, but optionally also whether the VM is running 
or turned off (CPU
-state) and the memory contents. The snapshot is stored in &PRODUCT;'s 
primary storage.
-  VM snapshots can have a parent/child relationship. Each successive 
snapshot of the same VM
-is the child of the snapshot that came before it. Each time you take an 
additional snapshot of
-the same VM, it saves only the differences between the current state of 
the VM and the state
-stored in the most recent previous snapshot. The previous snapshot becomes 
a parent, and the new
-snapshot is its child. It is possible to create a long chain of these 
parent/child snapshots,
-which amount to a "redo" record leading from the current state of the VM 
back to the
-original.
-  If you need more information about VM snapshots on VMware, check out 
the VMware documentation and the
-VMware Knowledge Base, especially http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180";
-  >Understanding virtual machine snapshots.
-  
-Limitations on VM Snapshots
-
-  
-If a VM has some stored snapshots, you can't attach new volume 
to the VM or delete any
-  existing volumes. If you change the volumes on the VM, it would 
become impossible to
-  restore the VM snapshot which was created with the previous volume 
structure. If you want
-  to attach a volume to such a VM, first delete its snapshots.
-  
-  
-VM snapshots which include both data volumes and memory can't be 
kept if you change
-  the VM's service offering. Any existing VM snapshots of this type 
will be
-  discarded.
-  
-  
-You can't make a VM snapshot at the same time as you are taking 
a volume
-  snapshot.
-  
-  
-You should use only &PRODUCT; to create VM snapshots on hosts 
managed by
-  &PRODUCT;. Any snapshots that you make directly on the hypervisor 
will not be tracked in
-  &PRODUCT;.
-  
-
-  
-  
-Configuring VM Snapshots
-The cloud administrator can use global configuration variables to 
control the behavior of
-  VM snapshots. To set these variables, go through the Global Settings 
area of the &PRODUCT;
-  UI.
-
-  
-
-  
-Configuration Setting Name
-Description
-  
-
-
-  
-vmsnapshots.max
-The maximum number of VM snapshots that can be saved 
for any given virtual
-machine in the cloud. The total possible number of VM 
snapshots in the cloud is
-(number of VMs) * vmsnapshots.max. If the number of snapshots 
for any VM ever hits
-the maximum, the older ones are removed by the snapshot 
expunge job.
-  
-  
-vmsnapshot.create.wait
-Number of seconds to wait for a snapshot job to 
succeed before declaring
-failure and issuing an error.
-  
-
-  
-
-  
-  
-Using VM Snapshots
-To create a VM snapshot using the &PRODUCT; UI:
-
-  
-Log in to the &PRODUCT; UI as a user or administrator.
-  
-  
-Click Instances.
-  
-  
-Click the name of the VM you want to snapshot.
-  
-  
-Click the Take VM Snapshot button. 
-
-  
-
-  
-
-  If a snapshot is already in progress, then clicking this 
button will have no
-effect.
-
-
-  
-  
-Provide a name and description. These will be displayed in the 
VM Snapshots
-  list.
-  
-  
-(For running VMs only) If you want to include the VM's memory in 
the snapshot, click
-  the Memory checkbox. This saves the CPU and memory state of the 
virtual machine. If

[35/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/egress-firewall-rule.xml
--
diff --git a/en-US/egress-firewall-rule.xml b/en-US/egress-firewall-rule.xml
deleted file mode 100644
index 93d5a81..000
--- a/en-US/egress-firewall-rule.xml
+++ /dev/null
@@ -1,168 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Egress Firewall Rules in an Advanced Zone
-  The egress traffic originates from a private network to a public 
network, such as the
-Internet. By default, the egress traffic is blocked in default network 
offerings, so no outgoing
-traffic is allowed from a guest network to the Internet. However, you can 
control the egress
-traffic in an Advanced zone by creating egress firewall rules. When an 
egress firewall rule is
-applied, the traffic specific to the rule is allowed and the remaining 
traffic is blocked. When
-all the firewall rules are removed the default policy, Block, is 
applied.
-  
-Prerequisites and Guidelines
-Consider the following scenarios to apply egress firewall 
rules:
-
-  
-Egress firewall rules are supported on Juniper SRX and virtual 
router.
-  
-  
-The egress firewall rules are not supported on shared 
networks.
-  
-  
-Allow the egress traffic from specified source CIDR. The Source 
CIDR is part of guest
-  network CIDR.
-  
-  
-Allow the egress traffic with protocol TCP,UDP,ICMP, or 
ALL.
-  
-  
-Allow the egress traffic with protocol and destination port 
range. The port range is
-  specified for TCP, UDP or for ICMP type and code.
-  
-  
-The default policy is Allow for the new network offerings, 
whereas on upgrade existing
-  network offerings with firewall service providers will have the 
default egress policy
-  Deny.
-  
-
-  
-  
-Configuring an Egress Firewall Rule
-
-  
-Log in to the &PRODUCT; UI as an administrator or end user. 

-  
-  
-In the left navigation, choose Network.
-  
-  
-In Select view, choose Guest networks, then click the Guest 
network you want.
-  
-  
-To add an egress rule, click the Egress rules tab and fill out 
the following fields to
-  specify what type of traffic is allowed to be sent out of VM 
instances in this guest
-  network:
-
-  
-
-  
-  
-egress-firewall-rule.png: adding an egress firewall 
rule
-  
-
-
-  
-CIDR: (Add by CIDR only) To 
send traffic only 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 
destination. For example,
-  192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.
-  
-  
-Protocol: The networking 
protocol that VMs uses
-  to send outgoing traffic. 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.
-  
-  
-Start Port, End Port: (TCP, 
UDP only) A range of
-  listening ports that are the destination for the outgoing 
traffic. If you are opening
-  a single port, use the same number in both fields.
-  
-  
-ICMP Type, ICMP Code: (ICMP 
only) The type of
-  message and error code that are sent.
-  
-
-  
-  
-Click Add.
-  
-
-  
-  
-Configuring the Default Egress Policy
-The default egress policy for Isolated guest network is configured 
by using Network
-  offering.  Use the create network offering option to determine whether 
the default policy
-  should be block or allow all the traffic to the public network from a 
guest network.  Use this
-  network offering to create the network. If no policy is specified, by 
default all the traffic
-  is allowed from the guest network that you create by using this network 
offering.
-You have two options: Allow and Deny.
-
-  Allow
-  If you select Allow for a network offering, by default egress 
traffic is allowed.
-However, when an egress rule is configured for a guest network, rules 
are applied to block
-the specified traffic and rest are allowed. If no egress rules are 
configured for the
-network, egress traffic is accepted.
-
-
-  Deny
-  If you select Deny for a network offering, by default egress 
traffic for the guest
-network is blocked. However, when an egress rules is configured for a 
guest network, rules
-

[46/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/acquire-new-ip-for-vpc.xml
--
diff --git a/en-US/acquire-new-ip-for-vpc.xml b/en-US/acquire-new-ip-for-vpc.xml
deleted file mode 100644
index c0cb876..000
--- a/en-US/acquire-new-ip-for-vpc.xml
+++ /dev/null
@@ -1,88 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Acquiring a New IP Address for a VPC
-  When you acquire an IP address, all IP addresses are allocated to VPC, 
not to the guest
-networks within the VPC. The IPs are associated to the guest network only 
when the first
-port-forwarding, load balancing, or Static NAT rule is created for the IP 
or the network. IP
-can't be associated to more than one network at a time.
-  
-
-  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 to which you want to deploy 
the VMs.
-  The VPC page is displayed where all the tiers you created are 
listed in a
-diagram.
-  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 IP Addresses.
-  The Public IP Addresses page is displayed.
-
-
-  Click Acquire New IP, and click Yes in the confirmation 
dialog.
-  You are prompted for confirmation because, typically, IP addresses 
are a limited
-resource. Within a few moments, the new IP address should appear with 
the state Allocated.
-You can now use the IP address in port forwarding, load balancing, and 
static NAT
-rules.
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/add-additional-guest-network.xml
--
diff --git a/en-US/add-additional-guest-network.xml 
b/en-US/add-additional-guest-network.xml
deleted file mode 100644
index c684da0..000
--- a/en-US/add-additional-guest-network.xml
+++ /dev/null
@@ -1,65 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Adding an Additional Guest Network
-  
-
-  Log in to the &PRODUCT; UI as an administrator or end user. 
-
-
-  In the left navigation, choose Network.
-
-
-  Click Add guest network. 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 name of the zone 
this network applies to.
-Each zone is a broadcast domain, and therefore each zone has a 
different IP range for
-the guest network. The administrator must configure the IP range 
for each zone.
-
-
-  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 Create.
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/add-clusters-kvm-xenserver.xml
--
diff --git a/en-US/add-clusters-kvm-xenserver.xml 
b/en-US/add-clusters-kvm-xenserver.xml
deleted file mode 100644
index ad57371..000
--- a/en-US/add-clusters-kvm-xenserver.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Add Cluster: KVM or XenServer
-  These steps assume you have already installed the hypervisor on the 
hosts and logged in to
-the &PRODUCT; UI.
-  
-
-  In the left navigation, choose Infrastructure. In Zones, click 
View More, then click the
-zone in which you want to add the cluster.
-
-
-  Click the Compute tab.
-
-
-  In the Clusters node of the diagram, click View All.
-
-
-  Click Add Cluster.
-
-
-

[25/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/region-add.xml
--
diff --git a/en-US/region-add.xml b/en-US/region-add.xml
deleted file mode 100644
index 212047a..000
--- a/en-US/region-add.xml
+++ /dev/null
@@ -1,151 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-  Adding Regions (optional)
-Grouping your cloud resources into geographic regions is an optional 
step when provisioning the cloud.
-For an overview of regions, see .
-
-The First Region: The Default Region
-If you do not take action to define regions, then all the zones in 
your cloud will be
-automatically grouped into a single default region. This region is 
assigned the region
-ID of 1. You can change the name or URL of the default region by 
displaying the region in
-the &PRODUCT; UI and clicking the Edit button.
-
-
-Adding a Region
-Use these steps to add a second region in addition to the 
default region.
-  
-  Each region has its own &PRODUCT; instance. Therefore, 
the first step of creating a new region
-is to install the Management Server software, on one or 
more nodes, in the
-geographic area where you want to set up the new region. 
Use the steps in the
-Installation guide. When you come to the step where you 
set up the database, use
-the additional command-line flag -r 
 to set a
-  region ID for the new region. The default region is automatically 
assigned a
-  region ID of 1, so your first additional region might be region 
2.
-  cloudstack-setup-databases 
cloud:@localhost --deploy-as=root: -e 
 -m  -k 
 -r 
-  
-  By the end of the installation procedure, the Management 
Server should have been started. Be sure that the Management Server 
installation was successful and complete.
-  Now add the new region to region 1 in &PRODUCT;.
-  
-  Log in to &PRODUCT; in the first region as root 
administrator
-  (that is, log in to 
:8080/client).
-  In the left navigation bar, click 
Regions.
-  Click Add Region. In the dialog, fill in the 
following fields:
-  
-  ID. A unique identifying number. Use the 
same number
-  you set in the database during Management Server 
installation in the new region;
-  for example, 2.
-  Name. Give the new region a descriptive 
name.
-  Endpoint. The URL where you can log in 
to the Management Server in the new region.
-  This has the format 
:8080/client.
-  
-  
-  
-  
-  Now perform the same procedure in reverse. Log in to 
region 2, and add region 1.
-  Copy the account, user, and domain tables from the 
region 1 database to the region 2 database.
-  In the following commands, it is assumed that you have set the 
root password on the
-  database, which is a &PRODUCT; recommended best practice. 
Substitute your own MySQL
-  root password.
-  
-  First, run this command to copy the contents of 
the database:
-# mysqldump -u root -p 
-h  cloud account user domain > 
region1.sql
-  
-  Then run this command to put the data onto the 
region 2 database:
-# mysql -u root -p -h 
 cloud < region1.sql
-  
-  
-  
-  Remove project accounts. Run these commands on the 
region 2 database:
-  mysql> delete from account where type = 
5;
-  
-  Set the default zone as null:
-  mysql> update account set default_zone_id = 
null;
-  
-  Restart the Management Servers in region 
2.
-  
-
-
-Adding Third and Subsequent Regions
-To add the third region, and subsequent additional regions, the 
steps are similar to those for adding the second region.
-However, you must repeat certain steps additional times for each 
additional region:
-
-Install &PRODUCT; in each additional region. Set 
the region ID for each region during the database setup step.
-cloudstack-setup-databases 
cloud:@localhost --deploy-as=root: -e 
 -m  -k 
 -r 
-Once the Management Server is running, add your 
new region to all existing regions by
-repeatedly using the Add Region button in

[36/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

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..000
--- a/en-US/creating-vms.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Creating VMs
-  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.
-  
-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
-  
-  To create a VM from a template:
-  
-
-  Log in to the &PRODUCT; UI as an administrator or user.
-
-
-  In the left navigation bar, click Instances.
-
-
-  Click Add Instance.
-
-
-  Select a zone.
-
-
-  Select a template, then follow the steps in the wizard. For more 
information about how
-the templates came to be in this list, see .
-
-
-  Be sure that the hardware you have allows starting the selected 
service offering.
-
-
-  Click Submit and your VM will be created and started.
-  
-For security reason, the internal name of the VM is visible only 
to the root
-  admin.
-  
-
-  
-  To create a VM from an ISO:
-  
-(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.
-  
-  
-
-  Log in to the &PRODUCT; UI as an administrator or user.
-
-
-  In the left navigation bar, click Instances.
-
-
-  Click Add Instance.
-
-
-  Select a zone.
-
-
-  Select ISO Boot, and follow the steps in the wizard.
-
-
-  Click Submit and your VM will be created and started.
-
-
-  
-

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..000
--- a/en-US/customizing-dns.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Customizing the Network Domain Name
-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.
-
-Set the DNS suffix at the desired scope
-
-At the network level, the DNS suffix can be 
assigned through the UI when creating a new network, as described in  or with the updateNetwork command in 
the &PRODUCT; API.
-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.
-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.
-
-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.
-
-The source of the network domain that is used depends on the 
following rules.
-
-For all networks, if a network domain is specified as 
part of a network's own configuration, that value is used.
-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.
-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.
-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.
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/

[29/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/limit-accounts-domains.xml
--
diff --git a/en-US/limit-accounts-domains.xml b/en-US/limit-accounts-domains.xml
deleted file mode 100644
index 78a642b..000
--- a/en-US/limit-accounts-domains.xml
+++ /dev/null
@@ -1,371 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Limiting Resource Usage
-  &PRODUCT; allows you to control resource usage based on the types of 
resources, such as CPU,
-RAM, Primary storage, and Secondary storage.  A new set of resource types 
has been added to the
-existing pool of resources to support the new customization 
model—need-basis usage, such
-as large VM or small VM. The new resource types are now broadly classified 
as CPU, RAM, Primary
-storage, and Secondary storage. The root administrator is able to impose 
resource usage limit by
-the following resource types for Domain, Project, and Accounts. 
-  
-
-  CPUs
-
-
-  Memory (RAM)
-
-
-  Primary Storage (Volumes)
-
-
-  Secondary Storage (Snapshots, Templates, ISOs)
-
-  
-  To control the behaviour of this feature, the following configuration 
parameters have been
-added:
-  
-
-  
-
-  Parameter Name
-  Description
-
-  
-  
-
-  max.account.cpus
-  Maximum number of CPU cores that can be used for an 
account. 
-Default is 40.
-
-
-  max.account.ram (MB)
-  Maximum RAM that can be used for an account. 
-Default is 40960.
-
-
-  max.account.primary.storage (GB)
-  Maximum primary storage space that can be used for an 
account. 
-Default is 200.
-  
-
-
-  max.account.secondary.storage (GB)
-  Maximum secondary storage space that can be used for an 
account. 
-Default is 400.
-
-
-  max.project.cpus
-  
-Maximum number of CPU cores that can be used for an account. 

-Default is 40.
-  
-
-
-  max.project.ram (MB)
-  
-Maximum RAM that can be used for an account. 
-Default is 40960.
-  
-
-
-  max.project.primary.storage (GB)
-  
-Maximum primary storage space that can be used for an 
account. 
-Default is 200.
-  
-
-
-  max.project.secondary.storage (GB)
-  
-Maximum secondary storage space that can be used for an 
account. 
-Default is 400.
-  
-
-  
-
-  
-  
-User Permission
-The root administrator, domain administrators and users are able to 
list resources. Ensure
-  that proper logs are maintained in the vmops.log and
-api.log files.
-
-  
-The root admin will have the privilege to list and update 
resource limits.
-  
-  
-The domain administrators are allowed to list and change these 
resource limits only
-  for the sub-domains and accounts under their own domain or the 
sub-domains. 
-  
-  
-The end users will the privilege to list resource limits. Use 
the listResourceLimits
-  API.
-  
-
-  
-  
-Limit Usage Considerations
-
-  
-Primary or Secondary storage space refers to the stated size of 
the volume and not the
-  physical size— the actual consumed size on disk in case of 
thin provisioning.
-  
-  
-If the admin reduces the resource limit for an account and set 
it to less than the
-  resources that are currently being consumed, the existing 
VMs/templates/volumes are not
-  destroyed. Limits are imposed only if the user under that account 
tries to execute a new
-  operation using any of these resources. For example, the existing 
behavior in the case of
-  a VM are: 
-
-  
-migrateVirtualMachine: The users under that account will be 
able to migrate the
-  running VM into any other host without facing any limit 
issue.
-  
-  
-recoverVirtualMachine: Destroyed VMs cannot be 
recovered.
-  
-
-  
-  
-For any resource type, if a domain has limit X, sub-domains or 
accounts under that
-  domain can have there own limits. However, the sum of resource 
allocated to a sub-domain
-  or accounts under the domain at any point of time should not exceed 
the value X.
-For example, if a domain has the CPU limit of 40 and the 
sub-domain D1 and account A1
-  can have limits of 30 each, but at any point of time the resource 
allocated to D1 and A1
-  should not e

[09/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/database-replication.pot
--
diff --git a/pot/database-replication.pot b/pot/database-replication.pot
deleted file mode 100644
index 6efcacf..000
--- a/pot/database-replication.pot
+++ /dev/null
@@ -1,254 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Database Replication (Optional)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&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."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Creating a replica is not a backup solution. You should develop a 
backup procedure for the MySQL data that is distinct from replication."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Ensure that this is a fresh install with no data in the master."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Edit my.cnf on the master and add the following in the [mysqld] section 
below datadir."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"log_bin=mysql-bin\n"
-"server_id=1\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "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."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Restart the MySQL service:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"# service mysqld restart\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "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."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"# mysql -u root\n"
-"mysql> create user 'cloud-repl'@'172.16.1.%' identified by 'password';\n"
-"mysql> grant replication slave on *.* TO 'cloud-repl'@'172.16.1.%';\n"
-"mysql> flush privileges;\n"
-"mysql> flush tables with read lock;\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Leave the current MySQL session running."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In a new shell start a second MySQL session."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Retrieve the current position of the database."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"# mysql -u root\n"
-"mysql> show master status;\n"
-"+--+--+--+--+\n"
-"| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |\n"
-"+--+--+--+--+\n"
-"| mysql-bin.01 |  412 |  |  |\n"
-"+--+--+--+--+\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Note the file and the position that are returned by your instance."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Exit from this session."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Complete the master setup. Returning to your first session on the 
master, release the locks and exit MySQL."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"mysql> unlock tables;\n"
-""
-msgstr ""
-
-#. Tag: para

[15/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/add-iso.pot
--
diff --git a/pot/add-iso.pot b/pot/add-iso.pot
deleted file mode 100644
index eb1e630..000
--- a/pot/add-iso.pot
+++ /dev/null
@@ -1,215 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:56\n"
-"PO-Revision-Date: 2013-02-02T20:11:56\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Adding an ISO"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To make additional operating system or other software available for use 
with guest VMs, you can add an ISO. The ISO is typically thought of as an 
operating system image, but you can also add ISOs for other types of software, 
such as desktop applications that you want to be installed as part of a 
template."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the &PRODUCT; UI as an administrator or end user."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the left navigation bar, click Templates."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In Select View, choose ISOs."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click Add ISO."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the Add ISO screen, provide the following:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Name: Short name for the ISO image. 
For example, CentOS 6.2 64-bit."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Description: Display test for the 
ISO image. For example, CentOS 6.2 64-bit."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "URL: The URL that hosts the ISO 
image. The Management Server must be able to access this location via HTTP. If 
needed you can place the ISO image directly on the Management Server"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Zone: Choose the zone where you want 
the ISO to be available, or All Zones to make it available throughout 
&PRODUCT;."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Bootable: Whether or not a guest 
could boot off this ISO image. For example, a CentOS ISO is bootable, a 
Microsoft Office ISO is not bootable."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "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."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If the operating system of your desired ISO image is listed, choose it."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If the OS Type of the ISO is not listed or if the ISO is not bootable, 
choose Other."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "(XenServer only) If you want to boot from this ISO in PV mode, choose 
Other PV (32-bit) or Other PV (64-bit)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "(KVM only) If you choose an OS that is PV-enabled, the VMs created from 
this ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the 
VMs will have an IDE root disk. The PV-enabled types are:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fedora 13"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fedora 12"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fedora 11"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fedora 10"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fedora 9"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Other PV"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Debian GNU/Linux"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "CentOS 5.3"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "CentOS 5.4"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "CentOS 5.5"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Red Hat Enterprise Linux 5.3"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Red Hat Enterprise Linux 5.4"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Red Hat Enterprise Linux 5.5"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Red Hat Enterprise Linux 6"
-msg

[33/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/gsoc-imduffy15.xml
--
diff --git a/en-US/gsoc-imduffy15.xml b/en-US/gsoc-imduffy15.xml
deleted file mode 100644
index 652152f..000
--- a/en-US/gsoc-imduffy15.xml
+++ /dev/null
@@ -1,395 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Ians's 2013 GSoC Proposal
-This chapter describes Ians 2013 Google Summer of Code project 
within the &PRODUCT; ASF project. It is a copy paste of the submitted 
proposal.
-   
-   LDAP user provisioning
-   
-   "Need to automate the way the LDAP users are 
provisioned into cloud stack. This will mean better
-   integration with a LDAP server, ability to import users 
and a way to define how the LDAP user
-   maps to the cloudstack users."
-   
-   
-   
-   Abstract
-   
-   The aim of this project is to provide an more effective 
mechanism to provision users from LDAP
-   into cloudstack. Currently cloudstack enables LDAP 
authentication. In this authentication users
-   must be first setup in cloudstack. Once the user is 
setup in cloudstack they can authenticate
-   using their LDAP username and password. This project 
will improve Cloudstack LDAP integration
-   by enabling users be setup automatically using their 
LDAP credential
-   
-   
-   
-   Deliverables
-   
-   
-   Service that retrieves a list of LDAP 
users from a configured group
-   
-   
-   Extension of the cloudstack UI "Add User" 
screen to offer user list from LDAP
-   
-   
-   Add service for saving new user it 
details from LDAP
-   
-   
-   BDD unit and acceptance automated 
testing
-   
-   
-   Document change details
-   
-   
-   
-   
-   Quantifiable Results
-   
-   
-   
-   
-   Given
-   An administrator wants 
to add new user to cloudstack and LDAP is setup in cloudstack
-   
-   
-   When
-   The administrator opens 
the "Add User" screen
-   
-   
-   Then
-   A table of users appears 
for the current list of users (not already created on cloudstack) from the LDAP 
group displaying their usernames, given name and email address. The timezone 
dropdown will still be available beside each user
-   
-   
-   
-   
-   
-   
-   
-   
-   
-   Given
-   An administrator wants 
to add new user to cloudstack and LDAP is not setup in cloudstack
-   
-   
-   When
-   The administrator opens 
the "Add User" screen
-   
-   
-   Then
-   The current add user 
screen and functionality is provided
-   
-   
-   
-   
-   
-   
-   
-   
-   
-   Given
-   An administrator wants 
to add new user to cloudstack and LDAP is setup in cloudstack
-   
-   
-

[31/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-kvm-install-flow.xml
--
diff --git a/en-US/hypervisor-kvm-install-flow.xml 
b/en-US/hypervisor-kvm-install-flow.xml
deleted file mode 100644
index aa19e47..000
--- a/en-US/hypervisor-kvm-install-flow.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-KVM Hypervisor Host Installation
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-  http://www.w3.org/2001/XInclude"; />
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-kvm-requirements.xml
--
diff --git a/en-US/hypervisor-kvm-requirements.xml 
b/en-US/hypervisor-kvm-requirements.xml
deleted file mode 100644
index cdfc808..000
--- a/en-US/hypervisor-kvm-requirements.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-System Requirements for KVM Hypervisor Hosts
-  KVM is included with a variety of Linux-based operating systems. 
Although you are not required to run these distributions, the following are 
recommended:
-  
-CentOS / RHEL: 6.3
-Ubuntu: 12.04(.1)
-  
-  The main requirement for KVM hypervisors is the libvirt and Qemu 
version. No matter what
-Linux distribution you are using, make sure the following requirements are 
met:
-  
-libvirt: 0.9.4 or higher
-Qemu/KVM: 1.0 or higher
-  
-  The default bridge in &PRODUCT; is the Linux native bridge 
implementation (bridge module). &PRODUCT; includes an option to work with 
OpenVswitch, the requirements are listed below
-  
-libvirt: 0.9.11 or higher
-openvswitch: 1.7.1 or higher
-  
-  In addition, the following hardware requirements apply:
-  
-Within a single cluster, the hosts must be of the same 
distribution version.
-All hosts within a cluster must be homogenous. The CPUs 
must be of the same type, count, and feature flags.
-Must support HVM (Intel-VT or AMD-V 
enabled)
-64-bit x86 CPU (more cores results in better 
performance)
-4 GB of memory
-At least 1 NIC
-When you deploy &PRODUCT;, the hypervisor host must not 
have any VMs already running
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/hypervisor-support-for-primarystorage.xml
--
diff --git a/en-US/hypervisor-support-for-primarystorage.xml 
b/en-US/hypervisor-support-for-primarystorage.xml
deleted file mode 100644
index c48d85b..000
--- a/en-US/hypervisor-support-for-primarystorage.xml
+++ /dev/null
@@ -1,119 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Hypervisor Support for Primary Storage
-  The following table shows storage options and parameters for different 
hypervisors.
-  
-
-  
-  
-  
-  
-  
-  
-
-  
-  VMware vSphere
-  Citrix XenServer
-  KVM
-  Hyper-V
-
-  
-  
-
-  Format for 
Disks, Templates, and
-  Snapshots
-  VMDK
-  VHD
-  QCOW2
-  VHD
-Snapshots are not supported.
-
-
-  iSCSI 
support
-  VMFS
-  Clustered LVM
-  Yes, via Shared Mountpoint
-  No
-
-
-  Fiber Channel 
support
-  VMFS
-  Yes, via Existing SR
-  Yes, via Shared Mountpoint
-  No
-
-
-  NFS 
support
-  Y
-  Y
-  Y
-  No
-
-
-  Local storage 
support
-  Y
-  Y
-  Y
-  Y
-
-
-  Storage 
over-provisioning
-  NFS and iSCSI
-  NFS
-  NFS
-  No
-
-
-  SMB/CIFS
-  No
-  No
-  No
-  Yes
-
-  
-
-  
-  XenServer uses a clustered LVM system to store VM images on iSCSI and 
Fiber Channel volumes
-and does not support over-provisioning in the hypervisor. The storage 
server itself, however,
-can support thin-provisioning. As a result the &PRODUCT; can still support 
storage
-over-provisioning by running on thin-provisioned storage volumes.
-  KVM supports "Shared Mountpoint" storage. A shared mountpoint is a 
file system path local to
-e

[13/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/aws-ec2-supported-commands.pot
--
diff --git a/pot/aws-ec2-supported-commands.pot 
b/pot/aws-ec2-supported-commands.pot
deleted file mode 100644
index 9ffd9f4..000
--- a/pot/aws-ec2-supported-commands.pot
+++ /dev/null
@@ -1,665 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:57\n"
-"PO-Revision-Date: 2013-02-02T20:11:57\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Supported AWS API Calls"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The following Amazon EC2 commands are supported by &PRODUCT; when the 
AWS API compatible interface is enabled. For a few commands, there are 
differences between the &PRODUCT; and Amazon EC2 versions, and these 
differences are noted. The underlying SOAP call for each command is also given, 
for those who have built tools using those calls."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Elastic IP API mapping"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "EC2 command"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "SOAP call"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "&PRODUCT; API call"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-allocate-address"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "AllocateAddress"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "associateIpAddress"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-associate-address"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "AssociateAddress"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "enableStaticNat"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-describe-addresses"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DescribeAddresses"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "listPublicIpAddresses"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-diassociate-address"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DisassociateAddress"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "disableStaticNat"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-release-address"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ReleaseAddress"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "disassociateIpAddress"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Availability Zone API mapping"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-describe-availability-zones"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DescribeAvailabilityZones"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "listZones"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Images API mapping"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-create-image"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "CreateImage"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "createTemplate"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-deregister"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DeregisterImage"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DeleteTemplate"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-describe-images"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DescribeImages"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "listTemplates"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-register"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "RegisterImage"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "registerTemplate"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Image Attributes API mapping"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-describe-image-attribute"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "DescribeImageAttribute"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "listTemplatePermissions"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ec2-modify-image-attribute"
-msgstr ""
-
-#. Tag: entry
-#, no-c-format
-msgid "ModifyImageAttribute"
-msgstr ""
-
-#. T

[03/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/provisioning-auth-api.pot
--
diff --git a/pot/provisioning-auth-api.pot b/pot/provisioning-auth-api.pot
deleted file mode 100644
index 671e641..000
--- a/pot/provisioning-auth-api.pot
+++ /dev/null
@@ -1,40 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Provisioning and Authentication API"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&PRODUCT; expects that a customer will have their own user provisioning 
infrastructure. It provides APIs to integrate with these existing systems where 
the systems call out to &PRODUCT; to add/remove users.."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&PRODUCT; supports pluggable authenticators. By default, &PRODUCT; 
assumes it is provisioned with the userâs password, and as a result 
authentication is done locally. However, external authentication is possible as 
well. For example, see Using an LDAP Server for User Authentication."
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/provisioning-steps-overview.pot
--
diff --git a/pot/provisioning-steps-overview.pot 
b/pot/provisioning-steps-overview.pot
deleted file mode 100644
index 8d2873a..000
--- a/pot/provisioning-steps-overview.pot
+++ /dev/null
@@ -1,85 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Overview of Provisioning Steps"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "After the Management Server is installed and running, you can add the 
compute resources for it to manage. For an overview of how a &PRODUCT; cloud 
infrastructure is organized, see ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To provision the cloud infrastructure, or to scale it up at any time, 
follow these procedures:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the root password. See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add a zone. See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more pods (optional). See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more clusters (optional). See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more hosts (optional). See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add primary storage. See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add secondary storage. See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Initialize and test the new cloud. See ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When you have finished these steps, you will have a deployment with the 
following basic structure:"
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5

[08/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/events-log.pot
--
diff --git a/pot/events-log.pot b/pot/events-log.pot
deleted file mode 100644
index bdfb9c2..000
--- a/pot/events-log.pot
+++ /dev/null
@@ -1,35 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Event Logs"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are two types of events logged in the &PRODUCT; Event Log. 
Standard events log the success or failure of an event and can be used to 
identify jobs or processes that have failed. There are also long running job 
events. Events for asynchronous jobs log when a job is scheduled, when it 
starts, and when it completes. Other long running synchronous jobs log when a 
job starts, and when it completes. Long running synchronous and asynchronous 
event logs can be used to gain more information on the status of a pending job 
or can be used to identify a job that is hanging or has not started. The 
following sections provide more information on these events.."
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/events.pot
--
diff --git a/pot/events.pot b/pot/events.pot
deleted file mode 100644
index 24a646e..000
--- a/pot/events.pot
+++ /dev/null
@@ -1,30 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Events"
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/example-LDAP-configuration-commands.pot
--
diff --git a/pot/example-LDAP-configuration-commands.pot 
b/pot/example-LDAP-configuration-commands.pot
deleted file mode 100644
index 693bf19..000
--- a/pot/example-LDAP-configuration-commands.pot
+++ /dev/null
@@ -1,82 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"

[22/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/system-vm-template.xml
--
diff --git a/en-US/system-vm-template.xml b/en-US/system-vm-template.xml
deleted file mode 100644
index a9477f3..000
--- a/en-US/system-vm-template.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-The System VM Template
-The System VMs come from a single template.  The System VM has the 
following characteristics:
-
-Debian 6.0 ("Squeeze"), 2.6.32 kernel with the latest 
security patches from the Debian security APT repository
-Has a minimal set of packages installed thereby 
reducing the attack surface
-32-bit for enhanced performance on 
Xen/VMWare
-pvops kernel with Xen PV drivers, KVM virtio drivers, 
and VMware tools for optimum performance on all hypervisors
-Xen tools inclusion allows performance 
monitoring
-Latest versions of HAProxy, iptables, IPsec, and 
Apache from debian repository ensures improved security and 
speed
-Latest version of JRE from Sun/Oracle ensures improved 
security and speed
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/tagging-resources.xml
--
diff --git a/en-US/tagging-resources.xml b/en-US/tagging-resources.xml
deleted file mode 100644
index 31ee382..000
--- a/en-US/tagging-resources.xml
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-   Using Tags to Organize Resources in the Cloud
-A tag is a key-value pair that stores metadata about a resource 
in the cloud. Tags are
-useful for categorizing resources. For example, you can tag a user 
VM with a
-value that indicates the user's city of residence. In this case, 
the key would
-be "city" and the value might be "Toronto" or "Tokyo." You can 
then request
-&PRODUCT; to find all resources that have a given tag; for 
example, VMs for
-users in a given city.
-You can tag a user virtual machine, volume, snapshot, guest 
network, template,
-ISO, firewall rule, port forwarding rule, public IP address, 
security group,
-load balancer rule, project, VPC, network ACL, or static route. 
You can not tag
-a remote access VPN.
-You can work with tags through the UI or through the API 
commands createTags,
-deleteTags, and listTags. You can define multiple tags for each 
resource. There
-is no limit on the number of tags you can define. Each tag can be 
up to 255
-characters long. Users can define tags on the resources they own, 
and
-administrators can define tags on any resources in the 
cloud.
-An optional input parameter, "tags," exists on many of the list* 
API commands. 
-The following example shows how to use this new parameter to find 
all the volumes
-having tag region=canada OR tag city=Toronto:
-command=listVolumes
-   &listAll=true
-   &tags[0].key=region
-   &tags[0].value=canada
-   &tags[1].key=city
-   &tags[1].value=Toronto
-The following API commands have the "tags" input 
parameter:
-
-listVirtualMachines
-listVolumes
-listSnapshots
-listNetworks
-listTemplates
-listIsos
-listFirewallRules
-listPortForwardingRules
-listPublicIpAddresses
-listSecurityGroups
-listLoadBalancerRules
-listProjects
-listVPCs
-listNetworkACLs
-listStaticRoutes
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/template-iso-snapshot-usage-record-format.xml
--
diff --git a/en-US/template-iso-snapshot-usage-record-format.xml 
b/en-US/template-iso-snapshot-usage-record-format.xml
deleted file mode 100644
index 3f34f36..000
--- a/en-US/template-iso-snapshot-usage-record-format.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Template, ISO, and Snapshot Usage Record Format
-
-account â name of the account
-accountid â ID of the account
-domainid â ID of the domain in which this account 
resides
-zoneid â Zone where the usage 
occurred
-description â A string describing what the usage 
record is tracking
-usage â String representation of the usage, 
including the units of usage (e.g. 'Hrs' for hours)
-usagetyp

[06/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/installation_steps_overview.pot
--
diff --git a/pot/installation_steps_overview.pot 
b/pot/installation_steps_overview.pot
deleted file mode 100644
index c3a7186..000
--- a/pot/installation_steps_overview.pot
+++ /dev/null
@@ -1,135 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Overview of Installation Steps"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For anything more than a simple trial installation, you will need 
guidance for a variety of configuration choices. It is strongly recommended 
that you read the following:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Choosing a Deployment Architecture"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Choosing a Hypervisor: Supported Features"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Network Setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Storage Setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Best Practices"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Prepare"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Make sure you have the required hardware ready"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "(Optional) Fill out the preparation checklists"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install the &PRODUCT; software"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install the Management Server (choose single-node or multi-node)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the UI"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Provision your cloud infrastructure"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add a zone. Includes the first pod, cluster, and host"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more pods"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more clusters"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more hosts"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more primary storage"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add more secondary storage"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Try using the cloud"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Initialization and testing"
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/inter-vlan-routing.pot
--
diff --git a/pot/inter-vlan-routing.pot b/pot/inter-vlan-routing.pot
deleted file mode 100644
index d65e88e..000
--- a/pot/inter-vlan-routing.pot
+++ /dev/null
@@ -1,120 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "About Inter-VLAN Routing"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Inter-VLAN Routing

[05/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/management-server-install-nfs-shares.pot
--
diff --git a/pot/management-server-install-nfs-shares.pot 
b/pot/management-server-install-nfs-shares.pot
deleted file mode 100644
index b269c49..000
--- a/pot/management-server-install-nfs-shares.pot
+++ /dev/null
@@ -1,70 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Prepare NFS Shares"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&PRODUCT; needs a place to keep primary and secondary storage (see 
Cloud Infrastructure Overview). Both of these can be NFS shares. This section 
tells how to set up the NFS shares before adding the storage to &PRODUCT;."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Alternative Storage"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "NFS is not the only option for primary or secondary storage. For 
example, you may use a Ceph RDB cluster, GlusterFS, iSCSI, and otthers."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The requirements for primary and secondary storage are described in:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A production installation typically uses a separate NFS server. See 
."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can also use the Management Server node as the NFS server. This is 
more typical of a trial installation, but is technically possible in a larger 
deployment. See ."
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/management-server-install-overview.pot
--
diff --git a/pot/management-server-install-overview.pot 
b/pot/management-server-install-overview.pot
deleted file mode 100644
index 5eb7644..000
--- a/pot/management-server-install-overview.pot
+++ /dev/null
@@ -1,95 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Management Server Installation Overview"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This section describes installing the Management Server. There are two 
slightly different installation flows, depending on how many Management Server 
nodes will be in your cloud:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A single Management Server node, with MySQL on the same node."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Multiple Management Server nodes, with MySQL on a node separate from 
the Management Servers."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In either case, each machine must meet the system requirements 
described in System Requirements."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fo

[11/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/citrix-xenserver-installation.pot
--
diff --git a/pot/citrix-xenserver-installation.pot 
b/pot/citrix-xenserver-installation.pot
deleted file mode 100644
index 1a54c15..000
--- a/pot/citrix-xenserver-installation.pot
+++ /dev/null
@@ -1,1195 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:57\n"
-"PO-Revision-Date: 2013-02-02T20:11:57\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Citrix XenServer Installation for &PRODUCT;"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you want to use the Citrix XenServer hypervisor to run guest virtual 
machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your 
cloud. For an initial installation, follow the steps below. If you have 
previously installed XenServer and want to upgrade to another version, see 
."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "System Requirements for XenServer Hosts"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The host must be certified as compatible with one of the following. See 
the Citrix Hardware Compatibility Guide: http://hcl.xensource.com\";>http://hcl.xensource.com"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "XenServer 5.6 SP2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "XenServer 6.0"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "XenServer 6.0.2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You must re-install Citrix XenServer if you are going to re-use a host 
from a previous install."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Must support HVM (Intel-VT or AMD-V enabled)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Be sure all the hotfixes provided by the hypervisor vendor are applied. 
Track the release of hypervisor patches through your hypervisor vendorâs 
support channel, and apply patches as soon as possible after they are released. 
&PRODUCT; will not track or notify you of required hypervisor patches. It is 
essential that your hosts are completely up to date with the provided 
hypervisor patches. The hypervisor vendor is likely to refuse to support any 
system that is not up to date with patches."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "All hosts within a cluster must be homogenous. The CPUs must be of the 
same type, count, and feature flags."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "64-bit x86 CPU (more cores results in better performance)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Hardware virtualization support required"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "4 GB of memory"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "36 GB of local disk"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "At least 1 NIC"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Statically allocated IP Address"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When you deploy &PRODUCT;, the hypervisor host must not have any VMs 
already running"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The lack of up-do-date hotfixes can lead to data corruption and lost 
VMs."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "XenServer Installation Steps"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "From https://www.citrix.com/English/ss/downloads/\";>https://www.citrix.com/English/ss/downloads/,
 download the appropriate version of XenServer for your &PRODUCT; version (see 
). Install it using the 
Citrix XenServer Installation Guide."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "After installation, perform the following configuration steps, which 
are described in the next few sections:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Required"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Optional"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-msgstr ""
-
-

[17/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/Release_Notes.pot
--
diff --git a/pot/Release_Notes.pot b/pot/Release_Notes.pot
deleted file mode 100644
index e95dc9e..000
--- a/pot/Release_Notes.pot
+++ /dev/null
@@ -1,4478 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:56\n"
-"PO-Revision-Date: 2013-02-02T20:11:56\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Submitting Feedback and Getting Help"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The Apache CloudStack project has mailing lists for users and 
developers. These are the official channels of communication for the project 
and are the best way to get answers about using and contributing to CloudStack. 
It's a good idea to subscribe to the cloudstack-users mailing list if you've 
deployed or are deploying CloudStack into production, and even for test 
deployments."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The CloudStack developer's mailing list (cloudstack-dev) is for 
discussions about CloudStack development, and is the best list for discussing 
possible bugs in CloudStack. Anyone contributing to CloudStack should be on 
this mailing list."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can also report bugs in CloudStack using the https://issues.apache.org/jira/secure/CreateIssue!default.jspa\";>Apache 
Defect Tracking System."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To posts to the lists, you'll need to be subscribed. See the http://incubator.apache.org/cloudstack/mailing-lists.html\";>CloudStack 
Web site for instructions."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Upgrade Instructions"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Upgrade from 3.0.2 to 4.0.0-incubating"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Perform the following to upgrade from version 3.0.2 to version 
4.0.0-incubating. Note that some of the steps here are only required if you're 
using a specific hypervisor. The steps that are hypervisor-specific are called 
out with a note."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Ensure that you query your IP address usage records and process them or 
make a backup. During the upgrade you will lose the old IP address usage 
records."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Starting in 3.0.2, the usage record format for IP addresses is the same 
as the rest of the usage types. Instead of a single record with the assignment 
and release dates, separate records are generated per aggregation period with 
start and end dates. After upgrading, any existing IP address usage records in 
the old format will no longer be available."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The following upgrade instructions apply only if you're using VMware 
hosts. If you're not using VMware hosts, skip this step and move on to step 3: 
stopping all usage servers."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In each zone that includes VMware hosts, you need to add a new system 
VM template."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "While running the existing 3.0.2 system, log in to the UI as root 
administrator."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the left navigation bar, click Templates."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In Select view, click Templates."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click Register template."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The Register template dialog box is displayed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the Register template dialog box, specify the following values (do 
not change these):"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Field"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Value"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Name"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "systemvm-vmware-3.0.0"
-msgstr ""
-
-#. Tag: pa

[45/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/add-password-management-to-templates.xml
--
diff --git a/en-US/add-password-management-to-templates.xml 
b/en-US/add-password-management-to-templates.xml
deleted file mode 100644
index 581e564..000
--- a/en-US/add-password-management-to-templates.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Adding Password Management to Your Templates
-&PRODUCT; provides an optional password reset feature that allows 
users to set a temporary admin or root password as well as reset the existing 
admin or root password from the &PRODUCT; UI.
-To enable the Reset Password feature, you will need to download an 
additional script to patch your template. When you later upload the template 
into &PRODUCT;, you can specify whether reset admin/root password feature 
should be enabled for this template.
-The password management feature works always resets the account 
password on instance boot.  The script does an HTTP call to the virtual router 
to retrieve the account password that should be set.  As long as the virtual 
router is accessible the guest will have access to the account password that 
should be used.   When the user requests a password reset the management server 
generates and sends a new password to the virtual router for the account.  Thus 
an instance reboot is necessary to effect any password changes.
-If the script is unable to contact the virtual router during 
instance boot it will not set the password but boot will continue 
normally.
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/add-portforward-rule-vpc.xml
--
diff --git a/en-US/add-portforward-rule-vpc.xml 
b/en-US/add-portforward-rule-vpc.xml
deleted file mode 100644
index 5b1bb49..000
--- a/en-US/add-portforward-rule-vpc.xml
+++ /dev/null
@@ -1,117 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Adding a Port Forwarding Rule on a VPC
-  
-
-  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 to which you want to deploy 
the VMs.
-  The VPC page is displayed where all the tiers you created are 
listed in a
-diagram.
-  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 the IP address for which you want to create the rule, then 
click the Configuration
-tab.
-
-
-  In the Port Forwarding node of the diagram, click View All.
-
-
-  Select the tier to which you want to apply the rule.
-
-
-  Specify the following:
-  
-
-  Public Port: The port to 
which public traffic will
-be addressed on the IP address you acquired in the previous 
step.
-
-
-  Private Port: The port on 
which the instance is
-listening for forwarded public traffic.
-
-
-  Protocol: The communication 
protocol in use between
-the two ports.
-  
-
-  TCP
-
-
-  UDP
-
-  
-
-
-  Add VM: Click Add VM. Select 
the name of the
-instance to which this rule applies, and click Apply.
-  You can test the rule by opening an SSH session to the 
instance.
-
-  
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/add-primary-storage.xml
--
diff --git a/en-US/add-primary-storage.xml b/en-US/add-primary-storage.xml
deleted file mode 100644
index a43567f..000
--- a/en-US/add-primary-storage.xml
+++ /dev/null
@@ -1,108 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Adding Primary St

[43/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/append-displayname-vms.xml
--
diff --git a/en-US/append-displayname-vms.xml b/en-US/append-displayname-vms.xml
deleted file mode 100644
index 592a6e8..000
--- a/en-US/append-displayname-vms.xml
+++ /dev/null
@@ -1,84 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Appending a Display Name to the Guest VMâs Internal Name
-  Every guest VM has an internal name. The host uses the internal name 
to identify the guest
-VMs. &PRODUCT; gives you an option to provide a guest VM with a display 
name. You can set this
-display name as the internal name so that the vCenter can use it to 
identify the guest VM. A new
-global parameter, vm.instancename.flag, has now been added to achieve this 
functionality.
-  The default format of the internal name is
-i---, where instance.name 
is a global
-parameter. However, If vm.instancename.flag is set to true, and if a 
display name is provided
-during the creation of a guest VM, the display name is appended to the 
internal name of the
-guest VM on the host. This makes the internal name format as
-i---. The default value of 
vm.instancename.flag
-is set to false. This feature is intended to make the correlation between 
instance names and
-internal names easier in large data center deployments.
-  The following table explains how a VM name is displayed in different 
scenarios.
-  
-
-  
-  
-  
-  
-  
-  
-
-  User-Provided Display Name 
-  vm.instancename.flag
-  Hostname on the VM
-  Name on vCenter
-  Internal Name
-
-  
-  
-
-  Yes
-  True
-  Display name
-  
i---displayName
-  
i---displayName
-
-
-  No
-  True
-  UUID
-  
i---
-  
i---
-
-
-  Yes
-  False
-  Display name
-  
i---
-  
i---
-
-
-  No
-  False
-  UUID
-  
i---
-  
i---
-
-  
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/asynchronous-commands-example.xml
--
diff --git a/en-US/asynchronous-commands-example.xml 
b/en-US/asynchronous-commands-example.xml
deleted file mode 100644
index 330f125..000
--- a/en-US/asynchronous-commands-example.xml
+++ /dev/null
@@ -1,106 +0,0 @@
-
-
-
-Example
-
-The following shows an example of using an asynchronous command. 
Assume the API command:
-
command=deployVirtualMachine&zoneId=1&serviceOfferingId=1&diskOfferingId=1&templateId=1
-
-CloudStack will immediately return a job ID and any other 
additional data.
-
-  
-  1
- 100
- 
-
-Using the job ID, you can periodically poll for the results by 
using the queryAsyncJobResult command.
-
command=queryAsyncJobResult&jobId=1
-Three possible results could come from this query.
-Job is still pending:
-
-  
-  1
-  0
-  1
- 
-
-Job has succeeded:
-
-
-  1
-  1
-  0
- 0
-  object
-  
-
-450
-i-2-450-VM
-i-2-450-VM
-admin
-1
-ROOT
-2011-03-10T18:20:25-0800
-Running
-false
-1
-San Jose 1
-2
-905-13.sjc.lab.vmops.com
-1

[42/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/basic-zone-configuration.xml
--
diff --git a/en-US/basic-zone-configuration.xml 
b/en-US/basic-zone-configuration.xml
deleted file mode 100644
index 79d4ab8..000
--- a/en-US/basic-zone-configuration.xml
+++ /dev/null
@@ -1,319 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Basic Zone Configuration
-  
-
-  After you select Basic in the Add Zone wizard and click Next, you 
will be asked to enter
-the following details. Then click Next.
-  
-
-  Name. A name for the 
zone.
-
-
-  DNS 1 and 2. These are DNS 
servers for use by guest
-VMs in the zone. These DNS servers will be accessed via the public 
network you will add
-later. The public IP addresses for the zone must have a route to 
the DNS server named
-here.
-
-
-  Internal DNS 1 and Internal DNS 
2. These are DNS
-servers for use by system VMs in the zone (these are VMs used by 
&PRODUCT; itself, such
-as virtual routers, console proxies, and Secondary Storage VMs.) 
These DNS servers will
-be accessed via the management traffic network interface of the 
System VMs. The private
-IP address you provide for the pods must have a route to the 
internal DNS server named
-here.
-
-
-  Hypervisor. (Introduced in 
version 3.0.1) Choose
-the hypervisor for the first cluster in the zone. You can add 
clusters with different
-hypervisors later, after you finish adding the zone.
-
-
-  Network Offering. Your choice 
here determines what
-network services will be available on the network for guest 
VMs.
-  
-
-  
-  
-  
-
-  Network Offering
-  Description
-
-  
-  
-
-  
DefaultSharedNetworkOfferingWithSGService
-  If you want to enable security groups for guest 
traffic isolation,
-  choose this. (See Using Security Groups to Control 
Traffic to
-VMs.)
-
-
-  DefaultSharedNetworkOffering
-  If you do not need security groups, choose 
this.
-
-
-  
DefaultSharedNetscalerEIPandELBNetworkOffering
-  If you have installed a Citrix NetScaler 
appliance as part of your
-  zone network, and you will be using its Elastic IP and 
Elastic Load Balancing
-  features, choose this. With the EIP and ELB features, a 
basic zone with
-  security groups enabled can offer 1:1 static NAT and load
-balancing.
-
-  
-
-  
-
-
-  Network Domain. (Optional) If 
you want to assign a
-special domain name to the guest VM network, specify the DNS 
suffix.
-
-
-  Public. A public zone is 
available to all users. A
-zone that is not public will be assigned to a particular domain. 
Only users in that
-domain will be allowed to create guest VMs in this zone.
-
-  
-
-
-  Choose which traffic types will be carried by the physical 
network.
-  The traffic types are management, public, guest, and storage 
traffic. For more
-information about the types, roll over the icons to display their tool 
tips, or see Basic
-Zone Network Traffic Types. This screen starts out with some traffic 
types already assigned.
-To add more, drag and drop traffic types onto the network. You can 
also change the network
-name if desired.
-
-
-  Assign a network traffic label to each traffic type on the 
physical network. These
-labels must match the labels you have already defined on the 
hypervisor host. To assign each
-label, click the Edit button under the traffic type icon. A popup 
dialog appears where you
-can type the label, then click OK.
-  These traffic labels will be defined only for the hypervisor 
selected for the first
-cluster. For all other hypervisors, the labels can be configured after 
the zone is
-created.
-
-
-  Click Next.
-
-
-  (NetScaler only) If you chose the network offering for NetScaler, 
you have an additional
-screen to fill out. Provide the requested details to set up the 
NetScaler, then click
-Next.
-  
-
-  IP address. The NSIP 
(NetScaler IP) address of the
-NetScaler device.
-

[38/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

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..000
--- a/en-US/configure-acl.xml
+++ /dev/null
@@ -1,287 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%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.
-  
-

[27/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/network-usage-record-format.xml
--
diff --git a/en-US/network-usage-record-format.xml 
b/en-US/network-usage-record-format.xml
deleted file mode 100644
index 34b8f2d..000
--- a/en-US/network-usage-record-format.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Network Usage Record Format
-For network usage (bytes sent/received), the following fields exist 
in a usage record.
-
-account â name of the account
-accountid â ID of the account
-domainid â ID of the domain in which this 
account resides
-zoneid â Zone where the usage 
occurred
-description â A string describing what the usage 
record is tracking
-usagetype â A number representing the usage type 
(see Usage Types)
-rawusage â A number representing the actual 
usage in hours
-usageid â Device ID (virtual router ID or 
external device ID)
-type â Device type (domain router, external load 
balancer, etc.)
-startdate, enddate â The range of time for which 
the usage is aggregated; see Dates in the Usage Record
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/networking-in-a-pod.xml
--
diff --git a/en-US/networking-in-a-pod.xml b/en-US/networking-in-a-pod.xml
deleted file mode 100644
index 5a569bf..000
--- a/en-US/networking-in-a-pod.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   Networking in a Pod
-   The figure below illustrates network setup within a single pod. 
The hosts are connected to a
-   pod-level switch. At a minimum, the hosts should have one 
physical uplink to each switch.
-   Bonded NICs are supported as well. The pod-level switch is a 
pair of redundant gigabit
-   switches with 10 G uplinks.
-   
-   
-   
-   
-   
-   networksinglepod.png: diagram showing logical 
view of network in a pod
-   
-   
-   Servers are connected as follows:
-   
-   Storage devices are connected to only the network that 
carries management traffic.
-   Hosts are connected to networks for both management 
traffic and public traffic. 
-   Hosts are also connected to one or more networks 
carrying guest traffic.
-   
-   We recommend the use of multiple physical Ethernet cards to 
implement each network interface as well as redundant switch fabric in order to 
maximize throughput and improve reliability.
-   
-   

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/networking-in-a-zone.xml
--
diff --git a/en-US/networking-in-a-zone.xml b/en-US/networking-in-a-zone.xml
deleted file mode 100644
index e50efba..000
--- a/en-US/networking-in-a-zone.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   Networking in a Zone
-   The following figure illustrates the network setup within a 
single zone.
-   
-   
-   
-   
-   
-   networksetupzone.png: Depicts network setup in 
a single zone
-   
-   
-   A firewall for management traffic operates in the NAT mode. The 
network typically is assigned IP addresses in the 192.168.0.0/16 Class B 
private address space. Each pod is assigned IP addresses in the 192.168.*.0/24 
Class C private address space.
-   Each zone has its own set of public IP addresses. Public IP 
addresses from different zones do not overlap.
-   
-   

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/networking-overview.xml
--
diff --git a/en-US/networking-overview.xml b/en-US/networking-overview.xml
deleted file mode 100644
index a71fe95..000
--- a/en-US/networking-overview.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   Networking Overview
-   &PRODUCT; offers two types of networking scenario:
-   
-   
-   Basic. For AWS-style networking. 
Provides a single network where guest isolation can be provided through layer-3 
means such as security groups (IP address source filtering).
-

[16/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/Revision_History.pot
--
diff --git a/pot/Revision_History.pot b/pot/Revision_History.pot
deleted file mode 100644
index 3f213ce..000
--- a/pot/Revision_History.pot
+++ /dev/null
@@ -1,45 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:56\n"
-"PO-Revision-Date: 2013-02-02T20:11:56\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Revision History"
-msgstr ""
-
-#. Tag: firstname
-#, no-c-format
-msgid "Jessica"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "Tomechak"
-msgstr ""
-
-#. Tag: member
-#, no-c-format
-msgid "Initial creation of book by publican"
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/Revision_History_Install_Guide.pot
--
diff --git a/pot/Revision_History_Install_Guide.pot 
b/pot/Revision_History_Install_Guide.pot
deleted file mode 100644
index 632f931..000
--- a/pot/Revision_History_Install_Guide.pot
+++ /dev/null
@@ -1,65 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:56\n"
-"PO-Revision-Date: 2013-02-02T20:11:56\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Revision History"
-msgstr ""
-
-#. Tag: firstname
-#, no-c-format
-msgid "Jessica"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "Tomechak"
-msgstr ""
-
-#. Tag: firstname
-#, no-c-format
-msgid "Radhika"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "PC"
-msgstr ""
-
-#. Tag: firstname
-#, no-c-format
-msgid "Wido"
-msgstr ""
-
-#. Tag: surname
-#, no-c-format
-msgid "den Hollander"
-msgstr ""
-
-#. Tag: member
-#, no-c-format
-msgid "Initial publication"
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/SSL-keystore-path-and-password.pot
--
diff --git a/pot/SSL-keystore-path-and-password.pot 
b/pot/SSL-keystore-path-and-password.pot
deleted file mode 100644
index 54955c8..000
--- a/pot/SSL-keystore-path-and-password.pot
+++ /dev/null
@@ -1,35 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creat

[12/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/castor-with-cs.pot
--
diff --git a/pot/castor-with-cs.pot b/pot/castor-with-cs.pot
deleted file mode 100644
index 1637a6b..000
--- a/pot/castor-with-cs.pot
+++ /dev/null
@@ -1,123 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:57\n"
-"PO-Revision-Date: 2013-02-02T20:11:57\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Using the CAStor Back-end Storage with &PRODUCT;"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This section describes how to use a CAStor cluster as the back-end 
storage system for a &PRODUCT; S3 front-end. The CAStor back-end storage for 
&PRODUCT; extends the existing storage classes and allows the storage 
configuration attribute to point to a CAStor cluster."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This feature makes use of the &PRODUCT; server's local disk to spool 
files before writing them to CAStor when handling the PUT operations. However, 
a file must be successfully written into the CAStor cluster prior to the return 
of a success code to the S3 client to ensure that the transaction outcome is 
correctly reported."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The S3 multipart file upload is not supported in this release. You are 
prompted with proper error message if a multipart upload is attempted."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To configure CAStor:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Install &PRODUCT; 4.0.0-incubating by following the instructions given 
in the INSTALL.txt file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can use the S3 storage system in &PRODUCT; without setting up and 
installing the compute components."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Enable the S3 API by setting \"enable.s3.api = true\" in the Global 
parameter section in the UI and register a user."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For more information, see https://cwiki.apache.org/CLOUDSTACK/s3-api-in-cloudstack.html\";>S3 API in 
&PRODUCT;."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Edit the cloud-bridge.properties file and modify the \"storage.root\" 
parameter."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Set \"storage.root\" to the key word \"castor\"."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Specify a CAStor tenant domain to which content is written. If the 
domain is not specified, the CAStor default domain, specified by the 
\"cluster\" parameter in CAStor's node.cfg file, will be used."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Specify a list of node IP addresses, or set \"zeroconf\" and the 
cluster name. When using a static IP list with a large cluster, it is not 
necessary to include every node, only a few is required to initialize the 
client software."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For example:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "storage.root=castor domain=cloudstack 10.1.1.51 10.1.1.52 10.1.1.53"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In this example, the configuration file directs &PRODUCT; to write the 
S3 files to CAStor instead of to a file system, where the CAStor domain name is 
cloudstack, and the CAStor node IP addresses are those listed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "(Optional) The last value is a port number on which to communicate with 
the CAStor cluster. If not specified, the default is 80."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "#Static IP list with optional port\n"
-"storage.root=castor domain=cloudstack 10.1.1.51 10.1.1.52 10.1.1.53 80\n"
-"#Zeroconf locator for cluster named \"castor.example.com\"\n"
-"storage.root=castor domain=cloudstack zeroconf=castor.example.com"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Create the tenant domain within the CAStor storage cluster. If you omit 
this step

[01/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

Repository: cloudstack-docs
Updated Branches:
  refs/heads/master 24fae4506 -> f42520a53


http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/sysprep-windows-server-2008R2.pot
--
diff --git a/pot/sysprep-windows-server-2008R2.pot 
b/pot/sysprep-windows-server-2008R2.pot
deleted file mode 100644
index 91202d8..000
--- a/pot/sysprep-windows-server-2008R2.pot
+++ /dev/null
@@ -1,147 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "System Preparation for Windows Server 2008 R2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For Windows 2008 R2, you run Windows System Image Manager to create a 
custom sysprep response XML file. Windows System Image Manager is installed as 
part of the Windows Automated Installation Kit (AIK). Windows AIK can be 
downloaded from the Microsoft Download Center at the following location:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "http://www.microsoft.com/en-us/download/details.aspx?id=9085\"; 
/>Microsoft Download Center."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Use the following steps to run sysprep for Windows 2008 R2:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The steps outlined here are derived from the excellent guide by Charity 
Shelbourne, originally published at http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx\";
 />Windows Server 2008 Sysprep Mini-Setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Download and install the Windows AIK"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Windows AIK should not be installed on the Windows 2008 R2 VM you just 
created. Windows AIK should not be part of the template you create. It is only 
used to create the sysprep answer file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy the install.wim file in the \\sources directory of the Windows 
2008 R2 installation DVD to the hard disk. This is a very large file and may 
take a long time to copy. Windows AIK requires the WIM file to be writable."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the Windows System Image Manager, which is part of the Windows 
AIK."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the Windows Image pane, right click âSelect a Windows image or 
catalog fileâ to load the install.wim file you just copied."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Select the Windows 2008 R2 Edition"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You may be prompted with a warning that the catalog file cannot be 
opened. Click Yes to create a new catalog file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the Answer File pane, right click to create a new answer file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Generate the answer file from the Windows System Image Manager using 
the following steps:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The first page you need to automate is the Language and Country or 
Region Selection page. To automate this, expand Components in your Windows 
Image pane, right-click and add the Microsoft-Windows-International-Core 
setting to Pass 7 oobeSystem. In your Answer File pane, configure the 
InputLocale, SystemLocale, UILanguage, and UserLocale with the appropriate 
settings for your language and country or region. Should you have a question 
about any of these settings, you can right-click on the specific setting and 
select Help. This will open the appropriate CHM help file with more 
information, including examples on the setting you are attempting to configure."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You need to automate the Software License Terms Selection page, 
otherwise known as the End-User License Agreement (EULA). To do this, expand 
the Microsoft-Windows-Shell-S

[19/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/vnmc-cisco.xml
--
diff --git a/en-US/vnmc-cisco.xml b/en-US/vnmc-cisco.xml
deleted file mode 100644
index b0785fc..000
--- a/en-US/vnmc-cisco.xml
+++ /dev/null
@@ -1,400 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  External Guest Firewall Integration for Cisco VNMC (Optional)
-  Cisco Virtual Network Management Center (VNMC) provides centralized 
multi-device and policy
-management for Cisco Network Virtual Services. You can integrate Cisco 
VNMC with &PRODUCT; to
-leverage the firewall and NAT service offered by ASA 1000v Cloud Firewall. 
Use it in a Cisco
-Nexus 1000v dvSwitch-enabled cluster in &PRODUCT;. In such a deployment, 
you will be able to: 
-  
-
-  Configure Cisco ASA 1000v firewalls. You can configure one per 
guest network.
-
-
-  Use Cisco ASA 1000v firewalls to create and apply security 
profiles that contain ACL
-policy sets for both ingress and egress traffic.
-
-
-  Use Cisco ASA 1000v firewalls to create and apply Source NAT, Port 
Forwarding, and
-Static NAT policy sets.
-
-  
-  &PRODUCT; supports Cisco VNMC on Cisco Nexus 1000v dvSwich-enabled 
VMware
-hypervisors.
-  
-Using Cisco ASA 1000v Firewall, Cisco Nexus 1000v dvSwitch, and 
Cisco VNMC in a
-  Deployment
-
-  Guidelines
-  
-
-  Cisco ASA 1000v firewall is supported only in Isolated Guest 
Networks.
-
-
-  Cisco ASA 1000v firewall is not supported on VPC.
-
-
-  Cisco ASA 1000v firewall is not supported for load 
balancing.
-
-
-  When a guest network is created with Cisco VNMC firewall 
provider, an additional
-public IP is acquired along with the Source NAT IP. The Source NAT 
IP is used for the
-rules, whereas the additional IP is used to for the ASA outside 
interface. Ensure that
-this additional public IP is not released. You can identify this 
IP as soon as the
-network is in implemented state and before acquiring any further 
public IPs. The
-additional IP is the one that is not marked as Source NAT. You can 
find the IP used for
-the ASA outside interface by looking at the Cisco VNMC used in 
your guest
-network.
-
-
-  Use the public IP address range from a single subnet. You 
cannot add IP addresses
-from different subnets.
-
-
-  Only one ASA instance per VLAN is allowed because multiple 
VLANS cannot be trunked
-to ASA ports. Therefore, you can use only one ASA instance in a 
guest network.
-
-
-  Only one Cisco VNMC per zone is allowed.
-
-
-  Supported only in Inline mode deployment with load 
balancer.
-
-
-  The ASA firewall rule is applicable to all the public IPs in 
the guest network.
-Unlike the firewall rules created on virtual router, a rule 
created on the ASA device is
-not tied to a specific public IP.
-
-
-  Use a version of Cisco Nexus 1000v dvSwitch that support the 
vservice command. For
-example: nexus-1000v.4.2.1.SV1.5.2b.bin
-  Cisco VNMC requires the vservice command to be available on 
the Nexus switch to
-create a guest network in &PRODUCT;. 
-
-  
-
-
-  Prerequisites
-  
-
-  Configure Cisco Nexus 1000v dvSwitch in a vCenter 
environment.
-  Create Port profiles for both internal and external network 
interfaces on Cisco
-Nexus 1000v dvSwitch. Note down the inside port profile, which 
needs to be provided
-while adding the ASA appliance to &PRODUCT;.
-  For information on configuration, see .
-
-
-  Deploy and configure Cisco VNMC.
-  For more information, see http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html";
-  >Installing Cisco Virtual Network Management Center and 
http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html";
-  >Configuring Cisco Virtual Network Management 
Center.
-
-
-  Register Cisco Nexus 1000v dvSwitch with Cisco VNMC.
-  For more information, see http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301";
-  >Registering a Cisco Nexus 1000V with Cisco VNMC.
-
-
-

[10/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/configure-vpn.pot
--
diff --git a/pot/configure-vpn.pot b/pot/configure-vpn.pot
deleted file mode 100644
index 9d4e798..000
--- a/pot/configure-vpn.pot
+++ /dev/null
@@ -1,105 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Configuring VPN"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To set up VPN for the cloud:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the &PRODUCT; UI as an administrator or end user."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the left navigation, click Global Settings."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Set the following global configuration parameters."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "remote.access.vpn.client.ip.range â The range of IP addressess to be 
allocated to remote access VPN clients. The first IP in the range is used by 
the VPN server."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "remote.access.vpn.psk.length â Length of the IPSec key."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "remote.access.vpn.user.limit â Maximum number of VPN users per 
account."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To enable VPN for a particular network:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in as a user or administrator to the &PRODUCT; UI."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "In the left navigation, click Network."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the name of the network you want to work with."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click View IP Addresses."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click one of the displayed IP address names."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the Enable VPN button   
  
AttachDiskButton.png: button to attach a 
volume ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The IPsec key is displayed in a popup window."
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/configure-xenserver-dom0-memory.pot
--
diff --git a/pot/configure-xenserver-dom0-memory.pot 
b/pot/configure-xenserver-dom0-memory.pot
deleted file mode 100644
index 33e6b06..000
--- a/pot/configure-xenserver-dom0-memory.pot
+++ /dev/null
@@ -1,35 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Configure XenServer dom0 Memory"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "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 h

[02/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/set-monitor-total-vm-limits-per-host.pot
--
diff --git a/pot/set-monitor-total-vm-limits-per-host.pot 
b/pot/set-monitor-total-vm-limits-per-host.pot
deleted file mode 100644
index 50fe432..000
--- a/pot/set-monitor-total-vm-limits-per-host.pot
+++ /dev/null
@@ -1,35 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Set and Monitor Total VM Limits per Host"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The &PRODUCT; administrator should monitor the total number of VM 
instances in each cluster, and disable allocation to the cluster if the total 
is approaching the maximum that the hypervisor can handle. Be sure to leave a 
safety margin to allow for the possibility of one or more hosts failing, which 
would increase the VM load on the other hosts as the VMs are automatically 
redeployed. Consult the documentation for your chosen hypervisor to find the 
maximum permitted number of VMs per host, then use &PRODUCT; global 
configuration settings to set this as the default limit. Monitor the VM 
activity in each cluster at all times. Keep the total number of VMs below a 
safe level that allows for the occasional host failure. For example, if there 
are N hosts in the cluster, and you want to allow for one host in the cluster 
to be down at any given time, the total number of VM instances you can permit 
in the cluster is at most (N-1) * (per-host-limit). Once a cluster reaches this 
number 
 of VMs, use the &PRODUCT; UI to disable allocation of more VMs to the cluster."
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/set-per-project-resource-limits.pot
--
diff --git a/pot/set-per-project-resource-limits.pot 
b/pot/set-per-project-resource-limits.pot
deleted file mode 100644
index b791974..000
--- a/pot/set-per-project-resource-limits.pot
+++ /dev/null
@@ -1,75 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Setting Per-Project Resource Limits"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The &PRODUCT; root administrator or the domain administrator of the 
domain where the project resides can set new resource limits for an individual 
project. The project owner can set resource limits only if the owner is also a 
domain or root administrator."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The new limits must be below the global default limits set by the 
&PRODUCT; administrator (as described in ). If the project already owns 
more of a given type of resource than the new maximum, the resources are not 
affected; however, the project can not add any new resources of that type until 
t

[21/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/upload-template.xml
--
diff --git a/en-US/upload-template.xml b/en-US/upload-template.xml
deleted file mode 100644
index f270c89..000
--- a/en-US/upload-template.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   Uploading Templates
-vSphere Templates and ISOsIf you are 
uploading a template that was created using vSphere Client, be sure the OVA 
file does not contain an ISO. If it does, the deployment of VMs from the 
template will fail.
-   Templates are uploaded based on a URL. HTTP is the supported 
access protocol. Templates are frequently large files. You can optionally gzip 
them to decrease upload times.
-   To upload a template:
-   
-   In the left navigation bar, click 
Templates.
-   Click Register Template.
-   Provide the following:
-   
-   Name and 
Description. These will be shown in the UI, so
-   choose something 
descriptive.
-   URL. 
The Management Server will download the file from the
-   specified URL, such as 
http://my.web.server/filename.vhd.gz.
-   Zone. 
Choose the zone where you want the template to be
-   available, or All Zones to make 
it available throughout
-   &PRODUCT;.
-   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.
-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.
-
-
-   Hypervisor: The supported hypervisors are listed. Select 
the desired one.
-   Format. The format of the template upload file, such as 
VHD
-   or OVA.
-   Password 
Enabled. Choose Yes if your template has the
-   &PRODUCT; password change 
script installed. See Adding Password
-   Management to Your 
Templates
-   Extractable. Choose Yes if the template is available for 
extraction. If this option is selected, end users can 
-download a full image of a 
template.
-   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 
.
-   Featured. Choose Yes if you would like this template to 
be
-   more prominent for users to 
select. The template will appear in the Featured
-   Templates list. Only an 
administrator can make a template Featured.
-   
-   
-   
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/usage-record-format.xml
--
diff --git a/en-US/usage-record-format.xml b/en-US/usage-record-format.xml
deleted file mode 100644
index 7f7db06..000
--- a/en-US/usage-record-format.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Usage Record Format
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/usage-types.xml
--
diff --git a/en-US/usage-types.xml b/en-US/usage-types.xml
deleted file mode 100644
index 5a18902..000
--- a/en-US/usage-types.xml
+++ /dev/

[04/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/nfs-shares-on-management-server.pot
--
diff --git a/pot/nfs-shares-on-management-server.pot 
b/pot/nfs-shares-on-management-server.pot
deleted file mode 100644
index bec36a1..000
--- a/pot/nfs-shares-on-management-server.pot
+++ /dev/null
@@ -1,240 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:59\n"
-"PO-Revision-Date: 2013-02-02T20:11:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Using the Management Server as the NFS Server"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This section tells how to set up NFS shares for primary and secondary 
storage on the same node with the Management Server. This is more typical of a 
trial installation, but is technically possible in a larger deployment. It is 
assumed that you will have less than 16TB of storage on the host."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The exact commands for the following steps may vary depending on your 
operating system version."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On Ubuntu/Debian systems, you'll need to install the nfs-kernel-server 
package:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"$ sudo apt-get install nfs-kernel-server\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the Management Server host, create two directories that you will use 
for primary and secondary storage. For example:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"# mkdir -p /export/primary\n"
-"# mkdir -p /export/secondary\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To configure the new directories as NFS exports, edit /etc/exports. 
Export the NFS share(s) with rw,async,no_root_squash. For example:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "# vi /etc/exports"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Insert the following line."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "/export  *(rw,async,no_root_squash)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Export the /export directory."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "# exportfs -a"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Edit the /etc/sysconfig/nfs file."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "# vi /etc/sysconfig/nfs"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Uncomment the following lines:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"LOCKD_TCPPORT=32803\n"
-"LOCKD_UDPPORT=32769\n"
-"MOUNTD_PORT=892\n"
-"RQUOTAD_PORT=875\n"
-"STATD_PORT=662\n"
-"STATD_OUTGOING_PORT=2020\n"
-""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Edit the /etc/sysconfig/iptables file."
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "# vi /etc/sysconfig/iptables"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the following lines at the beginning of the INPUT chain where 
 is the network that you'll be using:"
-msgstr ""
-
-#. Tag: programlisting
-#, no-c-format
-msgid "\n"
-"-A INPUT -s  -m state --state NEW -p udp --dport 111 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 111 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 2049 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 32803 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p udp --dport 32769 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 892 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p udp --dport 892 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 875 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p udp --dport 875 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p tcp --dport 662 -j 
ACCEPT\n"
-"-A INPUT -s  -m state --state NEW -p udp --dpor

[24/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/secondary-storage-add.xml
--
diff --git a/en-US/secondary-storage-add.xml b/en-US/secondary-storage-add.xml
deleted file mode 100644
index 4f06987..000
--- a/en-US/secondary-storage-add.xml
+++ /dev/null
@@ -1,114 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-   Adding Secondary Storage
-Be sure there is nothing stored on the server. Adding the 
server to &PRODUCT; will destroy any existing data.
-
-When you create a new zone, the first secondary storage is added as 
part of that procedure. You can add secondary storage servers at any time to 
add more servers to an existing zone.
-
-To prepare for the zone-based Secondary Staging Store, 
you should have created and mounted an NFS share during Management Server 
installation.
-Make sure you prepared the system VM template during 
Management Server installation.
-Log in to the &PRODUCT; UI as root 
administrator.
-In the left navigation bar, click 
Infrastructure.
-In Secondary Storage, click View All.
-Click Add Secondary Storage.
-Fill in the following fields:
-
-Name: Give 
the storage a descriptive name.
-Provider: 
Choose the type of storage provider (such as S3,
-Swift, or NFS). NFS can be used for zone-based storage, and the 
others for region-wide
-object storage. Depending on which provider you choose, additional 
fields will appear.
-Fill in all the required fields for your selected provider. For 
more information,
-consult the provider's documentation (such as the S3 or Swift 
website). 
-  For Hyper-V, select SMB/CIFS.
-You can use only a single region-wide object 
storage account per region.
-For example, you can not mix both Swift and S3, or use S3 
accounts from multiple different users.
-Create NFS Secondary 
Staging Store: Be sure this box is
-checked, unless the zone already contains a secondary staging 
store. This would only be
-the case if you are upgrading an existing NFS secondary storage 
into an object storage,
-as described in .
-Upgrading from NFS to Object Storage in 
the Installation
-  Guide. In this case, you can skip the rest of the 
fields described below
-(Zone, NFS Server, and Path).
-If you are setting up a new zone, be sure the 
box is checked.
-This checkbox and the three fields below it must be filled 
in.
-Even when object storage (such as S3) is used as the 
secondary storage provider, an NFS
-staging storage in each zone is still 
required.
-
-  Zone: The zone where the NFS 
Secondary Staging
-Store is to be located.
-
-  
-Server. The IP address 
or DNS name of
-  the storage device.
-  
-  
-Path. The exported path 
from the
-  server.
-  
-  
-SMB Username: 
Applicable only if you select
-SMB/CIFS provider. The username of the account which has the 
necessary permissions to
-the SMB shares. The user must be part of the Hyper-V administrator 
group.
-  
-  
-SMB Password: 
Applicable only if you select
-SMB/CIFS provider. The password associated with the account.
-  
-  
-SMB Domain: Applicable 
only if you select
-SMB/CIFS provider. The Active Directory domain that the SMB share 
is a part of.
-  
-NFS server: 
The name of the zone's Secondary Staging
-Store.
-Path: The 
path to the zone's Secondary Staging Store.
-
-
-
-
-Adding an NFS Secondary Staging Store for Each Zone
-You can skip this section if you are upgrading an existing zone 
from NFS to object storage.
-  You only need to perform the steps below when setting up a new zone 
that does not yet have its NFS server.
-Every zone must have at least one NFS store provisioned; 
multiple NFS servers are
-allowed per zone. To provision an NFS Staging Store for a 
zone:
-
-To prepare for the zone-based Secondary Staging 
Store, you should have created and mounted an NFS share during Management 
Server installation.
-Make sure you prepared the system VM template 
during Management Server installation.Log in 
to the &PRODUCT; UI as root administrator.
-In the left navigation bar, click 
Infrastructure.
-In Second

[14/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/advanced-zone-configuration.pot
--
diff --git a/pot/advanced-zone-configuration.pot 
b/pot/advanced-zone-configuration.pot
deleted file mode 100644
index 2c05431..000
--- a/pot/advanced-zone-configuration.pot
+++ /dev/null
@@ -1,345 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:57\n"
-"PO-Revision-Date: 2013-02-02T20:11:57\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Advanced Zone Configuration"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "After you select Advanced in the Add Zone wizard and click Next, you 
will be asked to enter the following details. Then click Next."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Name. A name for the zone."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "DNS 1 and 2. These are DNS servers 
for use by guest VMs in the zone. These DNS servers will be accessed via the 
public network you will add later. The public IP addresses for the zone must 
have a route to the DNS server named here."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Internal DNS 1 and Internal DNS 2. 
These are DNS servers for use by system VMs in the zone(these are VMs used by 
&PRODUCT; itself, such as virtual routers, console proxies,and Secondary 
Storage VMs.) These DNS servers will be accessed via the management traffic 
network interface of the System VMs. The private IP address you provide for the 
pods must have a route to the internal DNS server named here."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Network Domain. (Optional) If you 
want to assign a special domain name to the guest VM network, specify the DNS 
suffix."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Guest CIDR. This is the CIDR that 
describes the IP addresses in use in the guest virtual networks in this zone. 
For example, 10.1.1.0/24. As a matter of good practice you should set different 
CIDRs for different zones. This will make it easier to set up VPNs between 
networks in different zones."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Hypervisor. (Introduced in version 
3.0.1) Choose the hypervisor for the first cluster in the zone. You can add 
clusters with different hypervisors later, after you finish adding the zone."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Public. A public zone is available 
to all users. A zone that is not public will be assigned to a particular 
domain. Only users in that domain will be allowed to create guest VMs in this 
zone."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Choose which traffic types will be carried by the physical network."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The traffic types are management, public, guest, and storage traffic. 
For more information about the types, roll over the icons to display their tool 
tips, or see . This 
screen starts out with one network already configured. If you have multiple 
physical networks, you need to add more. Drag and drop traffic types onto a 
greyed-out network and it will become active. You can move the traffic icons 
from one network to another; for example, if the default traffic types shown 
for Network 1 do not match your actual setup, you can move them down. You can 
also change the network names if desired."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "(Introduced in version 3.0.1) Assign a network traffic label to each 
traffic type on each physical network. These labels must match the labels you 
have already defined on the hypervisor host. To assign each label, click the 
Edit button under the traffic type icon within each physical network. A popup 
dialog appears where you can type the label, then click OK."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These traffic labels will be defined only for the hypervisor selected 
for the first cluster. For all other hypervisors, the labels can be configured 
after the zone is

[07/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/host-add.pot
--
diff --git a/pot/host-add.pot b/pot/host-add.pot
deleted file mode 100644
index c52ebaa..000
--- a/pot/host-add.pot
+++ /dev/null
@@ -1,60 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Adding a Host"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Before adding a host to the &PRODUCT; configuration, you must first 
install your chosen hypervisor on the host. &PRODUCT; can manage hosts running 
VMs under a variety of hypervisors."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The &PRODUCT; Installation Guide provides instructions on how to 
install each supported hypervisor and configure it for use with &PRODUCT;. See 
the appropriate section in the Installation Guide for information about which 
version of your chosen hypervisor is supported, as well as crucial additional 
steps to configure the hypervisor hosts for use with &PRODUCT;."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Be sure you have performed the additional &PRODUCT;-specific 
configuration steps described in the hypervisor installation section for your 
particular hypervisor."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Now add the hypervisor host to &PRODUCT;. The technique to use varies 
depending on the hypervisor."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-msgstr ""
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/pot/host-allocation.pot
--
diff --git a/pot/host-allocation.pot b/pot/host-allocation.pot
deleted file mode 100644
index cb6bee6..000
--- a/pot/host-allocation.pot
+++ /dev/null
@@ -1,50 +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.
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2013-02-02T20:11:58\n"
-"PO-Revision-Date: 2013-02-02T20:11:58\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Host Allocation"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The system automatically picks the most appropriate host to run each 
virtual machine. End users may specify the zone in which the virtual machine 
will be created. End users do not have control over which host will run the 
virtual machine instance."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&PRODUCT; administrators can specify that certain hosts should have a 
preference for particular types of guest instances. For example, an 
administrator could state that a host should have a preference to run Windows 
guests. The default host allocator will attempt to place guests of that OS type 
on such hosts first. If no such host is available, the allocator will place the 
instance wherever there is sufficient physical capacity."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Both vertical and horizontal allocation is allow

[32/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/host-allocation.xml
--
diff --git a/en-US/host-allocation.xml b/en-US/host-allocation.xml
deleted file mode 100644
index dddffd5..000
--- a/en-US/host-allocation.xml
+++ /dev/null
@@ -1,123 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Assigning VMs to Hosts
-At any point in time, each virtual machine instance is running on a 
single host.
-How does &PRODUCT; determine which host to place a VM on? There are 
several ways:
-
-Automatic default host allocation. &PRODUCT; can 
automatically pick
-the most appropriate host to run each virtual 
machine.
-Instance type preferences. &PRODUCT; administrators 
can specify that certain hosts should have a preference for particular types of 
guest instances.
-For example, an administrator could state that a host should have 
a preference to run Windows guests.
-The default host allocator will attempt to place guests of that OS 
type on such hosts first.
-If no such host is available, the allocator will place the 
instance wherever there is sufficient physical capacity.
-Vertical and horizontal allocation.
-Vertical allocation consumes all the resources of a given host 
before allocating any guests on a second host.
-This reduces power consumption in the cloud. Horizontal allocation 
places a guest on each host in a round-robin fashion.
-This may yield better performance to the guests in some 
cases.
-End user preferences.
-Users can not control exactly which host will run a given VM 
instance,
-but they can specify a zone for the VM.
-&PRODUCT; is then restricted to allocating the VM only to one of 
the hosts in that zone.
-Host tags. The administrator can assign tags to hosts. 
These tags can be used to
-specify which host a VM should use.
-The &PRODUCT; administrator decides whether to define host tags, 
then create a service offering using those tags and offer it to the user.
-
-Affinity groups.
-By defining affinity groups and assigning VMs to them, the user or 
administrator can
-influence (but not dictate) which VMs should run on separate hosts.
-This feature is to let users specify that certain VMs won't be on 
the same host.
-&PRODUCT; also provides a pluggable interface for 
adding new allocators.
-These custom allocators can provide any policy the administrator 
desires.
-
-
-Affinity Groups
-By defining affinity groups and assigning VMs to them, the user 
or administrator can
-influence (but not dictate) which VMs should run on separate hosts.
-This feature is to let users specify that VMs with the same 
âhost anti-affinityâ type wonât be on the same host.
-This serves to increase fault tolerance.
-If a host fails, another VM offering the same service (for 
example, hosting the user's website) is still up and running on another 
host.
-The scope of an affinity group is per user account.
-Creating a New Affinity Group
-To add an affinity group:
-
-Log in to the &PRODUCT; UI as an administrator or 
user.
-In the left navigation bar, click Affinity 
Groups.
-Click Add affinity group. In the dialog box, fill 
in the following fields:
-
-Name. Give the group a 
name.
-Description. Any desired text to tell more 
about the purpose of the group.
-Type. The only supported type shipped with 
&PRODUCT; is Host Anti-Affinity.
-This indicates that the VMs in this group should avoid 
being placed on the same VM with each other.
-If you see other types in this list, it means that 
your installation of &PRODUCT; has been extended
-with customized affinity group 
plugins.
-
-
-
-Assign a New VM to an Affinity Group
-To assign a new VM to an affinity group:
-
-Create the VM as usual, as described in .
-In the Add Instance wizard, there is a new Affinity tab where 
you can select the affinity group.
-
-Change Affinity Group for an Existing VM
-To assign an existing VM to an affinity 
group:
-
-Log in to the &PRODUCT; UI as an administrator or 
user.
-In the left navigation bar, click 
Instances.
-Click the name of the VM you want to work 
with.
-Stop the VM by clicking the Stop 
button.
-Click the Change Affinity button. 

-

[26/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/prepare-linux-template.xml
--
diff --git a/en-US/prepare-linux-template.xml b/en-US/prepare-linux-template.xml
deleted file mode 100755
index 84c2cde..000
--- a/en-US/prepare-linux-template.xml
+++ /dev/null
@@ -1,190 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   System preparation for Linux
- The following steps will prepare a basic Linux installation for 
templating.
- 
- 
- 
- Installation
- It is good practice to name your VM something generic during 
installation, this will ensure components such as LVM do not appear unique to a 
machine. It is recommended that the name of "localhost" is used for 
installation.
- For CentOS, it is necessary to take unique 
identification out of the interface configuration file, for this edit 
/etc/sysconfig/network-scripts/ifcfg-eth0 and change the content to  the 
following.
- 
- DEVICE=eth0
- TYPE=Ethernet
- BOOTPROTO=dhcp
- ONBOOT=yes
- 
- 
- The next steps updates the packages on the Template 
Master.
-
-
-Ubuntu
-
-sudo -i
-apt-get update
-apt-get upgrade -y
-apt-get install -y acpid ntp
-reboot
-
-
-
-CentOS
-
-ifup eth0
-yum update -y
-reboot
-
-
- 
- 
- 
- Password management
- If preferred, custom users (such as ones created during 
the Ubuntu installation) should be removed. First ensure the root user account 
is enabled by giving it a password and then login as root to continue.
- 
- sudo passwd root
- logout
- 
- As root, remove any custom user accounts created during the 
installation process.
- 
- deluser myuser --remove-home
- 
- 
- See  for 
instructions to setup the password management script, this will allow &PRODUCT; 
to change your root password from the web interface.
- 
- 
- Hostname Management
- CentOS configures the hostname by default on boot. 
Unfortunately Ubuntu does not have this functionality, for Ubuntu installations 
use the following steps.
- 
- 
- Ubuntu
- The hostname of a Templated VM is set by a custom 
script in /etc/dhcp/dhclient-exit-hooks.d, this script first checks if the 
current hostname is localhost, if true, it will get the host-name, domain-name 
and fixed-ip from the DHCP lease file and use those values to set the hostname 
and append the /etc/hosts file for local hostname resolution. Once this script, 
or a user has changed the hostname from localhost, it will no longer adjust 
system files regardless of it's new hostname. The script also recreates 
openssh-server keys, which should have been deleted before templating (shown 
below). Save the following script to 
/etc/dhcp/dhclient-exit-hooks.d/sethostname, and adjust the permissions.
- 
- 
- #!/bin/sh
- # dhclient change hostname script for Ubuntu
- oldhostname=$(hostname -s)
- if [ $oldhostname = 'localhost' ]
- then
-  sleep 10 # Wait for configuration to be written to disk
-  hostname=$(cat /var/lib/dhcp/dhclient.eth0.leases  |  awk ' 
/host-name/ { host = $3 }  END { printf host } ' | sed 's/[";]//g' )
-  fqdn="$hostname.$(cat /var/lib/dhcp/dhclient.eth0.leases  |  
awk ' /domain-name/ { domain = $3 }  END { printf domain } ' | sed 's/[";]//g')"
-  ip=$(cat /var/lib/dhcp/dhclient.eth0.leases  |  awk ' 
/fixed-address/ { lease = $2 }  END { printf lease } ' | sed 's/[";]//g')
-  echo "cloudstack-hostname: Hostname _localhost_ detected. 
Changing hostname and adding hosts."
-  echo " Hostname: $hostname \n FQDN: $fqdn \n IP: $ip"
-  # Update /etc/hosts
-  awk -v i="$ip" -v f="$fqdn" -v h="$hostname" "/^127/{x=1} 
!/^127/ && x { x=0; print i,f,h; } { print $0; }" /etc/hosts > 
/etc/hosts.dhcp.tmp
-  mv /etc/hosts /etc/hosts.dhcp.bak
-  mv /etc/hosts.dhcp.tmp /etc/hosts
-  # Rename Host
-  echo $hostname > /etc/hostname
-  hostname $hostname
-  # Recreate SSH2
-  dpkg-reconfig openssh-server
- fi
- ### End of Script ###
-
- chmod 774  /etc/dhcp/dhclient-exit-hooks.d/sethostname
-

[23/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/source-build.xml
--
diff --git a/en-US/source-build.xml b/en-US/source-build.xml
deleted file mode 100644
index a56d304..000
--- a/en-US/source-build.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Building &PRODUCT; from Source
-
-Prior to the 4.0.0 incubating release, Ant was used to build 
&PRODUCT;. A migration to Maven started in the 4.0.0 cycle, and has completed 
in 4.1.0.
-The website and the wiki contain up to date information on the 
build procedure at:
-
-https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+on+master+branch";>https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+on+master+branch
-https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment";>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment
-
-
-The overarching steps to build &PRODUCT; are:.
-
-Install the prerequisites and setup your 
environment
-Understand that various Maven profiles and build 
targets
-Deploy and test your build 
-If needed, learn how to build 
binaries
-
-
-
-Learning Maven is outside the scope of this documentation.
-Go to the Maven website at http://maven.apache.org/guides/getting-started/index.html";>http://maven.apache.org/guides/getting-started/index.html
-
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/source-prereqs.xml
--
diff --git a/en-US/source-prereqs.xml b/en-US/source-prereqs.xml
deleted file mode 100644
index 2e40a58..000
--- a/en-US/source-prereqs.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Prerequisites for building Apache CloudStack
-
-   There are a number of prerequisites needed to build &PRODUCT;. This
-   document assumes compilation on a Linux system that uses RPMs or DEBs
-   for package management. 
-
-
-   You will need, at a minimum, the following to compile &PRODUCT;:
-   
-  Maven (version 3)
-  Java (OpenJDK 1.6 or Java 7/OpenJDK 
1.7)
-  Apache Web Services Common Utilities 
(ws-commons-util) 
-  MySQL
-  MySQLdb (provides Python database 
API)
-  Tomcat 6 (not 6.0.35)
-  genisoimage
-  rpmbuild or dpkg-dev
-   
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/source.xml
--
diff --git a/en-US/source.xml b/en-US/source.xml
deleted file mode 100644
index ea3..000
--- a/en-US/source.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Building from Source
-The official &PRODUCT; release is always in source code form. You 
will likely be able to find "convenience binaries," the source is the canonical 
release. In this section, we'll cover acquiring the source release and building 
that so that you can deploy it using Maven or create Debian packages or 
RPMs.
-Note that building and deploying directly from source is typically 
not the most efficient way to deploy an IaaS. However, we will cover that 
method as well as building RPMs or Debian packages for deploying 
&PRODUCT;.
-The instructions here are likely version-specific. That is, the 
method for building from source for the 4.0.x series is different from the 
4.1.x series.
-If you are working with a unreleased version of &PRODUCT;, see the 
INSTALL.md file in the top-level directory of the release.
-http://www.w3.org/2001/XInclude"; /> 
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />  
-http://www.w3.org/2001/XInclude"; />  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/ssl.xml
--
diff --git a/en-US/ssl.xml b/en-US/ssl.xml
deleted file mode 100644
index 9aeb2f9..000
--- a/en-US/ssl.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-SSL (Optional)
-&PRODUCT; provides HTTP access in its default installation. There 
are a number of technologies and sites which choose to implement SSL. As a 
result, we have left &PRODUCT; to expose HTTP under the assumption that a site 
will implement its typ

[39/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/citrix-xenserver-installation.xml
--
diff --git a/en-US/citrix-xenserver-installation.xml 
b/en-US/citrix-xenserver-installation.xml
deleted file mode 100644
index 09d07aa..000
--- a/en-US/citrix-xenserver-installation.xml
+++ /dev/null
@@ -1,757 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Citrix XenServer Installation for &PRODUCT;
-  If you want to use the Citrix XenServer hypervisor to run guest 
virtual machines, install
-XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an 
initial installation,
-follow the steps below. If you have previously installed XenServer and 
want to upgrade to
-another version, see .
-  
-System Requirements for XenServer Hosts
-
-  
-The host must be certified as compatible with one of the 
following. See the Citrix
-  Hardware Compatibility Guide: http://hcl.xensource.com";
->http://hcl.xensource.com
-
-  
-XenServer 5.6 SP2
-  
-  
-XenServer 6.0
-  
-  
-XenServer 6.0.2
-  
-
-  
-  
-You must re-install Citrix XenServer if you are going to re-use 
a host from a previous
-  install.
-  
-  
-Must support HVM (Intel-VT or AMD-V enabled)
-  
-  
-Be sure all the hotfixes provided by the hypervisor vendor are 
applied. Track the
-  release of hypervisor patches through your hypervisor vendorâs 
support channel, and apply
-  patches as soon as possible after they are released. &PRODUCT; will 
not track or notify
-  you of required hypervisor patches. It is essential that your hosts 
are completely up to
-  date with the provided hypervisor patches. The hypervisor vendor is 
likely to refuse to
-  support any system that is not up to date with patches.
-  
-  
-All hosts within a cluster must be homogeneous. The CPUs must be 
of the same type,
-  count, and feature flags.
-  
-  
-Must support HVM (Intel-VT or AMD-V enabled in BIOS)
-  
-  
-64-bit x86 CPU (more cores results in better performance)
-  
-  
-Hardware virtualization support required
-  
-  
-4 GB of memory
-  
-  
-36 GB of local disk
-  
-  
-At least 1 NIC
-  
-  
-Statically allocated IP Address
-  
-  
-When you deploy &PRODUCT;, the hypervisor host must not have any 
VMs already
-  running
-  
-
-
-  The lack of up-do-date hotfixes can lead to data corruption and 
lost VMs.
-
-  
-  
-XenServer Installation Steps
-
-  
-From https://www.citrix.com/English/ss/downloads/";
->https://www.citrix.com/English/ss/downloads/, download 
the appropriate version
-  of XenServer for your &PRODUCT; version (see ). Install it using 
the Citrix XenServer
-Installation Guide.
-Older Versions of XenServer
-Note that you can download the most recent release of XenServer 
without having a Citrix account. If you wish to download older versions, you 
will need to create an account and look through the download archives.
-
-  
-  
-After installation, perform the following configuration steps, 
which are described in
-  the next few sections:
-
-  
-
-
-
-  
-Required
-Optional
-  
-
-
-  
-
-
-  
-  
-
-Set up SR if not using NFS, iSCSI, or local disk; 
see 
-  
-  
-
-
-  
-  
-
-
-  
-
-  
-
-  
-
-  
-  
-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 http://support.citrix.com/article/CTX126531";
->http://support.citrix.com/article/CTX126531. The article 
refers to XenServer 5.6,
-  but the same information applies to XenServer 6.0.
-  
-  
-Username and Password
-All XenServers in a cluster must have the same username and password 
as configured in
-  &PRODUCT;.
-  
-  
-Time Synchronization
-The host must be set to use NTP. All hosts in a pod must have the 
same time.
-
-  
-Install NTP.
-# yum install ntp
-  
-

[40/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/changed-API-commands-4.3.xml
--
diff --git a/en-US/changed-API-commands-4.3.xml 
b/en-US/changed-API-commands-4.3.xml
deleted file mode 100644
index 8c4d962..000
--- a/en-US/changed-API-commands-4.3.xml
+++ /dev/null
@@ -1,619 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  API Changes Introduced in 4.3
-  Here are the list of APIs changed as part of the 4.3 release.
- 
-  
-Hyper-V
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-addPrimaryStorage
-To this existing API, the following field has been 
added:
-  smb
-  
-  
-addImageStore
-To this existing API, the following field has been 
added:
-  smb
-  
-
-  
-
-  
-  
-Reporting CPU Sockets
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-listhost
-To this existing API, the following request parameter 
has been added:
-hypervisor.The new response parameter added is: 
cpusockets
-  cpusockets returns the number of CPU sockets on the 
host.
-  
-
-  
-
-  
-  
-Migrating NFS Secondary Storages to Use Object Store
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-updateCloudToUseObjectStore
-Migrate current NFS secondary storages to use object 
store.
-  
-
-  
-
-  
-  
-LDAP Authentication
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-listLdapConfigurations
-Lists all the LDAP configurations.
-  
-  
-addLdapConfiguration
-Add a new LDAP Configuration.
-  
-  
-deleteLdapConfiguration
-Removes an LDAP Configuration.
-  
-  
-listLdapUsers
-Lists all the LDAP users.
-  
-  
-ldapCreateAccount
-Creates an account from an LDAP user.
-  
-  
-importLdapUsers
-Import LDAP users.
-  
-
-  
-
-The following APIs have been deprecated: ldapConfig and ldapRemove 

-  
-  
-Publishing Alerts Using the Web ROOT Admin API
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-generateAlert
-A new API has been added to generate and publish 
alerts for usage services.
-The usage services can be installed on a different host or the 
same host where the
-Management Server is running. This API is available only to 
the Root
-  Admin.
-  
-  
-listAlerts
-To this existing API, a new response parameter has 
been added: name. An
-alert can be searched on the basis of alert 
name.
-  
-
-  
-
-  
-  
-Dynamic Compute Offering
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-DeployVM
-To this existing API, the following request parameter 
has been added:
-details.
-  
-  
-ScaleVM
-To this existing API, the following request parameter 
has been added:
-details.
-  
-  
-ScaleSystemVM
-To this existing API, the following request parameter 
has been added:
-details.
-  
-  
-UpgradeVM
-To this existing API, the following request parameter 
has been added:
-details.
-  
-  
-UpgradeSysytemVM
-To this existing API, the following request parameter 
has been added:
-details.
-  
-
-  
-
-  
-  
-Enhanced Upgrade for Virtual Routers
-
-  
-
-
-
-  
-API
-Description
-  
-
-
-  
-upgradeRouterTemplate
-This is a new API which has been added in this 
release.
-  The following are the request parameters:
-  
-
-  id: Upgrade the specified VR
-
-
-  zone_id : Upgrade the VRs in the specifi

[37/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-vpn-connection-vpc.xml
--
diff --git a/en-US/create-vpn-connection-vpc.xml 
b/en-US/create-vpn-connection-vpc.xml
deleted file mode 100644
index 521b8b8..000
--- a/en-US/create-vpn-connection-vpc.xml
+++ /dev/null
@@ -1,136 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Creating a VPN Connection
-  
-&PRODUCT; supports creating up to 8 VPN connections.
-  
-  
-  
-
-  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 create for the account are listed in the 
page.
-
-
-  Click the Configure button of the VPC to which you want to deploy 
the VMs.
-  The VPC page is displayed where all the tiers you created are 
listed in a
-diagram.
-
-
-  Click the Settings icon.
-  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 Site-to-Site VPN.
-  The Site-to-Site VPN page is displayed.
-
-
-  From the Select View drop-down, ensure that VPN Connection is 
selected.
-
-
-  Click Create VPN Connection.
-   The Create VPN Connection dialog is displayed:
-  
-
-  
-
-
-  createvpnconnection.png: creating a VPN connection to the 
customer
-gateway.
-
-  
-
-
-  Select the desired customer gateway.
-
-
-  Select Passive if you want to establish a connection between two 
VPC virtual
-routers.
-  If you want to establish a connection between two VPC virtual 
routers, select Passive 
-only on one of the VPC virtual routers, which waits for the other VPC 
virtual router to initiate
-the connection. Do not select Passive on the VPC virtual router that 
initiates the
-connection.
-
-
-  Click OK to confirm.
-  Within a few moments, the VPN Connection is displayed.
-  The following information on the VPN connection is 
displayed:
-  
-
-  IP Address
-
-
-  Gateway
-
-
-  State
-
-
-  IPSec Preshared Key
-
-
-  IKE Policy
-
-
-  ESP Policy
-
-  
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/create-vpn-customer-gateway.xml
--
diff --git a/en-US/create-vpn-customer-gateway.xml 
b/en-US/create-vpn-customer-gateway.xml
deleted file mode 100644
index e4df6e2..000
--- a/en-US/create-vpn-customer-gateway.xml
+++ /dev/null
@@ -1,191 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Creating and Updating a VPN Customer Gateway
-  
-A VPN customer gateway can be connected to only one VPN gateway at a 
time.
-  
-  To add a VPN Customer Gateway:
-  
-
-  Log in to the &PRODUCT; UI as an administrator or end user. 
-
-
-  In the left navigation, choose Network.
-
-
-  In the Select view, select VPN Customer Gateway.
-
-
-  Click Add VPN Customer Gateway.
-  
-
-  
-
-
-  addvpncustomergateway.png: adding a customer 
gateway.
-
-  
-  Provide the following information:
-  
-
-  Name: A unique name for the 
VPN customer gateway
-you create.
-
-
-  Gateway: The IP address for 
the remote
-gateway.
-
-
-  CIDR list: The guest CIDR 
list of the remote
-subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure 
that a guest CIDR list
-is not overlapped with the VPCâs CIDR, or another guest CIDR. 
The CIDR must be
-RFC1918-compliant.
-
-
-  IPsec Preshared Key: 
Preshared keying is a method
-where the endpoints of the VPN share a secret key. This key value 
is used to
-authenticate the customer gateway and the VPC VPN gateway to each 
other. 
-  
-The IKE peers (VPN end points) authenticate each other by 
computing and sending a
-

[47/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/Developers_Guide.xml
--
diff --git a/en-US/Developers_Guide.xml b/en-US/Developers_Guide.xml
deleted file mode 100644
index 7106faf..000
--- a/en-US/Developers_Guide.xml
+++ /dev/null
@@ -1,61 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-&PRODUCT; Developer's Guide
-Apache CloudStack
-4.3.0
-
-
-
-
-This guide shows how to develop &PRODUCT;, use the API for 
operation and integration, access the usage data and use &PRODUCT; specific 
tools to ease development, testing and integration.
-
-
-
-
-
-
-
-
-
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-
-http://www.w3.org/2001/XInclude"; 
/>
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/Installation_Guide.ent
--
diff --git a/en-US/Installation_Guide.ent b/en-US/Installation_Guide.ent
deleted file mode 100644
index abb1885..000
--- a/en-US/Installation_Guide.ent
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/Installation_Guide.xml
--
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
deleted file mode 100644
index 8b4c871..000
--- a/en-US/Installation_Guide.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  
-&PRODUCT; Installation Guide
-Apache CloudStack
-4.3.0
-1
-
-
-   Installation Guide for &PRODUCT;. 
-
-
-  
-
-  
-
-  
-
-http://www.w3.org/2001/XInclude"/>
-http://www.w3.org/2001/XInclude"/>
-  
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/LDAPserver-for-user-authentication.xml
--
diff --git a/en-US/LDAPserver-for-user-authentication.xml 
b/en-US/LDAPserver-for-user-authentication.xml
deleted file mode 100644
index 449d500..000
--- a/en-US/LDAPserver-for-user-authentication.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Using an LDAP Server for User Authentication
-  &PRODUCT; supports authentication through a Lightweight Directory 
Access Protocol (LDAP)
-server, such as Microsoft Active Directory or ApacheDS. You can add LDAP 
associations to
-&PRODUCT; so users can log in by using credentials based on your existing 
authentication scheme.
-Additionally, the simplified LDAP authentication mechanism in &PRODUCT; 
4.3 allows you to import
-users directly from the configured LDAP Group. LDAP users are 
authenticated without creating
-individual users in &PRODUCT;.
-  To use LDAP for authentication of &PRODUCT; users, you must do the 
following steps:
-  
-
-  Add a working LDAP server.
-  See .
-
-
-  Configure the LDAP attributes.
-  See .
-
-
-  Import users from the LDAP group.
-  See .
-
-
-  To confirm authentication, log in to &PRODUCT; UI as one of the 
LDAP user you have
-imported.
-
-  
-  http://www.w3.org/2001/XInclude"/>
-  http://www.w3.org/2001/XInclude"/>
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/P

[48/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/qig/en-US/Overview.xml
--
diff --git a/archive/qig/en-US/Overview.xml b/archive/qig/en-US/Overview.xml
deleted file mode 100644
index 31915f5..000
--- a/archive/qig/en-US/Overview.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-  Overview
-
-Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, 
-and by definition they have a plethora of options, which often lead to 
confusion
-for even experienced admins who are newcomers to building cloud platforms. 
-The goal for this runbook is to provide a straightforward set of 
instructions 
-to get you up and running with CloudStack with a minimum amount of 
trouble. 
-
-
-  What exactly are we building?
-  
-  This runbook will focus on building a CloudStack cloud using KVM with 
-  CentOS 6.4 with NFS storage on a flat layer-2 network utilizing 
-  layer-3 network isolation (aka Security Groups), and doing it all
-  on a single piece of hardware.   
-  
-   
-KVM, or Kernel-based Virtual Machine is a virtualization technology
-for the Linux kernel. KVM supports native virtualization atop 
-processors with hardware virtualization extensions. 
-  
-  
-Security Groups act as distributed firewalls that control access
-to a group of virtual machines.
-  
-
-
-  High level overview of the process
-   
-Before we actually get to installing CloudStack, we'll start with 
-installing our base operating system, and then configuring that to act
-as an NFS server for several types of storage. We'll install the 
-management server, download the systemVMs, and finally install the 
agent
-software. Finally we'll spend a good deal of time configuring the 
entire
-cloud in the CloudStack web interface. 
-  
-
-
-  Prerequisites
-
-  To complete this runbook you'll need the following items:
-  
-
-  
-At least one computer which supports hardware virtualization. 
-  
-
-
-  
-The 
-http://mirror.stanford.edu/yum/pub/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-minimal.iso";>
-CentOS 6.4 x86_64 minimal install CD
-
-  
-
-
-  
-  A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP 
should be on this network and 
-  none of the computers running CloudStack will have a dynamic 
address. Again this is done for 
-  the sake of simplicity. 
-  
-
-  
-
-  
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/qig/en-US/Preface.xml
--
diff --git a/archive/qig/en-US/Preface.xml b/archive/qig/en-US/Preface.xml
deleted file mode 100644
index d6ba80e..000
--- a/archive/qig/en-US/Preface.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-Preface
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude";>http://www.w3.org/2001/XInclude";>http://www.w3.org/2001/XInclude"; />
-
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/qig/en-US/Revision_History.xml
--
diff --git a/archive/qig/en-US/Revision_History.xml 
b/archive/qig/en-US/Revision_History.xml
deleted file mode 100644
index 1ff4d77..000
--- a/archive/qig/en-US/Revision_History.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-Revision History
-
-
-
-0-0
-Fri Jun 28 2013
-
-
-Initial creation of book by publican
-
-
-
-
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/qig/en-US/config.xml
--
diff --git a/archive/qig/en-US/config.xml b/archive/qig/en-US/config.xml
deleted file mode 100644
index 7ff7a72..000
--- a/archive/qig/en-US/config.xml
+++ /dev/null
@@ -1,177 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-  Configuration
-  
-As we noted before we will be using security groups to provide isolation
-and by default that implies that we'll be using a f

[30/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/installation-steps-overview.xml
--
diff --git a/en-US/installation-steps-overview.xml 
b/en-US/installation-steps-overview.xml
deleted file mode 100644
index ea00057..000
--- a/en-US/installation-steps-overview.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Overview of Installation Steps
-For anything more than a simple trial installation, you will need 
guidance for a variety of configuration choices. It is strongly recommended 
that you read the following:
-
-Choosing a Deployment Architecture
-Choosing a Hypervisor: Supported 
Features
-Network Setup
-Storage Setup
-Best Practices
-
-
-
-Make sure you have the required hardware ready. See 
-
-
-Install the Management Server (choose single-node or multi-node). 
See 
-
-
-Log in to the UI. See 
-
-
-Add a zone. Includes the first pod, cluster, and host. See 
-
-
-Add more pods (optional). See 
-
-
-Add more clusters (optional). See 
-
-
-Add more hosts (optional). See 
-
-
-Add more primary storage (optional). See 
-
-
-Add more secondary storage (optional). See 
-
-
-Try using the cloud. See 
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/installation.xml
--
diff --git a/en-US/installation.xml b/en-US/installation.xml
deleted file mode 100644
index 5fc550e..000
--- a/en-US/installation.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Installation
-http://www.w3.org/2001/XInclude"/>
-http://www.w3.org/2001/XInclude"/>
-http://www.w3.org/2001/XInclude"/>
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"/>
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/installation_steps_overview.xml
--
diff --git a/en-US/installation_steps_overview.xml 
b/en-US/installation_steps_overview.xml
deleted file mode 100644
index 2632a4d..000
--- a/en-US/installation_steps_overview.xml
+++ /dev/null
@@ -1,84 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-  Overview of Installation Steps
-  For anything more than a simple trial installation, you will need 
-  guidance for a variety of configuration choices. It is strongly 
-  recommended that you read the following:
-  
-Choosing a Deployment Architecture
-Choosing a Hypervisor: Supported Features
-Network Setup
-Storage Setup
-Best Practices
-  
-  
-
-  
-Prepare
-  
-  Make sure you have the required hardware ready
-
-
-  (Optional) Fill out the preparation checklists
-
-
-  Install the &PRODUCT; 
software
-
-
-  Install the Management Server (choose single-node or 
multi-node)
-
-
-  Log in to the UI
-
-
-  Provision your cloud 
infrastructure
-
-
-  Add a zone. Includes the first pod, cluster, and host
-
-
-  Add more pods
-
-
-  Add more clusters
-
-
-  Add more hosts
-
-
-  Add more primary storage
-
-
-  Add more secondary storage
-
-
-  Try using the cloud
-
-
-  Initialization and testing
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/installing-publican.xml
--
diff --git a/en-US/installing-publican.xml b/en-US/installing-publican.xml
deleted file mode 100644
index 9f180aa..000
--- a/en-US/installing-publican.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Installing Publican
-&PRODUCT; documentation is built using publican. This section 
describes how to install publican on your own machine so that you can build the 
documentation guides.
-
-The &PRODUCT; documentation source code is located under 
/docs
-Publican documentation itself is also very http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Users_Guide/chap-Users_Guide-Installing_Publican.html";>useful.
-
-On RHEL and RHEL derivatives, install publican with the following 
command:
-yum install publican publican-doc
-On Ubuntu, install publican with the following command:
-apt-get install publican publican-doc
-For other distribution refer to the publican documentation listed 
above. For latest versions of OSX

[34/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/external-guest-lb-integration.xml
--
diff --git a/en-US/external-guest-lb-integration.xml 
b/en-US/external-guest-lb-integration.xml
deleted file mode 100644
index 5760f95..000
--- a/en-US/external-guest-lb-integration.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  External Guest Load Balancer Integration (Optional)
-  &PRODUCT; can optionally use a Citrix NetScaler or BigIP F5 load 
balancer to provide load
-balancing services to guests. If this is not enabled, &PRODUCT; will use 
the software load
-balancer in the virtual router.
-  To install and enable an external load balancer for &PRODUCT; 
management:
-  
-
-  Set up the appliance according to the vendor's directions.
-
-
-  Connect it to the networks carrying public traffic and management 
traffic (these could
-be the same network).
-
-
-  Record the IP address, username, password, public interface name, 
and private interface
-name. The interface names will be something like "1.1" or "1.2".
-
-
-  Make sure that the VLANs are trunked to the management network 
interface.
-
-
-  After the &PRODUCT; Management Server is installed, log in as 
administrator to the
-&PRODUCT; UI.
-
-
-  In the left navigation bar, click Infrastructure.
-
-
-  In Zones, click View More.
-
-
-  Choose the zone you want to work with.
-
-
-  Click the Network tab.
-
-
-  In the Network Service Providers node of the diagram, click 
Configure. (You might have
-to scroll down to see this.)
-
-
-  Click NetScaler or F5.
-
-
-  Click the Add button (+) and provide the following:
-  For NetScaler:
-  
-
-  IP Address: The IP address of the SRX.
-
-
-  Username/Password: The authentication credentials to access 
the device. &PRODUCT;
-uses these credentials to access the device.
-
-
-  Type: The type of device that is being added. It could be F5 
Big Ip Load Balancer,
-NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison 
of the NetScaler types,
-see the &PRODUCT; Administration Guide.
-
-
-  Public interface: Interface of device that is configured to be 
part of the public
-network.
-
-
-  Private interface: Interface of device that is configured to 
be part of the private
-network.
-
-
-  Number of retries. Number of times to attempt a command on the 
device before
-considering the operation failed. Default is 2.
-
-
-  Capacity: The number of networks the device can handle.
-
-
-  Dedicated: When marked as dedicated, this device will be 
dedicated to a single
-account. When Dedicated is checked, the value in the Capacity 
field has no significance
-implicitly, its value is 1.
-
-  
-
-
-  Click OK.
-
-  
-  The installation and provisioning of the external load balancer is 
finished. You can proceed
-to add VMs and NAT or load balancing rules.
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/extracting-source.xml
--
diff --git a/en-US/extracting-source.xml b/en-US/extracting-source.xml
deleted file mode 100644
index d169040..000
--- a/en-US/extracting-source.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Extracting source
-
-   Extracting the &PRODUCT; release is relatively simple and can be done
-   with a single command as follows: 
-   $ tar -jxvf 
apache-cloudstack-4.1.0.src.tar.bz2
-
-
-   You can now move into the directory:
-   $ cd 
./apache-cloudstack-4.1.0-src
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/feature-overview.xml
--
diff --git a/en-US/feature-overview.xml b/en-US/feature-overview.xml
deleted file mode 100644
index 42a65bb..000
--- a/en-US/feature-overview.xml
+++ /dev/null
@@ -1,81 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-   What Can &PRODUCT; Do?
-   
-   Multiple Hypervisor Support
-   
-   
-&PRODUCT; works with a variety of hypervisors, and a single cloud 
deployment can contain multiple hypervisor implementations. The current release 
of &PRODUCT; supports pre-packaged enterprise solutions like Citrix XenSer

[44/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/added-API-commands.xml
--
diff --git a/en-US/added-API-commands.xml b/en-US/added-API-commands.xml
deleted file mode 100644
index 99635de..000
--- a/en-US/added-API-commands.xml
+++ /dev/null
@@ -1,195 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Added API commands in 3.0
-  
-  Added in 3.0.2
-  
-
-  changeServiceForSystemVm
-  Changes the service offering for a system VM (console proxy or 
secondary storage). The
-system VM must be in a "Stopped" state for this command to take 
effect.
-
-  
-  
-  
-  Added in 3.0.1
-  
-
-  changeServiceForSystemVm
-  Changes the service offering for a system VM (console proxy or 
secondary storage). The
-system VM must be in a "Stopped" state for this command to take 
effect.
-
-  
-  
-  
-  Added in 3.0.0
-  
-
-  
-  
-  
-  
-
-  assignVirtualMachine (Move a user VM to another user 
under same
-  domain.)
-  restoreVirtualMachine (Restore a VM to original 
template or specific
-  snapshot)
-  createLBStickinessPolicy (Creates a Load Balancer 
stickiness policy
-)
-
-
-  deleteLBStickinessPolicy (Deletes a LB stickiness 
policy.)
-  listLBStickinessPolicies (Lists LBStickiness 
policies.)
-  ldapConfig (Configure the LDAP context for this 
site.)
-
-
-  addSwift (Adds Swift.)
-  listSwifts (List Swift.)
-  migrateVolume (Migrate volume)
-
-
-  updateStoragePool (Updates a storage 
pool.)
-  authorizeSecurityGroupEgress (Authorizes a particular 
egress rule for this
-  security group)
-  revokeSecurityGroupEgress (Deletes a particular egress 
rule from this
-  security group)
-
-
-  createNetworkOffering (Creates a network 
offering.)
-  deleteNetworkOffering (Deletes a network 
offering.)
-  createProject (Creates a project)
-
-
-  deleteProject (Deletes a project)
-  updateProject (Updates a project)
-  activateProject (Activates a project)
-
-
-  suspendProject (Suspends a project)
-  listProjects (Lists projects and provides detailed 
information for listed
-  projects)
-  addAccountToProject (Adds account to a 
project)
-
-
-  deleteAccountFromProject (Deletes account from the 
project)
-  listProjectAccounts (Lists project's 
accounts)
-  listProjectInvitations (Lists an account's invitations 
to join
-  projects)
-
-
-  updateProjectInvitation (Accepts or declines project
-invitation)
-  deleteProjectInvitation (Deletes a project 
invitation)
-  updateHypervisorCapabilities (Updates a hypervisor
-capabilities.)
-
-
-  listHypervisorCapabilities (Lists all hypervisor
-capabilities.)
-  createPhysicalNetwork (Creates a physical 
network)
-  deletePhysicalNetwork (Deletes a Physical 
Network.)
-
-
-  listPhysicalNetworks (Lists physical 
networks)
-  updatePhysicalNetwork (Updates a physical 
network)
-  listSupportedNetworkServices (Lists all network 
services provided by
-  &PRODUCT; or for the given Provider.)
-
-
-  addNetworkServiceProvider (Adds a network 
serviceProvider to a physical
-  network)
-  deleteNetworkServiceProvider (Deletes a Network Service
-Provider.)
-  listNetworkServiceProviders (Lists network 
serviceproviders for a given
-  physical network.)
-
-
-  updateNetworkServiceProvider (Updates a network 
serviceProvider of a physical
-  network)
-  addTrafficType (Adds traffic type to a physical 
network)
-  deleteTrafficType (Deletes traffic type of a physical 
network)
-
-
-  listTrafficTypes (Lists traffic types of a given 
physical
-network.)
-  updateTrafficType (Updates traffic type of a physical 
network)
-  listTrafficTypeImplementors (Lists implementors of 
implementor of a network
-  traffic type or implementors of all network traffic 
types)
-
-
-  createStorageNetworkIpRange (Creates a Storage network 
IP
-range.)
-  deleteStorageNetworkIpRange (Deletes a storage network 
IP
-Range.)
-  listStorageNetworkIpRange (List a storage network IP 
range.)
-
-
-  updateStorageNetworkIpRange (Update a Storage network 
IP range, only allowed
-

[49/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/midonet/en-US/plugin-midonet-usage.xml
--
diff --git a/archive/midonet/en-US/plugin-midonet-usage.xml 
b/archive/midonet/en-US/plugin-midonet-usage.xml
deleted file mode 100644
index a314581..000
--- a/archive/midonet/en-US/plugin-midonet-usage.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-http://www.docbook.org/xml/4.4/xinclude.mod";>
-%xinclude;
-]>
-
-
-Using the MidoNet Plugin
-
-http://www.w3.org/2001/XInclude";>
-http://www.w3.org/2001/XInclude";>
-http://www.w3.org/2001/XInclude";>
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/midonet/publican.cfg
--
diff --git a/archive/midonet/publican.cfg b/archive/midonet/publican.cfg
deleted file mode 100644
index 6558d99..000
--- a/archive/midonet/publican.cfg
+++ /dev/null
@@ -1,28 +0,0 @@
-# Publican configuration file for CloudStack Complete Documentation Set
-# Contains all technical docs except release notes
-# Config::Simple 4.58
-# Tue May 29 00:57:27 2012
-#
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information#
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-
-xml_lang: en-US
-type: Book
-docname: MidoNet_Plugin_Guide
-brand: cloudstack
-chunk_first: 1
-chunk_section_depth: 1
-condition: install

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/nicira/en-US/Author_Group.xml
--
diff --git a/archive/nicira/en-US/Author_Group.xml 
b/archive/nicira/en-US/Author_Group.xml
deleted file mode 100644
index ba9e651..000
--- a/archive/nicira/en-US/Author_Group.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-
-Apache
-CloudStack
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/nicira/en-US/Book_Info.xml
--
diff --git a/archive/nicira/en-US/Book_Info.xml 
b/archive/nicira/en-US/Book_Info.xml
deleted file mode 100644
index 327668d..000
--- a/archive/nicira/en-US/Book_Info.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-
-&PRODUCT; Guide
-Revised August 9, 2012 10:48 pm Pacific
-Apache CloudStack
-4.2.0
-1
-
-
-
-Complete technical documentation of &PRODUCT;.
-
-
-
-
-
-
-
-
-
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.org/2001/XInclude"; />
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.ent
--
diff --git a/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.ent 
b/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.ent
deleted file mode 100644
index abb1885..000
--- a/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.ent
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
-
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.xml
--
diff --git a/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.xml 
b/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.xml
deleted file mode 100644
index 5431fc1..000
--- a/archive/nicira/en-US/CloudStack_Nicira_NVP_Guide.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-http://www.docbook.org/xml/4.4/xinclude.mod";>
-%xinclude;
-]>
-
-
-
-
-
-&PRODUCT; Plugin Guide for the Nicira NVP Plugin
-Apache CloudStack
-4.2.0
-1
-
-
-
-Plugin Guide for the Nicira NVP Plugin.
-
-
-
-
-
-
-
-
-
-http://www.w3.org/2001/XInclude"; />
-http://www.w3.or

[28/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-overview.xml
--
diff --git a/en-US/management-server-install-overview.xml 
b/en-US/management-server-install-overview.xml
deleted file mode 100644
index 5f46b00..000
--- a/en-US/management-server-install-overview.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Management Server Installation Overview
-This section describes installing the Management Server. There are 
two slightly different installation flows, depending on how many Management 
Server nodes will be in your cloud:
-
-A single Management Server node, with MySQL on the 
same node.
-Multiple Management Server nodes, with MySQL on a node 
separate from the Management Servers.
-
-In either case, each machine must meet the system requirements 
described in System Requirements. 
-For the sake of security, be sure the public Internet can 
not access port 8096 or port 8250 on the Management Server.
-The procedure for installing the Management Server is:
-
-
-  Prepare the Operating System
-
-
-  (XenServer only) Download and install vhd-util.
-
-Install the First Management 
Server
-Install and Configure the MySQL 
database
-Prepare NFS Shares
-Prepare and Start Additional Management 
Servers (optional)
-Prepare the System VM 
Template
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-prepare-os.xml
--
diff --git a/en-US/management-server-install-prepare-os.xml 
b/en-US/management-server-install-prepare-os.xml
deleted file mode 100644
index 02453a0..000
--- a/en-US/management-server-install-prepare-os.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Prepare the Operating System
-The OS must be prepared to host the Management Server using the 
following steps. These steps must be performed on each Management Server 
node.
-
-Log in to your OS as root.
-
-Check for a fully qualified hostname.
-hostname --fqdn
-This should return a fully qualified hostname such as 
"management1.lab.example.org".  If it does not, edit /etc/hosts so that it 
does.
-
-
-Make sure that the machine can reach the Internet.
-ping 
www.cloudstack.org
-
-
-Turn on NTP for time synchronization.
-NTP is required to synchronize the clocks of the 
servers in your cloud.
-
-
-Install NTP.
-On RHEL or CentOS:
-yum install 
ntp
-On Ubuntu:
-apt-get install 
openntpd
-
-
-
-Repeat all of these steps on every host where the 
Management Server will be installed.
-
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/management-server-install-systemvm.xml
--
diff --git a/en-US/management-server-install-systemvm.xml 
b/en-US/management-server-install-systemvm.xml
deleted file mode 100644
index 32098b8..000
--- a/en-US/management-server-install-systemvm.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-  Prepare the System VM Template
-  Secondary storage must be seeded with a template that is used for 
&PRODUCT; system
-VMs.
-  
-When copying and pasting a command, be sure the command has pasted 
as a single line before
-  executing. Some document viewers may introduce unwanted line breaks in 
copied text.
-  
-  
-
-  On the Management Server, run one or more of the following 
cloud-install-sys-tmplt
-commands to retrieve and decompress the system VM template. Run the 
command for each
-hypervisor type that you expect end users to run in this Zone.
-  If your secondary storage mount point is not named /mnt/secondary, 
substitute your own
-mount point name.
-  If you set the &PRODUCT; database encryption type to "web" when 
you set up the database,
-  you must now add the parameter -s 
. See .
-  This process will require approximately 5 GB of free space on the 
local file system and
-up to 30 minutes each time it runs.
-  
-
-  For Hyper-V
-  # 
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt 
-m /mnt/secondary -u 
htt

[41/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/castor-with-cs.xml
--
diff --git a/en-US/castor-with-cs.xml b/en-US/castor-with-cs.xml
deleted file mode 100644
index 7bf676b..000
--- a/en-US/castor-with-cs.xml
+++ /dev/null
@@ -1,86 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-  Using the CAStor Back-end Storage with &PRODUCT;
-  This section describes how to use a CAStor cluster as the back-end 
storage system for a
-&PRODUCT; S3 front-end. The CAStor back-end storage for &PRODUCT; extends 
the existing storage
-classes and allows the storage configuration attribute to point to a 
CAStor cluster.
-  This feature makes use of the &PRODUCT; server's local disk to spool 
files before writing
-them to CAStor when handling the PUT operations. However, a file must be 
successfully written
-into the CAStor cluster prior to the return of a success code to the S3 
client to ensure that
-the transaction outcome is correctly reported.
-  
-The S3 multipart file upload is not supported in this release. You 
are prompted with
-  proper error message if a multipart upload is attempted.
-  
-  To configure CAStor:
-  
-
-  Install &PRODUCT; by following the instructions given in the 
INSTALL.txt file.
-  
-You can use the S3 storage system in &PRODUCT; without setting 
up and installing the
-  compute components.
-  
-
-
-  Enable the S3 API by setting "enable.s3.api = true" in the Global 
parameter section in
-the UI and register a user.
-  For more information, see https://cwiki.apache.org/CLOUDSTACK/s3-api-in-cloudstack.html";>S3 API in
-  &PRODUCT;.
-
-
-  Edit the cloud-bridge.properties file and modify the 
"storage.root" parameter.
-  
-
-  Set "storage.root" to the key word "castor".
-
-
-  Specify a CAStor tenant domain to which content is written. If 
the domain is not
-specified, the CAStor default domain, specified by the "cluster" 
parameter in CAStor's
-node.cfg file, will be used.
-
-
-  Specify a list of node IP addresses, or set 
"zeroconf" and the cluster
-name. When using a static IP list with a large cluster, it is not 
necessary to include
-every node, only a few is required to initialize the client 
software.
-  For example:
-  storage.root=castor domain=cloudstack 10.1.1.51 
10.1.1.52 10.1.1.53
-  In this example, the configuration file directs &PRODUCT; to 
write the S3 files to
-CAStor instead of to a file system, where the CAStor domain name 
is cloudstack, and the
-CAStor node IP addresses are those listed.
-
-
-  (Optional) The last value is a port number on which to 
communicate with the CAStor
-cluster. If not specified, the default is 80.
-  #Static IP list with optional port
-storage.root=castor domain=cloudstack 10.1.1.51 10.1.1.52 10.1.1.53 80
-#Zeroconf locator for cluster named "castor.example.com"
-storage.root=castor domain=cloudstack 
zeroconf=castor.example.com
-
-  
-
-
-  Create the tenant domain within the CAStor storage cluster. If you 
omit this step before
-attempting to store content, you will get HTTP 412 errors in the 
awsapi.log.
-
-  
-

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/en-US/change-console-proxy-ssl-certificate-domain.xml
--
diff --git a/en-US/change-console-proxy-ssl-certificate-domain.xml 
b/en-US/change-console-proxy-ssl-certificate-domain.xml
deleted file mode 100644
index 3fd0501..000
--- a/en-US/change-console-proxy-ssl-certificate-domain.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-
-http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
-
-%BOOK_ENTITIES;
-]>
-
-
-
-
-Changing the Console Proxy SSL Certificate and Domain
-If the administrator prefers, it is possible for the URL of the 
customer's console session to show a domain other than realhostip.com. The 
administrator can customize the displayed domain by selecting a different 
domain and uploading a new SSL certificate and private key. The domain must run 
a DNS service that is capable of resolving queries for addresses of the form 
aaa-bbb-ccc-ddd.your.domain to an IPv4 IP address in the form aaa.bbb.ccc.ddd, 
for example, 202.8.44.1. To change the console proxy domain, SSL certificate, 
and private key:
-
-Set up dynamic name resolution or populate all 
possible DNS names in your public IP range into your existing DNS server with 
the format aaa-bbb-ccc-ddd.company.com -> aaa.bbb.ccc.ddd.
-Generate the private key and certificate signing 
request (CSR). When you are using openssl to

[51/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

Remove all old docbook files


Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/f42520a5
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/f42520a5
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/f42520a5

Branch: refs/heads/master
Commit: f42520a53f2b68ca6568885da2d0f1c098dd2ad2
Parents: 24fae45
Author: Sebastien Goasguen 
Authored: Thu Oct 1 16:02:13 2015 +0200
Committer: Sebastien Goasguen 
Committed: Thu Oct 1 16:02:13 2015 +0200

--
 Common_Content/cloudstack/defaults.cfg  |   21 -
 Common_Content/cloudstack/en-US/Feedback.xml|   50 -
 .../cloudstack/en-US/Legal_Notice.xml   |   43 -
 .../cloudstack/en-US/css/overrides.css  |   74 -
 Common_Content/cloudstack/en-US/images/1.png|  Bin 1365 -> 0 bytes
 Common_Content/cloudstack/en-US/images/10.png   |  Bin 1705 -> 0 bytes
 Common_Content/cloudstack/en-US/images/11.png   |  Bin 1379 -> 0 bytes
 Common_Content/cloudstack/en-US/images/12.png   |  Bin 1721 -> 0 bytes
 Common_Content/cloudstack/en-US/images/13.png   |  Bin 1810 -> 0 bytes
 Common_Content/cloudstack/en-US/images/14.png   |  Bin 1597 -> 0 bytes
 Common_Content/cloudstack/en-US/images/15.png   |  Bin 1689 -> 0 bytes
 Common_Content/cloudstack/en-US/images/16.png   |  Bin 1817 -> 0 bytes
 Common_Content/cloudstack/en-US/images/17.png   |  Bin 1688 -> 0 bytes
 Common_Content/cloudstack/en-US/images/18.png   |  Bin 1832 -> 0 bytes
 Common_Content/cloudstack/en-US/images/19.png   |  Bin 1823 -> 0 bytes
 Common_Content/cloudstack/en-US/images/2.png|  Bin 1608 -> 0 bytes
 Common_Content/cloudstack/en-US/images/20.png   |  Bin 1937 -> 0 bytes
 Common_Content/cloudstack/en-US/images/21.png   |  Bin 1723 -> 0 bytes
 Common_Content/cloudstack/en-US/images/22.png   |  Bin 1620 -> 0 bytes
 Common_Content/cloudstack/en-US/images/23.png   |  Bin 2007 -> 0 bytes
 Common_Content/cloudstack/en-US/images/24.png   |  Bin 1774 -> 0 bytes
 Common_Content/cloudstack/en-US/images/25.png   |  Bin 1937 -> 0 bytes
 Common_Content/cloudstack/en-US/images/26.png   |  Bin 1975 -> 0 bytes
 Common_Content/cloudstack/en-US/images/27.png   |  Bin 1873 -> 0 bytes
 Common_Content/cloudstack/en-US/images/28.png   |  Bin 2055 -> 0 bytes
 Common_Content/cloudstack/en-US/images/29.png   |  Bin 2033 -> 0 bytes
 Common_Content/cloudstack/en-US/images/3.png|  Bin 1677 -> 0 bytes
 Common_Content/cloudstack/en-US/images/4.png|  Bin 1457 -> 0 bytes
 Common_Content/cloudstack/en-US/images/5.png|  Bin 1597 -> 0 bytes
 Common_Content/cloudstack/en-US/images/6.png|  Bin 1691 -> 0 bytes
 Common_Content/cloudstack/en-US/images/7.png|  Bin 1567 -> 0 bytes
 Common_Content/cloudstack/en-US/images/8.png|  Bin 1711 -> 0 bytes
 Common_Content/cloudstack/en-US/images/9.png|  Bin 1696 -> 0 bytes
 Common_Content/cloudstack/en-US/images/dot.png  |  Bin 173 -> 0 bytes
 Common_Content/cloudstack/en-US/images/dot2.png |  Bin 342 -> 0 bytes
 .../cloudstack/en-US/images/h1-bg.png   |  Bin 565 -> 0 bytes
 .../cloudstack/en-US/images/image_left.png  |  Bin 4044 -> 0 bytes
 .../cloudstack/en-US/images/image_right.png |  Bin 2260 -> 0 bytes
 .../cloudstack/en-US/images/important.png   |  Bin 2318 -> 0 bytes
 Common_Content/cloudstack/en-US/images/note.png |  Bin 2086 -> 0 bytes
 .../cloudstack/en-US/images/stock-go-back.png   |  Bin 790 -> 0 bytes
 .../en-US/images/stock-go-forward.png   |  Bin 860 -> 0 bytes
 .../cloudstack/en-US/images/stock-go-up.png |  Bin 753 -> 0 bytes
 .../cloudstack/en-US/images/stock-home.png  |  Bin 819 -> 0 bytes
 .../cloudstack/en-US/images/title_logo.png  |  Bin 585 -> 0 bytes
 .../cloudstack/en-US/images/title_logo.svg  |  370 --
 .../cloudstack/en-US/images/warning.png |  Bin 1941 -> 0 bytes
 .../cloudstack/en-US/images/watermark-draft.png |  Bin 25365 -> 0 bytes
 Common_Content/cloudstack/overrides.cfg |   20 -
 Common_Content/cloudstack/publican.cfg  |   24 -
 .../en-US/Allocator_Implementation_Guide.ent|   22 -
 .../en-US/Allocator_Implementation_Guide.xml|   51 -
 archive/allocator/en-US/Author_Group.xml|   32 -
 archive/allocator/en-US/Book_Info.xml   |   47 -
 archive/allocator/en-US/allocators.xml  |   38 -
 .../allocator/en-US/custom-hostallocator.xml|  151 -
 .../en-US/custom-storagepoolallocator.xml   |  132 -
 .../en-US/extras/custom-hostallocator.java  |   21 -
 .../en-US/extras/custom-hostallocator2.java |3 -
 .../en-US/extras/custom-storageallocator.java   |   11 -
 .../en-US/extras/custom-storageallocator2.java  |3 -
 archive/allocator/publican.cfg  |   30 -
 archive/midonet/en-US/Author_Group.xml  |   32 -
 archive/midonet/en-US/Book_Info.xml |   47 -
 archive/midonet/en-US/MidoNet_Plugin_Guide.ent  |   22 -

cloudstack-docs git commit: Remove one last old reference to docbook

2015-10-01 Thread sebgoa

Repository: cloudstack-docs
Updated Branches:
  refs/heads/master f42520a53 -> 82119f92f


Remove one last old reference to docbook


Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/82119f92
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/82119f92
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/82119f92

Branch: refs/heads/master
Commit: 82119f92fa355f10c1d017335ce53f1b6d2b4baa
Parents: f42520a
Author: Sebastien Goasguen 
Authored: Thu Oct 1 16:06:59 2015 +0200
Committer: Sebastien Goasguen 
Committed: Thu Oct 1 16:06:59 2015 +0200

--
 publican-cloudstack/LICENSE | 202 --
 publican-cloudstack/NOTICE  |   5 -
 publican-cloudstack/defaults.cfg|  21 --
 publican-cloudstack/en-US/Feedback.xml  |  44 ---
 publican-cloudstack/en-US/Legal_Notice.xml  |  67 
 publican-cloudstack/en-US/css/overrides.css |  74 
 publican-cloudstack/en-US/images/1.png  | Bin 1365 -> 0 bytes
 publican-cloudstack/en-US/images/10.png | Bin 1705 -> 0 bytes
 publican-cloudstack/en-US/images/11.png | Bin 1379 -> 0 bytes
 publican-cloudstack/en-US/images/12.png | Bin 1721 -> 0 bytes
 publican-cloudstack/en-US/images/13.png | Bin 1810 -> 0 bytes
 publican-cloudstack/en-US/images/14.png | Bin 1597 -> 0 bytes
 publican-cloudstack/en-US/images/15.png | Bin 1689 -> 0 bytes
 publican-cloudstack/en-US/images/16.png | Bin 1817 -> 0 bytes
 publican-cloudstack/en-US/images/17.png | Bin 1688 -> 0 bytes
 publican-cloudstack/en-US/images/18.png | Bin 1832 -> 0 bytes
 publican-cloudstack/en-US/images/19.png | Bin 1823 -> 0 bytes
 publican-cloudstack/en-US/images/2.png  | Bin 1608 -> 0 bytes
 publican-cloudstack/en-US/images/20.png | Bin 1937 -> 0 bytes
 publican-cloudstack/en-US/images/21.png | Bin 1723 -> 0 bytes
 publican-cloudstack/en-US/images/22.png | Bin 1620 -> 0 bytes
 publican-cloudstack/en-US/images/23.png | Bin 2007 -> 0 bytes
 publican-cloudstack/en-US/images/24.png | Bin 1774 -> 0 bytes
 publican-cloudstack/en-US/images/25.png | Bin 1937 -> 0 bytes
 publican-cloudstack/en-US/images/26.png | Bin 1975 -> 0 bytes
 publican-cloudstack/en-US/images/27.png | Bin 1873 -> 0 bytes
 publican-cloudstack/en-US/images/28.png | Bin 2055 -> 0 bytes
 publican-cloudstack/en-US/images/29.png | Bin 2033 -> 0 bytes
 publican-cloudstack/en-US/images/3.png  | Bin 1677 -> 0 bytes
 publican-cloudstack/en-US/images/4.png  | Bin 1457 -> 0 bytes
 publican-cloudstack/en-US/images/5.png  | Bin 1597 -> 0 bytes
 publican-cloudstack/en-US/images/6.png  | Bin 1691 -> 0 bytes
 publican-cloudstack/en-US/images/7.png  | Bin 1567 -> 0 bytes
 publican-cloudstack/en-US/images/8.png  | Bin 1711 -> 0 bytes
 publican-cloudstack/en-US/images/9.png  | Bin 1696 -> 0 bytes
 publican-cloudstack/en-US/images/dot.png| Bin 173 -> 0 bytes
 publican-cloudstack/en-US/images/dot2.png   | Bin 342 -> 0 bytes
 publican-cloudstack/en-US/images/h1-bg.png  | Bin 565 -> 0 bytes
 publican-cloudstack/en-US/images/image_left.png | Bin 4044 -> 0 bytes
 .../en-US/images/image_right.png| Bin 2260 -> 0 bytes
 publican-cloudstack/en-US/images/important.png  | Bin 2318 -> 0 bytes
 publican-cloudstack/en-US/images/note.png   | Bin 2086 -> 0 bytes
 .../en-US/images/stock-go-back.png  | Bin 790 -> 0 bytes
 .../en-US/images/stock-go-forward.png   | Bin 860 -> 0 bytes
 .../en-US/images/stock-go-up.png| Bin 753 -> 0 bytes
 publican-cloudstack/en-US/images/stock-home.png | Bin 819 -> 0 bytes
 publican-cloudstack/en-US/images/title_logo.png | Bin 585 -> 0 bytes
 publican-cloudstack/en-US/images/title_logo.svg | 370 ---
 publican-cloudstack/en-US/images/warning.png| Bin 1941 -> 0 bytes
 .../en-US/images/watermark-draft.png| Bin 25365 -> 0 bytes
 publican-cloudstack/gen_rpm.sh  |  22 --
 publican-cloudstack/overrides.cfg   |  20 -
 publican-cloudstack/publican-cloudstack.spec|  69 
 publican-cloudstack/publican.cfg|  24 --
 54 files changed, 918 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/82119f92/publican-cloudstack/LICENSE
--
diff --git a/publican-cloudstack/LICENSE b/publican-cloudstack/LICENSE
deleted file mode 100644
index d645695..000
--- a/publican-cloudstack/LICENSE
+++ /dev/null
@@ -1,202 +0,0 @@
-
- Apache License
-   Version

[50/51] [partial] cloudstack-docs git commit: Remove all old docbook files

2015-10-01 Thread sebgoa

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/17.png
--
diff --git a/Common_Content/cloudstack/en-US/images/17.png 
b/Common_Content/cloudstack/en-US/images/17.png
deleted file mode 100644
index 5949645..000
Binary files a/Common_Content/cloudstack/en-US/images/17.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/18.png
--
diff --git a/Common_Content/cloudstack/en-US/images/18.png 
b/Common_Content/cloudstack/en-US/images/18.png
deleted file mode 100644
index 7e8dbb4..000
Binary files a/Common_Content/cloudstack/en-US/images/18.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/19.png
--
diff --git a/Common_Content/cloudstack/en-US/images/19.png 
b/Common_Content/cloudstack/en-US/images/19.png
deleted file mode 100644
index eb43c6f..000
Binary files a/Common_Content/cloudstack/en-US/images/19.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/2.png
--
diff --git a/Common_Content/cloudstack/en-US/images/2.png 
b/Common_Content/cloudstack/en-US/images/2.png
deleted file mode 100644
index e550c21..000
Binary files a/Common_Content/cloudstack/en-US/images/2.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/20.png
--
diff --git a/Common_Content/cloudstack/en-US/images/20.png 
b/Common_Content/cloudstack/en-US/images/20.png
deleted file mode 100644
index 692badc..000
Binary files a/Common_Content/cloudstack/en-US/images/20.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/21.png
--
diff --git a/Common_Content/cloudstack/en-US/images/21.png 
b/Common_Content/cloudstack/en-US/images/21.png
deleted file mode 100644
index 231735e..000
Binary files a/Common_Content/cloudstack/en-US/images/21.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/22.png
--
diff --git a/Common_Content/cloudstack/en-US/images/22.png 
b/Common_Content/cloudstack/en-US/images/22.png
deleted file mode 100644
index a77ea0f..000
Binary files a/Common_Content/cloudstack/en-US/images/22.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/23.png
--
diff --git a/Common_Content/cloudstack/en-US/images/23.png 
b/Common_Content/cloudstack/en-US/images/23.png
deleted file mode 100644
index 1802579..000
Binary files a/Common_Content/cloudstack/en-US/images/23.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/24.png
--
diff --git a/Common_Content/cloudstack/en-US/images/24.png 
b/Common_Content/cloudstack/en-US/images/24.png
deleted file mode 100644
index 16e96e7..000
Binary files a/Common_Content/cloudstack/en-US/images/24.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/25.png
--
diff --git a/Common_Content/cloudstack/en-US/images/25.png 
b/Common_Content/cloudstack/en-US/images/25.png
deleted file mode 100644
index 7bfac57..000
Binary files a/Common_Content/cloudstack/en-US/images/25.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/26.png
--
diff --git a/Common_Content/cloudstack/en-US/images/26.png 
b/Common_Content/cloudstack/en-US/images/26.png
deleted file mode 100644
index 08de065..000
Binary files a/Common_Content/cloudstack/en-US/images/26.png and /dev/null 
differ

http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/f42520a5/Common_Content/cloudstack/en-US/images/27.png
--
diff --git a/Common_Content/cloudstack/en-US/images/27.png 
b/Common_Content/cloudstack/en-US/images/27.png
deleted file mode 100644

Git Push Summary

2015-10-01 Thread dahn

Repository: cloudstack
Updated Branches:
  refs/heads/hotfix/4.4-6460 [deleted] 536ec0578

Git Push Summary

2015-10-01 Thread dahn

Repository: cloudstack
Updated Branches:
  refs/heads/hotfix/4.4-6905 [deleted] 9800b9f07

58 matches

Mail list logo