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
{{ message }}
This repository has been archived by the owner on Apr 27, 2022. It is now read-only.
Allowing a server to manage virtual nodes and networks will allow HaaS developers to test their code without needing actual machines and switches. There is work needed to allow managing virtual nodes. For networks, the null driver will allow networks to be created and attached without needing a physical switch.
Implementing virtual nodes and documenting how to use them as well as the null network driver in the developer documentation will help our devs.
Nodes
Creating virtual nodes (ie - HaaS nodes that are not backed by physical nodes) will require adding a configuration primitive as well as updating any operation that touches physical nodes, which include the various IPMI proxy functions (system reset, getting the serial console).
Headnodes
This will also require modifying the headnode code not to do any actual creation or attaching of VMs.
Networks
From what I understand, the null driver can currently be used for this type of functionality. It would be nicer if it kept and verified state, though this could be done later. The main task to do for networks would be to document use of the null driver. If we are supporting multiple 802.1q tagged VLANs on a single switch port, then we will likely want to reuse the VLAN driver.
The text was updated successfully, but these errors were encountered:
From the development point of view this is still relevant, but on the other hand I don't want to spend time only on stuff that will be used for further development. Maybe I am wrong, but there are other more relevant/useful things we could do to the hil codebase before coming to this. This applies to #908 too.
@SahilTikale has been working on an openVswitch driver, and has plans to work on an obm driver that would basically make libvirt calls to VMs.
So I don't want simply close this, but rather come back to it later.
Re: obm driver, that should go in obmd, now that we're planning on moving the obm drivers there in general. @SahilTikale, take note; wouldn't want you to waste the effort.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Allowing a server to manage virtual nodes and networks will allow HaaS developers to test their code without needing actual machines and switches. There is work needed to allow managing virtual nodes. For networks, the null driver will allow networks to be created and attached without needing a physical switch.
Implementing virtual nodes and documenting how to use them as well as the null network driver in the developer documentation will help our devs.
Nodes
Creating virtual nodes (ie - HaaS nodes that are not backed by physical nodes) will require adding a configuration primitive as well as updating any operation that touches physical nodes, which include the various IPMI proxy functions (system reset, getting the serial console).
Headnodes
This will also require modifying the headnode code not to do any actual creation or attaching of VMs.
Networks
From what I understand, the null driver can currently be used for this type of functionality. It would be nicer if it kept and verified state, though this could be done later. The main task to do for networks would be to document use of the null driver. If we are supporting multiple 802.1q tagged VLANs on a single switch port, then we will likely want to reuse the VLAN driver.
The text was updated successfully, but these errors were encountered: