Tag Info

New answers tagged

0

I suggest you import an ssh key to your MAAS user and simply try to "deploy" a node. See if it comes up, transitions to "deployed" and if you can ssh into it with that key as the ubuntu user.


0

I found out the issue. The vagrant box I used for installing MAAS was precise32.box. I used another 64-bit box ubuntu/trusty64 and installed maas services. All MAAS links appeared in web UI and I could import images too. To setup nodes, we should do the following: Create a new network without dhcp enabled. Configure the maas dhcp to point to the above ...


0

I realise where is my issue maas_server: 172.16.0.1/MAAS I've given the IP of MAAS follow with /MAAS to fix it #to remove the proxy configuration http_proxy= https_proxy sudo mv ./.cloud-install ./.cloud-install-backup sudo openstack-install when ask for MAAS IP give only the IP NOTE: if you are working behind proxy remove proxy configuration


0

First of all install MAAS and configure juju on it correctly. If you are testing the installation, I would recommend you to use Ubuntu Server 14.04 LTS installation with MAAS and install juju afterwards. Use a Virtual Machine Manager such as Oracle VirtualBox and register the nodes in the MaaS cluster. Then you can use juju in it. Then install openstack. ...


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.


0

This problem is fixed in MAAS version 1.8.0+bzr4001-0ubuntu2 (trusty1). All nodes and its storage are identified correctly when I recommissioned the machines after upgrading from MAAS 1.7.


0

I'm not sure this is the best way, but after looking around I found some ppas for maas with: https://launchpad.net/ubuntu/+ppas?name_filter=maas Thanks to Andres Martinez, who posted a set of 1.7.6 packages, you can access them for apt-get install after: sudo apt-add-repository ppa:andreserl/maas


0

In theory, you can also use linux containers on the same machine or even your local machine. With linux containers you'll have some form of isolation between processes and each charm will get its own IP address from the DHCP server on your dedicated subnet (if you have a DHCP server installed). https://jujucharms.com/docs/stable/config-local This is ...


2

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


0

The solution has been to install MaaS directly using the ISO and then disable the Cluster Controller from MaaS Ui also if this is not what I want to realize but it's a useful solution


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

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 ...


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 ...


0

Yep that error has magically disappeared now (probably due to another DHCP running on the router) but I have one about IEerror 'Not a gzipped file' Will open another ticker


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

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 ...


0

You edit a node and select the architecture to be "amd64/hwe-u" for utopic and "amd-64/hwe-v" for vivid kernels. To get all kernel releases including development ones update the boot images sync url, in the settings page to be: http://maas.ubuntu.com/images/ephemeral-v2/daily/ and then re-import the boot images.


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

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

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" ...



Top 50 recent answers are included