Child pages
  • Contributions
onf2017.154IMP Work Items for future release V1.4: 7/2018V1.5: 4Q2018V2.0: 7/2019
Participation - L = Lead, P = actively Participate
ItemShort NameTR-512 sub docReleaseFor 2.0Chris HNigel DKam LBernd ZMalcolm BRod LQilei WXiang YYuji TItalo BXing ZKarthik SStephen SAndrea MScott MStephane St.LSibylle SAugie JRick JingPriorityStart Date1st Draft date1st reviewupdatefinal reviewTarget publica.Brigade Process ?Nov. Meeting DeliverableLong Description
1Controller81.4LPPPP?P8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Controller model and NE deconstruction (at least some more examples)
3Specification71.4LPPP 25-Sep8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Spec model (with Tapi) * Especially scheme spec related to the photonic model
4Software121.4LPP8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Modelling of software, Good material from TMF TR-225 * And relating it to hardware and emergent function
33Software exampleA.13L8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7
5OAM91.5PPPPPPPL P25-SepNoOAM (called for by Tapi); For November delivery generalize whatever in the current TAPI OAM
6Resilience51.5PP?LNoResilience examples (as called for by TAPI)
8Equipment enhancements61.4L 8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Equipment (as called for by TAPI). Chris: mix a lot of core framework with other stuff, Nigel: May need a strong story for v1.3.1 * Spec of capability; * Defining the properties of the equipment; * Equip - function (in the PC) Move the spec to 1.5
10Operation Patterns101.4LPPPP8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7Model patterns to support operations patterns including intent, TOSCA and policy (with Boulder), query More than just intent Join the operation pattern into the control
12Entity lifecycle31.5PPLPPP2-OctLifecycle of entities (including split and join) * Dynamic view/abstraction/virtualization
15RationaleA.31.4L 2-Oct8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7 1.3 overhang: Modelling rationale, ...
16P&R Methodology2LPPPrune &Refactoring methodology and tooling
17UML GuideTR-5141.4PLPDone18/6-22/625/6-6/79/7-20/723/7-27/7UML Modeling Guidelines
18Papyrus GuideTR-5151.4PLPDone18/6-22/625/6-6/79/7-20/723/7-27/7Papyrus Guidelines
19UML-YANG GuideTR-5311.4PLPPDone18/6-22/625/6-6/79/7-20/723/7-27/7Mapping Guidelines
20UML-OAPI GuideTR-543Mapping Guideines
22UML-Yang GenUML-Yang Generator
23UML-OAPI GenUML-OAPI Generator
25P&R ToolingPL
27UML-Protobuf GuideTR-544LP?Done
31Layer Examples (packet)A.61.4PPPL P?25-SepMarch18/6-22/625/6-6/79/7-20/723/7-27/7NoMore examples of layers (as called for by TAPI etc) * Defer L0 (media (photonic and wireless)) Analogue; * Focus on L1/2 Circuit; * L2/3 (inc LAG) Packet; * Multilayer etc
2Processing Construct111.4LPPP?PDone18/6-22/625/6-6/79/7-20/723/7-27/7NoSlide pack for TOSCAPC/Component/VNF/TOSCA * Should we continue to have ControlComponent as a specialized class of PC/Component
13Model StructureA.22LPNoModel structure & model patterns, Chris: cycle of model, need architecture of the model, Nigel: need cleaning
14Topology4 1.5LPP?P25-SepTopology stuff outstanding (IETF TEAS comparison). Fix ForwardingEntity _PAC model (should be decoration/spec); Per TAPI request, need to develop examples of usage of the topology Pacs. Consider pull this for 1.4 for TAPI needs.
21UML-TOSCA Guide1.5PPLHMapping Guideines
24UML-TOSCA Gen2.xLUML-TOSCA Generator
26Intent/Contsraint1.5LPP?P?P?28-SepBrigade (joint with ONOS)Could lead to use the operation patterns; could be merged into operation patterns More in the Interface model consideration, rather than on the Core model
28UML-Protobuf Gen2.xPL?
29Party model1.5LP
30Location model1.5LP
7Layer Examples (circuit)A.51.4L March18/6-22/625/6-6/79/7-20/723/7-27/7
9IP2PPIP driven by requirements from ECC/DCN ensuring we have core support (IMP, OT, TAPI brigade * Extending over time to “full” IP via appropriate collaboration and federation
11Views/Contexts0.81.5PL?PView abstractions and virtualisation
32Photonic model examplesA.41.4L8-Jun18/6-22/625/6-6/79/7-20/723/7-27/7
34LTP port investigation1.5PLPPP
35LTP port 2P
36Compute model (CPU Storage)2.0L
37Spec re-work2.0L
38Semantic compatibility framework2.0Could be a A.x in 1.5 or a separate TR or .B.x series; The microService will be a piece of the core model (so .x, not .A.x)
39Event driven solution investigation 1.5L
40Rule pattern investigation 1.52.0L2.0Investigation in the 1.5 time frame. Model ehancement in the 2.0 time framework
41Identity model investigation1.5PL2.0Investigate the identify model (Global class & Local class). Not inherit from Global or Local class. A tool will geneates the necessary identify attributes from the Global and Local classes and add to the entity classes at ?? time.
42General Profile/template approach1.5PLPUser profile and template as classes (i.e., not stereotype)
43Operarion pattern for general task1.5LUse TAPI OAM as the seed to investigate using the Operation Pattern to support general task, taking the G.8051 On-demand measurement job requirement into account as input.
44Refactor LTP Spec to be Comp-Sys Spec2.xL2.nIn v2.n, refactor the LTP spec to be a full generalized Component-System spec with constraints on what components can be used. Depends on LTP Port work.
45Model artifact lifecycle promotion1.5LPE.q., ProcessingConstruct