Epic Goal

• Extend MicroShift's ServiceManager implementation to
  • measure time from starting the component (calling Run()) to component being ready (closing ready channel)
  • provide extra runtime information on dependencies and ordering of the components

Why is this important?

• Make finding unnecessary or missing dependencies easier
• Measurements of components startup will tell us where we spend time and help track regressions of start up time

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. For OCPBUGS-18706 I had to add a bunch of extra logs that would tell me when components is started and when it's ready before I could find unnecessary bottlenecks.
   1. I also created graph manually

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>