with the following bundle:
# vim: set ts=2 et:
series: bionic
machines:
0:
constraints: tags=^nuc spaces=oam-space,ceph-replica-space
applications:
ubuntu:
charm: ubuntu
num_units: 1
bindings:
"": oam-space
to:
- 0
nova-compute:
charm: cs:~chris.macnaughton/nova-compute-profile-0
num_units: 1
bindings:
"": oam-space
to:
- lxd:0
neutron-openvswitch:
charm: cs:~openstack-charmers-next/neutron-openvswitch
relations:
- [ neutron-openvswitch, nova-compute ]
I reliably get:
Model Controller Cloud/Region Version SLA Timestamp
olympus-default olympus olympus 2.5-rc1 unsupported 15:50:07+01:00
App Version Status Scale Charm Store Rev OS Notes
neutron-openvswitch waiting 0 neutron-openvswitch jujucharms 329 ubuntu
nova-compute waiting 0/1 nova-compute local 133 ubuntu
ubuntu 18.04 active 1 ubuntu jujucharms 12 ubuntu
Unit Workload Agent Machine Public address Ports Message
nova-compute/0 waiting allocating 0/lxd/0 waiting for machine
ubuntu/0* active idle 0 10.0.4.60 ready
Machine State DNS Inst id Series AZ Message
0 started 10.0.4.60 w66q8g bionic default Deployed
0/lxd/0 down pending bionic cannot upgrade machine's lxd profile: machine 0/lxd/0 not provisioned
$ juju version
2.5-rc1-
$ snap info juju
name: juju
summary: juju client
publisher: Canonical✓
contact: http://
license: unset
description: |
Juju is an open source modelling tool for operating software in the cloud. Juju allows you to
deploy, configure, manage, maintain, and scale cloud applications quickly and efficiently on
public clouds, as well as on physical servers, OpenStack, and in containers. You can use Juju from
the command line or through its GUI.
In modern environments, applications are rarely deployed in isolation. Even simple applications
may require several other applications in order to function - like a database and a web server,
for example. For modeling a more complex system, e.g. OpenStack, many more applications need to be
installed, configured and connected to each other. Juju's application modelling provides tools to
express the intent of how to deploy such applications and to subsequently scale and manage them.
At the lowest level, traditional configuration management tools like Chef and Puppet, or even
general scripting languages such as Python or bash, automate the configuration of machines to a
particular specification. With Juju, you create a model of the relationships between applications
that make up your solution and you have a mapping of the parts of that model to machines. Juju
then applies the necessary configuration management scripts to each machine in the model.
Application-
backups and updates, and integration options with other pieces of software are encapsulated in
Juju's 'charms'. This knowledge can then be shared between team members, reused everywhere from
laptops to virtual machines and cloud, and shared with other organizations.
The charm defines everything you all collaboratively know about deploying that particular
application brilliantly. All you have to do is use any available charm (or write your own), and
the corresponding application will be deployed in seconds, on any cloud or server or virtual
machine.
https:/
https:/
https:/
commands:
- juju
snap-id: e2CPHpB1fUxcKtC
tracking: edge
refresh-date: today at 12:24 CET
channels:
stable: 2.4.7 (6012) 58MB classic
candidate: ↑
beta: 2.5-beta3 (6050) 64MB classic
edge: 2.5-rc1+
2.5/stable: –
2.5/candidate: –
2.5/beta: 2.5-beta3 (6050) 64MB classic
2.5/edge: ↑
2.4/stable: 2.4.7 (6012) 58MB classic
2.4/candidate: ↑
2.4/beta: ↑
2.4/edge: 2.4.8+2.4-d4ca58d (6066) 66MB classic...