zos4 New service to register nodes instead of tfchain

[ashraffouda]

Create a golang service to act as a registrar of the nodes of zos4 where it supports the following

• Create a farm
• List farms
• Get a farm
• Update a farm
• Register a node
• list all nodes
• get a node
• store uptime report
• store consumption report
• Store hardware info (DMI data)

Note: we need to create a standalone service that handles all of this away from using tfchain/substrate
let's have an interface implementing this so we can plug other implementations of this service in the future in zos

[xmonader]

Eta: 14th of Jan

[Eslam-Nawara]

Remaining work

• add account struct and update how to sign
• update how registrar handle uptime report
• add (Interfaces, SecureBoot, Virtualized, BoardSerial, ConnectionPrice) to the node struct
• add endpoint to update the node
• add endpoint to get zos version
• update uptime endpoint to return hash (what is hash?) - same for consumption report
• update create node/farm to return the ID of the created struct
• update how we handle the auth

[sameh-farouk]

Update:
I have started implementing the remaining work needed for the registration flow.
I have completed the account structure addition and handlers for creating and getting accounts.
Now, users can create accounts with a public key, which generates a TwinID.
Security aspects include:

• Using ED25519 signatures for account creation to prove ownership of the private key.
• Timestamp-based challenges to prevent replay attacks.

[sameh-farouk]

Update:
I have completed the update on how the registrar handles uptime reports, supporting the tracking of historical reports to calculate availability.

[sameh-farouk]

Update:

I have completed the implementation of middleware to manage authentication in the registrar. I made several code adjustments and fixed a few bugs. Additionally, I added authorization checks in the handlers to complement the authentication middleware.

I conducted initial tests for the following processes:

• Creating an account providing proper challenge
• Creating a farm with twin authentication
• Registering a node in that farm with twin authentication

Remaining tasks:

• Add an endpoint to update a node
• Add an endpoint to get an account by public key
• Manage zOS version

Estimated time for predefined work
2 Hours (By the end of the day)

[sameh-farouk]

Update:
All communicated work completed
I have completed the implementation of the update node endpoint, adjusted the code to support querying the account by either public key or twin_id, and added relevant flags and endpoints to allow a configurable admin to set the zOS version.

I'm waiting for the integration results so that I can make any necessary changes if needed.