openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: I8509a564f8db79c2796fef72aaa7f8615cbe20c1
This commit is contained in:
OpenStack Proposal Bot 2014-05-21 06:18:10 +00:00
parent 3e55d4c29f
commit f671ef84d7
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/training-guides/locale/training-guides.pot
View File

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-05-16 06:35+0000\n"
"POT-Creation-Date: 2014-05-21 06:17+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -919,7 +919,7 @@ msgid "Host Operating System (Host)"
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:9(para)
msgid "The operating system that is installed on your laptop or desktop that hosts virtual machines. Commonly referred to as host OS or <glossterm>host</glossterm>. In short, the machine where your Virtual Box is installed."
msgid "The operating system that is installed on your laptop or desktop that hosts virtual machines. This is commonly referred to as the host OS or <glossterm>host</glossterm>. In short, the machine where your Virtual Box is installed."
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:16(title)
@ -927,7 +927,7 @@ msgid "Guest Operating System (Guest)"
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:17(para)
msgid "The operating system that is installed on your Virtual Box Virtual Machine. This virtual instance is independent of the host OS. Commonly referred to as <glossterm>guest OS</glossterm> or guest."
msgid "The operating system that is installed on your Virtual Box Virtual Machine. This virtual instance is independent of the host OS. It is commonly referred to as <glossterm>guest OS</glossterm> or guest."
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:23(title)
@ -943,7 +943,7 @@ msgid "Control Node"
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:29(para)
msgid "Hosts the database, Keystone (Middleware), and the servers for the scope of the current OpenStack deployment. Acts as the brains behind OpenStack and drives services such as authentication, database, and so on."
msgid "Hosts the database, Keystone (Middleware), and the servers for the scope of the current OpenStack deployment. It acts as the brains behind OpenStack and drives services such as authentication, database, and so on."
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:35(title) ./doc/training-guides/lab003-compute-node.xml:7(title) ./doc/training-guides/lab003-compute-node.xml:32(guilabel) ./doc/training-guides/bk002-ch007-operator-compute-node.xml:8(title) ./doc/training-guides/bk001-ch005-associate-compute-node.xml:8(title)
@ -967,7 +967,7 @@ msgid "Using OpenSSH"
msgstr ""
#: ./doc/training-guides/lab000-important-terms.xml:46(para)
msgid "After you set up the network interfaces file, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine. Run the following command: <placeholder-1/>"
msgid "After the network interfaces file has been setup, you can switch to an SSH session by using an OpenSSH client to log in remotely to the required server node (Control, Network, Compute). Open a terminal on your host machine and run the following command: <placeholder-1/>"
msgstr ""
#: ./doc/training-guides/card007-core-overview.xml:7(title)
@ -8089,15 +8089,15 @@ msgid "Security Groups"
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:9(para)
msgid "Security groups and security group rules allows administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
msgid "Security groups and security group rules allow administrators and tenants the ability to specify the type of traffic and direction (ingress/egress) that is allowed to pass through a port. A security group is a container for security group rules."
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:14(para)
msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress. Rules can be added to this group in order to change the behaviour."
msgid "When a port is created in OpenStack Networking it is associated with a security group. If a security group is not specified the port will be associated with a 'default' security group. By default this group will drop all ingress traffic and allow all egress traffic. Rules can be added to this group in order to change this behaviour."
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:20(para)
msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file /etc/nova/nova.conf and set the config option security_group_api=neutron on every node running nova-compute and nova-api. After this change is made restart nova-api and nova-compute in order to pick up this change. After this change is made one will be able to use both the OpenStack Compute and OpenStack Network security group API at the same time."
msgid "If one desires to use the OpenStack Compute security group APIs and/or have OpenStack Compute orchestrate the creation of new ports for instances on specific security groups, additional configuration is needed. To enable this, one must configure the following file /etc/nova/nova.conf and set the config option security_group_api=neutron on every node running nova-compute and nova-api. After this change is made, restart nova-api and nova-compute in order to pick up this change. After this change is made, the user will be able to use both the OpenStack Compute and OpenStack Network security group API at the same time."
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:32(guilabel)
@ -8105,11 +8105,11 @@ msgid "Authentication and Authorization"
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:33(para)
msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled Users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies:"
msgid "OpenStack Networking uses the OpenStack Identity service (project name keystone) as the default authentication service. When OpenStack Identity is enabled, users submitting requests to the OpenStack Networking service must provide an authentication token in X-Auth-Token request header. The aforementioned token should have been obtained by authenticating with the OpenStack Identity endpoint. For more information concerning authentication with OpenStack Identity, please refer to the OpenStack Identity documentation. When OpenStack Identity is enabled, it is not mandatory to specify tenant_id for resources in create requests, as the tenant identifier will be derived from the Authentication token. Please note that the default authorization settings only allow administrative users to create resources on behalf of a different tenant. OpenStack Networking uses information received from OpenStack Identity to authorize user requests. OpenStack Networking handles two kind of authorization policies:"
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:54(para)
msgid "<emphasis role=\"bold\">Operation-based:</emphasis> policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes;"
msgid "<emphasis role=\"bold\">Operation-based:</emphasis> policies specify access criteria for specific operations, possibly with fine-grained control over specific attributes."
msgstr ""
#: ./doc/training-guides/module002-ch004-security-in-neutron.xml:60(para)