openstack/openstack-virtual-baremetal
Code Issues Proposed changes

Further tweaks to the introduction

Browse Source 
A few wording changes and a split of the introduction and the
discussion of benefits and drawbacks.  Also added a basic description
of an OVB environment.
This commit is contained in:
Ben Nemec 2017-01-06 09:47:21 -06:00
parent f46ac2263a
commit fed222bba0
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.rst
View File

@ -14,8 +14,16 @@ of the following pieces:
VMs, networks, and other resources needed. VMs, networks, and other resources needed.
- An OpenStack BMC that can be used to control OpenStack instances via IPMI - An OpenStack BMC that can be used to control OpenStack instances via IPMI
commands. commands.
- A tool to collect details from the deployed instances that are required to - A tool to collect details from the "baremetal" VMs so they can be added as
add them as nodes to be deployed by the OpenStack Ironic project. nodes in the OpenStack Ironic baremetal deployment project.
A basic OVB environment is just a BMC VM configured to control a number
of "baremetal" VMs. This allows them to be treated largely the same
way a real baremetal system with a BMC would. A number of additional
features can also be enabled to add more to the environment.
Benefits and Drawbacks
----------------------
OVB started as part of the OpenStack TripleO project. It was intended to OVB started as part of the OpenStack TripleO project. It was intended to
provide more flexible and scalable development and CI environments. Previous provide more flexible and scalable development and CI environments. Previous
@ -41,8 +49,8 @@ current public clouds. While it is possible to do an OVB deployment on a
completely stock OpenStack cloud, most public clouds have restrictions (older completely stock OpenStack cloud, most public clouds have restrictions (older
OpenStack releases, inability to upload new images, no Heat, etc.) that make OpenStack releases, inability to upload new images, no Heat, etc.) that make
it problematic. At this time, OVB is primarily used with semi-private clouds it problematic. At this time, OVB is primarily used with semi-private clouds
configured for ideal compatibility. As more public clouds move to newer configured for ideal compatibility. This situation should improve as more
OpenStack releases this situation should improve, however. public clouds move to newer OpenStack releases, however.
How-To How-To
------ ------