14:04:01 <bh526r> #startmeeting Weekly Technical Discussion
14:04:01 <collabot> Meeting started Thu Jan 19 14:04:01 2017 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:04:01 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:04:01 <collabot> The meeting name has been set to 'weekly_technical_discussion'
14:04:19 <bh526r> #topic Roll Call
14:04:23 <bh526r> #info Bin Hu
14:04:46 <uli-k> #info Uli
14:05:17 <uli-k> #link https://wiki.opnfv.org/display/INF/Scenario+Consolidation
14:05:51 <ljlamers> #info Larry Lamers
14:05:55 <bh526r> #topic Scenario Consolidation
14:06:16 <bh526r> #info See link provided by uli-k above
14:07:10 <bh526r> #info Uli indicated that there was discussion in the forum since last week
14:07:33 <bh526r> #info 2 different names - generic and specific
14:08:55 <bh526r> #info The intention is to merged with generic scenarios
14:12:42 <bh526r> #info Generic scenarios are our goal of integration work
14:13:23 <bh526r> #info typically generic scenarios should be supported by multiple installers
14:15:14 <bh526r> #info Bryan indicated that the expectation is to be supported by all installers
14:15:50 <bh526r> #info regardless of the installer being used, we can have the feature
14:16:13 <bh526r> #info This is the expectation - generic scenarios should be supported by all installers
14:17:44 <bh526r> #info we should keep the number of generic scenarios limited
14:19:27 <bh526r> #info Dan Radez suggested and Uli changed the wording to "... generic scenarios supported by all installers ..."
14:19:38 <bh526r> #info Bryan said to meet the soft target
14:21:28 <hongbo333> hello
14:21:54 <bh526r> #info some limitations, such as cannot deploy 2 SDN controllers at the same time
14:22:38 <bh526r> #info specific scenarios are to introduce new features
14:22:57 <bh526r> #info typically start with one installer
14:24:42 <bh526r> #info should provide roadmap from the beginning
14:25:36 <bh526r> #info overlap may happen, but should lead to merge
14:33:26 <bryan_att> #info more resources will be allocated to maintaining generic scenarios. specific scenarios will likely have a shorter support period after release as they are of interest to a smaller user community vs generic scenarios, and we may need to prioritize resources post-release for scenario maint/regression testing
14:34:12 <bryan_att> #info specific scenarios may be released at any time, vs generic scenarios that are expected to be released at the overall release schedule
14:37:22 <bh526r> #info HA scenarios typically in release
14:37:43 <bh526r> #info NOHA should be available to users
14:38:26 <bryan_att> #info non-HA as a config option is a better approach, as the expectation continues with the release, that the installers continue to support all config options for generic scenarios, at the least
14:38:54 <bryan_att> #info thus non-HA will continue to be supported post-release in any case
14:42:58 <bryan_att> #info HA/non-HA should be just a selectable option through the scenario descriptor file which enables the user to select which services are deployed in which node, and in which configuration (HA/non-HA)
14:45:07 <bryan_att> #info the resulting assumption is that all scenarios will support HA and non-HA, since they are selectable options in the scenario config file
14:58:08 <bh526r> #info Uli introduced details of current scenarios, and ideas of possible consolidation/merge
15:02:11 <bh526r> #info Uli will drive the actions of next steps
15:02:50 <dneary> I dropped from the call - I have another meeting
15:05:47 <bh526r> #info Uli will send a request to community for help of filling up the table and collect more information
15:06:14 <bh526r> #info Those information will help possible paths of scenario consolidation
15:06:36 <bh526r> #info We will discuss the status of information collection next week
15:06:42 <bh526r> #info Meeting adjourned
15:06:46 <bh526r> #endmeeting