POD Descriptor File 1 0 Quick Overview POD

  • Slides: 12
Download presentation
POD Descriptor File 1. 0 Quick Overview

POD Descriptor File 1. 0 Quick Overview

POD Descriptor File 1. 0 – Intro (1) • POD Descriptor File (PDF) defines

POD Descriptor File 1. 0 – Intro (1) • POD Descriptor File (PDF) defines what hardware is in an OPNFV POD • Part of the common configuration file consolidation effort • An effort to consolidate installer input configuration (align all OPNFV installer inputs into a common format)

POD Descriptor File 1. 0 – Intro (2) • Sections – Lab details (owner,

POD Descriptor File 1. 0 – Intro (2) • Sections – Lab details (owner, location, intended use) – Jump Server – Nodes • New features – Optional encryption for sensitive data – Schema validation to ensure all incoming PDFs are valid

POD Descriptor File 1. 0 – Doc Resources (1) [1] POD Descriptor File Deep

POD Descriptor File 1. 0 – Doc Resources (1) [1] POD Descriptor File Deep Dive (Jack Morgan) • https: //www. slideshare. net/OPNFV/pod-descriptor-file-deep-dive [2] PDF Template • https: //git. opnfv. org/pharos/tree/config/pdf/pod 1. yaml [3] PDF Template (with encrypted values) • https: //git. opnfv. org/pharos/tree/config/pdf/pod 1. encrypted. yaml [4] PDF Schema • https: //git. opnfv. org/pharos/tree/config/pdf/pod 1. schema. yaml

POD Descriptor File 1. 0 – Doc Resources (2) [5] Encrypting sensitive data •

POD Descriptor File 1. 0 – Doc Resources (2) [5] Encrypting sensitive data • https: //git. opnfv. org/pharos/tree/config/utils/README. eyaml. rst [6] Example PDF (lf-pod 2) • https: //git. opnfv. org/pharos/tree/labs/lf/pod 2. yaml [7] Schema validation script • https: //git. opnfv. org/pharos/tree/config/utils/check-schema. sh [8] Installer adapter validation script • https: //git. opnfv. org/pharos/tree/config/utils/check-jinja 2. sh

POD Descriptor File 1. 0 – CI Validation (1) • CI-driven validation of new

POD Descriptor File 1. 0 – CI Validation (1) • CI-driven validation of new PDFs submitted to Pharos git for: – Schema (strict) • Each new PDF is automatically validated by Jenkins using: • $. /config/utils/check-schema. sh # see [7] – Installer adapter template expansion • Each new PDF is automatically checked against all existing installer • adapter templates using: • $. /config/utils/check-jinja 2. sh # see [8] – Generic (yamllint, pylint etc. )

POD Descriptor File 1. 0 – CI Validation (2) • Current CI jobs ensure

POD Descriptor File 1. 0 – CI Validation (2) • Current CI jobs ensure newly submitted PDFs: – – Use valid YAML Have a structure that respects the template in [2, 3] Use values which respect the checks enforced in [4] Can be successfully expanded using installer adapter templates in Pharos

POD Descriptor File 1. 0 – Adoption Status • Lab config migration from securedlab

POD Descriptor File 1. 0 – Adoption Status • Lab config migration from securedlab to Pharos: 100% • Validate existing PDFs: 100% (renamed from “adoption”) • Installers relying on the new PDF: 100% (? To be doublecheked) – Some installers only read a few params from PDF for now; – Most installers hardcode the number of cluster nodes for now;

POD Descriptor File 1. 0 – Limitations (1) • PDFs cannot be created automatically

POD Descriptor File 1. 0 – Limitations (1) • PDFs cannot be created automatically (e. g. via a script) – Lab owners need to fill in data manually (one time job per POD) • PDF on its own is not enough to cover all installer inputs – Additional IDF (Installer Descriptor File) and SDF (Scenario Descriptor File) will be introduced later (already in progress) • Lab switch configuration is not covered by PDF – A `net_config` section was proposed in IDF to cover this

POD Descriptor File 1. 0 – Limitations (2) • PDF 1. 0 only covers

POD Descriptor File 1. 0 – Limitations (2) • PDF 1. 0 only covers baremetal nodes (not virtual) – v. PDF (support for virtual nodes) might be introduced in a later PDF release

POD Descriptor File 1. 0 – Future Plans • Open discussion – No outstanding

POD Descriptor File 1. 0 – Future Plans • Open discussion – No outstanding PDF 1. 0 issues – v. PDF was proposed, so installers can fully switch to PDF as a single input configuration file for all deployment types – Should be considered in the context of IDF/SDF complementing PDF

Thank you opnfv-tech-discuss@lists. opnfv. org

Thank you opnfv-tech-discuss@lists. opnfv. org