=========================================================== #opnfv-meeting: OPNFV RC0 Meeting - Release image readiness =========================================================== Meeting started by ChrisPriceAB at 14:00:45 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-04-02-14.00.log.html . Meeting summary --------------- * roll call (ChrisPriceAB, 14:01:06) * Frank Brockners (frankbrockners, 14:01:10) * Chris Price (ChrisPriceAB, 14:01:12) * Fatih Degirmenci (fdegir, 14:01:18) * Aric Gardner (aricg, 14:01:27) * Jerry Zhao (jerryz, 14:01:30) * Agenda for the meeting (ChrisPriceAB, 14:05:25) * RC execution reporting and issue logging – Fatih/Aric (ChrisPriceAB, 14:06:09) * Project reports on RC completion and next RC readiness – Project Leads (ChrisPriceAB, 14:06:21) * Actions and activities planned - All (ChrisPriceAB, 14:06:31) * any other topics people would like to see on the meeting? (ChrisPriceAB, 14:06:45) * RC execution reporting and issue logging – Fatih/Aric (ChrisPriceAB, 14:07:24) * Fuel and Foreman images have successfully built and stored on OPNFV Artifact Repository (fdegir, 14:08:06) * Links to Fuel ISO and build logs (fdegir, 14:08:25) * LINK: http://artifacts.opnfv.org/genesis/fuel/opnfv-32.iso (fdegir, 14:08:36) * LINK: https://build.opnfv.org/ci/job/genesis-fuel-daily-master/32/consoleFull (fdegir, 14:08:46) * Links to Foreman ISO and build logs (fdegir, 14:08:55) * LINK: http://artifacts.opnfv.org/genesis/foreman/opnfv-4.iso (fdegir, 14:09:02) * LINK: https://build.opnfv.org/ci/view/genesis/job/genesis-foreman-daily-master/4/consoleFull (fdegir, 14:09:12) * Fuel and Foreman Daily Jenkins jobs have also been enabled (fdegir, 14:09:31) * they will build latest master every night and store latest images on OPNFV Artifact Repository (fdegir, 14:09:48) * Any questions on the RC0 status? (ChrisPriceAB, 14:10:21) * is ISO required for other installers to make it to R1? (jerryz, 14:10:59) * could the link be posted with reqs for R1? (radez, 14:11:41) * Arno RC schedule is here (frankbrockners, 14:12:05) * LINK: https://wiki.opnfv.org/releases/arno/releasecandidates (frankbrockners, 14:12:07) * jerryz: That is the expectation, it would be very hard to catch up when we have only 2 RC - deploy weeks (ChrisPriceAB, 14:12:51) * Metadata for Fuel and Foreman are also stored on Artifact Repository (fdegir, 14:13:04) * The SHA1s used for building ISOs are stored in metadata files (fdegir, 14:13:21) * LINK: http://artifacts.opnfv.org/genesis/fuel/opnfv-32.properties (fdegir, 14:13:29) * LINK: http://artifacts.opnfv.org/genesis/foreman/opnfv-4.properties (fdegir, 14:13:37) * thanks fdegir, any other questions/comments or I will move on (ChrisPriceAB, 14:14:03) * ChrisPriceAB: we can get deploy.sh to work but build.sh still need some work for Compass (jerryz, 14:14:20) * yes we will do R1 planning and actions as the last point (ChrisPriceAB, 14:15:12) * Project reports on RC completion and next RC readiness – Project Leads (ChrisPriceAB, 14:15:18) * frankbrockners can you report on BGS? RC0 and moving to RC1 readiness (ChrisPriceAB, 14:15:45) * Sent out a request for status to the alias yesterday. Got details for Foreman and Fuel deployment approaches. (frankbrockners, 14:16:33) * Details are summarized on the BGS wiki as part of the release plan (frankbrockners, 14:16:54) * LINK: https://wiki.opnfv.org/get_started/get_started_release_plan (frankbrockners, 14:17:08) * For RC0: Successful built for Foreman and Fuel deployment approaches (frankbrockners, 14:17:43) * For RC0: Common puppet manifests mostly in place - some patches still in gerrit. See wiki for details. (frankbrockners, 14:18:40) * Q: So equivalent of code freeze achieved, with bug-fixes pending? (ChrisPriceAB, 14:19:13) * R1 readiness: Teams active on deploy scripts. (frankbrockners, 14:19:15) * R1 will also depend on LF infra fully available. (frankbrockners, 14:19:34) * "bug fixes" pending is appropriate (frankbrockners, 14:20:03) * One clarification would be good to have here: (frankbrockners, 14:20:27) * R1 question. Can we get a description on the wiki of what "deploy.sh" is supposed to do exactly. Just want to have the right expectations clear for everyone. (trozet, 14:20:48) * Teams are working on the assumption that "deploy.sh" will *not* include any testing. I.e. testing is run *post* installation and is independent from deploy (frankbrockners, 14:21:06) * Is this everyone's understanding? (frankbrockners, 14:21:24) * erm: Yes. Deploy should install the SW, validation shall occur post install as a standard functest suite. (ChrisPriceAB, 14:21:43) * but testing may need some input from deploy.sh, url, username, password,etc (jerryz, 14:22:06) * Robot and Tempest would be installed independently from any install/deploy approach (frankbrockners, 14:22:20) * as part of post install processes (rprakash, 14:22:44) * Q: As part of RC1 readiness have we identified consistent user names and passwords to be used? (ChrisPriceAB, 14:23:32) * how about self-contained virtualized deployment test (jerryz, 14:24:02) * foreman has tempest fired off as part of deploy but it can be separated without trouble (radez, 14:24:35) * ChrisPriceAB: no I don't think we have standards user/pass. We have been using octopus/octopus for all OpenStack user/pass and "Op3nStack" for linux root login (trozet, 14:24:43) * ACTION: BGS team to resolve consistent user names for RC1. (ChrisPriceAB, 14:25:10) * user names goes beyond BGS... - given that you have to reconfigure the switches every time you switch installers (frankbrockners, 14:25:52) * ChrisPriceAB: still have a question about deploy.sh (trozet, 14:25:59) * so an AI for pharos (frankbrockners, 14:26:04) * ACTION: Pharos team to provide consistent usernames for infrastucture. (ChrisPriceAB, 14:26:20) * HW readiness Wiring started yesterday, should be completed today. (aricg, 14:26:21) * so deploy.sh will not require to boot the iso created by build.sh? or deploy the install server? (trozet, 14:26:34) * my understanding is that deploy.sh will need to deploy the jumphost/install server (frankbrockners, 14:27:17) * trozet & bgs team please clarify deploy sequence details in the BGS project. (ChrisPriceAB, 14:27:29) * though it does not need to work off the ISO (frankbrockners, 14:27:31) * so build.sh iso needs to deploy.sh but not vise versa? (radez, 14:28:11) * for OPNFV purposes I would vote to use a VM and not rebuild baremetal install server with an ISO, for speed and reliability (trozet, 14:28:15) * CI readiness report. RC0 and moving to RC1 readiness. (ChrisPriceAB, 14:28:25) * CI jobs that verify changes that are done in genesis/common, genesis/fuel, and genesis/foreman are now activated (fdegir, 14:29:24) * go ahead Jerry (rprakash, 14:29:38) * any change in genesis repo that is still pending for review needs to rebase to master (fdegir, 14:29:56) * in order to get them tested with fuel and foreman verify jobs (fdegir, 14:30:15) * CI jobs created and triggered periodically for build.sh (jerryz, 14:30:17) * artifacts uploaded to google storage after each build (jerryz, 14:30:49) * Q: are the on commit and on merge jobs in place as well? (ChrisPriceAB, 14:32:07) * Jobs run for each commit are in place (fdegir, 14:32:40) * gerrit trigger in job template (jerryz, 14:32:58) * any commit that touches genesis/common, genesis/fuel, and genesis/foreman will trigger verify job (fdegir, 14:33:09) * Q: artifacts uploaded at each build or nightly? (ChrisPriceAB, 14:33:27) * artifacts are uploaded nightly (fdegir, 14:33:38) * no artifact is uploaded from verify and merge jobs (fdegir, 14:33:47) * work is still in progress for merge jobs (fdegir, 14:34:02) * RC1 readiness report, pending actions on Deploy & Test? (ChrisPriceAB, 14:34:22) * for CI (ChrisPriceAB, 14:34:36) * depending on how to test deploy, with what resource? (jerryz, 14:34:55) * We are waiting for BGS and FuncTest to provide mechanisms to deploy and test (fdegir, 14:35:19) * : deploy job template is there, no resource for deploy jobs yet (jerryz, 14:35:22) * We currently download ISOs from Google Storage in deploy phase as "dummy" jobs (fdegir, 14:35:47) * it will be replaced with real deployment once it is ready (fdegir, 14:36:04) * Q: so pending actions on functest and bgs to complete scripts in Jira? (ChrisPriceAB, 14:36:11) * correct (fdegir, 14:36:17) * slaves for deploy need to be in plae (jerryz, 14:36:36) * s/plae/place (jerryz, 14:36:48) * LF hardware is the prerequisite for RC1 (fdegir, 14:36:56) * as we lack build and deploy resources at the moment (fdegir, 14:37:14) * OK, more question on CI? otherwise I will move to Pharos (ChrisPriceAB, 14:37:20) * Pharos (LinuxFoundation infra) RC1 readiness report? (ChrisPriceAB, 14:37:51) * artur did you create mass juju fillers for rc0 in genesis (rprakash, 14:38:00) * Wiring started yesterday, some hangups, should complete today (aricg, 14:38:29) * ok done for ci on juju track (rprakash, 14:38:51) * Q: will we provide scripts for deploy tools for switch config etc? (maybe a better q for trevor_intel) (ChrisPriceAB, 14:39:29) * rprakash yes (arturt, 14:39:39) * ChrisPriceAB I dont think that is necessary. We have an agreed upon VLAN layout for the target system that should work with any installer (trozet, 14:40:07) * ok, thanks trozet (ChrisPriceAB, 14:40:24) * I have a different understanding (frankbrockners, 14:40:35) * depending on installer hosts send packets either VLAN tagged or not (frankbrockners, 14:40:54) * based on this, switch config would differ (either switch applies VLAN tag or not) (frankbrockners, 14:41:13) * no reason to use tagging unless we don't have enough ports per server. We agreed on this in the meeting yesterday. (trozet, 14:41:20) * requires clarification from teams (frankbrockners, 14:41:23) * action: bgs team to clarify if any abstraction is required from the Pharos project for deploy and add Jira jobs where neccessary. (ChrisPriceAB, 14:41:44) * functest RC1 readiness report. (ChrisPriceAB, 14:42:29) * is new project lead assigned for func test? (rprakash, 14:43:40) * the new commiters now have access. https://git.opnfv.org/cgit/functest/tree/INFO (aricg, 14:44:22) * currently the acting is trevor_intel, nominations have started (ChrisPriceAB, 14:44:33) * unable to secure functest reporting for RC1 readiness. (ChrisPriceAB, 14:45:04) * ACTION: ChrisPriceAB to secure functest updates and preparation for RC1 is on track (ChrisPriceAB, 14:45:42) * RC1 readiness for opnfvdocs (ChrisPriceAB, 14:45:46) * opnfvdocs repo was created yesterday, tooling is being prepared and we expect to get foundation templates in place over the weekend. (ChrisPriceAB, 14:46:18) * risk that we will not be ready for RC1, although I hope to have a clear structure and all Jira actions in place with templates by that time. (ChrisPriceAB, 14:46:45) * opnfvdocs team will help project teams complete the documentation in the templates in order to arrive at Release 1 (ChrisPriceAB, 14:47:33) * expected documents include: (ChrisPriceAB, 14:47:40) * - Release documentation (ChrisPriceAB, 14:47:50) * is all documentation work being scheduled through Jira? (rprakash, 14:47:51) * Installation docuemtation (ChrisPriceAB, 14:48:05) * - User guides, leveraging references to upstream documentation (ChrisPriceAB, 14:48:22) * - Test coverage documentation (ChrisPriceAB, 14:48:32) * the release documentation will derive from project source document files in order to enable the documents to be maintained with the projects. (ChrisPriceAB, 14:49:39) * opnfv docs while produceing release specific content will not replicate project specific infrmation (ChrisPriceAB, 14:49:59) * Ask: Can we agree on an RC1 milestone for docs? (frankbrockners, 14:50:24) * any questions on the opnfvdoc progress. (the little there is) (ChrisPriceAB, 14:50:28) * We can, due to easter being in the middle I am not confident on what to set as a goal. (ChrisPriceAB, 14:50:56) * How about "draft doc templates available to projects" (frankbrockners, 14:51:19) * tooling, templates and Jira actions might be a good start (ChrisPriceAB, 14:51:25) * ACTION: opnfvdocs project to ensure templates are available for all Release 1 projects by RC1, with associated structure and documentation 'guidelines' (ChrisPriceAB, 14:53:05) * Actions and activities planned (ChrisPriceAB, 14:54:41) * there will be an overall OPNFV doc describing the target deployment, functest, CI pipeline, and separate docs for the specific installers and projects (dneary, 14:54:46) * pending actions, let's capture needed steps leading to RC1. (ChrisPriceAB, 14:54:57) * LF hardware should be available by the end of this week. CI needs to move targets to the LF lab and begin building/deploy testing there. (ChrisPriceAB, 14:56:18) * for BGS/JuJu we gat POD5 next week so thats the wait for hold up you asked (rprakash, 14:56:46) * functest needs to migrate all work into the repository so it can begin to be tested against target automatically. (ChrisPriceAB, 14:56:58) * and functest infra (tempest, robot) needs to be avail on LF HW by RC1 (frankbrockners, 14:57:59) Meeting ended at 14:59:22 UTC. Action items, by person ----------------------- * ChrisPriceAB * ChrisPriceAB to secure functest updates and preparation for RC1 is on track * **UNASSIGNED** * BGS team to resolve consistent user names for RC1. * Pharos team to provide consistent usernames for infrastucture. * opnfvdocs project to ensure templates are available for all Release 1 projects by RC1, with associated structure and documentation 'guidelines' People present (lines said) --------------------------- * ChrisPriceAB (97) * frankbrockners (46) * fdegir (33) * dneary (22) * jerryz (14) * trozet (13) * rprakash (11) * radez (6) * aricg (5) * collabot (5) * bryan_att (3) * trevor_intel (1) * arturt (1) Generated by `MeetBot`_ 0.1.4