User Tools
juju
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
juju [2014/07/02 15:32] gsamfira |
juju [2015/08/17 11:37] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======= Working with Juju and MaaS ======= | ======= Working with Juju and MaaS ======= | ||
| - | :!: WARNING: | + | :!: WARNING: |
| :!: For the sake of this example, we will assume that your MaaS IP is **192.168.200.1** :!: | :!: For the sake of this example, we will assume that your MaaS IP is **192.168.200.1** :!: | ||
| Line 7: | Line 7: | ||
| * Install Go | * Install Go | ||
| - | sudo apt-get -y install golang-go git mercurial bzr | + | sudo apt-get -y install golang-go git mercurial bzr mongodb |
| * Set up your Go environment | * Set up your Go environment | ||
| Line 20: | Line 20: | ||
| * Get a copy of juju-core from launchpad. This will pull in all other dependencies: | * Get a copy of juju-core from launchpad. This will pull in all other dependencies: | ||
| - | go get launchpad.net/juju-core/... | + | go get -v github.com/juju/juju/... |
| - | * Get our patched version from git. This contains the windows support: | + | * Get correct dependencies |
| - | | + | |
| - | | + | |
| - | | + | |
| - | * Because of the way Go works, you will always get the latest revisions of dependencies. This might sometimes break the build of juju. The checkout from 19 April needs the following hack: | + | * build juju |
| - | | + | go install -v github.com/juju/juju/... |
| - | + | ||
| - | * Build juju-core on Linux | + | |
| - | + | ||
| - | | + | |
| Binaries will be in $GOPATH/bin | Binaries will be in $GOPATH/bin | ||
| Line 59: | Line 55: | ||
| mkdir -p ~/ | mkdir -p ~/ | ||
| cd ~/ | cd ~/ | ||
| - | cp ~/ | + | cp ~/ |
| - | tar -czf juju-1.19.1-trusty-amd64.tgz jujud | + | tar -czf juju-1.21.1-trusty-amd64.tgz jujud |
| rm jujud | rm jujud | ||
| | | ||
| - | Do this for every version of ubuntu that you want to have tools for. Precise and Trusty should be enough for development. While its good practice to build the binary on each platform to make sure no breakage will happen, I have found that the same binary works great on all versions. | + | Do this for every version of ubuntu that you want to have tools for. Trusty should be enough for development. |
| - | For windows machines | + | For windows machines: |
| cd ~/ | cd ~/ | ||
| - | | + | cp / |
| - | tar -xzf juju-service.tar.gz | + | tar -czf juju-1.21.1-win2012hvr2-amd64.tgz |
| - | | + | |
| - | tar -czf juju-1.19.1-win2012r2-amd64.tgz | + | |
| rm *.exe | rm *.exe | ||
| | | ||
| Line 81: | Line 75: | ||
| | | ||
| This will generate all metadata from the tools found in ~/ | This will generate all metadata from the tools found in ~/ | ||
| - | |||
| ls -l / | ls -l / | ||
| Line 90: | Line 83: | ||
| Go to your MaaS web interface under: | Go to your MaaS web interface under: | ||
| - | http:// | + | http:// |
| | | ||
| Where you will find: | Where you will find: | ||
juju.1404304340.txt.gz · Last modified: 2014/07/02 15:32 by gsamfira
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
