Tag Info

Hot answers tagged

2

I assume by charm store you are referring to the website? I'm almost sure that Squid is overkill. I see that machine 0 uses your proxy successfully. I can also see that the default route of machine 0 is 172.16.1.1, but the default route of the MAAS host is 172.16.1.2. It is set up incorrectly in the MAAS web interface, as you show in your screenshot. Change ...


2

So your node is a VM, right? MAAS will call virsh as the "maas" user, so ~maas/.ssh/id_rsa has to exist, be correct in terms of permissions and be a private key allowed to login on the host where the VM is running. You can test it by becoming the maas user on the MAAS machine and trying to use virsh as MAAS would. For example: sudo -H -u maas virsh -c ...


2

I will divide your question in two parts: Is it possible to have a Windows Server as a MAAS node? Yes, as this is FLOSS (Free/Libre Open Source Software) anything is possible as long as you find enough people willing to develop something. In the near future? Yes, MAAS can provision Windows Server 2012 RT/Hyper-V since 2014...


1

This launchpad bug is the same issue, seems better to handle it there probably?


1

It could be several things indeed. So let's go through the generic steps of getting logs from a failed deployment. First let's show how to get access to the different juju environments in play here: Landscape environment: where the Autopilot was deployed Autopilot environment: the cloud environment created by Autopilot Taken from Landscape openstack juju ...


1

The actual command that performs this operation is built into curtin in the partitioning_commands. Curtin by default will call "curtin block-meta simple". The command searches for a disk to perform the installation on, the error you are seeing is because your system has no disks that curtin can install to. Make sure that the system you are deploying to has a ...


1

MAAS will be on its own node, and most people usually run the installer from the MAAS machine. You'll still need 7 machines as stated in the requirements section from that document.


1

please see the following answer, I believe it's exactly what you are looking for: Add node to existing landscape openstack


1

I had the same issue and was able to get it working by disabling open-iscsi and enabling tgt: systemctl stop open-iscsi systemctl disable open-iscsi systemctl enable tgt systemctl start tgt ps -ef | grep tgtd grep tgtd /var/log/syslog You should see the MaaS iSCSI targets in the log.


1

The text quoted in the comment shows that at least the documentation is non-free. The Launchpad page for MAAS, which seems to be the most detailed source, says on 2015-05-21 GNU Affero GPL v3, Other/Proprietary (temporary) ... This project’s licence is proprietary. So it seems that MAAS is at least partially under a proprietary licence. It's hard to find ...


1

Try adjusting your hardware clock. If you are using Cisco switches, try to enable Portfast. Try to dig and ping your fully qualified domain name of your node and make sure DNS and network connectivity are set right.



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