canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.87k stars 856 forks source link

Enlistment does not do BMC discovery #2287

Closed ubuntu-server-builder closed 1 year ago

ubuntu-server-builder commented 1 year ago

This bug was originally filed in Launchpad as LP: #1042004

Launchpad details
affected_projects = ['maas']
assignee = None
assignee_name = None
date_closed = 2012-10-09T21:21:48.023026+00:00
date_created = 2012-08-27T01:50:08.212705+00:00
date_fix_committed = None
date_fix_released = None
id = 1042004
importance = undecided
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1042004
milestone = None
owner = julian-edwards
owner_name = Julian Edwards
private = False
status = invalid
submitter = julian-edwards
submitter_name = Julian Edwards
tags = []
duplicates = [1059074]

Launchpad user Julian Edwards(julian-edwards) wrote on 2012-08-27T01:50:08.212705+00:00

Without BMC discovery, power parameters have to be entered manually. This can be difficult when the BMC uses DHCP itself.

ubuntu-server-builder commented 1 year ago

Launchpad user Julian Edwards(julian-edwards) wrote on 2012-10-01T02:56:51.193799+00:00

Details capture from duplicate bug:

When a machine is declared to MAAS by booting ephemerally off PXE it should capture BMC information with:

sudo bmc-config --checkout

This provides a file like the attached, which can be parsed to gather IPMI details (ip address for the BMC specifically, but also details of user configuration and network config). The critical section looks like this:

ubuntu@node-0025904cbfb0:~$ sudo bmc-config --checkout --section Lan_Conf #

Section Lan_Conf Comments

#

In the Lan_Conf section, typical networking configuration is setup. Most users

will choose to set "Static" for the "IP_Address_Source" and set the

appropriate "IP_Address", "MAC_Address", "Subnet_Mask", etc. for the machine.

# Section Lan_Conf

Possible values: Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others

IP_Address_Source Use_DHCP

Give valid IP address

IP_Address 192.168.9.12

Give valid MAC address

MAC_Address 00:25:90:4B:AA:8A

Give valid Subnet Mask

Subnet_Mask 255.255.255.0

Give valid IP address

Default_Gateway_IP_Address 192.168.9.1

Give valid MAC address

Default_Gateway_MAC_Address 00:00:00:00:00:00

Give valid IP address

Backup_Gateway_IP_Address 0.0.0.0

Give valid MAC address

Backup_Gateway_MAC_Address 00:00:00:00:00:00

Give valid unsigned number

Vlan_id 0

Possible values: Yes/No

Vlan_Id_Enable No

Give valid unsigned number

Vlan_Priority 0 EndSection

ubuntu-server-builder commented 1 year ago

Launchpad user Julian Edwards(julian-edwards) wrote on 2012-10-01T02:57:28.319912+00:00

See also https://bugs.launchpad.net/maas/+bug/1059074/+attachment/3358361/+files/bmc-config.example.txt for example bmc-config output

ubuntu-server-builder commented 1 year ago

Launchpad user Mark Shuttleworth(sabdfl) wrote on 2012-10-09T14:09:28+00:00

\o/ thank you, looking forward to testing it. So this is a straight pxe-boot enlist and it should Just Work (tm)?

ubuntu-server-builder commented 1 year ago

Launchpad user Andres Rodriguez(andreserl) wrote on 2012-10-09T19:07:16.479785+00:00

Howdy.

Enlistment doesn't yet do BMC discovery,Commissioning does. However, the API now accepts power parameters which allow us sending the information back to MAAS during enlistment. Marking this bug as 'In Progress' as it is currently in progress.

Cheers.