Ask Your Question
0

How to update memory size allocated for undercloud and overcloud VMs , reproducing Deploying an HA OpenStack with tripleo-quickstart ?

asked 2016-04-20 16:34:19 -0500

jasonwg gravatar image

Following link http://blog.oddbit.com/2016/02/19/dep...
I see that proposed file playbooks/roles/nodes/defaults/main.yml doesn't exist any longer in
tripleo-quickstart after git clone https://github.com/redhat-openstack/t...
What is up to date path to yml template responsible for memory footprint update ?

edit retag flag offensive close merge delete

Comments

dbaxps gravatar imagedbaxps ( 2016-06-02 17:18:19 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-06-02 17:16:21 -0500

dbaxps gravatar image

updated 2016-06-03 06:17:07 -0500

UPDATE 06/03/2016
As of now template bellow works for me

compute_memory: 6144
compute_vcpu: 1

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

# 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 --neutron-network-type vxlan
  --neutron-tunnel-types vxlan
  -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
  --ntp-server pool.ntp.org
deploy_timeout: 75
tempest: false
pingtest: true

END UPDATE
Start on remote workstation ( say F23,CentOS 7.X)
$ export VIRTHOST=192.168.1.75 #put your own IP here
$ ssh-copy-id root@$VIRTHOST
$ ssh root@$VIRTHOST uname -a # make sure no prompt for root login
$ git clone https://github.com/openstack/tripleo-...
$ cd tripleo-quickstart
Then create for instance testing.yml like this

    undercloud_memory: 12288
    undercloud_vcpu: 4

    control_memory: 8192
    control_vcpu: 2
    compute_memory: 8192
    compute_vcpu: 2

    # We set introspection to true and use only the minimal amount of nodes
    # for this job, but test all defaults otherwise.
    step_introspect: true

    # Define a single controller node and a single compute node.
    overcloud_nodes:
      - name: control_0
        flavor: control

      - name: compute_0
        flavor: compute

      - name: compute_1
        flavor: compute

    # Tell tripleo how we want things done.
    extra_args: >-
      --compute-scale 2 --neutron-network-type vxlan
      --neutron-tunnel-types vxlan
      --ntp-server pool.ntp.org

    network_isolation: true

Then run under tripleo-quickstart
$ bash quickstart.sh --config ./testing.yml $VIRTHOST
If everything went well you will be brought back to command prompt and see message

##################################
Virtual Environment Setup Complete
##################################

Access the undercloud by:
( here you make ssh login into VM already running  on CentOS 7.2 Server 32 GB RAM )

 ssh -F /home/marcos/.quickstart/ssh.config.ansible undercloud 
There are scripts in the home directory to continue the deploy:

 undercloud-install.sh will run the undercloud install
 undercloud-post-install.sh will perform all pre-deploy steps
 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

During overcloud deployment open remote ssh session to server and run top
You will see that memory allocation matches you testing.yml
When done : su - stack on Server

[stack@ServerCentOS72 ~]$ virsh list
 Id    Name                           State
----------------------------------------------------
 2     undercloud                     running
 12    compute_0                      running
 13    compute_1                      running
 14    control_0                      running

[stack@ServerCentOS72 ~]$ virsh dumpxml control_0 | grep vcpu
  <vcpu placement='static'>2</vcpu>
[stack@ServerCentOS72 ~]$ virsh dumpxml control_0 | grep memory
  <memory unit='KiB'>8388608</memory>
[stack@ServerCentOS72 ~]$ virsh dumpxml undercloud | grep vcpu
  <vcpu placement='static'>4</vcpu>
[stack@ServerCentOS72 ~]$ virsh dumpxml undercloud | grep memory
  <memory unit='KiB'>12582912</memory>
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-04-20 16:34:19 -0500

Seen: 470 times

Last updated: Jun 03 '16