Skip to main content

Puppet building rules for OpenStack images.

Project description

http://governance.openstack.org/badges/tripleo-puppet-elements.svg

Puppet building rules for OpenStack images

These elements are used to build disk images for deploying OpenStack via Heat. They are built as part of the TripleO umbrella project.

Instructions

Checkout this source tree and also the diskimage builder, export an ELEMENTS_PATH to add elements from this tree, and build any disk images you need:

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

Common element combinations

Always include heat-cfntools in images that you intend to boot via heat : if that is not done, then the user ssh keys are not reliably pulled down from the metadata server due to interactions with cloud-init.

Architecture

OpenStack images are intended to be deployed and maintained using Nova + Heat.

As such they should strive to be stateless, maintained entirely via automation.

Configuration

In a running OpenStack there are several categories of config.

  • 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

We have five places we can do configuration in TripleO:
  • image build time

  • in-instance heat-driven (ORC scripts)

  • in-instance first-boot scripts [deprecated]

  • from outside via APIs

  • orchestrated by Heat

Our current heuristic for deciding where to do any particular configuration step:

  • 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.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tripleo-puppet-elements-11.1.1.tar.gz (36.9 kB view details)

Uploaded Source

Built Distribution

tripleo_puppet_elements-11.1.1-py2.py3-none-any.whl (50.2 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file tripleo-puppet-elements-11.1.1.tar.gz.

File metadata

  • Download URL: tripleo-puppet-elements-11.1.1.tar.gz
  • Upload date:
  • Size: 36.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.0 CPython/3.5.2

File hashes

Hashes for tripleo-puppet-elements-11.1.1.tar.gz
Algorithm Hash digest
SHA256 195c005e2fa24dcc14d7c916646fde64e8e92ba43dda84aaccf1fdf568a5e545
MD5 72a029d9755bf452e2ac694a4e63d94e
BLAKE2b-256 94cd58226640e8c9d6056832b981bdb2dfbdd691295287d91111824790d82fa1

See more details on using hashes here.

Provenance

File details

Details for the file tripleo_puppet_elements-11.1.1-py2.py3-none-any.whl.

File metadata

  • Download URL: tripleo_puppet_elements-11.1.1-py2.py3-none-any.whl
  • Upload date:
  • Size: 50.2 kB
  • Tags: Python 2, Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.0 CPython/3.5.2

File hashes

Hashes for tripleo_puppet_elements-11.1.1-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 4963da3442fe7711c8b5fa3b947331b9d3a0a8363bd1d6d7d7440849e7729592
MD5 0776ced861ea2a2c724d1d6a84636dd0
BLAKE2b-256 7dbb446881c28f55722bfc42deace4a974e80acb59a4aeea24a541180542aff8

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page