Repository cleanup after virtualbox scripts removed
Virtualbox scripts have been moved to a separate git repository https://review.openstack.org/#/c/279074/ Change-Id: Ic0965f26fb43c542161a2eb8d1264eff80ed1f77 Closes-Bug: #1549114
This commit is contained in:
parent
582d85f5fe
commit
a1a8d56353
|
@ -16,7 +16,6 @@
|
|||
build
|
||||
dist
|
||||
/local_mirror
|
||||
/virtualbox/iso/*.iso
|
||||
nosetests.xml
|
||||
nailgun.log
|
||||
lock
|
||||
|
|
|
@ -139,12 +139,6 @@ pieces of Fuel build system:
|
|||
|
||||
* **iso** - contains **make** scripts for building Fuel ISO file.
|
||||
|
||||
**Fuel-main** also contains a set of directories which are not directly
|
||||
related to Fuel build processes:
|
||||
|
||||
* **virtualbox** - contains a set of shell scripts
|
||||
which allow one to deploy Fuel demo lab easily using VirtualBox.
|
||||
|
||||
|
||||
.. _build-targets:
|
||||
|
||||
|
@ -208,14 +202,6 @@ They are defined in **config.mk** file:
|
|||
just ISO name.
|
||||
By default, it is **$(ARTS_DIR)/$(ISO_NAME).iso**.
|
||||
|
||||
* **VBOX_SCRIPTS_NAME** - defines the name of the archive with
|
||||
VirtualBox scripts.
|
||||
By default, it is placed into **$(VBOX_SCRIPTS_NAME).zip**.
|
||||
|
||||
* **VBOX_SCRIPTS_PATH** - defines full path for
|
||||
VirtualBox scripts archive.
|
||||
By default, it is **$(ARTS_DIR)/$(VBOX_SCRIPTS_NAME).zip**
|
||||
|
||||
* Fuel ISO contains some default settings for the
|
||||
Fuel Master node. These settings can be customized
|
||||
during Fuel Master node installation.
|
||||
|
|
|
@ -145,7 +145,7 @@ How to execute my tests?
|
|||
Simplest way is to install Fuel, and OSTF will be installed as part of it.
|
||||
- install virtualbox
|
||||
- build Fuel ISO: :ref:`building-fuel-iso`
|
||||
- use `virtualbox scripts to run an ISO <https://github.com/openstack/fuel-main/tree/master/virtualbox>`_
|
||||
- use `virtualbox scripts to run an ISO <https://github.com/openstack/fuel-virtualbox/tree/master/>`_
|
||||
- once the installation is finished, go to Fuel UI (usually it's 10.20.0.2:8000) and create a new cluster with necessary configuration
|
||||
- execute::
|
||||
|
||||
|
|
Loading…
Reference in New Issue