1,119 reputation
510
bio website landscape.canonical.com
location Curitiba, Brazil
age
visits member for 2 years, 4 months
seen yesterday

2d
comment Cannot get juju works with OpenStack Juno
I didn't see the index file and other content from that metadata directory in that bug, but maybe I missed it. Anyway, seems like the juju team is helping you out there.
2d
answered Juju status error
Mar
26
comment Could we use Juju without MAAS?
If you want to use the Landscape Autopilot, then yes, you need MAAS. You can also just use the cloud-installer, skip the MAAS installation and select the all-in-one option (I forgot its true name) instead of Landscape (ubuntu.com/download/cloud/install-ubuntu-openstack)
Mar
26
answered Could we use Juju without MAAS?
Mar
25
comment Openstack Autopilot fails while deploying Landscape
Try grabbing the unit logs in /var/log/juju/ from the bootstrap node and the containers (I think the directory in the bootstrap node has the containers' logs too) and make them available somewhere, or inspect them. When the installation fails with a timeout at this early stage, it's usually something network related.
Mar
25
comment Openstack Autopilot fails while deploying Landscape
It gave up after reaching the timeout. Can you check if, while the deployment is happening, if the maas nodes are being powered on and if they seem to be installing things? Even better would be to try to drive MAAS directly with juju first and see that works: maas.ubuntu.com/docs1.7/juju-quick-start.html It's also much easier to debug.
Mar
25
answered Cannot get juju works with OpenStack Juno
Mar
18
answered New Openstack Autopilot stuck at: In progress - Configure availability zones - 98%
Mar
18
comment Ceilometer deployment
When using juju, you don't have to worry about nodes, just services. You need to deploy the ceilometer service, then relate it to the other services and so on.
Mar
18
answered Ceilometer deployment
Mar
17
comment Computers not reporting to landscape
If there was no mysql.passwd file, I think this deployment is really broken now. I suggest to start over, unless you really want to dig in for learning purposes.
Mar
17
comment Computers not reporting to landscape
Those config-changed errors should be fixed. You will have to login to each unit that is in this state and inspect its /var/log/juju/unit-<name>.log file to see why it failed, fix it and run "juju resolved --retry <unitname>".
Mar
16
answered Computers not reporting to landscape
Mar
16
comment Computers not reporting to landscape
Yeah, the apache2 charm, when creating self-signed certificates, was ignoring a setting and making the certificate valid for 30 days only. It was fixed on February 25th, 2015. Can you paste the output of juju status of the MAAS environment, the one where Landscape is deployed? That's where the Apache2 service is, and it will tell us what it's charm store revision is and where it came from exactly. Then we can give you instructions on how to upgrade it and get the fixed version. Run, as ubuntu user, "JUJU_HOME=~/.cloud-install/juju juju status" and paste that output for us.
Mar
16
comment Computers not reporting to landscape
The certificate expired on Feb 11 19:42:34 2015 GMT. Let me think of a juju/charm way to fix it.
Mar
16
comment Computers not reporting to landscape
Hm, I don't a second certificate generation. Could you paste a copy of the apache2 certificate somewhere? Not the private key, just the public cert. You can obtain it with the command "openssl s_client -connect apache2-ip:443" and extract the BEGIN/END bits what will show up. Then go to a client and get the file pointed at by the ssl_public_key configuration in /etc/landscape/client.conf, it should be the same certificate (paste that one too).
Mar
16
answered Landscape Based Management of Public Cloud
Mar
15
comment JUJU Error “ERROR failed to bootstrap environment: waited for 10m0s without being able to connect: ”
If you can login on the node being bootstrapped while juju is still waiting, you can inspect logs there. Look into /var/log/juju and /var/log/cloud-init* (there should be two cloud-init logs). Also inspect a process listing. Something might be stuck, like an apt-get trying to reach the network and getting tarpitted by a firewall/proxy.
Mar
15
comment Computers not reporting to landscape
Looks like your server certificate changed. There used to be a bug in the Apache charm where it would regenerate the certificate, if SELFSIGNED was in use, on every reboot (bugs.launchpad.net/charms/+source/apache2/+bug/1322759). It's marked "fix released", though. To validate this theory, can you get us the /var/log/juju/unit-apache2-*.log file from the apache2 unit(s) and the approximate reboot time? Then we can correlate that with the certificate regeneration, if this is indeed what happened.
Mar
13
comment Computers not reporting to landscape
Please inspect and/or attach a /var/log/landscape/broker.log file from one of the computers that have this alert enabled. It's the log that contains information about the exchanges and will most likely have the reason why they are failing.