OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|4 days ago|
|doc/source||1 year ago|
|elements||1 month ago|
|releasenotes||5 days ago|
|tests||8 months ago|
|tools||1 year ago|
|zuul.d||4 months ago|
|.gitignore||2 years ago|
|.gitreview||4 days ago|
|.testr.conf||6 years ago|
|HACKING.rst||5 months ago|
|LICENSE||6 years ago|
|MANIFEST.in||5 years ago|
|README.md||8 months ago|
|babel.cfg||6 years ago|
|requirements.txt||3 years ago|
|run-flake8||4 years ago|
|setup.cfg||4 months ago|
|setup.py||5 years ago|
|test-requirements.txt||2 months ago|
|tox.ini||3 months ago|
These elements are used to build disk images for deploying OpenStack via Heat. They are built as part of the TripleO (https://wiki.openstack.org/wiki/TripleO) umbrella project.
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://git.openstack.org/openstack/diskimage-builder.git git clone https://git.openstack.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
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.
OpenStack images are intended to be deployed and maintained using Nova + Heat.
As such they should strive to be stateless, maintained entirely via automation.
In a running OpenStack there are several categories of config.
We have five places we can do configuration in TripleO:
Our current heuristic for deciding where to do any particular configuration step:
Copyright 2012,2013 Hewlett-Packard Development Company, L.P. Copyright © 2012 NTT DOCOMO, INC.
All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/tripleo-image-elements