Add slicing tool to the master branch

This patch added tools used for slicing and merging in translation process.
The patch also includes the POT files for each documents.
The PO files are not included, which can be downloaded from Transifex.

Fixes: bug #1153415
Change-Id: Ia455134c99acb1129e8f10deda0d85867b1ef9a3

Author: daisy-ycguo

doc/src/docbkx/openstack-ops/locale/openstack-ops.pot

@@ -0,0 +1,280 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: PACKAGE VERSION\n"
+"POT-Creation-Date: 2013-03-12 14:42+0800\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <[email protected]>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-manual-how-to-use.xml:5(title)
+msgid "How to use this manual"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-manual-how-to-use.xml:6(para)
+msgid "Intended Audience Conventions"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:5(title)
+msgid "Diagnostics and Troubleshooting"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:6(para)
+msgid "If this happens, then do this"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:10(title)
+msgid "Tips, Tricks, and Traps"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:11(para)
+msgid "Configuration settings that should not remain defaults Making sensible scheduler choices Figuring out how to find out what flags do"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:19(title)
+msgid "Monitoring"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-diagnostic-troubleshooting.xml:20(para)
+msgid "Sources of information and alerts Monitoring Hardware Monitoring the Network Monitoring the Cloud"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:5(title)
+msgid "Day to Day Operations"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:6(para)
+msgid "This chapter aims to describe \"A day in the life of an operator, by detailing the common tasks that every OpeStack administrator could expect to perform."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:11(title)
+msgid "Watch the Queues"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:15(para)
+msgid "Something!"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:12(para)
+msgid "A core part of OpenStack Compute is the message queue, provided by RabbitMQ, or QPID. The queue is responsible for: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:18(para)
+msgid "In general, if the queue has no messages this means that they are reaching their destination. One of the common signs of trouble in Compute is if there are pileups of messages for certain destinations. In cases like this, unless you are actively checking the queues, tasks can sit silently without being processed."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:26(para)
+msgid "You can check the state of the queues with: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:33(title)
+msgid "Network issues"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:34(para)
+msgid "Openstack provides and relies on broad access to the network, so when trouble occurs here the issues can be wide reaching. Thankfully there are some common tools you can use to determine the location of problems."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:38(para)
+msgid "Pings, traceroutes, nslookups for networking issues TCP dumps Look for pings with high latency"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:46(title)
+msgid "Resource Utilisation"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:47(para)
+msgid "Disk I/O - look for 100% utilization spots CPU Straces"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:55(title)
+msgid "Working with Instances"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:60(para)
+msgid "Instances stuck in \"build\" state"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:61(para)
+msgid "Instances can't be \"ping\"ed"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:62(para)
+msgid "Instances can't be accessed through a VNC console"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:56(para)
+msgid "Running virtual machines is a complex business, and many different points of failure can be realised. It is worth paying attention to these common cases: <placeholder-1/>"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:68(title)
+msgid "Working with Users"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:69(para)
+msgid "Direct users of OpenStack's Infrastructure-as-a-Service and Object Storage capabilities are likely to be technically competent developers. You may find your Tier 1 support (if any!) relies on you more to provide user support for these cases."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:73(para)
+msgid "Here are some example types of \"tickets\" generated by OpenStack users, and some tips for working the service into your support workflow"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:79(title)
+msgid "Daily monitoring practices"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:80(para)
+msgid "No one likes a spammy nagios, or having tail -f of a log file scroll past like the matrix. Metrics to follow with alarm settting Syslog trolling"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:87(title)
+msgid "Summary of Operational Tools"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-day-to-day.xml:88(para)
+msgid "Available tools modified or used in Openstack Euca Nova.conf Curl etc. Nagios"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-quick-start.xml:5(title)
+msgid "Operations Quick Start"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-quick-start.xml:6(para)
+msgid "Administrative starting tasks - first time operator on an OpenStack cloud, what do they need to know? New Hire Operator who needs to get up to speed quickly."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-periodic.xml:5(title)
+msgid "Periodic Operations"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-periodic.xml:6(para)
+msgid "Things that need to be done sometimes Cleanup of databases Rebuilding/Balancing the ring Log file rotation checks Capacity planning"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:10(title)
+msgid "OpenStack Operations Manual - <phrase os=\"rhel;centos;fedora\">Red Hat</phrase><phrase os=\"ubuntu\">Ubuntu</phrase>"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:20(orgname) ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:29(productname)
+msgid "OpenStack"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:24(year)
+msgid "2012"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:25(year)
+msgid "2013"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:26(holder)
+msgid "OpenStack Foundation"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:28(releaseinfo)
+msgid "trunk"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:30(pubdate)
+msgid "2012-09-10"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:33(remark)
+msgid "Copyright details are filled in by the template."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:37(para)
+msgid "The OpenStack™ system has several key projects that are separate installations but can work together depending on your cloud needs: OpenStack Compute, OpenStack Object Storage, OpenStack Identity Service, and OpenStack Image Service. <phrase os=\"ubuntu\">This manual provides operational pointers using packages available through Ubuntu 12.04.</phrase><phrase os=\"rhel;centos;fedora\">This manual provides operational pointers using packages available through Fedora 17 as well as on RHEL and derivatives through the EPEL repository.</phrase> It offers suggestions for common operational practices and aims to get new operators quickly up to speed."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:58(date)
+msgid "2012-07-29"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/bk_openstackopsmanual.xml:62(para)
+msgid "Initial structure."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:5(title)
+msgid "Operations Management Practices"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:6(para)
+msgid "This chapter discusses best practices for operations management."
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:11(title)
+msgid "Starting Up"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:12(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:17(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:29(para) ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:50(para)
+msgid "Text"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:16(title)
+msgid "Database Management"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:21(title)
+msgid "Storage Management"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:22(para)
+msgid "- volumes attached to compute instances Backups for volumes"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:28(title)
+msgid "User Management"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:33(title)
+msgid "Security Management"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:34(para)
+msgid "Security is important!"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:38(title)
+msgid "DevOps principles"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:39(para)
+msgid "Dev/Ops principals and how they work in the Ops environment"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:44(title)
+msgid "Migration and Upgrades"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:45(para)
+msgid "Migrations are hard!"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:49(title)
+msgid "Failover Planning"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:54(title)
+msgid "Disaster Recovery, Business Continuity Planning"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:55(para)
+msgid "DCs in flames"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:59(title)
+msgid "Automation"
+msgstr ""
+
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:60(para)
+msgid "Automation - What to automate and how to do it"
+msgstr ""
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
+#: ./doc/src/docbkx/openstack-ops/ch_ops-mgmt-practices.xml:0(None)
+msgid "translator-credits"
+msgstr ""
+