#opnfv-meeting: Colorado planning meeting

Meeting started by ChrisPriceAB at 15:08:05 UTC (full logs).

Meeting summary

    1. rprakash will help (rprakash, 15:09:14)

  2. Roll Call (ChrisPriceAB, 15:09:15)
    1. Bryan Sullivan (bryan_att, 15:09:22)
    2. Maryam Tahhan (VSPERF, SFQM) (mtahhan, 15:09:22)
    3. Bin Hu (bin_, 15:09:24)
    4. Frank Brockners (frankbrockners, 15:09:28)
    5. Chris Price (ChrisPriceAB, 15:09:28)
    6. Ana Cunha (Yardstick) (anac1, 15:09:35)
    7. Morgan Richomme (morgan_orange, 15:09:36)
    8. Fatih Degirmenci (Releng) (fdegir, 15:09:41)
    9. Tim Irnich (SDN VPN) (timirnich, 15:09:41)
    10. Uli Kleber, Octopus (uli-k_, 15:09:45)
    11. Bryan Sullivan (Copper, Models) (bryan_att, 15:09:46)
    12. RayNugent (RayNugent_, 15:09:54)
    13. Ashlee Young Networkfw (rprakash, 15:10:34)
    14. Tim Rozet (Apex) (trozet, 15:10:36)
    15. Mark Beierl (StorPerf) (mbeierl, 15:10:49)

  3. Colorado Planning (ChrisPriceAB, 15:11:36)
    1. https://wiki.opnfv.org/releases/colorado current approved Colorado plan (ChrisPriceAB, 15:12:18)
    2. Should we include the new release manager in these planning meetings? (RayNugent_, 15:14:58)
    3. https://wiki.opnfv.org/releases/colorado/projects list of participating projects for colorado (ChrisPriceAB, 15:15:02)

  4. Hack-Fest retrospective follow up (ChrisPriceAB, 15:18:30)
    1. David outlines the feedback that the test development and framework development happened in parallel with test cases in Brahmaputra. (ChrisPriceAB, 15:19:33)
    2. David raises the questions on if we would be able to close on the test infrastructure during Colorado. (ChrisPriceAB, 15:20:36)
    3. Capbity ofr feature tesing should be listed early like MS1 rther than Ms2 (rprakash_, 15:23:34)
    4. Capbity for feature tesing should be listed early like MS1 rther than Ms2 (rprakash_, 15:24:03)
    5. Framk says that we now have a test framework like Yardstick, Functest... (rprakash_, 15:24:36)
    6. Frank says that we now have a test framework like Yardstick, Functest... and even Installers are ready (rprakash_, 15:25:11)
    7. Morgan says create a stable scenerio with features declaraton and tickets for steering to correct testing project (rprakash_, 15:27:12)
    8. Selecting test cases accordingly and testing what is proven to work is paramount (fdegir, 15:28:09)
    9. Challenging but need to define CI test objective as well Feature test Objectives seperated and also frequenecy like weekly monthly tests etc. (rprakash_, 15:28:48)
    10. There is no point in testing everything on Baremetal is not necessary (rprakash_, 15:29:19)
    11. Tests Strategy must agree on mimimum vs exhaustive testing and schedule accordingly (rprakash_, 15:30:05)
    12. Relaying too much on Installer development is a sore point for some projects (rprakash_, 15:30:40)
    13. Relying too much on Installer development is a sore point for some projects (rprakash_, 15:31:04)
    14. Creating environment in CI so that Developers can test independent for minimal testing (rprakash_, 15:31:52)
    15. We need an OPNFV as a service project for testing from Cloud needs to be introduced and Bryan suggests Ravello as a showcase to see its viability (rprakash_, 15:33:44)
    16. Fathi to review if OPNFV virtual environment using BP can be established uisng Ravello for VNF (rprakash_, 15:35:37)
    17. Ravello is running on Mutiple servers and has emulated IPMI as per Bryan and Frank mentions that its a paid service and verify nested virtualization in LF (rprakash_, 15:37:01)
    18. Ravello is just a trial and if we can do it in LF then we will be in control (rprakash_, 15:37:39)
    19. TSC call to adress broad community colaboration issue (rprakash_, 15:42:20)
    20. Bryan can demo Ravello session in next 2 weeks (rprakash_, 15:43:42)
    21. Weekly test co-ordination call should address test co-ordination plan - Trevor can be assigned th Action Item (rprakash_, 15:45:08)
    22. need to define detail to seperate Dvelopment and Production testing (rprakash_, 15:46:03)
    23. nextweeks call we can discuss How do we allow individual Scenerios to allow testing like immediate dependencies versus actual targgetted (rprakash_, 15:48:59)
    24. eg starting with Liberty but ending with Mitaka etc. (rprakash_, 15:49:24)
    25. to cover upstream feedback etc so we should start discussions at next meeting (rprakash_, 15:50:14)
    26. Frank is documenting and will bring it to next meeting (rprakash_, 15:50:38)
    27. am going to end the meeting (rprakash_, 15:51:00)


Meeting ended at 15:51:24 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rprakash_ (29)
  2. ChrisPriceAB (17)
  3. fdegir (8)
  4. collabot (8)
  5. bryan_att (7)
  6. frankbrockners (3)
  7. rprakash (3)
  8. RayNugent_ (3)
  9. morgan_orange (2)
  10. uli-k_ (2)
  11. trozet (2)
  12. mtahhan (1)
  13. anac1 (1)
  14. timirnich (1)
  15. bin_ (1)
  16. mbeierl (1)
  17. davidmcbride (0)
  18. HKirksey (0)


Generated by MeetBot 0.1.4.