Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kolla Ansible
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Very Demiurge Very Mindful
Kolla Ansible
Commits
1929889e
Commit
1929889e
authored
8 years ago
by
Jenkins
Committed by
Gerrit Code Review
8 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Update production architecture guide for formatting"
parents
2825e18f
b2da75f6
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/production-architecture-guide.rst
+18
-16
18 additions, 16 deletions
doc/production-architecture-guide.rst
with
18 additions
and
16 deletions
doc/production-architecture-guide.rst
+
18
−
16
View file @
1929889e
...
...
@@ -20,7 +20,7 @@ A basic Kolla inventory consists of several types of nodes, known in Ansible as
* Network - This is the network node. It will host Neutron agents along with
haproxy / keepalived. These nodes will have a floating ip defined in
``
K
olla_internal_vip_address``.
``
k
olla_internal_vip_address``.
* Compute - These are servers for compute services. This is where guest VMs
live.
...
...
@@ -37,35 +37,37 @@ Interface configuration
In Kolla operators should configure following network interfaces:
* network_interface - While it is not used on its own, this provides the
*
``
network_interface
``
- While it is not used on its own, this provides the
required default for other interfaces below.
* api_interface - This interface is used for the management network. The
*
``
api_interface
``
- This interface is used for the management network. The
management network is the network OpenStack services uses to communicate to
each other and the databases. There are known security risks here, so it's
recommended to make this network internal, not accessible from outside.
Defaults to network_interface.
Defaults to
``
network_interface
``
.
* kolla_external_vip_interface - This interface is public-facing one. It's
*
``
kolla_external_vip_interface
``
- This interface is public-facing one. It's
used when you want HAProxy public endpoints to be exposed in different
network than internal ones. It is mandatory to set this option when
``kolla_enable_tls_external`` is set to yes. Defaults to network_interface.
``kolla_enable_tls_external`` is set to yes. Defaults to
``network_interface``.
* storage_interface - This is the interface that is used by virtual machines to
communicate to Ceph. This can be heavily utilized so it's recommended to put
this network on 10Gig networking. Defaults to network_interface.
* ``storage_interface`` - This is the interface that is used by virtual
machines to communicate to Ceph. This can be heavily utilized so it's
recommended to put this network on 10Gig networking. Defaults to
``network_interface``.
* cluster_interface - This is another interface used by Ceph. It's used for
*
``
cluster_interface
``
- This is another interface used by Ceph. It's used for
data replication. It can be heavily utilized also and if it becomes a
bottleneck it can affect data consistency and performance of whole cluster.
Defaults to network_interface.
Defaults to
``
network_interface
``
.
* tunnel_interface - This interface is used by Neutron for vm-to-vm traffic
over tunneled networks (like VxLan). Defaults to network_interface.
*
``
tunnel_interface
``
- This interface is used by Neutron for vm-to-vm traffic
over tunneled networks (like VxLan). Defaults to
``
network_interface
``
.
*
N
eutron_external_interface - This interface is required by Neutron.
Neutron
will put br-ex on it. It will be used for flat networking as well as
tagged
vlan networks. Has to be set separately.
*
``n
eutron_external_interface
``
- This interface is required by Neutron.
Neutron
will put br-ex on it. It will be used for flat networking as well as
tagged
vlan networks. Has to be set separately.
Docker configuration
====================
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment