ccec11f9c8
TripleO CI uses 10.0.0.1 statically for the undercloud's
public interface. When using extra node in some job's
there is sometime a conflict, because the extra node get's
the 10.0.0.1 address allocated.
Adding support to define the allocation pools on the
public_net allows TripleO CI to define a pool with the
10.0.0.1 address eliminated.
A good practice would be to set up OVB to use
[{start: 10.0.0.128, end: 10.0.0.253}], and then configure
the undercloud/overcloud deployed on the OVB infrastructure
to use addresses in the range 10.0.0.1-10.0.0.127.
The parameter public_net_allocation_pools controls the
allocation pool setting, by default all addresses of the
subnet is in the pool.
Related-Bug: #1874418
Change-Id: Ieca4864e069148abb49eb709bf7f48a14ef04e77
|
||
|---|---|---|
| bin | ||
| doc/source | ||
| environments | ||
| ipxe | ||
| openstack_virtual_baremetal | ||
| overcloud-templates | ||
| patches/nova | ||
| sample-env-generator | ||
| templates | ||
| .gitignore | ||
| .gitmodules | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
OpenStack Virtual Baremetal
OpenStack Virtual Baremetal is a way to use OpenStack instances to do simulated baremetal deployments. For more details, see the full documentation.