diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po b/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po new file mode 100644 index 0000000000..77c27d4517 --- /dev/null +++ b/doc/source/locale/en_GB/LC_MESSAGES/doc-troubleshooting.po @@ -0,0 +1,210 @@ +# Andi Chandler , 2018. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-12-11 21:29+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2018-12-04 05:10+0000\n" +"Last-Translator: Andi Chandler \n" +"Language-Team: English (United Kingdom)\n" +"Language: en_GB\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" + +msgid "Backing up a PVC" +msgstr "Backing up a PVC" + +msgid "" +"Backing up a PVC stored in Ceph, is fairly straigthforward, in this example " +"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will " +"also apply to any other services using PVCs eg. RabbitMQ, Postgres." +msgstr "" +"Backing up a PVC stored in Ceph, is fairly straightforward, in this example " +"we use the PVC ``mysql-data-mariadb-server-0`` as an example, but this will " +"also apply to any other services using PVCs e.g. RabbitMQ, Postgres." + +msgid "" +"Before proceeding, it is important to ensure that you have deployed a client " +"key in the namespace you wish to fulfill ``PersistentVolumeClaims``. To " +"verify that your deployment namespace has a client key:" +msgstr "" +"Before proceeding, it is important to ensure that you have deployed a client " +"key in the namespace you wish to fulfil ``PersistentVolumeClaims``. To " +"verify that your deployment namespace has a client key:" + +msgid "Bugs and Feature requests" +msgstr "Bugs and Feature requests" + +msgid "Ceph" +msgstr "Ceph" + +msgid "Ceph Deployment Status" +msgstr "Ceph Deployment Status" + +msgid "Ceph Validating PVC Operation" +msgstr "Ceph Validating PVC Operation" + +msgid "Ceph Validating StorageClass" +msgstr "Ceph Validating StorageClass" + +msgid "Channels" +msgstr "Channels" + +msgid "Database Deployments" +msgstr "Database Deployments" + +msgid "" +"First, we want to validate that Ceph is working correctly. This can be done " +"with the following Ceph command:" +msgstr "" +"First, we want to validate that Ceph is working correctly. This can be done " +"with the following Ceph command:" + +msgid "Galera Cluster" +msgstr "Galera Cluster" + +msgid "Getting help" +msgstr "Getting help" + +msgid "Installation" +msgstr "Installation" + +msgid "" +"Join us on `IRC `_: #openstack-" +"helm on freenode" +msgstr "" +"Join us on `IRC `_: #openstack-" +"helm on freenode" + +msgid "Join us on `Slack `_ - #openstack-helm" +msgstr "Join us on `Slack `_ - #openstack-helm" + +msgid "" +"Next we can look at the storage class, to make sure that it was created " +"correctly:" +msgstr "" +"Next we can look at the storage class, to make sure that it was created " +"correctly:" + +msgid "" +"Note: This step is not relevant for PVCs within the same namespace Ceph was " +"deployed." +msgstr "" +"Note: This step is not relevant for PVCs within the same namespace Ceph was " +"deployed." + +msgid "Once this has been done the workload can be restarted." +msgstr "Once this has been done the workload can be restarted." + +msgid "PVC Preliminary Validation" +msgstr "PVC Preliminary Validation" + +msgid "Persistent Storage" +msgstr "Persistent Storage" + +msgid "" +"Restoring is just as straightforward. Once the workload consuming the device " +"has been stopped, and the raw RBD device removed the following will import " +"the back up and create a device:" +msgstr "" +"Restoring is just as straightforward. Once the workload consuming the device " +"has been stopped, and the raw RBD device removed the following will import " +"the back up and create a device:" + +msgid "" +"Sometimes things go wrong. These guides will help you solve many common " +"issues with the following:" +msgstr "" +"Sometimes things go wrong. These guides will help you solve many common " +"issues with the following:" + +msgid "" +"The parameters are what we're looking for here. If we see parameters passed " +"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster." +"local:6789`` hostname/port, things like ``userid``, and appropriate secrets " +"used for volume claims." +msgstr "" +"The parameters are what we're looking for here. If we see parameters passed " +"to the StorageClass correctly, we will see the ``ceph-mon.ceph.svc.cluster." +"local:6789`` hostname/port, things like ``userid``, and appropriate secrets " +"used for volume claims." + +msgid "" +"This guide is to help users debug any general storage issues when deploying " +"Charts in this repository." +msgstr "" +"This guide is to help users debug any general storage issues when deploying " +"Charts in this repository." + +msgid "" +"This guide is to help users debug any general storage issues when deploying " +"charts in this repository." +msgstr "" +"This guide is to help users debug any general storage issues when deploying " +"charts in this repository." + +msgid "" +"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm " +"the following commands should be run on each node:" +msgstr "" +"To deploy the HWE kernel, prior to deploying Kubernetes and OpenStack-Helm " +"the following commands should be run on each node:" + +msgid "" +"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue " +"described `here `_ is fixed." +msgstr "" +"To make use of CephFS in Ubuntu the HWE Kernel is required, until the issue " +"described `here `_ is fixed." + +msgid "To test MariaDB, do the following:" +msgstr "To test MariaDB, do the following:" + +msgid "" +"To validate persistent volume claim (PVC) creation, we've placed a test " +"manifest `here `_. Deploy this manifest and verify the job " +"completes successfully." +msgstr "" +"To validate persistent volume claim (PVC) creation, we've placed a test " +"manifest `here `_. Deploy this manifest and verify the job " +"completes successfully." + +msgid "Troubleshooting" +msgstr "Troubleshooting" + +msgid "Ubuntu HWE Kernel" +msgstr "Ubuntu HWE Kernel" + +msgid "" +"Use one of your Ceph Monitors to check the status of the cluster. A couple " +"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've " +"established a quorum, and we can see that all of our OSDs are up and in the " +"OSD map." +msgstr "" +"Use one of your Ceph Monitors to check the status of the cluster. A couple " +"of things to note above; our health is `HEALTH\\_OK`, we have 3 mons, we've " +"established a quorum, and we can see that all of our OSDs are up and in the " +"OSD map." + +msgid "" +"When discovering a new bug, please report a bug in `Storyboard `_." +msgstr "" +"When discovering a new bug, please report a bug in `Storyboard `_." + +msgid "" +"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. " +"For more information, see how to `activate namespace for ceph <../install/" +"multinode.html#activating-control-plane-namespace-for-ceph>`_." +msgstr "" +"Without this, your RBD-backed PVCs will never reach the ``Bound`` state. " +"For more information, see how to `activate namespace for Ceph <../install/" +"multinode.html#activating-control-plane-namespace-for-ceph>`_." diff --git a/doc/source/locale/en_GB/LC_MESSAGES/doc.po b/doc/source/locale/en_GB/LC_MESSAGES/doc.po new file mode 100644 index 0000000000..24722e9c31 --- /dev/null +++ b/doc/source/locale/en_GB/LC_MESSAGES/doc.po @@ -0,0 +1,433 @@ +# Andi Chandler , 2018. #zanata +msgid "" +msgstr "" +"Project-Id-Version: openstack-helm\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2018-12-11 21:29+0000\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"PO-Revision-Date: 2018-12-04 05:08+0000\n" +"Last-Translator: Andi Chandler \n" +"Language-Team: English (United Kingdom)\n" +"Language: en_GB\n" +"X-Generator: Zanata 4.3.3\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" + +msgid ":ref:`genindex`" +msgstr ":ref:`genindex`" + +msgid ":ref:`modindex`" +msgstr ":ref:`modindex`" + +msgid ":ref:`search`" +msgstr ":ref:`search`" + +msgid "Adding Services" +msgstr "Adding Services" + +msgid "Adding Tests" +msgstr "Adding Tests" + +msgid "" +"Any additional functions required for testing new charts or improving the " +"gate workflow should be placed in the appropriate location." +msgstr "" +"Any additional functions required for testing new charts or improving the " +"gate workflow should be placed in the appropriate location." + +msgid "" +"Any tests that do not use the Rally testing framework would need to be " +"handled in the appropriate manner in launch script. This would ideally " +"result in new functions that could be reused, or expansion of the gate " +"scripts to include scenarios beyond basic service launches." +msgstr "" +"Any tests that do not use the Rally testing framework would need to be " +"handled in the appropriate manner in launch script. This would ideally " +"result in new functions that could be reused, or expansion of the gate " +"scripts to include scenarios beyond basic service launches." + +msgid "" +"As charts for additional services are added to OpenStack-Helm, they should " +"be included in the gates. Adding new services to the gates allows a chart " +"developer and the review team to identify any potential issues associated " +"with a new service. All services are currently launched in the gate via a " +"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` " +"dictates the order these scripts are launched. The script should contain an " +"installation command like:" +msgstr "" +"As charts for additional services are added to OpenStack-Helm, they should " +"be included in the gates. Adding new services to the gates allows a chart " +"developer and the review team to identify any potential issues associated " +"with a new service. All services are currently launched in the gate via a " +"series of launch scripts of the format ``NNN-service-name.sh`` where ``NNN`` " +"dictates the order these scripts are launched. The script should contain an " +"installation command like:" + +msgid "" +"As new charts are developed and the services are added to the gate, an " +"associated Helm test should be introduced to the gates. The appropriate " +"place for executing these tests is in the respective service's launch " +"script, and must be placed after the entry for installing the service and " +"any associated overrides. Any tests that use the Rally testing framework " +"should leverage the helm_test_deployment function in the aforementioned " +"funcs/helm.sh file. For example, a Helm test for Mistral might look like:" +msgstr "" +"As new charts are developed and the services are added to the gate, an " +"associated Helm test should be introduced to the gates. The appropriate " +"place for executing these tests is in the respective service's launch " +"script, and must be placed after the entry for installing the service and " +"any associated overrides. Any tests that use the Rally testing framework " +"should leverage the helm_test_deployment function in the aforementioned " +"funcs/helm.sh file. For example, a Helm test for Mistral might look like:" + +msgid "" +"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard `_." +msgstr "" +"Bugs and enhancements are tracked via OpenStack-Helm's `Storyboard `_." + +msgid "Bugs should be filed as stories in Storyboard, not GitHub:" +msgstr "Bugs should be filed as stories in Storyboard, not GitHub:" + +msgid "Communication" +msgstr "Communication" + +msgid "" +"Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on " +"freenode" +msgstr "" +"Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on " +"freenode" + +msgid "Contents:" +msgstr "Contents:" + +msgid "Contributing" +msgstr "Contributing" + +msgid "" +"Developers wishing to work on the OpenStack-Helm project should always base " +"their work on the latest code, available from the OpenStack-Helm git " +"repository." +msgstr "" +"Developers wishing to work on the OpenStack-Helm project should always base " +"their work on the latest code, available from the OpenStack-Helm git " +"repository." + +msgid "" +"Functions for Helm specific operations, found in helm.sh. These functions " +"include: installing Helm, serving a Helm repository locally, linting and " +"building all Helm charts, running Helm tests on a release, installing the " +"helm template plugin, and running the helm template plugin against a chart." +msgstr "" +"Functions for Helm specific operations, found in helm.sh. These functions " +"include: installing Helm, serving a Helm repository locally, linting and " +"building all Helm charts, running Helm tests on a release, installing the " +"helm template plugin, and running the helm template plugin against a chart." + +msgid "" +"Functions for Kubernetes specific operations, found in kube.sh. These " +"functions include: waiting for pods in a specific namespace to register as " +"ready, waiting for all nodes to register as ready, install the requirements " +"for the kubeadm-aio container used in the gates, building the kubeadm-aio " +"container, launching the kubeadm-aio container, and replacing the kube-" +"controller-manager with a specific image necessary for ceph functionality." +msgstr "" +"Functions for Kubernetes specific operations, found in kube.sh. These " +"functions include: waiting for pods in a specific namespace to register as " +"ready, waiting for all nodes to register as ready, install the requirements " +"for the kubeadm-aio container used in the gates, building the kubeadm-aio " +"container, launching the kubeadm-aio container, and replacing the kube-" +"controller-manager with a specific image necessary for Ceph functionality." + +msgid "" +"Functions for OpenStack specific operations, found in openstack.sh. These " +"functions include: waiting for a successful ping, and waiting for a booted " +"virtual machine's status to return as ACTIVE." +msgstr "" +"Functions for OpenStack specific operations, found in openstack.sh. These " +"functions include: waiting for a successful ping, and waiting for a booted " +"virtual machine's status to return as ACTIVE." + +msgid "Functions for common host preparation operations, found in common.sh" +msgstr "Functions for common host preparation operations, found in common.sh" + +msgid "" +"Functions for network specific operations, found in network.sh. These " +"functions include: creating a backup of the host's resolv.conf file before " +"deploying the kubeadm environments, restoring the original resolv.conf " +"settings, creating a backup of the host's /etc/hosts file before adding the " +"hosts interface and address, and restoring the original /etc/hosts file." +msgstr "" +"Functions for network specific operations, found in network.sh. These " +"functions include: creating a backup of the host's resolv.conf file before " +"deploying the kubeadm environments, restoring the original resolv.conf " +"settings, creating a backup of the host's /etc/hosts file before adding the " +"hosts interface and address, and restoring the original /etc/hosts file." + +msgid "Gate Checks" +msgstr "Gate Checks" + +msgid "Gate Functions" +msgstr "Gate Functions" + +msgid "Gate Output" +msgstr "Gate Output" + +msgid "" +"If you would like to contribute to the development of OpenStack, you must " +"follow the steps in this page:" +msgstr "" +"If you would like to contribute to the development of OpenStack, you must " +"follow the steps in this page:" + +msgid "Indices and Tables" +msgstr "Indices and Tables" + +msgid "Installation and Development" +msgstr "Installation and Development" + +msgid "" +"Join us on `IRC `_: #openstack-" +"helm on freenode" +msgstr "" +"Join us on `IRC `_: #openstack-" +"helm on freenode" + +msgid "" +"Join us on `Slack `_ - " +"#openstack-helm" +msgstr "" +"Join us on `Slack `_ - " +"#openstack-helm" + +msgid "" +"Meeting Agenda Items: `Agenda `_" +msgstr "" +"Meeting Agenda Items: `Agenda `_" + +msgid "Mission" +msgstr "Mission" + +msgid "" +"Once those steps have been completed, changes to OpenStack should be " +"submitted for review via the Gerrit tool, following the workflow documented " +"at:" +msgstr "" +"Once those steps have been completed, changes to OpenStack should be " +"submitted for review via the Gerrit tool, following the workflow documented " +"at:" + +msgid "OpenStack-Helm" +msgstr "OpenStack-Helm" + +msgid "OpenStack-Helm Gates" +msgstr "OpenStack-Helm Gates" + +msgid "OpenStack-Helm currently checks the following scenarios:" +msgstr "OpenStack-Helm currently checks the following scenarios:" + +msgid "" +"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio " +"environment created and maintained for use as a development environment. " +"All information regarding the kubeadm-aio environment can be found here_." +msgstr "" +"OpenStack-Helm's single node and multinode gates leverage the kubeadm-aio " +"environment created and maintained for use as a development environment. " +"All information regarding the kubeadm-aio environment can be found here_." + +msgid "" +"Please review our `documentation `_. For quick installation, evaluation, and convenience, we have a " +"kubeadm based all-in-one solution that runs in a Docker container. The " +"Kubeadm-AIO set up can be found `here `_." +msgstr "" +"Please review our `documentation `_. For quick installation, evaluation, and convenience, we have a " +"kubeadm based all-in-one solution that runs in a Docker container. The " +"Kubeadm-AIO set up can be found `here `_." + +msgid "" +"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack " +"services. This check is provided for both a two node cluster and a three " +"node cluster." +msgstr "" +"Provisioning a multi-node Ubuntu-1604 cluster and deploying the OpenStack " +"services. This check is provided for both a two node cluster and a three " +"node cluster." + +msgid "" +"Provisioning a single node cluster and deploying the OpenStack services. " +"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25." +msgstr "" +"Provisioning a single node cluster and deploying the OpenStack services. " +"This check is provided for: Ubuntu-1604, CentOS-7, and Fedora-25." + +msgid "Pull requests submitted through GitHub will be ignored." +msgstr "Pull requests submitted through GitHub will be ignored." + +msgid "Repository" +msgstr "Repository" + +msgid "" +"Running Make on each chart, which lints and packages the charts. This gate " +"does not stand up a Kubernetes cluster." +msgstr "" +"Running Make on each chart, which lints and packages the charts. This gate " +"does not stand up a Kubernetes cluster." + +msgid "" +"Some services in the gate require specific overrides to the default values " +"in the chart's values.yaml file. If a service requires multiple overrides " +"to function in the gate, the service should include a separate values.yaml " +"file placed in the tools/overrides/mvp directory. The .yaml MVP " +"files provide a configuration file to use for overriding default " +"configuration values in the chart's values.yaml as an alternative to " +"overriding individual values during installation. A chart that requires a " +"MVP overrides file requires the following format:" +msgstr "" +"Some services in the gate require specific overrides to the default values " +"in the chart's values.yaml file. If a service requires multiple overrides " +"to function in the gate, the service should include a separate values.yaml " +"file placed in the tools/overrides/mvp directory. The .yaml MVP " +"files provide a configuration file to use for overriding default " +"configuration values in the chart's values.yaml as an alternative to " +"overriding individual values during installation. A chart that requires a " +"MVP overrides file requires the following format:" + +msgid "Storyboard" +msgstr "Storyboard" + +msgid "Testing any documentation changes and impacts." +msgstr "Testing any documentation changes and impacts." + +msgid "" +"The K8s directory contains the logs and output of the Kubernetes objects. " +"It includes: pods, nodes, secrets, services, namespaces, configmaps, " +"deployments, daemonsets, and statefulsets. Descriptions for the state of " +"all resources during execution are found here, and this information can " +"prove valuable when debugging issues raised during a check. When a single " +"node or multi-node check fails, this is the first place to look. The logs " +"found here are helpful when the templates render correctly, but the services " +"are not functioning correctly, whether due to service configuration issues " +"or issues with the pods themselves." +msgstr "" +"The K8s directory contains the logs and output of the Kubernetes objects. " +"It includes: pods, nodes, secrets, services, namespaces, configmaps, " +"deployments, daemonsets, and statefulsets. Descriptions for the state of " +"all resources during execution are found here, and this information can " +"prove valuable when debugging issues raised during a check. When a single " +"node or multi-node check fails, this is the first place to look. The logs " +"found here are helpful when the templates render correctly, but the services " +"are not functioning correctly, whether due to service configuration issues " +"or issues with the pods themselves." + +msgid "" +"The dry-runs directory contains the rendered output of Helm dry-run installs " +"on each of the OpenStack service charts. This gives visibility into the " +"manifests created by the templates with the supplied values. When the dry-" +"run gate fails, the reason should be apparent in the dry-runs output. The " +"logs found here are helpful in identifying issues resulting from using helm-" +"toolkit functions incorrectly or other rendering issues with gotpl." +msgstr "" +"The dry-runs directory contains the rendered output of Helm dry-run installs " +"on each of the OpenStack service charts. This gives visibility into the " +"manifests created by the templates with the supplied values. When the dry-" +"run gate fails, the reason should be apparent in the dry-runs output. The " +"logs found here are helpful in identifying issues resulting from using helm-" +"toolkit functions incorrectly or other rendering issues with gotpl." + +msgid "" +"The goal of OpenStack-Helm is to provide a collection of Helm charts that " +"simply, resiliently, and flexibly deploy OpenStack and related services on " +"Kubernetes." +msgstr "" +"The goal of OpenStack-Helm is to provide a collection of Helm charts that " +"simply, resiliently, and flexibly deploy OpenStack and related services on " +"Kubernetes." + +msgid "" +"The nodes directory contains information about the node the gate tests are " +"running on in openstack-infra. This includes: the network interfaces, the " +"contents of iptables, the host's resolv.conf, and the kernel IP routing " +"table. These logs can be helpful when trying to identify issues with host " +"networking or other issues at the node level." +msgstr "" +"The nodes directory contains information about the node the gate tests are " +"running on in openstack-infra. This includes: the network interfaces, the " +"contents of iptables, the host's resolv.conf, and the kernel IP routing " +"table. These logs can be helpful when trying to identify issues with host " +"networking or other issues at the node level." + +msgid "" +"This project is under active development. We encourage anyone interested in " +"OpenStack-Helm to review our `Installation `_ documentation. Feel free to ask " +"questions or check out our current `Storyboard backlog `_." +msgstr "" +"This project is under active development. We encourage anyone interested in " +"OpenStack-Helm to review our `Installation `_ documentation. Feel free to ask " +"questions or check out our current `Storyboard backlog `_." + +msgid "This results in the gate running the following:" +msgstr "This results in the gate running the following:" + +msgid "" +"To evaluate a multinode installation, follow the `Bare Metal `_ install guide." +msgstr "" +"To evaluate a multinode installation, follow the `Bare Metal `_ install guide." + +msgid "" +"To facilitate ease of testing and debugging, information regarding gates and " +"their functionality can be found here." +msgstr "" +"To facilitate ease of testing and debugging, information regarding gates and " +"their functionality can be found here." + +msgid "" +"To provide meaningful output from the gates, all information pertaining to " +"the components of the cluster and workflow are output to the logs directory " +"inside each gate. The contents of the log directory are as follows:" +msgstr "" +"To provide meaningful output from the gates, all information pertaining to " +"the components of the cluster and workflow are output to the logs directory " +"inside each gate. The contents of the log directory are as follows:" + +msgid "" +"To provide reusable components for gate functionality, functions have been " +"provided in the gates/funcs directory. These functions include:" +msgstr "" +"To provide reusable components for gate functionality, functions have been " +"provided in the gates/funcs directory. These functions include:" + +msgid "Welcome to OpenStack-Helm's documentation!" +msgstr "Welcome to OpenStack-Helm's documentation!" + +msgid "" +"`OpenStack-Helm git repository `_" +msgstr "" +"`OpenStack-Helm git repository `_" + +msgid "https://docs.openstack.org/infra/manual/developers.html" +msgstr "https://docs.openstack.org/infra/manual/developers.html" + +msgid "" +"https://docs.openstack.org/infra/manual/developers.html#development-workflow" +msgstr "" +"https://docs.openstack.org/infra/manual/developers.html#development-workflow" + +msgid "https://storyboard.openstack.org/#!/project/886" +msgstr "https://storyboard.openstack.org/#!/project/886"