How to test Heat (by quqi99)

来源：互联网发布：金蝶会计软件编辑：程序博客网时间：2024/05/16 15:43

作者：张华发表于：2015-12-19
版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息及本版权声明

(http://blog.csdn.net/quqi99 )

Heat根据配置文件模板(HOT, heat orchestration template)实例化一组符合要求的虚机。也能够在其上对应用软件进行配置与编排。对支持对一个组件部署后的负载均衡进行编排。
Heat 服务包含以下重要的组件：

Heat-api组件实现OpenStack天然支持的REST API。该组件通过把API请求经由AMQP传送给Heat engine来处理API请求。
Heat-api-cfn组件提供兼容AWS CloudFormation的API，同时也会把API请求通过AMQP转发给heat engine。
Heat-engine组件提供Heat最主要的协作功能。

Setting up test environment

# bzr branch lp:~openstack-charm-testers/+junk/ipv6

bzr branch lp:openstack-charm-testing
juju destroy-environment --force zhhuabj
juju switch zhhuabj && juju bootstrap
juju-deployer -c ./next.yaml -d trusty-kilo
juju add-unit neutron-gateway
#juju set neutron-api overlay-network-type=vxlan
#juju set neutron-api l2-population=false enable-l3ha=true
./configure #edit script to use vxlan
source ./novarc
neutron net-list && neutron router-list
nova boot --image trusty --nic net-id=98e10e32-13eb-48ee-b265-4ae0e449b6e5 --flavor 2 i1
nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0
nova secgroup-add-rule default tcp 22 22 0.0.0.0/0
nova floating-ip-create
nova floating-ip-associate i1 10.5.150.1

或者使用devstack部署，localrc文件如下：

#OFFLINE=TrueDEST=/home/demoIPSEC_PACKAGE=strongswansudo route del -net 10.0.1.0/24 gw 192.168.101.3sudo apt-get install openvswitch-switch qemu-kvm libvirt-binsudo ovs-vsctl -- --may-exist add-br br-physleep 5

sudo ip addr add 172.16.1.1/24 dev br-phy#sudo ovs-vsctl -- --may-exist add-port br-phy eth0 -- set interface eth0 type=internalENABLED_SERVICES=rabbit,mysql,key,g-api,g-regENABLED_SERVICES+=,n-api,n-crt,n-obj,n-cpu,n-cond,n-sch#ENABLED_SERVICES+=,cinder,c-api,c-vol,c-schENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,neutron,q-lbaas,q-fwaas,q-vpn

Q_ML2_TENANT_NETWORK_TYPE=flat,vlan,gre,vxlanOVS_BRIDGE_MAPPINGS=physnet1:br-phy#ENABLED_SERVICES+=,horizon#ENABLED_SERVICES+=,s-proxy,s-object,s-container,s-accountVOLUME_BACKING_FILE_SIZE=500MSWIFT_HASH=66a3d6b56c1f479c8b4e70ab5c2000f5SWIFT_REPLICAS=1SWIFT_DATA_DIR=/home/demo/data/swiftHOST_IP=172.16.1.1SERVICE_HOST=172.16.1.1MYSQL_HOST=172.16.1.1RABBIT_HOST=172.16.1.1GLANCE_HOSTPORT=172.16.1.1:9292Q_HOST=172.16.1.1FIXED_RANGE=10.0.1.0/24FLOATING_RANGE=192.168.101.0/24Q_FLOATING_ALLOCATION_POOL=start=192.168.101.3,end=192.168.101.100PUBLIC_NETWORK_GATEWAY=192.168.101.1NETWORK_GATEWAY=10.0.1.1PUBLIC_BRIDGE=br-ex# sudo ovs-vsctl add-port br-ex eth1OVS_PHYSICAL_BRIDGE=br-phyDATABASE_USER=rootDATABASE_PASSWORD=passwordADMIN_PASSWORD=passwordSERVICE_PASSWORD=passwordRABBIT_PASSWORD=passwordSERVICE_TOKEN=ADMINLOGFILE=/home/demo/logs/stack.logENABLE_DEBUG_LOG_LEVEL=FalseSYSLOG=FalseSCREEN_LOGDIR=/home/demo/logsLOG_COLOR=FalseQ_USE_DEBUG_COMMAND=FalseAPACHE_ENABLED_SERVICES+=keystoneKEYSTONE_TOKEN_FORMAT=UUIDUSE_SSL=Falsedisable_service tls-proxyENABLED_SERVICES+=,heat,h-api,h-api-cfn,h-api-cw,h-engCIRROS_VERSION=0.3.4

使用Heat进行部署

heat_template_version: 2013-05-23description: HOT template for two interconnected VMs with floating ips.parameters:  image_id:    type: string    description: Image Name   secgroup_id:    type: string    description : Id of the security groupe  public_net:    type: string    description: public network idresources:  private_net:    type: OS::Neutron::Net    properties:      name: private-net       private_subnet:    type: OS::Neutron::Subnet    properties:      network_id: { get_resource: private_net }      cidr: 172.16.2.0/24      gateway_ip: 172.16.2.1       router1:    type: OS::Neutron::Router    properties:      external_gateway_info:        network: { get_param: public_net }       router1_interface:    type: OS::Neutron::RouterInterface    properties:      router_id: { get_resource: router1 }      subnet_id: { get_resource: private_subnet }  server1_port:    type: OS::Neutron::Port    properties:      network_id: { get_resource: private_net }      security_groups: [ get_param: secgroup_id ]      fixed_ips:        - subnet_id: { get_resource: private_subnet }   server1_floating_ip:    type: OS::Neutron::FloatingIP    properties:      floating_network_id: { get_param: public_net }      port_id: { get_resource: server1_port }  server1:    type: OS::Nova::Server    properties:      name: Server1      image: { get_param: image_id }      flavor: m1.tiny      networks:        - port: { get_resource: server1_port }      server2_port:    type: OS::Neutron::Port    properties:      network_id: { get_resource: private_net }      security_groups: [ get_param: secgroup_id ]      fixed_ips:        - subnet_id: { get_resource: private_subnet }       server2_floating_ip:    type: OS::Neutron::FloatingIP    properties:      floating_network_id: { get_param: public_net }      port_id: { get_resource: server2_port }       server2:    type: OS::Nova::Server    properties:      name: Server2      image: { get_param: image_id }      flavor: m1.tiny      networks:        - port: { get_resource: server2_port }     outputs:  server1_private_ip:    description: Private IP address of server1    value: { get_attr: [ server1, first_address ] }  server1_public_ip:    description: Floating IP address of server1    value: { get_attr: [ server1_floating_ip, floating_ip_address ] }  server2_private_ip:    description: Private IP address of server2    value: { get_attr: [ server2, first_address ] }  server2_public_ip:    description: Floating IP address of server2    value: { get_attr: [ server2_floating_ip, floating_ip_address ] }

这个ymal文件，大概是需要完成下面的工作

创建一个私有网络
创建一个路由器
连接好外部网络和内部网络
创建两个虚拟机，绑定floating ip

Heat目前支持两种格式的模板，一种是基于JSON格式的CFN模板；另外一种是基于YAML格式的HOT模板。CFN模板主要是为了保持对AWS的兼容性。HOT模板是Heat自有的，资源类型更加丰富，更能体现出Heat特点的模板。一个典型的 HOT 模板由下列元素构成：

模板版本：必填字段，指定所对应的模板版本，Heat 会根据版本进行检验。
参数列表：选填，指输入参数列表。
资源列表：必填，指生成的 Stack 所包含的各种资源。可以定义资源间的依赖关系，比如说生成Port，然后再用port来生成VM。
输出列表：选填，指生成的 Stack 暴露出来的信息，可以用来给用户使用，也可以用来作为输入提供给其它的 Stack。

NET_ID=$(nova net-list | awk '/ ext_net / { print $2 }')
SEC_ID=$(nova secgroup-list | awk '/ default / { print $2 }')
heat stack-create -f first-stack.yml -P image_id=cirros -P public_net=$NET_ID -P secgroup_id=$SEC_ID First_Stack

ubuntu@zhhuabj-bastion:~/openstack-charm-testing$ heat stack-list
+--------------------------------------+-------------+-----------------+----------------------+
| id                                   | stack_name | stack_status    | creation_time        |
+--------------------------------------+-------------+-----------------+----------------------+
| b36bdf67-bd59-401d-ab3b-f7437aa06c30 | First_Stack | CREATE_COMPLETE | 2015-12-19T10:18:49Z |
+--------------------------------------+-------------+-----------------+----------------------+

ubuntu@zhhuabj-bastion:~/openstack-charm-testing$ nova list
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| ID                                   | Name    | Status | Task State | Power State | Networks                           |
+--------------------------------------+---------+--------+------------+-------------+------------------------------------+
| 901d5365-01b6-4254-a65f-5177d804d074 | Server1 | ACTIVE | -          | Running     | private-net=172.16.2.3, 10.5.150.4 |
| f1441f2d-4fb2-4560-b0ff-85d0cde4bc45 | Server2 | ACTIVE | -          | Running     | private-net=172.16.2.4, 10.5.150.3 |

ubuntu@juju-zhhuabj-machine-7:~$ ps -ef|grep heat
root      3656     1 0 Dec08 ?        00:05:40 /var/lib/juju/tools/unit-heat-0/jujud unit --data-dir /var/lib/juju --unit-name heat/0 --debug
heat     20395     1 0 Dec08 ?        00:00:10 /usr/bin/python /usr/bin/heat-api --config-file=/etc/heat/heat.conf --log-file=/var/log/heat/heat-api.log
heat     20414     1 0 Dec08 ?        00:00:10 /usr/bin/python /usr/bin/heat-api-cfn --config-file=/etc/heat/heat.conf --log-file=/var/log/heat/heat-api-cfn.log
heat     20437     1 0 Dec08 ?        00:19:54 /usr/bin/python /usr/bin/heat-engine --config-file=/etc/heat/heat.conf --log-file=/var/log/heat/heat-engine.log

Heat也能对软件进行配置和部署的编排

Heat 提供了多种资源类型来支持对于软件配置和部署的编排，如下所列：

OS::Heat::CloudConfig： VM引导程序启动时的配置，由 OS::Nova::Server 引用
OS::Heat::SoftwareConfig：描述软件配置
OS::Heat::SoftwareDeployment：执行软件部署
OS::Heat::SoftwareDeploymentGroup：对一组 VM 执行软件部署
OS::Heat::SoftwareComponent：针对软件的不同生命周期部分，对应描述软件配置
OS::Heat::StructuredConfig：和 OS::Heat::SoftwareConfig 类似，但是用 Map 来表述配置
OS::Heat::StructuredDeployment：执行 OS::Heat::StructuredConfig 对应的配置
OS::Heat::StructuredDeploymentsGroup：对一组 VM 执行 OS::Heat::StructuredConfig 对应的配置

Heat 对负载均衡的编排

负载均衡也是一个很高级应用，它也是由一组不同的资源类型来实现的。资源类型包括：

OS::Neutron::Pool：定义资源池，一般可以由 VM 组成
OS::Neutron::PoolMember：定义资源池的成员
OS::Neutron::HealthMonitor：定义健康监视器，根据自定的协议，比如 TCP 来监控资源的状态，并提供给 OS::Neutron::Pool 来调整请求分发
OS::Neutron::LoadBalancer：关联资源池以定义整个负载均衡。

Heat对资源自动伸缩的编排
基础架构的自动伸缩是一个很高级的功能。Heat 提供自动伸缩组 OS::Heat::AutoScalingGroup 和伸缩策略 OS::Heat::ScalingPolicy，结合基于 Ceilometer 的 OS::Ceilometer::Alarm 实现了可以根据各种条件，比如负载，进行资源自动伸缩的功能。

如何使用Cirros作为例子镜像

Since cirros images don't currently support multi-part mime user-data, it's necessary to inject the hook script to the image and upload the modified image to glance:

https://github.com/openstack/heat-templates/tree/master/hot/software-config/example-templates/cirros-example
wget http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.img
virt-copy-in -a cirros-0.3.2-x86_64-disk.img init.d/heat-deploy-hook /etc/init.d
virt-copy-in -a cirros-0.3.2-x86_64-disk.img rc3.d/S99-heat-deploy-hook /etc/rc3.d
glance image-create --name cirros-0.3.2-sc --disk-format=qcow2 --container-format=bare < cirros-0.3.2-x86_64-disk.img
heat stack-create sc1 -f cirros-hello-world.yaml -P "image=cirros-0.3.2-sc"

或者用cirros 0.3.3：

glance image-create --name "Cirros 0.3.3" --disk-format qcow2 --container-format bare --is-public True --copy http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img
nova flavor-create m1.nano 42 64 0 1

或者在devstack中直接指定cirros的版本

CIRROS_VERSION=0.3.4

参考

[1] http://docs.openstack.org/developer/heat/template_guide/index.html

[2] http://www.ibm.com/developerworks/cn/cloud/library/1511_zoupx_openstackheat/index.htm

[3] https://github.com/openstack/heat-templates/tree/master/hot/software-config/example-templates/cirros-example

0 0