wiki: sync 2026-07-29 12:44 UTC — 1 file(s) updated

2026-07-29 12:44:10 +00:00
parent 79b0e597a2
commit 735350c33e
1 changed files with 67 additions and 0 deletions
@@ -20,6 +20,73 @@
 | ACT-12 | AWS Identity architecture: all VSSA users needing AWS Orgs access → records in main VSSA tenant IDC + federation to member accounts | 🔵 Active | 2026-07-15 |
 | ACT-13 | Release 0.1.0.0 → testing results — GCP start feeling | 🔵 Active | 2026-07-24 |
 | ACT-14 | Organize scanning of AWS organization — spun up using DPVP, then scanned by Atea | 🔵 Active | 2026-07-27 |
+| ACT-15 | DPVP Platform Phase 2 opportunity — scope, prioritise, estimate, and define delivery/commercial approach | 🟡 Opportunity | 2026-07-29 |
+
+## DPVP Platform — Phase 2 Opportunity
+
+### Executive Summary
+
+DPVP Phase 2 is an opportunity to expand the platform across four areas: the operator portal, backend execution, VSSA on-premises onboarding, and complex hybrid services.
+
+The proposed scope below contains only the capabilities currently identified for discussion.
+
+### 1. DPVP Portal
+
+Provide a workspace through which VSSA operators and clients can access and use DPVP services.
+
+#### Operator-guided services
+
+- Guided organisation creation, update, and deletion.
+- Guided project creation, update, and deletion.
+
+#### Service-request processing
+
+- Combine multiple Jira requests into a single DPVP service for processing.
+
+#### Cloud estate visibility
+
+- Provide a close-to-real-time view of the organisation farm within the cloud.
+
+#### Global configuration
+
+- Manage configuration across organisations.
+- Manage Terraform template versions.
+- Manage default tags.
+
+#### Client access and workspace
+
+- Allow VSSA clients to self-register or use their own login method.
+- Provide each client with a workspace.
+- Allow clients to receive cloud-service credentials through HashiCorp tooling.
+
+### 2. DPVP Backend
+
+Move the execution currently implemented in GitLab pipelines to another technology, with the target approach to be evaluated between:
+
+- a web server; or
+- cloud functions.
+
+### 3. VSSA On-Premises Data-Centre Onboarding
+
+Introduce DPVP support for onboarding a VSSA on-premises data centre.
+
+### 4. Complex Services
+
+Introduce complex DPVP services covering:
+
+- backup for on-premises workloads and systems;
+- web-application deployment on Kubernetes;
+- cloud-based disaster recovery; and
+- a cloud observability toolkit connected to on-premises environments.
+
+### Opportunity Qualification — Open
+
+- [ ] Confirm opportunity owner and Atea/VSSA stakeholders.
+- [ ] Prioritise capabilities and define Phase 2 boundaries.
+- [ ] Run technical discovery and produce estimates.
+- [ ] Define dependencies, acceptance criteria, and target dates.
+- [ ] Select/evaluate backend execution approach: web server or cloud functions.
+- [ ] Define the delivery and commercial/procurement approach.

 ## Completed