Skip to content

forj-oss/maestro

Repository files navigation

Directories structure:

  • bootstrap : Contains Box init code after server bootstraped.
  • build/bin : Contains scripts to build Maestro or node images or any distribution packages.
  • build/maestro : Contains bootstrap to build a basic maestro image
  • build/node : Contains bootstrap to build a basic node image.
  • puppet : Contains puppet modules to build maestro or node images.
  • api/bp-api : Blueprint api to expose blueprint toolset
  • ui : Maestro ui

How Maestro is created:

If you are building a Maestro image for your cloud, do the following:

This tool is based on hpcloud cli. You have to install it before. See http://docs.hpcloud.com/cli/unix

  • Configuring cloud credential

See hpcloud cli documentation for complete instructions.

$ gem install hpcloud
$ hpcloud account:setup

Make sure the network name used in the box configuration files used below is defined in your tenant. Default configuration uses the "private" network name, so either define such a network or tune the configuration file.

  • Build your box

To build a box named maestro, use the following:

$ cd build
$ vi conf/maestro.box.master.env
$ bin/build.sh --box-name maestro --build-conf-dir conf --build-config box

it will create a Maestro box image, by building a server and snapshooting it.

maestro requires a proto2b image to be built before.

To build proto2b image, use the following:

$ vi conf/proto2b.bld.master.env
$ bin/build.sh --box-name proto2b

For more details, read build/README.md

FORJ Team

Contributing to Forj

We welcome all types of contributions. Checkout our website (http://docs.forj.io/en/latest/dev/contribute.html) to start hacking on Forj. Also join us in our community (https://www.forj.io/community/) to help grow and foster Forj for your development today!

License

Maestro is licensed under the Apache License, Version 2.0. See LICENSE for full license text.