Versions Compared

Old Version 1

changes.mady.by.user Jim Baker

Saved on

compared with

New Version 2

changes.mady.by.user Georg Kunz

Saved on

Key

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

...

  • Open source development (Dovetail) community dissolved 
  • Lacking skill set in UI development - Intracomm was contracted
    • Original portal leveraged from OpenStack


Requirements

This list of requirements should be expanded in level of detail to support an RFP:

  • General requirements
    • the portal must at least provide the same functionality as today's portals (see https://nfvi-verified.lfnetworking.org/#/):
      • "marketplace": list companies and products which have obtained a badge
      • upload, validate, display and manage test results by "uploaders"
      • review test results by "reviewers"


  • OVP program integration
    • the web portal must integrate different types of OVP programs (e.g. NVFI, VNF, ...)
    • today, the VNF and NFVI program use separate web portals


  • test result management
    • authenticated users (role "uploader") must be able to
    • upload test results
    • edit meta data of a test result set (product name, etc.)
    • view and edit only their own test results
    • change status of a test result between "private" and "for review"


  • OVP release management
    • management of releases of OVP (create new, edit, delete) must be runtime operations, i.e., not requiring new versions of the portal
    • a OVP release comprises
    • documentation
    • a unique test result schema for test result validation and display


  • validation and display of test results
    • the web portal must
    • validate that an uploaded set of test results conforms to a given format (schema)
    • validation of test results must follow a schema (manageable as part of the release management)
    • the schema shall include
    • list of all tests per OVP release: "source of truth" - does an uploaded test result package contain results for all tests of an OVP release
    • OVP release ID (e.g. 2020.10)
    • OVP program type (e.g. NVFI, VNF, ...)


  • review management
    • reviewers (user role) must be able to
    • access all test results set to state "for review"
    • cast a vote (-1, 0, 1) on every instance of test results


  • portal lifecycle management
    • all management operations on test results, market place entries, users, and new releases of OVP must be runtime operations
    • not requiring new builds of the web portal
    • separation of LCM of the portal instance (responsibility of IT) and content (responsibility of OVP admins)


  • Marketplace management
    • "marketplace admins" (user role) must be able to manage entries of the marketplace (create, edit, delete)
    • all entries of the marketplace must be stored in persistent storage
    • market place data items per entry: see current fields + <add more if needed, Brandon?>


  • user management
    • allow for managing users and roles based on LF IDs
    • roles: reviewer, uploader, admin


Requirements (as noted during the call on :

  • Development
    • Represent the workflow of the respective participants
      • xtesting results uploaded - schema for uploads
      • portal to validate/accept inputs - version checking
      • Allow authorized set of people to manage the badging administration
    • No regression of functionality from Dovetail implementation
    • Alignment of results formats from ONAP/OPNFV
      • ?Allow all versions to be uploaded - deprecate older versions?
        • Bring forward existing badging - unlikely to support old schema/results 
        • Minimum: current xtesting and ONAP results - schemas
    • Converged portal (VNF/NFVIs/CNF) 
    • Built on LF infra (shared vs. dedicated)
    • Desire portal to be managed without LF IT interactions 
    • Naming changes?
      • Define that early
    • User management
      • integrated with LF SSO 
      • Privileged users for management
    • 3rd party OVP lab integration 
    • Use existing portal as a basis for MVP definition
    • Timeline?
      • Objective: full MVP implementation - Oct 2020 (ONES Sept 28)
        • Public availability
        • Migrate existing data
        • Internal Go-Live –  
        • Development time – start  
        • Review submissions to RFP
        • RFP open time –  
        • RFP definition complete –  
        • Budget setting/approval – LF GB  
        • Vendor qualification - at least 3 vendors
      • Support for incoming data sets and badging processes
  • Hosting
  • Maintenance

...