Charter Alignment roadmap

[dkurepa]

We want to create a mermaid graph with the rollout of the Charter Alignment epic

[dkurepa]

flowchart TB
classDef doneClass fill:#7CFC00
classDef inProgressClass fill:#00FFFF
classDef notStartedClass fill:#FF5733 
subgraph Legend
    DONE:::doneClass
    in-progress[IN PROGRESS]:::inProgressClass
    not-started[NOT STARTED]:::notStartedClass
end
dnceng-shared[Create dnceng-shared, move shared libreries and publish them from there]:::doneClass
helix-service[ES Create a dnceng-shared -> helix-service Maestro subscription and consume the libraries]:::doneClass
arcade-services[Create a dnceng-shared -> arcade-services Maestro subscription and consume the libraries. Delete the Shared libraries implementation from arcade-services]:::doneClass
dnceng[Create dotnet/dnceng repo and port all of the internal tools from arcade-services. Create dnceng-shared -> dnceng subscription]:::doneClass
dnceng-staging[Succesfully deploy internal tools from dotnet/dnceng to the staging environment]:::doneClass
arcade-services-disable[Disable internal tools rollouts from arcade-services]:::doneClass
dnceng-production[Rollout internal tools from dnceng]:::doneClass
arcade-services-cleanup[Cleanup arcade services]:::doneClass
telemetry-cluster[Migrate Telemetry Service outside of the Maestro SF cluster]:::inProgressClass
maestro-subscription[Create new Maestro subscriptions under the Product Construction Service tree]:::notStartedClass
maestro-migrate[Migrate Maestro++ into the new subscription]:::notStartedClass
maestro-legacy-migrate[Migrate Legacy Maestro into the new subscription]:::notStartedClass
BAR-migrate[Migrate the BuildAssetRegistry database into the new subscription]:::notStartedClass
issue-management[Migrate product construction issues to arcade-services and create a new workflow]:::doneClass
dnceng-shared-->arcade-services
dnceng-shared-->helix-service
arcade-services-->dnceng
dnceng-->dnceng-staging
dnceng-staging-->arcade-services-disable
arcade-services-disable-->dnceng-production
dnceng-production-->arcade-services-cleanup
arcade-services-cleanup-->maestro-subscription
maestro-subscription-->maestro-legacy-migrate
maestro-subscription-->BAR-migrate
maestro-subscription-->maestro-migrate
dnceng-production-->telemetry-cluster

@missymessa does this look correct to you?

[missymessa]

Create a cluster for the Telemetry service and deploy it there

I'm assuming this is a Service Fabric cluster? There might be other things in that will need to live there besides Telemetry, so let's make sure they don't get left behind.

/cc @riarenas, @AlitzelMendez, @garath in case I'm overlooking anything else.

[riarenas]

the maestro cluster currently only has two applications. Maestro and Telemetry. If we want to take it out of the Maestro cluster, that would be the only application in there. Is there a reason why they shouldn't stay in the same cluster? they even depend on each other afaik.

[missymessa]

Budgeting would be a reason to separate them. Team autonomy for ProdCon would be another reason.

[riarenas]

Is the plan to move the maestro cluster to a different subscription for budgeting? Currently they live in the HelixStaging/prod subscriptions.

Both teams can still have autonomy while deploying to the same cluster from two different repositories so I don't know if I'm following that argument.

We can definitely move things around, but there might be some work that needs to be done to make sure there are no regressions on both apps.

[missymessa]

Is the plan to move the maestro cluster to a different subscription for budgeting?

Yep.

[tkapin]

@dkurepa - Why is it blocked? What needs to happen to unblock this?

[dkurepa]

I wouldn't say it's blocked. It's more of a I don't know if we should call it complete

[dkurepa]

Closing the issue since the roadmap is completed