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
Which package/s are you suggesting this feature for?
Dashboard, grid_client
Is your feature request related to a problem? Please describe
There are now 2 different zos on the nodes (zos3, zos4), so the dashboard and grid client should identify the node zos version and use the corresponding workloads to deploy on them.
zos4 currently doesn't support wireguad, yggdrasil, or public ips. so it will require these filters from the grid proxy to be supported threefoldtech/tfgrid-sdk-go#1209
Which package/s are you suggesting this feature for?
Dashboard, grid_client
Is your feature request related to a problem? Please describe
There are now 2 different zos on the nodes (zos3, zos4), so the dashboard and grid client should identify the node zos version and use the corresponding workloads to deploy on them.
zos4 currently doesn't support
wireguad
,yggdrasil
, orpublic ips
. so it will require these filters from the grid proxy to be supported threefoldtech/tfgrid-sdk-go#1209Describe the solution you'd like
2 new workloads should be added
Before starting the deployment, the grid client should check the node version and decide which workloads to be used to deploy the vm and network.
Adjust the automatic and manual filters to respect the newly added queries on the gridproxy to suggest valid nodes for deployment.
The text was updated successfully, but these errors were encountered: