Tag Info

Hot answers tagged

4

The best thing todo is to wait until this Thursday (23rd October) and then upgrade to the latest release of OpenStack Charms, which support console configuration options using spice or vnc via the charm itself, rather than you having to hack stuff into you environment directly: juju set nova-cloud-controller console-access-protocol=spice should then just ...


2

This is answering the question independent of Blender 3D, assuming rendering in general. (The answer was started before an edit of the question adding the reference to Blender 3D) MAAS is a system to manage a cluster in a dynamic way. It is helpful if you often change your cluster hardware, or the services deployed on it, or the instances running on ...


2

It isn't possible just yet. I'm working on a bunch of user commands right now that I'm hoping will get into the 1.21 release. One of which will allow you to change the password.


1

You could try using juju bootstrap --upload-tools as a workaround. It should avoid the need for Juju to go out to the internet for getting the tools.


1

Before you start playing with Juju, check your MAAS correct function. Each time you add a new node in MAAS GUI and hit commision node, it should automaticaly boot the machine (node), run the commisioning scripts and then it will turn off the node with Ready state. You can do this as many times as you want and this way you can check that MAAS is able to ...


1

I think I solved it. I incorrectly understood how MAAS worked, and unfortunately the documentation is not very clear about it. "Ready" only means that the node can be used, it does NOT mean that there is already an OS on it at that point. I just went on into the documentation and bootstrapped Juju, et voila, when I started my nodes, one of them PXE-booted ...


1

In my case I had wakeonlan as power mode and had to power-up my box to pxe mode after issuing the juju bootstrap command. On bootstrap, Juju will acquire the node in Maas and deploy the OS based on the type Debian or Fast which you have configured for the node - this install time takes long and not within 10mins. So you should update your environment.yaml ...


1

It is missing the dependency - python-crochet. Had similar problem and it was solved by doing this. More on the solution can be found on https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1311765.


1

I just discovered that MAAS uses either Etherwake or Wakeonlan to boot the nodes, if using power type wake-on-lan. Those are not installed by default, and are not dependencies of MAAS. Just install Etherwake or Wakeonlan from the standard Ubuntu repo apt-get install etherwake or apt-get install wakeonlan Then, when you manually add a node using MAAS, ...


1

I don't think this kind of management is within MAAS's scope. That sounds like a job for other tools, the ones that come to mind are Landscape (https://landscape.canonical.com/), puppet and chef. That said, if all your nodes are deployed with MAAS, they will be quite homogeneous, so you can use tools like dsh to execute the same command on multiple nodes, ...


1

It's possible that it was finding the precise versions of juju-gui and puppermaster. You could try the following commands to force getting the precise charms: juju deploy cs:precise/mysql juju deploy cs:precise/rabbitmq-server


1

A MAAS cluster is for mass-deploying individual nodes that you deploy services onto, there is no compute sharing between MAAS nodes.


1

If you can access the internet from your MAAS server with the two NICs, and also enabled IP forwarding and NAT, you only need to make sure the MAAS cluster controller manages DNS and DHCP for its intranet NIC, and you set the "Router IP" to the same value as the NIC's IP. This will set all nodes' default gateway to that IP in they should be able to access ...


1

If you've deleted your $HOME/.juju/ directory, which contains all the SSH keys and certificates juju has generated, without also destroying your juju environment, you won't be able to access the environment from juju anymore, as the credentials and keys are lost. What I'd recommend is to bootstrap a new environment on your MAAS, using correctly commissioned ...


1

According to this related question and answer - http://askubuntu.com/a/437151/207309, this might be due to a DNS issue. If you can double-check your MAAS cluster controller (in the MAAS web UI) is set to manage DNS and DHCP on the its network interfaces? You might need to also go into your MAAS settings page and add a backup DNS, like 8.8.8.8 and see if it ...



Only top voted, non community-wiki answers of a minimum length are eligible