Mark, I'd point out that the PDF is not speculative. It was implemented in perhaps 3 or 4 different installers (I don't know the exact number) and has been in use for nearly two years. In calling this effort v1.0, the developers clearly saw this as a first draft that would be iterated over time.
David On Tue, Nov 26, 2019 at 6:53 PM SHOSTAK, MARK <mark.shos...@att.com> wrote: > Thanks George, > > > > That’s basically what I’ve seen so far. Unfortunately, a schema != a > specification. While there is some context in the structure of the schema, > there is still a great deal of ambiguity. Hacking against it is fine, but > I’m not sure I’d want to develop against it. > > > > That said, we do have a proposed plugfeast challenge to create a > preprocessor to mediate PDF to Airship manifest. Perhaps we can incorporate > an objective/requirement to show their work, so we can capture more > insight/data about the fields. *Jim*? > > > > --- > > > > WRT your question #2, note the Airship manifests describe the full stack > soup to nuts (i.e. h/w, s/w, networking, services, etc.), while the PDF > represents a subset of that information, so when xlating to Airship the PDF > will have to be supplemented with information to tell Airship what you’d > like it to do with the infra described in the PDF. Airship is currently > working on the 2.0 version, and that includes enhancements/changes to the > manifest format. You might be on to something when you talk about evolving > Airship and the PDF to go together. They’re both YAML, and given Airship > covers the full stack, the PDF (or SDF or other) may be able to inherit > from Airship, and potentially vice versa. > > > > Disclaimer: I use Airship, but don’t work on it, and do not represent it > any more than anyone else. This is just brainstorming from your original > comments. > > > > Thanks, > > -Mark > > > > > > *From:* Georg Kunz [mailto:georg.k...@ericsson.com] > *Sent:* Tuesday, November 26, 2019 16:20 > *To:* SHOSTAK, MARK <ms7...@att.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss][opnfv-tsc] Airship and PDF > > > > Hi Mark, > > > > Hoping that the pharos folks will correct me if I am wrong, the best > source of information I am aware of is the pharos repo [1] which holds the > schema of the pod descriptor file and an example. Moreover, pod descriptor > files for the various OPNFV labs are also stored in this repo [2]. > > > > [1] https://github.com/opnfv/pharos/tree/master/config/pdf > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_pharos_tree_master_config_pdf&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=mb4TI-s0r6iW8eaVypiejw&m=koOAoMGlfEpIcAilGbOVtGPe7c82e8fRvqy2nN2wPBQ&s=xPpQ9kcBTaLNSVcXg6SxJ-2MTdK4MFYqBamM8W8uBQM&e=> > > [2] https://github.com/opnfv/pharos/tree/master/labs > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_opnfv_pharos_tree_master_labs&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=mb4TI-s0r6iW8eaVypiejw&m=koOAoMGlfEpIcAilGbOVtGPe7c82e8fRvqy2nN2wPBQ&s=wp_XhdZj2m6p1GRxH7_VQbu3eTIM8tG6FKDELhWziNU&e=> > > > > Best regards > > Georg > > > > *From:* SHOSTAK, MARK <ms7...@att.com> > *Sent:* Tuesday, November 26, 2019 9:45 PM > *To:* Georg Kunz <georg.k...@ericsson.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss][opnfv-tsc] Airship and PDF > > > > Hi Georg, To that end, do you (or anyone) have the specification for PDF? > To Trevor’s point earlier today, all I’ve seen in a link to a PDF file, but > not an actual specification for the file. Thanks, -Mark > > > > *From:* opnfv-...@lists.opnfv.org [mailto:opnfv-...@lists.opnfv.org > <opnfv-...@lists.opnfv.org>] *On Behalf Of *Georg Kunz via Lists.Opnfv.Org > *Sent:* Tuesday, November 26, 2019 13:43 > *To:* opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > *Cc:* opnfv-...@lists.opnfv.org > *Subject:* [opnfv-tech-discuss][opnfv-tsc] Airship and PDF > > > > Hi all, > > > > I wanted to kick-off the email discussion around the wording and > additional input for next week’s vote on a potential exemption from the > requirement to utilize a Pod Descriptor File for the Airship project. > > > > Besides kicking off the wordsmithing process, I’d also like to direct a > request to the Airship team to compile input for the TSC. As I mentioned on > the TSC call, I’d like to prioritize value over former governance > decisions, but want to be able to better understand the context of our > decision. So, in line with other exemption requests and without attempting > to add an overly huge burden on the Airship team, I’d like to ask the > Airship project to describe… > > > > 1. the technical challenges of using the PDF for Airship. It has been > stated that there are gaps / missing information in the PDF making it > hardly suitable for Airship. I’d like to understand the challenges and the > effort needed to make this work. > 2. a firm plan on how to evolve Airship and the PDF (where needed) to > make both go together in the Jerma release. > > > > Assuming those aspects will be addressed, I’d like to propose the > following vote text: > > > > “Does the TSC exempt the Airship project from utilizing the Pod Descriptor > File for the Iruya release based on a documented plan for supporting the > PDF in the Jerma release?” > > > > Feedback and input is welcome. > > > > Best regards > > Georg > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#5714): > https://lists.opnfv.org/g/opnfv-tsc/message/5714 > Mute This Topic: https://lists.opnfv.org/mt/61965024/766177 > Group Owner: opnfv-tsc+ow...@lists.opnfv.org > Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub [ > dmcbr...@linuxfoundation.org] > -=-=-=-=-=-=-=-=-=-=-=- > -- *David McBride* Release Manager Linux Foundation Networking (LFN) Mobile: +1.805.276.8018 Email/Google Talk: dmcbr...@linuxfoundation.org IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23753): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23753 Mute This Topic: https://lists.opnfv.org/mt/61965023/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
