threefoldtech / tfgrid-sdk-ts

Apache License 2.0

4 stars 8 forks source link

Node Management: Farmer can configure the public bridge #114

Open muhamadazmy opened 2 years ago

muhamadazmy commented 2 years ago

Related to zos

Feature

The idea is for each node the farmer can see the following:

If node is running in a single nic setup, or dual nic setup. In case of a dual nic which nic is used for public IPs and traffic
List of all available node physical devices.
In case of free physical nics available, the farmer can choose which one to use for this specific node.

All those operations are possible over the node RMB api.
The api has 3 new calls that are allowed only for the node farmer.

`zos.network.admin.interfaces`
`zos.network.admin.get_public_nic`
`zos.network.admin.set_public_nic`

Please check the input/output details of the calls above int he Go client implementation.

coesensbert commented 2 years ago

Can this feature be pushed forward? @xmonader @rkhamis

Since the 'previous nic' used for the public bridge is persistent in ZOS, a farmer has no way to change this if it would be required.

https://github.com/threefoldtech/tf_operations/issues/1247

xmonader commented 1 year ago

Is this still needed ? @coesensbert @muhamadazmy

coesensbert commented 1 year ago

Is this still needed ? @coesensbert @muhamadazmy

yes please

alichaddad commented 1 year ago

To get this done we will need to have access to the user's mnemonics to sign the request and with the current integration using polkadot this won't make for the best user experience, since the user will have to do that for each request which doesn't make sense when he is simply checking the node configuration. There was an issue to use the profile manager in dashboard https://github.com/threefoldtech/tfgrid-sdk-ts/issues/470 which should fix this and work can't start here until this is done.

muhamadazmy commented 1 year ago

Actually I am not sure if we need this anymore. While the farmer can still actually set the exit interface of the node, we don't persist this on the node anymore. The persistence of which exit interface is used caused other issues, instead the farmer has to have his network well configured for ipv6 and let zos auto-detection take place.

We still can show which setup the node has, similar to what we show on zos console. But over the web ? and may be only if you click a button because this required an rmb call to the node to query the current node setup.

So basically same as above BUT with no ability to set it up

xmonader commented 1 year ago

Have to push that to next, with the current prios it won't be done in 3.11