Juju deployment of LDS

With Juju you can deploy Landscape in a scalable way, and still have all services on a single machine if you want to.

Let's get ready to use Juju:

    sudo add-apt-repository ppa:juju/stable
    sudo apt-get update
    sudo apt-get install juju-core juju-deployer juju-quickstart

To learn more about Juju and to configure a Juju environment, check out their getting started page.

Using a bundle

A bundle is a file that contains a description of all the services that make up a deployment and their relation with each other. If you already have a suitable Juju environment configured, you can run this command to deploy Landscape:

    juju-quickstart bundle:~landscape/landscape-scalable/landscape-scalable

Landscape will be deployed on 6 machines.

If you have a MAAS environment, you can take advantage of containers and use the landscape-dense-maas bundle:

    juju-quikcstart bundle:~landscape/landscape-dense-maas/landscape-dense-maas

This will deploy Landscape on the bootstrap node using containers, so total machine count is just one.

Using a deployer file

A deployer file is a configuration file in YAML that allows for very rich deployment layouts. It is very similar to a bundle, but supports inheritance among deployment targets and has other nice features. Checkout its home page to learn more.

The Landscape deployer file is inside the server charm:

    sudo apt-get update
    sudo apt-get install bzr
    bzr branch lp:~landscape-charmers/charms/trusty/landscape-server/trunk landscape-server
    cd landscape-server

To list the available deployments, run this command:

    juju-deployer -c config/landscape-deployments.yaml -l

The README.md file explains the different deployment layouts.

To deploy LDS 14.10, create a file called repo-file with the PPA URL:

    echo http://ppa.launchpad.net/landscape/14.10/ubuntu > config/repo-file

If you have an LDS license, put it in there too:

    cp license.txt config/license-file

If you don't have a license, just create an empty file so that the demo license will be used automatically:

    touch config/license-file

Now you are ready to deploy. For example, let's say you want to deploy using the landscape-dense target, which installs everything on the bootstrap node so you only use one machine:

    cd config
    juju-deployer -Wdv -c landscape-deployments.yaml landscape-dense

` After that is finished, follow the output of juju debug-log until it "quiets down". That means the service has been deployed and you can access it through the frontend hostname, which is the apache2/0 unit. Find out its address:

    juju status apache2/0

And connect to it with your browser.

LDS/JujuDeployment14.10 (last edited 2014-12-09 17:55:57 by ahasenack)