MAAS Development Summary – June 12th – 16th

The purpose of this update is to keep our community engaged and informed about the work the team is doing. We’ll cover important announcements, work-in-progress for the next release of MAAS and bugs fixes in release MAAS versions.

MAAS Sprint

The Canonical MAAS team sprinted at Canonical’s London offices this week. The purpose was to review the previous development cycle & release (MAAS 2.2), as well as discuss and finalize the plans and goals for the next development release cycle (MAAS 2.3).

MAAS 2.3 (current development release)

The team has been working on the following features and improvements:

  • New Feature – support for ‘upstream’ proxy (API only)Support for upstream proxies has landed in trunk. This iteration contains API only support. The team continues to work on the matching UI support for this feature.
  • Codebase transition from bzr to git – This week the team has focused efforts on updating all processes to the upcoming transition to Git. The progress so far is:
    • Prepared the MAAS CI infrastructure to fully support Git once the transition is complete.
    • Started working on creating new processes for PR’s auto-testing and landing.
  • Django 1.11 transition – The team continues to work through the Django 1.11 transition; we’re down to 130 unittest failures!
  • Network Beaconing & better network discovery – Prototype beacons have now been sent and received! The next steps will be to work on the full protocol implementation, followed by making use of beaconing to enhance rack registration. This will provide a better out-of-the-box experience for MAAS; interfaces which share network connectivity will no longer be assumed to be on separate fabrics.
  • Started the removal of ‘tgt’ as a dependency – We have started the removal of ‘tgt’ as a dependency. This simplies the boot process by not loading ephemeral images from tgt, but rather, having the initrd download and load the ephemeral environment.
  • UI Improvements
    • Performance Improvements – Improved the loading of elements in the Device Discovery, Node listing and Events page, which greatly improve UI performance.
    • LP #1695312 – The button to edit dynamic range says ‘Edit’ while it should say ‘Edit reserved range’
    • Remove auto-save on blur for the Fabric details summary row. Applied static content when not in edit mode.

Bug Fixes

The following issues have been fixed and backported to MAAS 2.2 branch. This will be available in the next point release of MAAS 2.2 (2.2.1) in the coming weeks:

  • LP: #1678339 – allow physical (and bond) interfaces to be placed on VLANs with a known 802.1q tag.
  • LP: #1652298 – Improve loading of elements in the device discovery page
Posted in MAAS, Planet | Leave a comment

MAAS Development Summary – June 8th, 2017

Thursday June 8th, 2017

The MAAS team is happy to announce the introduction of development summaries. We hope this helps to keep our community engaged and informed about the work the team is doing. We’ll cover important announcements, work-in-progress for the next release of MAAS, and bugs fixed in released MAAS versions.

Announcements

With the MAAS 2.2 release out of the door, we are happy to announce that:

  • MAAS 2.3 is now opened for development.
  • MAAS is moving to GIT in Launchpad – In the coming weeks, MAAS source will now be hosted under a GIT repository in Launchpad, once we complete the work of updating all our internal processes (e.g. CI, Landers, etc).

MAAS 2.3 (current development release)

With the team now focusing efforts on the new development release, MAAS 2.3, the team has been working on the following features and improvements:

  • Started adding support for Django 1.11 – MAAS will continue to be backward compatible with Django 1.8.
  • Adding support for ‘upstream’ proxy – MAAS deployed machines will continue to use MAAS’ internal proxy, while allowing MAAS ‘ proxy to communicate with an upstream proxy.
  • Started adding network beaconing – New feature to support better network (subnet’s, vlans) discovery and allow fabric deduplication.
    • Officially registered IPv4 and IPv6 multicast groups for MAAS beaconing (224.0.0.118 and ff02::15a, respectively).
    • Implemented a mechanism to provide authenticated encryption using the MAAS shared secret.
    • Prototyped initial beaconing multicast join mechanism and receive path.

Libmaas (python-libmaas)

With the continuous improvement of the new MAAS Python Library (python-libmaas), we have focused our efforts on the following improvements the past week:

  • Add support to be able to provide nested objects and object sets.
  • Add support to be able to update any object accessible via the library.
  • Add ability to read interfaces (nested) under Machines, Devices, Rack Controllers and Region Controllers.
  • Add ability to read VLAN’s (nested) under Fabrics.

Bug Fixes

The following issues have been fixed and backported to MAAS 2.2 branch. This will be available in the next point release of MAAS 2.2 (2.2.1) in the coming weeks:

  • Bug #1694767: RSD composition not setting local disk tags
  • Bug #1694759: RSD Pod refresh shows ComposedNodeState is “Failed”
  • Bug #1695083: Improve NTP IP address selection for MAAS DHCP clients.

Questions?

IRC – Find as on #maas @ freenode.

ML – https://lists.ubuntu.com/mailman/listinfo/maas-devel

Posted in MAAS, Planet, Ubuntu | Tagged | Leave a comment

MAAS 2.2.0 Released!

I’m happy to announce that MAAS 2.2.0 (final) has now been released, and it introduces quite a few exciting features:

  • MAAS Pods – Ability to dynamically create a machine on demand. This is reflected in MAAS’ support for Intel Rack Scale Design.
  • Hardware Testing
  • DHCP Relay Support
  • Unmanaged Subnets
  • Switch discovery and deployment on Facebook’s Wedge 40 & 100.
  • Various improvements and minor features.
  • MAAS Client Library
  • Intel Rack Scale Design support.

For more information, please read the release notes are available here.

Availability
MAAS 2.2.0 is currently available in the following MAAS team PPA.
ppa:maas/next
Please note that MAAS 2.2 will replace the MAAS 2.1 series, which will go out of support. We are holding MAAS 2.2 in the above PPA for a week, to provide enough notice to users that it will replace 2.1 series. In the following weeks, MAAS 2.2 will be backported into Ubuntu Xenial.
Posted in canonical, Planet, Ubuntu | Leave a comment

So… Where’s Chuck this past Weekend?

Filming Fast & Furious 7…

Note: The car is what we call a Combi in Peru, which is a form of public transportation. While I didn’t create the FF7 original pic, it is mock to peruvian combi drivers because those are one of the most reckless drivers in the world.

Posted in Planet, Ubuntu | Leave a comment

Getting Started with MAAS and Juju: MAAS Overview

For a while, I have been wanting to write about MAAS and how it can easily deploy workloads (specially OpenStack) with Juju, and the time has finally come. This will be the first of a series of posts where I’ll provide an Overview of how to quickly get started with MAAS and Juju.

What is MAAS?

I think that MAAS does not require introduction, but if people really need to know, this awesome video will provide a far better explanation than the one I can give in this blog post.

http://youtu.be/J1XH0SQARgo

 

Components and Architecture

MAAS have been designed in such a way that it can be deployed in different architectures and network environments. MAAS can be deployed as both, a Single-Node or Multi-Node Architecture. This allows MAAS to be a scalable deployment system to meet your needs. It has two basic components, the MAAS Region Controller and the MAAS Cluster Controller.

MAAS Architectures

Region Controller

The MAAS Region Controller is the component the users interface with, and is the one that controls the Cluster Controllers. It is the place of the WebUI and API. The Region Controller is also the place for the MAAS meta-data server for cloud-init, as well as the place where the DNS server runs. The region controller also configures a rsyslogd server to log the installation process, as well as a proxy (squid-deb-proxy) that is used to cache the debian packages. The preseeds used for the different stages of the process are also being stored here.

Cluster Controller

The MAAS Cluster Controller only interfaces with the Region controller and is the one in charge of provisioning in general. The Cluster Controller is the place the TFTP and DHCP server(s) are located. This is the place where both the PXE files and ephemeral images are being stored. It is also the Cluster Controller’s job to power on/off the managed nodes (if configured).

The Architecture

As you can see in the image above, MAAS can be deployed in both a single node or multi-node. The way MAAS has being designed makes MAAS highly scalable allowing to add more Cluster Controllers that will manage a different pool of machines. A single-node scenario can become in a multi-node scenario by simply adding more Cluster Controllers. Each Cluster Controller has to register with the Region Controller, and each can be configured to manage a different Network. The way has this is intended to work is that each Cluster Controller will manage a different pool of machines in different networks (for provisioning), allowing MAAS to manage hundreds of machines. This is completely transparent to users because MAAS makes the machines available to them as a single pool of machines, which can all be used for deploying/orchestrating your services with juju.

How Does It Work?

MAAS has 3 basic stages. These are Enlistment, Commissioning and Deployment which are explained below:

MAAS Process

Enlistment

The enlistment process is the process on which a new machine is registered to MAAS. When a new machine is started, it will obtain an IP address and PXE boot from the MAAS Cluster Controller. The PXE boot process will instruct the machine to load an ephemeral image that will run and perform an initial discovery process (via a preseed fed to cloud-init). This discovery process will obtain basic information such as network interfaces, MAC addresses and the machine’s architecture. Once this information is gathered, a request to register the machine is made to the MAAS Region Controller. Once this happens, the machine will appear in MAAS with a Declared state.

Commissioning

The commissioning process is the process where MAAS collects hardware information, such as the number of CPU cores, RAM memory, disk size, etc, which can be later used as constraints. Once the machine has been enlisted (Declared State), the machine must be accepted into the MAAS in order for the commissioning processes to begin and for it to be ready for deployment. For example, in the WebUI, an “Accept & Commission” button will be present. Once the machine gets accepted into MAAS, the machine will PXE boot from the MAAS Cluster Controller and will be instructed to run the same ephemeral image (again). This time, however, the commissioning process will be instructed to gather more information about the machine, which will be sent back to the MAAS region controller (via cloud-init from MAAS meta-data server). Once this process has finished, the machine information will be updated it will change to Ready state. This status means that the machine is ready for deployment.

Deployment

Once the machines are in Ready state, they can be used for deployment. Deployment can happen with both juju or the maas-cli (or even the WebUI). The maas-cli will only allow you to install Ubuntu on the machine, while juju will not only allow you to deploy Ubuntu on them, but will allow you to orchestrate services. When a machine has been deployed, its state will change to Allocated to <user>. This state means that the machine is in use by the user who requested its deployment.

Releasing Machines

Once a user doesn’t need the machine anymore, it can be released and its status will change from Allocated to <user> back to Ready. This means that the machine will be turned off and will be made available for later use.

But… How do Machines Turn On/Off?

Now, you might be wondering how are the machines being turned on/off or who is the one in charge of that. MAAS can manage power devices, such as IPMI/iLO, Sentry Switch CDU’s, or even virsh. By default, we expect that all the machines being controlled by MAAS have IPMI/iLO cards. So if your machines do, MAAS will attempt to auto-detect and auto-configure your IPMI/iLO cards during the Enlistment and Commissioning processes. Once the machines are Accepted into MAAS (after enlistment) they will be turned on automatically and they will be Commissioned (that is if IPMI was discovered and configured correctly).. This also means that every time a machine is being deployed, they will be turned on automatically.

Note that MAAS not only handles physical machines, it can also handle Virtual Machines, hence the virsh power management type. However, you will have to manually configure the details in order for MAAS to manage these virtual machines and turn them on/off automatically.

Posted in canonical, Planet, Ubuntu | Tagged , , , | Leave a comment

Arequipa – Peru

I just wanted to share a few pics I was sent of the Volcano & my hometown… enjoy!

Posted in Planet, Ubuntu | Tagged , | Leave a comment

PowerNap Improvements session at UDS-O

After the success of the improvements of PowerNap in Ubuntu Natty 11.04, we will be having another session st UDS-O Thursday the 12th at 15:00. In this session we will discuss the following:

  • Second Stage action when running in PowerSave mode.
  • Support for port-ranges in Network Monitors
  • Changing the polling monitoring system to an event based system.
  • Client/Server approach to monitor/manage PowerNap “client machines” over the network for data center wide deployments
  • Server ARP network Monitoring for Automatic Wake-up of Clients.
  • API like approach for Integration with other projects.

Everyone who’s interested are more than welcome to join! For more information, the blueprint can be found HERE.

Posted in Planet, Ubuntu | Tagged , , , | Leave a comment

HA Cluster Stack Session at UDS-O

Thursday the 12th at noon we will be having the HA Cluster Stack session. In the session we will discuss the following:

  • Discuss the adoption of new upstream releases of the HA Cluster Stack to include in Oneiric in preparation for the next Ubuntu LTS release.
  • Finish up work items from previous sessions (mainly documentation).
  • Gather feature requests and discuss the creation of meta-packages.
  • And, if the time allows us, I’d like to follow up with HA for OpenStack as they had a session in their Design Summit about it.

If you are interested of the Future of HA Clustering in Ubuntu, you are more than welcome to join this session. For more information the blueprint can be found HERE.

Posted in Planet, Ubuntu | Tagged , , | Leave a comment

Server Team 20110412 meeting minutes

Here are the minutes of the server team meeting. They can also be found online with the irc log here.

=== Meeting Actions ====

  • No actions.

==== Review ACTION points from previous meeting ====

  • Daviey to submit UDS-O topic for translations and docs
    • Talked to David P. about it and agreed to participate in the UDS-O session.
  • jamespage to helpout with verification of euca-dhcp bug
    • DONE
  • jamespage to discover process/location for fixing ubuntu server documentation
    • DONE
    • Docs up to date: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Documentor resources

==== Natty Development ====
Focus is now on bug fixing rather than development.

  • robbiew: any remaining work items should be universe related or non-code
  • SpampS mentioned a few items are remaining:
  • http://people.canonical.com/~platform/workitems/natty/canonical-server.html

==== Ubuntu Server Team Events ====

  • SpamapS: Apr. 13,14 I will be at the MySQL Users’ Conference in Santa Clara, CA
  • jamespage: I’ll be attending puppet camp europe on the 28/29 April in Amsterdam
  • zul: Apr 25 – 29 I will be at the Openstack summit, Santa Clara, CA

==== Weekly Updates & Questions for the QA Team (hggdh) ====

  • initial ISO tests via jenkins are all done, with success except for ec2.
  • Proposed to discuss jenkins usage on UDS.

==== Weekly Updates & Questions for the Kernel Team (smb) ====

  • Launchpad bug 751253 in linux (Ubuntu) “Many interrupts and slow disk I/O on Lucid xen guest” [Undecided,New] https://launchpad.net/bugs/751253
  • <smb> thinks really that sounds a bit like maybe xen version or actually a lot of traffic as that machine had 500GB going out in 5 days

==== Weekly Updates & Questions for the Documentation Team (sommer) ====

  • Not present
  • SpampS suggested to select someone else to drive the team.
  • RoAkSoAx suggested to remote the item from the Agenda until replacement is found.

==== Weekly Updates & Questions from the Ubuntu Community ====

  • kim0: Will be running a weekly community IRC meeting for the Ensemble team. This will be run in #ubuntu-cloud starting tomorrow at 6pm-UTC, it will be merged with the older community meeting. Everyone attending this meeting is a good candidate to attend tomorrow’s
  • That meeting will provide a high level overview of development in the Ensemble world since last meeting/week.
  • Writing an announcement on http://cloud.ubuntu.com/ right now, which I’ll mirror on planet, and everyone is encouraged to spread/tweet…etc

==== Open Discussion ====

  • kirkland throwing a release party:   http://blog.dustinkirkland.com/2011/04/austins-natty-release-party.html

==== Announce next meeting date and time ====

  • Tuesday, April  19th 2011 16:00 UTC
Posted in Planet, Ubuntu | Leave a comment

Cancer or AIDS?

Don’t worry, I don’t have the sickness nor I desire it to anyone (Knock on wood). This post represents my thoughts on the recent presidential elections held in Peru.  I’m not gonna go into much detail but rather give a brief overview of how I see things in my country. Also, I apologize if the reference to the sicknesses offends someone, as I’m just really trying to represent what great amount of people in my country think. (Not only me, but my family, friends, the young and the old, and even the press)

Yesterday Sunday, presidential elections were held. 5 were the candidates, 3 of which were the most popular. Unfortunately, only two of them go to a second stage on which the president will be elected. These are, Keiko Fujimori (Cancer) and Ollanta Humala (AIDS).

Keiko Fujimori, daughter of Alberto Fujimori, former president of Peru between 1990 and 2000 (after two consecutive periods) and 2001 (third period). Keiko Fujimori, very well educated person, having studied in the US. His father, the worst kind of man in the world. During this presidency, he stole millions and millions of dollars. He was supposed to only server two consecutive periods according to laws, however, his desire for power was greater that he tricked the elections and won a third time. After this, videos of his advisor Vladimiro Montesinos bribing congress man/business man/etc appeared on TV. The advisor, decided to scape the country, and with him Alberto Fujimori. He created a show trying to look after Vladimiro, however, it was just a distraction to help him scape (or so is presumed). Then, months later (if I recall correctly), he went to Japan for a presidential visit. However, once he arrived there, he declared himself as Japanese citizen and resigned to the presidency. Years later he tried to came back to Peru through Chile, but he was caught and now he is serving his sentence in jail for all the crimes he committed. It is presumed that along with his advisor, they stole millions of dollars from Peru, bribed people, controlled newspapers and all that sort of stuff. He managed to hide (or destroy) most of the evidence they got against him, but he left his advisor hanging. Anyways, during his first few years as a president, he didn’t do all bad things though. He pretty much eliminated terrorism and pulled Peru up economically, from a sinking ship. Peru was submerged in inflation. His daughter, however, doesn’t have anything to offer to the country. She got where she is thanks to the popularity of her father. Vote percentage (~26%)

Ollanta Humala, on the other hand, very badly educated (from my point of view). Retired commander from the Peruvian Army. Very well educated father, and murderer brother. Puppet of Hugo Chavez. Well, there’s not really much to say about him rather than he is just incompetent. His brother (and presumably him) organized a a take over of a small town in the Peru mountains leader-ed by the brother (Ollanta of course always said he wasn’t involved). They killed cops.  His brother is currently in jail and he has admitted that his brother was involved (I presume after left abandoned by him to rotten in Jail). In the northern part of the country, Indians from the jungle started a quarrel with the current government, taking roads and killing lots of cops. It was proven with videos and intelligence report that this was all organized by Ollanta and his puppets. Anyways, with help of Hugo Chavez, he has been trying to buy the country. In poor places, he has created organizations financed by Chavez, to “feed” (or should I say recruit) people to join the cause. Anyways, he has proven himself uneducated in the debates and an idiot in various aspects of the current situation of Peru in general. However, this didn’t prevent him from being the highest voted in Peru (~30%).

So anyways, Ollanta wants to renegotiate all the international treaties. He wants to change the constitution. He wants to give the wealth of the country to the poorest (and obviously take it from the richest’s and middle class). He wants to do what Chavez and Evo (president of Bolivia) did to their countries. He wants to rule all his life in a dictatorship rather than a democracy. Economically, he is gonna f**** the country up for his own interests. Which ones? Power, Money, you know. On the other side, Fujimori, is gonna probably follow his daddy’s saying. Yeah, she is just a face behind the master mind.

30% of the country was ignorant enough to chose for Ollanta. Yes only the poor, who were maliciously tricked, voted for Ollanta. Now, around 30% of the Peruvian population is considered to be poor. From that percentage, almost all voted for Ollanta (from my point of view). 26% of the population voted for Fujimori. The rest, around 56% voted for other candidates, mainly 3, who weren’t intelligent enough to join forces against a common enemy (again, they all went towards their own personal interests rather than the country’s sake). Unfortunately for us, everybody that decided to vote against the worse, voted for 3 of the candidates and that wasn’t enough to beat the enemy.

So you may wonder, why has this happened. In short and as I mentioned above, it is a combination of lack of judgment and education. Yes, Peru is a country on which education is not a priority. (State universities, schools, etc etc, simply suck). So candidates took advantage of the lack of education to get votes. Unfortunately for us, there were so many candidates that the worst ended up having the most votes. If I recall correctly, Peru is a country that has 85% of the biodiversity of the world. We have gold, natural gas, silver, and other minerals. We are so rich in many stuff, but yet, so poor in education and judgment. Congressman, Presidents, etc, they only worry about their own pockets and people is just so ignorant that they keep voting for them. People don’t vote objectively, they just vote because of the fancy things presidents say. Ignorants, voted for the ignorants. Fujimorists, voted for Fujimori. The rest, voted for the better, unfortunately, the better wasn’t united.

To conclude, Peru is now in the hands of us the voters to decide for the better. Not the best, the better. I just hope people see the way I see it. Unfortunately, we are between Cancer and AIDS. I believe if Fujimori ends up as a president, we have some hope, but if not, we are doomed. People is scared of getting the Fujimori clan into the government again, but most of us are even more scared of having Ollanta changing the country Chavez’ like!

Posted in Planet, Ubuntu | Leave a comment