# # Translators: # Łukasz Jernaś , 2013-2014 msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" "POT-Creation-Date: 2014-01-17 07:14+0000\n" "PO-Revision-Date: 2014-01-16 16:00+0000\n" "Last-Translator: Łukasz Jernaś \n" "Language-Team: Polish (Poland) (http://www.transifex.com/projects/p/openstack/language/pl_PL/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: pl_PL\n" "Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #: ./doc/install-guide/section_keystone-users.xml5(title) msgid "Define users, tenants, and roles" msgstr "" #: ./doc/install-guide/section_keystone-users.xml7(para) msgid "" "After you install the Identity Service, set up users, tenants, and roles to " "authenticate against. These are used to allow access to services and " "endpoints, described in the next section." msgstr "" #: ./doc/install-guide/section_keystone-users.xml21(replaceable) #: ./doc/install-guide/section_keystone-users.xml24(replaceable) msgid "FCAF3E..." msgstr "" #: ./doc/install-guide/section_keystone-users.xml11(para) msgid "" "Typically, you would indicate a user and password to authenticate with the " "Identity Service. At this point, however, we have not created any users, so " "we have to use the authorization token created in the previous section. You " "can pass this with the option to the " " command or set the OS_SERVICE_TOKEN " "environment variable. We'll set OS_SERVICE_TOKEN, as well as " "OS_SERVICE_ENDPOINT to specify where the Identity Service is " "running. Replace with your authorization token." msgstr "" #: ./doc/install-guide/section_keystone-users.xml27(para) msgid "" "First, create a tenant for an administrative user and a tenant for other " "OpenStack services to use." msgstr "" #: ./doc/install-guide/section_keystone-users.xml33(para) msgid "" "Next, create an administrative user called admin. Choose " "a password for the admin user and specify an email " "address for the account." msgstr "" #: ./doc/install-guide/section_keystone-users.xml37(replaceable) #: ./doc/install-guide/section_keystone-verify.xml25(replaceable) #: ./doc/install-guide/section_keystone-verify.xml35(replaceable) #: ./doc/install-guide/section_keystone-verify.xml48(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml408(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml377(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml483(replaceable) msgid "ADMIN_PASS" msgstr "HASŁO_ADMIN" #: ./doc/install-guide/section_keystone-users.xml38(replaceable) msgid "admin@example.com" msgstr "" #: ./doc/install-guide/section_keystone-users.xml40(para) msgid "" "Create a role for administrative tasks called admin. Any " "roles you create should map to roles specified in the " "policy.json files of the various OpenStack services. " "The default policy files use the admin role to allow " "access to most services." msgstr "" #: ./doc/install-guide/section_keystone-users.xml48(para) msgid "" "Finally, you have to add roles to users. Users always log in with a tenant, " "and roles are assigned to users within tenants. Add the " "admin role to the admin user when " "logging in with the admin tenant." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-api-endpoints.xml29(None) msgid "" "@@image: 'figures/debconf-screenshots/api-endpoint_1_register_endpoint.png';" " md5=d534be231be4f725820a1050fbf44231" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-api-endpoints.xml40(None) msgid "" "@@image: 'figures/debconf-screenshots/api-" "endpoint_2_keystone_server_ip.png'; md5=d2c5a5b82dd433fcf9cde6f5ac34c30e" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-api-endpoints.xml54(None) msgid "" "@@image: 'figures/debconf-screenshots/api-" "endpoint_3_keystone_authtoken.png'; md5=1f3b05ebe671f64d672ac70d246e4f39" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-api-endpoints.xml69(None) msgid "" "@@image: 'figures/debconf-screenshots/api-" "endpoint_4_service_endpoint_ip_address.png'; " "md5=6853f0ae2ef8d5fddb22c466d465de15" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-api-endpoints.xml81(None) msgid "" "@@image: 'figures/debconf-screenshots/api-endpoint_5_region_name.png'; " "md5=a6bce0acf5a1cb85f161290f0cf30733" msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml6(title) msgid "Register API endpoints" msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml7(para) msgid "" "All Debian packages for API services, except the heat-api" " package, register the service in the Identity Service catalog. This feature" " is helpful because API endpoints are difficult to remember." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml12(para) msgid "" "The heat-common package and not the heat-" "api package configures the Orchestration service." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml16(para) msgid "" "When you install a package for an API service, you are prompted to register " "that service. However, after you install or upgrade the package for an API " "service, Debian immediately removes your response to this prompt from the " "debconf database. Consequently, you are prompted to re-" "register the service with the Identity Service. If you already registered " "the API service, respond no when you upgrade." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml33(para) msgid "This screen registers packages in the Identity Service catalog:" msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml44(para) msgid "" "You are prompted for the Identity Service admin_token " "value. The Identity Service uses this value to register the API service. " "When you set up the keystone package, this value is " "configured automatically." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml58(para) msgid "" "This screen configures the IP addresses for the service. The configuration " "script automatically detects the IP address used by the interface that is " "connected to the default route (/sbin/route and " "/sbin/ip)." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml62(para) msgid "" "Unless you have a unique set up for your network, press " "ENTER." msgstr "" #: ./doc/install-guide/section_debconf-api-endpoints.xml73(para) msgid "" "This screen configures the region name for the service. For example, us-east-coast or europe-paris." msgstr "" #: ./doc/install-guide/ch_glance.xml6(title) msgid "Configure the Image Service" msgstr "" #: ./doc/install-guide/ch_glance.xml7(para) msgid "" "The OpenStack Image Service enables users to discover, register, and " "retrieve virtual machine images. Also known as the glance project, the Image" " Service offers a REST API that enables you to query virtual machine image " "metadata and retrieve an actual image. Virtual machine images made available" " through the Image Service can be stored in a variety of locations from " "simple file systems to object-storage systems like OpenStack Object Storage." msgstr "" #: ./doc/install-guide/ch_glance.xml16(para) msgid "" "For simplicity this guide configures the Image Service to use the " "file backend. This means that images uploaded to the " "Image Service will be stored in a directory on the same system that hosts " "the service. By default this directory is " "/var/lib/glance/images/." msgstr "" #: ./doc/install-guide/ch_glance.xml23(para) msgid "" "Ensure that the system has sufficient space available under this directory " "to store virtual machine images and snapshots before proceeding. At an " "absolute minimum several gigabytes of space should be available for use by " "the Image Service in a proof of concept deployment." msgstr "" #: ./doc/install-guide/ch_cinder.xml6(title) msgid "Add the Block Storage Service" msgstr "" #: ./doc/install-guide/ch_cinder.xml7(para) msgid "" "The OpenStack Block Storage Service works though the interaction of a series" " of daemon processes named cinder-* that reside persistently on the host " "machine or machines. You can run the binaries from a single node or across " "multiple nodes. You can also run them on the same node as other OpenStack " "services. The following sections introduce Block Storage Service components " "and concepts and show you how to configure and install the Block Storage " "Service." msgstr "" #: ./doc/install-guide/section_nova-kvm.xml5(title) msgid "Enable KVM on the Compute node" msgstr "" #: ./doc/install-guide/section_nova-kvm.xml7(para) msgid "" "OpenStack Compute requires hardware virtualization support and certain " "kernel modules. Use the following procedure to determine whether your system" " has this support and the correct kernel modules and to enable KVM. In many " "cases, your distribution completes this installation and you do not need to " "perform any additional action." msgstr "" #: ./doc/install-guide/section_glance-verify.xml5(title) msgid "Verify the Image Service installation" msgstr "" #: ./doc/install-guide/section_glance-verify.xml6(para) msgid "" "To test the Image Service installation, download at least one virtual " "machine image that is known to work with OpenStack. For example, CirrOS is a" " small test image that is often used for testing OpenStack deployments " "(CirrOS downloads). " "This walk through uses the 64-bit CirrOS QCOW2 image." msgstr "" #: ./doc/install-guide/section_glance-verify.xml13(para) msgid "" "For more information about how to download and build images, see OpenStack Virtual Machine Image " "Guide. For information about how to manage images, see " "the OpenStack User " "Guide." msgstr "" #: ./doc/install-guide/section_glance-verify.xml24(para) msgid "" "Download the image into a dedicated directory using or " ":" msgstr "" #: ./doc/install-guide/section_glance-verify.xml32(para) msgid "Upload the image to the Image Service:" msgstr "" #: ./doc/install-guide/section_glance-verify.xml33(replaceable) #: ./doc/install-guide/section_glance-verify.xml38(replaceable) msgid "imageLabel" msgstr "" #: ./doc/install-guide/section_glance-verify.xml33(replaceable) #: ./doc/install-guide/section_glance-verify.xml45(replaceable) msgid "fileFormat" msgstr "" #: ./doc/install-guide/section_glance-verify.xml34(replaceable) #: ./doc/install-guide/section_glance-verify.xml65(replaceable) msgid "containerFormat" msgstr "" #: ./doc/install-guide/section_glance-verify.xml34(replaceable) #: ./doc/install-guide/section_glance-verify.xml86(replaceable) msgid "accessValue" msgstr "" #: ./doc/install-guide/section_glance-verify.xml34(replaceable) #: ./doc/install-guide/section_glance-verify.xml101(replaceable) msgid "imageFile" msgstr "" #: ./doc/install-guide/section_glance-verify.xml35(para) msgid "Where:" msgstr "" #: ./doc/install-guide/section_glance-verify.xml40(para) msgid "Arbitrary label. The name by which users refer to the image." msgstr "" #: ./doc/install-guide/section_glance-verify.xml47(para) msgid "" "Specifies the format of the image file. Valid formats include " "qcow2, raw, vhd, " "vmdk, vdi, iso, " "aki, ari, and ami." msgstr "" #: ./doc/install-guide/section_glance-verify.xml58(para) msgid "" "You can verify the format using the command: " "" msgstr "" #: ./doc/install-guide/section_glance-verify.xml67(para) msgid "" "Specifies the container format. Valid formats include: " "bare, ovf, aki, " "ari and ami." msgstr "" #: ./doc/install-guide/section_glance-verify.xml73(para) msgid "" "Specify bare to indicate that the image file is not in a " "file format that contains metadata about the virtual machine. Although this " "field is currently required, it is not actually used by any of the OpenStack" " services and has no effect on system behavior. Because the value is not " "used anywhere, it safe to always specify bare as the " "container format." msgstr "" #: ./doc/install-guide/section_glance-verify.xml90(para) msgid "true - All users can view and use the image." msgstr "" #: ./doc/install-guide/section_glance-verify.xml94(para) msgid "false - Only administrators can view and use the image." msgstr "" #: ./doc/install-guide/section_glance-verify.xml88(para) msgid "Specifies image access: " msgstr "" #: ./doc/install-guide/section_glance-verify.xml103(para) msgid "Specifies the name of your downloaded image file." msgstr "" #: ./doc/install-guide/section_glance-verify.xml108(para) msgid "For example:" msgstr "Na przykład:" #: ./doc/install-guide/section_glance-verify.xml132(para) msgid "" "Because the returned image ID is generated dynamically, your deployment " "generates a different ID than the one shown in this example." msgstr "" #: ./doc/install-guide/section_glance-verify.xml138(para) msgid "Confirm that the image was uploaded and display its attributes:" msgstr "" #: ./doc/install-guide/ch_clients.xml6(title) msgid "Install and configure the OpenStack clients" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-keystone_authtoken.xml30(None) msgid "" "@@image: 'figures/debconf-" "screenshots/service_keystone_authtoken_server_hostname.png'; " "md5=aafd53894e1d960531d4901123952117" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-keystone_authtoken.xml37(None) msgid "" "@@image: 'figures/debconf-" "screenshots/service_keystone_authtoken_admin_tenant_name.png'; " "md5=a935563e4fba9b00040e35cdcfffc732" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-keystone_authtoken.xml44(None) msgid "" "@@image: 'figures/debconf-" "screenshots/service_keystone_authtoken_tenant_admin_user.png'; " "md5=fe3dc93c591b3e9783d4d05556efcf25" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-keystone_authtoken.xml51(None) msgid "" "@@image: 'figures/debconf-" "screenshots/service_keystone_authtoken_admin_password.png'; " "md5=0c30c80315d5e636dbe93a938fc2822b" msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml6(title) msgid "Services and the [keystone_authtoken]" msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml7(para) msgid "" "Because most OpenStack services must access the Identity Service, you must " "configure the IP address of the keystone server to be able to " "access it. You must also configure the admin_tenant_name, " "admin_user, and admin_password options for each " "service to work." msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml13(para) msgid "Generally, this section looks like this:" msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml21(para) msgid "" "The debconf system helps users configure the auth_host, " "admin_tenant_name, admin_user and " "admin_password options." msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml25(para) msgid "The following screens show an example Image Service configuration:" msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml55(para) msgid "" "This information is stored in the configuration file for each service. For " "example:" msgstr "" #: ./doc/install-guide/section_debconf-keystone_authtoken.xml63(para) msgid "" "The Debian OpenStack packages offer automation for this, so OpenStack users " "do not have to manually edit the configuration files." msgstr "" #: ./doc/install-guide/ch_swift.xml6(title) msgid "Add Object Storage" msgstr "" #: ./doc/install-guide/ch_swift.xml8(para) msgid "" "The OpenStack Object Storage services work together to provide object " "storage and retrieval through a REST API. For this example architecture, you" " must have already installed the Identity Service, also known as Keystone." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml8(title) msgid "Neutron concepts" msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml9(para) msgid "" "Like Nova Networking, Neutron manages software-defined networking for your " "OpenStack installation. However, unlike Nova Networking, you can configure " "Neutron for advanced virtual network topologies, such as per-tenant private " "networks and more." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml13(para) msgid "" "Neutron has the following object abstractions: networks, subnets, and " "routers. Each has functionality that mimics its physical counterpart: " "networks contain subnets, and routers route traffic between different subnet" " and networks." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml17(para) msgid "" "Any given Neutron set up has at least one external network. This network, " "unlike the other networks, is not merely a virtually defined network. " "Instead, it represents the view into a slice of the external network that is" " accessible outside the OpenStack installation. IP addresses on the Neutron " "external network are accessible by anybody physically on the outside " "network. Because this network merely represents a slice of the outside " "network, DHCP is disabled on this network." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml25(para) msgid "" "In addition to external networks, any Neutron set up has one or more " "internal networks. These software-defined networks connect directly to the " "VMs. Only the VMs on any given internal network, or those on subnets " "connected through interfaces to a similar router, can access VMs connected " "to that network directly." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml30(para) msgid "" "For the outside network to access VMs, and vice versa, routers between the " "networks are needed. Each router has one gateway that is connected to a " "network and many interfaces that are connected to subnets. Like a physical " "router, subnets can access machines on other subnets that are connected to " "the same router, and machines can access the outside network through the " "gateway for the router." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml37(para) msgid "" "Additionally, you can allocate IP addresses on an external networks to ports" " on the internal network. Whenever something is connected to a subnet, that " "connection is called a port. You can associate external network IP addresses" " with ports to VMs. This way, entities on the outside network can access " "VMs." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml42(para) msgid "" "Neutron also supports security groups. " "Security groups enable administrators to define firewall rules in groups. A " "VM can belong to one or more security groups, and Neutron applies the rules " "in those security groups to block or unblock ports, port ranges, or traffic " "types for that VM." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml48(para) msgid "" "Each plug-in that Neutron uses has its own concepts. While not vital to " "operating Neutron, understanding these concepts can help you set up Neutron." " All Neutron installations use a core plug-in and a security group plug-in " "(or just the No-Op security group plug-in). Additionally, Firewall-" "as-a-service (FWaaS) and Load-balancing-as-a-service (LBaaS) plug-ins are " "available." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml55(title) msgid "Open vSwitch concepts" msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml56(para) msgid "" "The Open vSwitch plug-in is one of the most popular core plug-ins. Open " "vSwitch configurations consists of bridges and ports. Ports represent " "connections to other things, such as physical interfaces and patch cables. " "Packets from any given port on a bridge are shared with all other ports on " "that bridge. Bridges can be connected through Open vSwitch virtual patch " "cables or through Linux virtual Ethernet cables (veth). " "Additionally, bridges appear as network interfaces to Linux, so you can " "assign IP addresses to them." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml66(para) msgid "" "In Neutron, the integration bridge, called br-int, " "connects directly to the VMs and associated services. The external bridge, " "called br-ex, connects to the external network. Finally, " "the VLAN configuration of the Open vSwitch plug-in uses bridges associated " "with each physical network." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml72(para) msgid "" "In addition to defining bridges, Open vSwitch has OpenFlow, which enables " "you to define networking flow rules. Certain configurations use these rules " "to transfer packets between VLANs." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml76(para) msgid "" "Finally, some configurations of Open vSwitch use network namespaces that " "enable Linux to group adapters into unique namespaces that are not visible " "to other namespaces, which allows the same network node to manage multiple " "Neutron routers." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml81(para) msgid "" "With Open vSwitch, you can use two different technologies to create the " "virtual networks: GRE or VLANs." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml83(para) msgid "" "Generic Routing Encapsulation (GRE) is the technology used in many VPNs. It " "wraps IP packets to create entirely new packets with different routing " "information. When the new packet reaches its destination, it is unwrapped, " "and the underlying packet is routed. To use GRE with Open vSwitch, Neutron " "creates GRE tunnels. These tunnels are ports on a bridge and enable bridges " "on different systems to act as though they were one bridge, which allows the" " compute and network nodes to act as one for the purposes of routing." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml92(para) msgid "" "Virtual LANs (VLANs), on the other hand, use a special modification to the " "Ethernet header. They add a 4-byte VLAN tag that ranges from 1 to 4094 (the " "0 tag is special, and the 4095 tag, made of all ones, is equivalent to an " "untagged packet). Special NICs, switches, and routers know how to interpret " "the VLAN tags, as does Open vSwitch. Packets tagged for one VLAN are only " "shared with other devices configured to be on that VLAN, even through all " "devices are on the same physical network." msgstr "" #: ./doc/install-guide/section_neutron-concepts.xml101(para) msgid "" "The most common security group driver used with Open vSwitch is the Hybrid " "IPTables/Open vSwitch plug-in. It uses a combination for IPTables and " "OpenFlow rules. Use the IPTables tool to create firewalls and set up NATs on" " Linux. This tool uses a complex rule system and chains of rules to " "accommodate the complex rules required by Neutron security groups." msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml6(title) msgid "Install the Telemetry service" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml8(para) msgid "" "OpenStack Telemetry is an API service that provides a collector and a range " "of disparate agents. Before you can install these agents on nodes such as " "the compute node, you must use this procedure to install the core components" " on the controller node." msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml14(para) msgid "Install the Telemetry service on the controller node:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml21(para) msgid "" "Respond to the prompts for [keystone_authtoken] " "settings, RabbitMQ " "credentials and API " "endpoint registration." msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml29(para) msgid "" "The Telemetry service uses a database to store information. Specify the " "location of the database in the configuration file. The examples use a " "MongoDB database on the controller node:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml38(para) msgid "" "Configure MongoDB to make it listen on the controller public IP address. " "Edit the /etc/mongodb.conf file and modify the " "bind_ip key:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml44(para) msgid "Restart the MongoDB service to apply the configuration change:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml48(para) msgid "" "Start the MongoDB server and configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml58(para) msgid "Create the database and a ceilometer database user:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml63(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml70(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml79(replaceable) msgid "CEILOMETER_DBPASS" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml68(para) msgid "Configure the Telemetry service to use the database:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml70(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml79(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml113(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml135(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml181(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml182(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml183(replaceable) #: ./doc/install-guide/section_nova-controller.xml55(replaceable) #: ./doc/install-guide/section_nova-controller.xml69(replaceable) #: ./doc/install-guide/section_nova-controller.xml154(replaceable) #: ./doc/install-guide/section_nova-controller.xml194(replaceable) #: ./doc/install-guide/section_nova-controller.xml197(replaceable) #: ./doc/install-guide/section_nova-controller.xml221(replaceable) #: ./doc/install-guide/section_nova-controller.xml222(replaceable) #: ./doc/install-guide/section_nova-controller.xml223(replaceable) #: ./doc/install-guide/section_keystone-services.xml46(replaceable) #: ./doc/install-guide/section_keystone-services.xml47(replaceable) #: ./doc/install-guide/section_keystone-services.xml48(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml181(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml186(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml194(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml199(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml271(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml276(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml326(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml410(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml117(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml179(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml183(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml187(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml193(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml223(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml227(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml235(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml322(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml326(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml330(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml336(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml378(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml379(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml193(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml212(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml229(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml234(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml284(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml287(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml291(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml301(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml332(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml337(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml346(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml365(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml424(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml449(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml485(replaceable) #: ./doc/install-guide/section_cinder-node.xml110(replaceable) #: ./doc/install-guide/section_cinder-node.xml127(replaceable) #: ./doc/install-guide/section_cinder-node.xml164(replaceable) #: ./doc/install-guide/section_cinder-node.xml167(replaceable) #: ./doc/install-guide/section_cinder-controller.xml47(replaceable) #: ./doc/install-guide/section_cinder-controller.xml50(replaceable) #: ./doc/install-guide/section_cinder-controller.xml89(replaceable) #: ./doc/install-guide/section_cinder-controller.xml107(replaceable) #: ./doc/install-guide/section_cinder-controller.xml144(replaceable) #: ./doc/install-guide/section_cinder-controller.xml145(replaceable) #: ./doc/install-guide/section_cinder-controller.xml146(replaceable) #: ./doc/install-guide/section_cinder-controller.xml157(replaceable) #: ./doc/install-guide/section_cinder-controller.xml158(replaceable) #: ./doc/install-guide/section_cinder-controller.xml159(replaceable) #: ./doc/install-guide/section_neutron-install.xml160(replaceable) #: ./doc/install-guide/section_neutron-install.xml161(replaceable) #: ./doc/install-guide/section_neutron-install.xml162(replaceable) #: ./doc/install-guide/section_neutron-install.xml285(replaceable) #: ./doc/install-guide/section_neutron-install.xml325(replaceable) #: ./doc/install-guide/section_neutron-install.xml343(replaceable) #: ./doc/install-guide/section_neutron-install.xml351(replaceable) #: ./doc/install-guide/section_neutron-install.xml353(replaceable) #: ./doc/install-guide/section_neutron-install.xml367(replaceable) #: ./doc/install-guide/section_neutron-install.xml368(replaceable) #: ./doc/install-guide/section_neutron-install.xml841(replaceable) #: ./doc/install-guide/section_neutron-install.xml843(replaceable) #: ./doc/install-guide/section_neutron-install.xml868(replaceable) #: ./doc/install-guide/section_neutron-install.xml880(replaceable) #: ./doc/install-guide/section_neutron-install.xml909(replaceable) #: ./doc/install-guide/section_neutron-install.xml917(replaceable) #: ./doc/install-guide/section_neutron-install.xml928(replaceable) #: ./doc/install-guide/section_neutron-install.xml943(replaceable) #: ./doc/install-guide/section_neutron-install.xml953(replaceable) #: ./doc/install-guide/section_neutron-install.xml964(replaceable) #: ./doc/install-guide/section_neutron-install.xml969(replaceable) #: ./doc/install-guide/section_neutron-install.xml1070(replaceable) #: ./doc/install-guide/section_neutron-install.xml1220(replaceable) #: ./doc/install-guide/section_neutron-install.xml1235(replaceable) #: ./doc/install-guide/section_neutron-install.xml1237(replaceable) #: ./doc/install-guide/section_neutron-install.xml1264(replaceable) #: ./doc/install-guide/section_neutron-install.xml1270(replaceable) #: ./doc/install-guide/section_neutron-install.xml1271(replaceable) #: ./doc/install-guide/section_neutron-install.xml1295(replaceable) #: ./doc/install-guide/section_neutron-install.xml1319(replaceable) #: ./doc/install-guide/section_neutron-install.xml1338(replaceable) #: ./doc/install-guide/section_neutron-install.xml1362(replaceable) #: ./doc/install-guide/section_neutron-install.xml1372(replaceable) #: ./doc/install-guide/section_neutron-install.xml1383(replaceable) #: ./doc/install-guide/section_neutron-install.xml1388(replaceable) #: ./doc/install-guide/section_heat-install.xml113(replaceable) #: ./doc/install-guide/section_heat-install.xml118(replaceable) #: ./doc/install-guide/section_heat-install.xml119(replaceable) #: ./doc/install-guide/section_heat-install.xml134(replaceable) #: ./doc/install-guide/section_heat-install.xml135(replaceable) #: ./doc/install-guide/section_heat-install.xml136(replaceable) #: ./doc/install-guide/section_heat-install.xml145(replaceable) #: ./doc/install-guide/section_heat-install.xml146(replaceable) #: ./doc/install-guide/section_heat-install.xml147(replaceable) #: ./doc/install-guide/section_nova-compute.xml112(replaceable) #: ./doc/install-guide/section_nova-compute.xml135(replaceable) #: ./doc/install-guide/section_nova-compute.xml158(replaceable) #: ./doc/install-guide/section_nova-compute.xml170(replaceable) #: ./doc/install-guide/section_nova-compute.xml178(replaceable) #: ./doc/install-guide/section_nova-compute.xml181(replaceable) #: ./doc/install-guide/section_nova-compute.xml221(replaceable) #: ./doc/install-guide/section_glance-install.xml57(replaceable) #: ./doc/install-guide/section_glance-install.xml59(replaceable) #: ./doc/install-guide/section_glance-install.xml70(replaceable) #: ./doc/install-guide/section_glance-install.xml114(replaceable) #: ./doc/install-guide/section_glance-install.xml121(replaceable) #: ./doc/install-guide/section_glance-install.xml135(replaceable) #: ./doc/install-guide/section_glance-install.xml178(replaceable) #: ./doc/install-guide/section_glance-install.xml179(replaceable) #: ./doc/install-guide/section_glance-install.xml180(replaceable) #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml99(replaceable) #: ./doc/install-guide/object-storage/section_object-storage-install.xml104(replaceable) #: ./doc/install-guide/object-storage/section_object-storage-install.xml105(replaceable) #: ./doc/install-guide/object-storage/section_object-storage-install.xml106(replaceable) msgid "controller" msgstr "kontroler" #: ./doc/install-guide/section_ceilometer-install.xml71(para) msgid "" "Edit the /etc/ceilometer/ceilometer.conf file and " "change the [database] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml84(para) msgid "" "You must define an secret key that is used as a shared secret among " "Telemetry service nodes. Use to generate a random token and" " store it in the configuration file:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml91(para) msgid "For SUSE Linux Enterprise, run the following command:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml95(para) msgid "" "Edit the /etc/ceilometer/ceilometer.conf file and " "change the [publisher_rpc] section. Replace " "ADMIN_TOKEN with the results of the " "openssl command:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml104(replaceable) msgid "ADMIN_TOKEN" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml109(para) msgid "Configure the RabbitMQ access:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml111(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml114(replaceable) #: ./doc/install-guide/section_nova-controller.xml78(replaceable) #: ./doc/install-guide/section_nova-controller.xml86(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml182(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml195(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml272(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml327(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml114(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml180(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml191(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml323(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml334(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml17(replaceable) #: ./doc/install-guide/section_ceilometer-glance.xml22(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml207(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml230(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml333(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml360(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml425(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml444(replaceable) #: ./doc/install-guide/ch_basics.xml619(replaceable) #: ./doc/install-guide/section_cinder-node.xml130(replaceable) #: ./doc/install-guide/section_cinder-node.xml150(replaceable) #: ./doc/install-guide/section_cinder-controller.xml110(replaceable) #: ./doc/install-guide/section_cinder-controller.xml130(replaceable) #: ./doc/install-guide/section_neutron-install.xml309(replaceable) #: ./doc/install-guide/section_neutron-install.xml318(replaceable) #: ./doc/install-guide/section_neutron-install.xml861(replaceable) #: ./doc/install-guide/section_neutron-install.xml891(replaceable) #: ./doc/install-guide/section_neutron-install.xml1312(replaceable) #: ./doc/install-guide/section_neutron-install.xml1339(replaceable) #: ./doc/install-guide/section_heat-install.xml91(replaceable) #: ./doc/install-guide/section_heat-install.xml94(replaceable) #: ./doc/install-guide/section_nova-compute.xml142(replaceable) #: ./doc/install-guide/section_nova-compute.xml148(replaceable) msgid "RABBIT_PASS" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml112(para) msgid "" "Edit the /etc/ceilometer/ceilometer.conf file and " "update the [DEFAULT] section." msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml118(para) msgid "Configure collector dispatcher" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml124(para) msgid "" "Create a ceilometer user that the Telemetry service uses " "to authenticate with the Identity Service. Use the " "service tenant and give the user the " "admin role:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml128(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml143(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml149(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml160(replaceable) #: ./doc/install-guide/section_ceilometer-install.xml166(replaceable) msgid "CEILOMETER_PASS" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml128(replaceable) msgid "ceilometer@example.com" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml132(para) msgid "" "Add the credentials to the configuration files for the Telemetry service:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml150(para) msgid "" "Edit the /etc/ceilometer/ceilometer.conf file and " "change the [keystone_authtoken] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml161(para) msgid "Also set the [service_credentials] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml169(para) msgid "" "Register the Telemetry service with the Identity Service so that other " "OpenStack services can locate it. Use the command to " "register the service and specify the endpoint:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml177(para) msgid "" "Note the id property that is returned for the service. " "Use it when you create the endpoint:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml180(replaceable) #: ./doc/install-guide/section_nova-controller.xml220(replaceable) #: ./doc/install-guide/section_keystone-services.xml45(replaceable) #: ./doc/install-guide/section_cinder-controller.xml143(replaceable) #: ./doc/install-guide/section_cinder-controller.xml156(replaceable) #: ./doc/install-guide/section_neutron-install.xml159(replaceable) #: ./doc/install-guide/section_heat-install.xml133(replaceable) #: ./doc/install-guide/section_heat-install.xml144(replaceable) #: ./doc/install-guide/section_glance-install.xml177(replaceable) #: ./doc/install-guide/object-storage/section_object-storage-install.xml103(replaceable) msgid "the_service_id_above" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml186(para) msgid "Restart the services with their new settings:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml191(para) msgid "" "If log files are not generated for each service automatically, you should " "edit the /etc/ceilometer/ceilometer.conf and change the" " [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-install.xml202(para) msgid "" "Start the openstack-ceilometer-" "api, openstack-ceilometer-agent-centralopenstack-ceilometer-" "central and openstack-ceilometer-" "collector services and configure them to start when the system " "boots:" msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml5(title) msgid "Verify the Telemetry Service installation" msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml6(para) msgid "" "To test the Telemetry Service installation, download an image from the Image" " Service, and use the Telemetry Service to display usage statistics." msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml11(para) msgid "" "Use the ceilometer meter-list command to test the access " "to the Telemetry Service:" msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml22(para) msgid "Download an image from the Image Service:" msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml26(para) msgid "" "Call the ceilometer meter-list command again to validate " "that the download has been detected and stored by the Telemetry Service:" msgstr "" #: ./doc/install-guide/section_ceilometer-verify.xml40(para) msgid "You can now get usage statistics for the various meters:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml5(title) msgid "Install Compute controller services" msgstr "" #: ./doc/install-guide/section_nova-controller.xml6(para) msgid "" "Compute is a collection of services that enable you to launch virtual " "machine instances. You can configure these services to run on separate nodes" " or the same node. In this guide, most services run on the controller node " "and the service that launches virtual machines runs on a dedicated compute " "node. This section shows you how to install and configure these services on " "the controller node." msgstr "" #: ./doc/install-guide/section_nova-controller.xml15(para) msgid "" "Install the openstack-nova meta-package, which installs " "various Compute packages that are used on the controller node." msgstr "" #: ./doc/install-guide/section_nova-controller.xml20(para) msgid "" "Install these Compute packages, which provide the Compute services that run " "on the controller node." msgstr "" #: ./doc/install-guide/section_nova-controller.xml38(para) msgid "" "Respond to the prompts for database management, [keystone_authtoken] " "settings, RabbitMQ " "credentials, and API " "endpoint registration. The command runs " "automatically." msgstr "" #: ./doc/install-guide/section_nova-controller.xml49(para) msgid "" "Compute stores information in a database. In this guide, we use a MySQL " "database on the controller node. Configure Compute with the database " "location and credentials. Replace NOVA_DBPASS " "with the password for the database that you will create in a later step." msgstr "" #: ./doc/install-guide/section_nova-controller.xml55(replaceable) #: ./doc/install-guide/section_nova-controller.xml61(replaceable) #: ./doc/install-guide/section_nova-controller.xml93(replaceable) #: ./doc/install-guide/section_nova-controller.xml107(replaceable) #: ./doc/install-guide/section_nova-controller.xml109(replaceable) #: ./doc/install-guide/section_nova-compute.xml110(replaceable) msgid "NOVA_DBPASS" msgstr "HASŁO_NOVADB" #: ./doc/install-guide/section_nova-controller.xml56(para) msgid "" "Edit the [database] section in the " "/etc/nova/nova.conf file to modify this key:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml65(para) msgid "" "Set these configuration keys to configure Compute to use the Qpid message " "broker:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml72(para) #: ./doc/install-guide/section_nova-compute.xml136(para) msgid "" "Configure the Compute Service to use the RabbitMQ message broker by setting " "these configuration keys in the [DEFAULT] configuration " "group of the /etc/nova/nova.conf file:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml81(para) msgid "" "Set these configuration keys to configure Compute to use the RabbitMQ " "message broker:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml90(para) msgid "" "Run the command to create the Compute service database and " "tables and a nova database user." msgstr "" #: ./doc/install-guide/section_nova-controller.xml96(para) msgid "" "By default, the Ubuntu packages create an SQLite database. Delete the " "nova.sqlite file created in the " "/var/lib/nova/ directory so that it does not get used " "by mistake." msgstr "" #: ./doc/install-guide/section_nova-controller.xml102(para) msgid "" "Use the password you created previously to log in as root. Create a " "nova database user:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml112(para) msgid "Create the Compute service tables:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml116(para) msgid "" "Set the , , and " " configuration options to the " "internal IP address of the controller node:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml124(para) #: ./doc/install-guide/section_nova-network.xml62(para) msgid "" "Edit the /etc/nova/nova.conf file and add these lines " "to the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml127(para) msgid "" "In Debian, the debconf package automatically sets up " "my_ip parameter but you must edit the " "/etc/nova/nova.conf file to configure the " " and " " options, which appear at the " "end of the file:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml142(para) msgid "" "Create a nova user that Compute uses to authenticate with" " the Identity Service. Use the service tenant and give " "the user the admin role:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml146(replaceable) #: ./doc/install-guide/section_nova-controller.xml159(replaceable) #: ./doc/install-guide/section_nova-controller.xml178(replaceable) #: ./doc/install-guide/section_nova-controller.xml200(replaceable) #: ./doc/install-guide/section_nova-compute.xml117(replaceable) #: ./doc/install-guide/section_nova-compute.xml226(replaceable) msgid "NOVA_PASS" msgstr "" #: ./doc/install-guide/section_nova-controller.xml146(replaceable) msgid "nova@example.com" msgstr "nova@example.com" #: ./doc/install-guide/section_nova-controller.xml150(para) msgid "" "Configure Compute to use these credentials with the Identity Service running" " on the controller. Replace NOVA_PASS with your " "Compute password." msgstr "" #: ./doc/install-guide/section_nova-controller.xml160(para) msgid "" "Edit the [DEFAULT] section in the " "/etc/nova/nova.conf file to add this key:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml168(para) msgid "Add these keys to the [keystone_authtoken] section:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml182(para) msgid "" "Add the credentials to the /etc/nova/api-paste.ini " "file. Add these options to the [filter:authtoken] " "section:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml187(title) #: ./doc/install-guide/section_nova-compute.xml214(title) msgid "Use of .ini files" msgstr "" #: ./doc/install-guide/section_nova-controller.xml188(para) msgid "" "You might sometimes have to edit .ini files during " "initial setup. However, do not edit these files for general configuration " "tasks." msgstr "" #: ./doc/install-guide/section_nova-controller.xml202(para) msgid "" "Ensure that the " "option is set in the /etc/nova/nova.conf file." msgstr "" #: ./doc/install-guide/section_nova-controller.xml209(para) msgid "" "You must register Compute with the Identity Service so that other OpenStack " "services can locate it. Register the service and specify the endpoint:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml217(para) msgid "" "Use the id property that is returned to create the " "endpoint." msgstr "" #: ./doc/install-guide/section_nova-controller.xml226(para) msgid "" "Start Compute services and configure them to start when the system boots:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml229(para) msgid "Restart Compute services:" msgstr "" #: ./doc/install-guide/section_nova-controller.xml250(para) msgid "To verify your configuration, list available images:" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml6(title) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml7(title) msgid "System requirements" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml7(para) msgid "" "Before you install the OpenStack dashboard, you must meet the following " "system requirements:" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml11(para) msgid "" "OpenStack Compute installation. Enable the Identity Service for user and " "project management." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml13(para) msgid "Note the URLs of the Identity Service and Compute endpoints." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml17(para) msgid "" "Identity Service user with sudo privileges. Because Apache does not serve " "content from a root user, users must run the dashboard as an Identity " "Service user with sudo privileges." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml23(para) msgid "" "Python 2.6 or 2.7. The Python version must support Django. The Python " "version should run on any system, including Mac OS X. Installation " "prerequisites might differ by platform." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml29(para) msgid "" "Then, install and configure the dashboard on a node that can contact the " "Identity Service." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml31(para) msgid "" "Provide users with the following information so that they can access the " "dashboard through a web browser on their local machine:" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml36(para) msgid "The public IP address from which they can access the dashboard" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml40(para) msgid "The user name and password with which they can access the dashboard" msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml44(para) msgid "" "Your web browser, and that of your users, must support HTML5 and have " "cookies and JavaScript enabled." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml48(para) msgid "" "To use the VNC client with the dashboard, the browser must support HTML5 " "Canvas and HTML5 WebSockets." msgstr "" #: ./doc/install-guide/section_dashboard-system-reqs.xml50(para) msgid "" "For details about browsers that support noVNC, see https://github.com/kanaka/noVNC/blob/master/README.md," " and https://github.com/kanaka/noVNC/wiki/Browser-support, " "respectively." msgstr "" #: ./doc/install-guide/section_nova-boot.xml5(title) msgid "Launch an instance" msgstr "" #: ./doc/install-guide/section_nova-boot.xml6(para) msgid "" "After you configure the Compute services, you can launch an instance. An " "instance is a virtual machine that OpenStack provisions on a Compute server." " This example shows you how to launch a low-resource instance by using a " "downloaded image." msgstr "" #: ./doc/install-guide/section_nova-boot.xml12(para) msgid "This procedure assumes you have:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml15(para) msgid "" "Installed the nova client library on the machine on which you will run the " "commands (log on the controller if you are not sure)." msgstr "" #: ./doc/install-guide/section_nova-boot.xml20(para) msgid "" "Set environment variables to specify your credentials. See ." msgstr "" #: ./doc/install-guide/section_nova-boot.xml24(para) msgid "Downloaded an image. See ." msgstr "" #: ./doc/install-guide/section_nova-boot.xml28(para) msgid "Configured networking. See ." msgstr "" #: ./doc/install-guide/section_nova-boot.xml35(para) msgid "" "Generate a keypair that consists of a private and public key to be able to " "launch instances on OpenStack. These keys are injected into the instances to" " make password-less SSH access to the instance. This depends on the way the " "necessary tools are bundled into the images. For more details, see the OpenStack Admin User " "Guide." msgstr "" #: ./doc/install-guide/section_nova-boot.xml47(para) msgid "" "You have just created the mykey keypair. The " "id_rsa private key is saved locally in " "~/.ssh, which you can use to connect to an instance " "launched by using mykey as the keypair. To view available keypairs:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml60(para) msgid "" "To launch an instance, you must specify the ID for the flavor you want to " "use for the instance. A flavor is a resource allocation profile. For " "example, it specifies how many virtual CPUs and how much RAM your instance " "gets. To see a list of the available profiles:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml77(para) msgid "Get the ID of the image to use for the instance:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml86(para) msgid "" "To use SSH and ping, you must configure security group rules. See the OpenStack " "User Guide." msgstr "" #: ./doc/install-guide/section_nova-boot.xml91(replaceable) #: ./doc/install-guide/section_nova-boot.xml92(replaceable) msgid "default" msgstr "" #: ./doc/install-guide/section_nova-boot.xml95(para) msgid "Launch the instance:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml96(replaceable) msgid "flavorType" msgstr "" #: ./doc/install-guide/section_nova-boot.xml96(replaceable) msgid "keypairName" msgstr "" #: ./doc/install-guide/section_nova-boot.xml96(replaceable) #: ./doc/install-guide/app_reserved_uids.xml29(th) msgid "ID" msgstr "ID" #: ./doc/install-guide/section_nova-boot.xml96(replaceable) msgid "newInstanceName" msgstr "" #: ./doc/install-guide/section_nova-boot.xml97(para) msgid "Create an instance by using flavor 1 or 2. For example:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml134(para) msgid "" "If sufficient RAM is not available for the instance, Compute creates, but " "does not start, the instance and sets the status for the instance to " "ERROR." msgstr "" #: ./doc/install-guide/section_nova-boot.xml141(para) msgid "" "After the instance launches, use the to view its status. " "The status changes from BUILD to " "ACTIVE:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml159(para) msgid "To show details for a specified instance:" msgstr "" #: ./doc/install-guide/section_nova-boot.xml197(para) msgid "" "After the instance boots and initializes and you have configured security " "groups, you can into the instance without a password by " "using the keypair you specified in the command. Use the " " command to get the IP address for the instance. You do not " "need to specify the private key because it was stored in the default " "location, ~/.ssh/.id_rsa, for the " "client." msgstr "" #: ./doc/install-guide/section_nova-boot.xml207(para) msgid "" "If using a CirrOS image to spawn an instance you must log in as the " "cirros, and not the root, user." msgstr "" #: ./doc/install-guide/section_nova-boot.xml210(para) msgid "" "You can also log in to the cirros account without an ssh " "key by using the cubswin:) password:" msgstr "" #: ./doc/install-guide/section_keystone-services.xml4(title) msgid "Define services and API endpoints" msgstr "" #: ./doc/install-guide/section_keystone-services.xml5(para) msgid "" "So that the Identity Service can track which OpenStack services are " "installed and where they are located on the network, you must register each " "service in your OpenStack installation. To register a service, run these " "commands:" msgstr "" #: ./doc/install-guide/section_keystone-services.xml11(para) msgid ". Describes the service." msgstr "" #: ./doc/install-guide/section_keystone-services.xml15(para) msgid ". Associates API endpoints with the service." msgstr "" #: ./doc/install-guide/section_keystone-services.xml19(para) msgid "" "You must also register the Identity Service itself. Use the " "OS_SERVICE_TOKEN environment variable, as set previously, for " "authentication." msgstr "" #: ./doc/install-guide/section_keystone-services.xml24(para) msgid "Create a service entry for the Identity Service:" msgstr "" #: ./doc/install-guide/section_keystone-services.xml35(para) #: ./doc/install-guide/object-storage/section_object-storage-install.xml93(para) msgid "" "The service ID is randomly generated and is different from the one shown " "here." msgstr "" #: ./doc/install-guide/section_keystone-services.xml39(para) msgid "" "Specify an API endpoint for the Identity Service by using the returned " "service ID. When you specify an endpoint, you provide URLs for the public " "API, internal API, and admin API. In this guide, the " "controller host name is used. Note that the Identity " "Service uses a different port for the admin API." msgstr "" #: ./doc/install-guide/section_keystone-services.xml62(para) msgid "" "You will need to create an additional endpoint for each service added to " "your OpenStack environment. The sections of this guide associated with the " "installation of each service include the endpoint creation step specific to " "the service." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml6(title) msgid "Verify the Identity Service installation" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml9(para) msgid "" "To verify that the Identity Service is installed and configured correctly, " "clear the values in the OS_SERVICE_TOKEN and " "OS_SERVICE_ENDPOINT environment variables:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml15(para) msgid "" "These variables, which were used to bootstrap the administrative user and " "register the Identity Service, are no longer needed." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml20(para) msgid "You can now use regular user name-based authentication." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml22(para) msgid "" "Request a authentication token by using the admin user " "and the password you chose for that user:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml27(para) msgid "" "In response, you receive a token paired with your user ID. This verifies " "that the Identity Service is running on the expected endpoint and that your " "user account is established with the expected credentials." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml33(para) msgid "" "Verify that authorization behaves as expected. To do so, request " "authorization on a tenant:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml37(para) msgid "" "In response, you receive a token that includes the ID of the tenant that you" " specified. This verifies that your user account has an explicitly defined " "role on the specified tenant and the tenant exists as expected." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml43(para) msgid "" "You can also set your --os-* variables in your " "environment to simplify command-line usage. Set up a " "openrc.sh file with the admin credentials and admin " "endpoint:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml53(para) msgid "Source this file to read in the environment variables:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml58(para) msgid "" "Verify that your openrc.sh file is configured " "correctly. Run the same command without the --os-* " "arguments:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml62(para) msgid "" "The command returns a token and the ID of the specified tenant. This " "verifies that you have configured your environment variables correctly." msgstr "Polecenie zwraca token oraz ID podanego projektu. Pozwala to na sprawdzenie czy zmienne środowiskowe zostały poprawnie skonfigurowane." #: ./doc/install-guide/section_keystone-verify.xml67(para) msgid "" "Verify that your admin account has authorization to perform administrative " "commands:" msgstr "" #: ./doc/install-guide/section_keystone-verify.xml75(para) msgid "" "This verifies that your user account has the admin role, " "which matches the role used in the Identity Service " "policy.json file." msgstr "" #: ./doc/install-guide/section_keystone-verify.xml80(para) msgid "" "As long as you define your credentials and the Identity Service endpoint " "through the command line or environment variables, you can run all OpenStack" " client commands from any machine. For details, see ." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml15(None) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml863(None) msgid "" "@@image: '../common/figures/UseCase-MultiRouter.png'; " "md5=5695d4b003e2f8442eab135cbcd1f842" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml25(None) msgid "" "@@image: '../common/figures/demo_routers_with_private_networks.png'; " "md5=985b8cacfd7161ce50ee13106b27f854" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml6(title) msgid "Per-tenant routers with private networks" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml7(para) msgid "" "This section describes how to install the OpenStack Networking service and " "its components for a use case that has per-tenant routers with private " "networks." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml19(para) msgid "The following figure shows the setup:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml29(para) msgid "As shown in the figure, the setup includes:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml32(para) msgid "An interface for management traffic on each node." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml36(para) msgid "Use of the Open vSwitch plug-in." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml39(para) msgid "GRE tunnels for data transport on all agents." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml42(para) msgid "" "Floating IPs and router gateway ports that are configured in an external " "network, and a physical router that connects the floating IPs and router " "gateway ports to the outside world." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml49(para) msgid "" "Because this example runs a DHCP agent and L3 agent on one node, you must " "set the use_namespace option to True " "in the configuration file for each agent. The default is " "True." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml55(para) msgid "This table describes the nodes:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml61(th) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml31(th) #: ./doc/install-guide/section_neutron-single-flat.xml32(th) msgid "Node" msgstr "Węzeł" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml62(th) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml32(th) #: ./doc/install-guide/app_reserved_uids.xml28(th) #: ./doc/install-guide/section_neutron-single-flat.xml33(th) msgid "Description" msgstr "Opis" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml67(td) #: ./doc/install-guide/section_neutron-single-flat.xml38(td) msgid "Controller Node" msgstr "Węzeł kontrolera" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml68(para) msgid "" "Runs Networking, Identity Service, and all Compute services that are " "required to deploy VMs (nova-api," " nova-scheduler, for example). " "The node must have at least one network interface, which connects to the " "Management Network. The host name is controlnode, which " "other nodes resolve to the IP of the controller node." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml80(para) msgid "" "The nova-network service should " "not be running. This is replaced by Networking." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml87(td) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml282(title) #: ./doc/install-guide/section_neutron-single-flat.xml70(td) msgid "Compute Node" msgstr "Węzeł obliczeniowy" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml90(systemitem) #: ./doc/install-guide/section_neutron-single-flat.xml73(systemitem) msgid "nova-compute" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml92(systemitem) msgid "nova-*" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml88(td) msgid "" "Runs the Networking L2 agent and the Compute services that run VMs " "( specifically, and optionally other " "services depending on configuration). The node must have at least two " "network interfaces. One interface communicates with the controller node " "through the management network. The other node is used for the VM traffic on" " the data network. The VM receives its IP address from the DHCP agent on " "this network." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml101(td) #: ./doc/install-guide/section_neutron-single-flat.xml84(td) msgid "Network Node" msgstr "Węzeł sieciowy" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml102(td) msgid "" "Runs Networking L2 agent, DHCP agent and L3 agent. This node has access to " "the external network. The DHCP agent allocates IP addresses to the VMs on " "data network. (Technically, the addresses are allocated by the Networking " "server, and distributed by the dhcp agent.) The node must have at least two " "network interfaces. One interface communicates with the controller node " "through the management network. The other interface is used as external " "network. GRE tunnels are set up as data networks." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml115(td) #: ./doc/install-guide/section_neutron-single-flat.xml94(td) msgid "Router" msgstr "Router" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml116(td) #: ./doc/install-guide/section_neutron-single-flat.xml95(td) msgid "" "Router has IP 30.0.0.1, which is the default gateway for all VMs. The router" " must be able to access public networks." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml122(para) msgid "The use case assumes the following:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml123(emphasis) #: ./doc/install-guide/section_neutron-single-flat.xml102(emphasis) msgid "Controller node" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml126(para) #: ./doc/install-guide/section_neutron-single-flat.xml105(para) msgid "Relevant Compute services are installed, configured, and running." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml130(para) msgid "" "Glance is installed, configured, and running. In addition, an image named " "tty must be present." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml135(para) msgid "" "Identity is installed, configured, and running. A Networking user named " "neutron should be created on tenant " "service with password " "NEUTRON_PASS." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml145(para) msgid "" "RabbitMQ is running with default guest and password " "RABBIT_PASS." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml150(para) #: ./doc/install-guide/section_neutron-single-flat.xml133(para) msgid "MySQL server (user is root)." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml143(para) msgid "Additional services: " msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml156(emphasis) #: ./doc/install-guide/section_neutron-single-flat.xml139(emphasis) msgid "Compute node" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml157(para) msgid "Install and configure Compute." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml159(title) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml92(title) #: ./doc/install-guide/section_neutron-single-flat.xml146(title) msgid "Install" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml162(emphasis) #: ./doc/install-guide/section_neutron-single-flat.xml149(emphasis) msgid "Controller node - Networking server" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml166(para) #: ./doc/install-guide/section_neutron-single-flat.xml154(para) msgid "Install the Networking server." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml169(para) #: ./doc/install-guide/section_neutron-single-flat.xml168(para) msgid "Create database ovs_neutron." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml173(para) msgid "" "Update the Networking configuration file, " "/etc/neutron/neutron.conf, with plug-in choice and Identity " "Service user as necessary:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml186(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml199(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml276(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml117(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml183(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml187(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml193(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml326(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml330(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml336(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml193(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml234(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml337(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml346(replaceable) #: ./doc/install-guide/section_neutron-install.xml141(replaceable) #: ./doc/install-guide/section_neutron-install.xml143(replaceable) #: ./doc/install-guide/section_neutron-install.xml336(replaceable) #: ./doc/install-guide/section_neutron-install.xml343(replaceable) #: ./doc/install-guide/section_neutron-install.xml902(replaceable) #: ./doc/install-guide/section_neutron-install.xml909(replaceable) #: ./doc/install-guide/section_neutron-install.xml1210(replaceable) #: ./doc/install-guide/section_neutron-install.xml1220(replaceable) msgid "NEUTRON_DBPASS" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml191(replaceable) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml236(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml133(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml226(replaceable) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml238(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml190(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml239(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml283(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml299(replaceable) #: ./doc/install-guide/section_neutron-install.xml149(replaceable) #: ./doc/install-guide/section_neutron-install.xml268(replaceable) #: ./doc/install-guide/section_neutron-install.xml290(replaceable) #: ./doc/install-guide/section_neutron-install.xml359(replaceable) #: ./doc/install-guide/section_neutron-install.xml371(replaceable) #: ./doc/install-guide/section_neutron-install.xml441(replaceable) #: ./doc/install-guide/section_neutron-install.xml455(replaceable) #: ./doc/install-guide/section_neutron-install.xml849(replaceable) #: ./doc/install-guide/section_neutron-install.xml883(replaceable) #: ./doc/install-guide/section_neutron-install.xml920(replaceable) #: ./doc/install-guide/section_neutron-install.xml934(replaceable) #: ./doc/install-guide/section_neutron-install.xml951(replaceable) #: ./doc/install-guide/section_neutron-install.xml968(replaceable) #: ./doc/install-guide/section_neutron-install.xml1243(replaceable) #: ./doc/install-guide/section_neutron-install.xml1269(replaceable) #: ./doc/install-guide/section_neutron-install.xml1285(replaceable) #: ./doc/install-guide/section_neutron-install.xml1301(replaceable) #: ./doc/install-guide/section_neutron-install.xml1370(replaceable) #: ./doc/install-guide/section_neutron-install.xml1387(replaceable) msgid "NEUTRON_PASS" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml202(para) msgid "" "Update the plug-in configuration file, " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml210(para) msgid "Start the Networking server." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml211(para) msgid "" "The Networking server can be a service of the operating system. The command " "to start the service depends on your operating system. The following command" " runs the Networking server directly:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml223(emphasis) msgid "Compute node—Compute" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml225(para) msgid "Install Compute services." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml228(para) msgid "" "Update the Compute /etc/nova/nova.conf configuration " "file. Make sure the following line appears at the end of this file:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml243(para) msgid "Restart relevant Compute services." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml249(emphasis) msgid "Compute and Networking node—L2 agent" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml253(para) msgid "Install and start Open vSwitch." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml256(para) msgid "Install the L2 agent (Neutron Open vSwitch agent)." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml260(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml170(para) msgid "Add the integration bridge to the Open vSwitch:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml265(para) msgid "" "Update the Networking configuration file, " "/etc/neutron/neutron.conf:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml279(para) msgid "" "Update the plug-in configuration file, " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml282(para) msgid "Compute node:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml288(para) msgid "Network node:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml296(para) msgid "Create the integration bridge br-int:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml301(para) msgid "Start the Networking L2 agent" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml302(para) msgid "" "The Networking Open vSwitch L2 agent can be a service of operating system. " "The command to start depends on your operating systems. The following " "command runs the service directly:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml313(emphasis) msgid "Network node—DHCP agent" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml317(para) #: ./doc/install-guide/section_neutron-single-flat.xml412(para) msgid "Install the DHCP agent." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml320(para) msgid "" "Update the Networking configuration file, " "/etc/neutron/neutron.conf" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml331(literal) msgid "allow_overlapping_ips" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml330(emphasis) msgid "" "Set because TenantA and TenantC use overlapping subnets." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml336(para) msgid "" "Update the DHCP /etc/neutron/dhcp_agent.ini " "configuration file:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml342(para) msgid "Start the DHCP agent." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml343(para) msgid "" "The Networking DHCP agent can be a service of operating system. The command " "to start the service depends on your operating system. The following command" " runs the service directly:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml354(emphasis) msgid "Network node—L3 agent" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml358(para) msgid "Install the L3 agent." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml361(para) msgid "Add the external network bridge" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml365(para) msgid "" "Add the physical interface, for example eth0, that is connected to the " "outside network to this bridge:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml371(para) msgid "" "Update the L3 configuration file " "/etc/neutron/l3_agent.ini:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml378(literal) msgid "use_namespaces" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml377(emphasis) msgid "" "Set the option (it is True by default) because TenantA and " "TenantC have overlapping subnets, and the routers are hosted on one l3 agent" " network node." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml386(para) msgid "Start the L3 agent" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml387(para) msgid "" "The Networking L3 agent can be a service of operating system. The command to" " start the service depends on your operating system. The following command " "starts the agent directly:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml401(title) #: ./doc/install-guide/section_neutron-single-flat.xml475(title) msgid "Configure logical network" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml402(para) msgid "You can run these commands on the network node." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml404(para) msgid "" "Ensure that the following environment variables are set. Various clients use" " these to access the Identity Service." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml414(para) #: ./doc/install-guide/section_neutron-single-flat.xml488(para) msgid "Get the tenant ID (Used as $TENANT_ID later):" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml428(para) msgid "Get user information:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml441(para) msgid "Create the external network and its subnet by admin user:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml479(literal) msgid "provider:network_type local" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml482(literal) msgid "router:external true" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml478(emphasis) msgid "" " means that Networking does not have to realize this network" " through provider network. means that an external network " "is created where you can create floating IP and router gateway port." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml488(para) msgid "Add an IP on external network to br-ex." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml489(para) msgid "" "Because br-ex is the external network bridge, add an IP 30.0.0.100/24 to br-" "ex and ping the floating IP of the VM from our network node." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml497(para) msgid "Serve TenantA." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml498(para) msgid "" "For TenantA, create a private network, subnet, server, router, and floating " "IP." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml502(para) msgid "Create a network for TenantA:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml518(para) msgid "" "After that, you can use admin user to query the provider network " "information:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml537(para) msgid "" "The network has GRE tunnel ID (for example, provider:segmentation_id) 1." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml542(para) msgid "Create a subnet on the network TenantA-Net:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml564(para) msgid "Create a server for TenantA:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml576(para) msgid "" "It is important to understand that you should not attach the instance to " "Ext-Net directly. Instead, you must use a floating IP to make it accessible " "from the external network." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml585(para) msgid "Create and configure a router for TenantA:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml603(para) msgid "Added interface to router TenantA-R1" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml612(para) msgid "Associate a floating IP for TenantA_VM1." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml616(para) msgid "Create a floating IP:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml633(para) msgid "" "Get the port ID of the VM with ID 7c5e6499-7ef7-4e36-8216-62c2941d21ff:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml645(para) msgid "Associate the floating IP with the VM port:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml663(para) msgid "Ping the public network from the server of TenantA." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml665(para) msgid "" "In my environment, 192.168.1.0/24 is my public network connected with my " "physical router, which also connects to the external network 30.0.0.0/24. " "With the floating IP and virtual router, you can ping the public network " "within the server of tenant A:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml683(para) msgid "Ping floating IP of the TenantA's server:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml696(para) msgid "Create other servers for TenantA." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml697(para) msgid "You can create more servers for TenantA and add floating IPs for them." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml701(para) msgid "Serve TenantC." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml702(para) msgid "" "For TenantC, you create two private networks with subnet 10.0.0.0/24 and " "subnet 10.0.1.0/24, some servers, one router to connect to these two subnets" " and some floating IPs." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml708(para) msgid "Create networks and subnets for TenantC:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml721(para) msgid "" "After that you can use admin user to query the network's provider network " "information:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml757(para) msgid "" "You can see GRE tunnel IDs (such as, provider:segmentation_id) 2 and 3. And " "also note the network IDs and subnet IDs because you use them to create VMs " "and router." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml764(para) msgid "Create a server TenantC-VM1 for TenantC on TenantC-Net1." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml771(para) msgid "Create a server TenantC-VM3 for TenantC on TenantC-Net2." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml778(para) msgid "List servers of TenantC." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml787(para) msgid "Note the server IDs because you use them later." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml791(para) msgid "Make sure servers get their IPs." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml792(para) msgid "" "You can use VNC to log on the VMs to check if they get IPs. If not, you must" " make sure that the Networking components are running correctly and the GRE " "tunnels work." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml799(para) msgid "Create and configure a router for TenantC:" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml814(para) msgid "Checkpoint: ping from within TenantC's servers." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml816(para) msgid "" "Because a router connects to two subnets, the VMs on these subnets can ping " "each other. And because the gateway for the router is set, TenantC's servers" " can ping external network IPs, such as 192.168.1.1, 30.0.0.1, and so on." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml824(para) #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml835(para) msgid "Associate floating IPs for TenantC's servers." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml826(para) msgid "" "Because a router connects to two subnets, the VMs on these subnets can ping " "each other. And because the gateway interface for the router is set, " "TenantC's servers can ping external network IPs, such as 192.168.1.1, " "30.0.0.1, and so on." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml837(para) msgid "" "You can use similar commands to the ones used in the section for TenantA." msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml845(title) msgid "Use case: per-tenant routers with private networks" msgstr "" #: ./doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml847(para) msgid "" "This use case represents a more advanced router scenario in which each " "tenant gets at least one router, and potentially has access to the " "Networking API to create additional routers. The tenant can create their own" " networks, potentially uplinking those networks to a router. This model " "enables tenant-defined, multi-tier applications, with each tier being a " "separate network behind the router. Because there are multiple routers, " "tenant subnets can overlap without conflicting, because access to external " "networks all happens through SNAT or floating IPs. Each router uplink and " "floating IP is allocated from the external network subnet." msgstr "" #: ./doc/install-guide/ch_horizon.xml6(title) msgid "Add the dashboard" msgstr "" #: ./doc/install-guide/ch_horizon.xml7(para) msgid "" "The OpenStack dashboard, also known as Horizon, is a Web " "interface that enables cloud administrators and users to manage various " "OpenStack resources and services." msgstr "" #: ./doc/install-guide/ch_horizon.xml12(para) msgid "" "The dashboard enables web-based interactions with the OpenStack Compute " "cloud controller through the OpenStack APIs." msgstr "" #: ./doc/install-guide/ch_horizon.xml15(para) msgid "" "These instructions show an example deployment configured with an Apache web " "server." msgstr "" #: ./doc/install-guide/ch_horizon.xml17(para) msgid "" "After you install and configure the " "dashboard, you can complete the following tasks:" msgstr "" #: ./doc/install-guide/ch_horizon.xml22(para) msgid "" "Customize your dashboard. See section Customize the dashboard in the OpenStack Cloud Administrator " "Guide." msgstr "" #: ./doc/install-guide/ch_horizon.xml30(para) msgid "" "Set up session storage for the dashboard. See ." msgstr "" #: ./doc/install-guide/section_heat-verify.xml6(title) msgid "Verify the Orchestration service installation" msgstr "" #: ./doc/install-guide/section_heat-verify.xml8(para) msgid "" "To verify that the Orchestration service is installed and configured " "correctly, make sure that your credentials are set up correctly in the " "openrc.sh file. Source the file, as follows:" msgstr "" #: ./doc/install-guide/section_heat-verify.xml14(para) msgid "Next, create some stacks by using the samples." msgstr "" #: ./doc/install-guide/ch_ceilometer.xml6(title) msgid "Add the Telemetry service" msgstr "" #: ./doc/install-guide/ch_ceilometer.xml8(para) msgid "" "The OpenStack Telemetry service provides a framework for monitoring and " "metering the OpenStack cloud. It is also known as the Ceilometer project." msgstr "" #: ./doc/install-guide/ch_keystone.xml6(title) msgid "Configure the Identity Service" msgstr "" #: ./doc/install-guide/ch_heat.xml6(title) msgid "Add the Orchestration service" msgstr "" #: ./doc/install-guide/ch_heat.xml7(para) msgid "" "Use the OpenStack Orchestration service to create cloud resources using a " "template language called HOT. The integrated project name is Heat." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-rabbitqm.xml15(None) msgid "" "@@image: 'figures/debconf-screenshots/rabbitmq-host.png'; " "md5=5353ad857884a2d31847cf82efbdc6b6" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-rabbitqm.xml22(None) msgid "" "@@image: 'figures/debconf-screenshots/rabbitmq-user.png'; " "md5=33a3c1182e79ed65f1b1b63f2156792c" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-rabbitqm.xml29(None) msgid "" "@@image: 'figures/debconf-screenshots/rabbitmq-password.png'; " "md5=6385185200d20e96b6316ae15ae1255d" msgstr "" #: ./doc/install-guide/section_debconf-rabbitqm.xml6(title) msgid "RabbitMQ credentials parameters" msgstr "" #: ./doc/install-guide/section_debconf-rabbitqm.xml7(para) msgid "" "For every package that must connect to a Messaging Server, the Debian " "package enables you to configure the IP address for that server and the user" " name and password that is used to connect. The following example shows " "configuration with the ceilometer-" "common package:" msgstr "" #: ./doc/install-guide/section_debconf-rabbitqm.xml33(para) msgid "" "These debconf screens appear in: ceilometer-" "common, cinder-" "common, glance-" "common, heat-common," " neutron-common and nova-common." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml16(None) #: ./doc/install-guide/ch_overview.xml95(None) msgid "" "@@image: '../common/figures/Neutron-PhysNet-Diagram.png'; " "md5=ac17dba8837f9d7ba714a692c60e68ab" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml651(None) msgid "" "@@image: '../common/figures/UseCase-SingleRouter.png'; " "md5=63d21d52d32ed7fa1c1dad1a1fd88eb5" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml6(title) msgid "Provider router with private networks" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml7(para) msgid "" "This section describes how to install the OpenStack Networking service and " "its components for a single router use case: a provider router with private " "networks." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml10(para) msgid "This figure shows the set up:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml21(para) msgid "" "Because you run the DHCP agent and L3 agent on one node, you must set " "use_namespaces to True (which is the " "default) in the configuration files for both agents." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml26(para) msgid "The configuration includes these nodes:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml28(caption) msgid "Nodes for use case" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml37(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml94(title) msgid "Controller" msgstr "Kontroler" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml38(para) msgid "" "Runs the Networking service, Identity Service, and all Compute services that" " are required to deploy a VM." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml42(para) msgid "" "The service must have at least two network interfaces. The first should be " "connected to the Management Network to communicate with the compute and " "network nodes. The second interface should be connected to the API/public " "network." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml50(para) msgid "Compute" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml51(para) msgid "Runs Compute and the Networking L2 agent." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml53(para) msgid "This node does not have access the public network." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml55(para) msgid "" "The node must have a network interface that communicates with the controller" " node through the management network. The VM receives its IP address from " "the DHCP agent on this network." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml62(para) msgid "Network" msgstr "Sieć" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml63(para) msgid "Runs Networking L2 agent, DHCP agent, and L3 agent." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml65(para) msgid "" "This node has access to the public network. The DHCP agent allocates IP " "addresses to the VMs on the network. The L3 agent performs NAT and enables " "the VMs to access the public network." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml72(para) msgid "" "A network interface that communicates with the controller node through the " "management network" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml78(para) msgid "A network interface on the data network that manages VM traffic" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml83(para) msgid "" "A network interface that connects to the external gateway on the network" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml70(para) msgid "The node must have:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml96(title) msgid "To install and configure the controller node" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml99(para) #: ./doc/install-guide/section_nova-compute.xml56(para) msgid "Run this command:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml105(para) msgid "Configure Networking services:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml108(para) msgid "" "Edit the /etc/neutron/neutron.conf file and add these " "lines:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml120(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml339(para) msgid "" "Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini file and " "add these lines:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml128(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml231(para) msgid "" "Edit the /etc/neutron/api-paste.ini file and add these" " lines:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml138(para) msgid "Start the services:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml145(title) msgid "Network node" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml147(title) msgid "To install and configure the network node" msgstr "" #. FIXME Review Fedora instructions #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml150(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml289(para) msgid "Install the packages:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml159(para) msgid "" "Start Open vSwitch and " "configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml175(para) msgid "" "Update the OpenStack Networking " "/etc/neutron/neutron.conf configuration file:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml196(para) msgid "" "Update the plug-in " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " "configuration file:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml205(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml310(para) msgid "" "Create the br-eth1 network bridge. All VM communication " "between the nodes occurs through br-eth1:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml213(para) msgid "Create the external network bridge to the Open vSwitch:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml219(para) msgid "" "Edit the /etc/neutron/l3_agent.ini file and add these " "lines:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml241(para) msgid "" "Edit the /etc/neutron/dhcp_agent.ini file and add this" " line:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml247(para) msgid "Restart networking services:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml253(para) #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml353(para) msgid "Start and permanently enable networking services:" msgstr "" #. FIXME: Required on Debian/Ubuntu? #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml270(para) msgid "" "Enable the neutron-ovs-cleanup " "service. This service starts on boot and ensures that Networking has full " "control over the creation and management of tap devices." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml285(title) msgid "To install and configure the compute node" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml295(para) msgid "" "Start the OpenvSwitch service and configure it to start when the " "system boots:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml306(para) msgid "Create the integration bridge:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml318(para) msgid "" "Edit the OpenStack Networking " "/etc/neutron/neutron.conf configuration file and add this line:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml348(para) msgid "Restart the OpenvSwitch Neutron plug-in agent:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml364(title) msgid "Logical network configuration" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml366(para) msgid "Run these commands on the network node." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml367(para) #: ./doc/install-guide/section_neutron-single-flat.xml478(para) msgid "" "Ensure that the following environment variables are set. Various clients use" " these variables to access the Identity Service." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml373(para) msgid "Create a novarc file:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml386(para) msgid "Export the variables:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml390(para) msgid "" "The admin user creates a network and subnet on behalf of tenant_A. A " "tenant_A user can also complete these steps." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml394(title) msgid "To configure internal networking" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml396(para) msgid "Get the tenant ID (Used as $TENANT_ID later)." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml409(para) msgid "" "Create an internal network named net1 for" " tenant_A ($TENANT_ID will be e40fa60181524f9f9ee7aa1038748f08):" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml431(para) msgid "" "Create a subnet on the network net1 (ID " "field below is used as $SUBNET_ID later):" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml452(para) msgid "" "A user with the admin role must complete these steps. In this procedure, the" " user is admin from provider_tenant." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml456(title) msgid "To configure the router and external networking" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml459(para) msgid "" "Create a router1 route. The ID is used as" " $ROUTER_ID later:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml474(para) msgid "" "The --tenant-id parameter is not specified, so this " "router is assigned to the provider_tenant tenant." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml480(para) msgid "" "Add an interface to the router1 router and attach it to " "the subnet from net1:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml487(para) msgid "" "You can repeat this step to add more interfaces for other networks that " "belong to other tenants." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml493(para) msgid "Create the ext_net external network:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml513(para) msgid "Create the subnet for floating IPs." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml515(para) msgid "The DHCP service is disabled for this subnet." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml538(para) msgid "Set the gateway for the router to the external network:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml544(para) msgid "" "A user from tenant_A completes these steps, so the credentials in the " "environment variables are different than those in the previous procedure." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml548(title) msgid "To allocate floating IP addresses" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml550(para) msgid "" "You can associate a floating IP address with a VM after it starts. Find the " "ID of the port ($PORT_ID) that was allocated for the VM, as follows:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml569(para) msgid "Allocate a floating IP (Used as $FLOATING_ID):" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml585(para) msgid "Associate the floating IP with the port for the VM:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml591(para) msgid "Show the floating IP:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml606(para) msgid "Test the floating IP:" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml616(title) msgid "Use case: provider router with private networks" msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml617(para) msgid "" "This use case provides each tenant with one or more private networks that " "connect to the outside world through an OpenStack Networking router. When " "each tenant gets exactly one network, this architecture maps to the same " "logical topology as the VlanManager in Compute (although of course, " "Networking does not require VLANs). Using the Networking API, the tenant can" " only see a network for each private network assigned to that tenant. The " "router object in the API is created and owned by the cloud administrator." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml627(para) msgid "" "This model supports assigning public addresses to VMs by using floating IPs; the router maps public " "addresses from the external network to fixed IPs on private networks. Hosts " "without floating IPs can still create outbound connections to the external " "network because the provider router performs SNAT to the router's external " "IP. The IP address of the physical router is used as the " "gateway_ip of the external network subnet, so the " "provider has a default router for Internet traffic." msgstr "" #: ./doc/install-guide/section_neutron-provider-router-with-private_networks.xml638(para) msgid "" "The router provides L3 connectivity among private networks. Tenants can " "reach instances for other tenants unless you use additional filtering, such " "as, security groups). With a single router, tenant networks cannot use " "overlapping IPs. To resolve this issue, the administrator can create private" " networks on behalf of the tenants." msgstr "" #: ./doc/install-guide/ch_nova.xml7(title) msgid "Configure Compute services" msgstr "" #: ./doc/install-guide/section_ceilometer-cinder.xml7(title) msgid "Add the Block Storage Service agent for the Telemetry service" msgstr "" #: ./doc/install-guide/section_ceilometer-cinder.xml11(para) msgid "" "To retrieve volume samples, you must configure the Block Storage Service to " "send notifications to the bus." msgstr "" #: ./doc/install-guide/section_ceilometer-cinder.xml14(para) msgid "" "Edit /etc/cinder/cinder.conf and add in the " "[DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-cinder.xml19(para) #: ./doc/install-guide/section_ceilometer-glance.xml19(para) #: ./doc/install-guide/section_heat-install.xml92(para) msgid "Run the following commands:" msgstr "" #: ./doc/install-guide/section_ceilometer-cinder.xml25(para) msgid "Restart the Block Storage services with their new settings:" msgstr "" #: ./doc/install-guide/section_nova-network.xml5(title) msgid "Configure networking" msgstr "" #: ./doc/install-guide/section_nova-network.xml6(para) msgid "" "Configuring networking in OpenStack can be a bewildering experience. The " "following example shows the simplest production-ready configuration that is " "available: the legacy networking in OpenStack Compute, with a flat network, " "that takes care of DHCP." msgstr "" #: ./doc/install-guide/section_nova-network.xml11(para) msgid "" "This set up uses multi-host functionality. Networking is configured to be " "highly available by distributing networking functionality across multiple " "hosts. As a result, no single network controller acts as a single point of " "failure. This process configures each compute node for networking." msgstr "" #: ./doc/install-guide/section_nova-network.xml17(para) msgid "Choose one of these options to configure networking in OpenStack:" msgstr "" #: ./doc/install-guide/section_nova-network.xml20(para) msgid "Legacy networking in OpenStack Compute, which is described here." msgstr "" #: ./doc/install-guide/section_nova-network.xml24(para) msgid "" "The full software-defined networking stack. See ." msgstr "" #: ./doc/install-guide/section_nova-network.xml31(para) msgid "" "Install the appropriate packages for compute networking on the compute node " "only. These packages are not required on the controller node." msgstr "" #: ./doc/install-guide/section_nova-network.xml34(para) msgid "" "So that the nova-network service " "can forward metadata requests on each compute node, each compute node must " "install the nova-api-metadata " "service, as follows:" msgstr "" #: ./doc/install-guide/section_nova-network.xml44(para) msgid "" "Edit the nova.conf file to define the networking mode:" msgstr "" #: ./doc/install-guide/section_nova-network.xml81(para) msgid "" "Provide a local metadata service that is reachable from instances on this " "compute node. Perform this step only on compute nodes that do not run the " "nova-api service." msgstr "" #: ./doc/install-guide/section_nova-network.xml90(para) msgid "Restart the network service:" msgstr "" #: ./doc/install-guide/section_nova-network.xml92(para) msgid "" "Start the network service and configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_nova-network.xml99(para) msgid "" "Create a network that virtual machines can use. Do this once for the entire " "installation and not on each compute node. Run the command " "on the controller:" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml6(title) #: ./doc/install-guide/app_reserved_uids.xml24(caption) msgid "Reserved user IDs" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml8(para) msgid "" "In OpenStack, certain user IDs are reserved and used to run specific " "OpenStack services and own specific OpenStack files. These users are set up " "according to the distribution packages. The following table gives an " "overview." msgstr "" #: ./doc/install-guide/app_reserved_uids.xml16(para) msgid "" "Some OpenStack packages generate and assign user IDs automatically during " "package installation. In these cases, the user ID value is not important. " "The existence of the user ID is what matters." msgstr "" #: ./doc/install-guide/app_reserved_uids.xml27(th) msgid "Name" msgstr "Nazwa" #: ./doc/install-guide/app_reserved_uids.xml35(td) msgid "ceilometer" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml36(td) msgid "openstack-ceilometer" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml37(td) msgid "OpenStack Ceilometer Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml38(td) msgid "166" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml39(td) #: ./doc/install-guide/app_reserved_uids.xml46(td) #: ./doc/install-guide/app_reserved_uids.xml53(td) #: ./doc/install-guide/app_reserved_uids.xml60(td) #: ./doc/install-guide/app_reserved_uids.xml67(td) #: ./doc/install-guide/app_reserved_uids.xml74(td) #: ./doc/install-guide/app_reserved_uids.xml82(td) #: ./doc/install-guide/app_reserved_uids.xml89(td) msgid "Assigned during package installation" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml42(td) msgid "cinder" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml43(td) msgid "openstack-cinder" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml44(td) msgid "OpenStack Cinder Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml45(td) msgid "165" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml49(td) msgid "glance" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml50(td) msgid "openstack-glance" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml51(td) msgid "OpenStack Glance Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml52(td) msgid "161" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml56(td) msgid "heat" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml57(td) msgid "openstack-heat" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml58(td) msgid "OpenStack Heat Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml59(td) msgid "187" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml63(td) msgid "keystone" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml64(td) msgid "openstack-keystone" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml65(td) msgid "OpenStack Keystone Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml66(td) msgid "163" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml70(td) msgid "neutron" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml71(td) msgid "openstack-neutron" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml72(td) msgid "OpenStack Neutron Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml73(td) msgid "164" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml77(td) msgid "nova" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml78(td) msgid "openstack-nova" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml79(td) msgid "OpenStack Nova Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml80(td) msgid "162" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml81(td) msgid "96" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml85(td) msgid "swift" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml86(td) msgid "openstack-swift" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml87(td) msgid "OpenStack Swift Daemons" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml88(td) msgid "160" msgstr "" #: ./doc/install-guide/app_reserved_uids.xml93(para) msgid "Each user belongs to a user group with the same name as the user." msgstr "" #: ./doc/install-guide/ch_preface.xml10(title) msgid "Preface" msgstr "" #: ./doc/install-guide/section_ceilometer-glance.xml6(title) msgid "Add the Image Service agent for the Telemetry service" msgstr "" #: ./doc/install-guide/section_ceilometer-glance.xml9(para) msgid "" "To retrieve image samples, you must configure the Image Service to send " "notifications to the bus." msgstr "" #: ./doc/install-guide/section_ceilometer-glance.xml12(para) msgid "" "Edit /etc/glance/glance-api.conf and modify the " "[DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-glance.xml28(para) msgid "Restart the Image services with their new settings:" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml7(title) msgid "debconf concepts" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml8(para) msgid "" "This chapter explains how to use the Debian debconf and dbconfig-common packages to configure OpenStack services. " "These packages enable users to perform configuration tasks. When users " "install OpenStack packages, debconf prompts the user for " "responses, which seed the contents of configuration files associated with " "that package. After package installation, users can update the configuration" " of a package by using the program." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml18(para) msgid "" "If you are familiar with these packages and pre-seeding, you can proceed to " "." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml21(title) msgid "The Debian packages" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml22(para) msgid "" "The rules described here are from the Debian Policy Manual. If any" " rule described in this chapter is not respected, you have found a serious " "bug that must be fixed." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml27(para) msgid "" "When you install or upgrade a Debian package, all configuration file values " "are preserved. Using the debconf " "database as a registry is considered a bug in Debian. If you edit something " "in any OpenStack configuration file, the debconf package reads that value when it " "prepares to prompt the user. For example, to change the log in name for the " "RabbitMQ messaging queue for a service, you can edit its value in the " "corresponding configuration file." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml36(para) msgid "" "To opt out of using the debconf " "package, run the command and select non-interactive mode:" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml41(para) msgid "" "Then, debconf does not prompt " "you." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml43(para) msgid "" "Another way to disable the debconf package is to prefix the " " command with " "DEBIAN_FRONTEND=noninteractive, as follows:" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml49(para) msgid "" "If you configure a package with debconf incorrectly, you can re-configure it," " as follows:" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml52(replaceable) msgid "PACKAGE-NAME" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml53(para) msgid "" "This calls the post-installation script for the PACKAGE-" "NAME package after the user responds to all prompts. If you " "cannot install a Debian package in a non-interactive way, you have found a " "release-critical bug in Debian. Report it to the Debian bug tracking system." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml58(para) msgid "" "Generally, the -common packages " "install the configuration files. For example, the glance-" "common package installs the glance-api.conf " "and glance-registry.conf files. So, for the Image " "Service, you must re-configure the glance-common package." " The same applies for cinder-common, nova-" "common, and heat-common packages." msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml68(para) msgid "" "In debconf, the higher the " "priority for a screen, the greater the chance that the user sees that " "screen. If a debconf screen has " "medium priority and you configure the Debian system to " "show only critical prompts, which is the default in " "Debian, the user does not see that debconf screen. Instead, the default for the " "related package is used. In the Debian OpenStack packages, a number of " "debconf screens are set with " "medium priority. Consequently, if you want to respond to " "all debconf screens from the " "Debian OpenStack packages, you must run the following command and select the" " medium priority before you install any packages:" msgstr "" #: ./doc/install-guide/section_debconf-concepts.xml87(para) msgid "" "The packages do not require pre-depends. If dbconfig-common is already installed on the system, the user" " sees all prompts. However, you cannot define the order in which the " "debconf screens appear. The user " "must make sense of it even if the prompts appear in an illogical order." msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml6(title) msgid "Add the Object Storage agent for the Telemetry service" msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml9(para) msgid "" "To retrieve object store statistics, the Telemetry service needs access to " "Object Storage with the ResellerAdmin role. Give this " "role to your os_username user for the " "os_tenant_name tenant:" msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml23(replaceable) msgid "462fa46c13fd4798a95a3bfbe27b5e54" msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml26(para) msgid "" "You must also add the Telemetry middleware to Object Storage to handle " "incoming and outgoing traffic. Add these lines to the /etc/swift" "/proxy-server.conf file:" msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml35(para) msgid "" "Add ceilometer to the pipeline " "parameter of that same file:" msgstr "" #: ./doc/install-guide/section_ceilometer-swift.xml41(para) #: ./doc/install-guide/section_heat-install.xml150(para) #: ./doc/install-guide/section_ceilometer-nova.xml68(para) msgid "Restart the service with its new settings:" msgstr "" #: ./doc/install-guide/section_debconf-preseeding.xml6(title) msgid "Pre-seed debconf prompts" msgstr "" #: ./doc/install-guide/section_debconf-preseeding.xml7(para) msgid "" "You can pre-seed all debconf " "prompts. To pre-seed means to store responses in the " "debconf database so that debconf does " "not prompt the user for responses. Pre-seeding enables a hands-free " "installation for users. The package maintainer creates scripts that " "automatically configure the services." msgstr "" #: ./doc/install-guide/section_debconf-preseeding.xml14(para) msgid "" "The following example shows how to pre-seed an automated MySQL Server " "installation:" msgstr "" #: ./doc/install-guide/section_debconf-preseeding.xml16(replaceable) #: ./doc/install-guide/section_debconf-preseeding.xml17(replaceable) #: ./doc/install-guide/section_debconf-preseeding.xml19(replaceable) msgid "MYSQL_PASSWORD" msgstr "" #: ./doc/install-guide/section_debconf-preseeding.xml23(para) msgid "" "The seen true option tells debconf that a " "specified screen was already seen by the user so do not show it again. This " "option is useful for upgrades." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-single-flat.xml22(None) msgid "" "@@image: '../common/figures/demo_flat_install.png'; " "md5=27b45d5871859ff4951c92df7c8763d8" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-single-flat.xml621(None) msgid "" "@@image: '../common/figures/UseCase-SingleFlat.png'; " "md5=bdd61f2967fb1a55e4f50d766db7b113" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-single-flat.xml637(None) msgid "" "@@image: '../common/figures/UseCase-MultiFlat.png'; " "md5=289e38a7a13a2a4413e5a1e62ce55b3e" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-single-flat.xml659(None) msgid "" "@@image: '../common/figures/UseCase-MixedFlatPrivate.png'; " "md5=8da4ceb5a1e5a2357394478645af7449" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml6(title) msgid "Single flat network" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml7(para) msgid "" "This section describes how to install the OpenStack Networking service and " "its components for a single flat network use case." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml10(para) msgid "" "The following diagram shows the set up. For simplicity, all nodes should " "have one interface for management traffic and one or more interfaces for " "traffic to and from VMs. The management network is 100.1.1.0/24 with " "controller node at 100.1.1.2. The example uses the Open vSwitch plugin and " "agent." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml16(para) msgid "" "You can modify this set up to make use of another supported plug-in and its " "agent." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml25(para) msgid "The following table describes some nodes in the set up:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml39(para) msgid "" "Runs the Networking service, Identity Service, and Compute services that are" " required to deploy VMs (nova-" "api, nova-scheduler," " for example). The node must have at least one network interface, which is " "connected to the Management Network. The host name is " "controller, which every other node resolves to the IP of " "the controller node." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml52(para) msgid "" "The nova-network service should " "not be running. This is replaced by the OpenStack Networking component, " "neutron. To delete a network, run" " this command:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml64(para) msgid "" "Note that a network must first be disassociated from a project using the " "nova network-disassociate command before it can be deleted." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml71(td) msgid "" "Runs the Networking L2 agent and the Compute services that run VMs " "( specifically, and optionally other nova-* services " "depending on configuration). The node must have at least two network " "interfaces. The first communicates with the controller node through the " "management network. The second interface handles the VM traffic on the data " "network. The VM can receive its IP address from the DHCP agent on this " "network." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml85(td) msgid "" "Runs Networking L2 agent and the DHCP agent. The DHCP agent allocates IP " "addresses to the VMs on the network. The node must have at least two network" " interfaces. The first communicates with the controller node through the " "management network. The second interface handles the VM traffic on the data " "network." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml101(para) msgid "The demo assumes the following prerequisites:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml109(para) msgid "" "Glance is installed, configured, and running. Additionally, an image must be" " available." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml113(para) msgid "" "OpenStack Identity is installed, configured, and running. A Networking user " "neutron is in place on tenant service with password " "NEUTRON_PASS." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml121(para) msgid "Additional services:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml124(para) msgid "" "RabbitMQ is running with the default guest user and password " "RABBIT_PASS." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml129(para) msgid "Qpid is running with the default guest user and password." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml142(para) msgid "Compute is installed and configured." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml155(para) msgid "" "Install the Networking server and respond to debconf prompts to configure the database, " "the keystone_authtoken, and the RabbitMQ credentials." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml162(para) msgid "" "See for " "installation instructions." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml171(para) msgid "" "See for database creation " "details." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml177(para) msgid "" "If not already configured, update the Networking " "/etc/neutron/neutron.conf configuration file to use the Identity " "Service, the plug-in, and database configuration:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml191(para) #: ./doc/install-guide/section_neutron-install.xml334(para) #: ./doc/install-guide/section_neutron-install.xml900(para) #: ./doc/install-guide/section_neutron-install.xml1208(para) msgid "Configure Networking to connect to the database:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml194(para) #: ./doc/install-guide/section_neutron-single-flat.xml347(para) msgid "Configure Networking to use your chosen plug-in:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml199(para) #: ./doc/install-guide/section_neutron-single-flat.xml352(para) #: ./doc/install-guide/section_neutron-single-flat.xml436(para) #: ./doc/install-guide/section_neutron-install.xml301(para) #: ./doc/install-guide/section_neutron-install.xml853(para) #: ./doc/install-guide/section_neutron-install.xml1304(para) msgid "Configure access to the RabbitMQ service:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml208(para) #: ./doc/install-guide/section_neutron-single-flat.xml361(para) #: ./doc/install-guide/section_neutron-single-flat.xml445(para) #: ./doc/install-guide/section_neutron-install.xml321(para) #: ./doc/install-guide/section_neutron-install.xml864(para) #: ./doc/install-guide/section_neutron-install.xml1315(para) msgid "Configure access to the Qpid message queue:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml216(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml218(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml369(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml371(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml453(replaceable) #: ./doc/install-guide/section_neutron-single-flat.xml455(replaceable) #: ./doc/install-guide/section_neutron-install.xml329(replaceable) #: ./doc/install-guide/section_neutron-install.xml331(replaceable) #: ./doc/install-guide/section_neutron-install.xml872(replaceable) #: ./doc/install-guide/section_neutron-install.xml874(replaceable) #: ./doc/install-guide/section_neutron-install.xml1323(replaceable) #: ./doc/install-guide/section_neutron-install.xml1325(replaceable) msgid "guest" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml221(para) msgid "" "If not already configured, update the Networking " "/etc/neutron/neutron.conf configuration file to choose a plug-in " "and Identity Service user as necessary:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml243(para) msgid "" "Update the plug-in " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " "configuration file with the bridge mappings:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml258(para) msgid "Restart the Networking service:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml265(emphasis) msgid "Compute node - Compute" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml267(para) msgid "" "Install the nova-compute service." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml271(para) msgid "See for installation instructions." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml276(para) msgid "" "Update the Compute /etc/nova/nova.conf configuration " "file to make use of OpenStack Networking:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml304(para) msgid "Restart the Compute services" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml311(emphasis) msgid "Compute and Network node - L2 agent" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml314(para) msgid "" "Install and start Open vSwitch. Then, configure neutron accordingly." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml316(para) msgid "" "See for detailed " "instructions." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml321(para) msgid "Add the integration bridge to Open vSwitch:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml326(para) #: ./doc/install-guide/section_neutron-single-flat.xml418(para) msgid "" "Update the Networking /etc/neutron/neutron.conf " "configuration file:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml341(para) msgid "" "If not already configured, update the Networking " "/etc/neutron/neutron.conf configuration file to use the plug-in, " "message queue, and database configuration:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml374(para) msgid "" "Update the plug-in " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini " "configuration file:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml388(para) msgid "" "Create a symbolic link from /etc/neutron/plugin.ini to " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " or neutron-server will not run:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml393(para) msgid "" "Create the br-eth0 network bridge to " "handle communication between nodes using eth0:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml401(para) msgid "Restart the OpenStack Networking L2 agent:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml409(emphasis) msgid "Network node - DHCP agent" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml413(para) msgid "" "See for generic installation instructions." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml429(para) msgid "" "If not already configured, update the Networking " "/etc/neutron/neutron.conf configuration file to use the plug-in " "and message queue." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml458(para) msgid "" "Ensure that the DHCP agent is using the correct plug-in my changing the " "configuration in /etc/neutron/dhcp_agent.ini:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml466(para) msgid "Restart the DHCP agent:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml476(para) msgid "Use the following commands on the network node." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml502(para) msgid "Get the user information:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml515(para) msgid "" "Create a internal shared network on the demo tenant ($TENANT_ID is " "b7445f221cda4f4a8ac7db6b218b1339):" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml538(para) msgid "Create a subnet on the network:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml558(para) msgid "Create a server for tenant A:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml571(para) msgid "Ping the server of tenant A:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml577(para) msgid "Ping the public network within the server of tenant A:" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml589(para) msgid "" "The 192.168.1.1 is an IP on public network to which the router connects." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml594(para) msgid "" "Create servers for other tenants with similar commands. Because all VMs " "share the same subnet, they can access each other." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml601(title) msgid "Use case: single flat network" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml602(para) msgid "" "The simplest use case is a single network. This is a \"shared\" network, " "meaning it is visible to all tenants via the Networking API. Tenant VMs have" " a single NIC, and receive a fixed IP address from the subnet(s) associated " "with that network. This use case essentially maps to the FlatManager and " "FlatDHCPManager models provided by Compute. Floating IPs are not supported." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml609(para) msgid "" "This network type is often created by the OpenStack administrator to map " "directly to an existing physical network in the data center (called a " "\"provider network\"). This allows the provider to use a physical router on " "that data center network as the gateway for VMs to reach the outside world. " "For each subnet on an external network, the gateway configuration on the " "physical router must be manually configured outside of OpenStack." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml628(title) msgid "Use case: multiple flat network" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml629(para) msgid "" "This use case is similar to the above single flat network use case, except " "that tenants can see multiple shared networks via the Networking API and can" " choose which network (or networks) to plug into." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml643(title) msgid "Use case: mixed flat and private network" msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml644(para) msgid "" "This use case is an extension of the above Flat Network use cases. In " "addition to being able to see one or more shared networks via the OpenStack " "Networking API, tenants can also have access to private per-tenant networks " "(only visible to tenant users)." msgstr "" #: ./doc/install-guide/section_neutron-single-flat.xml649(para) msgid "" "Created VMs can have NICs on any of the shared or private networks that the " "tenant owns. This enables the creation of multi-tier topologies that use VMs" " with multiple NICs. It also enables a VM to act as a gateway so that it can" " provide services such as routing, NAT, and load balancing." msgstr "" #: ./doc/install-guide/ch_neutron.xml6(title) msgid "Install the Networking service" msgstr "" #: ./doc/install-guide/ch_neutron.xml9(para) msgid "" "This chapter is a bit more adventurous than we would like. We are working on" " cleanup and improvements to it. Like for the rest of the Installation " "Guide, feedback through bug reports and patches to improve it are welcome." msgstr "" #: ./doc/install-guide/ch_neutron.xml16(title) msgid "Networking considerations" msgstr "" #: ./doc/install-guide/ch_neutron.xml17(para) msgid "" "OpenStack Networking drivers range from software bridges to full control of " "certain switching hardware. This guide focuses on the Open vSwitch driver. " "However, the theories presented here are mostly applicable to other " "mechanisms, and the Networking chapter of the OpenStack " "Configuration Reference offers additional information." msgstr "" #: ./doc/install-guide/ch_neutron.xml26(para) msgid "To prepare for installation, see ." msgstr "" #: ./doc/install-guide/ch_neutron.xml29(para) msgid "" "If you previously set up networking for your compute node by using " "nova-network, this configuration " "overrides those settings." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/ch_basics.xml121(None) msgid "" "@@image: 'figures/basic-architecture-networking.svg'; " "md5=1a9454b8cdb45af98a43fbff5dd58fe9" msgstr "" #: ./doc/install-guide/ch_basics.xml6(title) msgid "Basic operating system configuration" msgstr "" #: ./doc/install-guide/ch_basics.xml8(para) msgid "" "This guide shows you how to create a controller node to host most services " "and a compute node to run virtual machine instances. Subsequent chapters " "create additional nodes to run more services. OpenStack is flexible about " "how and where you run each service, so other configurations are possible. " "However, you must configure certain operating system settings on each node." msgstr "" #: ./doc/install-guide/ch_basics.xml14(para) msgid "" "This chapter details a sample configuration for the controller node and any " "additional nodes. You can configure the operating system in other ways, but " "this guide assumes that your configuration is compatible with the one " "described here." msgstr "" #: ./doc/install-guide/ch_basics.xml18(para) msgid "" "All example commands assume you have administrative privileges. Either run " "the commands as the root user or prefix them with the " "command." msgstr "" #: ./doc/install-guide/ch_basics.xml24(title) #: ./doc/install-guide/object-storage/section_object-storage-install.xml23(title) msgid "Before you begin" msgstr "" #: ./doc/install-guide/ch_basics.xml26(para) msgid "" "We strongly recommend that you install a 64-bit operating system on your " "compute nodes. If you use a 32-bit operating system, attempting a start a " "virtual machine using a 64-bit image will fail with an error." msgstr "" #: ./doc/install-guide/ch_basics.xml31(para) msgid "" "For more information about system requirements, see the OpenStack Operations Guide." msgstr "" #: ./doc/install-guide/ch_basics.xml38(title) msgid "Networking" msgstr "Sieć" #: ./doc/install-guide/ch_basics.xml40(para) msgid "" "For an OpenStack production deployment, most nodes must have these network " "interface cards:" msgstr "" #: ./doc/install-guide/ch_basics.xml44(para) msgid "One network interface card for external network traffic" msgstr "" #: ./doc/install-guide/ch_basics.xml48(para) msgid "Another card to communicate with other OpenStack nodes." msgstr "" #: ./doc/install-guide/ch_basics.xml52(para) msgid "" "For simple test cases, you can use machines with a single network interface " "card." msgstr "" #: ./doc/install-guide/ch_basics.xml54(para) msgid "" "The following example configures Networking on two networks with static IP " "addresses and manually manages a list of host names on each machine. If you " "manage a large network, you might already have systems in place to manage " "this. If so, you can skip this section but note that the rest of this guide " "assumes that each node can reach the other nodes on the internal network by " "using the controller and compute1 host" " names." msgstr "" #. these fedora only paragraphs are confirmed not needed in centos #: ./doc/install-guide/ch_basics.xml63(para) msgid "" "Disable the NetworkManager " "service and enable the network " "service. The network service is " "more suitable for the static network configuration done in this guide." msgstr "" #: ./doc/install-guide/ch_basics.xml75(para) msgid "" "Since Fedora 19, firewalld replaces " "iptables as the default firewall system." msgstr "" #: ./doc/install-guide/ch_basics.xml78(para) msgid "" "You can use firewalld successfully, but this guide " "recommends and demonstrates the use of the default " "iptables." msgstr "" #: ./doc/install-guide/ch_basics.xml81(para) msgid "" "For Fedora 19 systems, run the following commands to disable " "firewalld and enable iptables:" msgstr "" #: ./doc/install-guide/ch_basics.xml89(para) msgid "" "RHEL and derivatives including CentOS and Scientific Linux enable a " "restrictive firewall by default. During this installation, certain steps " "will fail unless you alter this setting or disable the firewall. For further" " information about securing your installation, refer to the OpenStack Security Guide." msgstr "" #: ./doc/install-guide/ch_basics.xml96(para) msgid "" "When you set up your system, use the traditional network scripts and do not " "use NetworkManager. You can " "change the settings after installation with the YaST network module:" msgstr "" #: ./doc/install-guide/ch_basics.xml102(para) msgid "" "Configure both eth0 and eth1. The " "examples in this guide use the " "192.168.0.x IP addresses for " "the internal network and the " "10.0.0.x IP addresses for the " "external network. Make sure to connect your network devices to the correct " "network." msgstr "" #: ./doc/install-guide/ch_basics.xml109(para) msgid "" "In this guide, the controller node uses the 192.168.0.10 " "and 10.0.0.10 IP addresses. When you create the compute " "node, use the 192.168.0.11 and " "10.0.0.11 addresses instead. Additional nodes that you " "add in subsequent chapters also follow this pattern." msgstr "" #: ./doc/install-guide/ch_basics.xml117(title) msgid "Basic architecture" msgstr "" #: ./doc/install-guide/ch_basics.xml126(filename) msgid "/etc/sysconfig/network-scripts/ifcfg-eth0" msgstr "" #: ./doc/install-guide/ch_basics.xml137(filename) msgid "/etc/sysconfig/network-scripts/ifcfg-eth1" msgstr "" #: ./doc/install-guide/ch_basics.xml147(para) msgid "" "To configure the network interfaces, start the YaST network module, as " "follows:" msgstr "" #: ./doc/install-guide/ch_basics.xml152(para) msgid "" "Use these parameters to set up the eth0 ethernet card for" " the internal network:" msgstr "" #: ./doc/install-guide/ch_basics.xml160(para) msgid "" "Use these parameters to set up the eth1 ethernet card for" " the external network:" msgstr "" #: ./doc/install-guide/ch_basics.xml168(para) msgid "Set up a default route on the external network." msgstr "" #: ./doc/install-guide/ch_basics.xml173(filename) msgid "/etc/network/interfaces" msgstr "" #: ./doc/install-guide/ch_basics.xml187(para) msgid "" "After you configure the network, restart the daemon for changes to take " "effect:" msgstr "" #: ./doc/install-guide/ch_basics.xml193(para) msgid "" "Set the host name of each machine. Name the controller node " "controller and the first compute node " "compute1. The examples in this guide use these host " "names." msgstr "" #: ./doc/install-guide/ch_basics.xml197(para) msgid "" "Use the command to set the host name: " msgstr "" #: ./doc/install-guide/ch_basics.xml200(para) msgid "Use to set the host name with YaST." msgstr "" #: ./doc/install-guide/ch_basics.xml202(para) msgid "" "To have the host name change persist when the system reboots, you must " "specify it in the proper configuration file. In Red Hat Enterprise Linux, " "CentOS, and older versions of Fedora, you set this in the file " "/etc/sysconfig/network. Change the line starting with " "HOSTNAME=." msgstr "" #: ./doc/install-guide/ch_basics.xml209(para) msgid "" "As of Fedora 18, Fedora uses the /etc/hostname file, " "which contains a single line with the host name." msgstr "" #: ./doc/install-guide/ch_basics.xml212(para) msgid "" "To configure this host name to be available when the system reboots, you " "must specify it in the /etc/hostname file, which " "contains a single line with the host name." msgstr "" #: ./doc/install-guide/ch_basics.xml216(para) msgid "" "Finally, ensure that each node can reach the other nodes by using host " "names. You must manually edit the /etc/hosts file on " "each system. For large-scale deployments, use DNS or a configuration " "management system like Puppet." msgstr "" #: ./doc/install-guide/ch_basics.xml226(title) msgid "Network Time Protocol (NTP)" msgstr "" #: ./doc/install-guide/ch_basics.xml227(para) msgid "" "To synchronize services across multiple machines, you must install NTP. The " "examples in this guide configure the controller node as the reference server" " and any additional nodes to set their time from the controller node." msgstr "" #: ./doc/install-guide/ch_basics.xml231(para) msgid "" "Install the ntp package on each system running OpenStack " "services." msgstr "" #: ./doc/install-guide/ch_basics.xml236(para) msgid "" "Set up the NTP server on your controller node so that it receives data by " "modifying the ntp.conf file and restarting the service." msgstr "" #: ./doc/install-guide/ch_basics.xml244(para) msgid "" "On additional nodes, it is advised that you configure the other nodes to " "synchronize their time from the controller node rather than from outside of " "your LAN. To do so, install the ntp daemon as above, then edit " "/etc/ntp.conf and change the server " "directive to use the controller node as internet time source." msgstr "" #: ./doc/install-guide/ch_basics.xml253(title) msgid "Passwords" msgstr "" #: ./doc/install-guide/ch_basics.xml255(para) msgid "" "The various OpenStack services and the required software like the database " "and the Messaging server have to be password protected. These passwords are " "needed when configuring a service and then again to access the service. You " "have to choose a random password while configuring the service and later " "remember to use the same password when accessing it. To generate a list of " "passwords, you can use the pwgen program to " "generate a list of passwords or take the output of: " msgstr "" #: ./doc/install-guide/ch_basics.xml266(para) msgid "" "This guide uses the convention that " "SERVICE_PASS is password to " "access the service SERVICE and " "SERVICE_DBPASS is the database" " password used by the service SERVICE to access the database." msgstr "" #: ./doc/install-guide/ch_basics.xml274(para) msgid "" "The complete list of passwords you need to define in this guide are:
Passwords
Password " "nameDescription
Database password " "(no variable used)Root password for the database
RABBIT_PASSPassword" " of user guest of " "RabbitMQ
KEYSTONE_DBPASSDatabase" " password of Identity " "service
ADMIN_PASSPassword" " of user " "admin
GLANCE_DBPASSDatabase" " password for Image " "Service
GLANCE_PASSPassword" " of Image Service user " "glance
NOVA_DBPASSDatabase" " password for Compute " "service
NOVA_PASSPassword" " of Compute service user " "nova
DASH_DBPASSDatabase" " password for the " "dashboard
CINDER_DBPASSDatabase" " password for the Block Storage " "Service
CINDER_PASSPassword" " of Block Storage Service user " "cinder
NEUTRON_DBPASSDatabase" " password for the Networking " "service
NEUTRON_PASSPassword" " of Networking service user " "neutron
HEAT_DBPASSDatabase" " password for the Orchestration " "service
HEAT_PASSPassword" " of Orchestration service user " "heat
CEILOMETER_DBPASSDatabase" " password for the Telemetry " "service
CEILOMETER_PASSPassword" " of Telemetry service user " "ceilometer
" msgstr "" #: ./doc/install-guide/ch_basics.xml358(title) msgid "MySQL database" msgstr "" #: ./doc/install-guide/ch_basics.xml359(para) msgid "" "Most OpenStack services require a database to store information. These " "examples use a MySQL database that runs on the controller node. You must " "install the MySQL database on the controller node. You must install MySQL " "client software on any additional nodes that access MySQL." msgstr "" #: ./doc/install-guide/ch_basics.xml365(para) msgid "" "Most OpenStack services require a database to store information. This guide " "uses a MySQL database on SUSE Linux Enterprise Server and a compatible " "database on openSUSE running on the controller node. This compatible " "database for openSUSE is MariaDB. You must install the MariaDB database on " "the controller node. You must install the MariaDB client software on any " "nodes that access the MariaDB database." msgstr "" #: ./doc/install-guide/ch_basics.xml375(title) msgid "Controller setup" msgstr "" #: ./doc/install-guide/ch_basics.xml376(para) msgid "" "For SUSE Linux Enterprise Server: On the " "controller node, install the MySQL client and server packages, and the " "Python library." msgstr "" #: ./doc/install-guide/ch_basics.xml380(para) msgid "" "For openSUSE: On the controller node, install the MariaDB client and " "database server packages, and the MySQL Python library." msgstr "" #: ./doc/install-guide/ch_basics.xml387(para) msgid "" "When you install the server package, you are prompted for the root password " "for the database. Choose a strong password and remember it." msgstr "" #: ./doc/install-guide/ch_basics.xml391(para) msgid "" "Edit /etc/mysql/my.cnf/etc/my.cnf and set the " "bind-address to the internal IP address of the " "controller, to enable access from outside the controller node." msgstr "" #: ./doc/install-guide/ch_basics.xml401(para) msgid "Restart the MySQL service to apply the changes:" msgstr "" #: ./doc/install-guide/ch_basics.xml404(para) msgid "" "Start the MySQLMariaDB or MySQL database server and set it to" " start automatically when the system boots." msgstr "" #: ./doc/install-guide/ch_basics.xml413(para) msgid "" "Finally, you should set a root password for your MySQLMariaDB" " or MySQL database. The OpenStack programs that set up databases " "and tables prompt you for this password if it is set." msgstr "" #: ./doc/install-guide/ch_basics.xml419(para) msgid "" "You must delete the anonymous users that are created when the database is " "first started. Otherwise, database connection problems occur when you follow" " the instructions in this guide. To do this, use the " "command. Note that if fails you might need to use " " first:" msgstr "" #: ./doc/install-guide/ch_basics.xml428(para) msgid "" "If you have not already set " "a root database password, press ENTER when you are prompted" " for the password. This command presents a number of options for " "you to secure your database installation. Respond to all " "prompts unless you have a good reason to do otherwise." msgstr "" #: ./doc/install-guide/ch_basics.xml438(title) msgid "Node setup" msgstr "" #: ./doc/install-guide/ch_basics.xml439(para) msgid "" "On all nodes other than the controller node, install the MySQLMariaDB (on openSUSE) client and the MySQL Python " "library on any system that does not host a MySQL database:" msgstr "" #: ./doc/install-guide/ch_basics.xml448(para) msgid "For SUSE Linux Enterprise, install MySQL:" msgstr "" #: ./doc/install-guide/ch_basics.xml455(title) msgid "OpenStack packages" msgstr "" #: ./doc/install-guide/ch_basics.xml456(para) msgid "" "Distributions might release OpenStack packages as part of their distribution" " or through other methods because the OpenStack and distribution release " "times are independent of each other." msgstr "" #: ./doc/install-guide/ch_basics.xml460(para) msgid "" "This section describes the configuration you must complete after you " "configure machines to install the latest OpenStack packages." msgstr "" #: ./doc/install-guide/ch_basics.xml463(para) msgid "" "The examples in this guide use the OpenStack packages from the RDO " "repository. These packages work on Red Hat Enterprise Linux 6, compatible " "versions of CentOS, and Fedora 19. To enable the RDO repository, download " "and install the rdo-release-havana package." msgstr "" #: ./doc/install-guide/ch_basics.xml470(para) msgid "" "The EPEL package includes GPG keys for package signing and repository " "information. This should only be installed on Red Hat Enterprise Linux and " "CentOS, not Fedora. Install the latest epel-release " "package (see http://download.fedoraproject.org/pub/epel/6/x86_64/repoview" "/epel-release.html). For example:" msgstr "" #: ./doc/install-guide/ch_basics.xml479(para) msgid "" "The openstack-utils package contains utility programs " "that make installation and configuration easier. These programs are used " "throughout this guide. Install openstack-utils. This " "verifies that you can access the RDO repository." msgstr "" #: ./doc/install-guide/ch_basics.xml486(para) msgid "" "The openstack-selinux package includes the policy files " "that are required to configure SELinux during OpenStack installation. " "Install openstack-selinux." msgstr "" #: ./doc/install-guide/ch_basics.xml490(para) #: ./doc/install-guide/ch_basics.xml510(para) msgid "Upgrade your system and reboot for all changes to take effect:" msgstr "" #: ./doc/install-guide/ch_basics.xml494(para) msgid "" "Use the Open Build Service repositories for Havana based on your openSUSE or" " SUSE Linux Enterprise Server version, for example if you run openSUSE 12.3 " "use:" msgstr "" #: ./doc/install-guide/ch_basics.xml498(para) msgid "If you use SUSE Linux Enterprise Server 11 SP3, use:" msgstr "" #: ./doc/install-guide/ch_basics.xml501(para) msgid "" "For openSUSE 13.1, nothing needs to be done because OpenStack Havana " "packages are part of the distribution itself." msgstr "" #: ./doc/install-guide/ch_basics.xml504(para) msgid "" "The openstack-utils package contains utility programs " "that make installation and configuration easier. These programs are used " "throughout this guide. Install openstack-utils. This " "verifies that you can access the Open Build Service repository:" msgstr "" #: ./doc/install-guide/ch_basics.xml516(title) msgid "To use the Ubuntu Cloud Archive for Havana" msgstr "" #: ./doc/install-guide/ch_basics.xml517(para) msgid "" "The Ubuntu " "Cloud Archive is a special repository that allows you to install " "newer releases of OpenStack on the stable supported version of Ubuntu." msgstr "" #: ./doc/install-guide/ch_basics.xml523(para) msgid "Install the Ubuntu Cloud Archive for Havana: " msgstr "" #: ./doc/install-guide/ch_basics.xml528(para) msgid "" "Update the package database, upgrade your system, and reboot for all changes" " to take effect: " msgstr "" #: ./doc/install-guide/ch_basics.xml535(title) msgid "To use the Debian Wheezy backports archive for Havana" msgstr "" #: ./doc/install-guide/ch_basics.xml537(para) msgid "" "The Havana release is available only in Debian Sid (otherwise called " "Unstable). However, the Debian maintainers of OpenStack also maintain a non-" "official Debian repository for OpenStack containing Wheezy backports." msgstr "" #: ./doc/install-guide/ch_basics.xml542(para) msgid "Install the Debian Wheezy backport repository Havana:" msgstr "" #: ./doc/install-guide/ch_basics.xml547(para) msgid "Install the Debian Wheezy OpenStack repository for Havana:" msgstr "" #: ./doc/install-guide/ch_basics.xml552(para) msgid "Update the repository database and install the key:" msgstr "" #: ./doc/install-guide/ch_basics.xml556(para) msgid "" "Update the package database, upgrade your system, and reboot for all changes" " to take effect:" msgstr "" #: ./doc/install-guide/ch_basics.xml562(para) msgid "" "Numerous archive.gplhost.com mirrors are available around the world. All are" " available with both FTP and HTTP protocols (you should use the closest " "mirror). The list of mirrors is available at http://archive.gplhost.com/readme.mirrors." msgstr "" #: ./doc/install-guide/ch_basics.xml570(title) msgid "Manually install python-argparse" msgstr "" #: ./doc/install-guide/ch_basics.xml571(para) msgid "" "The Debian OpenStack packages are maintained on Debian Sid (also known as " "Debian Unstable) - the current development version. Backported packages run " "correctly on Debian Wheezy with one caveat:" msgstr "" #: ./doc/install-guide/ch_basics.xml575(para) msgid "" "All OpenStack packages are written in Python. Wheezy uses Python 2.6 and " "2.7, with Python 2.6 as the default interpreter; Sid has only Python 2.7. " "There is one packaging change between these two. In Python 2.6, you " "installed the python-argparse package separately. In " "Python 2.7, this package is installed by default. Unfortunately, in Python " "2.7, this package does not include Provides: python-argparse " "directive." msgstr "" #: ./doc/install-guide/ch_basics.xml583(para) msgid "" "Because the packages are maintained in Sid where the Provides: python-" "argparse directive causes an error, and the Debian OpenStack " "maintainer wants to maintain one version of the OpenStack packages, you must" " manually install the python-argparse on each OpenStack " "system that runs Debian Wheezy before you install the other OpenStack " "packages. Use the following command to install the package:" msgstr "" #: ./doc/install-guide/ch_basics.xml592(para) msgid "This caveat applies to most OpenStack packages in Wheezy." msgstr "" #: ./doc/install-guide/ch_basics.xml596(title) msgid "Messaging server" msgstr "" #: ./doc/install-guide/ch_basics.xml597(para) msgid "" "On the controller node, install the messaging queue server. Typically this " "is RabbitMQQpid but QpidRabbitMQ and ZeroMQ (0MQ) are also " "available." msgstr "" #: ./doc/install-guide/ch_basics.xml607(title) msgid "Important security consideration" msgstr "" #: ./doc/install-guide/ch_basics.xml608(para) msgid "" "The rabbitmq-server package configures the RabbitMQ " "service to start automatically and creates a guest user " "with a default guest password. The RabbitMQ examples in " "this guide use the guest account, though it is strongly " "advised to change its default password, especially if you have IPv6 " "available: by default the RabbitMQ server enables anyone to connect to it by" " using guest as login and password, and with IPv6, it is reachable from the " "outside." msgstr "" #: ./doc/install-guide/ch_basics.xml618(para) msgid "To change the default guest password of RabbitMQ:" msgstr "" #: ./doc/install-guide/ch_basics.xml621(para) msgid "" "Disable Qpid authentication by editing /etc/qpidd.conf " "file and changing the auth option to " "no." msgstr "" #: ./doc/install-guide/ch_basics.xml627(para) msgid "" "To simplify configuration, the Qpid examples in this guide do not use " "authentication. However, we strongly advise enabling authentication for " "production deployments. For more information on securing Qpid refer to the " "Qpid " "Documentation." msgstr "" #: ./doc/install-guide/ch_basics.xml636(para) msgid "" "After enabling Qpid authenticaton, you must update the configuration file of" " each OpenStack service to ensure that the qpid_username " "and qpid_password configuration keys refer to a valid " "Qpid username and password, respectively." msgstr "" #: ./doc/install-guide/ch_basics.xml644(para) msgid "Start Qpid and set it to start automatically when the system boots." msgstr "" #: ./doc/install-guide/ch_basics.xml648(para) msgid "" "Start the messaging service and set it to start automatically when the " "system boots:" msgstr "" #: ./doc/install-guide/ch_basics.xml652(para) msgid "Congratulations, now you are ready to install OpenStack services!" msgstr "" #: ./doc/install-guide/section_cinder-node.xml6(title) msgid "Configure a Block Storage Service node" msgstr "" #: ./doc/install-guide/section_cinder-node.xml7(para) msgid "" "After you configure the services on the controller node, configure a second " "system to be a Block Storage Service node. This node contains the disk that " "serves volumes." msgstr "" #: ./doc/install-guide/section_cinder-node.xml10(para) #: ./doc/install-guide/section_cinder-controller.xml15(para) msgid "" "You can configure OpenStack to use various storage systems. The examples in " "this guide show you how to configure LVM." msgstr "" #: ./doc/install-guide/section_cinder-node.xml14(para) msgid "" "Use the instructions in to configure the " "system. Note the following differences from the installation instructions " "for the controller node:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml19(para) msgid "" "Set the host name to block1. Ensure that the IP addresses" " and host names for both nodes are listed in the " "/etc/hosts file on each system." msgstr "" #: ./doc/install-guide/section_cinder-node.xml25(para) msgid "" "Follow the instructions in to synchronize " "from the controller node." msgstr "" #: ./doc/install-guide/section_cinder-node.xml31(para) msgid "" "Install the required LVM packages, if they are not already installed: " "" msgstr "" #: ./doc/install-guide/section_cinder-node.xml37(para) msgid "" "Create the LVM physical and logical volumes. This guide assumes a second " "disk /dev/sdb that is used for this purpose:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml45(para) msgid "" "Add a filter entry to the devices section " "/etc/lvm/lvm.conf to keep LVM from scanning devices " "used by virtual machines:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml49(para) msgid "" "You must add required physical volumes for LVM on the Block Storage host. " "Run the command to get a list or required volumes." msgstr "" #: ./doc/install-guide/section_cinder-node.xml53(para) msgid "" "Each item in the filter array starts with either an a for" " accept, or an r for reject. The physical volumes that " "are required on the Block Storage host have names that begin with " "a. The array must end with \"r/.*/\" " "to reject any device not listed." msgstr "" #: ./doc/install-guide/section_cinder-node.xml59(para) msgid "" "In this example, /dev/sda1 is the volume where the " "volumes for the operating system for the node reside, while " "/dev/sdb is the volume reserved for cinder-" "volumes." msgstr "" #: ./doc/install-guide/section_cinder-node.xml70(para) msgid "" "After you configure the operating system, install the appropriate packages " "for the Block Storage Service:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml77(para) msgid "" "Respond to the debconf prompts " "about the database " "management, [keystone_authtoken] " "settings, and RabbitMQ " "credentials. Make sure to enter the same details as your Block " "Storage Service controller node." msgstr "" #: ./doc/install-guide/section_cinder-node.xml85(para) msgid "" "Another screen prompts you for the volume-" "group to use. The Debian package configuration script detects " "every active volume group, provided that the lvm2 package is installed before Block " "Storage (this should be the case if you configured the volume group first, " "as this guide recommends), and tries to use the first one it sees. If you " "have only one active volume group on your Block Storage Service node, you do" " not need to manually enter its name in when you install the cinder-volume package because it is detected " "automatically. If no volume-group" " is available when you install cinder-" "common, you must manually configure or re-configure cinder-common by using ." msgstr "" #: ./doc/install-guide/section_cinder-node.xml104(para) msgid "" "Copy the /etc/cinder/api-paste.ini file from the " "controller, or open the file in a text editor and locate the section " "[filter:authtoken]. Make sure the following options are " "set:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml115(replaceable) #: ./doc/install-guide/section_cinder-controller.xml78(replaceable) #: ./doc/install-guide/section_cinder-controller.xml94(replaceable) msgid "CINDER_PASS" msgstr "" #: ./doc/install-guide/section_cinder-node.xml118(para) #: ./doc/install-guide/section_cinder-controller.xml98(para) msgid "" "Configure Block Storage to use the RabbitMQ message broker by setting these " "configuration keys in the [DEFAULT] configuration group " "of the /etc/cinder/cinder.conf file. Replace " "RABBIT_PASS with the password you chose for " "RabbitMQ." msgstr "" #: ./doc/install-guide/section_cinder-node.xml133(para) #: ./doc/install-guide/section_cinder-controller.xml113(para) msgid "Configure Block Storage to use the Qpid message broker." msgstr "" #: ./doc/install-guide/section_cinder-node.xml140(para) #: ./doc/install-guide/section_cinder-controller.xml120(para) msgid "" "Configure Block Storage to use the RabbitMQ message broker. Replace " "RABBIT_PASS with the password you chose for " "RabbitMQ." msgstr "" #: ./doc/install-guide/section_cinder-node.xml153(para) msgid "" "Configure Block Storage to use your MySQL database. Edit the " "/etc/cinder/cinder.conf file and add the following key " "under the [database] section. Replace " "CINDER_DBPASS with the password you chose for the" " Block Storage database." msgstr "" #: ./doc/install-guide/section_cinder-node.xml158(para) #: ./doc/install-guide/section_cinder-controller.xml41(para) msgid "" "The /etc/cinder/cinder.conf file packaged with some " "distributions does not include the [database] section " "header. You must add this section header to the end of the file before " "proceeding further." msgstr "" #: ./doc/install-guide/section_cinder-node.xml164(replaceable) #: ./doc/install-guide/section_cinder-node.xml167(replaceable) #: ./doc/install-guide/section_cinder-controller.xml47(replaceable) #: ./doc/install-guide/section_cinder-controller.xml50(replaceable) #: ./doc/install-guide/section_cinder-controller.xml56(replaceable) #: ./doc/install-guide/section_cinder-controller.xml64(replaceable) #: ./doc/install-guide/section_cinder-controller.xml66(replaceable) msgid "CINDER_DBPASS" msgstr "" #: ./doc/install-guide/section_cinder-node.xml173(para) #: ./doc/install-guide/section_cinder-controller.xml162(para) msgid "Restart the cinder service with its new settings:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml180(para) msgid "" "Configure the ISCI target service to discover cinder volumes. Add the " "following line to the beginning of the " "/etc/tgt/targets.conf file, if it is not already " "present:" msgstr "" #: ./doc/install-guide/section_cinder-node.xml188(para) msgid "" "Start the cinder services and configure them to start when the system boots:" msgstr "" #: ./doc/install-guide/section_cinder-controller.xml5(title) msgid "Configure a Block Storage Service controller" msgstr "" #: ./doc/install-guide/section_cinder-controller.xml7(para) msgid "" "This section describes how to configure OpenStack Block Storage services on " "the Controller node and " "assumes that a second node provides storage through the cinder-volume service. For instructions on " "how to configure the second node, see ." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml19(para) msgid "Install the appropriate packages for the Block Storage Service:" msgstr "" #: ./doc/install-guide/section_cinder-controller.xml26(para) msgid "" "Respond to the prompts for database management, [keystone_authtoken] " "settings, RabbitMQ " "credentials and API " "endpoint registration." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml35(para) msgid "" "Configure Block Storage to use your MySQL database. Edit the " "/etc/cinder/cinder.conf file and add the following key " "under the [database] section. Replace " "CINDER_DBPASS with the password for the Block " "Storage database that you will create in a later step." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml53(para) msgid "" "To create the Block Storage Service database and tables and a " "cinder database user, run the command." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml59(para) msgid "" "Use the password that you set to log in as root to create a " "cinder database." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml69(para) msgid "Create the database tables for the Block Storage Service." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml74(para) msgid "" "Create a cinder user. The Block Storage Service uses this" " user to authenticate with the Identity Service. Use the " "service tenant and give the user the " "admin role." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml78(replaceable) msgid "cinder@example.com" msgstr "" #: ./doc/install-guide/section_cinder-controller.xml82(para) msgid "" "Add the credentials to the file /etc/cinder/api-" "paste.ini. Open the file in a text editor and locate the section " "[filter:authtoken]. Set the following options:" msgstr "" #: ./doc/install-guide/section_cinder-controller.xml134(para) msgid "" "Register the Block Storage Service with the Identity Service so that other " "OpenStack services can locate it. Register the service and specify the " "endpoint using the command." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml140(para) #: ./doc/install-guide/section_cinder-controller.xml153(para) msgid "" "Note the id property returned and use it to create the " "endpoint." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml149(para) msgid "" "Also register a service and endpoint for version 2 of the Block Storage " "Service API." msgstr "" #: ./doc/install-guide/section_cinder-controller.xml167(para) msgid "" "Start the cinder services and configure them to start when the system boots." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml8(title) msgid "" "OpenStack Installation Guide for Red Hat " "Enterprise Linux, CentOS, and Fedora for " "Ubuntu 12.04 (LTS) for Debian 7.0 " "(Wheezy) for openSUSE and SUSE Linux " "Enterprise Server" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml18(phrase) msgid "for Red Hat Enterprise Linux, CentOS, and Fedora" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml20(phrase) msgid "for Ubuntu 12.04 (LTS)" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml21(phrase) msgid "for openSUSE and SUSE Linux Enterprise Server" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml23(phrase) msgid "for Debian 7.0 (Wheezy)" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml17(titleabbrev) msgid "" "OpenStack Installation " "Guide" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml32(orgname) msgid "OpenStack" msgstr "OpenStack" #: ./doc/install-guide/bk_openstackinstallguide.xml36(year) msgid "2012" msgstr "2012" #: ./doc/install-guide/bk_openstackinstallguide.xml37(year) msgid "2013" msgstr "2013" #: ./doc/install-guide/bk_openstackinstallguide.xml38(holder) msgid "OpenStack Foundation" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml40(releaseinfo) msgid "havana" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml41(productname) msgid "OpenStack Installation Guide" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml45(remark) msgid "Copyright details are filled in by the template." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml50(para) msgid "" "The OpenStack® system consists of several key projects that you install " "separately but that work together depending on your cloud needs. These " "projects include Compute, Identity Service, Networking, Image Service, Block" " Storage Service, Object Storage, Telemetry, and Orchestration. You can " "install any of these projects separately and configure them standalone or as" " connected entities. This guide walks through an " "installation by using packages available through Debian 7.0 (code name: " "Wheezy).This guide walks through an " "installation by using packages available through Ubuntu 12.04 " "(LTS).This guide shows you how to" " install OpenStack by using packages available through Fedora 19 as well as " "on Red Hat Enterprise Linux and its derivatives through the EPEL " "repository.This guide shows you how to " "install OpenStack by using packages on openSUSE through the Open Build " "Service Cloud repository. Explanations of configuration options and" " sample configuration files are included." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml78(date) msgid "2013-10-25" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml82(para) msgid "Added initial Debian support." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml88(date) msgid "2013-10-17" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml92(para) msgid "Havana release." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml98(date) msgid "2013-10-16" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml102(para) msgid "Add support for SUSE Linux Enterprise." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml109(date) msgid "2013-10-08" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml113(para) msgid "Complete reorganization for Havana." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml120(date) msgid "2013-09-09" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml124(para) msgid "Build also for openSUSE." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml130(date) msgid "2013-08-01" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml134(para) msgid "" "Fixes to Object Storage verification steps. Fix bug 1207347." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml143(date) msgid "2013-07-25" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml147(para) msgid "" "Adds creation of cinder user and addition to the service tenant. Fix bug " "1205057." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml157(date) msgid "2013-05-08" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml161(para) msgid "Updated the book title for consistency." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml168(date) msgid "2013-05-02" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml172(para) msgid "Updated cover and fixed small errors in appendix." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml179(date) msgid "2013-04-30" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml183(para) msgid "Grizzly release." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml189(date) msgid "2013-04-18" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml193(para) msgid "Updates and clean up on the Object Storage installation." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml200(date) msgid "2013-04-08" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml204(para) msgid "" "Adds a note about availability of Grizzly packages on Ubuntu and Debian." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml212(date) msgid "2013-04-03" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml216(para) msgid "Updates RHEL/CentOS/Fedora information for Grizzly release." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml224(date) msgid "2013-03-26" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml228(para) msgid "Updates Dashboard (Horizon) information for Grizzly release." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml236(date) msgid "2013-02-12" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml240(para) msgid "" "Adds chapter about Essex to Folsom upgrade for Compute and related services " "(excludes OpenStack Object Storage (Swift) and OpenStack Networking " "(Quantum))." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml250(date) msgid "2013-01-16" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml254(para) msgid "Fix file copy issue for figures in the /common/ directory." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml261(date) msgid "2012-11-09" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml265(para) msgid "Folsom release of this document." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml272(date) msgid "2012-10-10" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml276(para) msgid "" "Doc bug fixes: 10544591064745" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml286(date) msgid "2012-09-26" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml290(para) msgid "Adds an all-in-one install section." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml297(date) msgid "2012-07-23" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml301(para) msgid "Adds additional detail about installing and configuring nova-volumes." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml306(para) msgid "" "Doc bug fixes: 9785101027230" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml317(date) msgid "2012-07-17" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml321(para) msgid "Update build process so two uniquely-named PDF files are output." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml329(date) msgid "2012-07-13" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml333(para) msgid "" "Doc bug fixes: 10258401025847" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml344(date) msgid "2012-06-19" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml348(para) msgid "Fix PDF links." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml351(para) msgid "" "Doc bug fixes: 967778984959, 1002294, 1010163." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml367(date) msgid "2012-05-31" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml371(para) msgid "Revise install guide to encompass more Linux distros." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml375(para) msgid "" "Doc bug fixes: 996988, 998116, 999005." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml387(date) msgid "2012-05-03" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml391(para) msgid "" "Fixes problems with glance-api-paste.ini and glance-registry-paste.ini samples and instructions." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml398(para) msgid "Removes \"DRAFT\" designation." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml404(date) msgid "2012-05-02" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml408(para) msgid "Essex release." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml414(date) msgid "2012-05-01" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml418(para) msgid "Updates the Object Storage and Identity (Keystone) configuration." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml426(date) msgid "2012-04-25" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml430(para) msgid "" "Changes service_id copy/paste error for the EC2 service-create command." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml433(para) msgid "Adds verification steps for Object Storage installation." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml435(para) msgid "" "Fixes proxy-server.conf file so it points to keystone " "not tempauth." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml444(date) msgid "2012-04-23" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml448(para) msgid "" "Adds installation and configuration for multi-node Object Storage service." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml456(date) msgid "2012-04-17" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml460(para) msgid "" "Doc bug fixes: 983417, 984106, 984034" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml472(date) msgid "2012-04-13" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml476(para) msgid "" "Doc bug fixes: 977905, 980882, 977823, adds additional Glance database " "preparation steps" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml490(date) msgid "2012-04-10" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml494(para) msgid "" "Doc bug fixes: 977831" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml502(date) msgid "2012-03-23" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml506(para) msgid "Updates for Xen hypervisor." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml512(date) msgid "2012-03-09" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml516(para) msgid "" "Updates for Essex release, includes new Glance config files, new Keystone " "configuration." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml524(date) msgid "2012-01-24" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml528(para) msgid "Initial draft for Essex." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml531(para) msgid "Assumes use of Ubuntu 12.04 repository." msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml540(date) msgid "2011-01-24" msgstr "" #: ./doc/install-guide/bk_openstackinstallguide.xml544(para) msgid "Initial draft for Diablo." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-install.xml21(None) msgid "" "@@image: 'figures/debconf-screenshots/neutron_1_plugin_selection.png'; " "md5=adf41c33778a691a560b7098908792db" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-install.xml113(None) msgid "" "@@image: 'figures/debconf-screenshots/neutron_2_networking_type.png'; " "md5=0d4d788a44ae0a716a503dca20b82f22" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_neutron-install.xml122(None) msgid "" "@@image: 'figures/debconf-screenshots/neutron_3_hypervisor_ip.png'; " "md5=2beb543a6334f641d7b69ac5dcbcb3a8" msgstr "" #: ./doc/install-guide/section_neutron-install.xml8(title) msgid "Install Networking services" msgstr "" #: ./doc/install-guide/section_neutron-install.xml9(para) msgid "" "When you install a Networking node, you must configure it for API endpoints," " RabbitMQ, keystone_authtoken, and the database. Use " "debconf to configure these values." msgstr "" #: ./doc/install-guide/section_neutron-install.xml13(para) msgid "" "When you install a Networking package, debconf prompts " "you to choose configuration options including which plug-in to use, as " "follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml25(para) msgid "" "This parameter sets the core_plugin option value in " "the /etc/neutron/neutron.conf file." msgstr "" #: ./doc/install-guide/section_neutron-install.xml29(para) msgid "" "When you install the neutron-common package, all plug-ins" " are installed by default." msgstr "" #: ./doc/install-guide/section_neutron-install.xml32(para) msgid "" "This table lists the values for the core_plugin " "option. These values depend on your response to the " "debconf prompt." msgstr "" #: ./doc/install-guide/section_neutron-install.xml36(caption) msgid "Plug-ins and the core_plugin option" msgstr "" #: ./doc/install-guide/section_neutron-install.xml39(th) msgid "Plug-in" msgstr "" #: ./doc/install-guide/section_neutron-install.xml41(filename) msgid "neutron.conf" msgstr "" #: ./doc/install-guide/section_neutron-install.xml40(th) msgid "core_plugin value in " msgstr "" #: ./doc/install-guide/section_neutron-install.xml46(para) msgid "BigSwitch" msgstr "" #: ./doc/install-guide/section_neutron-install.xml47(para) msgid "neutron.plugins.bigswitch.plugin.NeutronRestProxyV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml50(para) msgid "Brocade" msgstr "" #: ./doc/install-guide/section_neutron-install.xml51(para) msgid "neutron.plugins.brocade.NeutronPlugin.BrocadePluginV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml54(para) msgid "Cisco" msgstr "Cisco" #: ./doc/install-guide/section_neutron-install.xml55(para) msgid "neutron.plugins.cisco.network_plugin.PluginV2" msgstr "neutron.plugins.cisco.network_plugin.PluginV2" #: ./doc/install-guide/section_neutron-install.xml58(para) msgid "Hyper-V" msgstr "Hyper-V" #: ./doc/install-guide/section_neutron-install.xml59(para) msgid "neutron.plugins.hyperv.hyperv_neutron_plugin.HyperVNeutronPlugin" msgstr "" #: ./doc/install-guide/section_neutron-install.xml62(para) msgid "LinuxBridge" msgstr "" #: ./doc/install-guide/section_neutron-install.xml63(para) msgid "neutron.plugins.linuxbridge.lb_neutron_plugin.LinuxBridgePluginV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml66(para) msgid "Mellanox" msgstr "" #: ./doc/install-guide/section_neutron-install.xml67(para) msgid "neutron.plugins.mlnx.mlnx_plugin.MellanoxEswitchPlugin" msgstr "" #: ./doc/install-guide/section_neutron-install.xml70(para) msgid "MetaPlugin" msgstr "" #: ./doc/install-guide/section_neutron-install.xml71(para) msgid "neutron.plugins.metaplugin.meta_neutron_plugin.MetaPluginV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml74(para) msgid "Midonet" msgstr "Midonet" #: ./doc/install-guide/section_neutron-install.xml75(para) msgid "neutron.plugins.midonet.plugin.MidonetPluginV2" msgstr "neutron.plugins.midonet.plugin.MidonetPluginV2" #: ./doc/install-guide/section_neutron-install.xml78(para) msgid "ml2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml79(para) msgid "neutron.plugins.ml2.plugin.Ml2Plugin" msgstr "" #: ./doc/install-guide/section_neutron-install.xml82(para) msgid "Nec" msgstr "Nec" #: ./doc/install-guide/section_neutron-install.xml83(para) msgid "neutron.plugins.nec.nec_plugin.NECPluginV2" msgstr "neutron.plugins.nec.nec_plugin.NECPluginV2" #: ./doc/install-guide/section_neutron-install.xml86(para) msgid "OpenVSwitch" msgstr "" #: ./doc/install-guide/section_neutron-install.xml87(para) msgid "neutron.plugins.openvswitch.ovs_neutron_plugin.OVSNeutronPluginV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml90(para) msgid "PLUMgrid" msgstr "" #: ./doc/install-guide/section_neutron-install.xml91(para) msgid "" "neutron.plugins.plumgrid.plumgrid_nos_plugin.plumgrid_plugin.NeutronPluginPLUMgridV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml94(para) msgid "RYU" msgstr "" #: ./doc/install-guide/section_neutron-install.xml95(para) msgid "neutron.plugins.ryu.ryu_neutron_plugin.RyuNeutronPluginV2" msgstr "" #: ./doc/install-guide/section_neutron-install.xml99(para) msgid "" "Depending on the value of core_plugin, the start-up " "scripts start the daemons by using the corresponding plug-in configuration " "file directly. For example, if you selected the Open vSwitch plug-in, neutron-server automatically launches with --config-file " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." msgstr "" #: ./doc/install-guide/section_neutron-install.xml106(para) msgid "" "The neutron-common package also prompts you for the " "default network configuration:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml126(para) msgid "" "Before you configure individual nodes for Networking, you must create the " "required OpenStack components: user, service, database, and one or more " "endpoints. After you complete these steps on the controller node, follow the" " instructions in this guide to set up OpenStack Networking nodes." msgstr "" #. TODO(sross): move this into its own section #: ./doc/install-guide/section_neutron-install.xml136(para) msgid "" "Use the password that you set previously to log in as root and create a " "neutron database:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml146(para) msgid "" "Create the required user, service, and endpoint so that Networking can " "interface with the Identity Service." msgstr "" #: ./doc/install-guide/section_neutron-install.xml148(para) msgid "Create a neutron user:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml149(replaceable) msgid "neutron@example.com" msgstr "" #: ./doc/install-guide/section_neutron-install.xml150(para) msgid "Add the user role to the neutron user:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml152(para) msgid "Create the neutron service:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml155(para) msgid "" "Create a Networking endpoint. Use the id property for the" " service that was returned in the previous step to create the endpoint:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml166(title) msgid "Install Networking services on a dedicated network node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml169(para) msgid "" "Before you start, set up a machine as a dedicated network node. Dedicated " "network nodes have a MGMT_INTERFACE NIC, a " "DATA_INTERFACE NIC, and a " "EXTERNAL_INTERFACE NIC." msgstr "" #: ./doc/install-guide/section_neutron-install.xml174(para) msgid "" "The management network handles communication among nodes. The data network " "handles communication coming to and from VMs. The external NIC connects the " "network node, and optionally to the controller node, so your VMs can connect" " to the outside world." msgstr "" #: ./doc/install-guide/section_neutron-install.xml179(para) msgid "" "All NICs must have static IPs. However, the data and external NICs have a " "special set up. For details about Networking plug-ins, see ." msgstr "" #: ./doc/install-guide/section_neutron-install.xml185(para) msgid "" "By default, the system-config-firewall automated firewall" " configuration tool is in place on RHEL. This graphical interface (and a " "curses-style interface with -tui on the end of the name) " "enables you to configure IP tables as a basic firewall. You should disable " "it when you work with Networking unless you are familiar with the underlying" " network technologies, as, by default, it blocks various types of network " "traffic that are important to Networking. To disable it, simply launch the " "program and clear the Enabled check box." msgstr "" #: ./doc/install-guide/section_neutron-install.xml195(para) msgid "" "After you successfully set up OpenStack Networking, you can re-enable and " "configure the tool. However, during Networking set up, disable the tool to " "make it easier to debug network issues." msgstr "" #: ./doc/install-guide/section_neutron-install.xml202(para) msgid "Install the Networking packages and any dependencies." msgstr "" #: ./doc/install-guide/section_neutron-install.xml210(para) msgid "" "Respond to prompts for database " "management, [keystone_authtoken] " "settings, RabbitMQ " "credentials and API " "endpoint registration." msgstr "" #: ./doc/install-guide/section_neutron-install.xml221(para) msgid "Configure basic Networking-related services to start at boot time:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml227(para) msgid "" "Enable packet forwarding and disable packet destination filtering so that " "the network node can coordinate traffic for the VMs. Edit the " "/etc/sysctl.conf file, as follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml234(para) msgid "" "Use the command to ensure the changes made to the " "/etc/sysctl.conf file take effect:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml239(para) msgid "" "It is recommended that the networking service is restarted after changing " "values related to the networking configuration. This ensures that all " "modified values take effect immediately:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml248(para) #: ./doc/install-guide/section_neutron-install.xml829(para) #: ./doc/install-guide/section_neutron-install.xml1223(para) msgid "" "Configure Networking to use keystone for authentication:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml251(para) #: ./doc/install-guide/section_neutron-install.xml276(para) #: ./doc/install-guide/section_neutron-install.xml832(para) #: ./doc/install-guide/section_neutron-install.xml1226(para) msgid "" "Set the auth_strategy configuration key to " "keystone in the DEFAULT section of the" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml257(para) #: ./doc/install-guide/section_neutron-install.xml838(para) #: ./doc/install-guide/section_neutron-install.xml1232(para) msgid "" "Set the neutron configuration for" " keystone authentication:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml272(para) msgid "" "To configure neutron to use " "keystone for authentication, edit" " the /etc/neutron/neutron.conffile." msgstr "" #: ./doc/install-guide/section_neutron-install.xml282(para) msgid "" "Add these lines to the keystone_authtoken section of the " "file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml295(para) #: ./doc/install-guide/section_neutron-install.xml894(para) #: ./doc/install-guide/section_neutron-install.xml1342(para) msgid "" "Set the root_helper configuration in the " "[agent] section of " "/etc/neutron/neutron.conf:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml312(para) msgid "" "Configure the RabbitMQ access. Edit the " "/etc/neutron/neutron.conf file to modify the following " "parameters in the DEFAULT section." msgstr "" #: ./doc/install-guide/section_neutron-install.xml339(para) #: ./doc/install-guide/section_neutron-install.xml905(para) msgid "" "Configure Networking to connect to the database. Edit the " "[database] section in the same file, as follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml346(para) #: ./doc/install-guide/section_neutron-install.xml923(para) #: ./doc/install-guide/section_neutron-install.xml1290(para) msgid "" "Configure the /etc/neutron/api-paste.ini file for " "keystone authentication:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml362(para) #: ./doc/install-guide/section_neutron-install.xml912(para) msgid "" "Edit the /etc/neutron/api-paste.ini file and add these " "lines to the [filter:authtoken] section:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml373(para) msgid "" "keystoneclient.middleware.auth_token: You must configure " "auth_uri to point to the public identity endpoint. " "Otherwise, clients might not be able to authenticate against an admin " "endpoint." msgstr "" #: ./doc/install-guide/section_neutron-install.xml380(para) msgid "" "Configure your network plug-in. For instructions, see instructions. Then, return here." msgstr "" #: ./doc/install-guide/section_neutron-install.xml385(para) msgid "" "Install and configure a networking plug-in. OpenStack Networking uses this " "plug-in to perform software-defined networking. See for further details. Then, return here when " "finished." msgstr "" #: ./doc/install-guide/section_neutron-install.xml391(para) msgid "" "Now that you've installed and configured a plug-in, it is time to configure " "the remaining parts of OpenStack Networking." msgstr "" #: ./doc/install-guide/section_neutron-install.xml395(para) msgid "" "To perform DHCP on the software-defined networks, Networking supports " "several different plug-ins. However, in general, you use the " "dnsmasq plug-in." msgstr "" #: ./doc/install-guide/section_neutron-install.xml398(para) msgid "Configure the /etc/neutron/dhcp_agent.ini file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml407(para) msgid "" "To allow virtual machines to access the Compute metadata information, the " "Networking metadata agent must be enabled and configured. The agent will act" " as a proxy for the Compute metadata service." msgstr "" #: ./doc/install-guide/section_neutron-install.xml411(para) msgid "" "On the controller, edit the /etc/nova/nova.conf file to" " define a secret key that will be shared between the Compute Service and the" " Networking metadata agent." msgstr "" #: ./doc/install-guide/section_neutron-install.xml415(para) msgid "Add to the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml418(replaceable) #: ./doc/install-guide/section_neutron-install.xml424(replaceable) #: ./doc/install-guide/section_neutron-install.xml443(replaceable) #: ./doc/install-guide/section_neutron-install.xml459(replaceable) msgid "METADATA_PASS" msgstr "" #: ./doc/install-guide/section_neutron-install.xml420(para) msgid "Set the neutron_metadata_proxy_shared_secret key:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml427(para) msgid "Restart the nova-api service:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml431(para) msgid "On the network node, modify the metadata agent configuration." msgstr "" #: ./doc/install-guide/section_neutron-install.xml433(para) msgid "" "Edit the /etc/neutron/metadata_agent.ini file and " "modify the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml444(para) msgid "Set the required keys:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml461(para) msgid "" "The value of auth_region is case-sensitive and must match" " the endpoint region defined in Keystone." msgstr "" #: ./doc/install-guide/section_neutron-install.xml467(para) #: ./doc/install-guide/section_neutron-install.xml1431(para) msgid "" "The neutron-server initialization" " script expects a symbolic link /etc/neutron/plugin.ini" " pointing to the configuration file associated with your chosen plug-in. " "Using Open vSwitch, for example, the symbolic link must point to " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini." " If this symbolic link does not exist, create it using the following " "commands:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml479(para) #: ./doc/install-guide/section_neutron-install.xml1443(para) msgid "" "The openstack-neutron " "initialization script expects the variable " "NEUTRON_PLUGIN_CONF in file " "/etc/sysconfig/neutron to reference the configuration " "file associated with your chosen plug-in. Using Open vSwitch, for example, " "edit the /etc/sysconfig/neutron file and add the " "following:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml490(para) msgid "Restart Networking services." msgstr "" #: ./doc/install-guide/section_neutron-install.xml500(para) #: ./doc/install-guide/section_neutron-install.xml1023(para) msgid "" "Also restart your chosen Networking plug-in agent, for example, Open " "vSwitch." msgstr "" #: ./doc/install-guide/section_neutron-install.xml506(para) msgid "" "After you configure the compute and controller nodes, configure the base networks." msgstr "" #: ./doc/install-guide/section_neutron-install.xml516(title) msgid "Install and configure the Networking plug-ins" msgstr "" #: ./doc/install-guide/section_neutron-install.xml518(title) msgid "Install the Open vSwitch (OVS) plug-in" msgstr "" #: ./doc/install-guide/section_neutron-install.xml521(para) #: ./doc/install-guide/section_neutron-install.xml1037(para) msgid "Install the Open vSwitch plug-in and its dependencies:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml527(para) msgid "" "On Ubuntu 12.04 LTS with GRE you must install openvswitch-datapath-dkms and " "restart the service to enable the GRE flow so that OVS 1.10 and higher is " "used. Make sure you are running the OVS 1.10 kernel module in addition to " "the OVS 1.10 user space. Both the kernel module and user space are required " "for VXLAN support. The error you see in the /var/log" "/openvswitchovs-vswitchd.log log file is \"Stderr: 'ovs-ofctl: " "-1: negative values not supported for in_port\\n'\". If you see this error, " "make sure shows the right version. Also check the output " "from for the version of the OVS module being loaded." msgstr "" #: ./doc/install-guide/section_neutron-install.xml544(para) msgid "Start Open vSwitch:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml548(para) msgid "And configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml554(para) msgid "" "No matter which networking technology you use, you must add the br-" "int integration bridge, which connects to the VMs, and the " "br-ex external bridge, which connects to the outside " "world." msgstr "" #: ./doc/install-guide/section_neutron-install.xml563(para) msgid "" "Add a port (connection) from the " "EXTERNAL_INTERFACE interface to br-" "ex interface:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml566(replaceable) #: ./doc/install-guide/section_neutron-install.xml573(replaceable) msgid "EXTERNAL_INTERFACE" msgstr "" #: ./doc/install-guide/section_neutron-install.xml568(para) msgid "" "The host must have an IP address associated with an interface other than " "EXTERNAL_INTERFACE, and your remote terminal " "session must be associated with this other IP address." msgstr "" #: ./doc/install-guide/section_neutron-install.xml572(para) msgid "" "If you associate an IP address with " "EXTERNAL_INTERFACE, that IP address stops working" " after you issue the command. If you associate a remote " "terminal session with that IP address, you lose connectivity with the host." msgstr "" #: ./doc/install-guide/section_neutron-install.xml576(para) msgid "" "For more details about this behavior, see the Configuration " "Problems section of the Open vSwitch " "FAQ." msgstr "" #: ./doc/install-guide/section_neutron-install.xml583(para) msgid "" "Configure the EXTERNAL_INTERFACE without an IP " "address and in promiscuous mode. Additionally, you must set the newly " "created br-ex interface to have the IP address that " "formerly belonged to EXTERNAL_INTERFACE." msgstr "" #: ./doc/install-guide/section_neutron-install.xml590(para) msgid "" "Generic Receive Offload (GRO) should not be enabled on this interface as it " "can cause severe performance problems. It can be disabled with the ethtool " "utility." msgstr "" #: ./doc/install-guide/section_neutron-install.xml595(para) msgid "" "Edit the /etc/sysconfig/network-scripts/ifcfg-" "EXTERNAL_INTERFACE file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml604(para) msgid "" "Create and edit the /etc/sysconfig/network-scripts/ifcfg-br-" "ex file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml617(para) msgid "" "You must set some common configuration options no matter which networking " "technology you choose to use with Open vSwitch. Configure the L3 and DHCP " "agents to use OVS and namespaces. Edit the " "/etc/neutron/l3_agent.ini and " "/etc/neutron/dhcp_agent.ini files, respectively:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml626(para) msgid "" "You must enable veth support if you use certain kernels. Some kernels, such " "as recent versions of RHEL (not RHOS) and CentOS, only partially support " "namespaces. Edit the previous files, as follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml634(para) msgid "" "Similarly, you must also tell Neutron core to use OVS. " "Edit the /etc/neutron/neutron.conf file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml641(para) msgid "" "Choose a networking technology to create the virtual networks. Neutron " "supports GRE tunneling, VLANs, and VXLANs. This guide shows how to configure" " GRE tunneling and VLANs." msgstr "" #: ./doc/install-guide/section_neutron-install.xml645(para) msgid "" "GRE " "tunneling is simpler to set up because it does not require any " "special configuration from any physical network hardware. However, its " "protocol makes it difficult to filter traffic on the physical network. " "Additionally, this configuration does not use namespaces. You can have only " "one router for each network node. However, you can enable namespacing, and " "potentially veth, as described in the section detailing how to use VLANs " "with OVS)." msgstr "" #: ./doc/install-guide/section_neutron-install.xml656(para) msgid "" "On the other hand, VLAN tagging modifies the ethernet header of packets. " "You can filter packets on the physical network through normal methods. " "However, not all NICs handle the increased packet size of VLAN-tagged " "packets well, and you might need to complete additional configuration on " "physical network hardware to ensure that your Neutron VLANs do not interfere" " with any other VLANs on your network and that any physical network hardware" " between nodes does not strip VLAN tags." msgstr "" #: ./doc/install-guide/section_neutron-install.xml668(para) msgid "" "While the examples in this guide enable network namespaces by default, you " "can disable them if issues occur or your kernel does not support them. Edit " "the /etc/neutron/l3_agent.ini and " "/etc/neutron/dhcp_agent.ini files, respectively:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml675(para) msgid "" "Edit the /etc/neutron/neutron.conf file to disable " "overlapping IP addresses:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml679(para) msgid "" "Note that when network namespaces are disabled, you can have only one router" " for each network node and overlapping IP addresses are not supported." msgstr "" #: ./doc/install-guide/section_neutron-install.xml682(para) msgid "" "You must complete additional steps after you create the initial Neutron " "virtual networks and router." msgstr "" #: ./doc/install-guide/section_neutron-install.xml689(para) msgid "" "Configure a firewall plug-in. If you do not wish to enforce firewall rules, " "called security groups by" " OpenStack, you can use " "neutron.agent.firewall.NoopFirewall. Otherwise, you can " "choose one of the Networking firewall plug-ins. The most common choice is " "the Hybrid OVS-IPTables driver, but you can also use the Firewall-" "as-a-Service driver. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml704(para) #: ./doc/install-guide/section_neutron-install.xml1098(para) msgid "" "You must use at least the No-Op firewall. Otherwise, Horizon and other " "OpenStack services cannot get and set required VM boot options." msgstr "" #: ./doc/install-guide/section_neutron-install.xml711(para) #: ./doc/install-guide/section_neutron-install.xml1104(para) msgid "Configure the OVS plug-in to start on boot." msgstr "" #: ./doc/install-guide/section_neutron-install.xml717(para) #: ./doc/install-guide/section_neutron-install.xml1110(para) #: ./doc/install-guide/section_neutron-install.xml1137(para) #: ./doc/install-guide/section_neutron-install.xml1505(para) #: ./doc/install-guide/section_neutron-install.xml1668(para) msgid "Now, return to the general OVS instructions." msgstr "" #: ./doc/install-guide/section_neutron-install.xml722(title) msgid "Configure the Neutron OVS plug-in for GRE tunneling" msgstr "" #: ./doc/install-guide/section_neutron-install.xml726(para) msgid "" "Configure the OVS plug-in to use GRE tunneling, the " "br-int integration bridge, the br-tun " "tunneling bridge, and a local IP for the " "DATA_INTERFACE tunnel IP. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml743(para) #: ./doc/install-guide/section_neutron-install.xml1165(para) #: ./doc/install-guide/section_neutron-install.xml1525(para) #: ./doc/install-guide/section_neutron-install.xml1544(para) msgid "Return to the general OVS instructions." msgstr "" #: ./doc/install-guide/section_neutron-install.xml749(title) msgid "Configure the Neutron OVS plug-in for VLANs" msgstr "" #: ./doc/install-guide/section_neutron-install.xml753(para) msgid "" "Configure OVS to use VLANS. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml763(para) msgid "" "Create the bridge for DATA_INTERFACE and add " "DATA_INTERFACE to it:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml771(para) msgid "" "Transfer the IP address for DATA_INTERFACE to the" " bridge in the same way that you transferred the " "EXTERNAL_INTERFACE IP address to br-" "ex. However, do not turn on promiscuous mode." msgstr "" #: ./doc/install-guide/section_neutron-install.xml779(para) msgid "Return to the OVS general instruction." msgstr "" #: ./doc/install-guide/section_neutron-install.xml788(title) msgid "Install networking support on a dedicated compute node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml791(para) msgid "" "This section details set up for any node that runs the nova-" "compute component but does not run the full network stack." msgstr "" #: ./doc/install-guide/section_neutron-install.xml796(para) #: ./doc/install-guide/section_neutron-install.xml1185(para) msgid "" "By default, the system-config-firewall automated firewall" " configuration tool is in place on RHEL. This graphical interface (and a " "curses-style interface with -tui on the end of the name) " "enables you to configure IP tables as a basic firewall. You should disable " "it when you work with Neutron unless you are familiar with the underlying " "network technologies, as, by default, it blocks various types of network " "traffic that are important to Neutron. To disable it, simple launch the " "program and clear the Enabled check box." msgstr "" #: ./doc/install-guide/section_neutron-install.xml806(para) #: ./doc/install-guide/section_neutron-install.xml1195(para) msgid "" "After you successfully set up OpenStack with Neutron, you can re-enable and " "configure the tool. However, during Neutron set up, disable the tool to make" " it easier to debug network issues." msgstr "" #: ./doc/install-guide/section_neutron-install.xml813(para) msgid "" "Disable packet destination filtering (route verification) to let the " "networking services route traffic to the VMs. Edit the " "/etc/sysctl.conf file and run the following command to " "activate changes:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml823(para) msgid "" "Install and configure your networking plug-in components. To install and " "configure the network plug-in that you chose when you set up your network " "node, see ." msgstr "" #: ./doc/install-guide/section_neutron-install.xml877(para) msgid "" "Configure the core components of Neutron. Edit the " "/etc/neutron/neutron.conf file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml937(para) #: ./doc/install-guide/section_neutron-install.xml1356(para) msgid "" "Configure OpenStack Compute to use OpenStack Networking services. Configure " "the /etc/nova/nova.conf file as per instructions below:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml960(para) #: ./doc/install-guide/section_neutron-install.xml1379(para) msgid "" "Configure OpenStack Compute to use OpenStack Networking services. Edit the " "/etc/nova/nova.conf file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml976(para) msgid "" "No matter which firewall driver you chose when you configured the network " "and compute nodes, you must edit the " "/etc/nova/nova.conf file to set the firewall driver to " "nova.virt.firewall.NoopFirewallDriver. Because OpenStack " "Networking handles the firewall, this statement instructs Compute to not use" " a firewall." msgstr "" #: ./doc/install-guide/section_neutron-install.xml986(para) msgid "" "If you want Networking to handle the firewall, edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file to set the firewall_driver option to the firewall for the" " plug-in. For example, with OVS, edit the file as " "follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1001(para) msgid "" "If you do not want to use a firewall in Compute or Networking, edit both " "configuration files and set " "firewall_driver=nova.virt.firewall.NoopFirewallDriver. Also, " "edit the /etc/nova/nova.conf file and comment out or " "remove the security_group_api=neutron statement." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1009(para) msgid "" "Otherwise, when you issue commands, the ERROR: " "The server has either erred or is incapable of performing the requested " "operation. (HTTP 500) error might be returned." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1019(para) #: ./doc/install-guide/section_nova-compute.xml239(para) msgid "Restart the Compute service." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1030(title) msgid "Install and configure Neutron plug-ins on a dedicated compute node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1033(title) msgid "Install the Open vSwitch (OVS) plug-in on a dedicated compute node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1044(para) msgid "Restart Open vSwitch:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1048(para) msgid "Start Open vSwitch and configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1056(para) msgid "" "You must set some common configuration options no matter which networking " "technology you choose to use with Open vSwitch. You must add the br-int integration bridge, which connects to the VMs." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1064(para) msgid "" "You must set some common configuration options. You must configure " "Networking core to use OVS. Edit the " "/etc/neutron/neutron.conf file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1076(para) msgid "" "Configure the networking type that you chose when you set up the network " "node: either GRE tunneling or VLANs." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1085(para) msgid "" "You must configure a firewall as well. You should use the same firewall " "plug-in that you chose to use when you set up the network node. To do this, " "edit " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file and set the firewall_driver value under the " "securitygroup to the same value used on the network node." " For instance, if you chose to use the Hybrid OVS-IPTables plug-in, your " "configuration looks like this:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1116(title) msgid "" "Configure the Neutron OVS plug-in for GRE tunneling on a " "dedicated compute node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1120(para) msgid "" "Tell the OVS plug-in to use GRE tunneling with a br-int integration bridge, a br-tun tunneling " "bridge, and a local IP for the tunnel of " "DATA_INTERFACE's IP Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1134(replaceable) msgid "DATA_INTERFACE_IP" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1144(title) msgid "" "Configure the Neutron OVS plug-in for VLANs on a " "dedicated compute node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1148(para) msgid "" "Tell OVS to use VLANs. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1154(replaceable) msgid "DATA_INTERFACE" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1157(para) msgid "" "Create the bridge for the DATA_INTERFACE and add " "DATA_INTERFACE to it, the same way you did on the" " network node:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1174(title) msgid "Install networking support on a dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1177(para) msgid "" "This is for a node which runs the control components of Neutron, but does " "not run any of the components that provide the underlying functionality " "(such as the plug-in agent or the L3 agent). If you wish to have a combined " "controller/compute node follow these instructions, and then those for the " "compute node." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1202(para) msgid "Install the server component of Networking and any dependencies." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1213(para) msgid "" "Configure Networking to use your MySQL database. Edit the " "/etc/neutron/neutron.conf file and add the following " "key under the [database] section. Replace " "NEUTRON_DBPASS with the password you chose for " "the Neutron database." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1247(para) msgid "" "Configure Networking to use keystone as the Identity Service for " "authentication." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1251(para) msgid "" "Edit the /etc/neutron/neutron.conf file and add the " "following key under the [DEFAULT] section." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1258(para) msgid "" "Add the following keys under the [keystone_authtoken] " "section. Replace NEUTRON_PASS with the password " "you chose for the Neutron user in Keystone." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1275(para) msgid "" "Edit the /etc/neutron/api-paste.ini file and add the " "following keys under the [filter:authtoken] section. " "Replace NEUTRON_PASS with the password you chose " "for the Neutron user in Keystone." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1328(para) msgid "" "Configure Networking to use your message broker. Edit the " "/etc/neutron/neutron.conf file and add the following " "keys under the [DEFAULT] section." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1332(para) msgid "" "Replace RABBIT_PASS with the password you chose " "for RabbitMQ." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1348(para) msgid "" "Although the controller node does not run any Networking agents, you must " "install and configure the same plug-in that you configured on the network " "node." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1351(link) msgid "" "Install and configure the Networking plug-ins on a dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1395(para) msgid "" "Regardless of which firewall driver you chose when you configured the " "network and compute nodes, set this driver as the No-Op firewall. This " "firewall is a nova firewall, and " "because neutron handles the " "Firewall, you must tell nova not " "to use one." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1402(para) msgid "" "When Networking handles the firewall, the option " "firewall_driver should be set according to the specified plug-" "in. For example with OVS, edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1416(para) msgid "" "If you do not want to use a firewall in Compute or Networking, set " "firewall_driver=nova.virt.firewall.NoopFirewallDriver in both " "config files, and comment out or remove " "security_group_api=neutron in the " "/etc/nova/nova.conf file, otherwise you may encounter " "ERROR: The server has either erred or is incapable of performing " "the requested operation. (HTTP 500) when issuing " " commands." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1454(para) msgid "" "Start neutron-server and set it " "to start at boot:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1463(para) msgid "Restart neutron-server:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1469(title) msgid "" "Install and configure the Neutron plug-ins on a dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1472(title) msgid "Install the Open vSwitch (OVS) plug-in on a dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1476(para) msgid "Install the Open vSwitch plug-in:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1482(para) msgid "" "You must set some common configuration options no matter which networking " "technology you choose to use with Open vSwitch. You must configure " "Networking core to use OVS. Edit the " "/etc/neutron/neutron.conf file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1491(para) msgid "" "Configure the OVS plug-in for the networking type that " "you chose when you configured the network node: GRE tunneling or VLANs." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1500(para) msgid "" "The dedicated controller node does not need to run Open vSwitch or the Open " "vSwitch agent." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1511(title) msgid "" "Configure the Neutron OVS plug-in for GRE tunneling on a " "dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1515(para) msgid "" "Tell the OVS plug-in to use GRE tunneling. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1532(title) msgid "" "Configure the Neutron OVS plug-in for VLANs on a " "dedicated controller node" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1536(para) msgid "" "Tell OVS to use VLANS. Edit the " "/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini" " file, as follows:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1553(title) msgid "Create the base Neutron networks" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1555(para) msgid "" "In these sections, replace SPECIAL_OPTIONS with " "any options specific to your Networking plug-in choices. See here to " "check if your plug-in requires any special options." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1564(para) msgid "" "Create the ext-net external network. This network " "represents a slice of the outside world. VMs are not directly linked to this" " network; instead, they connect to internal networks. Outgoing traffic is " "routed by Neutron to the external network. Additionally, floating IP " "addresses from the subnet for ext-net might be assigned " "to VMs so that the external network can contact them. Neutron routes the " "traffic appropriately." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1573(replaceable) #: ./doc/install-guide/section_neutron-install.xml1618(replaceable) msgid "SPECIAL_OPTIONS" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1576(para) msgid "" "Create the associated subnet with the same gateway and CIDR as " "EXTERNAL_INTERFACE. It does not have DHCP because" " it represents a slice of the external world:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1581(replaceable) msgid "FLOATING_IP_START" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1581(replaceable) msgid "FLOATING_IP_END" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1582(replaceable) msgid "EXTERNAL_INTERFACE_GATEWAY" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1583(replaceable) msgid "EXTERNAL_INTERFACE_CIDR" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1586(para) msgid "Create one or more initial tenants, for example:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1587(replaceable) #: ./doc/install-guide/section_neutron-install.xml1602(replaceable) msgid "DEMO_TENANT" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1588(para) msgid "See for further details." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1590(para) msgid "See for further details." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1594(para) msgid "" "Create the router attached to the external network. This router routes " "traffic to the internal subnets as appropriate. You can create it under a " "given tenant: Append --tenant-id option with a value of " "DEMO_TENANT_ID to the command." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1600(para) msgid "" "Use the following to quickly get the DEMO_TENANT " "tenant-id:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1603(para) msgid "Then create the router:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1604(replaceable) #: ./doc/install-guide/section_neutron-install.xml1618(replaceable) #: ./doc/install-guide/section_neutron-install.xml1619(replaceable) msgid "DEMO_TENANT_ID" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1607(para) msgid "" "Connect the router to ext-net by setting the gateway for " "the router as ext-net:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1610(replaceable) #: ./doc/install-guide/section_neutron-install.xml1620(replaceable) #: ./doc/install-guide/section_neutron-install.xml1651(replaceable) msgid "EXT_TO_INT_ID" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1610(replaceable) #: ./doc/install-guide/section_neutron-install.xml1650(replaceable) msgid "EXT_NET_ID" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1613(para) msgid "" "Create an internal network for DEMO_TENANT (and " "associated subnet over an arbitrary internal IP range, such as, " "10.5.5.0/24), and connect it to the router by setting it " "as a port:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1620(replaceable) msgid "DEMO_NET_SUBNET_ID" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1623(para) msgid "" "Check the special options page for your plug-in for remaining steps. Now, " "return to the general OVS instructions." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1630(title) msgid "Plug-in-specific Neutron network options" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1633(title) msgid "Open vSwitch Network configuration options" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1636(title) msgid "GRE tunneling network options" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1638(para) msgid "" "While this guide currently enables network namespaces by default, you can " "disable them if you have issues or your kernel does not support them. If you" " disabled namespaces, you must perform some additional configuration for the" " L3 agent." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1643(para) msgid "" "After you create all the networks, tell the L3 agent what the external " "network ID is, as well as the ID of the router associated with this machine " "(because you are not using namespaces, there can be only one router for each" " machine). To do this, edit the " "/etc/neutron/l3_agent.ini file:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1652(para) msgid "Then, restart the L3 agent:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1655(para) msgid "When creating networks, you should use the options:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1658(para) msgid "" "SEG_ID should be 2 for the " "external network, and just any unique number inside the tunnel range " "specified before for any other network." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1663(para) msgid "" "These options are not needed beyond the first network, as Neutron " "automatically increments the segmentation id and copy the network type " "option for any additional networks." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1673(title) msgid "VLAN network options" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1674(para) msgid "When creating networks, use these options:" msgstr "" #: ./doc/install-guide/section_neutron-install.xml1676(para) msgid "" "SEG_ID should be 2 for the " "external network, and just any unique number inside the vlan range specified" " above for any other network." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1681(para) msgid "" "These options are not needed beyond the first network, as Neutron " "automatically increments the segmentation ID and copies the network type and" " physical network options for any additional networks. They are only needed " "if you wish to modify those values in any way." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1689(para) msgid "" "Some NICs have Linux drivers that do not handle VLANs properly. See the " "ovs-vlan-bug-workaround and ovs-vlan-" "test man pages for more information. Additionally, you might try " "turning off rx-vlan-offload and tx-vlan-" "offload by using ethtool on the " "DATA_INTERFACE. Another potential caveat to VLAN " "functionality is that VLAN tags add an additional 4 bytes to the packet " "size. If your NICs cannot handle large packets, make sure to set the MTU to " "a value that is 4 bytes less than the normal value on the " "DATA_INTERFACE." msgstr "" #: ./doc/install-guide/section_neutron-install.xml1704(para) msgid "" "If you run OpenStack inside a virtualized environment (for testing " "purposes), switching to the virtio NIC type (or a similar" " technology if you are not using KVM/QEMU to run your host VMs) might solve " "the issue." msgstr "" #: ./doc/install-guide/ch_debconf.xml6(title) msgid "Configure OpenStack with debconf" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/ch_overview.xml57(None) msgid "" "@@image: 'figures/basic-architecture.svg'; " "md5=33d7a8c99d42020ff657f85d80cc06bd" msgstr "" #: ./doc/install-guide/ch_overview.xml6(title) msgid "Architecture" msgstr "Architektura" #: ./doc/install-guide/ch_overview.xml7(para) msgid "" "This install guide offers a few of the many ways to install OpenStack " "components and have them work together. It is meant as a \"choose your own " "adventure\" guide, not a comprehensive guide. The OpenStack " "Configuration Reference lists every option in all OpenStack " "services. Before you begin an installation adventure, here are some things " "you should know about OpenStack concepts." msgstr "" #: ./doc/install-guide/ch_overview.xml25(title) msgid "Example architectures" msgstr "" #: ./doc/install-guide/ch_overview.xml26(para) msgid "" "This guide enables you to choose your own OpenStack adventure. OpenStack is " "highly configurable to meet different needs with various compute, " "networking, and storage options." msgstr "" #: ./doc/install-guide/ch_overview.xml29(para) msgid "This guide uses the following example architectures:" msgstr "" #: ./doc/install-guide/ch_overview.xml32(para) #: ./doc/install-guide/ch_overview.xml53(title) msgid "Basic architecture with legacy networking" msgstr "" #: ./doc/install-guide/ch_overview.xml35(para) msgid "" "The controller node runs the Identity Service, Image Service, dashboard, and" " management portion of Compute. It also contains the associated API " "services, MySQL databases, and messaging system." msgstr "" #: ./doc/install-guide/ch_overview.xml41(para) msgid "" "The compute node runs the hypervisor portion of Compute, which operates " "tenant virtual machines. By default, Compute uses KVM as the hypervisor. " "Compute also provisions and operates tenant networks and implements security" " groups. You can run more than one compute node." msgstr "" #: ./doc/install-guide/ch_overview.xml48(para) msgid "When implementing this architecture, skip ." msgstr "" #: ./doc/install-guide/ch_overview.xml63(para) #: ./doc/install-guide/ch_overview.xml91(title) msgid "Basic architecture with OpenStack Networking (Neutron)" msgstr "" #: ./doc/install-guide/ch_overview.xml66(para) msgid "" "The controller node runs the Identity Service, Image Service, dashboard, and" " management portions of Compute and Networking. It also contains the " "associated API services, MySQL databases, and messaging system." msgstr "" #: ./doc/install-guide/ch_overview.xml72(para) msgid "" "The network node runs the Networking plug-in agent and several layer 3 " "agents that provision tenant networks and provide services to them, " "including routing, NAT, and DHCP. It also handles external (internet) " "connectivity for tenant virtual machines." msgstr "" #: ./doc/install-guide/ch_overview.xml79(para) msgid "" "The compute node runs the hypervisor portion of Compute, which operates " "tenant virtual machines. By default, Compute uses KVM as the hypervisor. The" " compute node also runs the Networking plug-in agent, which operates tenant " "networks and implements security groups. You can run more than one compute " "node." msgstr "" #: ./doc/install-guide/ch_overview.xml86(para) msgid "" "When implementing this architecture, skip ." msgstr "" #: ./doc/install-guide/ch_overview.xml101(para) msgid "" "You can add nodes that run Block Storage or Object Storage to either of " "these architectures." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml13(title) msgid "Install the dashboard" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml14(para) msgid "" "Before you can install and configure the dashboard, meet the requirements in" " ." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml18(para) msgid "" "When you install only Object Storage and the Identity Service, even if you " "install the dashboard, it does not pull up projects and is unusable." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml22(para) msgid "" "For more information about how to deploy the dashboard, see deployment" " topics in the developer documentation." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml28(para) msgid "" "Install the dashboard on the node that can contact the Identity Service as " "root:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml34(title) msgid "Note for Ubuntu users" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml36(para) msgid "" "Remove the openstack-dashboard-ubuntu-theme package. This" " theme prevents translations, several menus as well as the network map from " "rendering correctly: " msgstr "" #: ./doc/install-guide/section_dashboard-install.xml45(title) msgid "Note for Debian users" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml46(para) msgid "To install the Apache package:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml48(para) msgid "" "This command installs and configures Apache correctly, provided that the " "user asks for it during the debconf prompts. The default " "SSL certificate is self-signed, and it is probably wise to have it signed by" " a root Certificate Authority (CA)." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml57(para) msgid "" "Modify the value of CACHES['default']['LOCATION'] in " "/etc/openstack-" "dashboard/local_settings.py/etc/openstack-" "dashboard/local_settings/usr/share" "/openstack-dashboard/openstack_dashboard/local/local_settings.py " "to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml69(para) msgid "" "Open /etc/openstack-" "dashboard/local_settings.py/etc/openstack-dashboard/local_settings" " and look for this line:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml82(title) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml25(td) msgid "Notes" msgstr "Notatki" #: ./doc/install-guide/section_dashboard-install.xml85(para) msgid "" "The address and port must match the ones set in /etc/memcached.conf/etc/sysconfig/memcached." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml90(para) msgid "" "If you change the memcached settings, you must restart the Apache web server" " for the changes to take effect." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml95(para) msgid "" "You can use options other than memcached option for session storage. Set the" " session back-end through the SESSION_ENGINE option." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml102(para) msgid "" "To change the timezone, use the dashboard or edit the /etc/openstack-" "dashboard/local_settings/etc" "/openstack-dashboard/local_settings.py/usr/share/openstack-" "dashboard/openstack_dashboard/local/local_settings.py file." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml111(para) msgid "Change the following parameter: TIME_ZONE = \"UTC\"" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml118(para) msgid "" "Update the ALLOWED_HOSTS in " "local_settings.py to include the addresses you wish to " "access the dashboard from." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml122(para) msgid "" "Edit /etc/openstack-" "dashboard/local_settings/etc" "/openstack-dashboard/local_settings.py/usr/share/openstack-" "dashboard/openstack_dashboard/local/local_settings.py:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml132(para) msgid "" "This guide assumes that you are running the Dashboard on the controller " "node. You can easily run the dashboard on a separate server, by changing the" " appropriate settings in local_settings.py." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml137(para) msgid "" "Edit /etc/openstack-" "dashboard/local_settings/etc" "/openstack-dashboard/local_settings.py/usr/share/openstack-" "dashboard/openstack_dashboard/local/local_settings.py and change " "OPENSTACK_HOST to the hostname of your Identity Service:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml149(para) msgid "Setup Apache configuration: " msgstr "" #: ./doc/install-guide/section_dashboard-install.xml156(para) msgid "" "By default, the openstack-dashboard package enables" " a database as session store. Before you continue, either change the session" " store set up as described in or " "finish the setup of the database session store as explained in ." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml166(para) msgid "Start the Apache web server and memcached:" msgstr "" #: ./doc/install-guide/section_dashboard-install.xml179(para) msgid "" "You can now access the dashboard at http://controller/horizonhttps://controller/http://controller/dashboardhttp://controller." msgstr "" #: ./doc/install-guide/section_dashboard-install.xml186(para) msgid "" "Login with credentials for any user that you created with the OpenStack " "Identity Service." msgstr "" #: ./doc/install-guide/section_heat-install.xml5(title) msgid "Install the Orchestration service" msgstr "" #: ./doc/install-guide/section_heat-install.xml8(para) #: ./doc/install-guide/section_heat-install.xml24(para) msgid "Install the OpenStack Orchestration service on the controller node:" msgstr "" #: ./doc/install-guide/section_heat-install.xml13(para) msgid "" "Respond to prompts for database " "management, [keystone_authtoken] " "settings, RabbitMQ " "credentials and API " "endpoint registration." msgstr "" #: ./doc/install-guide/section_heat-install.xml31(para) msgid "" "In the configuration file, specify the location of the database where the " "Orchestration service stores data. These examples use a MySQL database with " "a heat user on the controller node. Replace " "HEAT_DBPASS with the password for the database " "user:" msgstr "" #: ./doc/install-guide/section_heat-install.xml38(replaceable) #: ./doc/install-guide/section_heat-install.xml44(replaceable) #: ./doc/install-guide/section_heat-install.xml59(replaceable) #: ./doc/install-guide/section_heat-install.xml61(replaceable) msgid "HEAT_DBPASS" msgstr "" #: ./doc/install-guide/section_heat-install.xml39(para) msgid "" "Edit /etc/heat/heat.conf and change the " "[DEFAULT] section." msgstr "" #: ./doc/install-guide/section_heat-install.xml48(para) msgid "" "By default, the Ubuntu packages create an SQLite database. Delete the " "heat.sqlite file that was created in the " "/var/lib/heat/ directory so that it does not get used " "by mistake." msgstr "" #: ./doc/install-guide/section_heat-install.xml54(para) msgid "" "Use the password that you set previously to log in as " "root and create a heat database user:" msgstr "" #: ./doc/install-guide/section_heat-install.xml64(para) msgid "Create the heat service tables:" msgstr "" #: ./doc/install-guide/section_heat-install.xml67(para) msgid "Ignore DeprecationWarning errors." msgstr "" #: ./doc/install-guide/section_heat-install.xml72(para) msgid "" "The Ubuntu packages do not correctly set up logging. Edit the " "/etc/heat/heat.conf file and change the " "[DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_heat-install.xml86(para) msgid "" "Configure the Orchestration Service to use the RabbitMQ message broker." msgstr "" #: ./doc/install-guide/section_heat-install.xml88(para) msgid "" "Edit /etc/heat/heat.conf and modify the " "[DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_heat-install.xml97(para) msgid "" "Create a heat user that the Orchestration service can use" " to authenticate with the Identity Service. Use the " "service tenant and give the user the " "admin role:" msgstr "" #: ./doc/install-guide/section_heat-install.xml101(replaceable) #: ./doc/install-guide/section_heat-install.xml116(replaceable) msgid "HEAT_PASS" msgstr "" #: ./doc/install-guide/section_heat-install.xml101(replaceable) msgid "heat@example.com" msgstr "" #: ./doc/install-guide/section_heat-install.xml105(para) msgid "" "Edit the /etc/heat/heat.conf file to change the " "[keystone_authtoken] and " "[ec2_authtoken] sections to add credentials to the " "Orchestration Service:" msgstr "" #: ./doc/install-guide/section_heat-install.xml122(para) msgid "" "Register the Heat and CloudFormation APIs with the Identity Service so that " "other OpenStack services can locate these APIs. Register the service and " "specify the endpoint:" msgstr "" #: ./doc/install-guide/section_heat-install.xml130(para) #: ./doc/install-guide/section_heat-install.xml141(para) msgid "" "Use the id property that is returned for the service to " "create the endpoint:" msgstr "" #: ./doc/install-guide/section_heat-install.xml156(para) msgid "" "Start the heat-api, heat-api-cfn and heat-engine services and configure them to start when the " "system boots:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml7(title) msgid "Install the Compute agent for the Telemetry service" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml9(para) msgid "" "OpenStack Telemetry is an API service that provides a collector and a range " "of disparate agents. This procedure details how to install the agent that " "runs on the compute node." msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml14(para) msgid "Install the Telemetry service on the Compute node:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml20(para) msgid "" "Set the following options in the /etc/nova/nova.conf " "file:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml33(para) msgid "" "Edit the /etc/nova/nova.conf file and add the following" " lines to the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml47(para) msgid "Restart the Compute service:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml52(para) msgid "" "You must set the secret key that you defined previously. The Telemetry " "service nodes share this key as a shared secret:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml56(para) msgid "" "Edit the /etc/ceilometer/ceilometer.conf file and " "change these lines in the [DEFAULT] section. Replace " "ADMIN_TOKEN with the admin token that you created" " previously:" msgstr "" #: ./doc/install-guide/section_ceilometer-nova.xml72(para) msgid "Start the service and configure it to start when the system boots:" msgstr "" #: ./doc/install-guide/section_neutron-deploy-use-cases.xml6(title) msgid "Neutron deployment use cases" msgstr "" #: ./doc/install-guide/section_neutron-deploy-use-cases.xml7(para) msgid "" "This section describes how to configure the Networking service and its " "components for some typical use cases." msgstr "" #: ./doc/install-guide/section_nova-compute.xml5(title) msgid "Configure a Compute node" msgstr "" #: ./doc/install-guide/section_nova-compute.xml6(para) msgid "" "After you configure the Compute service on the controller node, you must " "configure another system as a Compute node. The Compute node receives " "requests from the controller node and hosts virtual machine instances. You " "can run all services on a single node, but the examples in this guide use " "separate systems. This makes it easy to scale horizontally by adding " "additional Compute nodes following the instructions in this section." msgstr "" #: ./doc/install-guide/section_nova-compute.xml13(para) msgid "" "The Compute service relies on a hypervisor to run virtual machine instances." " OpenStack can use various hypervisors, but this guide uses KVM." msgstr "" #: ./doc/install-guide/section_nova-compute.xml18(para) msgid "" "Configure the system. Use the instructions in ," " but note the following differences from the controller node:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml23(para) msgid "" "Use different IP addresses when you configure eth0. " "This guide uses 192.168.0.11 for the internal network. Do" " not configure eth1 with a static IP address. The " "networking component of OpenStack assigns and configures an IP address." msgstr "" #: ./doc/install-guide/section_nova-compute.xml31(para) msgid "" "Set the host name to compute1. To verify, use the " "uname -n parameter. Ensure that the IP addresses and host names" " for both nodes are listed in the /etc/hosts file on " "each system." msgstr "" #: ./doc/install-guide/section_nova-compute.xml38(para) msgid "" "Synchronize from the controller node. Follow the instructions in ." msgstr "" #: ./doc/install-guide/section_nova-compute.xml42(para) msgid "" "Install the MySQL client libraries. You do not need to install the MySQL " "database server or start the MySQL service." msgstr "" #: ./doc/install-guide/section_nova-compute.xml47(para) msgid "" "Enable the OpenStack packages for the distribution that you are using. See " "." msgstr "" #: ./doc/install-guide/section_nova-compute.xml54(para) msgid "" "After you configure the operating system, install the appropriate packages " "for the Compute service." msgstr "" #: ./doc/install-guide/section_nova-compute.xml58(para) msgid "" "When prompted to create a supermin appliance, respond " "." msgstr "" #: ./doc/install-guide/section_nova-compute.xml63(para) msgid "" "To use the meta-packages and install other components on your compute node, " "such as OVS Networking and Ceilometer agents, run this command:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml67(para) msgid "" "The controller node has the openstack-proxy-node and " "openstack-toaster meta-packages that install openstack-proxy-node and openstack-toaster at " "the same time." msgstr "" #: ./doc/install-guide/section_nova-compute.xml79(para) msgid "" "Respond to the prompts for database management, [keystone_authtoken] " "settings, RabbitMQ " "credentials, and API " "endpoint registration." msgstr "" #: ./doc/install-guide/section_nova-compute.xml88(para) msgid "" "For security reasons, the Linux kernel is not readable by normal users which" " restricts hypervisor services such as qemu and libguestfs. For details, see" " this " "bug. To make the current kernel readable, run: To " "also enable this override for all future kernel updates, create the file " "/etc/kernel/postinst.d/statoverride " "containing: Remember to make the file executable: " "" msgstr "" #: ./doc/install-guide/section_nova-compute.xml107(para) msgid "Edit the /etc/nova/nova.conf configuration file:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml118(para) msgid "" "Edit the /etc/nova/nova.conf configuration file and add" " these lines to the appropriate sections:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml131(para) msgid "" "Configure the Compute Service to use the Qpid message broker by setting " "these configuration keys:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml143(para) msgid "" "Configure the Compute Service to use the RabbitMQ message broker by setting " "these configuration keys:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml152(para) msgid "Configure Compute to provide remote console access to instances." msgstr "" #: ./doc/install-guide/section_nova-compute.xml159(para) msgid "" "Edit /etc/nova/nova.conf and add the following keys " "under the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml173(para) msgid "" "Specify the host that runs the Image Service. " "Edit /etc/nova/nova.conf file and add these lines to " "the [DEFAULT] section:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml184(para) msgid "" "If you install Compute on a virtual machine for testing purposes, you must " "determine whether your hypervisor and/or CPU support nested hardware " "acceleration using the following command:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml189(para) msgid "" "If this command returns a value of one or greater, your" " hypervisor and/or CPU support nested hardware acceleration which requires " "no additional configuration." msgstr "" #: ./doc/install-guide/section_nova-compute.xml193(para) msgid "" "If this command returns a value of zero, your " "hypervisor and/or CPU do not support nested hardware acceleration and " "libvirt must use QEMU instead of KVM. Edit the " "[DEFAULT] section in the /etc/nova/nova-" "compute.conf file to modify this key:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml203(para) msgid "" "If this command returns a value of zero, your " "hypervisor and/or CPU do not support nested hardware acceleration and " "libvirt must use QEMU instead of KVM. Configure " "libvirt to use QEMU:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml211(para) msgid "" "Edit the /etc/nova/api-paste.ini file to add the " "credentials to the [filter:authtoken] section:" msgstr "" #: ./doc/install-guide/section_nova-compute.xml215(para) msgid "" "Files with the extension .ini sometimes need to be " "edited during initial setup. However, they should not be used for general " "configuration tasks." msgstr "" #: ./doc/install-guide/section_nova-compute.xml229(para) msgid "" "Ensure that the " "option is set in /etc/nova/nova.conf file." msgstr "" #: ./doc/install-guide/section_nova-compute.xml236(para) msgid "" "Start the Compute service and configure it to start when the system boots." msgstr "" #: ./doc/install-guide/section_nova-compute.xml253(para) msgid "Remove the SQLite database created by the packages:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_glance-install.xml40(None) msgid "" "@@image: 'figures/debconf-screenshots/glance-common_pipeline_flavor.png'; " "md5=78bef92c36a140ad042074f6345d8917" msgstr "" #: ./doc/install-guide/section_glance-install.xml7(title) msgid "Install the Image Service" msgstr "" #: ./doc/install-guide/section_glance-install.xml8(para) msgid "" "The OpenStack Image Service acts as a registry for virtual disk images. " "Users can add new images or take a snapshot of an image from an existing " "server for immediate storage. Use snapshots for back up and as templates to " "launch new servers. You can store registered images in Object Storage or in " "other locations. For example, you can store images in simple file systems or" " external web servers." msgstr "" #: ./doc/install-guide/section_glance-install.xml16(para) msgid "" "This procedure assumes you set the appropriate environment variables to your" " credentials as described in ." msgstr "" #: ./doc/install-guide/section_glance-install.xml22(para) msgid "Install the Image Service on the controller node:" msgstr "" #: ./doc/install-guide/section_glance-install.xml29(para) msgid "" "Respond to prompts for database " "management, [keystone_authtoken] " "settings, RabbitMQ " "credentials and API " "endpoint registration. You must also select the caching type:" msgstr "" #: ./doc/install-guide/section_glance-install.xml45(para) msgid "" "The Image Service stores information about images in a database. The " "examples in this guide use the MySQL database that is used by other " "OpenStack services." msgstr "" #: ./doc/install-guide/section_glance-install.xml48(para) msgid "" "Configure the location of the database. The Image Service provides the " "glance-api and glance-registry services, each with its own " "configuration file. You must update both configuration files throughout this" " section. Replace GLANCE_DBPASS with your Image " "Service database password." msgstr "" #: ./doc/install-guide/section_glance-install.xml57(replaceable) #: ./doc/install-guide/section_glance-install.xml59(replaceable) #: ./doc/install-guide/section_glance-install.xml77(replaceable) #: ./doc/install-guide/section_glance-install.xml91(replaceable) #: ./doc/install-guide/section_glance-install.xml93(replaceable) msgid "GLANCE_DBPASS" msgstr "" #: ./doc/install-guide/section_glance-install.xml60(para) msgid "" "Edit /etc/glance/glance-api.conf and " "/etc/glance/glance-registry.conf and change the " "[DEFAULT] section." msgstr "" #: ./doc/install-guide/section_glance-install.xml74(para) msgid "" "Use the command to create the Image Service database and " "tables and a glance database user:" msgstr "" #: ./doc/install-guide/section_glance-install.xml80(para) msgid "" "By default, the Ubuntu packages create an SQLite database. Delete the " "glance.sqlite file created in the " "/var/lib/glance/ directory so that it does not get used" " by mistake." msgstr "" #: ./doc/install-guide/section_glance-install.xml86(para) msgid "" "Use the password you created to log in as root and create a " "glance database user:" msgstr "" #: ./doc/install-guide/section_glance-install.xml96(para) msgid "Create the database tables for the Image Service:" msgstr "" #: ./doc/install-guide/section_glance-install.xml100(para) msgid "" "Create a glance user that the Image Service can use to " "authenticate with the Identity Service. Choose a password and specify an " "email address for the glance user. Use the " "service tenant and give the user the " "admin role." msgstr "" #: ./doc/install-guide/section_glance-install.xml106(replaceable) #: ./doc/install-guide/section_glance-install.xml120(replaceable) #: ./doc/install-guide/section_glance-install.xml127(replaceable) #: ./doc/install-guide/section_glance-install.xml163(replaceable) msgid "GLANCE_PASS" msgstr "" #: ./doc/install-guide/section_glance-install.xml107(replaceable) msgid "glance@example.com" msgstr "" #: ./doc/install-guide/section_glance-install.xml111(para) msgid "Add the credentials to the Image Service configuration files:" msgstr "" #: ./doc/install-guide/section_glance-install.xml128(para) msgid "" "Edit /etc/glance/glance-api.conf and " "/etc/glance/glance-registry.conf and change the " "[keystone_authtoken] section." msgstr "" #: ./doc/install-guide/section_glance-install.xml144(para) msgid "" "Add the credentials to the /etc/glance/glance-api-" "paste.ini and /etc/glance/glance-registry-" "paste.ini files." msgstr "" #: ./doc/install-guide/section_glance-install.xml148(para) msgid "" "On CentOS, the package installation does not create these files created " "correctly. Copy the files to the correct location:" msgstr "" #: ./doc/install-guide/section_glance-install.xml155(para) msgid "" "Edit each file to set the following options in the " "[filter:authtoken] section and leave any other existing " "option as it is." msgstr "" #: ./doc/install-guide/section_glance-install.xml167(para) msgid "" "Register the Image Service with the Identity Service so that other OpenStack" " services can locate it. Register the service and create the endpoint:" msgstr "" #: ./doc/install-guide/section_glance-install.xml174(para) msgid "" "Use the id property returned for the service to create " "the endpoint:" msgstr "" #: ./doc/install-guide/section_glance-install.xml183(para) msgid "" "Restart the glance service with " "its new settings." msgstr "" #: ./doc/install-guide/section_glance-install.xml189(para) msgid "" "Start the glance-api and " "glance-registry services and " "configure them to start when the system boots:" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml30(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-common_keep_admin_pass.png'; " "md5=01af4867c16e458306b8abd78a1fccc9" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml39(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-" "common_used_for_remote_db.png'; md5=c6ec966bbfdee18ad87456cf4d44a56f" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml78(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-common_1_configure-with-" "dbconfig-yes-no.png'; md5=4e9d7bce27cc6c7bd68ce8622c80b60f" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml87(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-common_2_db-types.png'; " "md5=a77beb7e13b487cf79716c2140f258c2" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml96(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-" "common_3_connection_method.png'; md5=6cc592e5dd5ea404ad7aad98b37a71f6" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml105(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-" "common_4_mysql_root_password.png'; md5=873ec338742e37305583e9e692bcfdc6" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml114(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-" "common_5_mysql_app_password.png'; md5=3651970770d05892f21d1b5741afbee6" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_debconf-dbconfig-common.xml123(None) msgid "" "@@image: 'figures/debconf-screenshots/dbconfig-" "common_6_mysql_app_password_confirm.png'; " "md5=060cc90aaf6f6fd5cea718064829c1b1" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml6(title) msgid "Configure the database with dbconfig-common" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml7(para) msgid "" "The dbconfig-common package provides a standard Debian " "interface that enables you to configure Debian database parameters. It " "includes localized prompts for many languages and it supports the OpenStack " "database back ends: SQLite, MySQL, and PostgreSQL." msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml12(para) msgid "" "By default, the dbconfig-common package configures the " "OpenStack services to use SQLite3. So if you use debconf " "in non-interactive mode and without pre-seeding, the OpenStack services that" " you install use SQLite3." msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml17(para) msgid "" "By default, dbconfig-common does not provide access to " "database servers over a network. If you want the dbconfig-" "common package to prompt for remote database servers that are " "accessed over a network and not through a UNIX socket file, reconfigure it, " "as follows:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml23(para) msgid "" "These screens appear when you re-configure the dbconfig-" "common package:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml43(para) msgid "" "Unlike other debconf prompts, you cannot pre-seed the " "responses for the dbconfig-common prompts by using " ". Instead, you must create a file in /etc" "/dbconfig-common. For example, you might create a keystone " "configuration file for dbconfig-common that is located in" " /etc/dbconfig-common/keystone.conf, as follows:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml66(para) msgid "After you create this file, run this command:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml68(para) msgid "" "The Identity Service is installed with MySQL as the database back end, " "keystonedb as database name, and the localhost socket " "file." msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml71(para) msgid "The cinder-common package displays these screens:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml127(para) msgid "" "To access a MySQL server remotely, you must make it accessible as root from " "a remote server. To do so, run the openstack-proxy-node " "package command:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml131(para) msgid "" "Alternatively, if you do not want to install this package, run this script " "to enable remote root access:" msgstr "" #: ./doc/install-guide/section_debconf-dbconfig-common.xml154(para) msgid "You must enable remote access before you install OpenStack services." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml87(None) msgid "" "@@image: 'figures/debconf-screenshots/keystone_1_admin_token.png'; " "md5=29a51caaf09c3d6e3f0fda73c256a17a" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml112(None) msgid "" "@@image: 'figures/debconf-" "screenshots/keystone_2_register_admin_tenant_yes_no.png'; " "md5=25c9a90b1df2d979aae6ce9975c7285b" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml121(None) msgid "" "@@image: 'figures/debconf-screenshots/keystone_3_admin_user_name.png'; " "md5=173cf7ed13252df1425109be588b2ad6" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml130(None) msgid "" "@@image: 'figures/debconf-screenshots/keystone_4_admin_user_email.png'; " "md5=b7f0d34350ccc0aa9ae4e766b7ac80c1" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml139(None) msgid "" "@@image: 'figures/debconf-screenshots/keystone_5_admin_user_pass.png'; " "md5=e6b32d8d80af90f07a66abc8fb256c84" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml148(None) msgid "" "@@image: 'figures/debconf-" "screenshots/keystone_6_admin_user_pass_confirm.png'; " "md5=1fbf9223e4923c93030d53278d1771cc" msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/section_keystone-install.xml162(None) msgid "" "@@image: 'figures/debconf-screenshots/keystone_7_register_endpoint.png'; " "md5=d24d84133bfee936267e79631a2666e6" msgstr "" #: ./doc/install-guide/section_keystone-install.xml6(title) msgid "Install the Identity Service" msgstr "" #: ./doc/install-guide/section_keystone-install.xml9(para) msgid "" "Install the OpenStack Identity Service on the controller node, together with" " python-keystoneclient (which is a dependency):" msgstr "" #: ./doc/install-guide/section_keystone-install.xml17(para) msgid "" "Answer to the debconf and " "dbconfig-common questions for " "setting-up the database." msgstr "" #: ./doc/install-guide/section_keystone-install.xml23(para) msgid "" "The Identity Service uses a database to store information. Specify the " "location of the database in the configuration file. In this guide, we use a " "MySQL database on the controller node with the username " "keystone. Replace " "KEYSTONE_DBPASS with a " "suitable password for the database user." msgstr "" #: ./doc/install-guide/section_keystone-install.xml30(replaceable) #: ./doc/install-guide/section_keystone-install.xml50(replaceable) #: ./doc/install-guide/section_keystone-install.xml65(replaceable) #: ./doc/install-guide/section_keystone-install.xml67(replaceable) msgid "KEYSTONE_DBPASS" msgstr "HASŁO_KEYSTONEDB" #: ./doc/install-guide/section_keystone-install.xml31(para) msgid "" "Edit /etc/keystone/keystone.conf and change the " "[sql] section." msgstr "Należy otworzyć plik  /etc/keystone/keystone.conf[sql]." #: ./doc/install-guide/section_keystone-install.xml44(para) msgid "" "Use the command to create the database and tables, as well " "as a database user called keystone to connect to the " "database. Replace " "KEYSTONE_DBPASS with the same " "password used in the previous step." msgstr "" #: ./doc/install-guide/section_keystone-install.xml53(para) msgid "" "By default, the Ubuntu packages create an SQLite database. Delete the " "keystone.db file created in the " "/var/lib/keystone/ directory so that it does not get " "used by mistake." msgstr "" #: ./doc/install-guide/section_keystone-install.xml59(para) msgid "" "Use the password that you set previously to log in as root. Create a " "keystone database user:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml70(para) msgid "Create the database tables for the Identity Service:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml75(para) msgid "" "Define an authorization token to use as a shared secret between the Identity" " Service and other OpenStack services. Respond to the " "debconf prompt with the value in the " "admin_token directive in the keystone.conf" " file. Use the command to generate this password." msgstr "" #: ./doc/install-guide/section_keystone-install.xml91(para) msgid "" "Later, you can verify that the " "/etc/keystone/keystone.conf file contains the password " "you have set using debconf: " msgstr "" #: ./doc/install-guide/section_keystone-install.xml99(para) msgid "" "If you omit a password (for example by pressing Enter at the " "debconf prompt, or installing Keystone using the Debconf " "non-interactive mode) the package generates a random " "ADMIN_TOKEN value." msgstr "" #: ./doc/install-guide/section_keystone-install.xml105(para) msgid "Respond to the prompts to create an administrative tenant:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml154(para) msgid "" "If this is the first time you have installed the Identity Service, register " "the Identity Service in the service catalog:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml168(para) msgid "" "Define an authorization token to use as a shared secret between the Identity" " Service and other OpenStack services. Use to generate a " "random token and store it in the configuration file:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml177(para) msgid "For SUSE Linux Enterprise use instead as first command:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml180(para) msgid "" "Edit /etc/keystone/keystone.conf and change the " "[DEFAULT] section, replacing ADMIN_TOKEN with the results" " of the command." msgstr "" #: ./doc/install-guide/section_keystone-install.xml190(para) msgid "" "By default, Keystone uses PKI tokens. Create the signing keys and " "certificates:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml201(para) msgid "Restart the Identity Service:" msgstr "" #: ./doc/install-guide/section_keystone-install.xml205(para) msgid "" "Start the Identity Service and enable it to start when the system boots:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml6(title) msgid "Object Storage post-installation tasks" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml10(title) msgid "Add a proxy server" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml11(para) msgid "" "For reliability, you add proxy servers. You can set up an additional proxy " "node the same way that you set up the first proxy node but with additional " "configuration steps." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml15(para) msgid "" "After you have more than two proxies, you must load balance them; your " "storage endpoint (what clients use to connect to your storage) also changes." " You can select from different strategies for load balancing. For example, " "you could use round-robin DNS, or a software or hardware load balancer (like" " pound) in front of the two proxies, and point your storage URL to the load " "balancer." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml24(para) msgid "" "Configure an initial proxy node. Then, complete these steps to add proxy " "servers." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml28(para) msgid "" "Update the list of memcache servers in the /etc/swift/proxy-" "server.conf file for added proxy servers. If you run multiple " "memcache servers, use this pattern for the multiple IP:port listings in each" " proxy server configuration file:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml42(para) msgid "" "Copy ring information to all nodes, including new proxy nodes. Also, ensure " "that the ring information gets to all storage nodes." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-post-install.xml49(para) msgid "" "After you sync all nodes, make sure that the admin has keys in " "/etc/swift and the ownership for the ring file is " "correct." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml6(title) msgid "Verify the installation" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml7(para) msgid "" "You can run these commands from the proxy server or any server that has " "access to the Identity Service." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml11(para) msgid "" "Make sure that your credentials are set up correctly in the " "openrc.sh file and source it:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml15(para) msgid "Run the following command:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml27(para) msgid "" "Run the following commands to upload files to a container. " "Create the test.txt and test2.txt " "test files locally if needed." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-verifying-install.xml34(para) msgid "" "Run the following command to download all files from the " "myfiles container:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml6(title) msgid "Install and configure the proxy node" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml7(para) msgid "" "The proxy server takes each request and looks up locations for the account, " "container, or object and routes the requests correctly. The proxy server " "also handles API requests. You enable account management by configuring it " "in the proxy-server.conf file." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml13(para) msgid "" "The Object Storage processes run under a separate user and group, set by " "configuration options, and referred to as swift:swiftopenstack-swift:openstack-swift. The default " "user is swift, which may not" " exist on your system.openstack-" "swift." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml25(para) msgid "Install swift-proxy service:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml31(para) msgid "Create self-signed cert for SSL:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml36(para) msgid "" "Modify memcached to listen on the default interfaces on a local, non-public " "network. Edit this line in the /etc/memcached.conf " "file:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml40(para) msgid "Change it to:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml44(para) msgid "Restart the memcached server:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml48(para) msgid "" "RHEL/CentOS/Fedora only: To set up Object Storage to authenticate tokens, " "set the Identity Service Admin token in the swift proxy file with the " " command." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml58(para) msgid "" "Ubuntu only: Because the distribution packages do not include a copy of the " "keystoneauth middleware, ensure that the proxy server includes them:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml68(para) msgid "Create /etc/swift/proxy-server.conf:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml72(phrase) msgid "user = swift" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml73(phrase) msgid "user = openstack-swift" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml120(para) msgid "" "If you run multiple memcache servers, put the multiple IP:port listings in " "the [filter:cache] section of the proxy-server.conf " "file:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml125(para) msgid "Only the proxy server uses memcache." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml129(para) msgid "" "Create the signing_dir and set its " "permissions accordingly." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml138(para) msgid "" "Create the account, container, and object rings. The builder command creates" " a builder file with a few parameters. The parameter with the value of 18 " "represents 2 ^ 18th, the value that the partition is sized to. Set this " "“partition power” value based on the total amount of storage you expect your" " entire ring to use. The value 3 represents the number of replicas of each " "object, with the last value being the number of hours to restrict moving a " "partition more than once." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml154(para) msgid "For every storage device on each node add entries to each ring:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml160(para) msgid "" "You must omit the optional STORAGE_REPLICATION_NET_IP" " parameter if you do not want to use dedicated network for replication." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml164(para) msgid "" "For example, if a storage node has a partition in Zone 1 on IP 10.0.0.1, the" " storage node has address 10.0.1.1 from replication network. The mount point" " of this partition is /srv/node/sdb1, and the path in " "rsyncd.conf is /srv/node/, the DEVICE would be sdb1 and" " the commands are:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml175(para) msgid "" "If you assume five zones with one node for each zone, start ZONE at 1. For " "each additional node, increment ZONE by 1." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml181(para) msgid "Verify the ring contents for each ring:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml187(para) msgid "Rebalance the rings:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml192(para) msgid "Rebalancing rings can take some time." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml196(para) msgid "" "Copy the account.ring.gz, " "container.ring.gz, and " "object.ring.gz files to each of the Proxy and Storage " "nodes in /etc/swift." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml202(para) msgid "Make sure the swift user owns all configuration files:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-proxy-node.xml207(para) msgid "Start Proxy services:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml6(title) msgid "Plan networking for Object Storage" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml7(para) msgid "" "For both conserving network resources and ensuring that network " "administrators understand the needs for networks and public IP addresses for" " providing access to the APIs and storage network as necessary, this section" " offers recommendations and required minimum sizes. Throughput of at least " "1000 Mbps is suggested." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml15(para) msgid "A mandatory public network. Connects to the Proxy server." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml19(para) msgid "" "A mandatory storage network. Not accessible from outside the cluster. All " "nodes connect to this network." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml23(para) msgid "" "An optional replication network. Not accessible from outside the cluster. " "Dedicated to replication traffic among Storage nodes. Must be configured in " "the Ring." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml13(para) msgid "This guide describes the following networks:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml28(para) msgid "" "By default, all of the OpenStack Object Storage services, as well as the " "rsync daemon on the Storage nodes, are configured to listen on their " "STORAGE_LOCAL_NET IP addresses." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml32(para) msgid "" "If you configure a replication network in the Ring, the Account, Container " "and Object servers listen on both the STORAGE_LOCAL_NET " "and STORAGE_REPLICATION_NET IP addresses. The rsync " "daemon only listens on the STORAGE_REPLICATION_NET IP " "address." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml40(term) msgid "Public Network (Publicly routable IP range)" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml42(para) msgid "" "Provides public IP accessibility to the API endpoints within the cloud " "infrastructure." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml44(para) msgid "Minimum size: one IP address for each proxy server." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml49(term) msgid "Storage Network (RFC1918 IP Range, not publicly routable)" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml52(para) msgid "" "Manages all inter-server communications within the Object Storage " "infrastructure." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml54(para) msgid "Minimum size: one IP address for each storage node and proxy server." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml56(para) msgid "" "Recommended size: as above, with room for expansion to the largest your " "cluster size. For example, 255 or CIDR /24." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml62(term) msgid "Replication Network (RFC1918 IP Range, not publicly routable)" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml65(para) msgid "" "Manages replication-related communications among storage servers within the " "Object Storage infrastructure." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-network-planning.xml67(para) msgid "Recommended size: as for STORAGE_LOCAL_NET." msgstr "" #. When image changes, this message will be marked fuzzy or untranslated for #. you. #. It doesn't matter what you translate it to: it's not used at all. #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml45(None) msgid "" "@@image: '../figures/swift_install_arch.png'; " "md5=c6519fb969c1184afa22e024de9bd2a6" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml6(title) msgid "Example Object Storage installation architecture" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml9(para) msgid "" "node. A host machine that runs one or more OpenStack Object Storage " "services." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml13(para) msgid "Proxy node. Runs Proxy services." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml16(para) msgid "Storage node. Runs Account, Container, and Object services." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml20(para) msgid "" "Ring. A set of mappings between OpenStack Object Storage data to physical " "devices." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml24(para) msgid "" "Replica. A copy of an object. By default, three copies are maintained in the" " cluster." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml28(para) msgid "" "Zone. A logically separate section of the cluster, related to independent " "failure characteristics." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml32(para) msgid "" "To increase reliability and performance, you can add additional proxy " "servers." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-example-install-arch.xml34(para) msgid "" "This document describes each storage node as a separate zone in the ring. At" " a minimum, five zones are recommended. A zone is a group of nodes that is " "as isolated as possible from other nodes (separate servers, network, power, " "even geography). The ring guarantees that every replica is stored in a " "separate zone. This diagram shows one possible configuration for a minimal " "installation:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml6(title) msgid "Install Object Storage" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml7(para) msgid "" "Though you can install OpenStack Object Storage for development or testing " "purposes on one server, a multiple-server installation enables the high " "availability and redundancy you want in a production distributed object " "storage system." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml12(para) msgid "" "To perform a single-node installation for development purposes from source " "code, use the Swift All In One instructions (Ubuntu) or DevStack (multiple " "distros). See http://swift.openstack.org/development_saio.html" " for manual instructions or http://devstack.org for all-in-one " "including authentication with the Identity Service (keystone)." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml24(para) msgid "" "Have a copy of the operating system installation media available if you are " "installing on a new server." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml26(para) msgid "" "These steps assume you have set up repositories for packages for your " "operating system as shown in OpenStack " "Packages." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml30(para) msgid "" "This document demonstrates how to install a cluster by using the following " "types of nodes:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml34(para) msgid "" "One proxy node which runs the swift-proxy-server processes. The proxy server" " proxies requests to the appropriate storage nodes." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml39(para) msgid "" "Five storage nodes that run the swift-account-server, swift-container-" "server, and swift-object-server processes which control storage of the " "account databases, the container databases, as well as the actual stored " "objects." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml48(para) msgid "" "Fewer storage nodes can be used initially, but a minimum of five is " "recommended for a production cluster." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml54(title) msgid "General installation steps" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml57(para) msgid "Install core Swift files and openSSH." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml68(para) msgid "" "Create a swift user that the Object Storage Service can " "use to authenticate with the Identity Service. Choose a password and specify" " an email address for the swift user. Use the " "service tenant and give the user the " "admin role." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml75(replaceable) msgid "SWIFT_PASS" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml76(replaceable) msgid "swift@example.com" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml80(para) msgid "Create a service entry for the Object Storage Service:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml97(para) msgid "" "Specify an API endpoint for the Object Storage Service by using the returned" " service ID. When you specify an endpoint, you provide URLs for the public " "API, internal API, and admin API. In this guide, the " "controller host name is used." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml119(para) msgid "Create and populate configuration directories on all nodes:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml127(para) msgid "Create /etc/swift/swift.conf on all nodes:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml134(para) msgid "" "The suffix value in /etc/swift/swift.conf should be set" " to some random string of text to be used as a salt when hashing to " "determine mappings in the ring. This file should be the same on every node " "in the cluster!" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install.xml141(para) msgid "" "Next, set up your storage nodes and proxy node. This example uses the " "Identity Service for the common authentication piece." msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml7(title) msgid "Start services on the storage nodes" msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml8(para) msgid "" "Now that the ring files are on each storage node, you can start the " "services. On each storage node, run the following commands:" msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml36(para) msgid "To start all swift services at once, run the command:" msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml38(para) msgid "To know more about swift-init command, run:" msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml45(replaceable) msgid "service" msgstr "" #: ./doc/install-guide/object-storage/section_start-storage-node-services.xml44(para) msgid "On Fedora, you might need to use ." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml6(title) msgid "Install and configure storage nodes" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml8(para) msgid "" "Object Storage works on any file system that supports Extended Attributes " "(XATTRS). XFS shows the best overall performance for the swift use case " "after considerable testing and benchmarking at Rackspace. It is also the " "only file system that has been thoroughly tested. See the OpenStack Configuration " "Reference for additional recommendations." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml20(para) msgid "Install Storage node packages:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml29(para) msgid "" "For each device on the node that you want to use for storage, set up the XFS" " volume (/dev/sdb is used as an example). Use a single " "partition per drive. For example, in a server with 12 disks you may use one " "or two disks for the operating system which should not be touched in this " "step. The other 10 or 11 disks should be partitioned with a single " "partition, then formatted in XFS." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml52(para) msgid "Create /etc/rsyncd.conf:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml101(para) msgid "" "(Optional) If you want to separate rsync and replication traffic to " "replication network, set STORAGE_REPLICATION_NET_IP " "instead of STORAGE_LOCAL_NET_IP:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml109(para) msgid "Edit the following line in /etc/default/rsync:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml114(para) msgid "Start rsync daemon:" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml117(para) msgid "" "The rsync daemon requires no authentication, so run it on a local, private " "network." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-install-config-storage-nodes.xml122(para) msgid "Create the swift recon cache directory and set its permissions." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml8(para) msgid "" "Hardware: OpenStack Object Storage is " "designed to run on commodity hardware." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml11(para) msgid "" "When you install only the Object Storage and Identity Service, you cannot " "use the dashboard unless you also install Compute and the Image Service." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml16(caption) msgid "Hardware recommendations" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml23(td) msgid "Server" msgstr "Serwer" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml24(td) msgid "Recommended Hardware" msgstr "Wymagania sprzętowe" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml30(para) msgid "Object Storage object servers" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml32(para) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml61(para) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml71(para) msgid "Processor: dual quad core" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml33(para) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml62(para) msgid "Memory: 8 or 12 GB RAM" msgstr "Pamięć: 8 lub 12 GB RAM" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml34(para) msgid "Disk space: optimized for cost per GB" msgstr "Przestrzeń dyskowa: zoptymalizowana pod kątem ceny za GB" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml35(para) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml63(para) #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml72(para) msgid "Network: one 1 GB Network Interface Card (NIC)" msgstr "Sieć: jedna karta sieciowa (NIC) o przepustowości 1Gbps" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml37(para) msgid "" "The amount of disk space depends on how much you can fit into the rack " "efficiently. You want to optimize these for best cost per GB while still " "getting industry-standard failure rates. At Rackspace, our storage servers " "are currently running fairly generic 4U servers with 24 2T SATA drives and 8" " cores of processing power. RAID on the storage drives is not required and " "not recommended. Swift's disk usage pattern is the worst case possible for " "RAID, and performance degrades very quickly using RAID 5 or 6." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml49(para) msgid "" "As an example, Rackspace runs Cloud Files storage servers with 24 2T SATA " "drives and 8 cores of processing power. Most services support either a " "worker or concurrency value in the settings. This allows the services to " "make effective use of the cores available." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml58(para) msgid "Object Storage container/account servers" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml65(para) msgid "Optimized for IOPS due to tracking with SQLite databases." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml69(para) msgid "Object Storage proxy server" msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml74(para) msgid "" "Higher network throughput offers better performance for supporting many API " "requests." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml77(para) msgid "" "Optimize your proxy servers for best CPU performance. The Proxy Services are" " more CPU and network I/O intensive. If you are using 10 GB networking to " "the proxy, or are terminating SSL traffic at the proxy, greater CPU power is" " required." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml86(para) msgid "" "Operating system: OpenStack Object " "Storage currently runs on Ubuntu, RHEL, CentOS, Fedora, openSUSE, or SLES." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml89(para) msgid "" "Networking: 1Gpbs or 10 Gbps is suggested" " internally. For OpenStack Object Storage, an external network should " "connect the outside world to the proxy servers, and the storage network is " "intended to be isolated on a private network or multiple private networks." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml94(para) msgid "" "Database: For OpenStack Object Storage, a" " SQLite database is part of the OpenStack Object Storage container and " "account management process." msgstr "" #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml98(para) msgid "" "Permissions: You can install OpenStack " "Object Storage either as root or as a user with sudo permissions if you " "configure the sudoers file to enable all the permissions." msgstr "" #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 #: ./doc/install-guide/object-storage/section_object-storage-sys-requirements.xml0(None) msgid "translator-credits" msgstr "Lista tłumaczy"