Tag Info

Hot answers tagged

17

In maas 1.2 through 1.4 the virsh power type requires only the Address and Power ID. The libvirt-bin package needs to be installed to get the virsh command $ sudo apt-get -y install libvirt-bin the Power ID is the name of the virtual machine shown by sudo virsh list --all The address is a normal libvirt connect string: ...


10

I suspect they're just trying to stop people nicking portions of the documentation for their own nefarious purposes but no, by all measures that matter to people like us, that document is not free. But the MAAS packages in the main repos all use the AGPL3 license: MAAS is Copyright 2012 Canonical Ltd. Canonical Ltd ("Canonical") distributes the MAAS ...


5

Scope This document provides instructions on how to install the Metal As A Service (MAAS) software. You have sufficient, appropriate node hardware You will be using Juju to assign workloads to MAAS You will be configuring the cluster network to be controlled entirely by MAAS (i.e. DNS and DHCP) If you have a compatible power-management system, any ...


5

LDS stands for "Landscape Dedicated Server". From landscape.ubuntu.com: The Landscape systems management tool helps you monitor, manage and update your entire Ubuntu infrastructure from a single interface. Part of Canonical’s Ubuntu Advantage support service, Landscape brings you intuitive systems management tools combined with world-class support. ...


5

You may refer to Manual DHCP configuration in the following link http://maas.ubuntu.com/docs/configure.html#manual-dhcp There is also a nice document by DELL (Deploying workloads with Juju and MAAS) where you can find a section for using an existing DNS/DCHP server and you can find it here ...


5

Yes, for one machine MAAS is absolutely overkill. However Juju can (as of version 1.18) deploy to any Ubuntu Server with OpenSSH via manual provisioning, we designed this feature for cases like yours where you want to deploy services quickly without needing a cloud: https://juju.ubuntu.com/docs/config-manual.html The basic process is you register your ...


5

The DHCP configuration is for the MAAS server to be managing it's own subnet; this is how you would usually have a MAAS region/controller set up. The fields are as follows: IP: This is the IP address of your MAAS controller; you are correct in assuming that it would be 172.16.142.61 if you installed it at this address. Subnet Mask: This is the subnet mask ...


5

Ubuntu Cloud and MAAS are different things - different layers if you like. MAAS is a low-level layer which deals with physical hardware. It is for deploying the base level software to a rack of servers quickly and easily. It can then work in conjunction with juju to deploy particular services (e.g. web servers, databases) to that hardware. This could be for ...


5

The reason for this is that OpenStack is not really meant for a 2 node cluster. It is meant to scale to thousands of nodes. It has many disconnected components, including mysql, rabbitmq, several API services, etc. For your case of "just trying openstack out" you can simply use the local provider to install everything on one box rather than MaaS which wants ...


5

Each node that MAAS prepares for you has your ssh key on it, so you can automate these tasks using any method that can use ssh as transport, so that certainly includes Juju. That pushes you into the realm of customising your charms to do these set-up tasks, which might fit your expectations, but is going to be awkward if you're using off-the-shelf charms. ...


4

CONFLICT from maas means that it doesn't have any nodes available for juju to acquire (juju bootstrap needs to boot a node). It's not the best error unfortunately, juju needs fixing to show all the text. You need the server edition of 12.04


4

This can happen when the clock on the node is too far out of sync for the OAuth verification to work, which results in the node timing out when trying to download from the metadata service and eventually continues booting to a login prompt without finishing the commissioning script. Try checking the clock on the node and reset it if it's very different from ...


4

sudo maas changepassword <user>, where user is the user you want the password changed: cerdea@capiau:/var/log/maas$ sudo maas changepassword maas-root Changing password for user 'maas-root' Password: Password (again): Password changed successfully for user 'maas-root' cerdea@capiau:/var/log/maas$ Of course, you may need to find which user to ...


4

if someone deploys maas+juju for openstack, please run juju status --format=png > architecture.png


4

I have the same problem and found solution: you need to install maas-enlist & tftpd-hpa package. sudo apt-get install maas-enlist tftpd-hpa then re-run sudo maas-import-isos -u


4

You can't technically modify the PXE config file in/from MAAS. You have to manually edit it. Every time you add node to MAAS, a PXE config file will be created for one of the MAC Address of the node. In your case, and based on your logs, you would have to edit the following file: /var/lib/tftpboot/pxelinux.cfg/01-00-1d-09-f0-4b-c2 And add noacpi noapm ...


4

Sorry, only Ubuntu is currently supported.


4

The failure that you see is because this is a virtual machine. The ipmi_si related stuff will only work on real hardware, so the error doesn't really affect your case scenario and you don't really need a fix for it. A good idea would be if you were able to post the output of /proc/cpuinfo so that we can make sure that the module above is not loaded on ...


4

The suspected temporary fix to this is check for the presence of an apt proxy in /etc/apt/apt.conf.d and comment that out, as it causes problems with PPA installations from MAAS controlled hosts. For example, within my maas cluster I have /etc/apt/apt.conf.d/90curtin-aptproxy Acquire::HTTP::Proxy "http://10.0.10.2:8000/"; The presence of this curtin ...


4

OP Posted: I am using plain PCs to test the setup. Therefore I am forced to use WOL instead of e.g. IPMI/iDRAC etc. It seems that when you configure the node as using WOL, you have (!!) to enter the MAC address explicitly. Doc reference: http://maas.ubuntu.com/docs/nodes.html#manually-add-nodes


4

Landscape Dedicated Server (LDS) Landscape is the systems management tool for Ubuntu OpenStack included with Ubuntu Advantage. It allows you to manage, audit and report on your Ubuntu OpenStack cloud and services running within its easily as one, making your entire environment more cost-effective.Cloud management


4

Preparing MAAS for Juju and OpenStack using Simplestreams When Juju bootstraps a cloud, it needs two critical pieces of information: The uuid of the image to use when starting new compute instances. The URL from which to download the correct version of a tools tarball. This necessary information is stored in a json metadata format called ...


4

The place to look for this kind of information is /var/log/maas/celery.log. Whenever a node is powered on by MAAS it should contain an entry such as: [2014-05-28 10:10:54,226: INFO/MainProcess] Received task: provisioningserver.tasks.power_on[65b69047-46ca-4164-ad32-cb3362e79de9] [2014-05-28 10:10:54,447: INFO/MainProcess] Task ...


4

DISCLAMIER: I AM NOT AN OPENSTACK EXPERT. THE FOLLOWING IS MERELY AN OPINION AND MAY BE OUTDATED OR COMPLETELY INCORRECT. IN NO WAY CAN I BE HELD RESPONSIBLE FOR CONSEQUENCES IN USING THE CONTENT BELOW. Multi-Hosting Having networking services running on every node will have its advantages and disadvantages. Many different networking redundancy ...


4

I think you are probably hitting this bug: https://bugs.launchpad.net/ubuntu/raring/+source/ceph/+bug/1218852 Right now the version of Ceph in 13.04 and the Ubuntu Cloud Archive for Grizzly can't deal with uppercase letters in hostnames. Your hostname appears to be 'CS1'.


4

If you verified there are no obvious errors, you can always retry running the hook to see if it resolves the issue: juju resolved --retry keystone/0 If the problem still persists, you could try: juju debug-hooks keystone/0 config-changed, which will SSH into the machine and wait for the config-changed to run. You need to manually trigger the hook outside ...


4

Juju will use the url specified in your environments.yaml file under a provider of type maas. It should look something like this: maas: type: maas # Change this to where your MAAS server lives. It must specify the base path. maas-server: 'http://192.168.1.140/MAAS/' Note, there can be some differences based on the version of Juju you're using, so ...


4

The issue you were running into is with apparmor. 'dmesg' would probably have shown you something like: [ 4822.366235] type=1400 audit(1384973058.254:52): apparmor="DENIED" operation="mount" info="failed type match" error=-13 parent=1272 profile="lxc-container-default" name="/mnt/" pid=1273 comm="mount" fstype="ext4" srcname="/dev/loop0/" flags="ro" ...


4

HA is designed and planned for 14.04 in the case of both MAAS and Juju. You could manually construct it yourself now, but it would be rather difficult and then difficult to upgrade in future. For now, I'd suggest using RAID mirroring and careful choice of nodes for reliability. If your MAAS or Juju go down you cannot scale up but you also don't lose the ...


3

When nodes in MaaS are in the commissioning state, they are not available for Juju to use. When the nodes are ready for allocation, they will show in MaaS as the Ready state. When you bootstrap using Juju, it creates a node that will queue future deploy and relation setting commands to be run at the correct time during the installation of the various ...



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