Posting bellow is supposed to demonstrate KSM implementation on QuickStart providing significant relief on 32 GB VIRTHOST vs quite the same deploymet described in previous draft http://lxer.com/module/newswire/view/234740/index.html Deployment procedure for TripleO QuickStart is bit more complicated in meantime then it was designed for Mitaka stable release. Instructions bellow provide a step by step guide usually not required by QuickStart environment on undecloud VM after you logged into undercloud

Git clone repo bellow :-

[[email protected] release]$ git clone https://github.com/openstack/tripleo-quickstart [[email protected] release]$ cd tripleo* ; cd ./config/release

**********************************************

Now verify that newton.yml is here.

**********************************************

[[email protected] release]$ cat newton.yml

release: newton

undercloud_image_url: http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/newton/delorean/undercloud.qcow2

overcloud_image_url: http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/newton/delorean/overcloud-full.tar

ipa_image_url: http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/newton/delorean/ironic-python-agent.tar


TripleO QuickStart KSM vs instack-virt-setup deploying RDO Newton HA Overcloud

**************************************************************************************

UPDATE ./config/general_config/ha.yml of memory allocation for HA controller

up to 6.5 GB ( as minimum to avoid crash in step5 of overcloud deployment )

**************************************************************************************

[[email protected] tripleo-quickstart]$ cat ./config/general_config/ha.yml# Deploy an HA openstack environment.

#

# This will require (6144 * 4) == approx. 24GB for the overcloud

# nodes, plus another 8GB for the undercloud, for a total of around

# 32GB.

control_memory: 6500

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

# We don’t need introspection in a virtual environment (because we are

# creating all the “hardware” we really know the necessary

# information).

step_introspect: false

# Tell tripleo about our environment.

network_isolation: true

extra_args: >-

control-scale 3 compute-scale 1 neutron-network-type vxlan

neutron-tunnel-types vxlan

ntp-server pool.ntp.org

test_ping: true

enable_pacemaker: true

tempest_config: false

run_tempest: false

****************************************************************************

Run quickstart.sh to create undercloud VM on VIRTHOST

****************************************************************************

[[email protected] tripleo-quickstart]$ bash quickstart.sh -R newton config ./config/general_config/ha.yml $VIRTHOST

Login to undercloud when done

[[email protected] tripleo-quickstart]$ ssh -F /home/john/.quickstart/ssh.config.ansible undercloud

****************************************************************************************************

In meantime QuickStart requires manual overcloud deployment

Now you are logged into undecloud VM running on VIRTHOST as stack

Building overcloud images is skipped due to QuickStart CI. There is no harm in attempt of building them. It will take a second, they are already there.

****************************************************************************************************

# Upload per-built overcloud images [[email protected] ~]$ source stackrc
[[email protected] ~]$ openstack overcloud image upload
[[email protected] ~]$ openstack baremetal import instackenv.json
[[email protected] ~]$ openstack baremetal configure boot
[[email protected] ~]$ openstack baremetal introspection bulk start
[[email protected] ~]$ ironic node-list
[email protected] ~]$ neutron subnet-list
[[email protected] ~]$ neutron subnet-update 1b7d82e5-0bf1-4ba5-8008-4aa402598065 \ --dns-nameserver 192.168.122.1

**************************************

Create external interface vlan10

*************************************

[[email protected] ~]$ sudo vi /etc/sysconfig/network-scripts/ifcfg-vlan10

DEVICE=vlan10

ONBOOT=yes

DEVICETYPE=ovs

TYPE=OVSIntPort

BOOTPROTO=static

IPADDR=10.0.0.1

NETMASK=255.255.255.0

OVS_BRIDGE=br-ctlplane

OVS_OPTIONS=”tag=10″

[[email protected] ~]$ sudo ifup vlan10 [[email protected] ~]$ sudo ovs-vsctl show

0d9f9351-93cd-4c83-8eb4-82e8b1ca6665

Manager “ptcp:6640:127.0.0.1”

is_connected: true

Bridge br-ctlplane

Controller “tcp:127.0.0.1:6633”

is_connected: true

fail_mode: secure

Port br-ctlplane

Interface br-ctlplane

type: internal

Port phy-br-ctlplane

Interface phy-br-ctlplane

type: patch

options: {peer=int-br-ctlplane}

Port “eth1”

Interface “eth1”

Port “vlan10”

tag: 10

Interface “vlan10”

type: internal

Bridge br-int

Controller “tcp:127.0.0.1:6633”

is_connected: true

fail_mode: secure

Port int-br-ctlplane

Interface int-br-ctlplane

type: patch

options: {peer=phy-br-ctlplane}

Port br-int

Interface br-int

type: internal

Port “tapb0b80495-42”

tag: 1

Interface “tapb0b80495-42”

type: internal

ovs_version: “2.5.0”

*********************************************

Create manually network_env.yaml

*********************************************

[[email protected] ~]$vi network_env.yaml

{

“parameter_defaults”: {

“ControlPlaneDefaultRoute”: “192.0.2.1”,

“ControlPlaneSubnetCidr”: “24”,

“DnsServers”: [

“192.168.122.1”

],

“EC2MetadataIp”: “192.0.2.1”,

“ExternalAllocationPools”: [

{

“end”: “10.0.0.250”,

“start”: “10.0.0.4”

}

],

“ExternalNetCidr”: “10.0.0.1/24”,

“NeutronExternalNetworkBridge”: “”

}

}

$ sudo iptables -A BOOTSTACK_MASQ -s 10.0.0.0/24 ! -d 10.0.0.0/24 -j MASQUERADE -t nat

[[email protected] ~]$ sudo touch -f \
/usr/share/openstack-tripleo-heat-templates/puppet/post.yaml [[email protected] ~]$ cat overcloud-deploy.sh #!/bin/bash -x
source /home/stack/s

本文系统(linux)相关术语:linux系统 鸟哥的linux私房菜 linux命令大全 linux操作系统

主题: GitCPUTIOPT2G4G
分页:12
转载请注明
本文标题:TripleO QuickStart KSM vs instack-virt-setup deploying RDO Newton HA Overcloud
本站链接:http://www.codesec.net/view/482196.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(linux) | 评论(0) | 阅读(41)