tripleo-puppet-elements 11.1.0

说明

签出此源树和DiskImage Builder，导出 elements_path从树中添加元素，并生成任何磁盘映像 需要：

git clone https://opendev.org/openstack/diskimage-builder.git
git clone https://opendev.org/openstack/tripleo-puppet-elements.git
export ELEMENTS_PATH=tripleo-puppet-elements/elements
diskimage-builder/bin/disk-image-create -u base vm bootstrap local-config stackuser heat-cfntools -a i386 -o bootstrap

公共元素组合

始终在要通过heat引导的映像中包含heat cfntools:if 否则，用户ssh密钥就不能可靠地从 与cloud init交互导致的元数据服务器。

架构

OpenStack图像将使用Nova+Heat进行部署和维护。

因此，它们应该努力成为无状态的，完全通过自动化来维护。

配置

在一个运行的openstack中有几个配置类别。

• per user - e.g. ssh key registration with nova: we repeat this sort of config every time we add a user.
• local node - e.g. nova.conf or ovs-vsctl add-br br-ex : settings that apply individually to machines
• inter-node - e.g. credentials on rabbitmq for a given nova compute node
• application state - e.g. ‘neutron net-create …’ : settings that apply to the whole cluster not on a per-user / per-tenant basis

我们有五个地方可以在tripleo中进行配置：

• 图像生成时间
• 例如热驱动（ORC脚本）
• 在实例中，首次启动脚本[已弃用]
• 从外部通过API
• 由Heat精心策划

我们目前决定在哪里进行任何特定配置的启发式方法 步骤：

• per user config should be done from the outside via APIs, even for users like ‘admin’ that we know we’ll have. Note that service accounts are different - they are a form of inter-node configuration.
• local node configuration should be done via ORC driven by Heat and/or configuration management system metadata.
• inter-node configuration should be done by working through Heat. For instance, creating a rabbit account for a nova compute node is something that Heat should arrange, though the act of creating is probably done by a script on the rabbit server - triggered by Heat - and applying the config is done on the compute node by the local node script - again triggered by Heat.
• application state changes should be done from outside via APIs
• first-boot scripts should not be used.