Merge lp:~caio1982/capomastro/kthxbye-deploy into lp:~ubuntuone-hackers/capomastro/deploy

[Caio Begotti]

The old deploy branch of Capomastro is no longer useful but people might still refer to it (either because it was a known URL or because they would expect deployment instructions to be under the project tree) so this change keeps a brief note pointing people to the right place.

[Daniel Manrique (roadmr)]

+1, less confusion.

review: Approve

=== added file 'README'
--- README	1970-01-01 00:00:00 +0000
+++ README	2015-02-06 00:43:30 +0000
@@ -0,0 +1,1 @@
+This branch has been abandoned, please see lp:canonical-mojo-specs instead. Or possibly lp:~canonical-is/canonical-mojo-specs/mojo-pes-capomastro for non-merged spec changes.

=== removed file 'README.md'
--- README.md	2015-01-12 11:34:00 +0000
+++ README.md	1970-01-01 00:00:00 +0000
@@ -1,108 +0,0 @@
-Deploying Capomastro
-====================
-
-Requirements
-------------
-
- * Launchpad:
-   * Access to the spec code at lp:~canonical-is/canonical-mojo-specs/mojo-pes-capomastro/
-   * Access to Jenkins bot keys at lp:~ce-infrastructure/bygmester/ce-jenkins-bot
-   * Access to the PPA at lp:~ce-infrastructure/+archive/ubuntu/capomastro
- * OS:
-   * Trusty (14.04)
-
-Setup
------
-
-Install the Mojo package from its PPA (and juju-local if doing local test):
-
-  sudo apt-add-repository --yes ppa:mojo-maintainers/ppa && sudo apt-get update
-  sudo apt-get --yes install mojo juju-local
-
-Initialize the local environment for Juju so you can deploy Capomastro:
-
-  juju init
-  juju switch local
-  juju bootstrap
-
-It is also highly recommended to use the company VPN to run any deployment, see
-https://wiki.canonical.com/InformationInfrastructure/IS/HowTo/CompanyOpenVPN
-for instructions on how to set it up. You may have problems accessing IS-owned
-resources if you do not use the VPN when running the Mojo script.
-
-
-Mojo configuration
-------------------
-
-There are two important vars in the deployment script: MOJO_REPO and MOJO_STAGE.
-
-MOJO_REPO should have the Launchpad address of the repository containing the spec
-of Capomastro. It can be a local repository, i.e. a local directory in the file
-system, as long as all changes have been committed (not necessarily pushed though).
-
-MOJO_STAGE point to the working spec directory inside the Mojo repository. You
-may need to tweak that if you are working on a new spec which does not follow the
-IS organization, but most likely that never needs to be changed.
-
-Also, before running the deployment script, you must have both the secret of Capomastro's
-PPA and the SSH key pair used by the Jenkins bot to fetch and build images.
-
-The script expects the Capomastro PPA to be configured through a charm option
-and it is copied over the rest of the Mojo files automatically. Just put the
-option formatted as YAML in /tmp/secrets, like this:
-
-capomastro:
-    services:
-        capomastro:
-            options:
-                repository: "<private PPA credentials here>"
-
-As for the Jenkins bot configuration, simply create a directory /tmp/keys
-and add both SSH key and its .pub inside it. The script will use them for some
-post desployment steps, otherwise Jenkins won't be able to fetch and build
-images correctly right after the setup of the service.
-
-All this ensures no secrets or credentials are stored anywhere in the spec.
-
-Deploying
----------
-
-You may need to provide a password for sudo at the start of it:
-
-  ./mojo.sh
-
-Considerations
---------------
-
-1. you should avoid using this script for any serious production deployment. This
-was meant for testing and development only, though it could be used just fine
-on staging servers if needed. Local deployments with Juju and Mojo are supported
-but you may encounter unknown problems, so beware. Ideally you should always
-deploy to Canonistack, but that is quite slow, that's why this script exists.
-
-2. if using a non-local provider you will need to associate a floating IP with
-the "apache2/0" service unit for web access. Optionally associate a floating
-IP with the "jenkins/0" service unit if you require web access to it as well,
-but keep in mind that would be insecure as all artifacts by default are visible
-in Jenkins.
-
-3. when using this locally, you won't be able to actually build images with
-Capomastro right away as the default policy for LXC units is not to allow
-nesting. You'll need to stop the Jenkins unit, update its policy to allow that,
-restart the unit and then try again. These are the config options you'll need:
-
-  lxc.aa_profile = lxc-container-default-with-nesting
-  lxc.mount.auto = cgroup:mixed
-
-Old references
--------------
-
-Previously, in the shellscripts used to deploy the Capomastro charm manually, 
-these were the equivalent to the new Mojo spec commands we are using:
-
-  init.sh -> collect script
-  deploy.sh -> the manifest file at the root of the spec
-  bootstrap.sh -> manually done only when needed now
-  post-deploy-config.sh -> also part of the manifest file
-  upgrade-charm.sh -> collect-upgrade script
-  config/ directory -> services file

=== removed file 'mojo.sh'
--- mojo.sh	2015-01-12 13:28:50 +0000
+++ mojo.sh	1970-01-01 00:00:00 +0000
@@ -1,54 +0,0 @@
-#!/bin/bash
-#
-# [e-mail]
-# Mon 2015-01-05 15:32:20 -0200
-
-echo "
-WARNING: this script is meant for testing mojo specs only,
-         please do not use this for real production work
-         as the script creates temporary unique LXC environments
-         and it never cleans them up... you've been warned!
-
-         [press any key to continue]
-     "
-read
-
-# env vars are used for practical reasons only
-# as mojo still have problems parsing them so
-# you should stick with command line parameters
-
-export MOJO_TIMESTAMP=$(date +%s)
-export MOJO_PROJECT=capomastro-${MOJO_TIMESTAMP}
-export MOJO_WORKSPACE=capomastro-${MOJO_TIMESTAMP}
-export MOJO_SERIES=trusty
-export MOJO_STAGE=pes/mojo-pes-capomastro/devel
-
-# this can be a local directory in the filesystem,
-# as long it is a working bzr repository and that you
-# have committed any changes (no need to push them though)
-export MOJO_REPO=lp:~canonical-is/canonical-mojo-specs/mojo-pes-capomastro/
-
-set -xev
-
-# not sure why it can't call sudo itself
-sudo --preserve-env mojo project-new --series ${MOJO_SERIES} ${MOJO_PROJECT}
-
-# known bug with mojo
-sudo chmod 755 /var/lib/lxc/${MOJO_PROJECT}.${MOJO_SERIES}
-
-# creates a temporary workspace for the repo
-mojo workspace-new --series ${MOJO_SERIES} --project ${MOJO_PROJECT} --stage ${MOJO_STAGE} ${MOJO_REPO} ${MOJO_WORKSPACE}
-
-# prepare the secrets for local deployment
-sudo mkdir -p /srv/mojo/LOCAL/${MOJO_PROJECT}/pes/mojo-pes-capomastro/devel
-
-# private ppa option for the capomastro charm
-sudo cp -a /tmp/secrets /srv/mojo/LOCAL/${MOJO_PROJECT}/pes/mojo-pes-capomastro/devel/
-
-# directory with key pair for ce-jenkins-bot
-sudo cp -a /tmp/keys /srv/mojo/LOCAL/${MOJO_PROJECT}/pes/mojo-pes-capomastro/devel/
-
-# will execute all phases listed inside the manifest file
-mojo run --series ${MOJO_SERIES} --project ${MOJO_PROJECT} --stage ${MOJO_STAGE} ${MOJO_REPO} ${MOJO_WORKSPACE}
-
-exit 0