charm has difficulties when run behind a firewall
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Fix Released
|
High
|
Francesco Banconi | ||
Bug Description
Some of these may be difficult to resolve. However, this records the challenges that can arise in these circumstances.
Let's start with a given that the machine is running Precise, and that the machine has access to standard Precise deb repos through (or within) the firewall.
Let's also assume that the user is working with the juju in the PPA. I don't think we test it any other way, do we? The charm has some code to try to make this work, but we don't have any automated guarantees. Anyway, if the user is not using the Juju from the PPA, the machine needs access to ppa:juju/pkgs on Launchpad in order to get python-charmhelpers and python-
What else does the charm need?
- It needs access to ppa:juju-gui/ppa on Launchpad in order to get the newer haproxy version we need. This also means accepting another cert.
- It needs to be able to download the release tarball from Launchpad.
Once we address bug 1117896, the following will only be needed if you are trying to run a GUI branch, rather than a release.
- It needs access to ppa:chris-
- It needs to be able to check out the desired branch over bzr+ssh (usually from Launchpad).
Minimally, we should record these requirements (and assumptions!) in the charm's README. We can close this bug then, though we may want to open a duplicate later if we come up with a better solution.
Related branches
- charmers: Pending requested
-
Diff: 1923 lines (+1275/-367)11 files modifiedconfig.yaml (+1/-1)
hooks/backend.py (+63/-44)
hooks/bootstrap_utils.py (+0/-77)
hooks/install (+17/-21)
hooks/shelltoolbox.py (+669/-0)
hooks/utils.py (+19/-8)
revision (+1/-1)
tests/20-functional.test (+5/-2)
tests/requirements.pip (+0/-2)
tests/test_backends.py (+450/-211)
tests/test_utils.py (+50/-0)
- charmers: Pending requested
-
Diff: 780 lines (+414/-66)7 files modifiedHACKING.md (+14/-0)
README.md (+36/-5)
config.yaml (+21/-13)
hooks/utils.py (+91/-22)
revision (+1/-1)
tests/20-functional.test (+22/-11)
tests/test_utils.py (+229/-14)
| Gary Poster (gary) wrote | #1 |
| Gary Poster (gary) wrote | #2 |
| Gary Poster (gary) wrote | #3 |
| tags: | added: theme-oil |
| David Britton (dpb) wrote | #4 |
| Changed in juju-gui: | |
| assignee: | nobody → Francesco Banconi (frankban) |
| Changed in juju-gui: | |
| status: | Triaged → In Progress |
| Changed in juju-gui: | |
| status: | In Progress → Fix Released |
| Gary Poster (gary) wrote | #5 |
A simple improvement might be to see if we can get our haproxy in the juju ppa, or, assuming that the certs are shared, another ppa owned by ~juju. That would mean that, once bug 1117896 was fixed, the only necessity to run the charm with a released verion of the GUI is the ability to download the release tarball.