2801 lines
113 KiB
Plaintext
2801 lines
113 KiB
Plaintext
# Andi Chandler <andi@gowling.com>, 2020. #zanata
|
|
# Andi Chandler <andi@gowling.com>, 2021. #zanata
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: openstack-helm 0.1.1.dev3462\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"POT-Creation-Date: 2021-06-22 20:22+0000\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
"PO-Revision-Date: 2021-06-24 03:47+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 "**Charts in the appropriate project**"
|
|
msgstr "**Charts in the appropriate project**"
|
|
|
|
msgid "**Combined helm-toolkit**"
|
|
msgstr "**Combined helm-toolkit**"
|
|
|
|
msgid "**Document Kubernetes requirements**"
|
|
msgstr "**Document Kubernetes requirements**"
|
|
|
|
msgid "**Document version requirements**"
|
|
msgstr "**Document version requirements**"
|
|
|
|
msgid "**Helm test for all charts**"
|
|
msgstr "**Helm test for all charts**"
|
|
|
|
msgid "**Inclusion of all core services**"
|
|
msgstr "**Inclusion of all core services**"
|
|
|
|
msgid "**LMA Operations Guide**"
|
|
msgstr "**LMA Operations Guide**"
|
|
|
|
msgid "**OpenStack-Helm release process**"
|
|
msgstr "**OpenStack-Helm release process**"
|
|
|
|
msgid "**Release notes**"
|
|
msgstr "**Release notes**"
|
|
|
|
msgid "**Resiliency across reboots**"
|
|
msgstr "**Resiliency across reboots**"
|
|
|
|
msgid "**Split Ceph chart**"
|
|
msgstr "**Split Ceph chart**"
|
|
|
|
msgid "**Standardization of manifests**"
|
|
msgstr "**Standardisation of manifests**"
|
|
|
|
msgid "**Standardization of values**"
|
|
msgstr "**Standardisation of values**"
|
|
|
|
msgid "**Upgrades**"
|
|
msgstr "**Upgrades**"
|
|
|
|
msgid "**Values-driven config files**"
|
|
msgstr "**Values-driven config files**"
|
|
|
|
msgid "1) Prepare scripts:"
|
|
msgstr "1) Prepare scripts:"
|
|
|
|
msgid ""
|
|
"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:"
|
|
"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` "
|
|
"section which provides the credentials for accessing registry images and an "
|
|
"option ``enabled:`` to determine whether images authentication is required "
|
|
"or not. The registry basic information would also be included for generating "
|
|
"the registry URL by the endpoint lookup functions. Also add a new entry "
|
|
"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In "
|
|
"order to create the secret that holds the provided credentials, add a new "
|
|
"component ``secret_registry`` in ``manifests:`` section. For example:"
|
|
msgstr ""
|
|
"1. For each chart, add a new entry ``oci_image_registry:`` under ``endpoints:"
|
|
"`` in ``values.yaml``. The entry ``oci_image_registry:`` has the ``auth:`` "
|
|
"section which provides the credentials for accessing registry images and an "
|
|
"option ``enabled:`` to determine whether images authentication is required "
|
|
"or not. The registry basic information would also be included for generating "
|
|
"the registry URL by the endpoint lookup functions. Also add a new entry "
|
|
"``oci_image_registry:`` under ``secrets:`` to indicate the secret name. In "
|
|
"order to create the secret that holds the provided credentials, add a new "
|
|
"component ``secret_registry`` in ``manifests:`` section. For example:"
|
|
|
|
msgid "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``"
|
|
msgstr "2 Replace occurrence of ``ceph.yaml`` with ``tenant-ceph.yaml``"
|
|
|
|
msgid "2) Deploy ingress chart:"
|
|
msgstr "2) Deploy ingress chart:"
|
|
|
|
msgid ""
|
|
"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to "
|
|
"``for CHART in ceph-mon ceph-osd ceph-client; do``"
|
|
msgstr ""
|
|
"3 For tenant Ceph, no need to deploy ceph-provisioners. Update script to "
|
|
"``for CHART in ceph-mon ceph-osd ceph-client; do``"
|
|
|
|
msgid "3) Deploy Ceph for RBD:"
|
|
msgstr "3) Deploy Ceph for RBD:"
|
|
|
|
msgid "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:"
|
|
msgstr "4) Deploy MariaDB, RabbitMQ, Memcached and Keystone:"
|
|
|
|
msgid "5) Deploy Ceph for Tenant:"
|
|
msgstr "5) Deploy Ceph for Tenant:"
|
|
|
|
msgid "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
|
|
msgstr "6 VM based hosts (node1, node2, node3, node4, node5, node6)"
|
|
|
|
msgid "6) Enable Openstack namespace to use Tenant Ceph:"
|
|
msgstr "6) Enable OpenStack namespace to use Tenant Ceph:"
|
|
|
|
msgid "7) Tenant Ceph: Deploy Rados Gateway:"
|
|
msgstr "7) Tenant Ceph: Deploy RADOS Gateway:"
|
|
|
|
msgid "8) Deploy Glance:"
|
|
msgstr "8) Deploy Glance:"
|
|
|
|
msgid "9) Deploy Cinder:"
|
|
msgstr "9) Deploy Cinder:"
|
|
|
|
msgid ""
|
|
"A basic Logging, Monitoring, and Alerting-oriented operations guide must be "
|
|
"in place, illustrating for operators (and developers) how to set up and use "
|
|
"an example LMA setup for OpenStack and supporting services. It will include "
|
|
"instructions on how to perform basic configuration and how to access and use "
|
|
"the user interfaces at a high level. It will also link out to more detailed "
|
|
"documentation for the LMA tooling itself."
|
|
msgstr ""
|
|
"A basic Logging, Monitoring, and Alerting-oriented operations guide must be "
|
|
"in place, illustrating for operators (and developers) how to set up and use "
|
|
"an example LMA setup for OpenStack and supporting services. It will include "
|
|
"instructions on how to perform basic configuration and how to access and use "
|
|
"the user interfaces at a high level. It will also link out to more detailed "
|
|
"documentation for the LMA tooling itself."
|
|
|
|
msgid ""
|
|
"A few areas have been identified on changes required. Each of them will be a "
|
|
"work item."
|
|
msgstr ""
|
|
"A few areas have been identified on changes required. Each of them will be a "
|
|
"work item."
|
|
|
|
msgid ""
|
|
"A foundational requirement of 1.0 readiness is the presence of robust gating "
|
|
"that will ensure functionality, backward compatibility, and upgradeability. "
|
|
"This will allow development to continue and for support for new versions of "
|
|
"OpenStack to be added post-1.0. The following gating requirements must be "
|
|
"met:"
|
|
msgstr ""
|
|
"A foundational requirement of 1.0 readiness is the presence of robust gating "
|
|
"that will ensure functionality, backward compatibility, and upgradeability. "
|
|
"This will allow development to continue and for support for new versions of "
|
|
"OpenStack to be added post-1.0. The following gating requirements must be "
|
|
"met:"
|
|
|
|
msgid ""
|
|
"A gate will be added to OpenStack-Helm that runs through the developer "
|
|
"environment deployment process."
|
|
msgstr ""
|
|
"A gate will be added to OpenStack-Helm that runs through the developer "
|
|
"environment deployment process."
|
|
|
|
msgid ""
|
|
"A number of in-progress and planned development efforts must be completed "
|
|
"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter."
|
|
msgstr ""
|
|
"A number of in-progress and planned development efforts must be completed "
|
|
"prior to 1.0, to ensure a stable OpenStack-Helm interface thereafter."
|
|
|
|
msgid ""
|
|
"A set of scripts will be provided to exercise the deployed environment that "
|
|
"checks the basic functionality of the deployed cloud, driven where possible "
|
|
"via OpenStack heat:"
|
|
msgstr ""
|
|
"A set of scripts will be provided to exercise the deployed environment that "
|
|
"checks the basic functionality of the deployed cloud, driven where possible "
|
|
"via OpenStack heat:"
|
|
|
|
msgid ""
|
|
"A specification should precede any broad-reaching technical changes or "
|
|
"proposals to OpenStack-Helm. Examples of changes requiring a specification "
|
|
"include: a standard format to the values.yaml files, multiple backend "
|
|
"support for neutron, and the approach for logging and monitoring in "
|
|
"OpenStack-Helm. Some additional features will not need an accompanying "
|
|
"specification, but may be tied back to an existing specification. An "
|
|
"example of this would be introducing a service in OpenStack-Helm that could "
|
|
"be included under the scope of a specification already drafted and approved."
|
|
msgstr ""
|
|
"A specification should precede any broad-reaching technical changes or "
|
|
"proposals to OpenStack-Helm. Examples of changes requiring a specification "
|
|
"include: a standard format to the values.yaml files, multiple backend "
|
|
"support for neutron, and the approach for logging and monitoring in "
|
|
"OpenStack-Helm. Some additional features will not need an accompanying "
|
|
"specification, but may be tied back to an existing specification. An "
|
|
"example of this would be introducing a service in OpenStack-Helm that could "
|
|
"be included under the scope of a specification already drafted and approved."
|
|
|
|
msgid "API Deployments"
|
|
msgstr "API Deployments"
|
|
|
|
msgid "Ability to apply custom metadata and uniform format to logs"
|
|
msgstr "Ability to apply custom metadata and uniform format to logs"
|
|
|
|
msgid "Ability to perform custom queries against metrics collected"
|
|
msgstr "Ability to perform custom queries against metrics collected"
|
|
|
|
msgid "Ability to perform custom queries against stored logs"
|
|
msgstr "Ability to perform custom queries against stored logs"
|
|
|
|
msgid ""
|
|
"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which "
|
|
"shows that swift is pointing to tenant-ceph."
|
|
msgstr ""
|
|
"Above output shows ``http://ceph-rgw.openstack.svc.cluster.local`` which "
|
|
"shows that swift is pointing to tenant-ceph."
|
|
|
|
msgid ""
|
|
"Above output shows that tenant ceph now has 19 pools including one for "
|
|
"Cinder."
|
|
msgstr ""
|
|
"Above output shows that tenant Ceph now has 19 pools including one for "
|
|
"Cinder."
|
|
|
|
msgid "Add Linux Bridge as first alternative for OVS - separate spec needed."
|
|
msgstr "Add Linux Bridge as first alternative for OVS - separate spec needed."
|
|
|
|
msgid "Add LinuxBridge daemonset"
|
|
msgstr "Add LinuxBridge daemonset"
|
|
|
|
msgid ""
|
|
"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to "
|
|
"create a manifest for secret generation. For example:"
|
|
msgstr ""
|
|
"Add a helm-toolkit function ``helm-toolkit.manifests.secret_registry`` to "
|
|
"create a manifest for secret generation. For example:"
|
|
|
|
msgid ""
|
|
"Add a template highlighting the updated values ordering for use in chart "
|
|
"development"
|
|
msgstr ""
|
|
"Add a template highlighting the updated values ordering for use in chart "
|
|
"development"
|
|
|
|
msgid "Add documentation on how to use LinuxBridge"
|
|
msgstr "Add documentation on how to use LinuxBridge"
|
|
|
|
msgid "Add gate for developer environment"
|
|
msgstr "Add gate for developer environment"
|
|
|
|
msgid "Add gate job testing VM network connectivity"
|
|
msgstr "Add gate job testing VM network connectivity"
|
|
|
|
msgid ""
|
|
"Add one SDN to see if proposed change is working OK - separate spec needed."
|
|
msgstr ""
|
|
"Add one SDN to see if proposed change is working OK - separate spec needed."
|
|
|
|
msgid "Add or remove nodes depending on utilization"
|
|
msgstr "Add or remove nodes depending on utilisation"
|
|
|
|
msgid "Additional assignees TBD"
|
|
msgstr "Additional assignees TBD"
|
|
|
|
msgid ""
|
|
"Aggregator also send aggregated logs to Kafka for external tools to consume"
|
|
msgstr ""
|
|
"Aggregator also send aggregated logs to Kafka for external tools to consume"
|
|
|
|
msgid "Alerting capabilities to notify operators when thresholds exceeded"
|
|
msgstr "Alerting capabilities to notify operators when thresholds exceeded"
|
|
|
|
msgid "Alertmanager chart"
|
|
msgstr "Alertmanager chart"
|
|
|
|
msgid ""
|
|
"All charts must include sensible configuration values to make the monitoring "
|
|
"platform usable by default. These include: static Prometheus "
|
|
"configurations for the included exporters, static dashboards for Grafana "
|
|
"mounted via configMaps and configurations for Alertmanager out of the box."
|
|
msgstr ""
|
|
"All charts must include sensible configuration values to make the monitoring "
|
|
"platform usable by default. These include: static Prometheus "
|
|
"configurations for the included exporters, static dashboards for Grafana "
|
|
"mounted via configMaps and configurations for Alertmanager out of the box."
|
|
|
|
msgid ""
|
|
"All charts require valid and sensible default values to provide operational "
|
|
"value out of the box."
|
|
msgstr ""
|
|
"All charts require valid and sensible default values to provide operational "
|
|
"value out of the box."
|
|
|
|
msgid ""
|
|
"All charts should follow design approaches applied to all other OpenStack-"
|
|
"Helm charts, including the use of helm-toolkit."
|
|
msgstr ""
|
|
"All charts should follow design approaches applied to all other OpenStack-"
|
|
"Helm charts, including the use of helm-toolkit."
|
|
|
|
msgid "All charts should migrate to their appropriate home project as follows:"
|
|
msgstr ""
|
|
"All charts should migrate to their appropriate home project as follows:"
|
|
|
|
msgid ""
|
|
"All keys under top-level keys are listed in alphabetical order, with the "
|
|
"exception of the conf key. As some configuration files require a strict "
|
|
"ordering of their content, excluding this key from any alphabetical "
|
|
"organization is required."
|
|
msgstr ""
|
|
"All keys under top-level keys are listed in alphabetical order, with the "
|
|
"exception of the conf key. As some configuration files require a strict "
|
|
"ordering of their content, excluding this key from any alphabetical "
|
|
"organisation is required."
|
|
|
|
msgid "All services in OpenStack-Helm log to stdout and stderr by default"
|
|
msgstr "All services in OpenStack-Helm log to stdout and stderr by default"
|
|
|
|
msgid ""
|
|
"All services running within the platform should be subject to the security "
|
|
"practices applied to the other OpenStack-Helm charts."
|
|
msgstr ""
|
|
"All services running within the platform should be subject to the security "
|
|
"practices applied to the other OpenStack-Helm charts."
|
|
|
|
msgid ""
|
|
"All services should survive node reboots, and their functionality validated "
|
|
"following a reboot by a gate."
|
|
msgstr ""
|
|
"All services should survive node reboots, and their functionality validated "
|
|
"following a reboot by a gate."
|
|
|
|
msgid ""
|
|
"All three charts must include sensible configuration values to make the "
|
|
"logging platform usable by default. These include: proper input "
|
|
"configurations for Fluentd, proper metadata and formats applied to the logs "
|
|
"via Fluentd, sensible indexes created for Elasticsearch, and proper "
|
|
"configuration values for Kibana to query the Elasticsearch indexes "
|
|
"previously created."
|
|
msgstr ""
|
|
"All three charts must include sensible configuration values to make the "
|
|
"logging platform usable by default. These include: proper input "
|
|
"configurations for Fluentd, proper metadata and formats applied to the logs "
|
|
"via Fluentd, sensible indexes created for Elasticsearch, and proper "
|
|
"configuration values for Kibana to query the Elasticsearch indexes "
|
|
"previously created."
|
|
|
|
msgid "Allow the usage of multiple base images in OSH."
|
|
msgstr "Allow the usage of multiple base images in OSH."
|
|
|
|
msgid ""
|
|
"Allows different profiles of apache, should some charts require different "
|
|
"args for example for the same kind of images, by using yaml dict merges "
|
|
"features."
|
|
msgstr ""
|
|
"Allows different profiles of Apache, should some charts require different "
|
|
"args for example for the same kind of images, by using yaml dict merges "
|
|
"features."
|
|
|
|
msgid ""
|
|
"Alter webserver configuration per distro. Different distros have different "
|
|
"expectations in terms of path (including a different series of files "
|
|
"required), and it would make the operators' life easier by using their "
|
|
"expected distro paths."
|
|
msgstr ""
|
|
"Alter webserver configuration per distro. Different distros have different "
|
|
"expectations in terms of path (including a different series of files "
|
|
"required), and it would make the operators' life easier by using their "
|
|
"expected distro paths."
|
|
|
|
msgid "Alternatives"
|
|
msgstr "Alternatives"
|
|
|
|
msgid ""
|
|
"Alternatives to decomposable Neutron chart would be to copy whole Neutron "
|
|
"chart and create spin-offs with new SDN enabled. This approach has drawbacks "
|
|
"of maintaining the whole neutron chart in many places, and copies of "
|
|
"standard services may be out of sync with OSH improvements. This implies "
|
|
"constant maintenance effort to up to date."
|
|
msgstr ""
|
|
"Alternatives to decomposable Neutron chart would be to copy whole Neutron "
|
|
"chart and create spin-offs with new SDN enabled. This approach has drawbacks "
|
|
"of maintaining the whole neutron chart in many places, and copies of "
|
|
"standard services may be out of sync with OSH improvements. This implies "
|
|
"constant maintenance effort to up to date."
|
|
|
|
msgid "Angie Wang (angiewang)"
|
|
msgstr "Angie Wang (angiewang)"
|
|
|
|
msgid ""
|
|
"Another place where Neutron L2 agent should be pointed is dependencies list "
|
|
"in other OpenStack projects. Currently, :code:`nova-compute` has dependency "
|
|
"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:"
|
|
msgstr ""
|
|
"Another place where Neutron L2 agent should be pointed is dependencies list "
|
|
"in other OpenStack projects. Currently, :code:`nova-compute` has dependency "
|
|
"for :code:`ovs-agent` in :code:`nova/values.yaml`, it should be changed to:"
|
|
|
|
msgid "Any other changes to the external interface of OpenStack-Helm"
|
|
msgstr "Any other changes to the external interface of OpenStack-Helm"
|
|
|
|
msgid ""
|
|
"As mentioned before, configuration of L3/DHCP/metadata agent should be "
|
|
"adjusted to use LinuxBridge, sample configuration override:"
|
|
msgstr ""
|
|
"As mentioned before, configuration of L3/DHCP/metadata agent should be "
|
|
"adjusted to use LinuxBridge, sample configuration override:"
|
|
|
|
msgid "Assign Floating IP to VM"
|
|
msgstr "Assign Floating IP to VM"
|
|
|
|
msgid "Assignee(s)"
|
|
msgstr "Assignee(s)"
|
|
|
|
msgid ""
|
|
"At this point, curated scripts will be used to deploy OpenStack-Helm "
|
|
"services on demand as desired, with documentation provided to allow a new "
|
|
"developer to quickly set up either a single or multimode deployment of a "
|
|
"reference `OpenStack Compute Kit <https://governance.openstack.org/tc/"
|
|
"reference/tags/starter-kit_compute.html>`_ environment with the addition of:"
|
|
msgstr ""
|
|
"At this point, curated scripts will be used to deploy OpenStack-Helm "
|
|
"services on demand as desired, with documentation provided to allow a new "
|
|
"developer to quickly set up either a single or multimode deployment of a "
|
|
"reference `OpenStack Compute Kit <https://governance.openstack.org/tc/"
|
|
"reference/tags/starter-kit_compute.html>`_ environment with the addition of:"
|
|
|
|
msgid ""
|
|
"Authentication should be enabled for normal users to access Kube API server "
|
|
"via either kubectl command or kube REST API call."
|
|
msgstr ""
|
|
"Authentication should be enabled for normal users to access Kube API server "
|
|
"via either kubectl command or kube REST API call."
|
|
|
|
msgid "Backed by highly available storage"
|
|
msgstr "Backed by highly available storage"
|
|
|
|
msgid ""
|
|
"Before drafting a specification, a blueprint should be filed in Storyboard_ "
|
|
"along with any dependencies the blueprint requires. Once the blueprint has "
|
|
"been registered, submit the specification as a patch set to the specs/ "
|
|
"directory using the supplied template."
|
|
msgstr ""
|
|
"Before drafting a specification, a blueprint should be filed in Storyboard_ "
|
|
"along with any dependencies the blueprint requires. Once the blueprint has "
|
|
"been registered, submit the specification as a patch set to the specs/ "
|
|
"directory using the supplied template."
|
|
|
|
msgid "Before using Openstack-Helm to deploy openstack services,"
|
|
msgstr "Before using Openstack-Helm to deploy OpenStack services,"
|
|
|
|
msgid "Bin ConfigMaps"
|
|
msgstr "Bin ConfigMaps"
|
|
|
|
msgid ""
|
|
"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
|
|
"sidecar"
|
|
msgstr ""
|
|
"Blueprint: https://blueprints.launchpad.net/openstack-helm/+spec/nginx-"
|
|
"sidecar"
|
|
|
|
msgid "Blueprint: neutron-multiple-sdns_"
|
|
msgstr "Blueprint: neutron-multiple-sdns_"
|
|
|
|
msgid "Blueprint: support-linux-bridge-on-neutron_"
|
|
msgstr "Blueprint: support-linux-bridge-on-neutron_"
|
|
|
|
msgid "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
|
|
msgstr "Blueprint: support-oci-image-registry-with-authentication-turned-on_"
|
|
|
|
msgid "Blueprints: 1. osh-logging-framework_"
|
|
msgstr "Blueprints: 1. osh-logging-framework_"
|
|
|
|
msgid "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
|
|
msgstr "Blueprints: 1. osh-monitoring_ 2. osh-logging-framework_"
|
|
|
|
msgid ""
|
|
"But above alternatives have limitations and security impact. i.e...require "
|
|
"root access to configure on all nodes, all pods can read any configured "
|
|
"private registries, all pods can use any images cached on a node [1]_"
|
|
msgstr ""
|
|
"But above alternatives have limitations and security impact. i.e...require "
|
|
"root access to configure on all nodes, all pods can read any configured "
|
|
"private registries, all pods can use any images cached on a node [1]_"
|
|
|
|
msgid ""
|
|
"By default, :code:`daemonset_lb_agent` will be set to false to remain "
|
|
"default behaviour of installing OVS as networking agent."
|
|
msgstr ""
|
|
"By default, :code:`daemonset_lb_agent` will be set to false to remain "
|
|
"default behaviour of installing OVS as networking agent."
|
|
|
|
msgid "Ceph Clusters:"
|
|
msgstr "Ceph Clusters:"
|
|
|
|
msgid "Ceph backed Block Storage (cinder)"
|
|
msgstr "Ceph backed Block Storage (Cinder)"
|
|
|
|
msgid "Ceph backed Object Storage"
|
|
msgstr "Ceph backed Object Storage"
|
|
|
|
msgid "Ceph for RBD:"
|
|
msgstr "Ceph for RBD:"
|
|
|
|
msgid "Ceph for Tenant:"
|
|
msgstr "Ceph for Tenant:"
|
|
|
|
msgid "Ceph metrics: total pool usage, latency, health, etc"
|
|
msgstr "Ceph metrics: total pool usage, latency, health, etc"
|
|
|
|
msgid ""
|
|
"Change ordering of keys across all charts in openstack-helm, openstack-helm-"
|
|
"infra, and openstack-helm-addons"
|
|
msgstr ""
|
|
"Change ordering of keys across all charts in openstack-helm, openstack-helm-"
|
|
"infra, and openstack-helm-addons"
|
|
|
|
msgid ""
|
|
"Charts for all core OpenStack services must be present to achieve 1.0 "
|
|
"releasability. The only core service outstanding at this time is Swift."
|
|
msgstr ""
|
|
"Charts for all core OpenStack services must be present to achieve 1.0 "
|
|
"releasability. The only core service outstanding at this time is Swift."
|
|
|
|
msgid ""
|
|
"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?"
|
|
msgstr ""
|
|
"Charts for exporters: kube-state-metrics, ceph-exporter, openstack-exporter?"
|
|
|
|
msgid "Code Completion and Refactoring"
|
|
msgstr "Code Completion and Refactoring"
|
|
|
|
msgid "Collect logs from the node by Fluentbit"
|
|
msgstr "Collect logs from the node by Fluentbit"
|
|
|
|
msgid "Common method to configure all monitoring targets"
|
|
msgstr "Common method to configure all monitoring targets"
|
|
|
|
msgid ""
|
|
"Comprehensive documentation is key to the ability for real-world operators "
|
|
"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 "
|
|
"releasability. The following outstanding items must be completed from a "
|
|
"documentation perspective:"
|
|
msgstr ""
|
|
"Comprehensive documentation is key to the ability for real-world operators "
|
|
"to benefit from OpenStack-Helm, and so it is a requirement for 1.0 "
|
|
"releasability. The following outstanding items must be completed from a "
|
|
"documentation perspective:"
|
|
|
|
msgid "Configurable log rotation mechanism"
|
|
msgstr "Configurable log rotation mechanism"
|
|
|
|
msgid "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`"
|
|
msgstr "Configuration in :code:`neutron.conf` and :code:`ml2_conf.ini`"
|
|
|
|
msgid ""
|
|
"Cover the following logging use cases https://review.openstack.org/#/"
|
|
"c/482687/"
|
|
msgstr ""
|
|
"Cover the following logging use cases https://review.openstack.org/#/"
|
|
"c/482687/"
|
|
|
|
msgid "Create SSH Key in nova"
|
|
msgstr "Create SSH Key in Nova"
|
|
|
|
msgid "Create VM on tenant network"
|
|
msgstr "Create VM on tenant network"
|
|
|
|
msgid ""
|
|
"Create conditionals in the helm charts. This is problematic, as the amount "
|
|
"of conditionals will increase and will be harder to maintain. Overrides "
|
|
"files are easy to sync between charts."
|
|
msgstr ""
|
|
"Create conditionals in the Helm charts. This is problematic, as the amount "
|
|
"of conditionals will increase and will be harder to maintain. Overrides "
|
|
"files are easy to sync between charts."
|
|
|
|
msgid "Create external network"
|
|
msgstr "Create external network"
|
|
|
|
msgid "Create tenant network"
|
|
msgstr "Create tenant network"
|
|
|
|
msgid "Create tenant router to link tenant network and external"
|
|
msgstr "Create tenant router to link tenant network and external"
|
|
|
|
msgid "CronJobs"
|
|
msgstr "CronJobs"
|
|
|
|
msgid ""
|
|
"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization "
|
|
"engine. In order to support many possible backends (SDNs), changes are "
|
|
"required in neutron chart and in deployment techniques. OpenStack-Helm can "
|
|
"support every SDN solution that has Neutron plugin, either core_plugin or "
|
|
"mechanism_driver."
|
|
msgstr ""
|
|
"Currently OpenStack-Helm supports OpenVSwitch as a network virtualization "
|
|
"engine. In order to support many possible backends (SDNs), changes are "
|
|
"required in Neutron chart and in deployment techniques. OpenStack-Helm can "
|
|
"support every SDN solution that has Neutron plugin, either core_plugin or "
|
|
"mechanism_driver."
|
|
|
|
msgid ""
|
|
"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own "
|
|
"parallel versions of the Helm-Toolkit library chart. They must be combined "
|
|
"into a single chart in OpenStack-Helm-Infra prior to 1.0."
|
|
msgstr ""
|
|
"Currently both OpenStack-Helm and OpenStack-Helm-Infra have their own "
|
|
"parallel versions of the Helm-Toolkit library chart. They must be combined "
|
|
"into a single chart in OpenStack-Helm-Infra prior to 1.0."
|
|
|
|
msgid "DHCP - auto-assign IP address and DNS info"
|
|
msgstr "DHCP - auto-assign IP address and DNS info"
|
|
|
|
msgid "Database drop Job"
|
|
msgstr "Database drop Job"
|
|
|
|
msgid "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services"
|
|
msgstr "Deploy Kubernetes via KubeADM, with charts for CNI and DNS services"
|
|
|
|
msgid "Deploying multuple Ceph clusters"
|
|
msgstr "Deploying multiple Ceph clusters"
|
|
|
|
msgid ""
|
|
"Develop scripts for bringing up OpenStack-Helm Charts and perform basic "
|
|
"interactive tests"
|
|
msgstr ""
|
|
"Develop scripts for bringing up OpenStack-Helm Charts and perform basic "
|
|
"interactive tests"
|
|
|
|
msgid "Developer Environment"
|
|
msgstr "Developer Environment"
|
|
|
|
msgid ""
|
|
"Developers require a simple way of instantiating a working environment for "
|
|
"OpenStack-Helm, that allows them to quickly begin development of the "
|
|
"project. This is more complex to achieve than many OpenStack Projects that "
|
|
"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-"
|
|
"Helm is focused on the deployment of OpenStack (and associated) Projects, "
|
|
"rather than the development of the projects themselves, and also requires "
|
|
"additional supporting infrastructure, e.g. Kubernetes and a CNI."
|
|
msgstr ""
|
|
"Developers require a simple way of instantiating a working environment for "
|
|
"OpenStack-Helm, that allows them to quickly begin development of the "
|
|
"project. This is more complex to achieve than many OpenStack Projects that "
|
|
"can simply rely upon a devstack plugin to achieve this. This is as OpenStack-"
|
|
"Helm is focused on the deployment of OpenStack (and associated) Projects, "
|
|
"rather than the development of the projects themselves, and also requires "
|
|
"additional supporting infrastructure, e.g. Kubernetes and a CNI."
|
|
|
|
msgid "Development of OpenStack-Helm"
|
|
msgstr "Development of OpenStack-Helm"
|
|
|
|
msgid "Documentation"
|
|
msgstr "Documentation"
|
|
|
|
msgid "Documentation Impact"
|
|
msgstr "Documentation Impact"
|
|
|
|
msgid ""
|
|
"Documentation of how new SDN can be enabled, how Neutron should be "
|
|
"configured. Also, for each new SDN that would be incorporated, the "
|
|
"architecture overview should be provided."
|
|
msgstr ""
|
|
"Documentation of how new SDN can be enabled, how Neutron should be "
|
|
"configured. Also, for each new SDN that would be incorporated, the "
|
|
"architecture overview should be provided."
|
|
|
|
msgid "Documentation of how to enable the registry secret generation"
|
|
msgstr "Documentation of how to enable the registry secret generation"
|
|
|
|
msgid "Documentation on how to use LinuxBridge with Neutron chart."
|
|
msgstr "Documentation on how to use LinuxBridge with Neutron chart."
|
|
|
|
msgid ""
|
|
"Documentation should be included for each of the included charts as well as "
|
|
"documentation detailing the requirements for a usable monitoring platform, "
|
|
"preferably with sane default values out of the box."
|
|
msgstr ""
|
|
"Documentation should be included for each of the included charts as well as "
|
|
"documentation detailing the requirements for a usable monitoring platform, "
|
|
"preferably with sane default values out of the box."
|
|
|
|
msgid "Duplicate scripts as shows below for later use."
|
|
msgstr "Duplicate scripts as shows below for later use."
|
|
|
|
msgid ""
|
|
"Dynamically alter webserver environment conditionally in the helm chart. For "
|
|
"example, for apache, ensure the necessary modules to run openstack are "
|
|
"available and loaded at helm chart deploy time. This will leverage the "
|
|
"binaries listed in ``values.yaml``. These series of commands are "
|
|
"distribution/image dependent, as commands to list modules to load might "
|
|
"differ. However with a few parameters, we can get a very distro independent "
|
|
"process which would allow us to load all the required apache modules."
|
|
msgstr ""
|
|
"Dynamically alter webserver environment conditionally in the helm chart. For "
|
|
"example, for Apache, ensure the necessary modules to run OpenStack are "
|
|
"available and loaded at helm chart deploy time. This will leverage the "
|
|
"binaries listed in ``values.yaml``. These series of commands are "
|
|
"distribution/image dependent, as commands to list modules to load might "
|
|
"differ. However with a few parameters, we can get a very distro independent "
|
|
"process which would allow us to load all the required Apache modules."
|
|
|
|
msgid ""
|
|
"Each chart's values.yaml file contains various settings such as docker image "
|
|
"definition, chart structure setting, form of the resources being "
|
|
"distributed, and process configuration. Currently, the structure of the "
|
|
"yaml file is complicated, and finding keys between charts proves difficult "
|
|
"due to the lack of uniform values organization across charts."
|
|
msgstr ""
|
|
"Each chart's values.yaml file contains various settings such as docker image "
|
|
"definition, chart structure setting, form of the resources being "
|
|
"distributed, and process configuration. Currently, the structure of the "
|
|
"yaml file is complicated, and finding keys between charts proves difficult "
|
|
"due to the lack of uniform values organisation across charts."
|
|
|
|
msgid ""
|
|
"Edit all helm charts to remove possible references to image specific "
|
|
"elements, replacing them with values overrides or conditionals."
|
|
msgstr ""
|
|
"Edit all helm charts to remove possible references to image specific "
|
|
"elements, replacing them with values overrides or conditionals."
|
|
|
|
msgid "Elasticsearch chart"
|
|
msgstr "Elasticsearch chart"
|
|
|
|
msgid ""
|
|
"Elasticsearch configured in a highly available manner with sane defaults"
|
|
msgstr ""
|
|
"Elasticsearch configured in a highly available manner with sane defaults"
|
|
|
|
msgid "Elasticsearch configured to prevent memory swapping to disk"
|
|
msgstr "Elasticsearch configured to prevent memory swapping to disk"
|
|
|
|
msgid "Env Setup:"
|
|
msgstr "Env Setup:"
|
|
|
|
msgid "Etc ConfigMaps"
|
|
msgstr "Etc ConfigMaps"
|
|
|
|
msgid "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached"
|
|
msgstr "Every Fluentbit send logs to Fluentd with Kubernetes metadata attached"
|
|
|
|
msgid ""
|
|
"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. "
|
|
"That would provide flexibility to the operator, to choose which Neutron "
|
|
"components are reusable with different type of SDNs. For example, neutron-"
|
|
"server which is serving the API and configuring the database can be used "
|
|
"with different types of SDN plugin, and provider of that SDN chart would not "
|
|
"need to copy all logic from Neutron base chart to manage the API and "
|
|
"database."
|
|
msgstr ""
|
|
"Every Kubernetes manifest inside Neutron chart can be enabled or disabled. "
|
|
"That would provide flexibility to the operator, to choose which Neutron "
|
|
"components are reusable with different type of SDNs. For example, neutron-"
|
|
"server which is serving the API and configuring the database can be used "
|
|
"with different types of SDN plugin, and provider of that SDN chart would not "
|
|
"need to copy all logic from Neutron base chart to manage the API and "
|
|
"database."
|
|
|
|
msgid "Example OpenStack-Helm metrics requiring monitoring include:"
|
|
msgstr "Example OpenStack-Helm metrics requiring monitoring include:"
|
|
|
|
msgid "Example uses for centralized logging include:"
|
|
msgstr "Example uses for centralised logging include:"
|
|
|
|
msgid ""
|
|
"Example uses for centralized logging with Fluentbit and Fluentd include:"
|
|
msgstr ""
|
|
"Example uses for centralised logging with Fluentbit and Fluentd include:"
|
|
|
|
msgid "Examples of how these metrics can be used include:"
|
|
msgstr "Examples of how these metrics can be used include:"
|
|
|
|
msgid ""
|
|
"Examples of how to set up the above under KubeADM and KubeSpray-based "
|
|
"clusters must be documented as well."
|
|
msgstr ""
|
|
"Examples of how to set up the above under KubeADM and KubeSpray-based "
|
|
"clusters must be documented as well."
|
|
|
|
msgid "Execute script"
|
|
msgstr "Execute script"
|
|
|
|
msgid "Execute script."
|
|
msgstr "Execute script."
|
|
|
|
msgid ""
|
|
"Exposes security/configuration features of software, allowing deployers to "
|
|
"configure software to their needs."
|
|
msgstr ""
|
|
"Exposes security/configuration features of software, allowing deployers to "
|
|
"configure software to their needs."
|
|
|
|
msgid "External charts (Calico)"
|
|
msgstr "External charts (Calico)"
|
|
|
|
msgid "Find all backtraces for a tenant id's uuid"
|
|
msgstr "Find all backtraces for a tenant id's UUID"
|
|
|
|
msgid ""
|
|
"Find all logged events that match a pattern (service, pod, behavior, etc)"
|
|
msgstr ""
|
|
"Find all logged events that match a pattern (service, pod, behaviour, etc)"
|
|
|
|
msgid ""
|
|
"First reasonable testing in gates would be to setup Linux Bridge and check "
|
|
"if VM network connectivity is working."
|
|
msgstr ""
|
|
"First reasonable testing in gates would be to setup Linux Bridge and check "
|
|
"if VM network connectivity is working."
|
|
|
|
msgid ""
|
|
"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, "
|
|
"aggregating, and delivering of logged events. Fluntbit runs as a daemonset "
|
|
"on each node and mounts the /var/lib/docker/containers directory. The Docker "
|
|
"container runtime engine directs events posted to stdout and stderr to this "
|
|
"directory on the host. Fluentbit then forward the contents of that directory "
|
|
"to Fluentd. Fluentd runs as deployment at the designated nodes and expose "
|
|
"service for Fluentbit to forward logs. Fluentd should then apply the "
|
|
"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack "
|
|
"metadata to the logs. Fluentd will then forward the results to Elasticsearch "
|
|
"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* "
|
|
"index by default. Kafka stores the logs in a 'logs' topic by default. Any "
|
|
"external tool can then consume the 'logs' topic."
|
|
msgstr ""
|
|
"Fluentbit, Fluentd meet OpenStack-Helm's logging requirements for gathering, "
|
|
"aggregating, and delivering of logged events. Fluntbit runs as a daemonset "
|
|
"on each node and mounts the /var/lib/docker/containers directory. The Docker "
|
|
"container runtime engine directs events posted to stdout and stderr to this "
|
|
"directory on the host. Fluentbit then forward the contents of that directory "
|
|
"to Fluentd. Fluentd runs as deployment at the designated nodes and expose "
|
|
"service for Fluentbit to forward logs. Fluentd should then apply the "
|
|
"Logstash format to the logs. Fluentd can also write Kubernetes and OpenStack "
|
|
"metadata to the logs. Fluentd will then forward the results to Elasticsearch "
|
|
"and to optionally Kafka. Elasticsearch indexes the logs in a logstash-* "
|
|
"index by default. Kafka stores the logs in a 'logs' topic by default. Any "
|
|
"external tool can then consume the 'logs' topic."
|
|
|
|
msgid "Fluentbit-Fluentd logging chart"
|
|
msgstr "Fluentbit-Fluentd logging chart"
|
|
|
|
msgid "Fluentd chart"
|
|
msgstr "Fluentd chart"
|
|
|
|
msgid "Fluentd properly filters and categorizes logs"
|
|
msgstr "Fluentd properly filters and categorises logs"
|
|
|
|
msgid ""
|
|
"Fluentd send aggregated logs to Elasticsearch for the internal use cases"
|
|
msgstr ""
|
|
"Fluentd send aggregated logs to Elasticsearch for the internal use cases"
|
|
|
|
msgid "Fluentd then attaches Kubernetes and/or OpenStack metadata"
|
|
msgstr "Fluentd then attaches Kubernetes and/or OpenStack metadata"
|
|
|
|
msgid ""
|
|
"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging "
|
|
"requirements for capture, storage and visualization of logged events. "
|
|
"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/"
|
|
"containers directory. The Docker container runtime engine directs events "
|
|
"posted to stdout and stderr to this directory on the host. Fluentd should "
|
|
"then declare the contents of that directory as an input stream, and use the "
|
|
"fluent-plugin-elasticsearch plugin to apply the Logstash format to the "
|
|
"logs. Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin "
|
|
"to write Kubernetes metadata to the log record. Fluentd will then forward "
|
|
"the results to Elasticsearch, which indexes the logs in a logstash-* index "
|
|
"by default. The resulting logs can then be queried directly through "
|
|
"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard "
|
|
"that can create custom views on logged events, and Kibana integrates well "
|
|
"with Elasticsearch by default."
|
|
msgstr ""
|
|
"Fluentd, Elasticsearch, and Kibana meet OpenStack-Helm's logging "
|
|
"requirements for capture, storage and visualization of logged events. "
|
|
"Fluentd runs as a daemonset on each node and mounts the /var/lib/docker/"
|
|
"containers directory. The Docker container runtime engine directs events "
|
|
"posted to stdout and stderr to this directory on the host. Fluentd should "
|
|
"then declare the contents of that directory as an input stream, and use the "
|
|
"fluent-plugin-elasticsearch plugin to apply the Logstash format to the "
|
|
"logs. Fluentd will also use the fluentd-plugin-kubernetes-metadata plugin "
|
|
"to write Kubernetes metadata to the log record. Fluentd will then forward "
|
|
"the results to Elasticsearch, which indexes the logs in a logstash-* index "
|
|
"by default. The resulting logs can then be queried directly through "
|
|
"Elasticsearch, or they can be viewed via Kibana. Kibana offers a dashboard "
|
|
"that can create custom views on logged events, and Kibana integrates well "
|
|
"with Elasticsearch by default."
|
|
|
|
msgid ""
|
|
"For Tenant Ceph, we will not be provisioning storage classes therefor, "
|
|
"update script to not install ceph-provisioners chart as following."
|
|
msgstr ""
|
|
"For Tenant Ceph, we will not be provisioning storage classes therefore, "
|
|
"update script to not install ceph-provisioners chart as following."
|
|
|
|
msgid ""
|
|
"For the ``Category B`` helm charts, an informal testing has been done in the "
|
|
"past to ensure image independence. However, there is nothing exercising this "
|
|
"independence in gates. Due to that, code of the helm charts might or might "
|
|
"not require adapting."
|
|
msgstr ""
|
|
"For the ``Category B`` helm charts, an informal testing has been done in the "
|
|
"past to ensure image independence. However, there is nothing exercising this "
|
|
"independence in gates. Due to that, code of the helm charts might or might "
|
|
"not require adapting."
|
|
|
|
msgid ""
|
|
"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly "
|
|
"built. This means we do not require any override per image. Instead we "
|
|
"require a generic kind of override, per application, usable by all charts."
|
|
msgstr ""
|
|
"For this spec, we assume ``imagename1`` and ``imagename2`` are similarly "
|
|
"built. This means we do not require any override per image. Instead we "
|
|
"require a generic kind of override, per application, usable by all charts."
|
|
|
|
msgid "Gate job testing VM network connectivity."
|
|
msgstr "Gate job testing VM network connectivity."
|
|
|
|
msgid "Gating"
|
|
msgstr "Gating"
|
|
|
|
msgid ""
|
|
"Gating must prove that upgrades from each supported OpenStack version to the "
|
|
"next operate flawlessly, using the default image set (LOCI). Specifically, "
|
|
"each OpenStack chart should be upgraded from one release to the next, and "
|
|
"each infrastructure service from one minor version to the next. Both the "
|
|
"container image and configuration must be modified as part of this upgrade. "
|
|
"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release."
|
|
msgstr ""
|
|
"Gating must prove that upgrades from each supported OpenStack version to the "
|
|
"next operate flawlessly, using the default image set (LOCI). Specifically, "
|
|
"each OpenStack chart should be upgraded from one release to the next, and "
|
|
"each infrastructure service from one minor version to the next. Both the "
|
|
"container image and configuration must be modified as part of this upgrade. "
|
|
"At minimum, Newton to Ocata upgrade must be validated for the 1.0 release."
|
|
|
|
msgid "Grafana chart"
|
|
msgstr "Grafana chart"
|
|
|
|
msgid ""
|
|
"Having services configured, also the services pod dependencies should be "
|
|
"updated to reflect the new kind on L2 agent:"
|
|
msgstr ""
|
|
"Having services configured, also the services pod dependencies should be "
|
|
"updated to reflect the new kind on L2 agent:"
|
|
|
|
msgid "Helm"
|
|
msgstr "Helm"
|
|
|
|
msgid "Helm chart for Alertmanager"
|
|
msgstr "Helm chart for Alertmanager"
|
|
|
|
msgid "Helm chart for Elasticsearch"
|
|
msgstr "Helm chart for Elasticsearch"
|
|
|
|
msgid "Helm chart for Fluentbit-Fluentd Combination"
|
|
msgstr "Helm chart for Fluentbit-Fluentd Combination"
|
|
|
|
msgid "Helm chart for Fluentd"
|
|
msgstr "Helm chart for Fluentd"
|
|
|
|
msgid "Helm chart for Grafana"
|
|
msgstr "Helm chart for Grafana"
|
|
|
|
msgid "Helm chart for Kibana"
|
|
msgstr "Helm chart for Kibana"
|
|
|
|
msgid "Helm chart for Prometheus"
|
|
msgstr "Helm chart for Prometheus"
|
|
|
|
msgid "Helm charts for any appropriate Prometheus exporters"
|
|
msgstr "Helm charts for any appropriate Prometheus exporters"
|
|
|
|
msgid ""
|
|
"Helm charts for which we are building images in osh-images. (Called further "
|
|
"``Category B`` helm charts)"
|
|
msgstr ""
|
|
"Helm charts for which we are building images in osh-images. (Called further "
|
|
"``Category B`` helm charts)"
|
|
|
|
msgid ""
|
|
"Helm charts for which we use official upstream images. (Called further "
|
|
"``Category A`` helm charts)"
|
|
msgstr ""
|
|
"Helm charts for which we use official upstream images. (Called further "
|
|
"``Category A`` helm charts)"
|
|
|
|
msgid "Helm must be installed"
|
|
msgstr "Helm must be installed"
|
|
|
|
msgid ""
|
|
"Helm test is the building block for all gating. Each chart must integrate a "
|
|
"helm-test script which validates proper functionality. This is already a "
|
|
"merge criterion for new charts, but a handful of older charts still need for "
|
|
"helm test functionality to be added. No additional charts will be merged "
|
|
"prior to 1.0 unless they meet this requirement (and others in this document)."
|
|
msgstr ""
|
|
"Helm test is the building block for all gating. Each chart must integrate a "
|
|
"helm-test script which validates proper functionality. This is already a "
|
|
"merge criterion for new charts, but a handful of older charts still need for "
|
|
"helm test functionality to be added. No additional charts will be merged "
|
|
"prior to 1.0 unless they meet this requirement (and others in this document)."
|
|
|
|
msgid "Here is a list of the current specs:"
|
|
msgstr "Here is a list of the current specs:"
|
|
|
|
msgid "Host utilization: memory usage, CPU usage, disk I/O, network I/O, etc"
|
|
msgstr "Host utilisation: memory usage, CPU usage, disk I/O, network I/O, etc"
|
|
|
|
msgid "Hosts must use KubeDNS / CoreDNS for resolution"
|
|
msgstr "Hosts must use KubeDNS / CoreDNS for resolution"
|
|
|
|
msgid ""
|
|
"I propose to extend the conf schema with generic software information. For "
|
|
"example, for apache2:"
|
|
msgstr ""
|
|
"I propose to extend the conf schema with generic software information. For "
|
|
"example, for apache2:"
|
|
|
|
msgid "Identify etcd performance that could lead to cluster instability"
|
|
msgstr "Identify etcd performance that could lead to cluster instability"
|
|
|
|
msgid ""
|
|
"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, "
|
|
"etc"
|
|
msgstr ""
|
|
"Identify issues with Kubernetes components, such as: etcd, CNI, scheduler, "
|
|
"etc"
|
|
|
|
msgid ""
|
|
"Identify issues with infrastructure components, such as RabbitMQ, mariadb, "
|
|
"etc"
|
|
msgstr ""
|
|
"Identify issues with infrastructure components, such as RabbitMQ, Mariadb, "
|
|
"etc"
|
|
|
|
msgid "Identify opportunities for improving Prometheus's operation over time"
|
|
msgstr "Identify opportunities for improving Prometheus's operation over time"
|
|
|
|
msgid ""
|
|
"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, "
|
|
"then any containers created with the current service account will have the "
|
|
"``imagePullSecrets`` automatically added to their spec and the secret will "
|
|
"be passed to kubelet to be used for pulling images."
|
|
msgstr ""
|
|
"If .Values.endpoints.oci_image_registry.auth.enabled will be set to true, "
|
|
"then any containers created with the current service account will have the "
|
|
"``imagePullSecrets`` automatically added to their spec and the secret will "
|
|
"be passed to kubelet to be used for pulling images."
|
|
|
|
msgid ""
|
|
"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
|
|
"neutron ovs agent would not be launched. In that matter, other type of L2 or "
|
|
"L3 agent on compute node can be run."
|
|
msgstr ""
|
|
"If :code:`.Values.manifests.daemonset_ovs_agent` will be set to false, "
|
|
"neutron ovs agent would not be launched. In that matter, other type of L2 or "
|
|
"L3 agent on compute node can be run."
|
|
|
|
msgid "Implement decomposable Neutron chart"
|
|
msgstr "Implement decomposable Neutron chart"
|
|
|
|
msgid "Implementation"
|
|
msgstr "Implementation"
|
|
|
|
msgid ""
|
|
"In a secured deployment, TLS certificates are used to protect the transports "
|
|
"amongst the various components. In some cases, this requires additional "
|
|
"mechanism to handle TLS offloading and to terminate the connection "
|
|
"gracefully:"
|
|
msgstr ""
|
|
"In a secured deployment, TLS certificates are used to protect the transports "
|
|
"amongst the various components. In some cases, this requires additional "
|
|
"mechanism to handle TLS offloading and to terminate the connection "
|
|
"gracefully:"
|
|
|
|
msgid "In above example OVS and Neutron OVS agent are disabled."
|
|
msgstr "In above example OVS and Neutron OVS agent are disabled."
|
|
|
|
msgid ""
|
|
"In all cases, we will need to provide different ``profiles`` (in other "
|
|
"words, overrides), to test different image providers use cases in CI."
|
|
msgstr ""
|
|
"In all cases, we will need to provide different ``profiles`` (in other "
|
|
"words, overrides), to test different image providers use cases in CI."
|
|
|
|
msgid ""
|
|
"In order to maximize flexibility for operators, and to help facilitate "
|
|
"upgrades to newer versions of containerized software without editing the "
|
|
"chart itself, all configuration files will be specified dynamically based on "
|
|
"`values.yaml` and overrides. In most cases the config files will be "
|
|
"generated based on the YAML values tree itself, and in some cases the config "
|
|
"file content will be specified in `values.yaml` as a string literal."
|
|
msgstr ""
|
|
"In order to maximise flexibility for operators, and to help facilitate "
|
|
"upgrades to newer versions of containerised software without editing the "
|
|
"chart itself, all configuration files will be specified dynamically based on "
|
|
"`values.yaml` and overrides. In most cases the config files will be "
|
|
"generated based on the YAML values tree itself, and in some cases the config "
|
|
"file content will be specified in `values.yaml` as a string literal."
|
|
|
|
msgid "In particular, these charts must move to OpenStack-Helm-Infra:"
|
|
msgstr "In particular, these charts must move to OpenStack-Helm-Infra:"
|
|
|
|
msgid ""
|
|
"In the current openstack-helm, all charts provide an ``images:`` section in "
|
|
"their ``values.yaml`` that have the container images references. By default, "
|
|
"the container images are all downloaded from a registry hosted by Docker or "
|
|
"Quay. However, the image references can be overridden by operators to "
|
|
"download images from any OCI image registry. In the case that the OCI image "
|
|
"registry has authentication turned on, kubelet would fail to download the "
|
|
"images because the current Openstack-Helm does not provide a way to pass the "
|
|
"OCI image registry credentials to kubernetes when pulling images."
|
|
msgstr ""
|
|
"In the current openstack-helm, all charts provide an ``images:`` section in "
|
|
"their ``values.yaml`` that have the container images references. By default, "
|
|
"the container images are all downloaded from a registry hosted by Docker or "
|
|
"Quay. However, the image references can be overridden by operators to "
|
|
"download images from any OCI image registry. In the case that the OCI image "
|
|
"registry has authentication turned on, kubelet would fail to download the "
|
|
"images because the current Openstack-Helm does not provide a way to pass the "
|
|
"OCI image registry credentials to Kubernetes when pulling images."
|
|
|
|
msgid "Include the URL of your Storyboard RFE:"
|
|
msgstr "Include the URL of your Storyboard RFE:"
|
|
|
|
msgid ""
|
|
"Installing OVS requires Kubernetes worker node labeling with tag :code:"
|
|
"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will "
|
|
"be introduced: :code:`linuxbridge=enabled`."
|
|
msgstr ""
|
|
"Installing OVS requires Kubernetes worker node labelling with tag :code:"
|
|
"`openvswitch=enabled`. To mark nodes where LB should be used, new tag will "
|
|
"be introduced: :code:`linuxbridge=enabled`."
|
|
|
|
msgid "Instead of using nginx, haproxy can be used instead."
|
|
msgstr "Instead of using Nginx, HAProxy can be used instead."
|
|
|
|
msgid ""
|
|
"Introducing a new SDN solution should consider how the above services are "
|
|
"provided. It may be required to disable the built-in Neutron functionality."
|
|
msgstr ""
|
|
"Introducing a new SDN solution should consider how the above services are "
|
|
"provided. It may be required to disable the built-in Neutron functionality."
|
|
|
|
msgid ""
|
|
"It is important to notice that the helm charts can be split in two "
|
|
"categories for now:"
|
|
msgstr ""
|
|
"It is important to notice that the helm charts can be split in two "
|
|
"categories for now:"
|
|
|
|
msgid "Kibana chart"
|
|
msgstr "Kibana chart"
|
|
|
|
msgid "Kubernetes"
|
|
msgstr "Kubernetes"
|
|
|
|
msgid "Kubernetes metrics: pod status, replica availability, job status, etc"
|
|
msgstr "Kubernetes metrics: pod status, replica availability, job status, etc"
|
|
|
|
msgid ""
|
|
"Kubernetes must enable mount propagation (until it is enabled by default)"
|
|
msgstr ""
|
|
"Kubernetes must enable mount propagation (until it is enabled by default)"
|
|
|
|
msgid "L3 routing - creation of routers"
|
|
msgstr "L3 routing - creation of routers"
|
|
|
|
msgid "Labels assigned to nodes: node1, node2, node3:"
|
|
msgstr "Labels assigned to nodes: node1, node2, node3:"
|
|
|
|
msgid "Labels assigned to nodes: node4, node5, node6:"
|
|
msgstr "Labels assigned to nodes: node4, node5, node6:"
|
|
|
|
msgid ""
|
|
"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph."
|
|
msgstr ""
|
|
"Labels for mon, osd, rgw, mgr and job have been updated for tenant Ceph."
|
|
|
|
msgid ""
|
|
"Let's consider how new SDN can take advantage of disaggregated Neutron "
|
|
"services architecture. First assumption is that neutron-server functionality "
|
|
"would be common for all SDNs, as it provides networking API, database "
|
|
"management and Keystone interaction. Required modifications are:"
|
|
msgstr ""
|
|
"Let's consider how new SDN can take advantage of disaggregated Neutron "
|
|
"services architecture. First assumption is that neutron-server functionality "
|
|
"would be common for all SDNs, as it provides networking API, database "
|
|
"management and Keystone interaction. Required modifications are:"
|
|
|
|
msgid ""
|
|
"LinuxBridge installation with neutron chart takes advantaged of decomposable "
|
|
"neutron chart in OSH. LinuxBridge agent will be added as daemonset, "
|
|
"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` "
|
|
"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:"
|
|
msgstr ""
|
|
"LinuxBridge installation with Neutron chart takes advantaged of decomposable "
|
|
"Neutron chart in OSH. LinuxBridge agent will be added as daemonset, "
|
|
"similarly how OVS is implemented. New value :code:`daemonset_lb_agent` "
|
|
"should be added in :code:`neutron/values.yaml` in :code:`manifests` section:"
|
|
|
|
msgid "LinuxBridge should be also enabled in :code:`manifests` section:"
|
|
msgstr "LinuxBridge should be also enabled in :code:`manifests` section:"
|
|
|
|
msgid ""
|
|
"LinuxBridge should support external bridge configuration, as well as auto "
|
|
"bridge add mechanism implemented for OVS."
|
|
msgstr ""
|
|
"LinuxBridge should support external bridge configuration, as well as auto "
|
|
"bridge add mechanism implemented for OVS."
|
|
|
|
msgid "Log aggregator deployment runs on a selected node as deployment"
|
|
msgstr "Log aggregator deployment runs on a selected node as deployment"
|
|
|
|
msgid "Log aggregator is able to send data to Elasticsearch and Kafka"
|
|
msgstr "Log aggregator is able to send data to Elasticsearch and Kafka"
|
|
|
|
msgid "Log aggregator should be scalable"
|
|
msgstr "Log aggregator should be scalable"
|
|
|
|
msgid "Log aggregator should have HA capability"
|
|
msgstr "Log aggregator should have HA capability"
|
|
|
|
msgid "Log aggregator should have a flexible output capability to choose from"
|
|
msgstr "Log aggregator should have a flexible output capability to choose from"
|
|
|
|
msgid "Log collection daemon runs on each node to forward logs to aggregator"
|
|
msgstr "Log collection daemon runs on each node to forward logs to aggregator"
|
|
|
|
msgid "Log collection daemon runs on each node to forward logs to storage"
|
|
msgstr "Log collection daemon runs on each node to forward logs to storage"
|
|
|
|
msgid "Log collection daemon should have a minimal server footprint"
|
|
msgstr "Log collection daemon should have a minimal server footprint"
|
|
|
|
msgid "Logging"
|
|
msgstr "Logging"
|
|
|
|
msgid "Logging Requirements"
|
|
msgstr "Logging Requirements"
|
|
|
|
msgid "Logging Use Cases"
|
|
msgstr "Logging Use Cases"
|
|
|
|
msgid "Logical Diagram"
|
|
msgstr "Logical Diagram"
|
|
|
|
msgid ""
|
|
"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid."
|
|
"txt`` with ``tenant-ceph-fs-uuid.txt``"
|
|
msgstr ""
|
|
"Make following changes to script: 1 Replace occurrence of ``ceph-fs-uuid."
|
|
"txt`` with ``tenant-ceph-fs-uuid.txt``"
|
|
|
|
msgid ""
|
|
"Make webserver binary path/arguments templated using ``values.yaml``. As "
|
|
"expressed above, this allows us to provide different overrides per image/"
|
|
"distribution to automatically wire things."
|
|
msgstr ""
|
|
"Make webserver binary path/arguments templated using ``values.yaml``. As "
|
|
"expressed above, this allows us to provide different overrides per image/"
|
|
"distribution to automatically wire things."
|
|
|
|
msgid "Metadata- Provide proxy for Nova metadata service"
|
|
msgstr "Metadata- Provide proxy for Nova metadata service"
|
|
|
|
msgid "Monitoring"
|
|
msgstr "Monitoring"
|
|
|
|
msgid "Monitoring Requirements"
|
|
msgstr "Monitoring Requirements"
|
|
|
|
msgid "Monitoring Use Cases"
|
|
msgstr "Monitoring Use Cases"
|
|
|
|
msgid ""
|
|
"More information about the blueprint + specification lifecycle can be found "
|
|
"here_."
|
|
msgstr ""
|
|
"More information about the blueprint + specification lifecycle can be found "
|
|
"here_."
|
|
|
|
msgid "Multi-OS Support"
|
|
msgstr "Multi-OS Support"
|
|
|
|
msgid "Neutron multiple SDNs"
|
|
msgstr "Neutron multiple SDNs"
|
|
|
|
msgid "New charts"
|
|
msgstr "New charts"
|
|
|
|
msgid ""
|
|
"Next, Neutron services like L3 routing, DHCP and metadata serving should be "
|
|
"considered. If SDN provides its own implementation, the Neutron's default "
|
|
"one should be disabled:"
|
|
msgstr ""
|
|
"Next, Neutron services like L3 routing, DHCP and metadata serving should be "
|
|
"considered. If SDN provides its own implementation, the Neutron's default "
|
|
"one should be disabled:"
|
|
|
|
msgid "Nginx Sidecar"
|
|
msgstr "Nginx Sidecar"
|
|
|
|
msgid "No benchmark was done to evaluate:"
|
|
msgstr "No benchmark was done to evaluate:"
|
|
|
|
msgid ""
|
|
"No change in testing is required, *per se*. It is expected the new software "
|
|
"configuration would be tested with the current practices."
|
|
msgstr ""
|
|
"No change in testing is required, *per se*. It is expected the new software "
|
|
"configuration would be tested with the current practices."
|
|
|
|
msgid ""
|
|
"No direct impact, as there is no change in the current software/"
|
|
"configuration location, merely a templating change."
|
|
msgstr ""
|
|
"No direct impact, as there is no change in the current software/"
|
|
"configuration location, merely a templating change."
|
|
|
|
msgid "No impact"
|
|
msgstr "No impact"
|
|
|
|
msgid "No performance impact"
|
|
msgstr "No performance impact"
|
|
|
|
msgid "No security impact."
|
|
msgstr "No security impact."
|
|
|
|
msgid "None"
|
|
msgstr "None"
|
|
|
|
msgid ""
|
|
"None more than this spec, as it should be relatively transparent for the "
|
|
"user. However, extra documentation to explain the usage of "
|
|
"``value_overrides`` would be welcomed."
|
|
msgstr ""
|
|
"None more than this spec, as it should be relatively transparent for the "
|
|
"user. However, extra documentation to explain the usage of "
|
|
"``value_overrides`` would be welcomed."
|
|
|
|
msgid ""
|
|
"Not providing a support of multiple images. This leads to ease of "
|
|
"maintainance and reduced gate impact, with the risk of having less "
|
|
"contributors. For available overrides, users would have to provide many "
|
|
"overrides themselves, while this spec proposes a common community approach."
|
|
msgstr ""
|
|
"Not providing a support of multiple images. This leads to ease of "
|
|
"maintenance and reduced gate impact, with the risk of having less "
|
|
"contributors. For available overrides, users would have to provide many "
|
|
"overrides themselves, while this spec proposes a common community approach."
|
|
|
|
msgid "Note that mon_addr and mon_host have default mon port 6789."
|
|
msgstr "Note that mon_addr and mon_host have default mon port 6789."
|
|
|
|
msgid "OSH Logging, Monitoring, and Alerting"
|
|
msgstr "OSH Logging, Monitoring, and Alerting"
|
|
|
|
msgid ""
|
|
"OVS is an alternative in Neutron reference architecture. It is already in "
|
|
"tree."
|
|
msgstr ""
|
|
"OVS is an alternative in Neutron reference architecture. It is already in "
|
|
"tree."
|
|
|
|
msgid ""
|
|
"On top of that, the newly provided `example_values/` must aim for being "
|
|
"tested **as soon as possible upon delivery**. Without tests, those examples "
|
|
"will decrepit. The changes in CI pipelines for making use of "
|
|
"`example_values` is outside the scope of this spec."
|
|
msgstr ""
|
|
"On top of that, the newly provided `example_values/` must aim for being "
|
|
"tested **as soon as possible upon delivery**. Without tests, those examples "
|
|
"will decrepit. The changes in CI pipelines for making use of "
|
|
"`example_values` is outside the scope of this spec."
|
|
|
|
msgid ""
|
|
"Only provide one way to configure software, and expect to always have the "
|
|
"same versions. This is further away from the \"image independent\" contract, "
|
|
"with extra burden: We will need to maintain a curated list of versions, deal "
|
|
"with the differences of the defaults (selinux/apparmor profiles come to mind "
|
|
"as path sensitive for example), and different expectations for operational "
|
|
"teams (\"The code is not where I expect it to be in the image\"). Embracing "
|
|
"difference could even allow deployers to have different expectations for "
|
|
"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
|
|
msgstr ""
|
|
"Only provide one way to configure software, and expect to always have the "
|
|
"same versions. This is further away from the \"image independent\" contract, "
|
|
"with extra burden: We will need to maintain a curated list of versions, deal "
|
|
"with the differences of the defaults (selinux/apparmor profiles come to mind "
|
|
"as path sensitive for example), and different expectations for operational "
|
|
"teams (\"The code is not where I expect it to be in the image\"). Embracing "
|
|
"difference could even allow deployers to have different expectations for "
|
|
"images, for example: apache+mod_wsgi vs uwsgi standalone or uwsgi + nginx."
|
|
|
|
msgid ""
|
|
"OpenStack metrics: tenants, networks, flavors, floating IPs, quotas, etc"
|
|
msgstr ""
|
|
"OpenStack metrics: tenants, networks, flavours, floating IPs, quotas, etc"
|
|
|
|
msgid "OpenStack-Helm 1.0 Requirements"
|
|
msgstr "OpenStack-Helm 1.0 Requirements"
|
|
|
|
msgid ""
|
|
"OpenStack-Helm currently lacks a centralized mechanism for providing insight "
|
|
"into the performance of the OpenStack services and infrastructure "
|
|
"components. The log formats of the different components in OpenStack-Helm "
|
|
"vary, which makes identifying causes for issues difficult across services. "
|
|
"To support operational readiness by default, OpenStack-Helm should include "
|
|
"components for logging events in a common format, monitoring metrics at all "
|
|
"levels, alerting and alarms for those metrics, and visualization tools for "
|
|
"querying the logs and metrics in a single pane view."
|
|
msgstr ""
|
|
"OpenStack-Helm currently lacks a centralised mechanism for providing insight "
|
|
"into the performance of the OpenStack services and infrastructure "
|
|
"components. The log formats of the different components in OpenStack-Helm "
|
|
"vary, which makes identifying causes for issues difficult across services. "
|
|
"To support operational readiness by default, OpenStack-Helm should include "
|
|
"components for logging events in a common format, monitoring metrics at all "
|
|
"levels, alerting and alarms for those metrics, and visualisation tools for "
|
|
"querying the logs and metrics in a single pane view."
|
|
|
|
msgid ""
|
|
"OpenStack-Helm defines a centralized logging mechanism to provide insight "
|
|
"into the state of the OpenStack services and infrastructure components as "
|
|
"well as underlying Kubernetes platform. Among the requirements for a logging "
|
|
"platform, where log data can come from and where log data need to be "
|
|
"delivered are very variable. To support various logging scenarios, OpenStack-"
|
|
"Helm should provide a flexible mechanism to meet with certain operation "
|
|
"needs. This spec proposes fast and lightweight log forwarder and full "
|
|
"featured log aggregator complementing each other providing a flexible and "
|
|
"reliable solution. Especially, Fluentbit is proposed as a log forwarder and "
|
|
"Fluentd is proposed as a main log aggregator and processor."
|
|
msgstr ""
|
|
"OpenStack-Helm defines a centralised logging mechanism to provide insight "
|
|
"into the state of the OpenStack services and infrastructure components as "
|
|
"well as underlying Kubernetes platform. Among the requirements for a logging "
|
|
"platform, where log data can come from and where log data need to be "
|
|
"delivered are very variable. To support various logging scenarios, OpenStack-"
|
|
"Helm should provide a flexible mechanism to meet with certain operation "
|
|
"needs. This spec proposes fast and lightweight log forwarder and full "
|
|
"featured log aggregator complementing each other providing a flexible and "
|
|
"reliable solution. Especially, Fluentbit is proposed as a log forwarder and "
|
|
"Fluentd is proposed as a main log aggregator and processor."
|
|
|
|
msgid ""
|
|
"OpenStack-Helm documentation will be updated to indicate the usage of the "
|
|
"nginx sidecar."
|
|
msgstr ""
|
|
"OpenStack-Helm documentation will be updated to indicate the usage of the "
|
|
"Nginx sidecar."
|
|
|
|
msgid "OpenStack-Helm for OpenStack services"
|
|
msgstr "OpenStack-Helm for OpenStack services"
|
|
|
|
msgid ""
|
|
"OpenStack-Helm has developed a number of conventions around the format and "
|
|
"ordering of charts' `values.yaml` file, in support of both reusable Helm-"
|
|
"Toolkit functions and ease of developer ramp-up. For 1.0 readiness, "
|
|
"OpenStack-Helm must cement these conventions within a spec, as well as the "
|
|
"ordering of `values.yaml` keys. These conventions must then be gated to "
|
|
"guarantee conformity. The spec in progress can be found here [1]_."
|
|
msgstr ""
|
|
"OpenStack-Helm has developed a number of conventions around the format and "
|
|
"ordering of charts' `values.yaml` file, in support of both reusable Helm-"
|
|
"Toolkit functions and ease of developer ramp-up. For 1.0 readiness, "
|
|
"OpenStack-Helm must cement these conventions within a spec, as well as the "
|
|
"ordering of `values.yaml` keys. These conventions must then be gated to "
|
|
"guarantee conformity. The spec in progress can be found here [1]_."
|
|
|
|
msgid ""
|
|
"OpenStack-Helm has undergone rapid development and maturation over its "
|
|
"lifetime, and is nearing the point of real-world readiness. This spec "
|
|
"details the functionality that must be implemented in OpenStack-Helm for it "
|
|
"to be considered ready for a 1.0 release, as well as for general use."
|
|
msgstr ""
|
|
"OpenStack-Helm has undergone rapid development and maturation over its "
|
|
"lifetime, and is nearing the point of real-world readiness. This spec "
|
|
"details the functionality that must be implemented in OpenStack-Helm for it "
|
|
"to be considered ready for a 1.0 release, as well as for general use."
|
|
|
|
msgid ""
|
|
"OpenStack-Helm multinode guide includes scripts which are used to specify "
|
|
"overrides and deploy charts."
|
|
msgstr ""
|
|
"OpenStack-Helm multinode guide includes scripts which are used to specify "
|
|
"overrides and deploy charts."
|
|
|
|
msgid ""
|
|
"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm. Any "
|
|
"particular k8s configuration or feature requirements must be documented."
|
|
msgstr ""
|
|
"OpenStack-Helm supports a \"bring your own Kubernetes\" paradigm. Any "
|
|
"particular k8s configuration or feature requirements must be documented."
|
|
|
|
msgid "OpenStack-Helm-Addons for ancillary services"
|
|
msgstr "OpenStack-Helm-Addons for ancillary services"
|
|
|
|
msgid "OpenStack-Helm-Infra for supporting services"
|
|
msgstr "OpenStack-Helm-Infra for supporting services"
|
|
|
|
msgid "Operating system"
|
|
msgstr "Operating system"
|
|
|
|
msgid ""
|
|
"Operators should be able to use Openstack-Helm to deploy containerized "
|
|
"openstack services with a docker registry has authentication turned on."
|
|
msgstr ""
|
|
"Operators should be able to use Openstack-Helm to deploy containerised "
|
|
"OpenStack services with a docker registry has authentication turned on."
|
|
|
|
msgid "Orchestration (heat)"
|
|
msgstr "Orchestration (Heat)"
|
|
|
|
msgid "Organizational auditing needs"
|
|
msgstr "Organisational auditing needs"
|
|
|
|
msgid "Other networking services provided by Neutron are:"
|
|
msgstr "Other networking services provided by Neutron are:"
|
|
|
|
msgid ""
|
|
"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are "
|
|
"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause "
|
|
"changes in mentioned services configuration."
|
|
msgstr ""
|
|
"Other services inside Neutron reference stack (L3/DHCP/metadata agents) are "
|
|
"dependent on L2 connectivity agent. Thus, replacing OVS with LB would cause "
|
|
"changes in mentioned services configuration."
|
|
|
|
msgid ""
|
|
"Our :ref:`images documentation` documentation claims to be independent of "
|
|
"the image. However, some helm charts hard code paths of binaries, "
|
|
"executables' runtime configurations, etc. Therefore, the image agnostic "
|
|
"promise is broken."
|
|
msgstr ""
|
|
"Our :ref:`images documentation` documentation claims to be independent of "
|
|
"the image. However, some Helm charts hard code paths of binaries, "
|
|
"executables' runtime configurations, etc. Therefore, the image agnostic "
|
|
"promise is broken."
|
|
|
|
msgid "Performance Impact"
|
|
msgstr "Performance Impact"
|
|
|
|
msgid "Pete Birley <pete@port.direct>"
|
|
msgstr "Pete Birley <pete@port.direct>"
|
|
|
|
msgid "Platform Requirements"
|
|
msgstr "Platform Requirements"
|
|
|
|
msgid "PoC deployments of OpenStack-Helm"
|
|
msgstr "PoC deployments of OpenStack-Helm"
|
|
|
|
msgid "Port numbers for Ceph_Mon and Ceph_Mgr are different from default."
|
|
msgstr "Port numbers for Ceph_Mon and Ceph_Mgr are different from default."
|
|
|
|
msgid "Pre-pulling images on all nodes"
|
|
msgstr "Pre-pulling images on all nodes"
|
|
|
|
msgid "Prepare Host(s) for OpenStack-Helm deployment"
|
|
msgstr "Prepare Host(s) for OpenStack-Helm deployment"
|
|
|
|
msgid "Primary assignee:"
|
|
msgstr "Primary assignee:"
|
|
|
|
msgid "Primary assignees:"
|
|
msgstr "Primary assignees:"
|
|
|
|
msgid "Proactive monitoring of stack traces across all deployed infrastructure"
|
|
msgstr ""
|
|
"Proactive monitoring of stack traces across all deployed infrastructure"
|
|
|
|
msgid "Problem Description"
|
|
msgstr "Problem Description"
|
|
|
|
msgid "Process and Tooling"
|
|
msgstr "Process and Tooling"
|
|
|
|
msgid "Project Specifications"
|
|
msgstr "Project Specifications"
|
|
|
|
msgid ""
|
|
"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements. The "
|
|
"Prometheus monitoring tool provides the ability to scrape targets for "
|
|
"metrics over HTTP, and it stores these metrics in Prometheus's time-series "
|
|
"database. The monitoring targets can be discovered via static configuration "
|
|
"in Prometheus or through service discovery. Prometheus includes a querying "
|
|
"language that provides meaningful queries against the metrics gathered and "
|
|
"supports the creation of rules to measure these metrics against for alerting "
|
|
"purposes. It also supports a wide range of Prometheus exporters for "
|
|
"existing services, including Ceph and OpenStack. Grafana supports "
|
|
"Prometheus as a data source, and provides the ability to view the metrics "
|
|
"gathered by Prometheus in a single pane dashboard. Grafana can be "
|
|
"bootstrapped with dashboards for each target scraped, or the dashboards can "
|
|
"be added via Grafana's web interface directly. To meet OpenStack-Helm's "
|
|
"alerting needs, Alertmanager can be used to interface with Prometheus and "
|
|
"send alerts based on Prometheus rule evaluations."
|
|
msgstr ""
|
|
"Prometheus and Grafana meet OpenStack-Helm's monitoring requirements. The "
|
|
"Prometheus monitoring tool provides the ability to scrape targets for "
|
|
"metrics over HTTP, and it stores these metrics in Prometheus's time-series "
|
|
"database. The monitoring targets can be discovered via static configuration "
|
|
"in Prometheus or through service discovery. Prometheus includes a querying "
|
|
"language that provides meaningful queries against the metrics gathered and "
|
|
"supports the creation of rules to measure these metrics against for alerting "
|
|
"purposes. It also supports a wide range of Prometheus exporters for "
|
|
"existing services, including Ceph and OpenStack. Grafana supports "
|
|
"Prometheus as a data source, and provides the ability to view the metrics "
|
|
"gathered by Prometheus in a single pane dashboard. Grafana can be "
|
|
"bootstrapped with dashboards for each target scraped, or the dashboards can "
|
|
"be added via Grafana's web interface directly. To meet OpenStack-Helm's "
|
|
"alerting needs, Alertmanager can be used to interface with Prometheus and "
|
|
"send alerts based on Prometheus rule evaluations."
|
|
|
|
msgid "Prometheus chart"
|
|
msgstr "Prometheus chart"
|
|
|
|
msgid "Prometheus exporters"
|
|
msgstr "Prometheus exporters"
|
|
|
|
msgid "Proper directories mounted to retrieve logs from the node"
|
|
msgstr "Proper directories mounted to retrieve logs from the node"
|
|
|
|
msgid "Proposed Change"
|
|
msgstr "Proposed Change"
|
|
|
|
msgid ""
|
|
"Proposes a common approach to software configuration, describing the distro/"
|
|
"image specific differences for applications."
|
|
msgstr ""
|
|
"Proposes a common approach to software configuration, describing the distro/"
|
|
"image specific differences for applications."
|
|
|
|
msgid ""
|
|
"Provide the credentials and add the manifest across all charts in OSH and "
|
|
"OSH-infra"
|
|
msgstr ""
|
|
"Provide the credentials and add the manifest across all charts in OSH and "
|
|
"OSH-infra"
|
|
|
|
msgid "Providing the neutron plugin code."
|
|
msgstr "Providing the Neutron plugin code."
|
|
|
|
msgid "Provision of those services should be included inside SDN chart."
|
|
msgstr "Provision of those services should be included inside SDN chart."
|
|
|
|
msgid "Put .docker/config.json in docker/kubelet root directory on all nodes"
|
|
msgstr "Put .docker/config.json in docker/kubelet root directory on all nodes"
|
|
|
|
msgid "Record OpenStack service behavior and status"
|
|
msgstr "Record OpenStack service behaviour and status"
|
|
|
|
msgid "Record compute instance behavior across nodes and services"
|
|
msgstr "Record compute instance behaviour across nodes and services"
|
|
|
|
msgid ""
|
|
"Reference the created secret by adding the ``imagePullSecrets:`` field to "
|
|
"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/"
|
|
"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the "
|
|
"field is wrapped in a conditional. For example,"
|
|
msgstr ""
|
|
"Reference the created secret by adding the ``imagePullSecrets:`` field to "
|
|
"ServiceAccount resource template [2]_ in ``helm-toolkit/snippets/"
|
|
"_kubernetes_pod_rbac_serviceaccount.tpl``. To handle it as optional, the "
|
|
"field is wrapped in a conditional. For example,"
|
|
|
|
msgid "References"
|
|
msgstr "References"
|
|
|
|
msgid ""
|
|
"Release notes for the 1.0 release must be prepared, following OpenStack best "
|
|
"practices. The criteria for future changes that should be included in "
|
|
"release notes in an ongoing fashion must be defined / documented as well."
|
|
msgstr ""
|
|
"Release notes for the 1.0 release must be prepared, following OpenStack best "
|
|
"practices. The criteria for future changes that should be included in "
|
|
"release notes in an ongoing fashion must be defined / documented as well."
|
|
|
|
msgid ""
|
|
"Releated Specs: 1. OSH logging monitoring and alerting: https://review."
|
|
"openstack.org/#/c/482687/"
|
|
msgstr ""
|
|
"Related Specs: 1. OSH logging monitoring and alerting: https://review."
|
|
"openstack.org/#/c/482687/"
|
|
|
|
msgid "Result from Steps 2, 3, 4:"
|
|
msgstr "Result from Steps 2, 3, 4:"
|
|
|
|
msgid "Results from Step 5, 6, 7:"
|
|
msgstr "Results from Step 5, 6, 7:"
|
|
|
|
msgid "SSH into VM and check it can access the internet"
|
|
msgstr "SSH into VM and check it can access the Internet"
|
|
|
|
msgid "Sane defaults for log retention and rotation policies"
|
|
msgstr "Sane defaults for log retention and rotation policies"
|
|
|
|
msgid "Script to update and execute: ``020-ingress.sh``"
|
|
msgstr "Script to update and execute: ``020-ingress.sh``"
|
|
|
|
msgid "Script to update and execute: ``030-ceph.sh``"
|
|
msgstr "Script to update and execute: ``030-ceph.sh``"
|
|
|
|
msgid "Script to update and execute: ``030-tenant-ceph.sh``"
|
|
msgstr "Script to update and execute: ``030-tenant-ceph.sh``"
|
|
|
|
msgid "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``"
|
|
msgstr "Script to update and execute: ``040-tenant-ceph-ns-activate.sh``"
|
|
|
|
msgid "Script to update and execute: ``100-glance.sh``"
|
|
msgstr "Script to update and execute: ``100-glance.sh``"
|
|
|
|
msgid "Script to update and execute: ``110-cinder.sh``"
|
|
msgstr "Script to update and execute: ``110-cinder.sh``"
|
|
|
|
msgid "Script to update: ``090-tenant-ceph-radosgateway.sh``"
|
|
msgstr "Script to update: ``090-tenant-ceph-radosgateway.sh``"
|
|
|
|
msgid "Security Impact"
|
|
msgstr "Security Impact"
|
|
|
|
msgid "See above for documentation requirements."
|
|
msgstr "See above for documentation requirements."
|
|
|
|
msgid "See above for gating requirements."
|
|
msgstr "See above for gating requirements."
|
|
|
|
msgid "See above for the list of work items."
|
|
msgstr "See above for the list of work items."
|
|
|
|
msgid "Setup access to the external network from the development machine"
|
|
msgstr "Setup access to the external network from the development machine"
|
|
|
|
msgid "Single pane visualization capabilities"
|
|
msgstr "Single pane visualisation capabilities"
|
|
|
|
msgid "Specifications Process"
|
|
msgstr "Specifications Process"
|
|
|
|
msgid "Specifications Purpose"
|
|
msgstr "Specifications Purpose"
|
|
|
|
msgid ""
|
|
"Specifications in this repository represent a consensus on the topics "
|
|
"covered within. They should be considered a mandate on the path forward "
|
|
"with regards to the content on which they are drafted."
|
|
msgstr ""
|
|
"Specifications in this repository represent a consensus on the topics "
|
|
"covered within. They should be considered a mandate on the path forward "
|
|
"with regards to the content on which they are drafted."
|
|
|
|
msgid "StatefulSets"
|
|
msgstr "StatefulSets"
|
|
|
|
msgid "Support OCI image registry with authentication turned on"
|
|
msgstr "Support OCI image registry with authentication turned on"
|
|
|
|
msgid "Support linux bridge on neutron helm chart"
|
|
msgstr "Support LinuxBridge on Neutron Helm chart"
|
|
|
|
msgid "TODO - release management spec"
|
|
msgstr "TODO - release management spec"
|
|
|
|
msgid "Test Steps:"
|
|
msgstr "Test Steps:"
|
|
|
|
msgid "Testing"
|
|
msgstr "Testing"
|
|
|
|
msgid ""
|
|
"Testing should include Helm tests for each of the included charts as well as "
|
|
"an integration test in the gate."
|
|
msgstr ""
|
|
"Testing should include Helm tests for each of the included charts as well as "
|
|
"an integration test in the gate."
|
|
|
|
msgid ""
|
|
"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as "
|
|
"network configuration for VMs. Both OVS and LB are part of Neutron's Modular "
|
|
"Layer 2 (ML2) framework, allowing to simultaneously utilize the variety of "
|
|
"layer 2 networking technologies."
|
|
msgstr ""
|
|
"The LinuxBridge (LB) is Neutron's L2 agent, using linux kernel bridges as "
|
|
"network configuration for VMs. Both OVS and LB are part of Neutron's Modular "
|
|
"Layer 2 (ML2) framework, allowing to simultaneously utilise the variety of "
|
|
"layer 2 networking technologies."
|
|
|
|
msgid ""
|
|
"The Neutron reference architecture provides mechanism_drivers OpenVSwitch "
|
|
"(OVS) and linuxbridge (LB) with ML2 core_plugin framework."
|
|
msgstr ""
|
|
"The Neutron reference architecture provides mechanism_drivers OpenVSwitch "
|
|
"(OVS) and LinuxBridge (LB) with ML2 core_plugin framework."
|
|
|
|
msgid ""
|
|
"The OpenStack-Helm Zuulv2 gates were written to allow use outside of "
|
|
"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption "
|
|
"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 "
|
|
"Playbooks. This will be driven via a ``Makefile`` that will allow developers "
|
|
"to perform the following actions:"
|
|
msgstr ""
|
|
"The OpenStack-Helm Zuulv2 gates were written to allow use outside of "
|
|
"OpenStack-Infra, to quickly set up a Kubernetes cluster, with the adoption "
|
|
"of Zuulv3 underway it is logical to extend this paradigm to the Zuulv3 "
|
|
"Playbooks. This will be driven via a ``Makefile`` that will allow developers "
|
|
"to perform the following actions:"
|
|
|
|
msgid ""
|
|
"The OpenStack-Helm release process will be somewhat orthogonal to the "
|
|
"OpenStack release process, and the differences and relationship between the "
|
|
"two must be documented in a spec. This will help folks quickly understand "
|
|
"why OpenStack-Helm is a Release-Independent project from an OpenStack "
|
|
"perspective."
|
|
msgstr ""
|
|
"The OpenStack-Helm release process will be somewhat orthogonal to the "
|
|
"OpenStack release process, and the differences and relationship between the "
|
|
"two must be documented in a spec. This will help folks quickly understand "
|
|
"why OpenStack-Helm is a Release-Independent project from an OpenStack "
|
|
"perspective."
|
|
|
|
msgid ""
|
|
"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will "
|
|
"be provided in each chart's ``example_values/`` directory. This folder will "
|
|
"be masked to helm through a helmignore file. Its content is only for user "
|
|
"consumption, not for inclusion in helm charts through the File directive. In "
|
|
"other words, this is a user interface given for convenience merely using the "
|
|
"abilities of the existing helm charts."
|
|
msgstr ""
|
|
"The ``profiles`` yaml files (for example ``centos_7``, ``opensuse_15``) will "
|
|
"be provided in each chart's ``example_values/`` directory. This folder will "
|
|
"be masked to Helm through a helmignore file. Its content is only for user "
|
|
"consumption, not for inclusion in helm charts through the File directive. In "
|
|
"other words, this is a user interface given for convenience merely using the "
|
|
"abilities of the existing helm charts."
|
|
|
|
msgid ""
|
|
"The above chart must include sensible configuration values to make the "
|
|
"logging platform usable by default. These include: proper input "
|
|
"configurations for both Fluentbit and Fluentd, proper output configurations "
|
|
"for both Fluentbit and Fluentd, proper metadata and formats applied to the "
|
|
"logs via Fluentd."
|
|
msgstr ""
|
|
"The above chart must include sensible configuration values to make the "
|
|
"logging platform usable by default. These include: proper input "
|
|
"configurations for both Fluentbit and Fluentd, proper output configurations "
|
|
"for both Fluentbit and Fluentd, proper metadata and formats applied to the "
|
|
"logs via Fluentd."
|
|
|
|
msgid ""
|
|
"The alternative is to provide no organization layout for charts across all "
|
|
"openstack-helm repositories."
|
|
msgstr ""
|
|
"The alternative is to provide no organization layout for charts across all "
|
|
"openstack-helm repositories."
|
|
|
|
msgid ""
|
|
"The alternative would be to continue supporting the current bash driven "
|
|
"containerized KubeADM and Kubelet approach, though this has the following "
|
|
"issues:"
|
|
msgstr ""
|
|
"The alternative would be to continue supporting the current bash driven "
|
|
"containerized KubeADM and Kubelet approach, though this has the following "
|
|
"issues:"
|
|
|
|
msgid ""
|
|
"The bash scripts are largely undocumented and have grown to the point where "
|
|
"they are very hard for a new developer to work on."
|
|
msgstr ""
|
|
"The bash scripts are largely undocumented and have grown to the point where "
|
|
"they are very hard for a new developer to work on."
|
|
|
|
msgid ""
|
|
"The code can be supplied as modified neutron server image, or plugin can be "
|
|
"mounted to original image. The :code:`manifests` section in :code:`neutron/"
|
|
"values.yaml` should be enabled for below components:"
|
|
msgstr ""
|
|
"The code can be supplied as modified Neutron server image, or plugin can be "
|
|
"mounted to original image. The :code:`manifests` section in :code:`neutron/"
|
|
"values.yaml` should be enabled for below components:"
|
|
|
|
msgid ""
|
|
"The containerized Kubelet cannot survive a restart, as it does not setup "
|
|
"mounts correctly."
|
|
msgstr ""
|
|
"The containerised Kubelet cannot survive a restart, as it does not setup "
|
|
"mounts correctly."
|
|
|
|
msgid ""
|
|
"The credentials for the registry could be exposed by running the kubectl "
|
|
"command: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
|
|
"dockerconfigjson}\" | base64 --decode"
|
|
msgstr ""
|
|
"The credentials for the registry could be exposed by running the kubectl "
|
|
"command: kubectl get secret <secret-name> --output=\"jsonpath={.data.\\."
|
|
"dockerconfigjson}\" | base64 --decode"
|
|
|
|
msgid ""
|
|
"The default ``values.yaml`` need to expose those abilities, by adding a new "
|
|
"series of keys/values to add the necessary features."
|
|
msgstr ""
|
|
"The default ``values.yaml`` need to expose those abilities, by adding a new "
|
|
"series of keys/values to add the necessary features."
|
|
|
|
msgid "The detailed proposes change are described as following:"
|
|
msgstr "The detailed proposes change are described as following:"
|
|
|
|
msgid ""
|
|
"The developer documentation in OpenStack-Helm should be updated to guide key "
|
|
"ordering on value files."
|
|
msgstr ""
|
|
"The developer documentation in OpenStack-Helm should be updated to guide key "
|
|
"ordering on value files."
|
|
|
|
msgid ""
|
|
"The developer documentation in OpenStack-Helm should be updated to match the "
|
|
"gated developer deploy process."
|
|
msgstr ""
|
|
"The developer documentation in OpenStack-Helm should be updated to match the "
|
|
"gated developer deploy process."
|
|
|
|
msgid "The existing schema for images is the following:"
|
|
msgstr "The existing schema for images is the following:"
|
|
|
|
msgid ""
|
|
"The following work items need to be completed for this Specification to be "
|
|
"implemented."
|
|
msgstr ""
|
|
"The following work items need to be completed for this Specification to be "
|
|
"implemented."
|
|
|
|
msgid ""
|
|
"The following work items need to be completed for this specification to be "
|
|
"implemented."
|
|
msgstr ""
|
|
"The following work items need to be completed for this specification to be "
|
|
"implemented."
|
|
|
|
msgid ""
|
|
"The last thing to be considered is VM network virtualization. What engine "
|
|
"does SDN use? It is OpenVSwitch, Linux Bridges or l3 routing (no l2 "
|
|
"connectivity). If SDN is using the OpenVSwitch, it can take advantage of "
|
|
"existing OVS daemonsets. Any modification that would be required to OVS "
|
|
"manifests can be included in base Neutron chart as a configurable option. In "
|
|
"that way, the features of OVS can be shared between different SDNs. When "
|
|
"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and "
|
|
"OVS-vswitchd can be left enabled."
|
|
msgstr ""
|
|
"The last thing to be considered is VM network virtualization. What engine "
|
|
"does SDN use? It is OpenVSwitch, Linux Bridges or L3 routing (no L2 "
|
|
"connectivity). If SDN is using the OpenVSwitch, it can take advantage of "
|
|
"existing OVS daemonsets. Any modification that would be required to OVS "
|
|
"manifests can be included in base Neutron chart as a configurable option. In "
|
|
"that way, the features of OVS can be shared between different SDNs. When "
|
|
"using the OVS, default Neutron L2 agent should be disabled, but OVS-DB and "
|
|
"OVS-vswitchd can be left enabled."
|
|
|
|
msgid ""
|
|
"The monolithic Ceph chart does not allow for following Ceph upgrade best "
|
|
"practices, namely to upgrade Mons, OSDs, and client services in that order. "
|
|
"The Ceph chart must therefore be split into at least three charts (one for "
|
|
"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place "
|
|
"upgradability."
|
|
msgstr ""
|
|
"The monolithic Ceph chart does not allow for following Ceph upgrade best "
|
|
"practices, namely to upgrade Mons, OSDs, and client services in that order. "
|
|
"The Ceph chart must therefore be split into at least three charts (one for "
|
|
"each of the above upgrade phases) prior to 1.0 to ensure smooth in-place "
|
|
"upgradability."
|
|
|
|
msgid ""
|
|
"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there "
|
|
"would be no code reuse between the gate and developer environments, so "
|
|
"supporting the existing code for Zuulv2 will incur significant tech-debt."
|
|
msgstr ""
|
|
"The move to Zuulv3 native operation of the OpenStack-Helm gates mean there "
|
|
"would be no code reuse between the gate and developer environments, so "
|
|
"supporting the existing code for Zuulv2 will incur significant tech-debt."
|
|
|
|
msgid ""
|
|
"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:"
|
|
"`` provide the ability for operator to determine whether they would like to "
|
|
"have secrets generated and passed to kubernetes for pulling images."
|
|
msgstr ""
|
|
"The option ``enabled:`` under ``auth:`` and the manifest ``secret_registry:"
|
|
"`` provide the ability for operator to determine whether they would like to "
|
|
"have secrets generated and passed to Kubernetes for pulling images."
|
|
|
|
msgid ""
|
|
"The performance aspect of these point are restricted to deployment, and have "
|
|
"no performance impact on operations."
|
|
msgstr ""
|
|
"The performance aspect of these point are restricted to deployment, and have "
|
|
"no performance impact on operations."
|
|
|
|
msgid "The proposal includes the following:"
|
|
msgstr "The proposal includes the following:"
|
|
|
|
msgid "The proposed requirements for a 1.0 release are as follows:"
|
|
msgstr "The proposed requirements for a 1.0 release are as follows:"
|
|
|
|
msgid ""
|
|
"The proposes change would be to add in :code:`neutron/values.yaml` new "
|
|
"section with boolean values describing which Neutron's Kubernetes resources "
|
|
"should be enabled:"
|
|
msgstr ""
|
|
"The proposes change would be to add in :code:`neutron/values.yaml` new "
|
|
"section with boolean values describing which Neutron's Kubernetes resources "
|
|
"should be enabled:"
|
|
|
|
msgid "The requirements for a logging collector/aggregator include:"
|
|
msgstr "The requirements for a logging collector/aggregator include:"
|
|
|
|
msgid "The requirements for a logging platform include:"
|
|
msgstr "The requirements for a logging platform include:"
|
|
|
|
msgid "The requirements for a monitoring platform include:"
|
|
msgstr "The requirements for a monitoring platform include:"
|
|
|
|
msgid ""
|
|
"The secret would not be created with the default option ``enabled: false`` "
|
|
"and ``secret_registry: true``. To enable secret creation, operator should "
|
|
"override ``enabled:`` to true. The above example shows the default "
|
|
"credentials, operator should override the ``username:`` and ``password:`` "
|
|
"under ``auth:`` section to provide their own credentials."
|
|
msgstr ""
|
|
"The secret would not be created with the default option ``enabled: false`` "
|
|
"and ``secret_registry: true``. To enable secret creation, operator should "
|
|
"override ``enabled:`` to true. The above example shows the default "
|
|
"credentials, operator should override the ``username:`` and ``password:`` "
|
|
"under ``auth:`` section to provide their own credentials."
|
|
|
|
msgid ""
|
|
"The testing will be performed by the OpenStack-Helm gate to demonstrate the "
|
|
"sidecar container correctly routes traffic to the correct services."
|
|
msgstr ""
|
|
"The testing will be performed by the OpenStack-Helm gate to demonstrate the "
|
|
"sidecar container correctly routes traffic to the correct services."
|
|
|
|
msgid ""
|
|
"The top-level keys are based on the organizational keys common to all charts "
|
|
"in the openstack-helm repositories. The top-level keys are strictly ordered "
|
|
"according to function, which creates a common organization pattern between "
|
|
"all charts."
|
|
msgstr ""
|
|
"The top-level keys are based on the organisational keys common to all charts "
|
|
"in the openstack-helm repositories. The top-level keys are strictly ordered "
|
|
"according to function, which creates a common organisation pattern between "
|
|
"all charts."
|
|
|
|
msgid ""
|
|
"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage "
|
|
"the function that will be added in helm-toolkit to create the secret. For "
|
|
"example:"
|
|
msgstr ""
|
|
"Then, add manifest ``secret-registry.yaml`` in ``templates/`` to leverage "
|
|
"the function that will be added in helm-toolkit to create the secret. For "
|
|
"example:"
|
|
|
|
msgid ""
|
|
"Then, inside Kubernetes manifests, add global if statement, deciding if "
|
|
"given manifest should be declared on Kubernetes API, for example :code:"
|
|
"`neutron/templates/daemonset-ovs-agent.yaml`:"
|
|
msgstr ""
|
|
"Then, inside Kubernetes manifests, add global if statement, deciding if "
|
|
"given manifest should be declared on Kubernetes API, for example :code:"
|
|
"`neutron/templates/daemonset-ovs-agent.yaml`:"
|
|
|
|
msgid ""
|
|
"There is no significant performance impact as the traffic will be locally "
|
|
"routed (via 127.0.0.1) and may potentially improve performance for services "
|
|
"whose native TLS handling is inefficient."
|
|
msgstr ""
|
|
"There is no significant performance impact as the traffic will be locally "
|
|
"routed (via 127.0.0.1) and may potentially improve performance for services "
|
|
"whose native TLS handling is inefficient."
|
|
|
|
msgid ""
|
|
"There will be no security impact, as it will deploy the charts in OpenStack-"
|
|
"Helm[-infra/-addons] upon a reference KubeADM administered cluster."
|
|
msgstr ""
|
|
"There will be no security impact, as it will deploy the charts in OpenStack-"
|
|
"Helm[-infra/-addons] upon a reference KubeADM administered cluster."
|
|
|
|
msgid "This Ceph cluster will be used by Cinder and Glance as storage backend."
|
|
msgstr ""
|
|
"This Ceph cluster will be used by Cinder and Glance as storage backend."
|
|
|
|
msgid ""
|
|
"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used "
|
|
"by entire Kubernetes cluster."
|
|
msgstr ""
|
|
"This Ceph cluster will be used for k8s RBD storage (pvc). This can be used "
|
|
"by entire Kubernetes cluster."
|
|
|
|
msgid "This approach:"
|
|
msgstr "This approach:"
|
|
|
|
msgid ""
|
|
"This deployment process will be gated, to ensure that the development the "
|
|
"environment is consistently working against ``master`` for the OpenStack-"
|
|
"Helm repositories."
|
|
msgstr ""
|
|
"This deployment process will be gated, to ensure that the development the "
|
|
"environment is consistently working against ``master`` for the OpenStack-"
|
|
"Helm repositories."
|
|
|
|
msgid ""
|
|
"This enhances the system's security design by allowing pods with services "
|
|
"that cannot natively manage TLS to secure the traffic to the service pod."
|
|
msgstr ""
|
|
"This enhances the system's security design by allowing pods with services "
|
|
"that cannot natively manage TLS to secure the traffic to the service pod."
|
|
|
|
msgid "This feature will not affect the performance of OpenStack-Helm."
|
|
msgstr "This feature will not affect the performance of OpenStack-Helm."
|
|
|
|
msgid ""
|
|
"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will "
|
|
"be used for k8s RBD storage and while other Ceph cluster will be for tenant "
|
|
"facing storage backend for Cinder and Glance."
|
|
msgstr ""
|
|
"This guide shows how to setup multiple Ceph clusters. One Ceph cluster will "
|
|
"be used for k8s RBD storage and while other Ceph cluster will be for tenant "
|
|
"facing storage backend for Cinder and Glance."
|
|
|
|
msgid ""
|
|
"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after "
|
|
"which it will be for historical reference only."
|
|
msgstr ""
|
|
"This spec describes a point-in-time readiness for OpenStack-Helm 1.0, after "
|
|
"which it will be for historical reference only."
|
|
|
|
msgid ""
|
|
"This spec describes a wide variety of self-contained work efforts, which "
|
|
"will be implemented individually by the whole OpenStack-Helm team."
|
|
msgstr ""
|
|
"This spec describes a wide variety of self-contained work efforts, which "
|
|
"will be implemented individually by the whole OpenStack-Helm team."
|
|
|
|
msgid ""
|
|
"This spec lays out the criteria for a stable and reliable 1.0 release, which "
|
|
"can serve as the basis for real-world use as well as ongoing development. "
|
|
"The alternative approaches would be to either iterate indefinitely without "
|
|
"defining a 1.0 release, which would fail to signal to operators the point at "
|
|
"which the platform is ready for real-world use; or, to define a 1.0 release "
|
|
"which fails to satisfy key features which real-world operators need."
|
|
msgstr ""
|
|
"This spec lays out the criteria for a stable and reliable 1.0 release, which "
|
|
"can serve as the basis for real-world use as well as ongoing development. "
|
|
"The alternative approaches would be to either iterate indefinitely without "
|
|
"defining a 1.0 release, which would fail to signal to operators the point at "
|
|
"which the platform is ready for real-world use; or, to define a 1.0 release "
|
|
"which fails to satisfy key features which real-world operators need."
|
|
|
|
msgid ""
|
|
"This spec will be worked helm chart by helm chart, starting with keystone."
|
|
msgstr ""
|
|
"This spec will be worked Helm chart by Helm chart, starting with Keystone."
|
|
|
|
msgid ""
|
|
"This specification also proposes to restrict the addition of any new top-"
|
|
"level keys in charts across all OpenStack-Helm repositories, in order to "
|
|
"maintain the common structure the ordering creates. The addition of a new "
|
|
"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-"
|
|
"case basis. The addition of any new top-level keys should be documented, "
|
|
"and this specification shall be amended to account for any added keys."
|
|
msgstr ""
|
|
"This specification also proposes to restrict the addition of any new top-"
|
|
"level keys in charts across all OpenStack-Helm repositories, in order to "
|
|
"maintain the common structure the ordering creates. The addition of a new "
|
|
"top-level key shall be agreed upon by the OpenStack-Helm team on a case-by-"
|
|
"case basis. The addition of any new top-level keys should be documented, "
|
|
"and this specification shall be amended to account for any added keys."
|
|
|
|
msgid ""
|
|
"This specification proposes defining entries in the values.yaml file into "
|
|
"two categories: top-level keys, and their children (sub-level) keys."
|
|
msgstr ""
|
|
"This specification proposes defining entries in the values.yaml file into "
|
|
"two categories: top-level keys, and their children (sub-level) keys."
|
|
|
|
msgid ""
|
|
"This specification proposes introducing a uniform values.yaml structure "
|
|
"across all charts in openstack-helm, openstack-helm-infra, and openstack-"
|
|
"helm-addons, with the goal of reducing the complexities of working across "
|
|
"multiple charts and reducing the effort for creating new charts."
|
|
msgstr ""
|
|
"This specification proposes introducing a uniform values.yaml structure "
|
|
"across all charts in openstack-helm, openstack-helm-infra, and openstack-"
|
|
"helm-addons, with the goal of reducing the complexities of working across "
|
|
"multiple charts and reducing the effort for creating new charts."
|
|
|
|
msgid ""
|
|
"This specification proposes to add a nginx sidecar container to the pod for "
|
|
"service that requires the tls offloading. The nginx can be used to handle "
|
|
"the TLS offoading and terminate the TLS connection, and routes the traffic "
|
|
"to the service via localhost (127.0.0.1)."
|
|
msgstr ""
|
|
"This specification proposes to add a Nginx sidecar container to the pod for "
|
|
"service that requires the TLS offloading. The Nginx can be used to handle "
|
|
"the TLS offloading and terminate the TLS connection, and routes the traffic "
|
|
"to the service via localhost (127.0.0.1)."
|
|
|
|
msgid ""
|
|
"This specification will address enablement of LinuxBridge network "
|
|
"virtualization for OpenStack Helm (OSH). LinuxBridge is second available "
|
|
"networking technology in Neutron's reference architecture. The first one is "
|
|
"OVS, that is already implemented in OSH."
|
|
msgstr ""
|
|
"This specification will address enablement of LinuxBridge network "
|
|
"virtualization for OpenStack Helm (OSH). LinuxBridge is second available "
|
|
"networking technology in Neutron's reference architecture. The first one is "
|
|
"OVS, that is already implemented in OSH."
|
|
|
|
msgid "Time-series database for collected metrics"
|
|
msgstr "Time-series database for Collected metrics"
|
|
|
|
msgid "Time-series database for logs collected"
|
|
msgstr "Time-series database for logs collected"
|
|
|
|
msgid ""
|
|
"To be able to install Neutron with multiple possible SDNs as networking "
|
|
"plugin, Neutron chart should be modified to enable installation of base "
|
|
"services with decomposable approach. This means that operator can define "
|
|
"which components from base Neutron chart should be installed, and which "
|
|
"should not. This plus proper configuration of Neutron chart would enable "
|
|
"operator to flexibly provision OpenStack with chosen SDN."
|
|
msgstr ""
|
|
"To be able to install Neutron with multiple possible SDNs as networking "
|
|
"plugin, Neutron chart should be modified to enable installation of base "
|
|
"services with decomposable approach. This means that operator can define "
|
|
"which components from base Neutron chart should be installed, and which "
|
|
"should not. This plus proper configuration of Neutron chart would enable "
|
|
"operator to flexibly provision OpenStack with chosen SDN."
|
|
|
|
msgid ""
|
|
"To be able to pull images from an OCI image registry which has the "
|
|
"authentication turned on, kubernetes needs credentials. For each chart, a "
|
|
"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image "
|
|
"credentials, a secret needs to be generated to hold the credentials and the "
|
|
"``imagePullSecrets:`` field should be added in each service account to "
|
|
"specify which secret should be used to get the credentials from when pulling "
|
|
"images by kubelet."
|
|
msgstr ""
|
|
"To be able to pull images from an OCI image registry which has the "
|
|
"authentication turned on, Kubernetes needs credentials. For each chart, a "
|
|
"new ``endpoints:`` entry could be added in ``values.yaml`` to provide image "
|
|
"credentials, a secret needs to be generated to hold the credentials and the "
|
|
"``imagePullSecrets:`` field should be added in each service account to "
|
|
"specify which secret should be used to get the credentials from when pulling "
|
|
"images by kubelet."
|
|
|
|
msgid ""
|
|
"To enable new SDN solution, there should be separate chart created, which "
|
|
"would handle the deployment of service, setting up the database and any "
|
|
"related networking functionality that SDN is providing."
|
|
msgstr ""
|
|
"To enable new SDN solution, there should be separate chart created, which "
|
|
"would handle the deployment of service, setting up the database and any "
|
|
"related networking functionality that SDN is providing."
|
|
|
|
msgid ""
|
|
"To facilitate effective collaboration and communication across the OpenStack-"
|
|
"Helm community team, work items for the enhancements above will be captured "
|
|
"in Storyboard. Therefore, migration from Launchpad to Storyboard must be "
|
|
"accomplished prior to the 1.0 release. Going forward, Storyboard will be "
|
|
"leveraged as a tool to collaboratively define and communicate the OpenStack-"
|
|
"Helm roadmap."
|
|
msgstr ""
|
|
"To facilitate effective collaboration and communication across the OpenStack-"
|
|
"Helm community team, work items for the enhancements above will be captured "
|
|
"in Storyboard. Therefore, migration from Launchpad to Storyboard must be "
|
|
"accomplished prior to the 1.0 release. Going forward, Storyboard will be "
|
|
"leveraged as a tool to collaboratively define and communicate the OpenStack-"
|
|
"Helm roadmap."
|
|
|
|
msgid ""
|
|
"To minimize the performance impacts, the following should be considered:"
|
|
msgstr ""
|
|
"To minimise the performance impacts, the following should be considered:"
|
|
|
|
msgid ""
|
|
"To successfully enforce the ordering defined here, our gates need a method "
|
|
"for validating the ordering and the schema of all values.yaml files. "
|
|
"Without such a mechanism, the overhead associated with properly reviewing "
|
|
"and validating any changes to the structure will be substantial. A tool, "
|
|
"such as yamllint, would provide this functionality and remove the need to "
|
|
"write a custom validation tool"
|
|
msgstr ""
|
|
"To successfully enforce the ordering defined here, our gates need a method "
|
|
"for validating the ordering and the schema of all values.yaml files. "
|
|
"Without such a mechanism, the overhead associated with properly reviewing "
|
|
"and validating any changes to the structure will be substantial. A tool, "
|
|
"such as yamllint, would provide this functionality and remove the need to "
|
|
"write a custom validation tool"
|
|
|
|
msgid "Top-level keys are placed in this order:"
|
|
msgstr "Top-level keys are placed in this order:"
|
|
|
|
msgid "Topic: osh-1.0-requirements_"
|
|
msgstr "Topic: osh-1.0-requirements_"
|
|
|
|
msgid "Trigger alerts when desired replicas fall below required number"
|
|
msgstr "Trigger alerts when desired replicas fall below required number"
|
|
|
|
msgid "Trigger alerts when services become unavailable or unresponsive"
|
|
msgstr "Trigger alerts when services become unavailable or unresponsive"
|
|
|
|
msgid "Under storage: mon directory have been updated."
|
|
msgstr "Under storage: mon directory have been updated."
|
|
|
|
msgid ""
|
|
"Under storageclass section, values for following have been updated: "
|
|
"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
|
|
"user_secret_name"
|
|
msgstr ""
|
|
"Under storageclass section, values for following have been updated: "
|
|
"ceph_configmap_name, admin_secret_name, admin_secret_namespace, "
|
|
"user_secret_name"
|
|
|
|
msgid ""
|
|
"Update ``helm toolkit`` to provide snippet to create the nginx sidecar "
|
|
"container for the services that require it."
|
|
msgstr ""
|
|
"Update ``helm toolkit`` to provide snippet to create the Nginx sidecar "
|
|
"container for the services that require it."
|
|
|
|
msgid ""
|
|
"Update helm-toolkit serviceaccount template to pass the secret in a "
|
|
"conditional"
|
|
msgstr ""
|
|
"Update helm-toolkit serviceaccount template to pass the secret in a "
|
|
"conditional"
|
|
|
|
msgid ""
|
|
"Update helm-toolkit to provide manifest to create secret for registry "
|
|
"authentication"
|
|
msgstr ""
|
|
"Update helm-toolkit to provide manifest to create secret for registry "
|
|
"authentication"
|
|
|
|
msgid "Update of Developer Documentation"
|
|
msgstr "Update of Developer Documentation"
|
|
|
|
msgid ""
|
|
"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of "
|
|
"components"
|
|
msgstr ""
|
|
"Update of Makefile for OpenStack-Helm-Infra to allow modular deployment of "
|
|
"components"
|
|
|
|
msgid "Update of developer documentation"
|
|
msgstr "Update of developer documentation"
|
|
|
|
msgid "Update relevant Documentation."
|
|
msgstr "Update relevant Documentation."
|
|
|
|
msgid "Update script as following:"
|
|
msgstr "Update script as following:"
|
|
|
|
msgid "Update script overrides as following:"
|
|
msgstr "Update script overrides as following:"
|
|
|
|
msgid "Update script to include namespace ``tenant-ceph`` as shown below."
|
|
msgstr "Update script to include namespace ``tenant-ceph`` as shown below."
|
|
|
|
msgid ""
|
|
"Update script with following overrides. Note: The original RBD provisioner "
|
|
"is now deprecated. The CSI RBD provisioner is selected here. If you prefer "
|
|
"the original non-CSI RBD provisioner, then set rbd_provisioner to true "
|
|
"instead."
|
|
msgstr ""
|
|
"Update script with following overrides. Note: The original RBD provisioner "
|
|
"is now deprecated. The CSI RBD provisioner is selected here. If you prefer "
|
|
"the original non-CSI RBD provisioner, then set rbd_provisioner to true "
|
|
"instead."
|
|
|
|
msgid "Update script with following overrides:"
|
|
msgstr "Update script with following overrides:"
|
|
|
|
msgid "Update script's override section with following:"
|
|
msgstr "Update script's override section with following:"
|
|
|
|
msgid "Update service charts to use the updated ``helm toolkit``."
|
|
msgstr "Update service charts to use the updated ``helm toolkit``."
|
|
|
|
msgid "Use Cases"
|
|
msgstr "Use Cases"
|
|
|
|
msgid "Use case"
|
|
msgstr "Use case"
|
|
|
|
msgid "Use cases"
|
|
msgstr "Use cases"
|
|
|
|
msgid ""
|
|
"Use default overrides and execute following scripts as per OSH guide steps:"
|
|
msgstr ""
|
|
"Use default overrides and execute following scripts as per OSH guide steps:"
|
|
|
|
msgid "VM networking performance would be dependent of SDN used."
|
|
msgstr "VM networking performance would be dependent of SDN used."
|
|
|
|
msgid ""
|
|
"VM networking performance would be dependent on linux bridge implementation."
|
|
msgstr ""
|
|
"VM networking performance would be dependent on Linux bridge implementation."
|
|
|
|
msgid "Values File Ordering"
|
|
msgstr "Values File Ordering"
|
|
|
|
msgid ""
|
|
"Version requirements for the following must be documented and maintained:"
|
|
msgstr ""
|
|
"Version requirements for the following must be documented and maintained:"
|
|
|
|
msgid ""
|
|
"Visualize logged events to determine if an event is recurring or an outlier"
|
|
msgstr ""
|
|
"Visualise logged events to determine if an event is recurring or an outlier"
|
|
|
|
msgid ""
|
|
"Visualize performance to identify trends in traffic or utilization over time"
|
|
msgstr ""
|
|
"Visualise performance to identify trends in traffic or utilisation over time"
|
|
|
|
msgid "We are disabling rbd and cephfs provisioners."
|
|
msgstr "We are disabling rbd and cephfs provisioners."
|
|
|
|
msgid ""
|
|
"We need to adapt all the helm charts to remove the hard-coded bits, be image "
|
|
"agnostic, to allow users to bring their own images."
|
|
msgstr ""
|
|
"We need to adapt all the Helm charts to remove the hard-coded bits, be image "
|
|
"agnostic, to allow users to bring their own images."
|
|
|
|
msgid "Web UI (horizon)"
|
|
msgstr "Web UI (Horizon)"
|
|
|
|
msgid ""
|
|
"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` "
|
|
"functions to avoid repeating ourselves."
|
|
msgstr ""
|
|
"When possible, ``values_overrides/`` will refer to existing ``helm-toolkit`` "
|
|
"functions to avoid repeating ourselves."
|
|
|
|
msgid "Work Items"
|
|
msgstr "Work Items"
|
|
|
|
msgid ""
|
|
"Work is underway to refactor common manifest patterns into reusable snippets "
|
|
"in Helm-Toolkit. The following manifests have yet to be combined:"
|
|
msgstr ""
|
|
"Work is underway to refactor common manifest patterns into reusable snippets "
|
|
"in Helm-Toolkit. The following manifests have yet to be combined:"
|
|
|
|
msgid "Worker Deployments"
|
|
msgstr "Worker Deployments"
|
|
|
|
msgid "``040-ceph-ns-activate.sh``"
|
|
msgstr "``040-ceph-ns-activate.sh``"
|
|
|
|
msgid "``050-mariadb.sh``"
|
|
msgstr "``050-mariadb.sh``"
|
|
|
|
msgid "``060-rabbitmq.sh``"
|
|
msgstr "``060-rabbitmq.sh``"
|
|
|
|
msgid "``070-memcached.sh``"
|
|
msgstr "``070-memcached.sh``"
|
|
|
|
msgid "``080-keystone.sh``"
|
|
msgstr "``080-keystone.sh``"
|
|
|
|
msgid "``Ceph ConfigMaps``"
|
|
msgstr "``Ceph ConfigMaps``"
|
|
|
|
msgid "``Ceph Pods``"
|
|
msgstr "``Ceph Pods``"
|
|
|
|
msgid "``Ceph Status``"
|
|
msgstr "``Ceph Status``"
|
|
|
|
msgid "``Ceph endpoints``"
|
|
msgstr "``Ceph endpoints``"
|
|
|
|
msgid "``Ceph for RBD related labels:``"
|
|
msgstr "``Ceph for RBD related labels:``"
|
|
|
|
msgid "``Ceph for Tenant related labels:``"
|
|
msgstr "``Ceph for Tenant related labels:``"
|
|
|
|
msgid "``Ceph secrets``"
|
|
msgstr "``Ceph secrets``"
|
|
|
|
msgid "``Ceph services``"
|
|
msgstr "``Ceph services``"
|
|
|
|
msgid "``Openstack PV list``"
|
|
msgstr "``Openstack PV list``"
|
|
|
|
msgid "``Openstack Pods:``"
|
|
msgstr "``Openstack Pods:``"
|
|
|
|
msgid "``Openstack endpoints``"
|
|
msgstr "``Openstack endpoints``"
|
|
|
|
msgid "``Openstack secrets``"
|
|
msgstr "``Openstack secrets``"
|
|
|
|
msgid "``Openstack services``"
|
|
msgstr "``Openstack services``"
|
|
|
|
msgid "``Storage on node1, node2, node3:``"
|
|
msgstr "``Storage on node1, node2, node3:``"
|
|
|
|
msgid "``Storage on node4, node5, node6:``"
|
|
msgstr "``Storage on node4, node5, node6:``"
|
|
|
|
msgid "``ceph-mon-etc (ceph.conf)``"
|
|
msgstr "``ceph-mon-etc (ceph.conf)``"
|
|
|
|
msgid ""
|
|
"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set "
|
|
"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-"
|
|
"mds"
|
|
msgstr ""
|
|
"``cephfs_provisioner: false`` and ``provision_storage_class: false`` are set "
|
|
"to false to disable cephfs. ``deployment_mds: false`` is set to disable ceph-"
|
|
"mds"
|
|
|
|
msgid "``for CHART in ceph-mon ceph-osd ceph-client; do``"
|
|
msgstr "``for CHART in ceph-mon ceph-osd ceph-client; do``"
|
|
|
|
msgid ""
|
|
"``k8s node list with labels`` After applying above labels, node labels "
|
|
"should look like following."
|
|
msgstr ""
|
|
"``k8s node list with labels`` After applying above labels, node labels "
|
|
"should look like following."
|
|
|
|
msgid "``k8s storageclass``"
|
|
msgstr "``k8s storageclass``"
|
|
|
|
msgid "``netstat ceph mon port``"
|
|
msgstr "``netstat ceph mon port``"
|
|
|
|
msgid "`values.yaml` changes"
|
|
msgstr "`values.yaml` changes"
|
|
|
|
msgid "bootstrap * sub-keys (alphabetical order)"
|
|
msgstr "bootstrap * sub-keys (alphabetical order)"
|
|
|
|
msgid "ceph"
|
|
msgstr "ceph"
|
|
|
|
msgid "conf * sub-keys (up-to-chart-developer)"
|
|
msgstr "conf * sub-keys (up-to-chart-developer)"
|
|
|
|
msgid "dependencies * sub-keys (alphabetical order)"
|
|
msgstr "dependencies * sub-keys (alphabetical order)"
|
|
|
|
msgid ""
|
|
"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
|
|
"fluentbit-fluentd-diagram.png"
|
|
msgstr ""
|
|
"diagram link: https://github.com/sktelecom-oslab/docs/blob/master/images/"
|
|
"fluentbit-fluentd-diagram.png"
|
|
|
|
msgid "endpoints * sub-keys (alphabetical order)"
|
|
msgstr "endpoints * sub-keys (alphabetical order)"
|
|
|
|
msgid "etcd"
|
|
msgstr "etcd"
|
|
|
|
msgid "evrardjp"
|
|
msgstr "evrardjp"
|
|
|
|
msgid "fluentbit-fluentd logging architecture"
|
|
msgstr "fluentbit-fluentd logging architecture"
|
|
|
|
msgid ""
|
|
"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
|
|
msgstr ""
|
|
"https://blueprints.launchpad.net/openstack-helm/+spec/developer-environment"
|
|
|
|
msgid "https://kubernetes.io/docs/concepts/containers/images"
|
|
msgstr "https://kubernetes.io/docs/concepts/containers/images"
|
|
|
|
msgid ""
|
|
"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
|
|
"account/#add-imagepullsecrets-to-a-service-account"
|
|
msgstr ""
|
|
"https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-"
|
|
"account/#add-imagepullsecrets-to-a-service-account"
|
|
|
|
msgid "https://review.openstack.org/#/c/552485/"
|
|
msgstr "https://review.openstack.org/#/c/552485/"
|
|
|
|
msgid "https://storyboard.openstack.org/#!/story/2005130"
|
|
msgstr "https://storyboard.openstack.org/#!/story/2005130"
|
|
|
|
msgid "images * sub-keys (alphabetical order)"
|
|
msgstr "images * sub-keys (alphabetical order)"
|
|
|
|
msgid "ingress"
|
|
msgstr "ingress"
|
|
|
|
msgid "k8s namespace: ceph"
|
|
msgstr "k8s namespace: ceph"
|
|
|
|
msgid "k8s namespace: tenant-ceph"
|
|
msgstr "k8s namespace: tenant-ceph"
|
|
|
|
msgid "k8s node labels:"
|
|
msgstr "k8s node labels:"
|
|
|
|
msgid "korzen (Artur Korzeniewski)"
|
|
msgstr "korzen (Artur Korzeniewski)"
|
|
|
|
msgid "labels * sub-keys (alphabetical order)"
|
|
msgstr "labels * sub-keys (alphabetical order)"
|
|
|
|
msgid "ldap"
|
|
msgstr "ldap"
|
|
|
|
msgid "libvirt"
|
|
msgstr "libvirt"
|
|
|
|
msgid "manifests * sub-keys (alphabetical order)"
|
|
msgstr "manifests * sub-keys (alphabetical order)"
|
|
|
|
msgid "mariadb"
|
|
msgstr "mariadb"
|
|
|
|
msgid "mattmceuen (Matt McEuen <matt.mceuen@att.com>) for coordination"
|
|
msgstr "mattmceuen (Matt McEuen <matt.mceuen@att.com>) for coordination"
|
|
|
|
msgid "memcached"
|
|
msgstr "memcached"
|
|
|
|
msgid "metric port: 9283"
|
|
msgstr "metric port: 9283"
|
|
|
|
msgid "metric port: 9284"
|
|
msgstr "metric port: 9284"
|
|
|
|
msgid "mgr endpoint port: 7000"
|
|
msgstr "mgr endpoint port: 7000"
|
|
|
|
msgid "mgr endpoint port: 7001"
|
|
msgstr "mgr endpoint port: 7001"
|
|
|
|
msgid "mon endpoint port: 6789"
|
|
msgstr "mon endpoint port: 6789"
|
|
|
|
msgid "mon endpoint port: 6790"
|
|
msgstr "mon endpoint port: 6790"
|
|
|
|
msgid "mon_addr and mon_host have non default mon port 6790."
|
|
msgstr "mon_addr and mon_host have non default mon port 6790."
|
|
|
|
msgid "mongodb"
|
|
msgstr "mongodb"
|
|
|
|
msgid "monitoring * sub-keys (alphabetical order)"
|
|
msgstr "monitoring * sub-keys (alphabetical order)"
|
|
|
|
msgid "network * sub-keys (alphabetical order)"
|
|
msgstr "network * sub-keys (alphabetical order)"
|
|
|
|
msgid "no ceph-mds"
|
|
msgstr "no ceph-mds"
|
|
|
|
msgid "no ceph-mds and ceph-rgw"
|
|
msgstr "no ceph-mds and ceph-rgw"
|
|
|
|
msgid "no storage classes"
|
|
msgstr "no storage classes"
|
|
|
|
msgid ""
|
|
"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
|
|
"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
|
|
msgstr ""
|
|
"openstack-control-plane=enabled, ceph-mon=enabled, ceph-mgr=enabled, ceph-"
|
|
"rgw=enabled, ceph-mds=enabled, ceph-osd=enabled"
|
|
|
|
msgid ""
|
|
"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
|
|
"tenant=enabled, openstack-data-plane=enabled"
|
|
msgstr ""
|
|
"openstack-data-plane=enabled, openstack-compute-node=enabled, ceph-osd-"
|
|
"tenant=enabled, openstack-data-plane=enabled"
|
|
|
|
msgid "openvswitch"
|
|
msgstr "openvswitch"
|
|
|
|
msgid "pod * sub-keys (alphabetical order)"
|
|
msgstr "pod * sub-keys (alphabetical order)"
|
|
|
|
msgid ""
|
|
"portdirect (Pete Birley <pete@port.direct>) for the release management spec "
|
|
"[2]_"
|
|
msgstr ""
|
|
"portdirect (Pete Birley <pete@port.direct>) for the release management spec "
|
|
"[2]_"
|
|
|
|
msgid "portdirect (Pete Birley)"
|
|
msgstr "portdirect (Pete Birley)"
|
|
|
|
msgid "postgresql"
|
|
msgstr "postgresql"
|
|
|
|
msgid ""
|
|
"powerds (DaeSeong Kim <daeseong.kim@sk.com>) for the `values.yaml` ordering "
|
|
"spec [1]_"
|
|
msgstr ""
|
|
"powerds (DaeSeong Kim <daeseong.kim@sk.com>) for the `values.yaml` ordering "
|
|
"spec [1]_"
|
|
|
|
msgid ""
|
|
"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
|
|
"<sw5822@att.com>)"
|
|
msgstr ""
|
|
"powerds0111 (DaeSeong Kim <daeseong.kim@sk.com>) srwilkers (Steve Wilkerson "
|
|
"<sw5822@att.com>)"
|
|
|
|
msgid "rabbitmq"
|
|
msgstr "rabbitmq"
|
|
|
|
msgid ""
|
|
"randeep.jalli (Randeep Jalli <rj2083@att.com>) and renmak (Renis Makadia "
|
|
"<renis.makadia@att.com>) for splitting up the Ceph chart"
|
|
msgstr ""
|
|
"randeep.jalli (Randeep Jalli <rj2083@att.com>) and renmak (Renis Makadia "
|
|
"<renis.makadia@att.com>) for splitting up the Ceph chart"
|
|
|
|
msgid ""
|
|
"rwellum (Rich Wellum <richwellum@gmail.com>) for coordination of Storyboard "
|
|
"adoption"
|
|
msgstr ""
|
|
"rwellum (Rich Wellum <richwellum@gmail.com>) for coordination of Storyboard "
|
|
"adoption"
|
|
|
|
msgid "secrets * sub-keys (alphabetical order)"
|
|
msgstr "secrets * sub-keys (alphabetical order)"
|
|
|
|
msgid "services do not handle TLS offloading and termination,"
|
|
msgstr "services do not handle TLS offloading and termination,"
|
|
|
|
msgid ""
|
|
"services whose native handling of TLS offloading and termination cause major "
|
|
"performance impact, for example, eventlet."
|
|
msgstr ""
|
|
"services whose native handling of TLS offloading and termination cause major "
|
|
"performance impact, for example, eventlet."
|
|
|
|
msgid ""
|
|
"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
|
|
msgstr ""
|
|
"srwilker (Steve Wilkerson) portdirect (Pete Birley) lr699s (Larry Rensing)"
|
|
|
|
msgid "storage classes: general (rbd based for pvc)"
|
|
msgstr "storage classes: general (rbd based for pvc)"
|
|
|
|
msgid "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
|
|
msgstr "sungil (Sungil Im) jayahn (Jaesuk Ahn)"
|
|
|
|
msgid ""
|
|
"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
|
|
"tenant=enabled, ceph-rgw-tenant=enabled"
|
|
msgstr ""
|
|
"tenant-ceph-control-plane=enabled, ceph-mon-tenant=enabled, ceph-mgr-"
|
|
"tenant=enabled, ceph-rgw-tenant=enabled"
|
|
|
|
msgid ""
|
|
"the impact of adding extra conditionals in the helm charts, to deal with "
|
|
"multi-distro aspect (if not using the approach above, or when using an "
|
|
"alternative approach)"
|
|
msgstr ""
|
|
"the impact of adding extra conditionals in the helm charts, to deal with "
|
|
"multi-distro aspect (if not using the approach above, or when using an "
|
|
"alternative approach)"
|
|
|
|
msgid ""
|
|
"the impact of adding functionality in the ``helm-toolkit`` to deal with a "
|
|
"common multi-distro aspect (could possibly increase helm chart rendering "
|
|
"time)"
|
|
msgstr ""
|
|
"the impact of adding functionality in the ``helm-toolkit`` to deal with a "
|
|
"common multi-distro aspect (could possibly increase Helm chart rendering "
|
|
"time)"
|
|
|
|
msgid ""
|
|
"the impact of exposing extra key/values in the helm chart ``values.yaml`` "
|
|
"file (could possibly have a deployment speed/ram usage increase)."
|
|
msgstr ""
|
|
"the impact of exposing extra key/values in the helm chart ``values.yaml`` "
|
|
"file (could possibly have a deployment speed/ram usage increase)."
|