Understanding and implementing these fields correctly for the chosen back-end power driver is the user’s responsibility. Nevertheless, the power driver you’re connecting to Webhook may actually require a username and/or password. For example, Webhook doesn’t require a username or password for the power driver, because not all power drivers work that way. It’s important to understand that the Webhook power driver is more generic than other drivers, so it has some flexibility that the underlying power driver may not support. You should change this hostname to something descriptive, that helps you remember why this machine is in your MAAS network. ![]() The machine’s hostname – according to MAAS – is a randomly chosen string (here dear.ant). Note that most of the multiple-choice fields have drop-down menus to assist with your choice. The following catalogue helps to explain the fields in the “create machine” dialogue above. If you see this error, double-check your entered values by editing the power type, or consider another power type altogether.Īnother possible cause for this error may be the networking: traffic may be getting filtered between the rack controller and the BMC card. A successful power check is a good indication that MAAS can properly communicate with the machine, that is, it should quickly result in a power status of “Power off”. Once that’s done, MAAS performs a power check on the machine. Redfish is preferred if the machine supports both Redfish and IPMI.Ĭlick ‘Save changes’ to finish. Redfish can be detected and configured only if the BMC has a Redfish Host Interface enabled and exposed to the host. With the release of 3.2, if the machine uses either IPMI or Redfish for its BMC, the ephemeral environment will automatically detect it, create a separate user for MAAS and configure the machine, so that MAAS may check and control the machine’s power status. Prior to MAAS 3.2, all such BMC connections were made via IPMI. A script inside that environment registers the machine in MAAS. The machine boots into an ephemeral environment to gather information about the machine. It provides additional features above and beyond those provided by IPMI eventually, Redfish should supplant IPMI as the default BMC interface.Ī machine that isn’t registered in MAAS – but connected to the MAAS PXE network – can be powered on manually and made to network boot. Redfish is an alternative to the IPMI protocol ↗ for connecting with machine BMCs. MAAS 3.2 adds the capability to auto-detect Redfish and prefer it as the BMC protocol, if it’s present and enabled. MAAS has already supported Redfish for some time. That host interface can be accessed by the MAAS host.The BMC has a Redfish Host Interface enabled.MAAS 3.2 enhances support for Redfish as a BMC protocol by preferring Redfish over IPMI, provided that: If auto-detection fails MAAS will fall back to using freeipmi-tool default, 3, which is what previous versions of MAAS use. ![]() MAAS tries to find the most secure cipher suite available. When using IPMI, MAAS will attempt to automatically detect the correct cipher suite.
0 Comments
Leave a Reply. |