New answers tagged maas
There is no no-proxy support in juju just yet. It is on my very short term TODO list. Given that you are the third person I know of in a very short time frame that is needing this may well bump the priority. It isn't hard to do, and I'll look to get it done first thing Monday. If you are using trunk, expect it Tuesday, if not, you'll have to wait for the ...
I was facing similar issues on a devstack installation of openstack. It seems like the variable is case sensitive. To solve this I did the following: Get your ipaddress using the following: ifconfig and open your ~/.bashrc file, add this to the end: no_proxy=localhost,127.0.0.1,<your_ip_address> NO_PROXY=localhost,127.0.0.1,<your_ip_address> ...
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
I'm not 100% positive this works with MAAS - but I know this method works with other providers. When I want to destroy a service and its "stuck" in a dying state, using your wordpress deployment as an example: juju resolve wordpress/0 now if that fails to help the situation, ergo, it continues to go from hook to hook in an error state, I will destroy the ...
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 ...
Have you followed Havana installation guide for steps other that apt-get install openstack-dashborad ? you can find it here http://docs.openstack.org/havana/install-guide/install/apt/content/install_dashboard.html check also the note for Ubuntu users Remove the openstack-dashboard-ubuntu-theme package. This theme prevents translations, several menus as ...
As stated in MAAS documentation, altering the preseed files is not recommended, because it might prevent MAAS from properly commissioning and installing nodes. Are you able to connect to the node using SSH and user ubuntu? If so, looking in /var/log/dmesg and /var/log/syslog can help diagnosing startup and networking issues. If you need to alter the ...
The tutorial you mention is outdated, try following this one instead, but start from scratch, running rm -fr ~/.juju/environments* first. Make sure you change the necessary settings in the environments.yaml file juju generate-config created, in the configuration of the maas sample environment.
Thank you for the report! This is a confirmed bug in juju-core, which you helped discover: https://bugs.launchpad.net/juju-core/+bug/1283866. It basically means Juju's OpenStack provider is not yet compatible with versions of OpenStack later and including Grizzly (in certain cases). Since part of the current development emphasizes on more customizable ...
Juju GUI (source: lp:juju-gui; live demo) allows you to deploy services in a Juju environment through a web browser. It's a free software with AGPL v3 license, so you can probably fork it and modify it as needed, if it doesn't quite fit your needs. To use it, you'll need to deploy it in your environment and expose it. See the deployment instructions. If ...
Take a look at /var/log/maas/celery.log to make sure the import task starts and does not immediately stop with an error of some kind. From my experience, import-boot-images won't succeed if the MAAS Cluster Controller does not have access to the Internet, or if the DHCP/DNS configuration on the VM network is not properly configured. Once you see no errors ...
Make sure your manually added VM is configured properly, as described here. You can choose the Ubuntu release from the drop down menu. I'm assuming you followed the installation instructions outlined here, especially the Post-Install Tasks, like importing the boot images. They are needed, along with correct DHCP configuration on the network, so that VMs can ...
I came across the same errror, and yes indeed it was a typo in the mass-server URL at the ~/.juju/environments.yaml Yet after fixing it and bootstrapping again, same error appeared. The I removed the file ~/.juju/environments/maas.jenv and tried again. works like charm.
If you can add a second NIC to the master server, and enable IPv4 forwarding and NAT, you can use the second NIC to connect to the switch and all the other machines, while using the first NIC on the server to access the outside, both for the server and the machines. You might find this useful: https://help.ubuntu.com/community/Internet/ConnectionSharing
Since the bug mentions a fix was released for the python-django-piston package, try running: sudo apt-get update && sudo apt-get upgrade If the package gets upgraded, restart maasserver and retry adding the VM.
OK I repeated the same practice without "sudo apt-get dist-upgrade" and the error was gone.
Top 50 recent answers are included