Skip to content

Latest commit

 

History

History
43 lines (28 loc) · 1.59 KB

cli-workflow.md

File metadata and controls

43 lines (28 loc) · 1.59 KB

Standard GBE CLI workflow

Bootstrap a new GBE environment:

  • $TURBINE_ENVIRONMENT is the environment variable used to designate the GBE environment that GBE should work with. Such an environment is made of a bosh-environmentsubsystem and its related bosh-configs subsystems for the cloud config and runtime config.

  • source <(./bin/gbe env) to get the gbe CLI added to your shell $PATH. (this syntax requires Bash version 4+)

  • gbe up to converge the infrastructure.

  • source <(./bin/gbe env) to load the new environment variables, now that the BOSH environment is created.

  • gbe converge all: to converge all bosh-deployment subsystems. You will need 30+ GB RAM for the complete Easy Foundry environment. If you want to deploy only a subset of Easy Foundry, thes list the subsystems with gbe converge list and then deploy the subsystems you need with gbe converge <subsys> -n, one by one.

Update an already existing GBE environment

  • gbe update <cloud-config|runtime-config> when changes have been made to the cloud config or the runtime config.

  • gbe converge -y <subsys> [<subsys> ...] to converge a specific subsystem that has been modified.

  • gbe up or gbe converge to converge GBE environment when its desired state has been modified. (And then environment variables should be reloaded with source <(./bin/gbe env).)

Destroy a GBE environment

  • gbe delete all to delete all infrastructure modules.

  • gbe down to delete the base GBE environment. (All infrastructure modules should be deleted prior to deleting the environment.)