there were actually following changes in the oooq config file (-N parameter):
# cat config/nodes/3ctlr_1comp_ceph.yml
# This config file is used to deploy a dedicated node in the overcloud for ceph
# Define a controller node, a compute node, and a ceph node.
overcloud_nodes:
- name: control_0
flavor: control
virtualbmc_port: 6230
- name: control_1
flavor: control
virtualbmc_port: 6231
- name: control_2
flavor: control
virtualbmc_port: 6232
there were actually following changes in the oooq config file (-N parameter): nodes/3ctlr_ 1comp_ceph. yml
# cat config/
# This config file is used to deploy a dedicated node in the overcloud for ceph
# Define a controller node, a compute node, and a ceph node. port: 6230
overcloud_nodes:
- name: control_0
flavor: control
virtualbmc_
- name: control_1 port: 6231
flavor: control
virtualbmc_
- name: control_2 port: 6232
flavor: control
virtualbmc_
- name: compute_0 port: 6233
flavor: compute
virtualbmc_
- name: ceph_0 port: 6234
flavor: ceph
virtualbmc_
node_count: 5
# Tell tripleo which nodes to deploy. storage- scale 1 templates_ path}}/ environments/ storage- environment. yaml templates_ path}}/ environments/ enable- swap.yaml templates_ path}}/ environments/ puppet- pacemaker. yaml templates_ path}}/ environments/ manila- cephfsnative- config. yaml
topology: >-
--ceph-
--control-scale 3
-e {{overcloud_
-e {{overcloud_
-e {{overcloud_
-e {{overcloud_
network_isolation: true isolation_ type: 'single-nic-vlans'
network_