Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

ARTs:

Services
Benefit hypothesis:

Hide

This will set out what needs to be done to deploy the Dish compute platform, to create a deployment template that can be tested in PI24 and then used for AA0.5 rollout

Show
This will set out what needs to be done to deploy the Dish compute platform, to create a deployment template that can be tested in PI24 and then used for AA0.5 rollout
Acceptance criteria:
Hide

In the Mid ITF - 2 servers:

Server hardware is racked with designed network and disk pattern

Enrolled with seed/management server

Storage defined

Monitoring/Logging integrated

Kubernetes deployed (single node BM cluster, Storage Integration, Ingress, LB, Logging/Monitoring)

Prepared for shipping to site (renaming/reconfiguration performed - one server only)

One dish.LMC is made available for ITF based testing
Show
In the Mid ITF - 2 servers: Server hardware is racked with designed network and disk pattern Enrolled with seed/management server Storage defined Monitoring/Logging integrated Kubernetes deployed (single node BM cluster, Storage Integration, Ingress, LB, Logging/Monitoring) Prepared for shipping to site (renaming/reconfiguration performed - one server only) One dish.LMC is made available for ITF based testing
Feature Points:
2.5
Initial Size:
2.5
WSJF:
0
Agile Teams:

Team_BANG
Due Sprint:
Sprint 5
Story Point Burn-up:
Overdue:

Deploy the Mid Dish LMC computing platform for AA0.5 for SKA063

Achieved as of the end of PI24:

Node storage has been verified and configured.
Node has been inspected, provisioned and configured.
Kubernetes has been deployed on the node as a single-node cluster.
Kubernetes services have been deployed on the cluster.
Monitoring and logging exporters have been deployed and a prometheus instance reconfigured to scrape them.
DNS has been configured to resolve node related DNS names.

Story Point Burn-up: (0%)

Feature Estimate: 2.5

Prepare Mid Dish LMC Platform for AA0.5