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 the process of adding a Hypervisor is to SSH into it and then scan for the VMs/LXCs/etc. XPipe will display the SSH connection menu on top
The nesting makes sense in terms of the Hypervisor being a host that can run docker/other stuff like other hosts on itself but a Hypervisor is mostly used as virtualization platform to jump into VMs.
As an option maybe there should be a way for adding Hypervisors as top level during connection setup, for example a dedicated option in the Add Connection screen where you can select the connection as Hypervisor of your choice.
With this setup you would have the Hypervisor as top level connection and in the dropdown menu/second level all the VMs/LXCs
A current "workaround" is to make a new category and move the Hypervisor connection into it.
The text was updated successfully, but these errors were encountered:
Currently the process of adding a Hypervisor is to SSH into it and then scan for the VMs/LXCs/etc. XPipe will display the SSH connection menu on top
The nesting makes sense in terms of the Hypervisor being a host that can run docker/other stuff like other hosts on itself but a Hypervisor is mostly used as virtualization platform to jump into VMs.
As an option maybe there should be a way for adding Hypervisors as top level during connection setup, for example a dedicated option in the Add Connection screen where you can select the connection as Hypervisor of your choice.
With this setup you would have the Hypervisor as top level connection and in the dropdown menu/second level all the VMs/LXCs
A current "workaround" is to make a new category and move the Hypervisor connection into it.
The text was updated successfully, but these errors were encountered: