Um pouco de contexto.
Estou executando o Openstack, implantado por meio do MAAS em execução no VMWare 5.1u1.
Eu usei este guia para o MAAS: link
E este para o Openstack: link (a seção para MAAS e juju)
Depois de algumas dores de cabeça iniciais, MAAS e Openstack parecem felizes (ish).
Eu agora configurei o environments.yaml para anexar a configuração do openstack, que também parece funcionar. desde que juju bootstrap foi concluído com sucesso e vejo a instância aumentar em openstack.
juju status também parece bom:
$ juju status
2013-06-22 18:11:35,330 WARNING OpenStack identity service not using secure transport
2013-06-22 18:11:35,331 WARNING S3 API calls not using secure transport
2013-06-22 18:11:35,331 INFO Connecting to environment...
2013-06-22 18:11:35,401 WARNING OpenStack compute service not using secure transport
2013-06-22 18:11:36,041 INFO Connected to environment.
machines:
0:
agent-state: running
dns-name: 192.168.1.2
instance-id: 460b0613-92a0-4dfd-8ad8-1b187d77a9fa
instance-state: running
services: {}
2013-06-22 18:11:36,115 INFO 'status' command finished successfully
Se eu tentar implantar qualquer serviço, por exemplo, juju deploy juju-gui
$ juju deploy juju-gui
2013-06-22 18:15:32,060 INFO Searching for charm cs:precise/juju-gui in charm store
2013-06-22 18:15:33,320 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:33,320 WARNING S3 API calls not using secure transport
2013-06-22 18:15:33,402 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:33,428 INFO Connecting to environment...
2013-06-22 18:15:34,063 INFO Connected to environment.
2013-06-22 18:15:34,064 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,064 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,071 INFO Using cached charm version of juju-gui
2013-06-22 18:15:34,094 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,094 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,160 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,183 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,184 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,249 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,284 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,285 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,349 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,373 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,373 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,437 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,467 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,467 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,530 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,553 WARNING OpenStack identity service not using secure transport
2013-06-22 18:15:34,554 WARNING S3 API calls not using secure transport
2013-06-22 18:15:34,620 WARNING OpenStack compute service not using secure transport
2013-06-22 18:15:34,645 INFO Charm deployed as service: 'juju-gui'
2013-06-22 18:15:34,646 INFO 'deploy' command finished successfully
O comando foi concluído com sucesso, mas nada funciona em openstack.
Eu recebo alguns avisos sobre conexões seguras, sim, mas eu gostaria de pensar que inst causando meus problemas
$ juju status
2013-06-22 18:20:35,763 WARNING OpenStack identity service not using secure transport
2013-06-22 18:20:35,763 WARNING S3 API calls not using secure transport
2013-06-22 18:20:35,764 INFO Connecting to environment...
2013-06-22 18:20:35,833 WARNING OpenStack compute service not using secure transport
2013-06-22 18:20:36,464 INFO Connected to environment.
machines:
0:
agent-state: running
dns-name: 192.168.1.2
instance-id: 460b0613-92a0-4dfd-8ad8-1b187d77a9fa
instance-state: running
3:
instance-id: pending
services:
juju-gui:
charm: cs:precise/juju-gui-61
relations: {}
units:
juju-gui/1:
agent-state: pending
machine: 3
public-address: null
2013-06-22 18:20:36,553 INFO 'status' command finished successfully
Eu só tenho experimentado o juju por uma semana agora, então estou certo de como começar a solucionar isso. Tenho certeza de que é algo simples, há apenas mil coisas simples para verificar. Qualquer ajuda seria apreciada.
environments.yaml
default: openstack_s3
environments:
maas:
type: maas
maas-server: 'http://192.168.1.100:80/MAAS'
maas-oauth: 'wXcWaJZWF3JUBk8m9d:PYD5g4uT5ve2QmDHn9:pv2fnEpUUPpU96TStYb59jqjeGqmrUdm'
admin-secret: '|omitted|'
default-series: precise
openstack_s3:
type: openstack_s3
control-bucket: juju-openstack-admin-a1dd-ddf7023d869c
admin-secret: bec797e973914c05b954db4ef0074235
default-series: precise
default-image-id: 25eaf6ca-8568-403f-b395-29b64dcf8566
auth-url: http://192.168.1.112:5000/v2.0/
username: admin
password: openstack
project-name: admin
secret-key: 033f36a1e2524afea1142e6b2055c76b
ec2-uri: http://192.168.1.108:8773/services/Cloud
s3-uri: http://192.168.1.108:3333
$ juju --version
juju 0.7
Além disso, por MAAS e Juju Post-Bootstrap Connection Error Eu mudei os nomes de host em meus ambientes.YAML para IPs. Nenhuma mudança.