13:00:38 <bh526r> #startmeeting Weekly Technical Discussion 13:00:38 <collabot`> Meeting started Thu Sep 28 13:00:38 2017 UTC. The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:38 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic. 13:00:38 <collabot`> The meeting name has been set to 'weekly_technical_discussion' 13:01:09 <bh526r> #topic Roll Call 13:01:13 <bh526r> #info Bin Hu 13:01:30 <fdegir> #info Fatih Degirmenci 13:01:42 <rpaik> #info Ray Paik 13:02:09 <dmcbride> #info David McBride 13:03:05 <jmorgan1> #info Jack Morgan 13:05:42 <bh526r> #topic New Project Proposal: Dovestack 13:07:06 <bh526r> #info Prakash introduced that the target is to address the pain points from EUAG and Dovetail testing 13:10:53 <bh526r> #link https://wiki.opnfv.org/display/dovetail/Project+Name%3A++++++Dovestack 13:14:30 <bh526r> #info The proposal is to address pain points of dovetail test plan development during the early part of release to proactively address the execution of selected use case needed for a given release of Dovetail 13:15:37 <bh526r> #info The scope is to identity a list of features and functionality will be developed, including 13:15:51 <bh526r> #info (1) Creating Stack using Openstack/devstack (Heat) CLI manually and automate through FUNCTEST snaps library 13:16:04 <bh526r> #info (2) Leverage open source tests and adapt them for testing dovestack use case In this F release the focus will be on Clearwater vIMS tests. 13:16:19 <bh526r> #info (3) Provide inputs through Alfa and Beta testing to complete Functional and Dovetail testing for Scenario selected for the release. 13:31:46 <bh526r> #info Jack Morgan summarized that Dovestack will feed test plan and test case to Dovetail projects. Is it needed to have a separate project or should the work be part of Dovetail? 13:32:12 <bh526r> #info Prakash said that the test plan and test case should be independent of test execution 13:32:53 <bh526r> #info Jack asked what type of hardware needed? or only documentation? 13:35:01 <bh526r> #info Jack indicated that we don't have such type of "multi-arch" OPNFV pod 13:35:19 <bh526r> #info We only have Pharos specs 13:36:06 <bh526r> #info Jack if Dovetail will start to do CVP testing on multi-arch pod? 13:37:37 <bh526r> #info Fatih asked why we need a separate project now? We have test WG and many test projects, have you communicated with test WG? 13:39:39 <bh526r> #info Prakash said yes, he would bring it to test WG for discussion 13:41:59 <fdegir> thx rprakash 13:42:17 <fdegir> I just wanted to make sure if you collected feedback from the corresponding WGs/projects 13:42:48 <fdegir> so I don't directly oppose but wanted to ensure people are aware of this and they might be sharing same/simialr concerns as you 13:44:17 <bh526r> #info 3 actions for Prakash: 13:44:38 <bh526r> #info (1) send announcement to TSC mailing list and start the 2-week clock 13:45:43 <bh526r> #info (2) bring the proposal to test WG for socialization and deep dive of specific gaps and tasks identified in the proposal, so that the best way to move forward can be agreed 13:46:17 <bh526r> #info (3) bring the proposal to Dovetail project because Dovetail is targeted as the beneficiary of this proposal 13:46:25 <bryan_att> whats the etherpad link? 13:46:27 <rpaik> #link https://etherpad.opnfv.org/p/Pharos_Specification2.0 13:46:53 <bh526r> #topic Hardware Requirement and Improvements on Pharos Specs 13:47:19 <bh526r> #info Jack created an etherpad, and the link is posted by Ray above 13:50:01 <bh526r> #info We will collect suggestions of Pharos 2.0 in this etherpad 13:59:02 <bh526r> #info Jack will also provide example of pod description file 13:59:12 <bh526r> #info Meeting adjourned 13:59:15 <bh526r> #endmeeting