New answers tagged

0

There is a single document which describes all this, it is here: https://help.ubuntu.com/lts/clouddocs/en/Intro.html Beware that it is a bit outdated with respect to some topics as it was written two years ago. Similar documentation exists for the autopilot installer: https://help.ubuntu.com/lts/clouddocs/installer/


0

The logs show that the MAAS machine that Autopilot picked to bootstrap on doesn't have access to streams.canonical.com, can you confirm if you have a firewall in place?


0

We don't enable the console because the security implications of doing so are horrendous. The OpenStack Autopilot will deploy OpenStack in the best, safest way we know how and unfortunately that means no console access.


0

Well it seemed to be a problem with the default mirror "http://archive.ubuntu.com/ubuntu" that is set in setting tab of maas gui (As was pointed out in here). When I changed it to a different mirror address it got to internet but it was too slow that maas gui displayed "failed commissioning" under node's status. Selecting other mirrors was of no use. So I ...


0

Found my own answer - Looks like for some reason the auto-pilot build script is not setup to enable and configure the console component via "VNC" so instead the end user has to connect to juju and push config to the cloud controllers and all nova endpoints. Not sure if it should be logged as a bug or not but it will defiantly be putting people off taking up ...


0

I have found the best way to figure out what is failing is to SSH to a node while it being commissioned and to check /var/log directory. There is a log for a cloud-init script. If that part did complete correctly then look for /var/log/juju and the logs inside it will give a you a clue on what might be failing.


0

In the web UI click on settings, if you scroll down you can specify apt proxy for http/https to pull packages down. I am using 1.9.3 MAAS version.


0

I am stuck at the same pointscreenshot Openstack autopilot 16_03 one VMware 5.5 host I entered the host IP, root user, password MaaS discovered the 6 VMs I selected one VM to poweron. in MaaS settings default Ubuntu release for commissioning is 16.04 and for deployment is 14.04


0

I'm assuming you are using the USE team's MAAS client, from https://github.com/Ubuntu-Solutions-Engineering/maasclient. That client returns data from queries in BSON format. To parse BSON output, use the Python BSON package: https://github.com/py-bson/bson Here's how you'd read the data in your case: import bson resp = self.client.get(u"nodes/%s/" % ...


4

Well, this is an interesting set of questions :) First, there is no way to take a standard app and spread it across many machines to make it faster. You do have some apps which are designed to be spread across several machines, and those can be used very easily with MAAS and Juju to coordinate the deployment and operations of the distributed system. But you ...


0

I don't think MAAS has the ability to push a new key to an already-deployed node. Are you sure there was not a single key imported to your account when you deployed the node?


2

I was able to complete my installation successfully by re-running the hook in a second terminal. juju resolved --retry keystone/0



Top 50 recent answers are included