This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
juju-centos [2015/05/12 19:53] bteleaga [Generating MaaS images for CentOS 7] |
juju-centos [2015/05/13 15:34] anashwan |
||
---|---|---|---|
Line 1: | Line 1: | ||
======= Using Juju and MaaS with CentOS ======= | ======= Using Juju and MaaS with CentOS ======= | ||
- | Initial support has landed in master branch for CentOS 7 and is planned to be released with version 1.24 of juju. Keep in mind that this is an initial release | + | Initial support has landed in Juju' |
- | First off, to get started | + | To start off, you should follow our previous |
- | http:// | + | [[http:// |
- | http:// | + | [[http:// |
This will give you a ready to go MaaS and Juju environment. Make sure you can bootstrap a trusty state machine before following the next steps to make debugging easier. | This will give you a ready to go MaaS and Juju environment. Make sure you can bootstrap a trusty state machine before following the next steps to make debugging easier. | ||
Line 13: | Line 13: | ||
===== Generating MaaS images for CentOS 7 ===== | ===== Generating MaaS images for CentOS 7 ===== | ||
- | There is a nice project made available by Canonical that will facilitate the creation of a new CentOS image compatible with MaaS. We are using MaaS to test this, because | + | There is a nice project made available by Canonical that will facilitate the creation of a new CentOS image compatible with MaaS. We are using MaaS to test this, because |
Lets get a local copy of maas-iumagebuilder: | Lets get a local copy of maas-iumagebuilder: | ||
Line 21: | Line 21: | ||
python setup.py install | python setup.py install | ||
- | You may need to change the python-stevedore dependency to stevedore in setup.py for the installation to work. Once the image builder is installed, you need to make sure kvm works on the ubuntu | + | You may need to change the python-stevedore dependency to stevedore in setup.py for the installation to work. Once the image builder is installed, you need to make sure KVM works on the Ubuntu |
- | * Run the command for creating the image | + | * Run the command for creating the image: |
- | + | ||
- | :!: This will probably take a very long time. You can do the rest of the juju configuration in the meantime. However, before bootstrapping a node with CentOS, the image should be uploaded to MaaS. | + | |
maas-image-builder -o centos7-amd64-root-tgz centos --edition 7 | maas-image-builder -o centos7-amd64-root-tgz centos --edition 7 | ||
- | | + | :!: This will probably take a very long time. You can pass on to configuring Juju, but make sure you **stop before** issuing the `juju boostrap` command and come back here to upload the image to MaaS. |
+ | |||
+ | | ||
maas < | maas < | ||
Line 35: | Line 35: | ||
===== Create jujud agent tools ===== | ===== Create jujud agent tools ===== | ||
- | * While the image is uploading, you can create the tools and make them available to the MaaS machines. You do not need to create the trusty ones if they' | + | * While the image is uploading, you can create the tools and make them available to the MaaS machines. You don' |
mkdir -p ~/ | mkdir -p ~/ | ||
Line 44: | Line 44: | ||
rm jujud | rm jujud | ||
- | * If you followed | + | * If you' |
rm -rf ~/ | rm -rf ~/ | ||
Line 80: | Line 80: | ||
While these issues are present in this initial release, we are working on remedying them as soon as possible. Some may take longer then others, but we do want to have 1:1 feature set on all supported platforms. | While these issues are present in this initial release, we are working on remedying them as soon as possible. Some may take longer then others, but we do want to have 1:1 feature set on all supported platforms. | ||
- | * no support for yum mirrors/ | + | * no support for yum mirrors/ |
- | * no mongo tools(which implies no backups amongst other things) | + | * no mongo tools(which implies no backups, amongst other inconveniences) |