Merge lp:~ev/uci-engine/nfss-fixes into lp:~canonical-ci-engineering/uci-engine/nfss

Proposed by Evan
Status: Merged
Merge reported by: Thomi Richards
Merged at revision: not available
Proposed branch: lp:~ev/uci-engine/nfss-fixes
Merge into: lp:~canonical-ci-engineering/uci-engine/nfss
Diff against target: 26 lines (+3/-3)
1 file modified
juju-deployer/nf-data-collector.yaml.tmpl (+3/-3)
To merge this branch: bzr merge lp:~ev/uci-engine/nfss-fixes
Reviewer Review Type Date Requested Status
Thomi Richards Pending
Canonical CI Engineering Pending
Review via email: mp+224522@code.launchpad.net

Description of the change

We pin dependencies and charms in lp:uci-engine so two deployments that only differ in time produce the same results. The motivation being that if the deployment breaks, you know it's because of code you changed. Adding the python3 version of the gunicorn charm broke this:

➜ nfss-fixes ./juju-deployer/update.py --assert-pinned; echo $?
cannot import name compare_trees
lp:~canonical-ci-engineering/charms/trusty/gunicorn/gunicorn-py3-support is not pinned to a revno.
1

I also took the opportunity to install the python 2 version of pyramid again. It is co-installable with the python3 version. Supporting both means we don't have to keep a separate copy of the charm for services that haven't been transitioned to python3.

There's no need to install test dependencies with the production service, so I removed mock and webtest from the juju-deployer configuration.

To post a comment you must log in.
Revision history for this message
Andy Doan (doanac) wrote :

why support python2 and python3 for pyramid if we are only doing python3? If/when we need python2-pyramid, i don't mind adding the logic but that just adds X more things to install now?

lp:~ev/uci-engine/nfss-fixes updated
605. By Evan

As the restish charm isn't used outside of uci-engine, we can safely leave the python2 version of pyramid out until we need it.

Revision history for this message
Evan (ev) wrote :

On 25 June 2014 23:35, Andy Doan <email address hidden> wrote:
> why support python2 and python3 for pyramid if we are only doing python3? If/when we need python2-pyramid, i don't mind adding the logic but that just adds X more things to install now?

I had mistakenly assumed that restish existed outside of our
deployment. Reverted that change as r605.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'juju-deployer/nf-data-collector.yaml.tmpl'
2--- juju-deployer/nf-data-collector.yaml.tmpl 2014-06-25 03:59:27 +0000
3+++ juju-deployer/nf-data-collector.yaml.tmpl 2014-06-25 22:49:22 +0000
4@@ -10,19 +10,19 @@
5 tarball: ${CI_PAYLOAD_URL}
6 framework: pyramid
7 db_migration_cmd: ./nf-data-collector/nfdc/db_migrate.py
8- packages: "python-webtest python-mock python-jinja2 python3-psycopg2 python3-oauthlib python3-webtest python3-mock"
9+ packages: "python-jinja2 python3-psycopg2 python3-oauthlib"
10 python_path: ./nf-data-collector:./ci-utils
11 json_status_path: api/v1/status
12 install_sources: |
13 - ${CI_PPA}
14 install_keys: |
15 - ""
16- nagios_check_http_params: -H gatekeeper -I 127.0.0.1 -e '
17+ nagios_check_http_params: -H nfdc -I 127.0.0.1 -e '
18 200 OK' --url='/api/v1/' -p 8080
19 nagios_context: ci-airline-staging
20 ci-airline-nfdc-gunicorn:
21 charm: gunicorn
22- branch: lp:~canonical-ci-engineering/charms/trusty/gunicorn/gunicorn-py3-support
23+ branch: lp:~canonical-ci-engineering/charms/trusty/gunicorn/gunicorn-py3-support@34
24 options:
25 wsgi_wsgi_file: nfdc:app
26 use_python3: true

Subscribers

People subscribed via source and target branches

to all changes: