Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleLegend

Color code:

  • Red: below maturity level
  • Yellow: same maturity.
  • Green: improved maturity level.

M1 Actual represents the assessment before M1. M1 Target represents, at M1 date, what the team plans to implement. M4 result represents what has been really implemented at M4 date . All these fields are self-assessed by the team.




AREA

Design / Run-TimePerformanceStabilityResiliencySecurityScalabilityManageabilityUsability
Min TSC Recommendations
M1 Actual

M1 Target

M4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 resultM1 ActualM1 TargetM4 result
Project Name





















A&AIR11112WIP2221

1 (stretch goal; 2 unlikely)


111112

1+

(see note 10)

111
Application Authorization FrameworkR01101212212201211111

1

APPCR0001

1 (APPC)

2 (Integration) (Note 1)

12221

1 - Partial

(Note 2)

1111111111
CLAMPD0001111111111111

1

(2 if CLAMP get more resource)

11

1

(2  if CLAMP get more resource)


Common Controller SDKR000NANANA222111111111111
DCAED & R1

2 (stretch)

12222221

1

(+topic security w/dependency Note3)

11111

1

(+logging v1.2)

1111
DMaaPR11WIP11WIP22211

WIP

Note 9

1
22
11111111
DocumentationNA




















External API FrameworkR001001002011001001002
HolmesR11111112WIP12 Stretch1(descoped)11111112 StretchWIP

Integration

NA




















Logging Enhancements Project R122
32
222222120111121 (see note #8)121
POMBA (under but separate pod from Logging)R112112112111111111111
Microservices BusR111111222011111111111
ModelingD
0
/R11122211111
2
101
0
111
0
11
0
11
Multi VIM/CloudR111111222111111111111
MUSICR11
11
22
22111
11
11
ONAP CLID & R11
11
22
11
11
11
22
ONAP Operations ManagerNA




















ONAP Optimization FrameworkR11
11
22
11
11
11
11
ONAP Usecase UI Project ProposalD12112122211+101111+111+1
Policy Framework Project ProposalD & R

1

2

1+

See Note #5

11

1

See Note #4

22

1

See Note #4

12

1

No Silver Badging

11

1

See Note #4

11 (logging v1.2 only)

1

See Note #6

111
Portal Platform Project ProposalD & R1111112221

1+

See Note #7

1111111222
SDN-CR000111222111111111111
Service Design & CreationD00
12
11
1

1+(AAF integration and https support)

WIP


00
1

1(with

logiing

logging v1.2 spec support)

WIP


11
Service OrchestratorR011111222111111111111
VFCR111121222111011111111
VIDR00012

2

(Note 1)

222111 - WIP11111(with
logiing
logging v1.2 spec support)1 (Note 8)111
VNF SDKD00
11
11
11
00
11
11
VNF RequirementsNA




















VNF Validation (VVP)DNA

NA

NA

11
NA

NA

NA

Note 1: Assumption is that platform 72 hour test is run by Integration team; Component team will run regression (Level 1) on Casablanca release

Note 2: APPC was Level 1 compliant in Beijing; however, Level 1 definition changes in Casablanca. APPC cannot commit to Level 1 due to pending item. See M1 Planning for more details.

Note 3: Dynamic topic provisioning and RBAC assignment has dependency on DMAAP-BC (DMAAP project) and AAF team

...

Note 6: The resources for doing logging v1.2 went away as part of the contract/restructuring between the two corporations early 2018.

Note 7: AAF integration into portal-sdk is partially complete and CADI integration is planned for next release - for more details see Risk #3.

Note 8: logging spec and implementation changes done with AT&T/TechMahindra to sync to Acumos - logging resources are absolute minimal during casablanca - 1.2 spec completion is pushed to Dublin

Note 9: AAF CADI integration is pending

Note 10: logging spec very close to 1.2; completion slated for Dublin