# Andi Chandler <andi@gowling.com>, 2018. #zanata
# Andi Chandler <andi@gowling.com>, 2020. #zanata
msgid ""
msgstr ""
"Project-Id-Version: openstack-helm 0.1.1.dev3186\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-08-14 04:24+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2020-08-14 12:32+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\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 "**Check Chart Status**"
msgstr "**Check Chart Status**"

msgid ""
"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
"and Nova."
msgstr ""
"**First**, edit the ``values.yaml`` for Neutron, Glance, Horizon, Keystone, "
"and Nova."

msgid "**Review the Ingress configuration.**"
msgstr "**Review the Ingress configuration.**"

msgid ""
"**Second** option would be as ``--set`` flags when calling ``helm install``"
msgstr ""
"**Second** option would be as ``--set`` flags when calling ``helm install``"

msgid ""
"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
"OpenVSwitch or SR-IOV Nic Switch."
msgstr ""
"**TaaS Agent, TaaS OVS Driver and TaaS SR-IOV Driver**: This forms the back-"
"end of TaaS which runs as a ML2 agent extension on compute nodes. It handles "
"the RPC calls made by TaaS Plugin and configures the mechanism driver, i.e. "
"OpenVSwitch or SR-IOV Nic Switch."

msgid ""
"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
"resources in the Horizon Dashboard."
msgstr ""
"**TaaS Dashboard Plugin**: Horizon Plugin which adds GUI panels for TaaS "
"resources in the Horizon Dashboard."

msgid ""
"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
"configuration state to/from Neutron TaaS DB."
msgstr ""
"**TaaS Plugin**: This is the front-end of TaaS which runs on controller node "
"(Neutron server). This serves TaaS APIs and stores/retrieves TaaS "
"configuration state to/from Neutron TaaS DB."

msgid "16GB of RAM"
msgstr "16GB of RAM"

msgid "4 Cores"
msgstr "4 Cores"

msgid "48GB HDD"
msgstr "48GB HDD"

msgid "8 Cores"
msgstr "8 Cores"

msgid "8GB of RAM"
msgstr "8GB of RAM"

msgid ""
"A correct DPDK configuration depends heavily on the specific hardware "
"resources and its configuration. Before deploying Openvswitch with DPDK, "
"check the amount and type of available hugepages on the host OS."
msgstr ""
"A correct DPDK configuration depends heavily on the specific hardware "
"resources and its configuration. Before deploying Openvswitch with DPDK, "
"check the amount and type of available hugepages on the host OS."

msgid "Activate the OpenStack namespace to be able to use Ceph"
msgstr "Activate the OpenStack namespace to be able to use Ceph"

msgid "Activate the openstack namespace to be able to use Ceph"
msgstr "Activate the OpenStack namespace to be able to use Ceph"

msgid ""
"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/"
"horizon`` repo, i.e. https://opendev.org/openstack/horizon"
msgstr ""
"Add TaaS Dashboard dependency in ``requirements.txt`` file in ``openstack/"
"horizon`` repo, i.e. https://opendev.org/openstack/horizon"

msgid ""
"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` "
"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/"
"openstack/requirements"
msgstr ""
"Add TaaS and TaaS dashboard dependencies in :code:`upper-constraints.txt` "
"file in :code:`openstack/requirements` repo, i.e. https://opendev.org/"
"openstack/requirements"

msgid ""
"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` "
"repo, i.e. https://opendev.org/openstack/neutron"
msgstr ""
"Add TaaS dependency in ``requirements.txt`` file in ``openstack/neutron`` "
"repo, i.e. https://opendev.org/openstack/neutron"

msgid "Add TaaS panel to Horizon Dashboard:"
msgstr "Add TaaS panel to Horizon Dashboard:"

msgid ""
"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."
msgstr ""
"Add the address of the Kubernetes API, ``172.17.0.1``, and ``.svc.cluster."
"local`` to your ``no_proxy`` and ``NO_PROXY`` environment variables."

msgid ""
"Add to the Install steps these flags - also adding a shell environment "
"variable to save on repeat code."
msgstr ""
"Add to the Install steps these flags - also adding a shell environment "
"variable to save on repeat code."

msgid "Adding a DPDK port to Openvswitch fails"
msgstr "Adding a DPDK port to Openvswitch fails"

msgid ""
"Additional configuration variables can be found `here <https://github.com/"
"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
"be used to override the pod subnet set up by Calico (the default container "
"SDN), if you have a preexisting network that conflicts with the default pod "
"subnet of 192.168.0.0/16."
msgstr ""
"Additional configuration variables can be found `here <https://github.com/"
"openstack/openstack-helm-infra/blob/master/roles/deploy-kubeadm-aio-common/"
"defaults/main.yml>`_. In particular, ``kubernetes_cluster_pod_subnet`` can "
"be used to override the pod subnet set up by Calico (the default container "
"SDN), if you have a preexisting network that conflicts with the default pod "
"subnet of 192.168.0.0/16."

msgid ""
"Additional information on Kubernetes Ceph-based integration can be found in "
"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
"md>`_ provisioner."
msgstr ""
"Additional information on Kubernetes Ceph-based integration can be found in "
"the documentation for the `CephFS <https://github.com/kubernetes-incubator/"
"external-storage/blob/master/ceph/cephfs/README.md>`_ and `RBD <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/ceph/rbd/README."
"md>`_ storage provisioners, as well as for the alternative `NFS <https://"
"github.com/kubernetes-incubator/external-storage/blob/master/nfs/README."
"md>`_ provisioner."

msgid ""
"Additionally, the default configuration of the neutron chart must be adapted "
"according to the underlying hardware. The corresponding configuration "
"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/"
"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should "
"list all NICs which should be bound to DPDK with their corresponding PCI-"
"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, "
"etc."
msgstr ""
"Additionally, the default configuration of the neutron chart must be adapted "
"according to the underlying hardware. The corresponding configuration "
"parameter is labeled with \"CHANGE-ME\" in the script \"values_overrides/"
"dpdk.yaml\". Specifically, the \"ovs_dpdk\" configuration section should "
"list all NICs which should be bound to DPDK with their corresponding PCI-"
"IDs. Moreover, the name of each NIC needs to be unique, e.g., dpdk0, dpdk1, "
"etc."

msgid ""
"After making the configuration changes, run a ``make`` and then install as "
"you would from AIO or MultiNode instructions."
msgstr ""
"After making the configuration changes, run a ``make`` and then install as "
"you would from AIO or MultiNode instructions."

msgid ""
"All commands below should be run as a normal user, not as root. Appropriate "
"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
"used below, so there's no need to install them ahead of time."
msgstr ""
"All commands below should be run as a normal user, not as root. Appropriate "
"versions of Docker, Kubernetes, and Helm will be installed by the playbooks "
"used below, so there's no need to install them ahead of time."

msgid ""
"Alternatively, these steps can be performed by running the script directly::"
msgstr ""
"Alternatively, these steps can be performed by running the script directly::"

msgid ""
"Alternatively, this step can be performed by running the script directly:"
msgstr ""
"Alternatively, this step can be performed by running the script directly:"

msgid ""
"An Ingress is a collection of rules that allow inbound connections to reach "
"the cluster services."
msgstr ""
"An Ingress is a collection of rules that allow inbound connections to reach "
"the cluster services."

msgid ""
"Apart from the variables above with gerrit refspec values, additionally "
"export following environment variables with values as applicable:"
msgstr ""
"Apart from the variables above with gerrit refspec values, additionally "
"export following environment variables with values as applicable:"

msgid ""
"As a final validation step, re-run the **openstack helm stack list** and "
"**openstack helm keypair list** commands and confirm the returned results "
"are shown as empty.::"
msgstr ""
"As a final validation step, re-run the **openstack helm stack list** and "
"**openstack helm keypair list** commands and confirm the returned results "
"are shown as empty.::"

msgid ""
"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
"following modules:"
msgstr ""
"As any other Neutron plugin, TaaS neutron plugin functionality consists of "
"following modules:"

msgid ""
"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
"and/or Horizon LOCI images."
msgstr ""
"Before deploying TaaS and/or TaaS Dashboard, it needs to be added in Neutron "
"and/or Horizon LOCI images."

msgid ""
"Below are some instructions and suggestions to help you get started with a "
"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of "
"Linux can also be used, with the appropriate changes to package installation."
msgstr ""
"Below are some instructions and suggestions to help you get started with a "
"Kubeadm All-in-One environment on Ubuntu 18.04. Other supported versions of "
"Linux can also be used, with the appropriate changes to package installation."

msgid "Build the requirements LOCI image using above commit"
msgstr "Build the requirements LOCI image using above commit"

msgid ""
"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will "
"update resolv.conf as a result. If those IPs are blocked by your proxy, "
"running the OSH scripts will result in the inability to connect to anything "
"on the network. These DNS nameserver entries can be changed by updating the "
"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/"
"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``."
msgstr ""
"By default OSH will use Google DNS Server IPs (8.8.8.8, 8.8.4.4) and will "
"update resolv.conf as a result. If those IPs are blocked by your proxy, "
"running the OSH scripts will result in the inability to connect to anything "
"on the network. These DNS nameserver entries can be changed by updating the "
"external_dns_nameservers entry in the file ``openstack-helm-infra/tools/"
"images/kubeadm-aio/assets/opt/playbooks/vars.yaml``."

msgid ""
"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
"these CIDRs are not in use on the development node before proceeding, or "
"adjust as required."
msgstr ""
"By default the Calico CNI will use ``192.168.0.0/16`` and Kubernetes "
"services will use ``10.96.0.0/16`` as the CIDR for services. Check that "
"these CIDRs are not in use on the development node before proceeding, or "
"adjust as required."

msgid ""
"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
"by the proxy, this will overwrite the original DNS entries and result in the "
"inability to connect to anything on the network behind the proxy. These DNS "
"nameserver entries can be changed by updating the "
"``external_dns_nameservers`` entry in this file:"
msgstr ""
"By default, this installation will use Google DNS Server IPs (8.8.8.8, "
"8.8.4.4) and will update resolv.conf as a result. If those IPs are blocked "
"by the proxy, this will overwrite the original DNS entries and result in the "
"inability to connect to anything on the network behind the proxy. These DNS "
"nameserver entries can be changed by updating the "
"``external_dns_nameservers`` entry in this file:"

msgid ""
"Cinder deployment is not tested in the OSH development environment community "
"gates"
msgstr ""
"Cinder deployment is not tested in the OSH development environment community "
"gates"

msgid "Cleaning the Deployment"
msgstr "Cleaning the Deployment"

msgid "Clone the OpenStack-Helm Repos"
msgstr "Clone the OpenStack-Helm Repos"

msgid "Code examples below."
msgstr "Code examples below."

msgid "Common Deployment Requirements"
msgstr "Common Deployment Requirements"

msgid "Configure OpenStack"
msgstr "Configure OpenStack"

msgid "Configure TaaS in Neutron chart"
msgstr "Configure TaaS in Neutron chart"

msgid ""
"Configuring OpenStack for a particular production use-case is beyond the "
"scope of this guide. Please refer to the OpenStack `Configuration <https://"
"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
"version of OpenStack to determine what additional values overrides should be "
"provided to the OpenStack-Helm charts to ensure appropriate networking, "
"security, etc. is in place."
msgstr ""
"Configuring OpenStack for a particular production use-case is beyond the "
"scope of this guide. Please refer to the OpenStack `Configuration <https://"
"docs.openstack.org/latest/configuration/>`_ documentation for your selected "
"version of OpenStack to determine what additional values overrides should be "
"provided to the OpenStack-Helm charts to ensure appropriate networking, "
"security, etc. is in place."

msgid "Contents:"
msgstr "Contents:"

msgid ""
"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"
msgstr ""
"Copy the key: ``sudo cp ~/.ssh/id_rsa /etc/openstack-helm/deploy-key.pem``"

msgid "Create a patchset for ``openstack/horizon`` repo"
msgstr "Create a patchset for ``openstack/horizon`` repo"

msgid "Create a patchset for ``openstack/neutron`` repo"
msgstr "Create a patchset for ``openstack/neutron`` repo"

msgid "Create a patchset for ``openstack/requirements`` repo"
msgstr "Create a patchset for ``openstack/requirements`` repo"

msgid "Create an environment file"
msgstr "Create an environment file"

msgid "Create an inventory file"
msgstr "Create an inventory file"

msgid ""
"Create an ssh-key on the master node, and add the public key to each node "
"that you intend to join the cluster."
msgstr ""
"Create an ssh-key on the master node, and add the public key to each node "
"that you intend to join the cluster."

msgid "Create loopback devices for CEPH"
msgstr "Create loopback devices for CEPH"

msgid ""
"Create two loopback devices for ceph as one disk for OSD data and other disk "
"for block DB and block WAL. If loop0 and loop1  devices are busy in your "
"case , feel free to change them in parameters by using --ceph-osd-data and --"
"ceph-osd-dbwal options."
msgstr ""
"Create two loopback devices for Ceph as one disk for OSD data and other disk "
"for block DB and block WAL. If loop0 and loop1  devices are busy in your "
"case , feel free to change them in parameters by using --ceph-osd-data and --"
"ceph-osd-dbwal options."

msgid ""
"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
"override following parameter:"
msgstr ""
"Default log level for Neutron TaaS is :code:`INFO`. For changing it, "
"override following parameter:"

msgid "Delete the keypair(s) returned from the list command above::"
msgstr "Delete the keypair(s) returned from the list command above::"

msgid ""
"Delete the stacks returned from the *openstack helm stack list* command "
"above::"
msgstr ""
"Delete the stacks returned from the *openstack helm stack list* command "
"above::"

msgid ""
"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
"Refer to your specific proxy documentation."
msgstr ""
"Depending on your specific proxy, https_proxy may be the same as http_proxy. "
"Refer to your specific proxy documentation."

msgid "Deploy Barbican"
msgstr "Deploy Barbican"

msgid "Deploy Ceph"
msgstr "Deploy Ceph"

msgid "Deploy Cinder"
msgstr "Deploy Cinder"

msgid "Deploy Compute Kit (Nova and Neutron)"
msgstr "Deploy Compute Kit (Nova and Neutron)"

msgid "Deploy Glance"
msgstr "Deploy Glance"

msgid "Deploy Heat"
msgstr "Deploy Heat"

msgid "Deploy Horizon"
msgstr "Deploy Horizon"

msgid "Deploy Keystone"
msgstr "Deploy Keystone"

msgid "Deploy Kubernetes & Helm"
msgstr "Deploy Kubernetes & Helm"

msgid "Deploy Libvirt"
msgstr "Deploy Libvirt"

msgid "Deploy MariaDB"
msgstr "Deploy MariaDB"

msgid "Deploy Memcached"
msgstr "Deploy Memcached"

msgid "Deploy NFS Provisioner"
msgstr "Deploy NFS Provisioner"

msgid "Deploy OVS-DPDK"
msgstr "Deploy OVS-DPDK"

msgid "Deploy OpenStack-Helm"
msgstr "Deploy OpenStack-Helm"

msgid "Deploy OpenvSwitch"
msgstr "Deploy OpenvSwitch"

msgid "Deploy RabbitMQ"
msgstr "Deploy RabbitMQ"

msgid "Deploy Rados Gateway for object store"
msgstr "Deploy Rados Gateway for object store"

msgid "Deploy TaaS Dashboard Plugin"
msgstr "Deploy TaaS Dashboard Plugin"

msgid "Deploy TaaS Plugin"
msgstr "Deploy TaaS Plugin"

msgid "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"
msgstr "Deploy tap-as-a-service (TaaS) Neutron / Dashboard plugin"

msgid "Deploy the ingress controller"
msgstr "Deploy the ingress controller"

msgid "Deployment"
msgstr "Deployment"

msgid "Deployment With Ceph"
msgstr "Deployment With Ceph"

msgid "Deployment With NFS"
msgstr "Deployment With NFS"

msgid "Deployment with Tungsten Fabric"
msgstr "Deployment with Tungsten Fabric"

msgid "Development"
msgstr "Development"

msgid "Environment tear-down"
msgstr "Environment tear-down"

msgid ""
"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
"\" or \"keystone.openstack\" and will route those requests to the proper "
"internal K8s Services. These public listeners in Ingress must match the "
"external DNS that you will set up to access your OpenStack deployment. Note "
"each rule also has a Service that directs Ingress Controllers allow access "
"to the endpoints from within the cluster."
msgstr ""
"Essentially the use of Ingress for OpenStack-Helm is an Nginx proxy service. "
"Ingress (Nginx) is accessible by your cluster public IP - e.g. the IP "
"associated with ``kubectl get pods -o wide --all-namespaces | grep ingress-"
"api`` Ingress/Nginx will be listening for server name requests of \"keystone"
"\" or \"keystone.openstack\" and will route those requests to the proper "
"internal K8s Services. These public listeners in Ingress must match the "
"external DNS that you will set up to access your OpenStack deployment. Note "
"each rule also has a Service that directs Ingress Controllers allow access "
"to the endpoints from within the cluster."

msgid "Examples"
msgstr "Examples"

msgid ""
"Execution of the **900-use-it.sh** script results in the creation of 4 heat "
"stacks and a unique keypair enabling access to a newly created VM.  "
"Subsequent runs of the **900-use-it.sh** script requires deletion of the "
"stacks, a keypair, and key files, generated during the initial script "
"execution."
msgstr ""
"Execution of the **900-use-it.sh** script results in the creation of 4 heat "
"stacks and a unique keypair enabling access to a newly created VM.  "
"Subsequent runs of the **900-use-it.sh** script requires deletion of the "
"stacks, a keypair, and key files, generated during the initial script "
"execution."

msgid "Exercise the Cloud"
msgstr "Exercise the Cloud"

msgid "External DNS and FQDN"
msgstr "External DNS and FQDN"

msgid "External DNS to FQDN/Ingress"
msgstr "External DNS to FQDN/Ingress"

msgid ""
"First you have to set up OpenStack and Linux versions and install needed "
"packages"
msgstr ""
"First you have to set up OpenStack and Linux versions and install needed "
"packages"

msgid ""
"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"
msgstr ""
"For ``identity`` and ``dashboard`` at ``host_fdqn_override.public`` replace "
"``null`` with the value as ``keystone.os.foo.org`` and ``horizon.os.foo.org``"

msgid ""
"For a deployment without cinder and horizon the system requirements are:"
msgstr ""
"For a deployment without Cinder and Horizon the system requirements are:"

msgid ""
"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
"html>`__."
msgstr ""
"For a lab or proof-of-concept environment, the OpenStack-Helm gate scripts "
"can be used to quickly deploy a multinode Kubernetes cluster using KubeADM "
"and Ansible. Please refer to the deployment guide `here <./kubernetes-gate."
"html>`__."

msgid ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:"
msgstr ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\", so export the :code:`REQUIREMENTS_REF_SPEC` variable as follows:"

msgid ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:"
msgstr ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\"; so export the :code:`HORIZON_REF_SPEC` variable as follows:"

msgid ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:"
msgstr ""
"For example if gerrit refspec for this commit is \"refs/changes/xx/xxxxxx/x"
"\"; so export the :code:`NEUTRON_REF_SPEC` variable as follows:"

msgid "For more details, refer to TaaS specification: Tap-as-a-service_."
msgstr "For more details, refer to TaaS specification: Tap-as-a-service_."

msgid ""
"For other deployment options, select appropriate ``Deployment with ...`` "
"option from `Index <../developer/index.html>`__ page."
msgstr ""
"For other deployment options, select appropriate ``Deployment with ...`` "
"option from `Index <../developer/index.html>`__ page."

msgid "Gate-Based Kubernetes"
msgstr "Gate-Based Kubernetes"

msgid "Get the Nginx configuration from the Ingress Pod:"
msgstr "Get the Nginx configuration from the Ingress Pod:"

msgid "Get the ``helm status`` of your chart."
msgstr "Get the ``helm status`` of your chart."

msgid "Helm Chart Installation"
msgstr "Helm Chart Installation"

msgid ""
"Horizon deployment is not tested in the OSH development environment "
"community gates"
msgstr ""
"Horizon deployment is not tested in the OSH development environment "
"community gates"

msgid "Host Configuration"
msgstr "Host Configuration"

msgid "Host Proxy & DNS Configuration"
msgstr "Host Proxy & DNS Configuration"

msgid ""
"If OVS fails to start up because of no hugepages are available, check the "
"configuration of the OVS daemonset. Older versions of helm-toolkit were not "
"able to render hugepage configuration into the Kubernetes manifest and just "
"removed the hugepage attributes. If no hugepage configuration is defined for "
"the OVS daemonset, consider using a newer version of helm-toolkit."
msgstr ""
"If OVS fails to start up because of no hugepages are available, check the "
"configuration of the OVS daemonset. Older versions of helm-toolkit were not "
"able to render hugepage configuration into the Kubernetes manifest and just "
"removed the hugepage attributes. If no hugepage configuration is defined for "
"the OVS daemonset, consider using a newer version of helm-toolkit."

msgid ""
"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
"install/developer/index.html>`__, all the ``--set`` flags"
msgstr ""
"If doing an `AIO install <https://docs.openstack.org/openstack-helm/latest/"
"install/developer/index.html>`__, all the ``--set`` flags"

msgid ""
"If you are not deploying OSH behind a proxy, skip this step and continue "
"with \"Deploy Kubernetes & Helm\"."
msgstr ""
"If you are not deploying OSH behind a proxy, skip this step and continue "
"with \"Deploy Kubernetes & Helm\"."

msgid "If you are not deploying OSH behind a proxy, skip this step."
msgstr "If you are not deploying OSH behind a proxy, skip this step."

msgid ""
"Implementing the FQDN overrides **must** be done at install time. If you run "
"these as helm upgrades, Ingress will notice the updates though none of the "
"endpoint build-out jobs will run again, unless they are cleaned up manually "
"or using a tool like Armada."
msgstr ""
"Implementing the FQDN overrides **must** be done at install time. If you run "
"these as helm upgrades, Ingress will notice the updates though none of the "
"endpoint build-out jobs will run again, unless they are cleaned up manually "
"or using a tool like Armada."

msgid ""
"In order to access your OpenStack deployment on Kubernetes we can use the "
"Ingress Controller or NodePorts to provide a pathway in. A background on "
"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
"installation, examples, and troubleshooting will be discussed here."
msgstr ""
"In order to access your OpenStack deployment on Kubernetes we can use the "
"Ingress Controller or NodePorts to provide a pathway in. A background on "
"Ingress, OpenStack-Helm fully qualified domain name (FQDN) overrides, "
"installation, examples, and troubleshooting will be discussed here."

msgid ""
"In order to allow OVS inside a pod to make use of hugepages, the "
"corresponding type and amount of hugepages must be specified in the resource "
"section of the OVS chart's values.yaml:"
msgstr ""
"In order to allow OVS inside a pod to make use of hugepages, the "
"corresponding type and amount of hugepages must be specified in the resource "
"section of the OVS chart's values.yaml:"

msgid ""
"In order to deploy OSH behind a proxy, add the following entries to "
"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"
msgstr ""
"In order to deploy OSH behind a proxy, add the following entries to "
"``openstack-helm-infra/tools/gate/devel/local-vars.yaml``:"

msgid ""
"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
"yaml``."
msgstr ""
"In order to deploy OpenStack-Helm behind corporate proxy servers, add the "
"following entries to ``openstack-helm-infra/tools/gate/devel/local-vars."
"yaml``."

msgid ""
"In order to drive towards a production-ready OpenStack solution, our goal is "
"to provide containerized, yet stable `persistent volumes <https://kubernetes."
"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
"schedule applications that require state, such as MariaDB (Galera). Although "
"we assume that the project should provide a \"batteries included\" approach "
"towards persistent storage, we want to allow operators to define their own "
"solution as well. Examples of this work will be documented in another "
"section, however evidence of this is found throughout the project. If you "
"find any issues or gaps, please create a `story <https://storyboard."
"openstack.org/#!/project/886>`_ to track what can be done to improve our "
"documentation."
msgstr ""
"In order to drive towards a production-ready OpenStack solution, our goal is "
"to provide containerized, yet stable `persistent volumes <https://kubernetes."
"io/docs/concepts/storage/persistent-volumes/>`_ that Kubernetes can use to "
"schedule applications that require state, such as MariaDB (Galera). Although "
"we assume that the project should provide a \"batteries included\" approach "
"towards persistent storage, we want to allow operators to define their own "
"solution as well. Examples of this work will be documented in another "
"section, however evidence of this is found throughout the project. If you "
"find any issues or gaps, please create a `story <https://storyboard."
"openstack.org/#!/project/886>`_ to track what can be done to improve our "
"documentation."

msgid ""
"In the example above, bonding isn't used and hence an empty list is passed "
"in the \"bonds\" section."
msgstr ""
"In the example above, bonding isn't used and hence an empty list is passed "
"in the \"bonds\" section."

msgid ""
"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
"being used and 6 are still available."
msgstr ""
"In this example, 8 hugepages of 1G size have been allocated. 2 of those are "
"being used and 6 are still available."

msgid ""
"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA "
"socket 1. As a result, this NIC can only be used by OVS if"
msgstr ""
"In this example, the NIC with PCI-ID 0000:00:04.0 is connected to NUMA "
"socket 1. As a result, this NIC can only be used by OVS if"

msgid "Ingress"
msgstr "Ingress"

msgid "Install Basic Utilities"
msgstr "Install Basic Utilities"

msgid "Install OpenStack packages"
msgstr "Install OpenStack packages"

msgid "Install OpenStack-Helm"
msgstr "Install OpenStack-Helm"

msgid "Install k8s Minikube"
msgstr "Install k8s Minikube"

msgid "Installation"
msgstr "Installation"

msgid "Intro"
msgstr "Intro"

msgid ""
"It can be configured to give services externally-reachable URLs, load "
"balance traffic, terminate SSL, offer name based virtual hosting, and more."
msgstr ""
"It can be configured to give services externally-reachable URLs, load "
"balance traffic, terminate SSL, offer name based virtual hosting, and more."

msgid ""
"It is recommended to add your own existing DNS nameserver entries to avoid "
"losing connection."
msgstr ""
"It is recommended to add your own existing DNS nameserver entries to avoid "
"losing connection."

msgid "Kubernetes Preparation"
msgstr "Kubernetes Preparation"

msgid "Kubernetes and Common Setup"
msgstr "Kubernetes and Common Setup"

msgid "Latest Version Installs"
msgstr "Latest Version Installs"

msgid "List the keypair(s) generated during the script execution::"
msgstr "List the keypair(s) generated during the script execution::"

msgid ""
"List the stacks created during script execution which will need to be "
"deleted::"
msgstr ""
"List the stacks created during script execution which will need to be "
"deleted::"

msgid ""
"Look for *server* configuration with a *server_name* matching your desired "
"FQDN"
msgstr ""
"Look for *server* configuration with a *server_name* matching your desired "
"FQDN"

msgid ""
"Managing and configuring a Kubernetes cluster is beyond the scope of "
"OpenStack-Helm and this guide."
msgstr ""
"Managing and configuring a Kubernetes cluster is beyond the scope of "
"OpenStack-Helm and this guide."

msgid ""
"Manually remove the keypair directories created from the script in the ~/."
"ssh directory::"
msgstr ""
"Manually remove the keypair directories created from the script in the ~/."
"ssh directory::"

msgid ""
"Many of the default container images that are referenced across OpenStack-"
"Helm charts are not intended for production use; for example, while LOCI and "
"Kolla can be used to produce production-grade images, their public reference "
"images are not prod-grade.  In addition, some of the default images use "
"``latest`` or ``master`` tags, which are moving targets and can lead to "
"unpredictable behavior.  For production-like deployments, we recommend "
"building custom images, or at minimum caching a set of known images, and "
"incorporating them into OpenStack-Helm via values overrides."
msgstr ""
"Many of the default container images that are referenced across OpenStack-"
"Helm charts are not intended for production use; for example, while LOCI and "
"Kolla can be used to produce production-grade images, their public reference "
"images are not prod-grade.  In addition, some of the default images use "
"``latest`` or ``master`` tags, which are moving targets and can lead to "
"unpredictable behavior.  For production-like deployments, we recommend "
"building custom images, or at minimum caching a set of known images, and "
"incorporating them into OpenStack-Helm via values overrides."

msgid ""
"More information can be found in the `Openvswitch documentation <http://docs."
"openvswitch.org/en/latest/intro/install/dpdk/>`_."
msgstr ""
"More information can be found in the `Openvswitch documentation <http://docs."
"openvswitch.org/en/latest/intro/install/dpdk/>`_."

msgid ""
"More information on how to allocate and configure hugepages on the host OS "
"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
"en/latest/intro/install/dpdk/>`_."
msgstr ""
"More information on how to allocate and configure hugepages on the host OS "
"can be found in the `Openvswitch documentation <http://docs.openvswitch.org/"
"en/latest/intro/install/dpdk/>`_."

msgid "Multinode"
msgstr "Multinode"

msgid "Neutron TaaS support in Openstack-Helm commits:"
msgstr "Neutron TaaS support in Openstack-Helm commits:"

msgid "Neutron and Horizon LOCI images"
msgstr "Neutron and Horizon LOCI images"

msgid ""
"Note if you need to make a DNS change, you will have to do uninstall (``helm "
"delete <chart>``) and install again."
msgstr ""
"Note if you need to make a DNS change, you will have to do uninstall (``helm "
"delete <chart>``) and install again."

msgid ""
"Note that OVS-DPDK deployment has been tested with Openstack Rocky release "
"and Ubuntu Bionic container distributions. If the above variables aren't "
"set, the defaults (currently Openstack Ocata and Ubuntu Xenial) will be used."
msgstr ""
"Note that OVS-DPDK deployment has been tested with Openstack Rocky release "
"and Ubuntu Bionic container distributions. If the above variables aren't "
"set, the defaults (currently Openstack Ocata and Ubuntu Xenial) will be used."

msgid ""
"Note that this command will only enable you to auth successfully using the "
"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
"clouds.yaml`` and run::"
msgstr ""
"Note that this command will only enable you to auth successfully using the "
"``python-openstackclient`` CLI. To use legacy clients like the ``python-"
"novaclient`` from the CLI, reference the auth values in ``/etc/openstack/"
"clouds.yaml`` and run::"

msgid "OSH Proxy & DNS Configuration"
msgstr "OSH Proxy & DNS Configuration"

msgid ""
"OSH runs updates for local apt packages, so we will need to set the proxy "
"for apt as well by adding these lines to `/etc/apt/apt.conf`:"
msgstr ""
"OSH runs updates for local apt packages, so we will need to set the proxy "
"for apt as well by adding these lines to `/etc/apt/apt.conf`:"

msgid "OVS startup failure"
msgstr "OVS startup failure"

msgid ""
"On the host or master node, install the latest versions of Git, CA Certs & "
"Make if necessary"
msgstr ""
"On the host or master node, install the latest versions of Git, CA Certs & "
"Make if necessary"

msgid "On the master node create an environment file for the cluster:"
msgstr "On the master node create an environment file for the cluster:"

msgid "On the master node create an inventory file for the cluster:"
msgstr "On the master node create an inventory file for the cluster:"

msgid "On the master node run the playbooks:"
msgstr "On the master node run the playbooks:"

msgid "On the worker nodes:"
msgstr "On the worker nodes:"

msgid ""
"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
"with the OpenStack client, or the same heat templates that are used in the "
"validation gates."
msgstr ""
"Once OpenStack-Helm has been deployed, the cloud can be exercised either "
"with the OpenStack client, or the same Heat templates that are used in the "
"validation gates."

msgid ""
"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"
msgstr ""
"Once installed, access the API's or Dashboard at `http://horizon.os.foo.org`"

msgid ""
"Once the above requirements are met, start deploying Openstack Helm using "
"the deployment scripts under the dpdk directory in an increasing order"
msgstr ""
"Once the above requirements are met, start deploying Openstack Helm using "
"the deployment scripts under the dpdk directory in an increasing order"

msgid ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned onto each node in the cluster:"
msgstr ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned onto each node in the cluster:"

msgid ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned:"
msgstr ""
"Once the host has been configured the repos containing the OpenStack-Helm "
"charts should be cloned:"

msgid ""
"One can also specify the name of Openstack release and container OS "
"distribution as overrides before running the deployment scripts, for "
"instance,"
msgstr ""
"One can also specify the name of Openstack release and container OS "
"distribution as overrides before running the deployment scripts, for "
"instance,"

msgid ""
"OpenStack-Helm uses the hosts networking namespace for many pods including, "
"Ceph, Neutron and Nova components. For this, to function, as expected pods "
"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
"other distributions make use of ``mdns4_minimal`` which does not operate as "
"Kubernetes expects with its default TLD of ``.local``. To operate at "
"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
"confirm that it matches:"
msgstr ""
"OpenStack-Helm uses the hosts networking namespace for many pods including, "
"Ceph, Neutron and Nova components. For this, to function, as expected pods "
"need to be able to resolve DNS requests correctly. Ubuntu Desktop and some "
"other distributions make use of ``mdns4_minimal`` which does not operate as "
"Kubernetes expects with its default TLD of ``.local``. To operate at "
"expected either change the ``hosts`` line in the ``/etc/nsswitch.conf``, or "
"confirm that it matches:"

msgid ""
"OpenStack-Helm utilizes the `Kubernetes Ingress Controller <https://"
"kubernetes.io/docs/concepts/services-networking/ingress/>`__"
msgstr ""
"OpenStack-Helm utilises the `Kubernetes Ingress Controller <https://"
"kubernetes.io/docs/concepts/services-networking/ingress/>`__"

msgid "OpenStack-Helm-Infra KubeADM deployment"
msgstr "OpenStack-Helm-Infra KubeADM deployment"

msgid ""
"Other versions and considerations (such as other CNI SDN providers), config "
"map data, and value overrides will be included in other documentation as we "
"explore these options further."
msgstr ""
"Other versions and considerations (such as other CNI SDN providers), config "
"map data, and value overrides will be included in other documentation as we "
"explore these options further."

msgid "Override images in Neutron chart"
msgstr "Override images in Neutron chart"

msgid ""
"Override the :code:`images` section parameters for Neutron chart with the "
"custom LOCI image's tag, prepared as explained in above sections."
msgstr ""
"Override the :code:`images` section parameters for Neutron chart with the "
"custom LOCI image's tag, prepared as explained in above sections."

msgid "Overview"
msgstr "Overview"

msgid "PMD threads have been assigned to NUMA socket 1."
msgstr "PMD threads have been assigned to NUMA socket 1."

msgid "Passwordless Sudo"
msgstr "Passwordless Sudo"

msgid ""
"Please see the supported application versions outlined in the `source "
"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
"roles/build-images/defaults/main.yml>`_."
msgstr ""
"Please see the supported application versions outlined in the `source "
"variable file <https://github.com/openstack/openstack-helm-infra/blob/master/"
"roles/build-images/defaults/main.yml>`_."

msgid "Plugins"
msgstr "Plugins"

msgid "Prepare LOCI images"
msgstr "Prepare LOCI images"

msgid ""
"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
"`docker build --build-arg WHEELS` command argument."
msgstr ""
"Prepare Neutron or Horizon LOCI image using this requirements image as :code:"
"`docker build --build-arg WHEELS` command argument."

msgid ""
"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
"installed."
msgstr ""
"Prepare a requirements LOCI image with Neutron TaaS and TaaS Dashboard code "
"installed."

msgid ""
"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
"OpenStack endpoints you will want to expose for API and Dashboard access."
msgstr ""
"Prepare ahead of time your FQDN and DNS layouts. There are a handful of "
"OpenStack endpoints you will want to expose for API and Dashboard access."

msgid "Prepare host"
msgstr "Prepare host"

msgid "Prepare host and openstack helm for tf"
msgstr "Prepare host and OpenStack Helm for tf"

msgid "Proxy Configuration"
msgstr "Proxy Configuration"

msgid "Putting it all together"
msgstr "Putting it all together"

msgid "References"
msgstr "References"

msgid "Removing Helm Charts"
msgstr "Removing Helm Charts"

msgid "Requirements"
msgstr "Requirements"

msgid "Requirements LOCI image"
msgstr "Requirements LOCI image"

msgid "Requirements and Host Configuration"
msgstr "Requirements and Host Configuration"

msgid "Run the playbooks"
msgstr "Run the playbooks"

msgid "SSH-Key preparation"
msgstr "SSH-Key preparation"

msgid ""
"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
"pem``"
msgstr ""
"Set correct ownership: ``sudo chown ubuntu /etc/openstack-helm/deploy-key."
"pem``"

msgid "Set log level for TaaS"
msgstr "Set log level for TaaS"

msgid ""
"Set your local environment variables to use the proxy information. This "
"involves adding or setting the following values in ``/etc/environment``:"
msgstr ""
"Set your local environment variables to use the proxy information. This "
"involves adding or setting the following values in ``/etc/environment``:"

msgid "Setup Clients on the host and assemble the charts"
msgstr "Setup Clients on the host and assemble the charts"

msgid "Setup DNS for use cluster DNS"
msgstr "Setup DNS for use cluster DNS"

msgid "Setup Glance"
msgstr "Setup Glance"

msgid "Setup Heat"
msgstr "Setup Heat"

msgid "Setup Ingress"
msgstr "Setup Ingress"

msgid "Setup Keystone"
msgstr "Setup Keystone"

msgid "Setup MariaDB"
msgstr "Setup MariaDB"

msgid "Setup Memcached"
msgstr "Setup Memcached"

msgid "Setup NFS"
msgstr "Setup NFS"

msgid "Setup Neutron and Nova"
msgstr "Setup Neutron and Nova"

msgid "Setup OpenStack client"
msgstr "Setup OpenStack client"

msgid "Setup RabbitMQ"
msgstr "Setup RabbitMQ"

msgid "Setup Tungsten Fabric"
msgstr "Setup Tungsten Fabric"

msgid "Setup env for apply values_overrides"
msgstr "Setup env for apply values_overrides"

msgid "Setup libvirt"
msgstr "Setup libvirt"

msgid "Setup the gateway to the public network"
msgstr "Setup the gateway to the public network"

msgid "Subsequent Runs & Post Clean-up"
msgstr "Subsequent Runs & Post Clean-up"

msgid "System Requirements"
msgstr "System Requirements"

msgid "TaaS Architecture"
msgstr "TaaS Architecture"

msgid ""
"TaaS dashboard plugin can be deployed simply by using custom LOCI images "
"having TaaS Dashboard code installed (as explained in above sections), i.e. "
"override the :code:`images` section parameters for Horizon charts:"
msgstr ""
"TaaS dashboard plugin can be deployed simply by using custom LOCI images "
"having TaaS Dashboard code installed (as explained in above sections), i.e. "
"override the :code:`images` section parameters for Horizon charts:"

msgid ""
"TaaS plugin provides a mechanism to mirror certain traffic (for example "
"tagged with specific VLANs) from a source VM to any traffic analyzer VM. "
"When packet will be forwarded, the original value of source and target ip/"
"ports information will not be altered and the system administrator will be "
"able to run, for ex. tcpdump, on the target VM to trace these packets."
msgstr ""
"TaaS plugin provides a mechanism to mirror certain traffic (for example "
"tagged with specific VLANs) from a source VM to any traffic analyser VM. "
"When packet will be forwarded, the original value of source and target ip/"
"ports information will not be altered and the system administrator will be "
"able to run, for ex. tcpdump, on the target VM to trace these packets."

msgid ""
"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
"Neither operation should require a password."
msgstr ""
"Test this by ssh'ing to a node and then executing a command with 'sudo'. "
"Neither operation should require a password."

msgid ""
"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd "
"log:"
msgstr ""
"The NUMA socket a given NIC is connected to can be found in the ovs-vswitchd "
"log:"

msgid ""
"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
"charts can be performed by running the following commands:"
msgstr ""
"The OpenStack clients and Kubernetes RBAC rules, along with assembly of the "
"charts can be performed by running the following commands:"

msgid ""
"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
"docker to run."
msgstr ""
"The `./tools/deployment/multinode/kube-node-subnet.sh` script requires "
"docker to run."

msgid ""
"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
"to communicate without being routed through proxy servers. The IP address "
"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
"Replace the addresses if your configuration does not match the one defined "
"above."
msgstr ""
"The ``.svc.cluster.local`` address is required to allow the OpenStack client "
"to communicate without being routed through proxy servers. The IP address "
"``172.17.0.1`` is the advertised IP address for the Kubernetes API server. "
"Replace the addresses if your configuration does not match the one defined "
"above."

msgid "The default FQDN's for OpenStack-Helm are"
msgstr "The default FQDN's for OpenStack-Helm are"

msgid ""
"The example above uses the default values used by ``openstack-helm-infra``."
msgstr ""
"The example above uses the default values used by ``openstack-helm-infra``."

msgid ""
"The following commands all assume that they are run from the ``/opt/"
"openstack-helm`` directory."
msgstr ""
"The following commands all assume that they are run from the ``/opt/"
"openstack-helm`` directory."

msgid ""
"The following commands all assume that they are run from the ``openstack-"
"helm`` directory and the repos have been cloned as above."
msgstr ""
"The following commands all assume that they are run from the ``openstack-"
"helm`` directory and the repos have been cloned as above."

msgid ""
"The following steps serve as a guide to clean-up the client environment by "
"deleting stacks and respective artifacts created during the **900-use-it."
"sh** script:"
msgstr ""
"The following steps serve as a guide to clean-up the client environment by "
"deleting stacks and respective artefacts created during the **900-use-it."
"sh** script:"

msgid ""
"The installation procedures below, will take an administrator from a new "
"``kubeadm`` installation to OpenStack-Helm deployment."
msgstr ""
"The installation procedures below, will take an administrator from a new "
"``kubeadm`` installation to OpenStack-Helm deployment."

msgid ""
"The mapping of CPU cores to NUMA sockets can be determined by means of "
"``lspci``, for instance:"
msgstr ""
"The mapping of CPU cores to NUMA sockets can be determined by means of "
"``lspci``, for instance:"

msgid "The recommended minimum system requirements for a full deployment are:"
msgstr "The recommended minimum system requirements for a full deployment are:"

msgid ""
"The script below configures Ceph to use loopback devices created in previous "
"step as backend for ceph osds. To configure a custom block device-based "
"backend, please refer to the ``ceph-osd`` `values.yaml <https://github.com/"
"openstack/openstack-helm/blob/master/ceph-osd/values.yaml>`_."
msgstr ""
"The script below configures Ceph to use loopback devices created in previous "
"step as backend for ceph osds. To configure a custom block device-based "
"backend, please refer to the ``ceph-osd`` `values.yaml <https://github.com/"
"openstack/openstack-helm/blob/master/ceph-osd/values.yaml>`_."

msgid ""
"The upstream Ceph image repository does not currently pin tags to specific "
"Ceph point releases.  This can lead to unpredictable results in long-lived "
"deployments.  In production scenarios, we strongly recommend overriding the "
"Ceph images to use either custom built images or controlled, cached images."
msgstr ""
"The upstream Ceph image repository does not currently pin tags to specific "
"Ceph point releases.  This can lead to unpredictable results in long-lived "
"deployments.  In production scenarios, we strongly recommend overriding the "
"Ceph images to use either custom built images or controlled, cached images."

msgid ""
"These commands will restore the environment back to a clean Kubernetes "
"deployment, that can either be manually removed or over-written by "
"restarting the deployment process. It is recommended to restart the host "
"before doing so to ensure any residual state, eg. Network interfaces are "
"removed."
msgstr ""
"These commands will restore the environment back to a clean Kubernetes "
"deployment, that can either be manually removed or over-written by "
"restarting the deployment process. It is recommended to restart the host "
"before doing so to ensure any residual state, eg. Network interfaces are "
"removed."

msgid "These values can be retrieved by running:"
msgstr "These values can be retrieved by running:"

msgid ""
"This command will deploy a single node KubeADM administered cluster. This "
"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to "
"control the deployment, which can be over-ridden by adding entries to ``"
"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``."
msgstr ""
"This command will deploy a single node KubeADM administered cluster. This "
"will use the parameters in ``${OSH_INFRA_PATH}/playbooks/vars.yaml`` to "
"control the deployment, which can be over-ridden by adding entries to ``"
"${OSH_INFRA_PATH}/tools/gate/devel/local-vars.yaml``."

msgid ""
"This guide assumes that users wishing to deploy behind a proxy have already "
"defined the conventional proxy environment variables ``http_proxy``, "
"``https_proxy``, and ``no_proxy``."
msgstr ""
"This guide assumes that users wishing to deploy behind a proxy have already "
"defined the conventional proxy environment variables ``http_proxy``, "
"``https_proxy``, and ``no_proxy``."

msgid "This guide covers the minimum number of requirements to get started."
msgstr "This guide covers the minimum number of requirements to get started."

msgid ""
"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
"TaaS Dashboard plugin in Neutron and Horizon charts respectively."
msgstr ""
"This guide explains how to deploy tap-as-a-service (TaaS) Neutron plugin and "
"TaaS Dashboard plugin in Neutron and Horizon charts respectively."

msgid ""
"This installation, by default will use Google DNS servers, 8.8.8.8 or "
"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
"change must be done on each node in your cluster."
msgstr ""
"This installation, by default will use Google DNS servers, 8.8.8.8 or "
"8.8.4.4 and updates resolv.conf. These DNS nameserver entries can be changed "
"by updating file ``/opt/openstack-helm-infra/tools/images/kubeadm-aio/assets/"
"opt/playbooks/vars.yaml`` under section ``external_dns_nameservers``. This "
"change must be done on each node in your cluster."

msgid "This is a two step process, i.e."
msgstr "This is a two step process, i.e."

msgid ""
"This script will create two loopback devices for Ceph as one disk for OSD "
"data and other disk for block DB and block WAL. If default devices (loop0 "
"and loop1) are busy in your case, feel free to change them by exporting "
"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)."
msgstr ""
"This script will create two loopback devices for Ceph as one disk for OSD "
"data and other disk for block DB and block WAL. If default devices (loop0 "
"and loop1) are busy in your case, feel free to change them by exporting "
"environment variables(CEPH_OSD_DATA_DEVICE and CEPH_OSD_DB_WAL_DEVICE)."

msgid ""
"This will delete all Kubernetes resources generated when the chart was "
"instantiated. However for OpenStack charts, by default, this will not delete "
"the database and database users that were created when the chart was "
"installed. All OpenStack projects can be configured such that upon deletion, "
"their database will also be removed. To delete the database when the chart "
"is deleted the database drop job must be enabled before installing the "
"chart. There are two ways to enable the job, set the job_db_drop value to "
"true in the chart's ``values.yaml`` file, or override the value using the "
"helm install command as follows:"
msgstr ""
"This will delete all Kubernetes resources generated when the chart was "
"instantiated. However for OpenStack charts, by default, this will not delete "
"the database and database users that were created when the chart was "
"installed. All OpenStack projects can be configured such that upon deletion, "
"their database will also be removed. To delete the database when the chart "
"is deleted the database drop job must be enabled before installing the "
"chart. There are two ways to enable the job, set the job_db_drop value to "
"true in the chart's ``values.yaml`` file, or override the value using the "
"helm install command as follows:"

msgid ""
"Throughout this guide the assumption is that the user is: ``ubuntu``. "
"Because this user has to execute root level commands remotely to other "
"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
"node:"
msgstr ""
"Throughout this guide the assumption is that the user is: ``ubuntu``. "
"Because this user has to execute root level commands remotely to other "
"nodes, it is advised to add the following lines to ``/etc/sudoers`` for each "
"node:"

msgid ""
"To allocate PMD threads to NUMA sockets in OVS, ensure that the "
"``pmd_cpu_mask`` attribute in values.yaml includes CPU sockets on the "
"corresponding NUMA socket. In the example below, the mask of 0xf covers the "
"first 4 CPU cores which are dsitributed across NUMA sockets 0 and 1."
msgstr ""
"To allocate PMD threads to NUMA sockets in OVS, ensure that the "
"``pmd_cpu_mask`` attribute in values.yaml includes CPU sockets on the "
"corresponding NUMA socket. In the example below, the mask of 0xf covers the "
"first 4 CPU cores which are dsitributed across NUMA sockets 0 and 1."

msgid ""
"To allocate hugepages to NUMA sockets in OVS, ensure that the "
"``socket_memory`` attribute in values.yaml specifies a value for the "
"corresponding NUMA socket. In the following example, OVS will use one 1G "
"hugepage for NUMA socket 0 and socket 1."
msgstr ""
"To allocate hugepages to NUMA sockets in OVS, ensure that the "
"``socket_memory`` attribute in values.yaml specifies a value for the "
"corresponding NUMA socket. In the following example, OVS will use one 1G "
"hugepage for NUMA socket 0 and socket 1."

msgid ""
"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy "
"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."
msgstr ""
"To continue to deploy OpenStack on Kubernetes via OSH, see :doc:`Deploy "
"NFS<./deploy-with-nfs>` or :doc:`Deploy Ceph<./deploy-with-ceph>`."

msgid ""
"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"
msgstr ""
"To copy the ssh key to each node, this can be accomplished with the ``ssh-"
"copy-id`` command, for example: *ssh-copy-id ubuntu@192.168.122.178*"

msgid "To delete an installed helm chart, use the following command:"
msgstr "To delete an installed helm chart, use the following command:"

msgid "To generate the key you can use ``ssh-keygen -t rsa``"
msgstr "To generate the key you can use ``ssh-keygen -t rsa``"

msgid "To get started with OSH, we will need both ``git`` and ``curl``."
msgstr "To get started with OSH, we will need both ``git`` and ``curl``."

msgid ""
"To run further commands from the CLI manually, execute the following to set "
"up authentication credentials::"
msgstr ""
"To run further commands from the CLI manually, execute the following to set "
"up authentication credentials::"

msgid ""
"To tear-down, the development environment charts should be removed first "
"from the 'openstack' namespace and then the 'ceph' namespace using the "
"commands from the `Removing Helm Charts` section. Additionally charts should "
"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
"backing or bare metal development support. You can run the following "
"commands to loop through and delete the charts, then stop the kubelet "
"systemd unit and remove all the containers before removing the directories "
"used on the host by pods."
msgstr ""
"To tear-down, the development environment charts should be removed first "
"from the 'openstack' namespace and then the 'ceph' namespace using the "
"commands from the `Removing Helm Charts` section. Additionally charts should "
"be removed from the 'nfs' and 'libvirt' namespaces if deploying with NFS "
"backing or bare metal development support. You can run the following "
"commands to loop through and delete the charts, then stop the kubelet "
"systemd unit and remove all the containers before removing the directories "
"used on the host by pods."

msgid "Troubleshooting"
msgstr "Troubleshooting"

msgid ""
"Tungsten Fabric is the multicloud and multistack network solution which you "
"can use for your OpenStack as a network plugin. This document decribes how "
"you can deploy a single node Open Stack based on Tungsten Fabric using "
"openstack helm for development purpose."
msgstr ""
"Tungsten Fabric is the multicloud and multistack network solution which you "
"can use for your OpenStack as a network plugin. This document describes how "
"you can deploy a single node Open Stack based on Tungsten Fabric using "
"OpenStack helm for development purpose."

msgid ""
"Two similar options exist to set the FQDN overrides for External DNS mapping."
msgstr ""
"Two similar options exist to set the FQDN overrides for External DNS mapping."

msgid ""
"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
"required to use CephFS."
msgstr ""
"Until the Ubuntu kernel shipped with 16.04 supports CephFS subvolume mounts "
"by default the `HWE Kernel <../troubleshooting/ubuntu-hwe-kernel.html>`__ is "
"required to use CephFS."

msgid ""
"Update your lab/environment DNS server with your appropriate host values "
"creating A Records for the edge node IP's and various FQDN's. Alternatively "
"you can test these settings locally by editing your ``/etc/hosts``. Below is "
"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
"``1.2.3.4``."
msgstr ""
"Update your lab/environment DNS server with your appropriate host values "
"creating A Records for the edge node IP's and various FQDN's. Alternatively "
"you can test these settings locally by editing your ``/etc/hosts``. Below is "
"an example with a dummy domain ``os.foo.org`` and dummy Ingress IP "
"``1.2.3.4``."

msgid ""
"Use above gerrit commits to prepare the LOCI images using following script:"
msgstr ""
"Use above gerrit commits to prepare the LOCI images using following script:"

msgid ""
"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` "
"command argument to build the requirements LOCI image."
msgstr ""
"Use it as ``docker build --build-arg PROJECT_REF=${REQUIREMENTS_REF_SPEC}`` "
"command argument to build the requirements LOCI image."

msgid "Using Horizon as an example, find the ``endpoints`` config."
msgstr "Using Horizon as an example, find the ``endpoints`` config."

msgid ""
"Using the Helm packages previously pushed to the local Helm repository, run "
"the following commands to instruct tiller to create an instance of the given "
"chart. During installation, the helm client will print useful information "
"about resources created, the state of the Helm releases, and whether any "
"additional configuration steps are necessary."
msgstr ""
"Using the Helm packages previously pushed to the local Helm repository, run "
"the following commands to instruct tiller to create an instance of the given "
"chart. During installation, the helm client will print useful information "
"about resources created, the state of the Helm releases, and whether any "
"additional configuration steps are necessary."

msgid "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"
msgstr "Verify the *v1beta1/Ingress* resource has a Host with your FQDN value"

msgid ""
"We are also going to seperate Ceph metadata and data onto a different "
"devices to replicate the ideal scenario of fast disks for metadata and slow "
"disks to store data. You can change this as per your design by referring to "
"the documentation explained in ../openstack-helm-infra/ceph-osd/values.yaml"
msgstr ""
"We are also going to separate Ceph metadata and data onto a different "
"devices to replicate the ideal scenario of fast disks for metadata and slow "
"disks to store data. You can change this as per your design by referring to "
"the documentation explained in ../openstack-helm-infra/ceph-osd/values.yaml"

msgid ""
"We are going to install Ceph OSDs backed by loopback devices as this will "
"help us not to attach extra disks, in case if you have enough disks on the "
"node then feel free to skip creating loopback devices by exporting "
"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the  block devices "
"names as environment variables(CEPH_OSD_DATA_DEVICE and "
"CEPH_OSD_DB_WAL_DEVICE)."
msgstr ""
"We are going to install Ceph OSDs backed by loopback devices as this will "
"help us not to attach extra disks, in case if you have enough disks on the "
"node then feel free to skip creating loopback devices by exporting "
"CREATE_LOOPBACK_DEVICES_FOR_CEPH to false and export the  block devices "
"names as environment variables(CEPH_OSD_DATA_DEVICE and "
"CEPH_OSD_DB_WAL_DEVICE)."

msgid ""
"We want to change the **public** configurations to match our DNS layouts "
"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
"has ``host_fqdn_override``'s for each API that the Chart either produces or "
"is dependent on. `Read more about how Endpoints are developed <https://docs."
"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
"Glance Registry is listening on a Ingress http endpoint, you will not need "
"to expose the registry for external services."
msgstr ""
"We want to change the **public** configurations to match our DNS layouts "
"above. In each Chart ``values.yaml`` is a ``endpoints`` configuration that "
"has ``host_fqdn_override``'s for each API that the Chart either produces or "
"is dependent on. `Read more about how Endpoints are developed <https://docs."
"openstack.org/openstack-helm/latest/devref/endpoints.html>`__. Note while "
"Glance Registry is listening on a Ingress http endpoint, you will not need "
"to expose the registry for external services."

msgid ""
"When adding a DPDK port (a NIC bound to DPDK) to OVS fails, one source of "
"error is related to an incorrect configuration with regards to the NUMA "
"topology of the underlying hardware. Every NIC is connected to one specific "
"NUMA socket. In order to use a NIC as DPDK port in OVS, the OVS "
"configuration regarding hugepages and PMD threas needs to match the NUMA "
"topology."
msgstr ""
"When adding a DPDK port (a NIC bound to DPDK) to OVS fails, one source of "
"error is related to an incorrect configuration with regards to the NUMA "
"topology of the underlying hardware. Every NIC is connected to one specific "
"NUMA socket. In order to use a NIC as DPDK port in OVS, the OVS "
"configuration regarding hugepages and PMD threas needs to match the NUMA "
"topology."

msgid ""
"While deploying neutron-server and L2 agents, TaaS should be enabled in "
"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: "
"plugins`` section to add TaaS as a L2 agent extension; in ``conf: "
"taas_plugin`` section to configure the ``service_provider`` endpoint used by "
"Neutron TaaS plugin:"
msgstr ""
"While deploying neutron-server and L2 agents, TaaS should be enabled in "
"``conf: neutron`` section to add TaaS as a service plugin; in ``conf: "
"plugins`` section to add TaaS as a L2 agent extension; in ``conf: "
"taas_plugin`` section to configure the ``service_provider`` endpoint used by "
"Neutron TaaS plugin:"

msgid ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. For production deployments, please "
"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
"e.g.:"
msgstr ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. For production deployments, please "
"choose (and tune appropriately) a highly-resilient Kubernetes distribution, "
"e.g.:"

msgid ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. This guide describes how to simply "
"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
"which use KubeADM and Ansible. Although this cluster won't be production-"
"grade, it will serve as a quick starting point in a lab or proof-of-concept "
"environment."
msgstr ""
"You can use any Kubernetes deployment tool to bring up a working Kubernetes "
"cluster for use with OpenStack-Helm. This guide describes how to simply "
"stand up a multinode Kubernetes cluster via the OpenStack-Helm gate scripts, "
"which use KubeADM and Ansible. Although this cluster won't be production-"
"grade, it will serve as a quick starting point in a lab or proof-of-concept "
"environment."

msgid ""
"You may now deploy kubernetes, and helm onto your machine, first move into "
"the ``openstack-helm`` directory and then run the following:"
msgstr ""
"You may now deploy kubernetes, and helm onto your machine, first move into "
"the ``openstack-helm`` directory and then run the following:"

msgid ""
"Your changes to `/etc/environment` will not be applied until you source them:"
msgstr ""
"Your changes to `/etc/environment` will not be applied until you source them:"

msgid ""
"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
"platform"
msgstr ""
"`Airship <https://airshipit.org/>`_, a declarative open cloud infrastructure "
"platform"

msgid ""
"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
">`_, the foundation of a number of Kubernetes installation solutions"
msgstr ""
"`KubeADM <https://kubernetes.io/docs/setup/independent/high-availability/"
">`_, the foundation of a number of Kubernetes installation solutions"

msgid "https://review.openstack.org/#/c/597200/"
msgstr "https://review.openstack.org/#/c/597200/"

msgid "https://review.openstack.org/#/c/607392/"
msgstr "https://review.openstack.org/#/c/607392/"

msgid "https://review.openstack.org/#/c/621606/"
msgstr "https://review.openstack.org/#/c/621606/"

msgid "hugepages have been allocated on NUMA socket 1 by OVS, and"
msgstr "hugepages have been allocated on NUMA socket 1 by OVS, and"

msgid ""
"if you are rerunning the below script then make sure to skip the loopback "
"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false."
msgstr ""
"if you are rerunning the below script then make sure to skip the loopback "
"device creation by exporting CREATE_LOOPBACK_DEVICES_FOR_CEPH to false."

msgid ""
"node_one, node_two and node_three below are all worker nodes, children of "
"the master node that the commands below are executed on."
msgstr ""
"node_one, node_two and node_three below are all worker nodes, children of "
"the master node that the commands below are executed on."
