Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4669

UKSRC - Meet *full* v0.1 storage, compute and network requirements in time

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      The commencement of v0.1 will be a landmark achievement for SRCNet, intended to be achieved by 2024-12-01. 

      To enable initial engineering operations by this date, SRCs may deploy services on temporary infrastructure and/or infrastructure with low storage/compute/network capacities. This arrangement will be sufficient for SRCNet to begin the v0.1 phase of work, but will soon become insufficient to e.g. perform testing at scale.

      Meeting the full v0.1 storage, compute and network requirements (as detailed in the v0.1 EoIs) or committing to a plan to deliver these resources early next year, is one criteria for SRCNet to "confirm" that SRCs will be a v0.1 node.

      A sufficient number of SRCs must be confirmed for SRCnet to commence the v0.1 phase of work.

      Show
      The commencement of v0.1 will be a landmark achievement for SRCNet, intended to be achieved by 2024-12-01.  To enable initial engineering operations by this date, SRCs may deploy services on temporary infrastructure and/or infrastructure with low storage/compute/network capacities. This arrangement will be sufficient for SRCNet to begin the v0.1 phase of work, but will soon become insufficient to e.g. perform testing at scale. Meeting the full v0.1 storage, compute and network requirements (as detailed in the v0.1 EoIs) or committing to a plan to deliver these resources early next year, is one criteria for SRCNet to "confirm" that SRCs will be a v0.1 node. A sufficient number of SRCs must be confirmed for SRCnet to commence the v0.1 phase of work.
    • Hide

      AC: Meet full v0.1 storage, compute and network requirements by 2024-12-01 (start of v0.1), capable of hosting all local compulsory services and assigned global services OR a plan shared with the ISMG has been approved by Janneke de Boer that shall deliver these resources by 2025-03-11 (end of PI25).

      In effect, the v0.1 deadline has been extended, the original v0.1 node requirements stated "Jan 2025".

      If sharing a plan, these considerations must be taken into account:

      • Steps and effort required to transition from temporary infrastructure to production infrastructure.
      • What services shall be deployed <-> What additional development work is required to adapt software / services to run on this particular infrastructure.
      • The operational impact on non-SRCNet clients and mitigating actions that need to be taken.

      For some SRCs, this may be a simple task satisfied by a basic timeline / Miro. For others a more detailed plan is required.

      Show
      AC: Meet full v0.1 storage, compute and network requirements by 2024-12-01 (start of v0.1), capable of hosting all local compulsory services and assigned global services OR a plan shared with the ISMG has been approved by Janneke de Boer that shall deliver these resources by 2025-03-11 (end of PI25). In effect, the v0.1 deadline has been extended, the original v0.1 node requirements stated "Jan 2025". If sharing a plan, these considerations must be taken into account: Steps and effort required to transition from temporary infrastructure to production infrastructure. What services shall be deployed <-> What additional development work is required to adapt software / services to run on this particular infrastructure. The operational impact on non-SRCNet clients and mitigating actions that need to be taken. For some SRCs, this may be a simple task satisfied by a basic timeline / Miro. For others a more detailed plan is required.
    • 0
    • 0
    • Team_PURPLE

    • PI24 - UNCOVERED

    • PI24-PB SRCNet0.1 Team_PURPLE
    • SPO-3481

    Description

      The v0.1 storage, compute, network requirements have been in place since the v0.1 EoIs were committed to in late March 2024.

      Making these resources available is an Infrastructure Management activity - therefore will not be credited with feature points. 

      These plans will be managed via the ISMG.

      The complexity of this task and the work remaining varies greatly per SRC. For some, a simple timeline will be sufficient. For others, the plan will require greater effort.

      The reason this feature has been created to ensure that capacity is reserved during PI planning, and to improve tracking / visibility.

      The SRC member responsible may not be a member of an Agile Team - that field may be left blank. 

       

       

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SP-4683 At least 4 SRCs will meet *full* v0.1 storage, compute and network requirements in time

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog
          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4257 Develop the tests and monitoring for v0.1 Data Challenge

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Program Backlog

          Structure

            Activity

              People

                J.DeBoer De Boer, Janneke
                Robert.Perry Perry, Robert
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 0.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel