e8cecab45c
Augment the developing_elements.rst by taking advantage of Sphinx markup. Most of the doc used to be in /README.md and thus did not leverage on Sphinx. Use inline codeblock to denote variables, files, command: ``foo`` Phase Subdirectories: List phase names in the preliminary introduction Get rid of lists in favor of definitions Highlight whether the phase runs in or outside the chroot Input parameters are now lists Use definition lists in Dependencies and Ramdisk sections. Link to elements README when they exist. Testing Element: split into two subsections: 'shell' and 'python'. Use "sourcecode:: sh" for the couple examples at the very top and very bottom of the document. Change-Id: I2421f76ec452cac243ccb2208f88c7d320ffedd3
Image building tools for OpenStack
These tools are the components of TripleO (https://wiki.openstack.org/wiki/TripleO) that are responsible for building disk images.
This repository has the core functionality for building disk images, file system images and ramdisk images for use with OpenStack (both virtual and bare metal). The core functionality includes the various operating system specific modules for disk/filesystem images, and deployment and hardware inventory ramdisks.
The TripleO project also develops elements that can be used to deploy OpenStack itself. These live in the TripleO elements repository (https://git.openstack.org/cgit/openstack/tripleo-image-elements).
Online documentation:
Copyright
Copyright 2012 Hewlett-Packard Development Company, L.P. Copyright (c) 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.