ERROR cannot deploy bundle: cannot deploy application "masakari": space not found

Hi.

I deploy masakari follw 《 Instance high availability》, but output is :“ERROR cannot deploy bundle: cannot deploy application “masakari”: space not found”:

The commad is :
juju deploy ./bundle.yaml --overlay masakari-overlay.yaml

masakari-overlay.yaml:
machines:
‘0’:
series: focal
‘1’:
series: focal
‘2’:
series: focal
‘3’:
series: focal
relations:
- - nova-compute:juju-info
- masakari-monitors:container
- - masakari:ha
- hacluster:ha
- - keystone:identity-credentials
- masakari-monitors:identity-credentials
- - nova-compute:juju-info
- pacemaker-remote:juju-info
- - hacluster:pacemaker-remote
- pacemaker-remote:pacemaker-remote
- - masakari:identity-service
- keystone:identity-service
- - masakari:shared-db
- masakari-mysql-router:shared-db
- - masakari:amqp
- rabbitmq-server:amqp
series: focal
applications:
masakari-monitors:
charm: /root/openstack-base-72/masakari-monitors
hacluster:
charm: cs:hacluster
options:
maas_url: http://10.0.0.3:5240/MAAS
maas_credentials: HrNTLvEaW2Z4hUaGCr:rXuELuKrB2q3wAne2r:xmTKFCDheeNXunddCdBkuHZbGVgFv9sU
pacemaker-remote:
charm: /root/openstack-base-72/pacemaker-remote
options:
enable-stonith: True
enable-resources: False
masakari-mysql-router:
charm: /root/openstack-base-72/mysql-router-6
masakari:
charm: /root/openstack-base-72/masakari
series: focal
num_units: 3
options:
openstack-origin: cloud:focal-victoria
vip: 10.0.7.72
bindings:
public: public
admin: admin
internal: internal
shared-db: internal
amqp: internal
to:
- ‘lxd:1’
- ‘lxd:2’
- ‘lxd:3’

what’s happened on it?

Thank you again!

Based on these bindings for masakari, the network spaces admin, public, and internal must exist. Do they?

The spaces documentation is here: Juju | Network spaces.

We are actively trying to improve these docs, so if you find them lacking please feel free to let us know.

1 Like

Thank you@ manadart

I has two question:

1
I deployed masakari successful by comment them:
#bindings:
#public: public
#admin: admin
#internal: internal
#shared-db: internal
#amqp: internal
But, I don’t know that masakari can work without them?

2
Do I need creat space in MAAS first before deploy openstack-base’s bundle? If I creat space first do I need deploy bundle use:

juju deploy bundle.yaml --overlay openstack-base-spaces-overlay.yaml

But, masakari also use overlay-yaml,Do I deploy bundle like:

juju deploy bundle.yaml --overlay openstack-base-spaces-overlay.yaml --overlay masakari-overlay.yaml

Can you give me the list of spaces’s ip and Network topology map.
Now maas server use 10.0.0.3/20,
public use which ip subnet?
admin use which ip subnet?
internal use which ip subnet?

Thank you again.

If you do not wish to use spaces and use only one network for your deployment, you do not need to specify bindings/spaces in your bundle, meaning, remove all of the bindings: section in the masakari application in your bundle.yaml. Masakari can work without space bindings if nothing is deployed using spaces.

If you do wish to use separate networks, then you’ll want to define the spaces in the subnet/spaces section of MAAS to define which subnet is “public”, which is “admin” and which is “internal”, and then update the spaces from MAAS into juju with juju reload-spaces and then also use the openstack-base-spaces-overlay.yaml. You can then see what spaces match with which subnets in juju using the juju spaces command.

You can use multiple overlays in the command just as you’ve noted. They will be applied, or overlaid, in the order they appear on the command line, so anything in the last overlay defined will “win” if overloading the same variable in bundle and any overlays.

-Drew

Thank you a lot.@ afreibergerDrew FreibergerCanonical Staff@ manadart

I found a helpful old document Introduction: Deploying OpenStack on MAAS 1.9+ with Juju

Thank you again.

1 Like