Challenge: OPNFV PDF to Airship Manifest Transformation

Owned by Lincoln Lavoie
Last updated: Jan 14, 2020 by Mark Shostak
1 min read

Challenge Outline & Goals

  • OPNFV uses PDF to specific POD Descriptor File

  • Airship does not use PDF; instead it uses a “treasure map” manifest file that’s a combination of PDF + SDF (Scenario Descriptor File)

  • Discussion around creating a PDF to Airship Manifest 1.0 converter

  • Discussion around expanding to scope to potentially replacing PDF with the new format

Resources

Attendees

  1. @Mark Shostak

  2. @Daniel Balsiger

  3. @Al Morton

Notes, etc.

  • TBD

Treasuremap Files

When looking shortly at treasuremap I see at least those files affected, i.e. containing information which is in OPNFV PDF (it is not a complete list):

site/${your_site}/profiles/hardware/${your_bm_node_type}.yaml site/${your_site}/baremetal/nodes.yaml site/${your_site}/networks/common-addresses.yaml site/${your_site}/networks/physical/networks.yaml site/${your_site}/profiles/host/compute.yaml site/${your_site}/secrets/passphrases/ipmi_admin_password.yaml



Team, Here is a link to the actual manifest files used to deploy various pods in the Intel lab: https://github.com/opnfv/airship/tree/master/site

This is the OPNFV deployment guide for Airship, and is focused on deploying in the pods in the Intel lab: https://wiki.opnfv.org/display/AIR/Airship+Installer+Deployment+Guide

Here are the generic treasuremaps, released every few months (1.6 is the latest at the time of writing): https://github.com/airshipit/treasuremap/releases



Machine generated PDF from UNH: