Merge lp:~ev/ubuntu-ci-services-itself/public-address-howto into lp:ubuntu-ci-services-itself

[Evan]

Short howto on exposing a service to the wider web.

Short howto on exposing a service to the wider web.

[lp:~ev/ubuntu-ci-services-itself/public-address-howto]

259. By Evan on 2014-02-21

Typo.

[PS Jenkins bot (ps-jenkins)]

PASSED: Continuous integration, rev:259
http://s-jenkins.ubuntu-ci:8080/job/uci-engine-ci/204/
Executed test runs:

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/uci-engine-ci/204/rebuild

review: Approve (continuous-integration)

[Andy Doan (doanac)]

review: Approve

[Chris Johnston (cjohnston)]

 merge approved

review: Approve

=== modified file 'TRICKS'
--- TRICKS	2014-02-20 16:50:09 +0000
+++ TRICKS	2014-02-21 12:03:05 +0000
@@ -107,3 +107,16 @@
 
 Enter your ~/.juju/environments.yaml admin-secret as the password.
 
+Accessing services from public addresses
+========================================
+
+Sometimes you want to share access to a component with another engineer for
+debugging. The following steps will give that component a public IP address and
+expose it to the wider Internet. Please be careful to clean up unused public
+IPs. They are a scarce resource.
+
+$ IP=$(euca-allocate-address)
+$ juju status # note the IP of the service you're after, save it to SERVICE_IP.
+$ euca-describe-instances | grep $SERVICE_IP # note the instance ID (i-xxxxxx).
+$ euca-associate-address -i $INSTANCE_ID $IP
+$ juju expose $SERVICE_NAME # Tell juju to allow access.