Skip to main content

Disk image builder elements for deploying OpenStack.

Project description

https://governance.openstack.org/tc/badges/tripleo-image-elements.svg

Image 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:

virtualenv .
source bin/activate
pip install dib-utils pyyaml
git clone https://opendev.org/openstack/diskimage-builder.git
git clone https://opendev.org/openstack/tripleo-image-elements.git
export ELEMENTS_PATH=tripleo-image-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)

  • 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

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-image-elements-15.0.0.tar.gz (77.0 kB view details)

Uploaded Source

Built Distribution

tripleo_image_elements-15.0.0-py3-none-any.whl (72.8 kB view details)

Uploaded Python 3

File details

Details for the file tripleo-image-elements-15.0.0.tar.gz.

File metadata

File hashes

Hashes for tripleo-image-elements-15.0.0.tar.gz
Algorithm Hash digest
SHA256 667c581c6a0fc193a475207cea24a4af8ddb2464929dc333e36391afcbd84e6b
MD5 efcc4ba8b71fea5fbd4914b0fbb4bd5e
BLAKE2b-256 716ad12b8331c0743906b9abbd1776048a26eeb1512df455913192fdbdefb7b8

See more details on using hashes here.

File details

Details for the file tripleo_image_elements-15.0.0-py3-none-any.whl.

File metadata

File hashes

Hashes for tripleo_image_elements-15.0.0-py3-none-any.whl
Algorithm Hash digest
SHA256 227790563b959c58926eac72a0d1a74784fe52b0c14dbc9005c45456426a024b
MD5 04a48d3909e6ae9548b72d3a9547d045
BLAKE2b-256 4681be7f03c97635c5329117eb09a885236e56f889c168889380ef061f843fdd

See more details on using hashes here.

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