Red Hat NETWORK 4.0.5 - Przewodnik Instalacji Strona 40

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 53
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 39
* ovs_bridge_mappings = [], a mapping between the name of the VLAN
range defined above (ovs_vlan_ranges) and the bridge name that
was defined above (ovs_bridge_uplinks)
* ovs_tunnel_iface = '', name of interface to use for tunneling
* ovs_tunnel_network = '', network as seen by puppet to use for
tunneling (determines ip or nic for you, value like 192.168.2.0)
* ovs_vlan_ranges = '', a mapping between a name of a VLAN range
to an actual VLAN range (e.g: internal_vlan_range:100-150 [,
internal_vlan_range:180-200] (the ',' is for additional ranges, if
the same name is used, it adds it to the previous range) )
* ovs_tunnel_types = [],a list of available tunnel types - vxlan,
gre, etc
* tenant_network_type = 'vlan',
* tunnel_id_ranges = '1:1000',
* verbose = 'true'/'false', whether the service should have
verbose logging
BZ #10886 11
Feature: Added Orchestration to HA All In One Controller host
group.
Result: HA All In One Controller host group can be deployed
including the Orchestration component. Most notable parameters on
quickstack::pacemaker::params class:
* heat_cfn_enabled - boolean switch for enabling heat-api-cfn
service
* heat_cloudwatch_enabled - boolean switch for enabling heat-api-
cloudwatch service
BZ #109 1003
This enhancement adds an enhanced wizard-based installation
process for Red Hat Enterprise Linux OpenStack Platform. The
solution is based on the staypuft foreman plugin, and utilizes
existing puppet classes used by other installation methods.
This was added due to a need for a UI-based installation; all
previous installation methods are still present.
BZ #109 3055
This feature allows multiple concurrent deployments of Red Hat
Enterprise Linux OpenStack Platform to be managed from the
Staypuft UI.
BZ #109 334 9
RHOS 4.0 will support multiple, active instances of the Neutron
API service. This will allow higher scalability as well as a
limited form of high availability. RHOS 4.0 will use a haproxy
configuration, while RHOS 5.0 will use the HA Neutron deployment
via the Foreman Staypuft installer.
Red Hat Ent erprise Linux O penSt ack Plat form 4 Release Not es
36
Przeglądanie stron 39
1 2 ... 35 36 37 38 39 40 41 42 43 44 45 ... 52 53

Komentarze do niniejszej Instrukcji

Brak uwag