精华内容
下载资源
问答
  • OpenStack Heat 源码分析 是 OpenStack 项目中负责部署、协调资源的平台工具,它允许用户提前写好一个模板文件,然后通过 Heat 引擎来启动、停止所定义的资源。 本书将剖析 Heat 组件(服务端)的代码。 最新版本...
  • CompactHeatExchangers

    2019-02-02 09:29:27
    It is essential for newcomers to the field to have a reliable guide to the important design considerations of CHEs. This book provides for the first time an in-depth coverage of CHEs, and it will ...
  • OpenStack Heat编排管理功能介绍技术创新变革未来Heat为OpenStack提供资源编排服务完成OpenStack中资源及应用的自动部署掌握Heat知识对自动化运维OpenStack至关重要本章节分为两个部分理论和实验理论部分主要讲解...
  • ADI_method.pdf - 使用 ADI 方法写下热方程的数值解solve_heat_equation_implicit_ADI.m - 使用 ADI 方法的数值解的代码thomas_algorithm.m - 求解三对角矩阵的快速算法compare_to_analytical_solution.m - 用于将 ...
  • simulink 搭建的气气式换热器模型
  • 精主轴传动系统热流密度计算,换热系数及热传导计算
  • 只需编写一个描述您的基础设施资源(实例、网络、数据库、图像...)的 Heat 模板并将其发送到 Heat! 它将与所有其他 OpenStack API 通信以部署您的堆栈! 如果您想扩展或重新设计您的基础架构,请修改模板并更新您...
  • 热传递 matlab代码 Heat-Transfer Codes (Matlab & Python Scripts) for Heat Transfer
  • 谷歌热瓷砖 Google 地图的热图图块 ... script type =" text/javascript " src =" path/to/google-heat-tiles.js " > </ script > 通用JS var HeatTiles = require ( 'path/to/google-heat-tiles' ) ; AMD
  • 计量(Ceilometer)服务  以标准格式收集数据存储和系统资源使用信息,而统计和计费。同时可获取操作执行所产生的信息、触发通知。采用客户端部署agent的架构,收集数据,将数据存放在数据库中,或者提供一个处理...
  • heat_flux_ABAQUS_MMucha.pdf

    2020-05-29 09:16:23
    L型平板的热传导过程ABAQUS有限元建模详解,稳态热传导,各向异性材料,热流边界条件和温度边界条件,温度场输出
  • Thermal radiation heat transfer
  • Heat Conduction

    2018-06-01 10:47:56
    Provide students with the tools to model, analyze and solve a wide range of engineering applications involving conduction heat transfer.
  • Heat-Equation-源码

    2021-07-10 14:56:29
    解热方程的各种方案。 我们提出一维问题来求解网格节点中的热方程。 ([维基百科]) 输入: 参数 a 的值 X 左 X 右 T左 右 F - 方程的右边部分 t = 0 的初始条件 ... - Wolfram Mathematica 的表达式以绘制精确解和...
  • Modest 的经典书籍Radiative_Heat_Transfer第三版,辐射换热理论经典
  • Heat2D是一个简单而简洁的2D游戏引擎。 该引擎的主要目的是通过提供有目的性和有用的工具和库来简化和加速游戏开发过程。 Heat2D易于使用,您可以访问。 您可以使用API​​参考,或者,如果您是初学者,请阅读入门...
  • Our reassembly algorithm employs a sale-space representation of shape based on the heat kernel, which only depends on the intrinsic geometry of the surfaces. Partial matching and then be conducted e&...
  • 该存储库包含heat1d行星热模型的源代码和示例。 以目前的形式, heat1d使用有限差分法求解一维热方程。 主要特征包括与深度和温度有关的热物理性质,以及适合不同行星体的边界条件。 正在开发三种不同语言的实现: C...
  • heat-ooo-源码

    2021-03-29 23:52:31
    heat-ooo
  • Heat RevA_PID控温_源码

    2021-10-03 04:57:17
    利用STC的8系列单片机实现固态继电器PID控温
  • China Heat Map.xlsm

    2021-02-23 00:08:09
    China Heat Map.xlsm
  • Esri传单热图特征图层 Esri Leaflet的插件,可将功能服务可视化为基于 Leaflet插件构建的热图。 演示版 现场演示可以在。 例 这是一个快速的示例,可以帮助您入门。 <... meta name =' viewport ' content =' ...
  • 文件:FEM_for_heat_equation-确定性的情况。 FEM_for_the_Stochastic_Heat_Equation-随机情况。 Generate_FEM_Mesh-非简单域的三角剖分。 Dloc-局部质量矩阵的函数。 Bloc-局部刚度矩阵的函数。 FEM_RHS_t-热量方程...
  • 自动缩放 OpenStack Heat、Ceilometer 和 Autoscale 的参考内容 此存储库包含有关使用 OpenStack 进行自动缩放的安装、配置和测试的内容。
  • python-heatclient OpenStack Orchestration API客户端库 这是基于Heat编排API的Heat的客户端库。 它提供了一个Python API( heatclient模块)和一个命令行工具( heat )。 免费软件:Apache许可证 软件包安装 -...
  • Openstack Heat try-out What’s Heat ? How to install Heat and make it ready to use? 1.Installation 2.Prepare JEOS(Just enough OS) Use cases 1.Deploy a single WordPress blog server with a floating ...

     

    Openstack Heat try-out

    How to install Heat and make it ready to use?

    Use cases

    Whats Heat ?

    Heat is a service to orchestrate multiple composite cloud applications using the AWS CloudFormation template format, its Openstacks implementation of CloudFormation and CloudWatch.

    Heat integrates other core components of OpenStack into a one-file template system. The templates allow creation of most OpenStack resource types, the main functions of Heat cover:

    -vAPP stack creation/update/deletion (suspend/resume will be added in Havana)
    -High Availability
    -Autoscaling
    -Manual scale in/out(in Havana)

    How to install Heat and make it ready to use?

    1.Installation

    ->Heat has been included in RDO repo, installation can be done by Yum:

    yum install openstack-heat-api openstack-heat-api-cfn openstack-heat-api-cloudwatch openstack-heat-cli openstack-heat-common openstack-heat-engine python-heatclient python-heatclient-doc heat-cfntools heat-jeos

    ->Comment out following line since we use RabbitMQ instead of QPID as message queue. Do this for heat-api-cfn.conf, heat-api-cloudwatch.conf, heat-api.conf, heat-engine.conf under /etc/heat.

    #rpc_backend=heat.openstack.common.rpc.impl_qpid

    ->Configure [filter:authtoken] section of heat-api-cfn-paste.ini  heat-api-cloudwatch-paste.ini  heat-api-paste.ini under /etc/heat

    [filter:authtoken]
    paste.filter_factory = heat.common.auth_token:filter_factory
    service_protocol = http
    service_host = api-vip
    service_port = 5000
    auth_host = api-vip
    auth_port = 35357
    auth_protocol = http
    auth_uri = http://api-vip:35357/v2.0
    admin_tenant_name = service
    admin_user = heat
    admin_password = password

    ->Configure [filter:ec2authtoken] section of  heat-api-cfn-paste.ini  heat-api-cloudwatch-paste.ini under /etc/heat

    [filter:ec2authtoken]
    paste.filter_factory = heat.api.aws.ec2token:EC2Token_filter_factory
    auth_uri = http://api-vip:5000/v2.0
    keystone_ec2_uri = http://api-vip:5000/v2.0/ec2tokens

    >Update /etc/heat/heat-engine.conf as below:

    heat_metadata_server_url = http://10.68.125.11:8000
    heat_waitcondition_server_url = http://10.68.125.11:8000/v1/waitcondition
    heat_watch_server_url = http://10.68.125.11:8003
    sql_connection = mysql://heat:heat@db-vip/heat

    #The IP for metadata, watchcondition and watch_server should be the host IP of heat services are running on, and should be reachable from VM instance.

    ->Setup database for heat:

    heat-db-setup rpm -y -r <root password of mysql>

    ->Setup keystone entries for heat:

    heat-keystone-setup

    ->Start heat services:

    service openstack-heat-api start
    service openstack-heat-api-cfn start
    service openstack-heat-api-cloudwatch start
    service openstack-heat-engine start

    2.Prepare JEOS(Just enough OS)

    JEOS image is basic OS image with cloud-init  and heat-cfn-tools pre-installed, they are the keys for Heat and VM exchanging information and doing post and regular jobs.

    Pre-built JEOS of Fedora 17 and 18 can be downloaded from: http://fedorapeople.org/groups/heat/prebuilt-jeos-images/

    To make our own JEOS on RHEL, following the steps:

    a.Assume we have a RHEL 6.3 image registered in Glance already, launch a VM instance from it.
    b.Log into the VM, install cloud-init and heat-cfn-tools

    yum -y update
    export http_proxy=<http proxy server IP>   #This is needed if lab has no direct internet access
    curl -O
    http://ftp.ps.pl/pub/Linux/fedora-epel/6/i386/epel-release-6-7.noarch.rpm
    rpm -Uvh epel-release-6-7.noarch.rpm
    yum -y install perl python python-setuptools cloud-init python-pip
    pip-python install argparse
    boto==2.5.2 heat-cfntools
    cfn-create-aws-symlinks
    source /usr/bin
    rm -rf /etc/udev/rules.d/70-persistent-net.rules

    c.From Horizon GUI or CLI, make a snapshot for this VM, name it as rhel63-x86_64-cfntools.  This snapshot actually becomes a valid JEOS image.

    Use cases

    1.Deploy a single WordPress blog server with a floating IP associated.

    This templates deploy a single VM instance with a associated floating IP, then install mysql-server, httpd and wordpress packages, initial database, integrate each other and finally start up wordpress web service.

    ->Download the template file:

    wget https://github.com/abckey/heat-templates/raw/master/WordPress_Single_Instance_With_EIP.template

    ->Source a tenant credential

    source /root/nceprc

    >Create a key-pair

    nova  keypair-add ncepkey > ncepkey.pem

    chmod 400 ncepkey.pem

    ->Deploy this template by heat

    heat stack-create wordpress  -f WordPress_Single_Instance_With_EIP.template -P InstanceType=m1.medium;DBUsername=wordpress;DBPassword=worldpress;KeyName=ncepkey;LinuxDistribution=RHEL-6.3

    #Parameters followed after -P are needed for instance type selection, DB access setup, key-pair selection and image selection.

    ->Check stack creation process

    Once the stack-create is issued, we should see the stack in CREATE_IN_PROGRESS status from output of heat list

    Once creation is complete, we can see the status will change to CREATE_COMPLETE.

    [root@controller-1 heat(keystone_ncep)]# heat list
    +
    ————————————–+————–+—————–+———————-+
    | ID | Name | Status | Created |
    +
    ————————————–+————–+—————–+———————-+
    | a6740599-2c98-41b8-a55e-490f28f6f6f8 | wordpress | CREATE_COMPLETE | 2013-08-05T06:57:40Z |
    +
    ————————————–+————–+—————–+———————-+

    We can also see detailed resource status in the stack by:

    [root@controller-1 heat(keystone_ncep)]# heat resource-list wordpress
    +
    ————————+————————–+—————–+———————-+
    | Name | Type | Status | Updated |
    +
    ————————+————————–+—————–+———————-+
    | IPAddress | AWS::EC2::EIP | CREATE_COMPLETE | 2013-08-05T06:57:40Z |
    | WebServerSecurityGroup | AWS::EC2::SecurityGroup | CREATE_COMPLETE | 2013-08-05T06:57:41Z |
    | IPAssoc | AWS::EC2::EIPAssociation | CREATE_COMPLETE | 2013-08-05T06:57:52Z |
    | WebServer | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T06:57:52Z |
    +
    ————————+————————–+—————–+———————-+

    Also heat stack-show wordpress can be used to show detailed information of the stack

    ->Try to access the wordpress web UI

    From nova list, we could see a VM named wordpress.WebServer is created with internal IP and floating IP:

    [root@controller-1 heat(keystone_ncep)]# nova list
    +
    ————————————–+——————————————–+——–+————————————-+
    | ID | Name | Status | Networks |
    +
    ————————————–+——————————————–+——–+————————————-+|
    | 02da7185-a0a6-44cf-8076-875754163dac | wordpress.WebServer | ACTIVE | ncep-net=10.20.20.17, 10.68.124.102 |
    +
    ————————————–+——————————————–+——–+————————————-+

    Try to access the wordpress website by its floating IP

    http://10.68.124.102/wordpress

    You should see the login page in the browser!!!

    2.Deploy wordpress blog server with 2 VM instances(front-end + back-end topology)

    This template deploy a 2 VM wordpress solution, one VM running web server, 2nd VM running Mysql DB.

    ->Download the template:

    wget https://github.com/abckey/heat-templates/raw/master/WordPress_2_Instances.template

    ->Deploy the template by heat

    heat stack-create wp-2-vm  -f WordPress_2_Instances.template -P InstanceType=m1.medium;DBUsername=wordpress;DBPassword=worldpress;KeyName=ncepkey;LinuxDistribution=RHEL-6.3

    >From heat resource-list wp-2-vm, we can see 2 VM instances are created, also a floating IP and association with Webserver is there

    [root@controller-1 heat(keystone_ncep)]# heat resource-list wp-2-vm
    +
    —————-+————————–+—————–+———————-+
    | Name | Type | Status | Updated |
    +
    —————-+————————–+—————–+———————-+
    | DatabaseServer | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T07:14:04Z |
    | IPAddress | AWS::EC2::EIP | CREATE_COMPLETE | 2013-08-05T07:14:13Z |
    | WebServer | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T07:14:13Z |
    | IPAssoc | AWS::EC2::EIPAssociation | CREATE_COMPLETE | 2013-08-05T07:14:14Z |
    +
    —————-+————————–+—————–+———————-+

    ->Try wordpress website with floating IP of WebServer VM instance

    [root@controller-1 heat(keystone_ncep)]# nova list
    +
    ————————————–+——————————————–+——–+————————————-+
    | ID | Name | Status | Networks |
    +
    ————————————–+——————————————–+——–+————————————-+
    | 4879bb03-bc20-4c33-91e2-d4a7e197d2e5 | wp-2-vm.DatabaseServer | ACTIVE | ncep-net=10.20.20.18 |
    | 8e1dc2c7-bc34-4e5d-b833-b64dc8a12c9b | wp-2-vm.WebServer | ACTIVE | ncep-net=10.20.20.19, 10.68.124.103 |
    +
    ————————————–+——————————————–+——–+————————————-+

    http://10.68.124.103/wordpress

    3.Deploy a wordpress blog server with EBS volume as mysql DB storage

    This template deploy a VM instance with httpd, wordpress and mysql-server installed, a EBS volume is attached to instance as Mysql DB storage point.

    ->Download the template

    wget https://github.com/abckey/heat-templates/raw/master/WordPress_Single_Instance_With_EBS_EIP.template

    ->Deploy

    heat stack-create wp-ebs -f WordPress_Single_Instance_With_EBS_EIP.template -P VolumeSize=5;InstanceType=m1.medium;DBUsername=wordpress;DBPassword=worldpress;KeyName=ncepkey;LinuxDistribution=RHEL-6.3

    #Here we need use parameter VolumeSize to specify the volume size we intend to use as DB storage.

    ->From resource list , we can see it has volume and volume attachment there

    [root@controller-1 heat(keystone_ncep)]# heat resource-list wp-ebs
    +
    ————————-+—————————-+—————–+———————-+
    | Name | Type | Status | Updated |
    +
    ————————-+—————————-+—————–+———————-+
    | DataVolume | AWS::EC2::Volume | CREATE_COMPLETE | 2013-08-05T07:35:48Z |
    | WikiServerSecurityGroup | AWS::EC2::SecurityGroup | CREATE_COMPLETE | 2013-08-05T07:35:48Z |
    | IPAddress | AWS::EC2::EIP | CREATE_COMPLETE | 2013-08-05T07:35:59Z |
    | WikiServer | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T07:35:59Z |
    | IPAssoc | AWS::EC2::EIPAssociation | CREATE_COMPLETE | 2013-08-05T07:36:00Z |
    | MountPoint | AWS::EC2::VolumeAttachment | CREATE_COMPLETE | 2013-08-05T07:36:02Z |
    +
    ————————-+—————————-+—————–+———————-+

    ->Check volume and attachment

    [root@controller-1 heat(keystone_ncep)]# cinder list
    +
    ————————————–+——–+————————-+——+————-+———-+————————————–+
    | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
    +
    ————————————–+——–+————————-+——+————-+———-+————————————–+
    | 16c9c84f-9bf3-43c7-853d-453ec161b170 | in-use | wp-ebs.DataVolume | 5 | None | false | 0738154d-8d58-4a84-a5fc-71774228105d |
    +
    ————————————–+——–+————————-+——+————-+———-+————————————–+

    Inside vm, we can check mounts:

    [root@wp-ebs ~]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/vda1 5.0G 1.6G 3.1G 34% /
    tmpfs 1.9G 0 1.9G 0% /dev/shm
    /dev/vdb1 938M 39M 853M 5% /var/lib/mysql

    ->Try to access wordpress by floating IP.

    4.Deploy a wordpress blog server with HA protection enabled

    This template deploy a VM instance with wordpress server installed, and HA is enabled to monitor httpd/mysqld services to make sure they are already running.

    ->Download template:

    wget https://github.com/abckey/heat-templates/raw/master/WordPress_Single_Instance_With_HA.template

    ->Assign admin role to the tenant user by keystone user-role-add command.

    To use HA, waitcondition resource is needed, which needs to create an ec2signed url and to do that it creates a restricted user in keystone. To create any user in keystone we need admin rights:(

    This issue has been addressed by a bug ticket: https://bugs.launchpad.net/bugs/1089261

     keystone user-role-add user <ncep user id> role <admin role id>  tenant-id <ncep tenant id>

    ->Deploy

    heat stack-create wp-ha -f WordPress_Single_Instance_With_HA.template -P HupPollInterval=1;InstanceType=m1.medium;DBUsername=wordpress;DBPassword=worldpress;KeyName=ncepkey;LinuxDistribution=RHEL-6.3

    #Parameter HupPollInterval is needed to specify the cfn-hup process running interval in minutes, cfn-hup is to check services status, and restart them if return code of service <service name> status is not 0.

    ->Check resource

    [root@controller-1 heat(keystone_ncep)]# heat resource-list wp-ha
    +
    —————+——————————————+—————–+———————-+
    | Name | Type | Status | Updated |
    +
    —————+——————————————+—————–+———————-+
    | CfnUser | AWS::IAM::User | CREATE_COMPLETE | 2013-08-05T07:53:30Z |
    | WaitHandle | AWS::CloudFormation::WaitConditionHandle | CREATE_COMPLETE | 2013-08-05T07:53:30Z |
    | WebServerKeys | AWS::IAM::AccessKey | CREATE_COMPLETE | 2013-08-05T07:53:30Z |
    | WaitCondition | AWS::CloudFormation::WaitCondition | IN_PROGRESS | 2013-08-05T07:53:41Z |
    | WikiDatabase | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T07:53:41Z |
    +
    —————+——————————————+—————–+———————-+

    Here WaitCondition actually is waiting VM instance is properly started and configured, then goes to next step

    Whole resource list after create_complete:

    [root@controller-1 heat(keystone_ncep)]# heat resource-list wp-ha
    +
    ————————+——————————————+—————–+———————-+
    | Name | Type | Status | Updated |
    +
    ————————+——————————————+—————–+———————-+
    | CfnUser | AWS::IAM::User | CREATE_COMPLETE | 2013-08-05T07:53:30Z |
    | WebServerKeys | AWS::IAM::AccessKey | CREATE_COMPLETE | 2013-08-05T07:53:30Z |
    | WaitHandle | AWS::CloudFormation::WaitConditionHandle | CREATE_COMPLETE | 2013-08-05T07:54:41Z |
    | WikiDatabase | AWS::EC2::Instance | CREATE_COMPLETE | 2013-08-05T07:54:41Z |
    | HttpFailureAlarm | AWS::CloudWatch::Alarm | CREATE_COMPLETE | 2013-08-05T07:54:47Z |
    | WaitCondition | AWS::CloudFormation::WaitCondition | CREATE_COMPLETE | 2013-08-05T07:54:47Z |
    | WebServerRestartPolicy | OS::Heat::HARestarter | CREATE_COMPLETE | 2013-08-05T07:54:47Z |
    +
    ————————+——————————————+—————–+———————-+

    Resource OS::Heat::HARestart takes care of service HA.

    ->Try to access wordpress web by floating IP

    Login page should show up.

    ->Try HA by stopping httpd service

    In the VM, do service httpd stop.

    Check cfn-hup.log

    [root@wp-ha ~]# tail -f /var/log/cfn-hup.log

    DEBUG [2013-08-05 16:28:02,552] Running command: /sbin/service httpd status
    DEBUG [2013-08-05 16:28:02,609] Return code of 3 after executing:
    ['su', 'root', '-c', u'/sbin/service httpd status']
    WARNING [2013-08-05 16:28:02,610] Restarting service httpd
    DEBUG [2013-08-05 16:28:02,610] Running command: /sbin/service httpd start
    DEBUG [2013-08-05 16:28:02,732] Running command: /etc/cfn/notify-on-httpd-restarted
    DEBUG [2013-08-05 16:28:03,634] Running command: /sbin/service mysqld status
    DEBUG [2013-08-05 16:28:03,714] Running command: /sbin/service crond status

    We can see once cfn-hup found httpd service has problem, it tried to start httpd service.

    ->Check wordpress web access again, it should work again.

     

    原文处处不明,此处为笔记,侵删。

    展开全文
  • 热传递matlab代码使用传热数据的TCN模型 TCN中间图像(训练期间的预测图像) 项目组织 ├── README.md <- Organizational chart of this project. │ ├── data │ ├── bdd_feu <...mat
  • 语言:English (United States) 您的制表符背景仅需要极品飞车热量的最佳高清图像。 每个选项卡上的极品飞车高清图像! 您将获得:1:高清新标签页体验2:简单,清晰的视图! 没有无用的工具,图块或小部件!...
  • ozisik heat conduction
  • HEAT-源码

    2021-03-27 03:36:32
    HEATHEAT Plus均可作为在线版本和可下载的桌面版本使用。 有关HEATHEAT Plus的更多信息,请访问WHO网站: : 源代码 源代码在4个存储库中可用: 版权 :copyright:世界卫生组织版权所有,2016-2021年。 建议引用...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 18,054
精华内容 7,221
关键字:

heat