This message was deleted.
# elemental
a
This message was deleted.
m
Hey Mike πŸ‘‹ ,
well, so you need to set different labels on the MachineInventory resources associated to workers and the ones associated to "controllers"
you can have different ISO, i.e., different registrations where you add a label
or you can just add the labels manually once the MachineInventories are created
if the HW is different, you can just have one single registration/ISO, using a label based on hw data
q
yes i did read about this. when i think about automation i would just spin up another vm in vsphere. so the best solution would be that the the decision about which cluster to join and what kind of node it will be is a separate register endpoint?
m
that would be the most straightforward... but with HW labels (or SMBIOS data) you can have one registration with a label templated on some HW / SMBIOS info... the you create the VM with that specific HW / SMBIOS resource value
q
vsphere sets different hardware labels for a vm but i found nothing about the vm name.
Copy code
labels:
    element: fire
    machineUUID: 82151542-7d77-2e4e-4093-2fe93df65fc0
    manufacturer: VMware-Inc
    productName: VMware7-1
    serialNumber: VMware-42-15-15-82-77-7d-4e-2e-40-93-2
  name: m-a21bb85b-708d-45cf-91f1-8c530ce25aa6
m
Well, I don't know which values can be read from SMBIOS from VMware. Nor which HW assignments can be the most useful for that... anyway, for example, if you change the CPU model of VMs you can use that (or a different amount of RAM, or. ... full list here: https://elemental.docs.rancher.com/hardwarelabels)
Then you match the "HWlabel" to whatever you set there
q
it seems its all about dmidecode
m
smbios is about dmidecode. The HW labels goes beyond that
if there is something else may be worth to track, even just for VMware scenario, well, could be interesting
q
then i will check if i can set smbios values when i create a vm. that would work then
m
yep, that would work well
if there is something that could be get when booting from linux, we can open a feature request
the code is fairly easily extensible to add more "HW" data
(e.g., we have just added the transient hostname in the dev version, not released yet)
q
the one which will be changed by elemental installer?
m
exactly
because the new feature that is coming is to keep hostname assigned by DHCP server
(by default the m-${UUID} will stay there, but there will be an option to keep the hostname assigned by DHCP server... which will also be used for the MachineInventory name)
q
sounds good πŸ™‚
m
Was a feature we have been asked few times... and eventually we are adding it πŸ™‚
will need newer operator and base elemental images... next release likely
since vmware is a pretty common use case, if you find values that we could retrieve from the linux inside the booted VM, please share
q
ok
πŸ‘ 1
for the record: I did not find a way to add another field to smbios information which is then printed out using
dmidecode
but i could use an existing one and change it. You can add "Configuration Parameters" to a VM and use
smBIOS.assetTag = "worker"
for example.
πŸ‘ 1