openstack/bifrost
Code Issues Proposed changes

Follow-up doc patch for 200834

Browse Source 
Updating the README.rst file to be more clear and added an
additional note in the test script to provide better documentation
and context to a user reviewing those areas.

Change-Id: I59718b83928f2cccb198dcc993967be4d809ad70
This commit is contained in:
Julia Kreger 2015-07-15 07:41:22 -04:00
parent edd5b67afc
commit abbd7ca060
2 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -374,8 +374,8 @@ to consume the entire disk, which may, or may not be desirable depending
upon operational needs. This is dependent upon what base OS image you upon operational needs. This is dependent upon what base OS image you
utilize, and if the support is included in that image or not. At present, utilize, and if the support is included in that image or not. At present,
the standard ubuntu cloud image includes cloud-init which will grow the the standard ubuntu cloud image includes cloud-init which will grow the
root partition, however the minimal image does not include the image, and root partition, however the ubuntu-minimal image does not include cloud-init
thus will not grow the root partition. and thus will not automatically grow the root partition.
Due to the nature of the design, it would be relatively easy for a user to Due to the nature of the design, it would be relatively easy for a user to
import automatic growth or reconfiguration steps either in the image to be import automatic growth or reconfiguration steps either in the image to be

7
scripts/test-bifrost.sh
View File

@ -35,8 +35,15 @@ ansible-playbook -vvvv -i inventory/localhost test-bifrost-create-vm.yaml
export BIFROST_INVENTORY_SOURCE=/tmp/baremetal.csv export BIFROST_INVENTORY_SOURCE=/tmp/baremetal.csv
# Execute the installation and VM startup test. # Execute the installation and VM startup test.
# NOTE(TheJulia): The variables defined on the command line are to
# drive the use of Cirros as the deployed operating system, and
# as such sets the test user to cirros, and writes a debian style
# interfaces file out to the configuration drive as cirros does
# not support the network_info.json format file placed in the
# configuration drive.
ansible-playbook -vvvv -i inventory/bifrost_inventory.py test-bifrost-dynamic.yaml -e use_cirros=true -e testing_user=cirros -e write_interfaces_file=true ansible-playbook -vvvv -i inventory/bifrost_inventory.py test-bifrost-dynamic.yaml -e use_cirros=true -e testing_user=cirros -e write_interfaces_file=true
EXITCODE=$? EXITCODE=$?
if [ $EXITCODE != 0 ]; then if [ $EXITCODE != 0 ]; then
echo "****************************" echo "****************************"
echo "Test failed. See logs folder" echo "Test failed. See logs folder"