Home
The Virtual Regional Office (VRO) platform is a Platform as a Service (PaaS) offering, hosted on the VA's Lighthouse Delivery Infrastructure (LHDI) platform. It is managed and maintained by the VA's OCTO Benefits Crew. Initially, the project had a very different objective when it was formed for the Rapid Ready Decisions (RRD) project. However, the original idea was re-evaluated, leading to the creation of the new vision for the VRO platform.
"The VRO platform provides teams with access to shared knowledge, processes, and tools, enabling them to quickly build and validate ideas that improve the VA's internal claims process".
As a platform team, our success is measured by the time-to-value for our partners—the product teams developing and iterating on applications within VRO. At its core, VRO is an ecosystem of services hosted on AWS Managed Kubernetes clusters offered by LHDI. Please refer to our architectural diagram below for a technical overview
cATO: VRO maintains the continuous Authority to Operate (cATO), so our partner teams do not need to obtain one themselves, significantly reducing the time to market for new applications. Build on us and cut the line!
Standardized Deployment Processes: VRO solves the problem of fragmented deployment practices by providing a standardized process for continuous integration (CI) tests and deployments, ensuring consistency and efficiency.
Intermediary Flexibility: VRO acts as a bridge between LHDI and their services, so our partner teams do not have to handle these complexities themselves.
Managed Data Services: VRO owns and manages the shared data services offered on their platform, taking the responsibility off their partner teams.
DevOps Management: VRO handles all the DevOps responsibilities for the overall platform, allowing partner teams to focus on building and improving their applications.
BIP Claims API
BEP Development Notes Service
BIE Contention Events
(See below for more detailed information on services)
-
Virtual Regional Office (VRO) Overview for Partner Teams
-
2024 Roadmap and VRO Priorities
Archived Priorities
- VRO v1 Roadmap
Active efforts
VRO priorities
BIE Kafka Client
[BIE Contention Events User Guide](./BIE-Contention-Events-User-Guide)
[VA.gov Data Visibility Initiative](./VA.gov-Data-Visibility-Initiative)
Problem Overview
Diagrams:
Postgres and persistent data Entity Relationship Diagram (ERD)
RabbitMQ and AMQP Design:
- Advanced Message Queuing Architecture
- Microservice Communication
- RabbitMQ Microservice reliability
- RabbitMQ Publishing Messages in LHDI
- Microservice Communication
VRO Team Dependency Map and Process Outline - a visual map showing who our contacts are for which services
- Software Conventions
- VRO RabbitMQ Strategy
- Code structure
- Microservice Communication
- Development Process
- Culture and Norms
- VRO Engineering Team Members
- Code structure
- Configuration settings
- Software Conventions
- Team Processes
- Change Management Plan
- Pull Requests
Docker Compose Docker containers Kubernetes Liveness and Readiness Probes Lightkeeper tool Helm Charts Deploying VRO
- VA API Authorization - Mutual TLS
- BIP APIs
- BEP Services (formerly BIS) ((formerly BGS)) User Guide
- BIE Services
- VRO priorities
- VA.gov Data Visibility Initiative
- API Documentation
- Data Visibility
- Data Visibility MVP Tech spec
- VA.gov Data Visibility Initiative
- LHDI's Boilerplate Instructions
- API Gateway
- Lightkeeper tool
- Gradle
- GitHub Actions
- DataDog monitoring
- Dependabot
- Hashicorp Vault
- New Domain Setup
- Partner Team Quick Deployment Guide
- Partner Team Incident Reports
- Domain Applications in VRO
- Contention Classification
- Updating Contention Classification DC Lookup Table 📋
- VRO Partner Team Database Migrations
- Employee Experience
Local Setup Setup on Windows Terminal to LHDI Ubuntu VM Setup Troubleshooting Local Environment
- Escalation History
- New Domain Setup
- [Machine User Account](./Machine User Account)
- Updating Contention Classification DC Lookup Table
- Update vets api parameters for VRO