[TASK] View and Manage Pending Instances [Operators]

[monaiuu]

Description

Implement a table to enable Operators to view and mange pending instance requests. Once operators have registered for Blueprints and signaled their availability to provide services, instance requests from deployers will enter a pending state. Operators must review these pending instances to decide whether to approve or reject the deployment request.

Instance Request Overview:

Operators can view all pending instances under the "Pending" tab, which displays a list of deployment requests, including:

• Blueprint/Instance Name: The name of the Blueprint and instance being requested (e.g., "DFNS-CGGMP21, INST-001").
• Price: The cost per unit associated with the instance (e.g., $/unit), determined by the operator's global resource pricing.
• Deployer: Display address and identity of the deployer.
• Duration: The estimated time for which the service will be active or the length of the requested service period.

Approval/Rejection Mechanism:

Operators must decide whether to approve or reject each instance request. This decision is typically based on:

• Pricing: Operators will review if the set pricing aligns with the deployer’s request.
• Resource Availability: Operators need to ensure they have sufficient resources (e.g., CPU, memory, bandwidth) to run the requested service instance.

Screenshots

Figma Link