ONAP Developer Wiki
Spaces
Apps
Templates
Create
ONAP Wiki
All content
Space settings
Shortcuts
Shared links
Shared links
This trigger is hidden
File lists
File lists
This trigger is hidden
Meeting notes
Meeting notes
This trigger is hidden
JIRA Reports
JIRA Reports
This trigger is hidden
How-to articles
How-to articles
This trigger is hidden
Retrospectives
Retrospectives
This trigger is hidden
Product requirements
Product requirements
This trigger is hidden
Content
Results will update as you type.
ONAP Developer Wiki
ONAP Community Awards
Technical Steering Committee (TSC)
TSC Documentation
TSC Policies and Decision Logs
•
Reacting, Responding and Healing
TSC Subcommittees
Control Loop Subcommittee
Modeling sub-committee
•
2019 Modeling Subcommittee Decisions
•
2020 Modeling Subcommittee Decisions
•
2021 Modeling Subcommittee Decisions
•
2022 Modeling Subcommittee Decisions
•
Modeling Current Activity Status
•
Modeling sub-committee Contributions
Modeling sub-committee meetings
•
Modeling Subcommittee Election
•
Modeling Subcommittee Members
Modeling tools
ONAP Model Enabled Reviews
ONAP Modeling Design Principles and Guidelines
ONAP Modeling Governance
ONAP Modeling specification
ONAP Non-MANO Artifacts Set Identifiers
ONAP R2 Modeling working space
ONAP R3 Modeling working space
•
ONAP R2 VNF Papyrus Sub Model - For Review
ONAP R3 Modeling High Level Requirements
ONAP R3 Resource Data Model
•
Data Model Interest Group Participants
•
ONAP R3 Resource DM Clean Version
ONAP R3 Resource DM Discussion
•
Mapping between SOL001 Model and Internal Model
•
Separate Models for Onboarding and Orchestration: Concerns and Solutions
•
Why does R3 need multiple DMs
•
Patterns of translating IM into TOSCA-based DM
•
ONAP Data Models Convergence
•
PNF TOSCA Model
•
Allotted Resource TOSCA Model
•
Abstract Resource Node Types
•
Expressing abstraction in model
ONAP R3 Resource DM Proposals
•
State of Affairs in ONAP Modeling in R2
•
R3 Data Model Meeting Day/Time Poll
ONAP R3 Resource Information Model
ONAP R3+ Cloud Infrastructure Modeling
ONAP R3+ Service IM Workspace
ONAP R4 Modeling working space
ONAP R5 Modeling work space
ONAP R6 Modeling working space
ONAP R7 Modeling working space
ONAP R8 Modeling working space
ONAP R9 Modeling working space
ONAP R10 Modeling working space
ONAP R11 Modeling working space
ONAP R12 Modeling working space
Process Improvements
Progress Summary Info for ONAP related SDOs
•
Recommended specs from SDOs
Target Platform Data Model (was Target Internal Data Model)
The Glossary of Modeling Subcommittee
•
the modeling contact from each ONAP project
ONAP Security coordination
Open Lab Subcommittee
•
Proposal: VNF Validation Subcommittee (VVC)
Requirements subcommittee (is merged into ARCCOM)
TSC Task Force - Cloud Native
TSC Task Force: ONAP for Enterprise Business
TSC Task Force: Wiki 2.0
Use Case Subcommittee (replaced by Requirements subcommittee)
x-Deprecated Architecture Subcommittee *** Please note New Location within ***
ONAP Vulnerability Management
Technical Community Coordinators and ONAP Liaisons
•
Test Notes
Blogs
ONAP Wiki
/
/
ONAP R3 Resource DM Discussion
/
Why does R3 need multiple DMs
Summarize
Why does R3 need multiple DMs
Anatoly Katzman
Owned by
Anatoly Katzman
Last updated:
Apr 25, 2018
1 min read
Loading data...
Discussion Summary
{"serverDuration": 31, "requestCorrelationId": "6674419e1e8149e280a9da454888f840"}
Anatoly Katzman