This bi-weekly update in MAAS, we’ve gone through a few QA sessions for cloud-init and in-app new release notifications. For SR-IOV NUMA node, we’ve started building a skeleton placeholder for the UI and waiting to be connected with the API services for a complete sign off.
Cloud init snippet input - QA
In 2.9 our deployment form will support additional cloud-init snippets for users who prefer to customise their user-data during deployment. Once you select a machine(s) for deployment, you may select the “Cloud-init user-data” checkbox or “choose file” button to import your user-data script during deployment. You may also register MAAS as KVM host at the same time. However, we currently only support Ubuntu 18.04 “Bionic Beaver” for this option.
At this stage, if a user uploaded the cloud-init script during deployment, you won’t be able to validate your script or provide confirmation on which machine has a script embedded. Part of our future work will include validation, reusable script selection, as well as a flag to describe extra add-ons.
New Release Notifications in-app - QA
In our previous blog post, we mentioned that we want to encourage MAAS users to upgrade their MAAS to the newest version. Thus, increasing the announcement channel is one solution to help our MAASters upgrade and stay informed about security and bug fixes. In 2.9 our new release announcements will also be in the MAAS-UI, providing pertinent information for the upgrade.
If a user and admin users chose to dismiss the notification, we will send another automatic follow-up for the announcement in 2 weeks.
As an admin user, you may also manage your notification settings to never inform you about the new release, by deselecting the enable new release notification checkbox.
To avoid noises in the UI, we will only show this announcement on the machine listing page and the settings page, so our users’ workflow won’t get interrupted with announcements.
Last iteration, we have finalised our NUMA node design for KVMs. This view aims to provide a bird’s eye view of resources such as information about your virtual memory, hardware, NICs and storage.
This week, the UI team has built a placeholder template from the finalised designs for our first round UX/UI QA and will perform another QA once we have integrated these functionalities with the API services.
Users can view resources by NUMA node and through the aggregated view. We also save the state on your latest viewing option. So once you revisit, the switch will be left in the latest selected state.