Feature Request
-
Feel free to explain here
-
@olivierlambert I would like the ability to rename physical network interfaces for a host inside of XO.
To disconnect an interface (put it in a down state) and rename it instead of having to do it via the CLI.
This would help when trying to join new hosts to a pool that have different interfaces out of the box because the interfaces have to be renamed to be the same across the entire pool.
-
Can you describe more explicitly or compare with xe commands so we can understand exactly?
edit: I think I get it but I want to be sure.
-
This section.
https://xcp-ng.org/docs/networking.html#renaming-nics
If we could go into a host and change the network interface status to disconnected and then click on the "device" name and change the interface - and then change the status to connected, that would make it a lot easier for users to rename interfaces on hosts that do not match the rest of the pool.
In my particular instance, the rest of the servers are using eth4 for the 10gb/s interface but this particular host has that interface as eth2, so it needs to be renamed to eth4 so that this host may be used with the pool without issues.
-
interface-renameis a local script that is not exposed in XAPI, so we can't command it remotely from any client (xe or XO) -
Interesting.
Does XO connect to each of the servers via SSH to be able to manage the stuff via XAPI etc?
Couldn't you integrate a bash script via the SSH connection to do this when someone tries to rename an interface via the XO UI?
Perhaps I can work on one that could just be ran as a standalone for now.
-
No, not at all. There's 0 SSH communication, it all goes via the XAPI. And we want to keep it that way
(in future releases, SSH will be disabled by default) -
@olivierlambert Interesting.
When you say SSH disabled by default, are you talking about XCP-NG not supporting SSH connections out of the box? Or XOA?
-
XCP-ng. The idea is to make it open via a XAPI call when needed (or automatically when XAPI is down).
-
@olivierlambert said in Feature Request:
XCP-ng. The idea is to make it open via a XAPI call when needed (or automatically when XAPI is down).
@guiltykeyboard A bit similar to how VMware ESXi handles SSH server, it has SSH stopped and/or disabled until requested in its web interface.
Unlike possibly VMware ESXi its going to automatically enable and start the SSH server if XAPI is down!
