You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently elemental-register supports a multitude of arguments that can be used all together, even though they may be mutually exclusive. This makes the code a bit harder to maintain, and harder to extend as well with new functionality.
Note that backward compatibility should be granted when running elemental-register root command.
Subcommands:
version Displays the version
register Registers this machine, if --install is used, installation will take place automatically after registration.
install Installs the OS on this machine.
reset Resets the machine. If --network-only is used, it will only reset the network (consider alternative network reset subcommand)
verify (NEW!) performs a simple verification (fetch the remote registration? also machineinventory authentication?) that can be used for boot assessment
I also propose to drop all other arguments that can be retrieved from the configuration file/remote registration, like emulate-tpm, no-smbios, ca-cert, auth, and so on). --config should be enough as a global argument
--state is nice to have to be able to point to a state file without having to expose that in the MachineRegistration API, but I would also think about making the elemental-register stateless again. This can be simply achieved by dropping any emulated-tpm support, which will also improve maintenance and reduce complexity. We have alternative auth methods that can be equally used for non-production/demo purposes already.
The text was updated successfully, but these errors were encountered:
fgiudici
added a commit
to fgiudici/elemental-operator
that referenced
this issue
Sep 5, 2024
'dumpdata' allows to inspect host data from the running host as they are
collected during the registration phase: those are the data made
available in the Elemental Label Templates feature.
This subcommand was developed while working at rancher#834 and since could be
handy for debugging and even for users (elemental sysadmins) adding it
to the elemental-register binary.
'version' is the very first step in moving the elemental-register flags
to command, as requested by rancher#832.
Related to issues: rancher#832, rancher#834
Signed-off-by: Francesco Giudici <[email protected]>
'dumpdata' allows to inspect host data from the running host as they are
collected during the registration phase: those are the data made
available in the Elemental Label Templates feature.
This subcommand was developed while working at #834 and since could be
handy for debugging and even for users (elemental sysadmins) adding it
to the elemental-register binary.
'version' is the very first step in moving the elemental-register flags
to command, as requested by #832.
Related to issues: #832, #834
Signed-off-by: Francesco Giudici <[email protected]>
Currently
elemental-register
supports a multitude of arguments that can be used all together, even though they may be mutually exclusive. This makes the code a bit harder to maintain, and harder to extend as well with new functionality.It would be best to split into subcommands.
Global args:
--config
,--state
,--debug
Note that backward compatibility should be granted when running
elemental-register
root command.Subcommands:
version
Displays the versionregister
Registers this machine, if--install
is used, installation will take place automatically after registration.install
Installs the OS on this machine.reset
Resets the machine. If--network-only
is used, it will only reset the network (consider alternativenetwork reset
subcommand)verify
(NEW!) performs a simple verification (fetch the remote registration? also machineinventory authentication?) that can be used for boot assessmentI also propose to drop all other arguments that can be retrieved from the configuration file/remote registration, like
emulate-tpm
,no-smbios
,ca-cert
,auth
, and so on).--config
should be enough as a global argument--state
is nice to have to be able to point to a state file without having to expose that in the MachineRegistration API, but I would also think about making theelemental-register
stateless again. This can be simply achieved by dropping anyemulated-tpm
support, which will also improve maintenance and reduce complexity. We have alternative auth methods that can be equally used for non-production/demo purposes already.The text was updated successfully, but these errors were encountered: