Esta é a minha primeira vez em contêineres, por favor, tenha paciência comigo. Eu tentei implantar o openstack usando o MAAS2.0.
Eu configurei as máquinas necessárias (4 nós + Controlador Juju) e segui as instruções neste blog que foi bastante completo
Implantando o OpenStack no MAAS 1.9+ com Juju
Agora existem algumas diferenças do Juju 2.0 e do pacote Openstack atualmente disponíveis e da escrita do blog, mas geralmente tudo parece ok até a configuração nova-compute. Eu sempre fico preso aqui. Em juju gui, ele apenas pede a bridge network e os-internal-network. Eu sei que os-internal-network é a sub-rede internal-api, mas não tenho certeza do que fazer com a bridge
Machine State DNS Inst id Series AZ
0 started 10.100.0.111 t66637 xenial default
0/lxd/0 down pending xenial
0/lxd/1 down pending xenial
0/lxd/2 down pending xenial
1 started 10.100.0.114 ctf87e xenial default
1/lxd/0 down pending xenial
1/lxd/1 down pending xenial
1/lxd/2 down pending xenial
2 started 10.100.0.112 a4medb xenial default
2/lxd/0 down pending xenial
2/lxd/1 down pending xenial
2/lxd/2 down pending xenial
3 started 10.100.0.113 fa3xwa xenial default
3/lxd/0 down pending xenial
3/lxd/1 down pending xenial
3/lxd/2 down pending xenial
e aqui está a saída para juju show-machine
model: openstack-base
machines:
"0":
juju-status:
current: started
since: 14 Apr 2017 01:12:02Z
version: 2.1.2
dns-name: 10.100.0.111
ip-addresses:
- 10.100.0.111
- 10.14.0.111
- 10.150.0.111
- 10.200.0.111
- 10.250.0.111
- 10.50.0.111
instance-id: t66637
machine-status:
current: running
message: Deployed
since: 14 Apr 2017 01:11:13Z
series: xenial
containers:
0/lxd/0:
juju-status:
current: down
message: agent is not communicating with the server
since: 14 Apr 2017 01:12:49Z
instance-id: pending
machine-status:
current: provisioning error
message: 'unable to setup network: no obvious space for container "0/lxd/0",
host machine has spaces: "admin-api", "compute-data", "internal-api",
"maas-mgmt", "public-api", "storage-data"'
since: 14 Apr 2017 01:12:49Z
series: xenial
0/lxd/1:
juju-status:
current: down
message: agent is not communicating with the server
since: 14 Apr 2017 01:13:25Z
instance-id: pending
machine-status:
current: provisioning error
message: 'unable to setup network: no obvious space for container "0/lxd/1",
host machine has spaces: "admin-api", "compute-data", "internal-api",
"maas-mgmt", "public-api", "storage-data"'
since: 14 Apr 2017 01:13:25Z
series: xenial
0/lxd/2:
juju-status:
current: down
message: agent is not communicating with the server
since: 14 Apr 2017 01:14:01Z
instance-id: pending
machine-status:
current: provisioning error
message: 'unable to setup network: no obvious space for container "0/lxd/2",
host machine has spaces: "admin-api", "compute-data", "internal-api",
"maas-mgmt", "public-api", "storage-data"'
since: 14 Apr 2017 01:14:01Z
series: xenial
hardware: arch=amd64 cores=12 mem=12288M tags=virtual availability-zone=default
Mesma saída para as outras 3 máquinas físicas.
A última coisa, (que eu tenho certeza que não está relacionada, mas para completar) toda a configuração não está na máquina real, eles são 5 VMs no vSphere todos conectados usando NICs individuais para um vSwitch (4096 todos), então o encaminhamento vlans. Cada VM obteve seus ips atribuídos estaticamente no MAAS.
Muito obrigado
$juju spaces
Space Subnets
admin-api 10.150.0.0/20
compute-data 10.250.0.0/20
compute-external 10.99.0.0/20
internal-api 10.100.0.0/20
maas-mgmt 10.14.0.0/20
192.168.122.0/24
public-api 10.50.0.0/20
storage-cluster 10.30.0.0/20
storage-data 10.200.0.0/20
unused 192.168.140.0/24