openstack
/
openstack-virtual-baremetal
Code Issues Proposed changes

Update introduction to reflect current status 

It's no longer true that OVB can't run on public clouds. This change
updates the introduction to better describe the current situation
with OVB on public cloud, and to make note of another limitation
that recently came to my attention.
This commit is contained in:
Ben Nemec 2018-09-07 11:38:38 -05:00
parent c61719f8c4
commit 405cf53ed1
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/introduction.rst
View File

@ -46,10 +46,12 @@ number of drawbacks:
resources, test environments can be easily tailored to their intended use
case.
One drawback to OVB at this time is that it is generally not compatible with
current public clouds. While it is possible to do an OVB deployment on a
completely stock OpenStack cloud, most public clouds have restrictions (older
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
configured for ideal compatibility. This situation should improve as more
public clouds move to newer OpenStack releases, however.
One drawback to OVB at this time is that it does have hard requirements on a
few OpenStack features (Heat, Neutron port-security, private image uploads,
for example) that are not all widely available in public clouds. Fortunately,
as they move to newer and newer versions of OpenStack that situation should
improve.
It should also be noted that without the Nova PXE boot patch, OVB is not
compatible with any workflows that write to the root disk before deployment.
This includes Ironic node cleaning.