I have a working two node juju enabled MAAS that has the beginnings of hadoop installed. I got this working using the following steps:
- bootstrapping the environment
- adding a hadoop charm
Once I did added the charm, the second node appeared when I ran juju status. It was never able to install the agent, which always reported as not-started.
To get the agent installed, I destroy-environment'ed my juju. Then I did a bootstrap again. To my surprise all the nodes appeared in the list in MAAS as allocated to me, and then when I rebooted the second node, it all of a sudden wanted to install the image with the juju agent in it.
So, I have two functioning nodes one is the juju environment node, the other is the hadoop master. What I am trying to do is bring a third node up so that I can have some slavecluster nodes. But I am now facing the same problem as with the second node:
MAAS is not installing the juju-agent enabled image to the third node, so the agent status is always not-started.
Is this a juju problem, where juju must inform MAAS that it should install the correct image to the node? Or is this a MAAS problem where states are out of sync?
It really surprising that to get this to work, I have to destroy-environment, and then bootstrap again, and everything is OK.
Anyone have any ideas what I have done here?