Revision history [back]

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

Check report if undercloud VM has been set up :-

Access the undercloud by:
 ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud

There are scripts in the home directory to continue the deploy:

 overcloud-deploy.sh will deploy the overcloud
 overcloud-deploy-post.sh will do any post-deploy configuration
 overcloud-validate.sh will run post-deploy validation

Details here :-

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

Check report if undercloud VM has been set up :-

Access the undercloud by:
 ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud

There are scripts in the home directory to continue the deploy:

 overcloud-deploy.sh will deploy the overcloud
 overcloud-deploy-post.sh will do any post-deploy configuration
 overcloud-validate.sh will run post-deploy validation

Details here :-

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description



You might find this blog http://hardysteven.blogspot.com very handy working on TripleO Quickstart

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

Check report if undercloud VM has been set up :-

Access the undercloud by:
 ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud

There are scripts in the home directory to continue the deploy:

 overcloud-deploy.sh will deploy the overcloud
 overcloud-deploy-post.sh will do any post-deploy configuration
 overcloud-validate.sh will run post-deploy validation

Details here :-

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

[stack@ServerCentOS72 ~]$ virsh list --all

Id    Name                           State
----------------------------------------------------
 2     undercloud                     running
 8     control_1                      running
 9     compute_1                      running
 10    control_0                      running
 11    control_2                      running
 12    compute_0                      running



You might find this blog http://hardysteven.blogspot.com very handy working on TripleO Quickstart

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

Check report if undercloud VM has been set up :-

Access the undercloud by:
 ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud

There are scripts in the home directory to continue the deploy:

 overcloud-deploy.sh will deploy the overcloud
 overcloud-deploy-post.sh will do any post-deploy configuration
 overcloud-validate.sh will run post-deploy validation

Details here :-

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

[stack@ServerCentOS72 ~]$ virsh list --all

Id    Name                           State
----------------------------------------------------
 2     undercloud                     running
 8     control_1                      running
 9     compute_1                      running
 10    control_0                      running
 11    control_2                      running
 12    compute_0                      running

image description

You might find this blog http://hardysteven.blogspot.com very handy working on TripleO Quickstart

Regarding POC for 3 Node Pacemaker/Corosync HA Controller's Cluster try TripleO Quickstart ( works only on CentOS 7.2, RHEL 7.2, 32 GB Ram)
Sample of deployment template

# Deploy an HA openstack environment.
control_memory: 6144
compute_memory: 6144
undercloud_memory: 8192

# Giving the undercloud additional CPUs can greatly improve heat's
# performance (and result in a shorter deploy time).
undercloud_vcpu: 4
# Create three controller nodes and one compute node.
overcloud_nodes:
  - name: control_0
    flavor: control
  - name: control_1
    flavor: control
  - name: control_2
    flavor: control

  - name: compute_0
    flavor: compute
  - name: compute_1
    flavor: compute
# We don't need introspection in a virtual environment (because we are
# creating all the "hardware" we really know the necessary
# information).
introspect: false

# Tell tripleo about our environment.
network_isolation: true
extra_args: >-
  --control-scale 3 --compute-scale 2 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  --ntp-server pool.ntp.org
test_tempest: false
test_ping: true
enable_pacemaker: true

Then proceed from workstation

$ git clone https://github.com/openstack/tripleo-quickstart
$ cd tripleo-quickstart
$ sudo bash quickstart.sh --install-deps
$ sudo yum -y  install redhat-rpm-config
$export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-keygen
$ssh-copy-id root@$VIRTHOST
$ssh root@$VIRTHOST uname -a # no root login prompt

Then run under tripleo-quickstart

$ bash quickstart.sh --config ./config/general_config/ha.yml  $VIRTHOST

Check report if undercloud VM has been set up :-

Access the undercloud by:
 ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud

There are scripts in the home directory to continue the deploy:

 overcloud-deploy.sh will deploy the overcloud
 overcloud-deploy-post.sh will do any post-deploy configuration
 overcloud-validate.sh will run post-deploy validation

Details here :-

http://lxer.com/module/newswire/view/230289/index.html
http://lxer.com/module/newswire/view/230814/index.html

image description

See also https://www.linux.com/blog/tripleo-quickstart-ha-setup-keeping-undercloud-persistent-between-cold-reboots

image description

You might find this blog http://hardysteven.blogspot.com very handy working on TripleO Quickstart