The file's text, extracted by GovTribe without its formatting.
ATTACHMENT B
Hyperconverged Infrastructure (HCI) Vendor and S3 Object Storage PROFESSIONAL SERVICES REQUIREMENTS
Infrastructure and S3 Object Storage Configuration for:
Abacus Visual Playbook Builder and Automation Orchestrator
Department of Veterans Affairs Veterans Health Administration (VHA) Veterans Integrated Service Network 23 (VISN 23) Healthcare Technology Management / Biomedical Engineering
Project Context The HCI Vendor provides the hyperconverged infrastructure for the Abacus platform. This includes:
| Hardware |
| HCI nodes (racked, cabled, powered) |
| Cluster |
| HCI Cluster Manager with storage |
| Management |
| Dedicated HCI Management Console instance |
| Storage |
| S3-compatible Object Storage for automation assets |
Three systems interact with HCI and S3 infrastructure:
| Red Hat OpenShift |
| Runs on AAP approved/validated HCI cluster |
| Abacus |
| Uploads automation assets to S3 bucket |
| AAP (Ansible Automation Platform) |
| Generates presigned URLs for asset downloads; may also execute VM provisioning workflows if Contractor selects AAP-based approach |
| Windows Workstations |
| Download assets via presigned URLs |
| VM Provisioning Component | |
| Provisions VMs on existing VISN 23 Nutanix infrastructure (implementation at Contractor discretion per L14) | Comment by Minetti, Christopher: Not to beat a dead horse, but other brands can do this right? |
HCI Vendor’s role is infrastructure provider only. Application logic is handled by other parties.
Architecture Overview The following diagram illustrates the HCI infrastructure stack:
HYPERCONVERGED INFRASTRUCTURE (HCI) STACK
HCI Management Console (Dedicated) FQDN: hci.abacus.<domain>.com (TLS, internal CA-signed) Purpose: Centralized HCI management for Abacus cluster and hosts OpenShift + Abacus
| Manages v
HCI Cluster ManagerCluster (Abacus Cluster) Nodes: [Quantity TBD based on sizing] Purpose: Hyperconverged infrastructure for OpenShift + Abacus Storage: Containers configured for OpenShift CSI
| Hosts v
S3-Compatible Storage – S3 Store: "abacus-S3-store" FQDN: S3.abacus.<domain>.com (TLS, internal CA-signed) Bucket: abacus-playbook-assets Purpose: Automation assets (installers, config files) Structure: assets/{card-uuid}.zip, assets/{card-uuid}.manifest Versioning: Enabled
Data Flow:
Abacus Ingress ---- Writes ----> Bucket AAP ---- Generates presigned URLs ----> Windows Workstations download
Hardware Procurement and Installation Hardware Procurement
| ID |
| Requirement |
| What It Enables |
| NX-HW1 |
| Government shall fund procurement of hyperconverged infrastructure hardware through this contract |
| Capital expense covered by Government; hardware is contract deliverable |
| NX-HW2 |
| Contractor shall coordinate hardware ordering with HCI Vendor, including Bill of Materials validation and delivery logistics |
| Single point of coordination; Government not burdened with vendor logistics |
| NX-HW3 |
| Hardware specifications shall be sized to support OpenShift Container Platform and Abacus workloads as defined in Category AF (Scale and Concurrency) |
| Right-sized infrastructure; avoids over-provisioning or capacity constraints |
| NX-HW4 |
| Hardware shall be delivered to Government datacenter by Month 3 milestone per contract schedule |
| Aligns with AE3; allows time for installation before Month 5 cluster online milestone |
Physical Installation
| ID |
| Requirement |
| What It Enables |
| NX-HW5 |
| HCI Vendor Professional Services shall perform physical rack installation of all hardware components |
| Validated installation by certified personnel; preserves hardware warranty and support eligibility |
| NX-HW6 |
| Physical installation includes: unboxing, rack mounting, cabling (power and network), and initial power-on verification |
| Complete physical deployment; hardware ready for HCI cluster creation |
| NX-HW7 |
| HCI Vendor shall coordinate installation schedule with Government datacenter operations |
| Minimizes disruption; ensures datacenter staff availability for access and escorts |
| NX-HW8 |
| HCI Vendor shall provide installation documentation including rack elevation diagrams, cable labeling scheme, and as-built network port assignments |
| Government maintains accurate datacenter records; supports future maintenance |
Government Network Preparation
| ID |
| Requirement |
| What It Enables |
| NX-HW9 |
| Government shall ensure top-of-rack (ToR) switches are installed, configured, and ready to accept HCI node connections prior to physical installation date |
| Network infrastructure prerequisite; HCI Vendor cannot complete installation without network readiness |
| NX-HW10 |
| Government shall provide VLAN assignments, IP address allocations, and gateway information for HCI management network, storage network, and VM networks |
| Network configuration inputs required for Foundation process |
| NX-HW11 |
| Government shall ensure sufficient rack space, power capacity, and cooling for HCI hardware prior to delivery |
| Physical infrastructure prerequisites |
HCI Cluster Manager Configuration HCI Cluster Manager Formation
| ID |
| Requirement |
| What It Enables |
| NX-PE1 |
| HCI Vendor Professional Services shall perform cluster initialization process to initialize all nodes and form a single HCI cluster |
| Transforms bare hardware into operational hyperconverged cluster |
| NX-PE2 |
| Cluster initialization process includes: imaging nodes with HCI Node Operating System, configuring storage controller, network settings, and cluster creation |
| Complete software initialization; cluster ready for workloads |
| NX-PE3 |
| Cluster shall be named according to Government naming convention (name to be provided during implementation) |
| Consistent naming; aligns with Government IT asset management |
| NX-PE4 |
| HCI Cluster Manager shall be configured with redundancy factor appropriate for node count |
| Data protection; cluster survives node failures |
| NX-PE5 |
| HCI Vendor shall configure storage containers for OpenShift workloads per Red Hat OpenShift on HCI validated design |
| Storage ready for OpenShift CSI integration |
HCI Cluster Manager Access Configuration
| ID |
| Requirement |
| What It Enables |
| NX-PE6 |
| HCI Cluster Manager web console shall be accessible via HTTPS on Government-provided FQDN |
| Secure management access; human-readable URL |
| NX-PE7 |
| TLS certificate for HCI Cluster Manager shall be provided by Government (internal CA-signed) and applied by HCI Vendor during configuration |
| Secure access without browser warnings; aligns with Government PKI |
| NX-PE8 |
| HCI Vendor shall configure HCI Cluster Manager for Active Directory authentication using Government-provided service account and AD group mappings |
| Centralized identity; role-based access control |
| NX-PE9 |
| HCI Vendor shall document local administrator credentials and deliver securely to Government |
| Break-glass access; disaster recovery capability |
Cluster Validation
| ID |
| Requirement |
| What It Enables |
| NX-PE10 |
| HCI Vendor shall perform cluster health validation and remediate any warnings or failures before handoff |
| Verified healthy cluster; issues resolved before production use |
| NX-PE11 |
| HCI Vendor shall provide cluster configuration documentation including: node inventory, network configuration, storage container layout, and NCC health report |
| Government maintains configuration baseline; supports future troubleshooting |
HCI Management Console Deployment HCI Management Console Installation
| ID |
| Requirement |
| What It Enables |
| NX-PC1 |
| HCI Vendor Professional Services shall deploy a dedicated HCI Management Console instance for Abacus cluster management |
| Centralized multi-cluster management capability; required for S3-Compatible Storage |
| NX-PC2 |
| HCI Management Console shall be deployed on the Abacus HCI Cluster (not shared with other Government HCI environments) |
| Dedicated management plane; isolation from other Government HCI environments |
| NX-PC3 |
| HCI Management Console deployment size shall be appropriate for single-cluster management |
| Right-sized deployment; avoids over-provisioning |
| NX-PC4 |
| HCI Management Console shall be registered with the Abacus HCI Cluster Manager |
| Enables centralized management features |
HCI Management Console Access Configuration
| ID |
| Requirement |
| What It Enables |
| NX-PC5 |
| HCI Management Console web console shall be accessible via HTTPS on Government-provided FQDN (e.g., cluster.abacus.<domain>.com) |
| Secure management access; human-readable URL |
| NX-PC6 |
| TLS certificate for HCI Management Console shall be provided by Government (internal CA-signed) and applied by HCI vendor during configuration |
| Secure access without browser warnings; aligns with Government PKI |
| NX-PC7 |
| HCI Vendor shall configure HCI Management Console for Active Directory authentication using Government-provided service account and AD group mappings |
| Centralized identity; role-based access control |
| NX-PC8 |
| HCI Vendor shall document local administrator credentials and deliver securely to Government |
| Break-glass access; disaster recovery capability |
HCI Management Console Validation
| ID |
| Requirement |
| What It Enables |
| NX-PC9 |
| HCI Vendor shall verify HCI Management Console health and successful cluster registration before proceeding to S3 storage deployment |
| Validated management plane; prerequisite for S3 storage |
| NX-PC10 |
| HCI Management Console shall be operational and accessible by Month 5 milestone |
| Aligns with AE4; enables Objects activation and OpenShift deployment |
Existing Prism Central Configuration The Government operates an existing Prism Central instance that manages the eight (8) physical site Prism Element clusters. AAP requires credentials to this existing Prism Central for VM provisioning via the nutanix.ncp collection. Comment by Minetti, Christopher: Or equivalent?
| ID |
| Requirement |
| What It Enables |
| NX-PC11 |
| HCI Vendor Professional Services shall create eight (8) local user accounts on the Government's existing Prism Central for AAP automation use. Each account shall have RBAC permissions scoped to a single physical site's Prism Element cluster (Fort Meade, Fargo, Sioux Falls, Saint Cloud, Minneapolis, Omaha, Iowa City, Central Iowa). Account naming convention shall be coordinated with the Contractor. |
| Site-scoped VM provisioning credentials for AAP |
| NX-PC12 | |
| HCI Vendor shall generate access credentials for each local user account and deliver them securely to the Contractor. | |
| Contractor can configure AAP with site-scoped Nutanix access | Comment by Minetti, Christopher: Can this be made generic as well? |
| NX-PC13 |
| HCI Vendor shall document the RBAC configuration applied to each account, including which Prism Element cluster each account can access. |
| Government maintains configuration records; supports troubleshooting |
Note: This configuration is performed on the Government's existing Prism Central
S3-Compatible Storage Configuration S3-Compatible Storage Infrastructure
| ID |
| Requirement |
| What It Enables |
| NX-OBJ1 |
| S3-Compatible Storage activated on Abacus cluster |
| S3-compatible storage available for platform use |
| NX-OBJ2 |
| S3-Compatible Storageconfigured with ”right-sized” workers and load balancer configuration |
| Sufficient capacity and redundancy for workload |
| NX-OBJ3 |
| FQDN configured for S3-Compatible Storage endpoint (e.g., s3.abacus.<domain>.com) |
| Human-readable, DNS-resolvable endpoint; enables TLS with proper certificate |
| NX-OBJ4 |
| TLS certificate applied to S3-Compatible Storage endpoint, signed by Government's internal CA, with FQDN in subject/SAN |
| Secure HTTPS access; presigned URLs trusted by target workstations |
| NX-OBJ5 |
| Single DNS A record points to primary load balancer; secondary LB available for manual failover if available |
| Simplified DNS; documented failover path without round-robin complexity |
Bucket Configuration
| ID |
| Requirement |
| What It Enables |
| NX-OBJ6 |
| Bucket created: abacus-playbook-assets |
| Storage for automation assets (installers, config files, manifests) |
| NX-OBJ7 |
| Versioning enabled on abacus-playbook-assets bucket |
| Multiple versions of same asset tracked; supports rollback and audit |
Access Control
| ID |
| Requirement |
| What It Enables |
| NX-OBJ8 |
| All S3 access uses local HCI Vendor users (not Active Directory) |
| Eliminates AD service account password rotation burden; per-bucket isolation |
| NX-OBJ9 |
| Local user abacus-assets-writer created with read/write access to abacus-playbook-assets |
| Abacus Ingress Uploader can store uploaded assets |
| NX-OBJ10 |
| Local user aap-assets-reader created with read-only access to abacus-playbook-assets |
| AAP can generate presigned download URLs without write capability |
| NX-OBJ11 |
| Access/secret keys generated for each local user and delivered securely to appropriate party |
| Each system has credentials scoped to its required access |
Local User Summary:
| User Name |
| Bucket |
| Permissions |
| Credential Recipient |
| abacus-assets-writer |
| abacus-playbook-assets |
| Read + Write |
| Primary Contractor (Abacus) |
| aap-assets-reader |
| abacus-playbook-assets |
| Read only |
| Red Hat (AAP) |
TLS Certificate Requirements Certificate Overview
| Component |
| FQDN Pattern |
| Certificate Purpose |
| HCI Cluster Manager |
| cluster.abacus.<domain>.com |
| Cluster management console |
| HCI Management Console |
| management.abacus.<domain>.com |
| Centralized management console |
| S3-Compatible Storage |
| s3.abacus.<domain>.com |
| S3 API endpoint; presigned URLs |
Certificate Specifications
| Certificate Type |
| X.509, signed by Government's internal CA |
| Key Usage |
| Server authentication |
| Subject/SAN |
| Must include the component's FQDN |
| Validity |
| Per Government certificate policy (typically 1-2 years) |
Certificate Requirements
| ID |
| Requirement |
| What It Enables |
| NX-TLS1 |
| All TLS certificates shall be signed by Government's internal Certificate Authority |
| Certificates trusted by Government systems without external CA dependency |
| NX-TLS2 |
| Certificates shall include FQDN in both Subject Common Name and Subject Alternative Name (SAN) |
| Proper certificate validation by clients |
| NX-TLS3 |
| Government shall provide certificates to HCI Vendor prior to component configuration |
| HCI Vendor can apply certificates during initial setup (not post-hoc) |
| NX-TLS4 |
| HCI Vendor shall apply TLS certificates to HCI Cluster Manager, HCI Management Console, and S3-Compatible Storage |
| Secure HTTPS access to all management interfaces and APIs |
| NX-TLS5 |
| HCI Vendor shall verify certificate installation by confirming HTTPS access without certificate warnings from a Government workstation |
| Validated certificate chain; confirms CA trust is properly configured |
Why FQDN matters for presigned URLs:
AAP generates presigned URLs that embed the hostname. If AAP connects via FQDN, the presigned URLs contain that FQDN. Target workstations trust the internal CA (installed during onboarding), so downloads succeed. Using an IP address or self-signed certificate would cause TLS trust failures on workstations.
Certificate Responsibility Model
| Certificate request and issuance |
| Government PKI Team |
| DNS A record creation |
| Government Network Team |
| Certificate application to HCI components |
| HCI Vendor Professional Services |
| Certificate renewal (post-deployment) |
| Government (HCI Vendor provides guidance) |
License Activation Timing License Deferral Requirements
| ID |
| Requirement |
| What It Enables |
| NX-LIC1 |
| HCI vendor software licenses shall not activate or begin subscription term until successful completion of Final Acceptance milestone (Month 12) |
| Government receives full license term value; development period does not consume production entitlements |
| NX-LIC2 |
| HCI Vendor shall provide evaluation, trial, or development licenses during the period of performance (Months 1-12) at no additional cost to the Government |
| Infrastructure operational for development without consuming production license term |
| NX-LIC3 |
| If evaluation licenses are unavailable for specific HCI vendor components, Contractor shall coordinate with HCI Vendor to propose alternative approach (e.g., deferred invoicing) and obtain Contracting Officer approval |
| Flexibility for edge cases while maintaining Government cost protection |
| NX-LIC4 |
| Contractor shall not invoice Government for HCI vendor production licenses until Final Acceptance is successfully completed |
| Invoice timing aligned with license activation |
| NX-LIC5 |
| HCI Vendor (or Contractor coordinating with HCI Vendor) shall provide license activation schedule documenting: activation date, term length, renewal date, and license quantities for each component |
| Clear record for Government renewal planning |
License Scope
| Component |
| License Type |
| Activation Trigger |
| HCI Node Operating System |
| Per-node |
| Final Acceptance (Month 12) |
| S3-Compatible Storage |
| Capacity-based |
| Final Acceptance (Month 12) |
Note: Exact license SKUs and quantities will be determined during hardware sizing. This section establishes the timing policy, not the specific license inventory.
Integration Points Integration with Red Hat (AAP) Presigned URL Workflow:
AAP Controller --> S3 API: Generate presigned URL --> S3-Compatible Storage API --> Returns: HTTPS URL with signature --> AAP Controller AAP Controller --> URL provided to Windows workstation Windows Workstation --> HTTPS download --> S3-Compatible Storage
HCI Vendor provides to Red Hat:
- S3-Compatible API FQDN
- aap-assets-reader credentials
Red Hat provides to HCI vendor:
- Nothing required
Integration with Primary Contractor (Abacus) Data Flow:
Abacus Ingress Uploader ---- Writes ----> abacus-playbook-assets bucket
HCI Vendor provides to Contractor:
- S3-Compatible API FQDN
- abacus-assets-writer credentials (for Ingress Uploader)
- HCI Management Console API endpoint
Contractor provides to HCI Vendor:
- Nothing required
Integration with Target Workstations Download Flow:
Windows Workstation ---- HTTPS (presigned URL) ----> abacus-playbook-assets
Critical requirement: The S3-Compatible endpoint must use an FQDN with a TLS certificate signed by the internal CA. Workstations will have this CA in their trust store (installed during onboarding via separate Git-based workflow). If the certificate is not trusted, asset downloads will fail.
Day 0 Implementation Checklist Phase 1: Pre-Delivery Preparation
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 1 |
| Confirm datacenter readiness (rack space, power, cooling) |
| Government |
| None |
| Pre-Month 4 |
| 2 |
| Confirm ToR switch readiness and provide network configuration |
| Government |
| None |
| Pre-Month 4 |
| 3 |
| Provide VLAN assignments, IP allocations, gateway info |
| Government |
| None |
| Pre-Month 4 |
| 4 |
| Provide FQDNs for HCI Cluster Manager, Management Console, and S3-Compatible storage |
| Government |
| None |
| Pre-Month 4 |
| 5 |
| Create DNS A records for all FQDNs |
| Government |
| FQDNs defined |
| Pre-Month 5 |
| 6 |
| Issue TLS certificates HCI Cluster Manager, Management Console, and S3-Compatible endpoint |
| Government PKI |
| FQDNs defined |
| Pre-Month 5 |
| 7 |
| Provide AD service account and group mappings |
| Government |
| None |
| Pre-Month 5 |
Phase 2: Hardware Delivery and Installation
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 8 |
| Deliver hardware to Government datacenter |
| HCI Vendor |
| NX-HW4 |
| Month 4 |
| 9 |
| Perform physical rack installation |
| HCI vVndor |
| Hardware delivered |
| Month 4 |
| 10 |
| Complete cabling (power and network) |
| HCI Vendor |
| Rack installation |
| Month 4 |
| 11 |
| Perform power-on verification |
| HCI Vendor |
| Cabling complete |
| Month 4 |
| 12 |
| Deliver installation documentation |
| HCI Vendor |
| Installation complete |
| Month 4 |
Phase 3: HCI Cluster Manager
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 13 |
| Perform cluster initialization process |
| HCI Vendor |
| Physical installation |
| Month 5 |
| 14 |
| Configure storage containers for OpenShift |
| HCI Vendor |
| Foundation complete |
| Month 5 |
| 15 |
| Apply TLS certificate to HCI Cluster Manager |
| HCI Vendor |
| Certificate provided |
| Month 5 |
| 16 |
| Configure AD authentication for HCI Cluster Manager |
| HCI Vendor |
| AD info provided |
| Month 5 |
| 17 |
| Perform HCI cluster health validation |
| HCI Vendor |
| Cluster configured |
| Month 5 |
| 18 |
| Document and deliver HCI Cluster Management admin credentials |
| HCI Vendor |
| Cluster configured |
| Month 5 |
Phase 4: HCI Management Console
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 19 |
| Deploy HCI Management Console on cluster |
| HCI Vendor |
| PE operational |
| Month 5 |
| 20 |
| Register cluster with HCI Management Console |
| HCI Vendor |
| PC deployed |
| Month 5 |
| 21 |
| Apply TLS certificate to HCI Management Console |
| HCI Vendor |
| Certificate provided |
| Month 5 |
| 22 |
| Configure AD authentication for HCI Management Console |
| HCI Vendor |
| AD info provided |
| Month 5 |
| 23 |
| Verify HCI Management Consolehealth |
| HCI Vendor |
| PC configured |
| Month 5 |
| 24 |
| Document and deliver HCI Management Console local admin credentials |
| HCI Vendor |
| PC configured |
| Month 5 |
Phase 5: S3-Compatible Storage
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 25 |
| Activate S3-Compatible Storage on HCI Management Console |
| HCI Vendor |
| HCI cluster operational |
| Month 5 |
| 26 |
| Create S3-Compatible storage with FQDN endpoint |
| HCI Vendor |
| S3 storage activated, DNS ready |
| Month 5 |
| 27 |
| Apply TLS certificate to S3-Compatible endpoint |
| HCI Vendor |
| Certificate provided |
| Month 5 |
| 28 |
| Verify HTTPS access to S3-Compatible endpoint |
| HCI Vendor |
| TLS applied |
| Month 5 |
| 29 |
| Create bucket: abacus-playbook-assets |
| HCI Vendor |
| Object Store created |
| Month 5 |
| 30 |
| Enable versioning on bucket |
| HCI Vendor |
| Bucket created |
| Month 5 |
| 31 |
| Create local user: abacus-assets-writer |
| HCI Vendor |
| Bucket created |
| Month 5 |
| 32 |
| Create local user: aap-assets-reader |
| HCI Vendor |
| Bucket created |
| Month 5 |
| 33 |
| Configure bucket policies per access matrix |
| HCI Vendor |
| Users created |
| Month 5 |
| 34 |
| Generate access/secret keys |
| HCI Vendor |
| Policies configured |
| Month 5 |
Phase 6: Handoff
| # |
| Task |
| Responsible |
| Dependency |
| Target |
| 35 |
| Deliver configuration documentation |
| HCI Vendor |
| All phases complete |
| Month 5 |
| 36 |
| Deliver credential inventory to Government |
| HCI Vendor |
| All phases complete |
| Month 5 |
| 37 |
| Deliver S3-Compatible FQDN and CA cert to Red Hat |
| HCI Vendor |
| TLS verified |
| Month 5 |
| 38 |
| Deliver aap-assets-reader credentials to Red Hat |
| HCI Vendor |
| Keys generated |
| Month 5 |
| 39 |
| Deliver S3-Compatible FQDN to Primary Contractor |
| HCI Vendor |
| TLS verified |
| Month 5 |
| 40 |
| Deliver abacus-assets-writer credentials to Contractor |
| HCI Vendor |
| Keys generated |
| Month 5 |
| 41 |
| Government acknowledges infrastructure handoff |
| Government |
| Documentation delivered |
| Month 5 |
Coordination Requirements
| From |
| To |
| Information Exchanged |
| When |
| Government |
| HCI Vendor |
| Datacenter readiness confirmation |
| Pre-Month 4 |
| Government |
| HCI Vendor |
| Network configuration (VLANs, IPs, gateways) |
| Pre-Month 4 |
| Government |
| HCI Vendor |
| FQDNs for Cluster Manager, Management Console, and S3-Compatible Storage |
| Pre-Month 4 |
| Government |
| HCI Vendor |
| TLS certificates for Cluster Manager, Management Console, and S3-Compatible Storage |
| Pre-Month 5 |
| Government |
| HCI Vendor |
| AD service account and group mappings |
| Pre-Month 5 |
| HCI Vendor |
| Government |
| Hardware delivery schedule |
| Month 4 |
| HCI Vendor |
| Government |
| Installation completion confirmation |
| Month 4 |
| HCI Vendor |
| Government |
| Configuration documentation and credentials |
| Month 5 |
| HCI Vendor |
| Red Hat |
| S3-Compatible Storage FQDN, internal CA certificate, aap-assets-reader credentials |
| Month 5 |
| HCI Vendor |
| Primary Contractor |
| S3-Compatible Storage FQDN, abacus-assets-writer credentials, HCI Management Console API endpoint |
| Month 5 |
| Primary Contractor |
| HCI Vendor |
| License activation authorization |
| Month 12 |
What HCI Vendor Does NOT Own
| Datacenter preparation (rack space, power, cooling) |
| Government Facilities |
| Top-of-rack switch installation and configuration |
| Government Network Team |
| DNS A record creation for all FQDNs |
| Government Network Team |
| TLS certificate issuance |
| Government PKI Team |
| Active Directory service account creation |
| Government Identity Team |
| OpenShift installation on HCI cluster |
| Red Hat Professional Services |
| AAP installation and configuration |
| Red Hat Professional Services |
| Abacus application development and deployment |
| Primary Contractor |
| Understanding Ansible, WinRM, or Windows automation |
| Red Hat / Primary Contractor |
| Certificate renewal post-deployment |
| Government (HCI Vendor provides guidance) |
| License procurement funding |
| Government (via contract) |
| License activation timing coordination |
| Primary Contractor |
| Certificate management and workstation onboarding workflows |
| Red Hat (via Git repository) |
HCI Vendor Deliverables Summary Infrastructure Deliverables
| # |
| Deliverable |
| Description |
| 1 |
| Hardware |
| Hyperconverged infrastructure nodes, racked and cabled |
| 2 |
| HCI Cluster Manager |
| Operational cluster with storage containers configured for OpenShift |
| 3 |
| HCI Management Console |
| Dedicated management instance registered with cluster |
| 4 |
| S3-Compatible Storage |
| S3-Compatible Storage with FQDN endpoint and TLS certificate |
| 5 |
| S3 Bucket |
| abacus-playbook-assets bucket with versioning enabled |
Access Deliverables
| 6 |
| HCI Cluster Manager local admin credentials |
| Government |
| 7 |
| HCI Management Management Console local admin credentials |
| Government |
| 8 |
| abacus-assets-writer S3 credentials |
| Primary Contractor (for Abacus) |
| 9 |
| aap-assets-reader S3 credentials |
| Red Hat (for AAP) |
| 10 |
| HCI Management Console API credentials (8, site-scoped) |
| Primary Contractor (for AAP) |
Documentation Deliverables
| # |
| Deliverable |
| Description |
| 11 |
| Rack elevation diagram |
| Physical hardware placement |
| 12 |
| Network port assignments |
| As-built cabling documentation |
| 13 |
| Cluster configuration document |
| Node inventory, network config, storage layout |
| 14 |
| HCI health report |
| Cluster validation results |
| 15 |
| Credential inventory |
| Secure handoff of all generated credentials |
| 16 |
| License activation schedule |
| Dates, terms, and renewal information |
