Migrating juju to HP Cloud’s Horizon
Canonical
on 12 June 2014
HP Cloud retired its old regions this month. If you use juju on HP Cloud and your account was created before this year, you may need to update your juju config and possibly complete your project setup in Horizon.
There are two changes you must make to each HP Cloud environment listed in environments.yaml. Set the region option to “region-a.geo-1″ or “region-b.geo-1″, which are US West and US East respectively. The new regions do not automatically assign public IPs. The use-floating-ip option must be set to “true” to tell juju to request a public address.
use-floating-ip: true region: region-a.geo-1
Note that juju does not yet release the public address when you destroy the machine, You need to use the nova command line tools or the Horizon console > Project > Compute > Access & Security > Floating IPs to release them. We will release a fix for “Floating IPs are not recycled in OpenStack Havana” soon.
If you haven’t used these regions before, you needs to register your public SSH keys and create a default network for each one you use. Visit Horizon console > Project > Compute > Access & Security > Key Pairs. Most people migrating just copied their public keys to the new region. Visit Horizon console > Project > Networks > Network and verify or create a default network, something like 10.0.0.0/24.
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
A decade of Ubuntu on IBM Z and IBM LinuxONE
This year we celebrate a decade of Ubuntu Server support on the s390x architecture: marking a long-standing collaboration between Canonical and IBM that began...
AI at the edge: simplifying infrastructure with Cisco and Canonical
Legacy infrastructure was not designed for the requirements of the AI era. While large-scale model training remains centralized in data centers, test-time...
The next era of telco clouds: get open infrastructure choice with Sylva and Canonical Kubernetes
Achieving vendor neutrality in telco clouds requires an infrastructure layer that respects open standards, without wrapping them in rigid platform layers. By...