Fiberlink maas 360

The maas server must be modified from its default configuration in order to execute the extensions scripts correctly.Extensions ArchitectureOnce installed, the extensions are placed in:The power template folder for MAAS: this is usually /etc/maas/templates/power.The VBox_extensions folder in the MAAS default user: this is usually maas, therefore some scripts are placed in /home/maas/VBox_extensions or /var/lib/maas/VBox_extensions.The VBox_host_extensions folder in the VirtualBox default user: this is usually a standard user, for example IvanZoratti, therefore some scripts are placed in OS X in /Users/IvanZoratti/Vbox_host_extensions and in Ubuntu in /home/IvanZoratti/Vbox_host_extensions.Each request (a Power ON request) follows this flow:The request is activated by an adimn action, for example "Commission Node"MAAS calls the script generated by a power template, in this case "/etc/maas/templates/power/ether_wake.template"The power template calls a script in the VBox_extension folder, in this case "power_on"The power script checks the incoming request and sends a request to all the available VirtualBox hosts machines via SSH. The request calls a script in the VBox_host_extension folder, in this case "startvm"LoggingA basic logging of all the operations is kept in the /tmp/VBox.log file. The file is updated by the template and the scripts in the MAAS server. The file is removed when the MAAS server reboots.MAAS PreparationThese actions must be performed in order to prepare the MAAS server:Check the status of the maas user, i.e. home directory and shell. Retrieve the status of the user with:grep "maas" /etc/passwdMake the maas user interactive and sudoer: from a sudoer user in the MAAS server:sudo -u maas chsh -s /bin/bashsudo passwd maas...Type you favourite password for the maas usersudo adduser maas sudoLogin to maas using the new passwordIn the maas home folder, copy the VBox_extensions folder and files.It is advisable, for testing and demoing, to set the accept-all option for all the nodes registered on the MAAS server. This action is not mandatory (see to the maas user and run the installation script:cd VBox_extensions./install_extensions user@vbox_host_address, where is the IP address of the VirtualBox host machine to add to MAAS and is a standard user on the VirtualBox host machine. For example, a valid parameter is [email protected] the install_extensions script for all the VirtualBox host machines you want to control from the MAAS server.This is in brief what the script does:Check the presence of the user@vbox_host_address paramterRetrieve and save the MAAS API KeyThe script requires the maas password to sudoCopy the new power template in the MAAS server power template folderGenerate a new public key for the maas userIf the key already exists, the script may require to overwrite the old keyCopy the maas user public key to the VirtualBox host machineThe password for the designated user on the VirtualBox host machine is requiredCopy the extension scripts on the VirtualBox host machineHow to use

MAAS_VirtualBoxThis project offers a set of basic extensions for MAAS to integrate VirtualBox VMs. It has been tested with VirtualBox 4.3.20r96996 for OS X (Mavericks 10.9.5), hence different versions of VirtualBox and/or VirtualBox running on other host machines may have some issues.These extensions work well for testing, demoing and development, but they are not recommended for production use.FeaturesThe VirtualBox extensions for MAAS offer these features:VirtualBox VMs can be autodiscovered, they can be started, commissioned and acquired.Multiple VirtualBox host machines are allowed, provided they are accessible from the MAAS server and the MAAS server can offer PXE Boot, DHCP and DNS services.Current LimitationsAt the moment, the VirtualBox extensions for MAAS have these limitations:VirtualBox VMs cannot be checked, i.e. administrators using MAAS cannot check from MAAS if the node is ON or OFF by using the "Check power state" button in the "Edit Node" page.VirtualBox VMs cannot be stopped from MAAS.The Wake-on-LAN option is no longer present in MAASThe description of the physical zones in MAAS is no longer freely usable (it is reserved for the extensions).A power request is sent to all the available VirtualBox host machines, i.e. at the moment the scripts do not check which VirtualBox machine hosts the VM.The error status of many commands in the powering process is not checked.The testing is limited to Ubuntu VMs on VirtualBox host machines in OS X Mavericks 10.9.5.Basic ConceptsThe VirtualBox extensions for MAAS are used to control VirtualBox VMs from the MAAS server. At the moment, only the "Start Node" (or Power ON) action has been implemented, but there are already scripts that can be used to integrate "Stop Node" (or Power DOWN) and "Check power state" (or Power CHECK).The extensions rely on these basic concepts:The MAAS server and the VirtualBox host machines are connected to the same network: this is also essential to allow PXE boot of the VMs, the use of OS images hosted by the MAAS server and the use of DHCP and DNS services, also offered by the MASS Server.The MAAS server must send ssh commands to the VirtualBox host machines.The VirtualBox extensions replace the Wake-on-LAN option in MAAS: this means that the parameters used to identify a VirtualBox VM must be added to a node by using the "Power Type" options for Wake-on-LAN. It also means that the standard Wake-on-LAN power option is no longer available on the MAAS server.The VirtualBox host machines are identified by MAAS physical zones.A MAAS physical zone can refer only to one VirtualBox host machine.Many MAAS physical zones can refer to the same VirtualBox host machine, although this is not advisable: the best approach is to identify one physical zone in MAAS for one VirtualBox host machine.The maas user on

3 Fourth Wing (1 of 2) [Dramatized Adaptation] : The Empyrean 1(Empyrean) Rebecca Yarros 4 Fourth Wing (2 of 2) [Dramatized Adaptation] : The Empyrean 1 (Empyrean) Rebecca Yarros 5 A Court of Thorns and Roses (1 of 2) [Dramatized Adaptation] : A Court of Thorns and Roses 1 (Court of Thorns and Roses) Sarah J. Maas 6 Iron Flame (1 of 2) [Dramatized Adaptation] : The Empyrean 2 (Empyrean) Rebecca Yarros 8 Iron Flame (2 of 2) [Dramatized Adaptation] : The Empyrean 2 (Empyrean) Rebecca Yarros 10 The Awakening [Dramatized Adaptation] : Zodiac Academy 1 (Zodiac Academy) Susanne Valenti & Caroline Peckham 14 A Court of Thorns and Roses (2 of 2) [Dramatized Adaptation] : A Court of Thorns and Roses 1 (Court of Thorns and Roses) Sarah J. Maas 15 A Court of Mist and Fury (1 of 2) [Dramatized Adaptation] : A Court of Thorns and Roses 2 (Court of Thorns and Roses) Sarah J. Maas 16 All Your Perfects (Unabridged) Colleen Hoover 17 A Court of Silver Flames (Court of Thorns and Roses) Sarah J. Maas 21 A Court of Wings and Ruin (2 of 3) [Dramatized Adaptation] : A Court of Thorns and Roses 3 (Court of Thorns and Roses) Sarah J. Maas 22 A Court of Wings and Ruin (3 of 3) [Dramatized Adaptation] : A Court of Thorns and Roses 3 (Court of Thorns and Roses) Sarah J. Maas 23 A Court of Silver Flames (2 of 2) [Dramatized Adaptation] : A Court of Thorns and Roses 4 (Court of Thorns and Roses) Sarah J. Maas 24 Wild Love: Rose Hill, Book 1 (Unabridged) Elsie Silver 26 A Court of Mist and Fury (2 of 2) [Dramatized Adaptation] : A Court of Thorns and Roses 2 (Court of Thorns and Roses) Sarah J.