#opnfv-meeting: OPNFV Arno RC2 status meeting

Meeting started by ChrisPriceAB at 14:00:50 UTC (full logs).

Meeting summary

  1. roll call (ChrisPriceAB, 14:00:56)
    1. Uli (ulik, 14:01:04)
    2. Chris Price (ChrisPriceAB, 14:01:05)
    3. Heather (HKirksey, 14:01:26)
    4. Fatih Degirmenci (fdegir, 14:01:29)
    5. Dan Radez (radez, 14:01:37)
    6. Prakash R (rprakash_, 14:01:41)
    7. Trevor Cooper (trevor_intel, 14:01:52)
    8. Tim Rozet (trozet, 14:01:55)
    9. Jonas Bjurel ([1]JonasB, 14:02:26)
    10. Frank Brockners (frankbrockners, 14:03:00)
    11. Larry Lamers (Guest98285, 14:03:28)

  2. RC execution reporting and issue logging (ChrisPriceAB, 14:05:25)
    1. aricg, fdegir where are we with toolchain and lab status and task completion for RC2 (ChrisPriceAB, 14:05:58)
    2. Dave Neary (dneary, 14:06:02)
    3. Bryan Sullivan (bryan_att, 14:06:15)
    4. Build jobs are still in same state - up and running and producing/storing ISOs daily (fdegir, 14:06:37)
    5. Build jobs are still running on ericsson-build (fdegir, 14:07:00)
    6. We're starting with deploy jobs (fdegir, 14:07:08)
    7. do we have toolchain execution up on LF hardware yet? (ChrisPriceAB, 14:07:12)
    8. LF hardware is not ready to use from Jenkins as of yet (fdegir, 14:07:29)
    9. ok, thanks. (ChrisPriceAB, 14:07:46)
    10. Do we know what is required by CI to get going to LF hardware? (frankbrockners, 14:08:08)
    11. We need OS and needed tool installations done on LF HW in order for us to connect them as slaves to OPNFV Jenkins (fdegir, 14:08:41)
    12. Who is working the OS installation? (frankbrockners, 14:09:11)
    13. is there a Jira on that, and who has the ball? (ChrisPriceAB, 14:09:14)
    14. or a helpdesk ticket for that matter (ChrisPriceAB, 14:09:51)
    15. Why do we need a Jira there? Did we need Jira for hardware? (ulik, 14:10:16)
    16. pbandzi is working on with setup (fdegir, 14:10:20)
    17. but I'm not sure how far he will go with the setup/installation/configuraiton (fdegir, 14:10:40)
    18. It is pretty obvious, we need software setup. (ulik, 14:10:43)
    19. We should use Jira for activity and task tracking, seems like a task to be tracked (unless it's a helpdesk ticket) (ChrisPriceAB, 14:10:52)
    20. pbandzi has configured UCSs - and is in the process of installing the jumphost with base OS (Centos 7) (frankbrockners, 14:11:11)
    21. Is it a Jira in Pharos? (ulik, 14:11:20)
    22. to be able to deploy, wee need some decent documentation of the LF environment. ([1]JonasB, 14:11:45)
    23. One topic at a time please (ChrisPriceAB, 14:11:56)
    24. Ok, so is it enough to have OS up on the jumphost. Does our toolchain automate other nodes bring up sufficiently? (ChrisPriceAB, 14:12:29)
    25. ChrisPriceAB, thats the whole point of deploy right, it brings up nodes other than the jumphost (trozet, 14:13:55)
    26. If we will connect jumphost to jenkins and initiate deployment and testing from there than that should be enough (fdegir, 14:14:05)
    27. Builds probably need other hosts to be attached to OPNFV Jenkins (fdegir, 14:14:29)
    28. (hoping the IMPI etc. is up) (ulik, 14:14:33)
    29. Good, I like confirmation on the simple questions. (ChrisPriceAB, 14:14:34)
    30. other nodes just need to be set to pxe boot first, off their first interface (trozet, 14:14:35)
    31. Ok, tabled discussions. Jira actions on LF HW activity. Pharos documentation. (ChrisPriceAB, 14:15:15)
    32. So my take right now is we are in progress on the LF hardware. Currently using a hosted lab for the purposes of build and deploy. (ChrisPriceAB, 14:16:01)
    33. That is correct ChrisPriceAB (fdegir, 14:16:14)
    34. thanks. (ChrisPriceAB, 14:16:22)
    35. Foreman deploy work could start with intel lab until LF HW is ready (fdegir, 14:16:29)
    36. Fuel work will continue with ericsson lab (fdegir, 14:16:36)
    37. until LF HW is ready (fdegir, 14:16:46)

  3. Project reports on RC completion and next RC readiness (ChrisPriceAB, 14:16:50)
    1. let's move onto the project reporting. (ChrisPriceAB, 14:17:01)
    2. Do we successfully deploy by now? (frankbrockners, 14:17:01)
    3. Pharos project status, needed actions, incl. LF activities. (ChrisPriceAB, 14:17:47)
    4. 1) Spec file is in gerrit (trevor_intel, 14:18:54)
    5. 2) Infrastructure usernames is still outstanding but haev made progress with input from community (trevor_intel, 14:19:36)
    6. https://gerrit.opnfv.org/gerrit/289 (trevor_intel, 14:19:59)
    7. https://gerrit.opnfv.org/gerrit/#/c/289/ (vlaza, 14:20:01)
    8. https://gerrit.opnfv.org/gerrit/289 pharos spec file patch (ChrisPriceAB, 14:20:21)
    9. What I am not sure is how doc project inputs for this realease (trevor_intel, 14:21:08)
    10. let's discuss in the opnfvdocs update section (ChrisPriceAB, 14:21:27)
    11. Can we action Pharos to capture activity in Jira so we can track issues leading to next week? (ChrisPriceAB, 14:22:26)
    12. yes (trevor_intel, 14:22:37)
    13. ACTION: Pharos to update Jira leading up to Arno release (and onwards :) (ChrisPriceAB, 14:22:58)
    14. I already added a Jira ticket to request for documentation where we can help ; https://jira.opnfv.org/browse/PHAROS-1 (vlaza, 14:23:15)
    15. Octopus status update for RC2 (ChrisPriceAB, 14:23:29)
    16. fdegir has reported the main things already (ulik, 14:23:53)
    17. We are also working with reference documentation for Octopus (fdegir, 14:24:27)
    18. additionally octopus doc is in createion (ulik, 14:24:32)
    19. Does automatic deploy to some lab work already? (frankbrockners, 14:24:34)
    20. and working with BGS teams to get deployment working (fdegir, 14:24:42)
    21. Fuel deployment is currently ongoing on Ericsson lab (fdegir, 14:25:02)
    22. https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-daily-master/48/console (fdegir, 14:25:16)
    23. do we have Jira tasks for each deploy/lab activity and someone who owns them from the CI side? (ChrisPriceAB, 14:25:30)
    24. Here they are (fdegir, 14:25:55)
    25. Fuel daily pipeline: https://jira.opnfv.org/browse/OCTO-3 (fdegir, 14:26:22)
    26. Foreman daily pipeline: https://jira.opnfv.org/browse/OCTO-4 (fdegir, 14:26:33)
    27. Daily Pipelines include deployment activities (fdegir, 14:26:50)
    28. for CI (fdegir, 14:27:01)
    29. Lab details are excluded since we work with deploying to whatever we have (fdegir, 14:27:32)
    30. can I ask for an assignee to BGS Foreman Daily Pipeline: https://jira.opnfv.org/browse/OCTO-4 (ChrisPriceAB, 14:27:55)
    31. ACTION: Assign a responsible person to the foreman daily pipeline activity (ChrisPriceAB, 14:30:03)
    32. BGS status reporting for RC2 (ChrisPriceAB, 14:31:12)
    33. default username/passwd chosen: opnfv/opnfvstack (frankbrockners, 14:32:21)
    34. trying to deploy on Intel Pod 1. Intel Pod 1 uses different subnet masks, have submitted a patch for deploy to allow subnets other than /24. Hitting a DNS problem with Foreman install right now. (trozet, 14:33:55)
    35. have a fix for it and will retry, hoping to be done today (trozet, 14:34:07)
    36. Plans to deploy to LF hardware? (frankbrockners, 14:34:45)
    37. Will do when it is ready. (trozet, 14:35:07)
    38. build working ([1]JonasB, 14:36:43)
    39. 60-70% of docs in place and will be built in RC2 ([1]JonasB, 14:37:08)
    40. Autodeployment integrated with jenkins work done (ChrisPriceAB, 14:38:10)
    41. Deploying as we speek, and hopefully we can claim victory on that in an hour or so ([1]JonasB, 14:38:39)
    42. Ongoing deployment console https://build.opnfv.org/ci/view/genesis/job/genesis-fuel-daily-master/48/console ([1]JonasB, 14:39:17)
    43. On topic LF lab, yes we have plans, we have started integration with the CISCO Python API and the emulator. ([1]JonasB, 14:40:16)
    44. I have a question, once we get the LF hardware up there will be some resource contention I guess between deploy toolchain fixing, functest validation activities etc. (ChrisPriceAB, 14:40:21)
    45. do we have a plan in place to maintain order and keep things smooth? (ChrisPriceAB, 14:40:37)
    46. About resource contention: we can adjust the Jenkins job scheduling (fdegir, 14:41:05)
    47. As I mentioned, in order to prepare for LF, we need some environment documentation. ([1]JonasB, 14:41:20)
    48. can we action Pharos to provide a concise document? (ChrisPriceAB, 14:41:50)
    49. ... LF will produce this? (trevor_intel, 14:42:49)
    50. on maintaining order: We could consider using a LF HW POD per installer for the time being. It would reduce potential conflicts. (frankbrockners, 14:42:57)
    51. trevor_intel, no it should be a target hardware config document. Will need to be part of the release documentation as well. We need to set up an activity to produce this. (ChrisPriceAB, 14:43:37)
    52. ok (trevor_intel, 14:44:43)
    53. ACTION: Pharos to produce lab environment documentation, opnfvdocs and bgs to help (ChrisPriceAB, 14:45:18)
    54. pharos owns logical ... LF owns physical documentation? (trevor_intel, 14:45:28)
    55. ok, we need to get this together. I'll call for a gathering tomorrow. (ChrisPriceAB, 14:46:44)
    56. ACTION: ChrisPriceAB to rally the troups for environment documentation (ChrisPriceAB, 14:47:04)
    57. functest status reporting for RC2 (ChrisPriceAB, 14:47:27)
    58. Rally scenarios = Morgan who is out this week, vPing = Sama, vIMS = Martin, Robot = Peter ... (trevor_intel, 14:48:25)
    59. ACTION: functest to provide concise reporting on the mailing lists before the end of the week (ChrisPriceAB, 14:50:23)
    60. opnfvdocs status update for RC2 (ChrisPriceAB, 14:50:34)
    61. (from what I know from Peter): Robot up and running on Intel lab - performing subset of ODL tests (frankbrockners, 14:50:35)
    62. couple of robot tests are uploaded in git, there is however some duplicated code with odl integratiion tests... - need to decide how we going to proceed (pbandzi, 14:50:40)
    63. if we want to create just scripts whil will configure env and start required test from odl integration (pbandzi, 14:51:15)
    64. ok, can we please solve these things and whoever is standing in for Morgan this week needs to provide an upadte on mail (ChrisPriceAB, 14:51:17)
    65. opnfvdocs status update for RC2 (ChrisPriceAB, 14:51:23)
    66. toolchain for Arno is in place, described on the documentation WiKi (ChrisPriceAB, 14:51:40)
    67. https://wiki.opnfv.org/documentation docs & toolchain description (ChrisPriceAB, 14:52:14)
    68. templates in place, not all documents yet under authorship. (ChrisPriceAB, 14:52:32)
    69. release notes and instalation guide drafts ready for parts of BGS. (ChrisPriceAB, 14:53:05)
    70. http://artifacts.opnfv.org/genesis/fuel/docs/release-notes.html current release note artifacts built (ChrisPriceAB, 14:53:29)
    71. http://artifacts.opnfv.org/genesis/fuel/docs/installation-instructions.html current installation instructure notes built (ChrisPriceAB, 14:53:50)
    72. user guide template not yet started. (ChrisPriceAB, 14:54:10)
    73. environment documentation not yet started (ChrisPriceAB, 14:54:20)
    74. remaining BGS docs to be integrated into templates (ChrisPriceAB, 14:54:34)
    75. that's it. 5 minutes left lets capture actions. (ChrisPriceAB, 14:55:03)

  4. Actions and activities planned (ChrisPriceAB, 14:55:08)
    1. We should also document build-guidelines ([1]JonasB, 14:55:10)
    2. extrapolate that thought Jonas (ChrisPriceAB, 14:55:27)
    3. ok, but not as part of the release documentation, BGS general build documentation. (ChrisPriceAB, 14:57:33)
    4. I would assume that we should allow consumers of Arno to build them selves, even if the result is not supported? ([1]JonasB, 14:57:35)
    5. I agree with Jonas - we will need to extend ARNO due to lack of certain features we need for project testing (bryan_att, 14:58:31)
    6. Ah, OK yes. But I don't gate on Arno for that, I think we need to improve documentation across the board a little. So agree, but will not focus on that for the next 7 days. :) (ChrisPriceAB, 14:58:37)
    7. SO we need build instructions - it's OK that this follows release though (bryan_att, 14:58:59)
    8. Ok, want to hear form the project leads. Next 7 days, priority areas places we need support from others (ChrisPriceAB, 14:59:18)
    9. ACTION: ChrisPriceAB to coordinate across projects for Arno key items leading up to next week. (ChrisPriceAB, 15:00:25)
    10. unless there is something urgent, or to be added we can close off the RC2 meeting. (ChrisPriceAB, 15:00:43)
    11. basic status is that we are not yet Jenkns integrated with the LF hardware and have not egun deployment there. (ChrisPriceAB, 15:01:04)
    12. rprakash_: for what project? (vlaza, 15:01:10)
    13. sound accurate? (ChrisPriceAB, 15:01:28)
    14. Ok thanks all. I might start a series of daily syncs for project leads starting tomorrow so we get day by day updates (ChrisPriceAB, 15:03:55)


Meeting ended at 15:03:59 UTC (full logs).

Action items

  1. Pharos to update Jira leading up to Arno release (and onwards :)
  2. Assign a responsible person to the foreman daily pipeline activity
  3. Pharos to produce lab environment documentation, opnfvdocs and bgs to help
  4. ChrisPriceAB to rally the troups for environment documentation
  5. functest to provide concise reporting on the mailing lists before the end of the week
  6. ChrisPriceAB to coordinate across projects for Arno key items leading up to next week.


Action items, by person

  1. ChrisPriceAB
    1. ChrisPriceAB to rally the troups for environment documentation
    2. ChrisPriceAB to coordinate across projects for Arno key items leading up to next week.
  2. UNASSIGNED
    1. Pharos to update Jira leading up to Arno release (and onwards :)
    2. Assign a responsible person to the foreman daily pipeline activity
    3. Pharos to produce lab environment documentation, opnfvdocs and bgs to help
    4. functest to provide concise reporting on the mailing lists before the end of the week


People present (lines said)

  1. ChrisPriceAB (97)
  2. fdegir (34)
  3. frankbrockners (19)
  4. trevor_intel (14)
  5. [1]JonasB (13)
  6. ulik (10)
  7. rprakash_ (6)
  8. HKirksey (6)
  9. trozet (6)
  10. vlaza (5)
  11. pbandzi (4)
  12. collabot (4)
  13. radez (3)
  14. bryan_att (3)
  15. dneary (1)
  16. icbts (1)
  17. Guest98285 (1)
  18. lmcdasm (1)


Generated by MeetBot 0.1.4.