devstack

History

Dean Troyer 768295e9f1 Add mechanism to automatically load additional projects This adds an extras.d directory to contain startup scripts that stack.sh runs automatically at the end. Similar to local.sh except the scripts are sourced into the stack.sh process rather than executed as a child process. This gives them complete access to the stack.sh environment. Convert Tempest to use this format as an example. Change-Id: Ibc95e6aaecf4211da948319eb452293ae4357780	2013-01-09 19:53:45 -06:00
..
80-tempest.sh	Add mechanism to automatically load additional projects	2013-01-09 19:53:45 -06:00
README	Add mechanism to automatically load additional projects	2013-01-09 19:53:45 -06:00

Dean Troyer 768295e9f1 Add mechanism to automatically load additional projects

This adds an extras.d directory to contain startup scripts that
stack.sh runs automatically at the end.  Similar to local.sh
except the scripts are sourced into the stack.sh process rather
than executed as a child process.  This gives them complete
access to the stack.sh environment.

Convert Tempest to use this format as an example.

Change-Id: Ibc95e6aaecf4211da948319eb452293ae4357780

2013-01-09 19:53:45 -06:00

80-tempest.sh

Add mechanism to automatically load additional projects

2013-01-09 19:53:45 -06:00

README

Add mechanism to automatically load additional projects

2013-01-09 19:53:45 -06:00

README

The extras.d directory contains project initialization scripts to be
sourced by stack.sh at the end of its run.  This is expected to be
used by external projects that want to be configured, started and
stopped with DevStack.

Order is controlled by prefixing the script names with the a two digit
sequence number.  Script names must end with '.sh'.  This provides a
convenient way to disable scripts by simoy renaming them.

DevStack reserves the sequence numbers 00 through 09 and 90 through 99
for its own use.

The scripts are called with an argument of 'stack' by stack.sh and
with an argument of 'unstack' by unstack.sh.