Skip to main content
  1. Blog
  2. Article

Canonical
on 12 June 2014

Migrating juju to HP Cloud’s Horizon


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.

Related posts


Philip Williams
18 February 2026

Predict, compare, and reduce costs with our S3 cost calculator

Ceph Article

Previously I have written about how useful public cloud storage can be when starting a new project without knowing how much data you will need to store.  However, as datasets grow  over time, the costs of public cloud storage can become overwhelming.  This is where an on premise, or co-located, self-hosted storage system becomes advantage ...


Yanisa Haley Scherber
17 February 2026

A year of documentation-driven development

Ubuntu Article

For many software teams, documentation is written after features are built and design decisions have already been made. When that happens, questions about how a feature is understood or used often don’t surface until much later.  A little over one year ago, our team began to recognize this pattern in our own work. Features generally ...


Henry Coggill
17 February 2026

Announcing FIPS 140-3 for Ubuntu Core22

Hardening Article

FIPS compliance for IoT use cases in Federal space. In this article, we’ll explore what Ubuntu Core is, and how to use it with FIPS. ...