❓ How to choose default target network for mappings

[yaacov]

Issue:
when creating a new network mapping we default the target network to pod network.

It may be nicer to have some better heuristic to guess a NAD that is preferred for virtualization so the user will not need to manually change to pod network to the preferred one.

[yaacov]

cc:// @ahadas @liranr23 @rszwajko

[yaacov]

Update:

Corrent dev is done with the assumption of using "Pod netwok"
Ref:
#801 (comment)

cc:// @ahadas

[liranr23]

i don't see a good way to tell: this is going to be the network we are going to use for our virtualization. i think making wrong network is dangerous. therefore, i do think "Pod network" or any other network that set as a default (like storage, if there is an annotation for it).

[yaacov]

move to next, currently we use pod network, we may change that based on user feedback

[ahadas]

move to next, currently we use pod network, we may change that based on user feedback

I think we can already say that we use the pod network as a temporary solution, which may be alright for VMs with a single network. Imagine you have a VM with multiple networks - it's not that great to map all networks to the pod network.. as a user I would expect to be told that I should change the mappings if I don't expect all the interfaces to be on the same network on the destination (e.g., "this VM was configured with multiple networks and would have a single network on the destination". btw, are we going to show a message to the user about this implicit networks mapping?)

maybe we tackle this from an incorrect angle - the idea is to simplify the creation of the plan, assuming that selecting existing mappings, and then obviously creating new mappings, makes the process more complex than it should, right? in that case, maybe we should rather have the notion of "default" mappings, mappings that are set for source and destination providers and are selected by default when creating a plan with these providers?

[yaacov]

maybe we should rather have the notion of "default" mappings, mappings that are set for source and destination providers and are selected by default when creating a plan with these providers?

makes sense to me 👍

a. it will be the responsibility of a user ( sys admin, or self serve user ) to create this one time "default X to Y mappings"
b. once a "from X to Y default mapping" exist, it will be the default mapping suggested to the user in the fast create instead of using "all" to "pod net" and "all" to "default storage"

[yaacov]

addressed by #801