Deploy an OpenStack environment using networking templates¶
By default, the Elasticsearch-Kibana cluster will be deployed on the Fuel management network. If this default configuration does not meet your requirements, you can leverage the Fuel networking templates’ capability to change that default configuration and use a dedicated network instead.
Below is a networking template example to define a new network named
monitoring
. You can use this configuration example as a starting point
and adapt it to your requirements.
adv_net_template:
default:
network_assignments:
fuelweb_admin:
ep: br-fw-admin
management:
ep: br-mgmt
private:
ep: br-mesh
public:
ep: br-ex
storage:
ep: br-storage
monitoring:
ep: br-monitoring
network_scheme:
admin:
endpoints:
- br-fw-admin
roles:
admin/pxe: br-fw-admin
fw-admin: br-fw-admin
transformations:
- action: add-br
name: br-fw-admin
- action: add-port
bridge: br-fw-admin
name: <% if1 %>
mgmt:
endpoints:
- br-mgmt
roles:
ceilometer/api: br-mgmt
cinder/api: br-mgmt
glance/api: br-mgmt
heat/api: br-mgmt
horizon: br-mgmt
keystone/api: br-mgmt
management: br-mgmt
mgmt/api: br-mgmt
mgmt/corosync: br-mgmt
mgmt/database: br-mgmt
mgmt/memcache: br-mgmt
mgmt/messaging: br-mgmt
mgmt/vip: br-mgmt
mongo/db: br-mgmt
murano/api: br-mgmt
neutron/api: br-mgmt
neutron/private: br-mgmt
nova/api: br-mgmt
nova/migration: br-mgmt
rados_gw_management_vip: br-mgmt
sahara/api: br-mgmt
swift/api: br-mgmt
swift/replication: br-mgmt
transformations:
- action: add-br
name: br-mgmt
- action: add-port
bridge: br-mgmt
name: <% if3 %>
private:
endpoints:
- br-mesh
roles:
neutron/mesh: br-mesh
transformations:
- action: add-br
name: br-mesh
- action: add-port
bridge: br-mesh
name: <% if4 %>
public:
endpoints:
- br-ex
roles:
ceph/radosgw: br-ex
cinder/api: br-ex
ex: br-ex
neutron/floating: br-floating
public/vip: br-ex
transformations:
- action: add-br
name: br-ex
- action: add-br
name: br-floating
provider: ovs
- action: add-patch
bridges:
- br-floating
- br-ex
mtu: 65000
provider: ovs
- action: add-port
bridge: br-ex
name: <% if2 %>
storage:
endpoints:
- br-storage
roles:
ceph/replication: br-storage
cinder/iscsi: br-storage
storage: br-storage
swift/replication: br-storage
transformations:
- action: add-br
name: br-storage
- action: add-port
bridge: br-storage
name: <% if5 %>
monitoring:
endpoints:
- br-monitoring
roles:
monitoring: br-monitoring
elasticsearch: br-monitoring
kibana: br-monitoring
influxdb_vip: br-monitoring
grafana: br-monitoring
infrastructure_alerting: br-monitoring
infrastructure_alerting_ui: br-monitoring
transformations:
- action: add-br
name: br-monitoring
- action: add-port
bridge: br-monitoring
name: <% if3 %>.101
nic_mapping:
default:
# fw-admin
if1: eth0
# public
if2: eth1
# management + monitoring (VLAN: 101)
if3: eth2
# private
if4: eth3
# storage
if5: eth4
templates_for_node_role:
# The following roles supports deployments using Neutron with tunneling segmentation
# and Cinder with LVM over iSCSI
cinder:
- admin
- mgmt
- private
- storage
- monitoring
compute:
- admin
- mgmt
- private
- storage
- monitoring
controller:
- admin
- mgmt
- public
- private
- storage
- monitoring
elasticsearch_kibana:
- admin
- mgmt
- private
- storage
- monitoring
influxdb_grafana:
- admin
- mgmt
- private
- storage
- monitoring
infrastructure_alerting:
- admin
- mgmt
- private
- storage
- monitoring
To deploy an environment using networking templates:
Upload the networking template:
$ fuel2 network-template upload -f ./network_template <ENVIRONMENT_ID>
Allocate an IP subnet for the
monitoring
network:$ fuel2 network-group create -N <ENVIRONMENT_ID> -C 10.109.5.0/24 monitoring
Optional. Using the Fuel web UI, adjust the IP range:
Proceed to Configure the plugin.
For details on networking templates, see the Fuel User Guide.