Hi, Thanks, Alexandru, I think you solved my action from yesterday’s Infra call :-).
I think the idf as you proposed it is a good thing. Just make sure, we don’t need to duplicate information too often (e.g. where there is identical information for all pods in a lab). The sdf template exists since a few months, but I didn’t get enough feedback from the installer teams. We have to make sure that not only the sdf can be easily consumed by the installers, but also provides all data the installers need in an independent way and there is no gap then between the pdf&idf and the sdf. The sdf template is available since June. Please have a look and let me know if there are things missing. At that time I couldn’t check against MCP, only against Fuel configuration files. (see https://git.opnfv.org/octopus/tree/scenarios/templates/sdf-template.yaml ) Please other installer teams, also let me know about missing or wrong things. Also feel free to propose patches ;-). The scenario lifecycle document is also available in octopus repo (or http://artifacts.opnfv.org/octopus/docs/scenario-lifecycle/index.html ) and awaiting more feedback. Cheers, Uli From: [email protected] [mailto:[email protected]] On Behalf Of Alexandru Avadanii Sent: Monday, 18 September, 2017 19:00 To: Julien; [email protected]; Chigang (Justin); [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Cc: Charalampos Kominos; Guillermo Herrero Subject: Re: [opnfv-tech-discuss] [infra][pharos]Is PDF feature supported by installer project now? Hi, In today’s Infra meeting, we had very little time to discuss the specifics of using PDF in real-life use-cases, so I am continuing the discussion here. Afaik, there are at least 2 installer projects actively working on using PDF: 1. Fuel/Armband based on MCP – Guillermo H. and I have submitted some patches covering PDFs for our PODs, as well as minor improvements to PDF parsing, and an installer adapter (draft); 2. Openstack Ansible (OSA) – David B. has submitted a few patches, touching the PDF design and possible extensions; Both installers work well with PDF as an input, but we hit a few design quirks that I want to elaborate on: 1. PDF tooling and installer adapters should be publicly available, which we decided today to move to pharos git repo (see [1]), eventually split that repo into smaller repos; 2. PDF alone is not enough to describe installer-specific configuration that is scenario-indepedent, e.g.: a. Both David and I noticed there is no sane way to map POD networks to bridge names on the jump host; b. David proposed a new section should be added to describe this mapping; I found a way around it for Fuel, but it requires each bridge to have an IP addr in each subnet it covers [2]; c. For OSA, there are other things that can’t be described by PDF, like possible node roles (controller, compute, network etc.) which Fuel solves by assuming all nodes are the same, and the first 3 nodes in PDF should be controllers – this works, but it’s not the best approach for PODs with different blades; Since SDF is not yet available, we want to propose a mechanism that allows describing this installer-specific configuration. David proposed in [3] a set of changes on top of PDF: removing some useless entries from PDF, as well as adding a new companion file, the IDF (Installer Descriptor File). My understanding is that changing the PDF to include the IDF in its specification is not a good long-term action, or at least that’s what I got from today’s meeting. Although I agree on mixing installer data with PDF is not a good long-term solution, we would like to fiind an acceptable solution for the short term (until SDF lands). So, my proposal is to make IDF a separate thing. Design-wise, everything in PDF is good to go as it is right now. Fuel (MCP) and Armband projects can easily consume the PDF without and IDF (provided we have an IP in the right subnet for each jump host bridge, but even that is optional and can be overriden via <ci/deploy.sh –B> via Jenkins slave parameters / env vars). Implementation-wise, David’s patch should be taken as-in. The IDF file (when required) will be in the same location the PDF is, with a derived name like „podX-idf.yaml”. The syntax and structure will be installer-specific, so there’s no need to cover this in Pharos; installers should be responsible for describing their own format. The IDF would be optional, of course. If your installer does not require setting this kind of data, just ignore it and go with a plain PDF, according to current specs. Please let me know what you think about this, we want to support PDF asap. Fuel documentation will heavily rely on PDF as an input (actually most of the input required for the deploy will be in the PDF), so we need to agree on this to move forward. BR, Alex [1] http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-18-15.02.html [2] https://gerrit.opnfv.org/gerrit/#/c/42017/ [3] https://gerrit.opnfv.org/gerrit/#/c/42233/ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alexandru Avadanii Sent: Friday, September 15, 2017 9:03 PM To: Julien; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: Charalampos Kominos; Guillermo Herrero Subject: Re: [opnfv-tech-discuss] [infra][pharos]Is PDF feature supported by installer project now? Hi, Fuel and Armband teams are working on the final bits for switching to PDF. We proposed a minor improvement to the parsing mechanism [1]; a PDF file for our arm-pod5 is already in place [2]; lf-pod2 PDF will land shortly (we have an internal draft we are currently revising), and of course an installer adapter that is still being tested before the final switch [3] (will be moved to securedlab when ready). Overall, I think the PDF is a great idea, and we should switch to it as soon as possible. There are still some minor implemention issues on the installer side (e.g. trying to determine the jump host bridge names in case they already exist), but I will bring that up after I try a few more things, as I think the current PDF format is enough to handle all of this, with some minor installer-specific parsing. BR, Alex [1] https://gerrit.opnfv.org/gerrit/#/c/42075/ [2] https://gerrit.opnfv.org/gerrit/#/c/41005/<https://url10.mailanyone.net/v1/?m=1dsuxP-0007wX-55&i=57e1b682&c=7uVUYZjML7cfZz7g5nCmecerAsQZ5DgpI-BmdQM53e9a0aB-NenDwRoGlmVU8SuFTWYYWP74Jcmxg2XIBlfXFnEOtGahV3un-a61y97mVpvT50Vcak5SDI6liT_s6Me5AXFfHp2jl7-ZlI36AhllAJMbqsPQOaEgTcFLoup1vOV0Q6NIwtshr9mtmOqVPMZwD8qIH_PU9pkbRhpEb4Fqbz5OclxDFzXcxzhvwwM38FjQO9MPqhlfjHik-bdwaoWE> [3] https://gerrit.opnfv.org/gerrit/#/c/41855/8/mcp/reclass/classes/cluster/all-mcp-ocata-common/opnfv/pdf/pod-config.yml.j2 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Julien Sent: Thursday, September 14, 2017 7:21 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [opnfv-tech-discuss] [infra][pharos]Is PDF feature supported by installer project now? Hi, dear installer PTLs, In this week's infra WG meeting, we discuss whether PDF(Pod Description File) can be released or not. We want to know current status of each installer project. As I can find in the wiki, all the installer projects in OPNFV, including Apex, Compass, Daisy, Fuel/MCP and Joid will attend Euphrates release[1]. Currently, some PDF files have been submitted by pharos lab owners including Ericsson, Intel, LF and ZTE. Several labs' PDF files including ARM, BII, Huawei and Nokia are in review[2]. Aric has finished some installer transfer script in scuredlab repo[3] using jinja template. This feature is planned to released in Euphrates. If it is not supported yet, can you share us current status and your plan. [1]: https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status<https://url10.mailanyone.net/v1/?m=1dsuxP-0007wX-55&i=57e1b682&c=GDxkn2Tq8vML2rviSS3r5MaQmT--LKHjVUOIxO2-cenrRVW2I7-r3O9aR2mzwYFItZ93N0Kq0jJoZiZJXMag0N4que2GEd3nVj89SljClyQQyloZ5qygqvVSkTFYfLPl0RVzQoylRCyTQTwv6grBdKgvOMJVF52EGGdKfu1DAajOr-AU6gm5ryM_LOQPDG66pR1jy9dx6dw5TWUwpg9_R_T5x1X6uEHQkYG9k-Og0vJ45Lu4PpAs58Ir66xgK1P0NYDy42yw4coOQA3FCN5VP4zrHNlZHJKKg7IQaJxa_vpYgmryFbw3jZ5b4Z5haY-rvnK_gbzASLpBKwYC7cegWIvSFR38I9tzv4wrbu5L9Y3k3BYsbgoOrtcyqrzfjYSiQw-0OrdJSKNjwCcniqYMNlKMbaOflu-tmAZg3YHj9g4TJL5z2qwPNzK1Iq7GJN4YteF2SbB-t6JjUjcFwEY4fGGRLOsitWTtujAu18IwiCNk7gbJcuzNVY0n-8Jtwhejfso3nc5Mv1Ur8Qb4W0uXF-jsFF6oHUZv0AgQnEbgIleGNIzUnJVinWgFznQlZL3DU9WMtd9eaTNQsQoU4uct5brL9o4u1si_YPtKsRSriJ2Lpcxr2QUaAMTxgL_4SEa7gzMIpD_9lcmJEZ6_sP4_-g> [2]: https://gerrit.opnfv.org/gerrit/#/q/project:+securedlab+status:open<https://url10.mailanyone.net/v1/?m=1dsuxP-0007wX-55&i=57e1b682&c=hYS7a1DoaKo8p10ANUdJqmrQziJKaDasruh91_olxbmPm1HAz4Frty7AXdHLc4yYOYclwcnVtubVGEPu8s-2AjbcA1aAsCJtrcwPOjo1U4wEXeAnS0PQhng7g97vW9LyZtZDGJpRGcbd15BxL51QqkZYAyQfZyyVqdzgjY55vHpaFfYQZfmh-QyDt7ZVTiRM6-7Zw4ssEmrhG86S4Yc0EYe9D54gkiB_lphCbbb6sEv_SthpjrDtNzsuIU9_ogzoeDeVC_ghYSaeRxvZn7zXAe4TPCxhKi1QPW5lCuHwcz3mDlt7AW6FGOw3uCRxTJ0HorIj_AsaGiu9SV979rb_mvzTkOKRi2waRNsGplnGtWwV9l8B_uFfb8T9fZBZm2VongTwVHK25QQXowmIOh-KwIOC-6aFAG-1U1xl8RveCR5cIFLHkY4dTvLkto0BHUk6KZZlllDKWFDBtDvLrR7L75jwbkZ2atN12fPOaJA2Bw6kp0cLQl4UnTJm7K18DozQhn4h7xsaXPEr23yedm4pGx66yPrjsCIXAiRS3tqZ5bmxhVCNws1fW_klRxU_lY7V7mRVvWQmFDLhKrM9BVuJLcYQ2YPaPo4fI7EaKsePwRUvxRys8ZpGeVyp7sOxVFtl8Q5uMsZViCt9C71S6Wuigg> [3]: https://gerrit.opnfv.org/gerrit/#/admin/projects/securedlab<https://url10.mailanyone.net/v1/?m=1dsuxP-0007wX-55&i=57e1b682&c=D1Rc2lMkwVgxluIDreMZhdmG5cd59vaXeYuX56BWHcx4cFjOfpRt0LEVhzUGN3zQE6unzcXtbqzU29-4xpJ68HdquURAG0QD-6JIvqbuUiPnalrGFHwQQJQU5_GGdYpxVvWPVem5Vb3rlycmSvHSR7LjWRxnaEIjvaDE6Cv-9FSV_XFkuq2n4J1uH7ER-lm_01sDJD1pJ7IV6YDBvbaF3bCGELisMIDJyex-L5koahjYEUL3MyBobuE1jq8pVjVkmwItzo7NDlkL4QfRJWym07hLMHGFPdmskXM9JexaFt2kQpgzWWAIp1jNCOn1_eHMXdMuU2qE1HSPU2cCVQd1OJ3n4YjGzmXG53lo4Bs2b_3M0Zs4QuRKMrlIO1qU3CwVCXv2f2lmDk7QZ4j49OE4X1SaStXlK2aEihDglKMtiWaEJ1yk2mMubmKdyM6F1m_aX_W6FUcQ6dBVD3G_sgKlZnUwM7GJ5RscNDufD3QhV-z6psOG9BLHreKhShn-Ty9XP0d6yMn0kRhhr3tclas38BmRk_mIYHyV6_rT6y7W2UYH6l7fQoI-7eg02n7oe4em2tL9OT9MjJdoX1N8H4Pwe9kAneBbeNsbOgKaepMEWIYBwO-bBc5tPuJjmpr6JeUeirnSsZmzBzoKxpq1ftlstA> BR/Julien
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
