Tag Info

Hot answers tagged

2

Removed "Precise" from /etc/maas/bootresources.yaml and it's now working


1

two ways - you could create an image for mass that has desktop, or, in your charm, in your install hook, you include sudo apt-get install <desktoppackagename> Where sudo aptitude install --no-install-recommends ubuntu-desktop Personally, I think the charm is the easiest way. Help received from this answer: How to install GUI desktop on a ...


1

It appears that you cannot have special characters in your admin secret password.


1

I was recently facing the same question and, aside from the URL quoted above did not find much more. With Maas and Curtin's developer's help, I was able to come up with a working scenario that I described in this blog post. I hope that it can help you out an others facing the same question.


1

Juju attempts to start a new machine and use cloud-init to inject the script necessary to download and start a juju agent process. This process then contacts the juju state server (machine 0) and check in. The status remains in pending forever until the client checks in. If anything goes wrong with this process then the machine stays in pending state ...


1

Hurray. I finally resolved the issue with my remote cluster controller just after editing my post and this by accident. The solution is as following. When creating the remote cluster controller (named Cluster 2 in my case) add a DNS zone different that for the cluster controller associated with the region controller (named Cluster 1 in my case). By ...


1

Yes, although MAAS is not specifically designed for that purpose it could easily be used to manage a deployment of desktop machines. MAAS expects machines to use cloud-init in the boot process, which connects to a metadata source over the network on boot to configure the operating system. Linux operating systems and windows servers can run cloud-init. MAAS ...


1

Yes. There is no difference between loading an image with some other system and loading it with MaaS. The only issue I might see is that MaaS is linux server centric, and there don't seem to be any good tools for building custom images for it. Thus, it doesn't lend itself to loading Desktop or Windows. A work around might be to build "Fast Installer" ...


1

MAAS uses the curtin (or fast path installer) to install images, this copies the image onto the local disk and reboots into it. So, technically it is possible to install any image and it would install it. However, MAAS uses cloud-init in any operating system image to customise the server on booting. This is a requirement of any image that MAAS deploys ...


1

Can you simply start or deploy that node from MAAS without using Juju? I would start there first, and make sure you have imported your key in the MAAS user settings.


1

You need a separate network on which you control the DHCP service. That service tells clients where to go for PXE boot images. If you are running virtualBox machines, all on your machine, you can set their nics as being on "internal network", and have your server be on that network as well. Then set up your MaaS server as DHCP. you may have to turn DHCP ...


1

I also hit that bug, but it's fixed and about to be pushed to the updates repository. Can you try installing the updated package from -proposed and see if it fixes it for you as well? Instructions for adding the -proposed repository are here in this bug comment: https://bugs.launchpad.net/curtin/+bug/1263181/comments/21


1

Curtin tries to choose the most appropriate partition table type for a given node: For systems that are booting in BIOS mode, it defaults to an MBR-stored DOS partition table For systems that are booting in UEFI mode (including ARMv8-based UEFI-enabled systems like Cavium Thunder and APM X-Gene) it defaults to a GPT partition table Therefore, the easiest ...



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