Scaleway integration with juju
Juju provides for workloads management and orchestration using a collection of workloads definitions (charms) that can be assembled lego fashion at runtime into complex application topologies.
This plugin is highly inspired by @kapilt Juju plugins.
A usable version of Juju is available out of the box in Ubuntu 14.04 and later versions. For earlier versions of Ubuntu, please use the stable PPA:
$ sudo add-apt-repository ppa:juju/stable $ apt-get update && apt-get install juju
Juju is in Homebrew. To install Juju it is required to have homebrew installed. To install Juju run the following command:
$ brew install juju
Plugin installation is done via pip which is the python language package managers, its available by default on Ubuntu. Also recommended is virtualenv to sandbox this install from your system packages:
$ pip install -U juju-scaleway
Provide the credentials required by the plugin using environment variables:
$ export SCALEWAY_ACCESS_KEY=<organization_key> $ export SCALEWAY_SECRET_KEY=<secret_token>
To configure a Juju environment for Scaleway, add the following in your ~/.juju/environments.yaml:
environments: scaleway: type: manual bootstrap-host: null bootstrap-user: root
You have to tell Juju which environment to use. One way to do this is to use the following command:
$ juju switch scaleway $ export JUJU_ENV=scaleway
Now you can bootstrap your Scaleway environment:
$ juju scaleway bootstrap
All machines created by this plugin will have the Juju environment name as a prefix for their servers name.
After your environment is bootstrapped you can add additional machines to it via the the add-machine command, for instance the following will add 2 additional machines:
$ juju scaleway add-machine -n 2 $ juju status
You can now use standard Juju commands for deploying service workloads aka charms:
$ juju deploy wordpress
Without specifying the machine to place the workload on, the machine will automatically go to an unused machine within the environment.
You can use manual placement to deploy target particular machines:
$ juju deploy mysql --to=2
And of course the real magic of Juju comes in its ability to assemble these workloads together via relations like lego blocks:
$ juju add-relation wordpress mysql
You can list all machines in Scaleway that are part of the Juju environment with the list-machines command. This directly queries the Scaleway API and does not interact with Juju API.
$ juju scaleway list-machines Id Name Status Created Address 6222349 scaleway-0 active 2014-11-25 18.104.22.168 6342360 scaleway-ef19ad5cc... active 2014-11-25 22.214.171.124 2224321 scaleway-145bf7a80... active 2014-11-25 126.96.36.199
You can terminate allocated machines by their machine ID. By default with the Scaleway plugin, machines are forcibly terminated which will also terminate any service units on those machines:
$ juju scaleway terminate-machine 1 2
And you can destroy the entire environment via:
$ juju scaleway destroy-environment
destroy-environment also takes a --force option which only uses the Scaleway API. Its helpful if state server or other machines are killed independently of Juju.
All commands have builtin help facilities and accept a -v option which will print verbose output while running.
You can find out more about using from Juju docs.
This software is licensed under a BSD 2-Clause License.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|File Name & Checksum SHA256 Checksum Help||Version||File Type||Upload Date|
|juju_scaleway-1.0.3-py2.7.egg (17.2 kB) Copy SHA256 Checksum SHA256||2.7||Egg||Nov 23, 2015|
|juju_scaleway-1.0.3-py2-none-any.whl (19.0 kB) Copy SHA256 Checksum SHA256||2.7||Wheel||Nov 23, 2015|
|juju-scaleway-1.0.3.tar.gz (14.4 kB) Copy SHA256 Checksum SHA256||–||Source||Nov 23, 2015|