Hi David, I agree your comments about net_config in [2]. Before my holiday maybe I make a mistake that I think IDF is used for infrastructure network descriptor. For Jobs naming, I think in Kubernetes, we still need to resolve the usage of network and storage, while these features are not well supported in the Kubernetes community. Control is equivalent to Master, and Minion is equivalent to Minion. It is difficult to define one set of names to meet all the requirement. If someday VMware or HyperV is introduced into the community as VIM, the names are meaningful to the new VIMs?
<david.blaisonn...@orange.com>于2017年10月16日周一 下午4:26写道： > Hi everyone, > > I agree that the PDF/IDF definitions must be fixed ASAP. > > - *About net_config in IDF*: I think it is a bad idea. As i answer in > the patch #42233 [2], if the L3 network is configured in the infra > (firewall, router, ...), and not configurable by the installer, it must > stay in the PDF. If the PDF leaves an empty L3 network section, it could be > fixed by the installer, and configured in the IDF. > - *About net_config as proposed by **Guillermo Herrero in #42893 [1]:* > +1 with an official naming less openstack 'like'. For a better > understanding and writing by infra ops, can we authorize comments > describing what is this network in simple name (and openstack 'like' naming > if the author like it)? We must consider that ops may not use the same > convention in the data center, and pdf writting must not be painful. > - *Jobs naming: *Today, jobs in IDF are also openstack centric and can > only describe a ha or noha mode, but not both, I propose in #42233[2] that > we use 'infra', 'worker' and 'infra_or_worker' as naming for main node's > job. This will let SDF file describing what is the mapping to openstack, > k8s or any other vim naming. > - *storage definition in shared IDF part [3]*: Julien propose to add > the storage definition in IDF, I agree, but it must be consolidated. I will > comment in the patch > > BR > > David > > [1] https://gerrit.opnfv.org/gerrit/#/c/42893 > <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml> > <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml> > <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>[2] > https://gerrit.opnfv.org/gerrit/#/c/42233 > <https://gerrit.opnfv.org/gerrit/#/c/42233> > > <https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml>[3] > https://gerrit.opnfv.org/gerrit/#/c/44603/1/labs/att/idf-pod1.yaml > <https://gerrit.opnfv.org/gerrit/#/c/42233> > > > -- > David BLAISONNEAU > NFV platforms DevOPS - OPNFV contributor > Orange - IMT / OLN / CNC / NCA / SINA > > tel: +33 (0)2 96 07 27 93 <+33%202%2096%2007%2027%2093> > email: david.blaisonn...@orange.com > 2, avenue Pierre Marzin 22307 LANNION Cedex - France > > Le 16/10/2017 à 02:25, Julien a écrit : > > Hi Alex, > > It's a great news. > 2 PODs in our lab reserved for MCP are blocked to deploy in master branch. > Can you give me a PDF/IDF link which are used now, then we will submit > PDF/IDF patches according to your version. > > For **net_config**, I personally suggest to move it to IDF and get the > template/format approved ASSP, for it is really important to us. > > BR/Julien > > Alexandru Avadanii <alexandru.avada...@enea.com>于2017年10月15日周日 下午9:44写道： > >> Hi, >> >> Fuel has been using PDF and IDF for weeks now. >> >> We still rely on net_config, which is out of spec, to map between PDF >> networks and the network role within the installer. >> >> Apart from net_config, we still need to sort out the mapping between >> interfaces indexes in PDF and the interface names inside OS (e.g. iface 0 = >> eno1, iface 2 = enp1s0f1). >> >> >> >> For net_config, Guillermo proposed an alternative as a comment in [1], >> which imo is closer to the hardware view of the setup (especially the >> port_matrix part). >> >> For iface name mapping, we will probably add it to IDF as a Fuel-specific >> section for now (no PoC proposed yet). >> >> >> >> BR, >> >> Alex >> >> >> >> [1] https://gerrit.opnfv.org/gerrit/#/c/42893/6/labs/lf/pod4.yaml >> >> >> >> >> >> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: >> opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Julien >> *Sent:* Sunday, October 15, 2017 12:38 PM >> *To:* Jack Morgan; opnfv-tech-discuss >> *Subject:* Re: [opnfv-tech-discuss] [Infra] Infra WG Weekly Meeting >> Minutes - Oct. 9th >> >> >> >> Hi Jack and Infra team: >> >> >> >> This week I have a chance to directly discuss with installer team: Apex >> and Compass. I still can not contact Joid. >> >> >> >> This is the status of PDF in each installer: >> >> >> >> Apex: Not started, won't support in E release, and I have submitted a >> Jira ticket in Apex. >> >> Compass: Not started, and plan to support in F release >> >> Daisy: PDF is supported and used in CI PODs for deployment, while IDF is >> not used for now >> >> Fuel: Started, not finished yet >> >> Joid: No response in email and IRC(#opnfv-joid) >> >> >> >> I would like to suggest to clear PDF/IDF patches in gerrit, let's make an >> acceptable template and update them in the future, then the lab owners can >> submit their PDF/IDF and used for deployment. >> >> >> >> BR/Julien >> >> Jack Morgan <jack.mor...@intel.com>于2017年10月10日周二 上午12:38写道： >> >> October 9th >> >> *Agenda:* >> >> 1. Status update on PDF >> >> · complete discussion from last week as this is a deliverable >> for Euphrates release >> >> 2. LaaS and Dashboard integration Lincoln Lavoie >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=1IFLKZX5m-w0jQVJ5jKOFTYO7F6xOB6uhW0HliHa_qhFYHQbCgqPd_7z-PcOplBM_XsJaRrrND6tLlpvnOy0EcMi4rQvCGaIpiDit0Qn_vrbvc6Gc0p2_RpO8QfVna-rnESF04QP9JvQWJFXbJhH3nRZChwv5eW5YyfcgFFvvHVdOUepLOAmoKkBh_gKXbqLV4ztzfr9Ep4FoNlyp1oBXLgwPyiG7PIJsLaJ2sJKsHXGr_L8E2HcfSyqQoDRggGk> >> >> 3. Infra documentation on RTD - patch 40329 >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=R3smn9KMUV4coY97MEbnSr5yc5wbiwHo7iTzbVVVZh-UBn7Uy7tj2tVtmNc9P1mkm4ETDwfjFlxDyAnXoZCzhWjT303o6iJAPB2lvRWP5MIR2nr24v2kpxlc_4CpgzBsyF18_RiEJ4PWRTWFPTIvXRKUnXJVi9zDFMhtXih8jGtlqajSV3QK60gIg1N0U-pi-PuGQ4RqO7K3HorX0WIlk4ArP9cBsrOFwcCQhC2B7GS5vSuQ5c44O6O2YghGUOwJ> >> merged, >> what else? >> >> a. Discussion of Infra documentation >> >> 4. Zuul v3, Fatih Degirmenci >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=is70_YbviOZLKdDVg7G0GT7mi7Pl9P_RyyejcRkSk_KH3oTKeyS91Pg1hiWAr8WXwM6yRk7-4DYMolLZrkoPAZ6q1XXAAqJEZtjAsmWXXmy2siatCe_SAW7UeY-LCC0qoOWJ6IETo_Nl2CphSsrk54HFtmxMs0lEBgbHRtrWg6dv8zy8OpIfPu6tzbQc3Wes09BKcPdkbKJqzPrpYKzYDBaKoZa0gYRhcKUlILQ08wv_jTlIQxPZPimLlv-fLQGB> >> >> . possibility to start a prototype? >> >> 5. Follow up on security audit job logs RELENG-272 >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=wES3NshmpEfrUpqgTRuPoxbpwEKKOxH1CrN36Clv-z6aP_TkC9pTSo5yr7EiwrjUtZcASXoX_Oxg-OA4r4pCnfD6Hcq8CRpOAxcT4L_U8V2ky7mRNosDfSOakUCa2e_hZynjMk9YFWCXVX9GbVIY1hZScJomcqpT31hdUrGI_qf8wc296mZ3nom_L8FFhfokwmSveMkkFnEnQBE3UKuLehAh5euUhR_gWP3BjwYjgTqx3KE--iIta3bm3GbfWt3v> >> - Ericsson Build 3 not reporting failures to comments *IN PROGRESS* >> >> 6. F Release participation >> >> 7. Review actions items >> >> *Minutes (*link >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=khjviKurcBef762jqBOj6fK_jj_cnNMQ5SK34IPrXlkXWn8QLrfOTumzKM-Tv0Q3F_8Rmz7mV609OlH00ThzNKaIGHQIJtz13i_VlrOhPsAlTE8u7GeApYKuFjipEF1Vm6Gnb4rJvDGQHAV5vPnYSrwTwaelmjOOjN1Ybzhk1nMlx3sfjUjTOe5PC-j8b63pcjJJ7QOWD13lQNjHi2165tv_c6Y3qS2zgKsISbCE4HDXMyauI6HVrW8I4PB9HKdOzXbve8QfgIEARROwdJN9-uL686lUdMo_KCtMoGaIy7Nl2iYQVTPznLMykjGSjA88> >> *)* >> >> 1. *Status update on PDF * >> >> · David_Orange reports that IDF is mostly complete and haven't >> heard any feedback during the last week on his patch below >> >> · work in progress patch >> https://gerrit.opnfv.org/gerrit/#/c/42233/5/labs/orange/idf-pod1.yaml >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=JGvldXYsL6-yPn6p2-BDr7n23bbftYxnOFSguy-2wr60Lq5WveeJKYHw4FuCnDBm4loJflpzBlGJ9EoA73d76R1ZFvG30plPuakukmvRPsHS8zbwR63zRaGTRUU6id-P3PM3P4TklKQLkXBS5B_mZ39yu4rzUc3dzRB0pzE5LocwcgxQw9V4bIkm-gn-6861v9OgqY2DXHB1H9OllR-QcL7anB72n8hXat400JRJVWvuj3aIghXX9CemEe6er5PkssxAjWD2m7ZPsPxvqHDMTjwRl7CozOOJGjWpogzwJQ8> >> >> · current SDF patch https://gerrit.opnfv.org/gerrit/#/c/36977/ >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=SLvPkpc4DhEXcLpl5Ei1Xzh0H-qoaoRf-i4tv3xIi9ELH2_BLYNwGwQXewbsxfRXu_cFYMc-qdkm9oIBGM_9YT43NZd3Bc72Y-5zNO9ZWNqgPQtx55wlaug7-tQuRPhKET6hCtR4gcoRN9IBWBzXqKnWBIzQOSVOtdQydTjRJU0NepKaa-FrQoEyldQx-ITGomwrwvOSTDoiyVTUA_ir_MpAfJSgoB8RUALi_22hy7DuZhPtEbqvyaE8CgZswkbd> >> >> 2. *LaaS and Dashboard integration* >> >> · lylavoie is working on LF hosting issues with bramwelt but >> will focus on it after the release >> >> · requirements gathering and plan is being tracked via Dashboard >> Roadmap >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=rARNFo3VKxZJMwVWTzbKK4-7dBPgi8e8WNN5FXWINE_1vD6jZUexW5phVMo5rheREpjXSvQoUReMdExGOZfJ2UJJf_ZDp_RT84kVhiuwN_v-HZbXvTdiFOzJhDan_jeM00wMQXVZ4bSN1z8d1VNidCm4Vzkl3MV7gLt2BEfYouUg7l8B4fG8157ZP82Swt4-tPUJhIQPXhkLqjamxlCBhBTAlJpmp7CPMiK3ArLZIDFGHqglTD6hQvvX9j3YfTCx> >> >> 3. *Infra documentation on RTD* >> >> · initial patch 40329 >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=R3smn9KMUV4coY97MEbnSr5yc5wbiwHo7iTzbVVVZh-UBn7Uy7tj2tVtmNc9P1mkm4ETDwfjFlxDyAnXoZCzhWjT303o6iJAPB2lvRWP5MIR2nr24v2kpxlc_4CpgzBsyF18_RiEJ4PWRTWFPTIvXRKUnXJVi9zDFMhtXih8jGtlqajSV3QK60gIg1N0U-pi-PuGQ4RqO7K3HorX0WIlk4ArP9cBsrOFwcCQhC2B7GS5vSuQ5c44O6O2YghGUOwJ> >> has >> been merged, what else needs to be migrated >> >> · bramwelt has some documentation to post but not sure which >> project it goes >> >> 4. *AoB* >> >> · bryan_att mentioned that the Equifax breach was due to Apache >> structs vulnerability >> >> · bryan_att suggests we need some discussion on potential >> scanner tools for production deployments >> >> · Luke will investigate ODL scanning and bryan_att will bring it >> up at the TSC >> >> · jmorgan1 mentions this is a good Plugfest topic >> >> 5. *Action Items* >> >> · contact installer PTLs support of PDF in Euphrates >> >> · Fuel/MCP and Daisy4NFV has support for PDF, Compass4NFV will >> delay working on it until F release >> >> · Apex and Joid have not responded to emails >> >> · closed and new action items below >> >> *Closed Actions:* >> >> · Contact installer PTLs for support of PDF in Euphrates julien >> zhang >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=vspuURuKXW3sIU3YQpYOAlk423lgFFykXupnKa6WAZNuL-TwwOCBbN8o4nDIVtQIy4ZZS5b1VEgHZrtnDPoJxs6YfkGgm_GzaDry6vXmhPN-D8F5sQ4Iaqx5yPfWYy95fbLkUwiAy_rOZ5UNyCr0YD4ImbJquhJbcUj2hhL_L5zth5Dpuf8nfBv5Y64eFgFfLMPVVvzc8rlw_y8ijZoMAObJAkt6dUQTP4aZlBeie36bowMzpisNNN8ZWSC91LWF> >> >> · Submit patches to add lab owners and others to Pharos repo Aric >> Gardner >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=RwpSsMmYs9y-MHxcTzelx35DBQPCEn1xjscTtWtuGvwpECuHWPuRd4lQdJ_q-kfOh6L8eg-U8leMliLJvtTU0K4ZJRJ2-csYKDdTJGaUFliFlL6xZJdsv9cVtaP1uX-16Z5CTXWBLn4x2jIe598f9XZulb4S9YWCv0eHejfSA2-okmBg_pYv-gkPJVJCzW34wkqDinkh183oGLQ1m_fH1uGS7_gowzjtDesPaqAdtajn8oo-lf10oj94sSDgKn-0> >> >> · Reach out to lab owners to collect feedback on including >> username and password in PDF Jack Morgan >> >> · Reach out to Luke Hinds >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=XwKHUdMq8y6j7l7h0pTx_88Q1VNKNVQiIsl-yi_K9_K8hw3sjBw0eco6fcn_DXGWN4_ERirus3j5WcjcXCzgO0SD5MMx_C4h1kWtkNkWceg7LN9ZU--y6tHR3acZfA0QN3RkfAECXu4WWWPUsrPFoqg_Zln7xfeK2_iYkwoSZB2MB-vRVenOeeO0nBwY1p51AVfjjOJlCHh-N10iW-Hs-wXP4SvPNGfKD_BO5ailB4kf_1d0-xF4EyiZCcQD7gnB> >> to >> security projects input on passwords in PDF Aric Gardner >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=RwpSsMmYs9y-MHxcTzelx35DBQPCEn1xjscTtWtuGvwpECuHWPuRd4lQdJ_q-kfOh6L8eg-U8leMliLJvtTU0K4ZJRJ2-csYKDdTJGaUFliFlL6xZJdsv9cVtaP1uX-16Z5CTXWBLn4x2jIe598f9XZulb4S9YWCv0eHejfSA2-okmBg_pYv-gkPJVJCzW34wkqDinkh183oGLQ1m_fH1uGS7_gowzjtDesPaqAdtajn8oo-lf10oj94sSDgKn-0> >> >> · Create wiki page to track next steps and features for >> Laas/dashboard effort Lincoln Lavoie >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=1IFLKZX5m-w0jQVJ5jKOFTYO7F6xOB6uhW0HliHa_qhFYHQbCgqPd_7z-PcOplBM_XsJaRrrND6tLlpvnOy0EcMi4rQvCGaIpiDit0Qn_vrbvc6Gc0p2_RpO8QfVna-rnESF04QP9JvQWJFXbJhH3nRZChwv5eW5YyfcgFFvvHVdOUepLOAmoKkBh_gKXbqLV4ztzfr9Ep4FoNlyp1oBXLgwPyiG7PIJsLaJ2sJKsHXGr_L8E2HcfSyqQoDRggGk> >> >> · Reach out to Joid, Apex and Compass need to provide a contact >> for PDF effort julien zhang >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=vspuURuKXW3sIU3YQpYOAlk423lgFFykXupnKa6WAZNuL-TwwOCBbN8o4nDIVtQIy4ZZS5b1VEgHZrtnDPoJxs6YfkGgm_GzaDry6vXmhPN-D8F5sQ4Iaqx5yPfWYy95fbLkUwiAy_rOZ5UNyCr0YD4ImbJquhJbcUj2hhL_L5zth5Dpuf8nfBv5Y64eFgFfLMPVVvzc8rlw_y8ijZoMAObJAkt6dUQTP4aZlBeie36bowMzpisNNN8ZWSC91LWF> >> >> · create POC on encryption option Aric Gardner >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=RwpSsMmYs9y-MHxcTzelx35DBQPCEn1xjscTtWtuGvwpECuHWPuRd4lQdJ_q-kfOh6L8eg-U8leMliLJvtTU0K4ZJRJ2-csYKDdTJGaUFliFlL6xZJdsv9cVtaP1uX-16Z5CTXWBLn4x2jIe598f9XZulb4S9YWCv0eHejfSA2-okmBg_pYv-gkPJVJCzW34wkqDinkh183oGLQ1m_fH1uGS7_gowzjtDesPaqAdtajn8oo-lf10oj94sSDgKn-0> >> >> · >> >> *New Actions:* >> >> · work on putting infrastructure documentation structure in >> place Trevor Bramwell >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=FhS4joUAnjINvU62oZ4Y3GG76npQeXk8PhSp74SqZAP4w_VTlBn5cAI0ELSBcbPsHY8qZc2TzR0HEjl4H2jSrzyShM1J3L2plqEvZHCZWVBu-g8K-BuOblrO8b19CXsbVaxj1OEyHVVa0CReotTVdvfkVMrsIIQYe5EE-sm_4AUs-xkB1neczCY00DMgRWXNSooa8fcLJeUALbDtohVIR5Dwg33Rtgi9SYesGf8U9wM6pBomQseAGqbsZ1_yeEJc> >> >> · work with lylavoie to get CI Pods displayed on labs.opnfv.org >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=-abuWwcOrOWHEzLmD-wChlBv24RP2VdU9s2naSwWtqzy8KTmyo_d9g38goszs3EqB62fLaOsM7UKgwKly32DfqQccTuHiuVkuxcI5zElM2B32jGj0OecKQnRIT4-ENHm5szFoBEtmDu3XlipRerzyT2jpLDEOPclAIWaaVoBujeIVh2rzaauT5x331gz8PTGswyYvdgFrs9KvgPw_bZSHJof6BXpeHp_4o9ghCH_uRY> >> Trevor Bramwell >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=FhS4joUAnjINvU62oZ4Y3GG76npQeXk8PhSp74SqZAP4w_VTlBn5cAI0ELSBcbPsHY8qZc2TzR0HEjl4H2jSrzyShM1J3L2plqEvZHCZWVBu-g8K-BuOblrO8b19CXsbVaxj1OEyHVVa0CReotTVdvfkVMrsIIQYe5EE-sm_4AUs-xkB1neczCY00DMgRWXNSooa8fcLJeUALbDtohVIR5Dwg33Rtgi9SYesGf8U9wM6pBomQseAGqbsZ1_yeEJc> >> >> -- >> >> Jack Morgan >> >> OPNFV Pharos Intel Lab >> >> _______________________________________________ >> opnfv-tech-discuss mailing list >> opnfv-tech-discuss@lists.opnfv.org >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >> <https://url10.mailanyone.net/v1/?m=1e3fNf-0006XB-4X&i=57e1b682&c=fXpStdg_FwlfJV0QfykxiJISnm-IR_YG4mJNJCi62u5XnuAFvHTyAO5iKvorY_frTeinYGB7DTGDzRJ5lozgBnBVAp4ht0vneiZcQkmoUd6yrZG7aJfEp_cEngLsqMICfsJFMcaodKFzoESlz-R4M-VccyOuH6fJsQroQ1yRrRRfxuY2y595Dcq3qS-rONUXd_AM7gxulvhzhZs4qb-hdw9IScpuKwKhySNtDJg0btkbMonMP-PeOWScC2yIhaE3yU0GFeORjZU7wvwEyJA2ww> >> >> > > _______________________________________________ > opnfv-tech-discuss mailing > listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
