Projects page

[AhmedHanafy725]

The idea is to group the contracts that are related to each other in a project that has the total billing rate of three contracts, a delete button, and so on...

Suggestion

Approach 1

add a new field on the contract's metadata to point to the related workloads.

• vms -> add network_name
• k8s -> add network_name
• gateways -> add vm_name

Approach 2

Update the projectName (used in the gridClient as a namespace) to have the solution's type and the instance's name. For example: if we have the solution's type taiga and the instance's name is test, the projectName should be taiga_test.

• This will guarantee that each instance has its own namespace and the contracts are grouped together.
• But the listing in the solution's page will need to be changed to group the namespaces that start with the same key instead of the full key of the namespace.

Remarks

• When deleting a project, we should check the dependencies, and if the workload is used by other workloads, we shouldn't allow the deletion or we can delete with warnings.
• Both approaches need to migrate the listing from the kvstore to use contracts' metadata to not do the migration twice.

Related issues

• 1055

• 23

[MohamedElmdary]

applied the new path on machines but an error happen while deploying k8s working on fixing it

[MohamedElmdary]

Read but blocked until merging https://github.com/threefoldtech/tfgrid-sdk-ts/pull/1215