22:00:09 <sgordon> #startmeeting telcowg
22:00:12 <openstack> Meeting started Wed Feb 18 22:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is sgordon. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:00:15 <openstack> The meeting name has been set to 'telcowg'
22:00:19 <sgordon> #link https://etherpad.openstack.org/p/nfv-meeting-agenda
22:00:22 <sgordon> #topic roll call
22:00:26 <amitry> hola
22:00:29 <sgordon> yo
22:00:43 <cloudon> hi
22:00:51 <jhaller> hi
22:01:42 <aveiga> hello
22:02:12 <sgordon> #topic Action items from last week
22:02:28 <sgordon> #info sgordon, adrian-hoban, cloudon, ian_ott, vks were to review SBC use case and  leave comments in Gerrit
22:02:38 <sgordon> seems we had some success with this
22:02:45 <sgordon> plenty of comments inline in the review
22:02:47 <sgordon> #link https://review.openstack.org/#/c/152940/1
22:02:59 <sgordon> which connects to the other AI from last week
22:03:07 <sgordon> #info mkoderer and sgordon were to work together on LP and repo creation
22:03:27 <sgordon> mkoderer requested a repo and infra have merged that request here
22:03:29 <sgordon> #link https://review.openstack.org/#/c/155248/
22:03:54 <sgordon> so in theory we now have the repo stackforge/telcowg-usecases to use
22:04:35 <sgordon> <insert lively discussion about how to structure that here>
22:05:29 <aveiga> sgordon: is it worth trying to get it to build like -specs? Use rst markup and have it build an html doc, but still allow comments and +1?
22:05:54 <sgordon> probably since i think RST markup is going to make the most sense anyway
22:06:01 <sgordon> i have no idea how that is set up though
22:06:02 <aveiga> we can put structure around that to ensure at least a minimal set of headings as well
22:07:03 <sgordon> aveiga, do you want to take a stab at an RST template?
22:07:15 <aveiga> I can try
22:08:11 <sgordon> #action aveiga to take first stab at an RST template for use cases
22:08:32 <sgordon> i will take the action to import what we have as reviews
22:08:52 <sgordon> that will likely need to be molded to the template once we have one
22:10:52 <sgordon> #action sgordon to import existing use case proposals as gerrit reviews
22:11:31 <sgordon> so the other topic that came up as a result of this is making sure that we have a clear workflow for the many contributors who may not be as familiar with the 'normal' openstack workflow
22:11:43 <sgordon> so:
22:11:51 <sgordon> Use case submission workflow
22:11:51 <sgordon> Use case review workflow
22:11:51 <sgordon> Use case update workflow
22:12:37 <sgordon> i think there are probably three prongs to addressing this, written documentation (pointing to existing resources where feasible)
22:12:52 <sgordon> walking through the process face to face (form of training / process verification)
22:13:04 <sgordon> and ideally recording a run through
22:13:40 <sgordon> tom from the foundation reached out to me and confirmed we will have some time allocated during the operators mid-cycle
22:14:10 <sgordon> i thought that might be a good opportunity for those of us in attendance to walk through one of the use cases
22:14:23 <sgordon> including submitting it, reviewing it in gerrit, etc.
22:14:32 <sgordon> #link https://etherpad.openstack.org/p/PHL-ops-telco
22:18:17 <sgordon> ok
22:18:27 <sgordon> #topic use cases
22:18:49 <sgordon> so i mentioned there have been some good comments on the session border controller use case proposal
22:19:07 <sgordon> does anyone have any other updates to those that are still in the etherpads for now?
22:20:01 <sgordon> looks like there are still some good questions coming up on orchestration
22:20:03 <sgordon> #link https://etherpad.openstack.org/p/telco_orchestration
22:21:35 <sgordon> #topic implementation
22:21:47 <sgordon> last week we talked about the feature freeze and exception requests
22:21:55 <sgordon> the nova team went through theirs this week
22:22:05 <sgordon> #link https://etherpad.openstack.org/p/kilo-nova-ffe-requests
22:22:08 <sgordon> ^ full list
22:22:34 <sgordon> specific to those we talked about the request for libvirt vhostuser was granted and it has merged
22:22:59 <sgordon> does anyone have any other notable implementation related issues at this stage of the cycle?
22:24:07 <sgordon> #topic other business
22:24:37 <sgordon> amitry, tom tells me registration is going well for the ops mid cycle
22:24:51 <sgordon> do we have any visibility into how many who intersect with this group are attending?
22:25:04 <amitry> yes, I just asked for exactly that :)
22:25:21 <amitry> foundation has the registrations, we don't have direct access
22:26:06 <sgordon> ok cool
22:26:21 <sgordon> as i said somewhere up above tom has given us some time/space
22:26:33 <sgordon> we can nail down ideas for how to use it here: https://etherpad.openstack.org/p/PHL-ops-telco
22:26:59 <sgordon> in saying that exactly which time/space is still being figured out - he just let me know that we would have some
22:27:36 <amitry> ok, we gave tom all the rooms and time slots - so I guess he has to work his magic :)
22:27:42 <aveiga> do you want to discuss options for that now?
22:27:51 <aveiga> for the agenda and format, I mean
22:28:11 <sgordon> sure
22:28:54 <sgordon> so the things i had noted down were around nailing down workflow for submitting/reviewing/updating/use cases
22:28:57 <aveiga> do you think it's better to use it as a "getting started" with the new workflow or to discuss issues and use cases?
22:29:12 <aveiga> do we know how much time we'll have, or is taht still undecided
22:29:15 <sgordon> i think half and half ideally
22:29:22 <sgordon> he indicated 90 mins
22:29:26 <aveiga> ah, ok
22:29:30 <aveiga> we should have enough time for both then
22:29:46 <sgordon> so a run through of the workflow
22:29:53 <sgordon> then "let's actually do a few"
22:30:14 <aveiga> it might be good to not just open the floor up to undocumented use cases yet, because that might spiral
22:30:23 <aveiga> and instead just direct people to put them into the reviews
22:30:31 <sgordon> no i think we would go with the ones we have
22:30:41 <sgordon> and trying to discuss them
22:31:28 <aveiga> it might be good to come up with some guidance on them too. Especially considering a lot of different backgrounds are going to come together in the same place and possible not communicate well with each other
22:32:07 <sgordon> indeed
22:32:47 <sgordon> what kind of guidance did you have in mind
22:33:13 <sgordon> (i am also taking some notes in that ether pad here)
22:33:26 <aveiga> things like spelling out acronyms, giving a description for specialized gear/services, or linking to standards groups where possible for a given protocol or function
22:33:54 <aveiga> things that would help explain the gaps between an OpenStack dev and what a Telco might consider domain specific info
22:34:49 <amitry> maybe some guidance as to what land on top of openstack versus within openstack?
22:34:55 <aveiga> +1
22:35:17 <sgordon> all good points, noting in the etherpad
22:36:46 <sgordon> i think that is good for now
22:36:59 <sgordon> again rough framework here: https://etherpad.openstack.org/p/PHL-ops-telco
22:37:16 <sgordon> we will probably want to identify which existing proposals we want to try get through ahead of time
22:37:55 <aveiga> maybe in next week's meeting? Assuming I can get the template together, we should at least have those selected use cases migrated into the review system ahead of time
22:38:05 <sgordon> yeah
22:38:06 <sgordon> agree
22:38:40 <sgordon> #action all need to identify use cases for mid cycle discussion
22:38:53 <sgordon> just recording that so i dont forget when i frame agenda next week
22:39:19 <sgordon> ok
22:39:27 <sgordon> i dont have anything further to add for today
22:39:32 <sgordon> anyone else?
22:39:45 <aveiga> not I
22:39:51 <amitry> nor I
22:41:12 <sgordon> ok
22:41:15 <sgordon> thanks all!
22:41:18 <sgordon> #endmeeting