15:08:05 <ChrisPriceAB> #startmeeting Colorado planning meeting
15:08:05 <collabot> Meeting started Tue Mar 22 15:08:05 2016 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:08:05 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:08:05 <collabot> The meeting name has been set to 'colorado_planning_meeting'
15:08:15 <ChrisPriceAB> #chair davidmcbride
15:08:15 <collabot> Current chairs: ChrisPriceAB davidmcbride
15:08:38 <ChrisPriceAB> #chair HKirksey
15:08:38 <collabot> Current chairs: ChrisPriceAB HKirksey davidmcbride
15:09:00 <ChrisPriceAB> #chair uli-k_
15:09:00 <collabot> Current chairs: ChrisPriceAB HKirksey davidmcbride uli-k_
15:09:01 <fdegir> can try as well
15:09:08 <ChrisPriceAB> #chair fdegir
15:09:08 <collabot> Current chairs: ChrisPriceAB HKirksey davidmcbride fdegir uli-k_
15:09:14 <rprakash> #info rprakash will help
15:09:15 <ChrisPriceAB> #topic Roll Call
15:09:22 <bryan_att> #info Bryan Sullivan
15:09:22 <mtahhan> #info Maryam Tahhan (VSPERF, SFQM)
15:09:24 <bin_> #info Bin Hu
15:09:28 <frankbrockners> #info Frank Brockners
15:09:28 <ChrisPriceAB> #info Chris Price
15:09:35 <anac1> #info Ana Cunha (Yardstick)
15:09:36 <morgan_orange> #info Morgan Richomme
15:09:41 <fdegir> #info Fatih Degirmenci (Releng)
15:09:41 <timirnich> #info Tim Irnich (SDN VPN)
15:09:45 <uli-k_> #info Uli Kleber, Octopus
15:09:46 <bryan_att> #info Bryan Sullivan (Copper, Models)
15:09:54 <RayNugent_> #info RayNugent
15:10:03 <morgan_orange> is it GTM or IRC only
15:10:15 <frankbrockners> we're on GTM as well
15:10:19 <frankbrockners> same as TSC call
15:10:34 <rprakash> #info Ashlee Young Networkfw
15:10:36 <trozet> #info Tim Rozet (Apex)
15:10:45 <ChrisPriceAB> #chair rprakash
15:10:45 <collabot> Current chairs: ChrisPriceAB HKirksey davidmcbride fdegir rprakash uli-k_
15:10:49 <mbeierl> #info Mark Beierl (StorPerf)
15:11:10 * ChrisPriceAB wants trozet to update https://wiki.opnfv.org/releases/brahmaputra/2.0.release.plan when he get a chance today
15:11:25 <rprakash> 4#info for Ulas Kozat Domino
15:11:36 <ChrisPriceAB> #topic Colorado Planning
15:11:58 <trozet> ChrisPriceAB: will do
15:12:18 <ChrisPriceAB> #link https://wiki.opnfv.org/releases/colorado current approved Colorado plan
15:13:08 <bryan_att> I thought we were supposed to copy the releaseplan page and edit it on our wikis... I have started that.
15:13:31 <bryan_att> e.g. https://wiki.opnfv.org/models/releaseplan
15:14:58 <RayNugent_> #info Should we include the new release manager in these planning meetings?
15:15:02 <ChrisPriceAB> #link https://wiki.opnfv.org/releases/colorado/projects list of participating projects for colorado
15:15:06 <bryan_att> Is the definition of scenario the same for this release? I think we had issues with the concept in B. I think we may need to disconnect features from the scenarios if there is no low-level dependency e.g. OVS
15:15:26 <RayNugent_> Thanks
15:15:35 <bryan_att> (just some topics to consider
15:16:11 <ChrisPriceAB> all good topics bryan_att
15:18:30 <ChrisPriceAB> #topic Hack-Fest retrospective follow up
15:19:33 <ChrisPriceAB> #info David outlines the feedback that the test development and framework development happened in parallel with test cases in Brahmaputra.
15:20:36 <ChrisPriceAB> #info David raises the questions on if we would be able to close on the test infrastructure during Colorado.
15:23:11 <bryan_att> For the Models project I will be working to pattern the vIMS test approach as a generic way to test other use cases, and make that available soon in the release. I don't know if others will find that useful but just FYI.
15:23:34 <rprakash_> #info Capbity ofr feature tesing should be listed early like MS1 rther than Ms2
15:23:41 <rprakash_> #undo
15:24:03 <rprakash_> #info Capbity for feature tesing should be listed early like MS1 rther than Ms2
15:24:36 <rprakash_> #info Framk says that we now have a test framework like Yardstick, Functest...
15:24:47 <rprakash_> #undo
15:25:11 <rprakash_> #info Frank says that we now have a test framework like Yardstick, Functest... and even Installers are ready
15:27:12 <rprakash_> #info  Morgan says create a stable scenerio with features declaraton and tickets for steering to correct  testing project
15:28:09 <fdegir> #info Selecting test cases accordingly and testing what is proven to work is paramount
15:28:48 <rprakash_> #info Challenging but need to define CI test objective as well Feature test Objectives seperated and also frequenecy like weekly monthly tests etc.
15:29:19 <rprakash_> #info There is no point in testing everything on Baremetal is not necessary
15:30:05 <rprakash_> #info Tests Strategy must agree on mimimum vs exhaustive testing  and schedule accordingly
15:30:40 <rprakash_> #info Relaying too much on Installer development is a sore point for some projects
15:30:49 <rprakash_> #undo
15:31:04 <rprakash_> #info Relying too much on Installer development is a sore point for some projects
15:31:52 <rprakash_> #info Creating environment in CI so that Developers can test independent for minimal testing
15:33:44 <rprakash_> #info 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
15:35:37 <rprakash_> #info Fathi to review if OPNFV virtual environment using BP can be established uisng Ravello for VNF
15:37:01 <rprakash_> #info 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
15:37:39 <rprakash_> #info Ravello is just a trial and if we can do it in LF then we will be in control
15:38:28 <fdegir> bryan_att: I
15:38:37 <fdegir> ll send my findings to you
15:38:57 <fdegir> cause I've been experiencing some stabiltiy issues, vcpu exceptions, crashes, hangings and so on
15:42:20 <rprakash_> #info TSC call to adress broad community colaboration issue
15:42:26 <fdegir> the Ravello proposal/evaluation has 2 aspects; providing resources for the projects for development purposes
15:42:35 <fdegir> and using Ravello for CI/CD purposes
15:43:42 <rprakash_> #info Bryan can demo Ravello session in next 2 weeks
15:45:08 <rprakash_> #info Weekly test co-ordination call should address test co-ordination plan - Trevor can be assigned th Action Item
15:45:56 * ChrisPriceAB has to drop off the call. (rprakash don't forget to endmeeting at the end.)
15:46:03 <rprakash_> #info need to define detail to seperate Dvelopment and Production testing
15:46:25 <rprakash_> ok will do
15:48:59 <rprakash_> #info nextweeks call we can discuss How do we allow individual Scenerios to allow testing like immediate dependencies versus actual targgetted
15:49:24 <rprakash_> #info eg starting with Liberty but ending with Mitaka etc.
15:50:14 <rprakash_> #info to cover upstream feedback etc so we should start discussions at next meeting
15:50:38 <rprakash_> #info Frank is documenting and will bring it to next meeting
15:51:00 <rprakash_> #info am going to end the meeting
15:51:06 <rprakash_> #endmeeting
15:51:24 <uli-k_> #endmeeting