diff options
author | Tim Rozet <trozet@redhat.com> | 2015-11-30 15:30:31 -0500 |
---|---|---|
committer | Tim Rozet <trozet@redhat.com> | 2015-12-07 16:17:26 -0500 |
commit | 281c4fe57a9462363fe87e058ecb08eb18c70dd1 (patch) | |
tree | 3c3a35bfffdedeb5b353ad19dfd13e2d709bb432 /.gitreview | |
parent | f1d8550d7de86f048902428c6ce0cc4fd76d2569 (diff) |
Requirement: Supported Logical Networks for Target System
Installers must support being able to separate network traffic for
OpenStack + SDN controllers into these logical networks:
1) Admin network - used by OpenStack for Admin user traffic
2) Private network- used by OpenStack for inter-component traffic
3) Public network- user + internet access. References OpenStack public
network.
4) Storage network - for storage related traffic only
OpenStack is configurable in that it allows its components to be bound
to specific networks. Installers should also support configuring
OpenStack this way, and separating components/traffic across these
logical networks.
For example, keystone admin endpoint should only be available on the
Admin network. Access to keystone admin endpoint on Public network would
not be allowed.
Note: This requirement does not restrict installers from deploying other
types of logical network configurations such as combining all traffic
into a single logical network, or combining some logical networks into
one. The requirement simply states that the 4 listed above must be
supported and the default option.
An optional 5th network for lights out management (IPMI access) is also
typically used (especially with baremetal deployments), but it is beyond
the scope of this requirement (logical OpenStack networks), and it's
network definition/configuration should be defined by the
environment/POD being used.
JIRA: GENESIS-62
Change-Id: I3942bba91f0831a1f8088fa75968d23aa968eebe
Signed-off-by: Tim Rozet <trozet@redhat.com>
Diffstat (limited to '.gitreview')
0 files changed, 0 insertions, 0 deletions