16:59:54 <colindixon> #startmeeting tsc
16:59:54 <odl_meetbot> Meeting started Thu May 28 16:59:54 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:59:54 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:59:54 <odl_meetbot> The meeting name has been set to 'tsc'
16:59:59 <colindixon> #topic agenda bashing and roll call
17:00:13 <dlenrow> #info dlenrow
17:00:32 <colindixon> #info colindixon
17:00:39 <tbachman> #link  https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-21-16.59.html minutes to previous meeting
17:00:55 <tbachman> #link https://wiki.opendaylight.org/view/TSC:Main#Agenda Agenda for today’s meeting
17:01:10 <edwarnicke> #info edwarnicke
17:01:30 <colindixon> thanks tbachman
17:01:34 <tbachman> colindixon: np!
17:01:38 * tbachman waits for chair
17:01:51 <colindixon> #action colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade
17:01:54 <colindixon> #chair tbachman
17:01:54 <odl_meetbot> Current chairs: colindixon tbachman
17:01:58 <tbachman> anyone?
17:02:09 <edwarnicke> bueller? bueler?
17:02:15 <tbachman> edwarnicke: LOL
17:02:35 * tbachman has much catching up to do
17:02:52 <mohnish> #info mohnish anumala
17:03:03 <tbachman> should we save that for infra?
17:03:06 <colindixon> #action LuisGomez and tykeal and jamoluhrsen to work out getting a patch merged in openstack to view all historical performance data
17:03:10 <tbachman> k
17:03:12 <dfarrell07> 4 TSC members sof ar
17:03:28 <LuisGomez> #info LuisGomez
17:03:33 <tbachman> I’ll get that link
17:03:46 * zxiiro is having issues connecting to webex
17:03:53 <ChrisPriceAB> #info Chris Price
17:03:57 <dfarrell07> 6
17:04:06 <tbachman> #link https://lists.opendaylight.org/pipermail/release/2015-May/002443.html Email from phrobb on Beryllium release plan proposal
17:04:13 <colindixon> #actoin ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and testing
17:04:14 <cdub> #info Chris Wright
17:04:21 <dfarrell07> 7, gtg
17:04:31 <tbachman> #action ChrisPriceAB to work with rovarga, jmedved, et. al. to look into leveraging OPNFV infrastructure for performance measurements and
17:05:01 <alagalah> Sleep is for the weak
17:05:09 <jmedved> #info jmedved
17:05:11 <colindixon> #topic events
17:05:12 <alagalah> ... Phil is strong :)
17:05:27 <tbachman> #info phrobb says ONS is coming up in a few weeks
17:05:36 <colindixon> #link http://www.opendaylight.org/news/events/ the events page in it’s usually place
17:05:45 * zxiiro is connect with voice only
17:05:56 <tbachman> #info phrobb says they’re looking at shifting some things around for the summit — going to put out an agenda for the developer forum shortly after the Lithium release
17:06:30 <tbachman> #info colindixon asks for additional topics
17:06:48 <tbachman> #info edwarnicke says he’d like to discuss the IPv6 issues with respect to branch-cutting
17:07:43 <tbachman> #topic rovarga says he doesn’t see the restconf/netconf and other creation reviews (breakout projects)
17:07:48 <tbachman> #undo
17:07:48 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1c3ecd0>
17:07:57 <tbachman> #info rovarga says he doesn’t see the restconf/netconf and other creation reviews (breakout projects)
17:08:06 <tbachman> #info colindixon says he’ll schedule this for next week, given the time frame
17:08:19 <tbachman> #topic Lithium and stable/helium updates
17:08:43 <tbachman> #info colindixon asks zxiiro what the status is of autorelease and branch cutting
17:09:00 <tbachman> #info zxiiro says autorelease is failing b/c l2switch is trying to build a distribution that no longer exists
17:09:24 <tbachman> #link https://bugs.opendaylight.org/show_bug.cgi?id=3398 bug against l2switch building old distribution
17:09:42 <tbachman> #info edwarnicke says l2switch is trying to build a hydrogen style distribution, but that distribution no longer exists
17:11:10 <tbachman> #info colindixon asks if downstream projects should wait to bump their versions
17:12:07 <tbachman> #info rovarga says until we perform the bumps, we don’t have visibility into what breakages are present
17:12:49 <tbachman> #info rovarga says we shouldn’t be shipping Lithium until the corresponding patch in yangtools is merged into Lithium
17:13:04 <tbachman> #undo
17:13:05 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1c3e190>
17:13:28 <tbachman> #info rovarga says we shouldn’t be shipping Lithium until the corresponding patch in yangtools is merged (cherry-picked) into stable/lithium
17:13:52 <tbachman> #info colindixon asks if downstream projects do bump their versions, will this cause issues using two different versions of yangtools
17:14:01 <tbachman> #info edwarnicke says this will definitely cause issues
17:14:36 <tbachman> #info colindixon says lithium isn’t blocked on this, but the ability to expose bugs in downstream projects is limited
17:15:55 <tbachman> #info edwarnicke says cutting master without version bumps is meaningless
17:16:18 <alagalah> #info edwarnicke also highlights that a lot of downstream projects feel pressure to "cut"
17:16:34 <tbachman> alagalah: thx!
17:16:47 <cdub> lots of noise
17:16:55 <cdub> better, thank you
17:16:56 <alagalah> cdub: Oh fine, I make one comment.
17:17:01 <alagalah> sheesh
17:17:06 <tbachman> lol
17:17:09 <cdub> heh
17:17:51 <edwarnicke> #link https://git.opendaylight.org/gerrit/#/c/21268/ <- l2switch stable/lithium should not be blocking autorelease anymore
17:17:53 <dbainbri> ok, as a mere human, i am hearing there is (a) no requirement to create stable/lithium and (b) we should not version bump
17:17:57 <tbachman> #info The view of the TSC at this point is that the stable/lithium branch cutting does not block the ability to cut RC<n> releases
17:18:01 <tbachman> colindixon: does that look good?
17:18:12 <edwarnicke> dbainbri: That does not match my understanding of what was said
17:18:17 <cdub> dbainbri: no i don't hthink so
17:18:36 <zxiiro> edwarnicke: that's great thanks!
17:19:03 <zxiiro> thanks to evanz rather
17:19:08 <tbachman> #info dbainbri asks if there is (a) no requirement to create stable/lithium and (b) we should not version bump
17:19:16 <edwarnicke> zxiiro: Let the record reflect that it merged 8 minutes ago, and so you were 100% factually correct in what you said when you said it :)
17:19:54 <tbachman> #info colindixon says there is currently no value in cutting stable/lithium unless you bump on master; if you cannot bump all your versions on master, you should not cut stable/litihium b/c you get no value, but does increase complexity
17:20:03 <edwarnicke> colindixon: You did not repeat what I said, you said a version of it that is clearer ;)
17:20:33 * tbachman didn’t quite get that last part
17:20:58 <tbachman> #info colindixon says that not bumping master, you have two things publishing artifacts to nexus, with no way of saying which one ‘wins’
17:21:16 <rovarga> #info looking at OFP master, I see ./parent/pom.xml:        <yangtools.version>0.8.0-SNAPSHOT</yangtools.version>
17:22:12 <tbachman> #action zxiiro to send email to release to asking projects to not cut stable/lithium without version bumping
17:22:20 <tbachman> oops
17:22:21 <edwarnicke> rovarga: So it does appear that OFpluing master depends on the correct yangtools version then?
17:22:23 <tbachman> poor grammar there
17:22:29 <tbachman> #undo
17:22:29 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x1ba98d0>
17:22:47 <tbachman> #action zxiiro and gzhao to send email to release asking projects to not cut stable/lithium without version bumping
17:23:04 <tbachman> #info ebrjohn says that SFC has already cut stable/lithium and not bumped versions
17:23:18 <tbachman> #info colindixon says you technically shouldn’t merge to master w/o the version bump
17:23:34 <rovarga> edwarnicke: yup
17:23:52 <tbachman> #info edwarnicke says it may be easier for SFC to delete the current stable/lithium branch, and then redo it when you’re ready to version bump
17:24:17 <gzhao> tbachman: thanks, I have IRC only right now
17:24:24 <tbachman> gzhao: np!
17:24:24 <abhijitkumbhare> edwarnicke rovarga  - I believe we are pointing to correct Yangtools version with your patch https://git.opendaylight.org/gerrit/#/c/20316/
17:25:09 <tbachman> #link https://git.opendaylight.org/gerrit/#/c/20316/ patch from edwarnicke that bumped yangtools version in openflowplugin
17:25:20 * edwarnicke apparently can't even keep track of what he himself has done
17:25:34 <tbachman> #info LuisGomez says that integration already did their branch — without the branch, there’s no way they can do their testing
17:26:00 * tbachman loves the smell of integration in the morning
17:26:12 <tbachman> s/integration/branch-cutting/
17:26:33 <tbachman> where’s regXboi when you need him to get a movie reference?
17:26:42 <cdub> smells like victory
17:26:46 <tbachman> lol
17:26:50 * cdub helps tbachman out
17:26:51 <tbachman> teen spirit even?
17:26:53 <tbachman> lol
17:26:56 <dbainbri> mvn dependency:list ;)
17:26:59 <tbachman> <cricket, cricket>
17:27:27 * tbachman is glad that cdub got the ref
17:27:46 <colindixon> https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Project_Dependency_Diagram
17:27:53 <tbachman> #info edwarnicke says there are a lot of projects that depend on OVSDB, so it’s probably the next project that needs to cut and bump
17:27:54 <alagalah> tbachman: but what about the inference ?
17:28:01 <tbachman> movie
17:28:05 <tbachman> think war movie
17:28:07 <alagalah> tbachman: yes, and ...
17:28:09 <zxiiro> #link https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-daily-master/lastFailedBuild/artifact/dependencies.log
17:28:10 <alagalah> tbachman: inference...
17:28:16 <tbachman> reference
17:28:18 <alagalah> "napalm == integration" ??
17:28:22 <alagalah> tbachman: sigh
17:28:27 <tbachman> branch-cutting
17:28:28 <tbachman> had to fix it
17:28:34 <tbachman> zxiiro: thx
17:28:58 <tbachman> rovarga: is that you?
17:29:09 <ebrjohn> lots of noise again
17:29:09 <rovarga> I am trying to get to talk :)
17:29:48 <dbainbri> ebrjohn: so are you suggesting that rovarga talking is "lots of noise" … :)
17:29:55 <alagalah> rovarga: Going off mute seems to be a successful strategy for you, as the squelch is just amazing...
17:30:33 <colindixon> #action zxiiro and gzhao to work to drive the version bump through projects using the dependency chart as a guide: it seems, like the next targets would be OVSDB and L2 Switch, followed by dlux
17:31:52 <tbachman> isn’t the big concern here integration?
17:32:08 <colindixon> #info rovarga suggests that we force merge the version bump on master and then deal with the issue later to return the build to normal, edwarnicke sees dragons there
17:32:09 <tbachman> the offset 0 and 1 projects are all cut and bumped
17:32:24 <colindixon> tbachman: but there are dependendencies within offset 2
17:32:51 <tbachman> colindixon: yeah, but my point being that the main thing depending on offset 2 projects is integration
17:32:57 <ebrjohn> colindixon: did you see that email I sent today about problems with the Vesion-bump.sh script?
17:32:58 <colindixon> tbachman: yes
17:32:59 <tbachman> and that’s our “health meter”
17:33:15 * ChrisPriceAB appreciates Ed's social consciousness. :O
17:33:16 <colindixon> ebrjohn: I didn’t, but I’ll look later
17:33:23 <rovarga> edwarnicke: fair enough
17:33:49 <edwarnicke> ChrisPriceAB: I have scars, so many scars ;)
17:33:56 <ChrisPriceAB> ;-)
17:34:11 <cdub> crazy talk
17:34:21 <colindixon> #link https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=676729675 blocking bugs
17:34:29 <rovarga> colindixon: edwarnicke: it is an option, I think we should try another week and see whether we actually in sucha bind where it is useful :)
17:34:39 <tbachman> #link https://wiki.opendaylight.org/view/Weather link to weather map page
17:35:01 <abhijitkumbhare> This branch cutting / version bump has been very painful this time around :)
17:35:59 <tbachman> #topic System Integration and Test
17:36:05 <dbainbri> edwarnicke: and the titanic cross went smoothly, except for that iceberg thing
17:36:15 <colindixon> #info OVS 2.3 is working in CI, yay!
17:36:17 <cdub> hehe
17:36:36 <alagalah> LuisGomez: What are we doing around OVS2.4 ?
17:36:43 <tbachman> #info LuisGomez says they cut stable/lithium yesterday
17:37:12 <alagalah> LuisGomez: Its not released but will be soon... just like Lithium :)
17:37:22 <tbachman> #info LuisGomez says their main issue is that all their triggers are “weird” now, so when something fails, it’s hard to know whether it was from stable/lithium or from master
17:37:44 <colindixon> #info the key issue is that cross-project triggers are still intra-branch, e.g., master triggerst master, stable/lithium triggers stable/lithium, but that’s not the reality on the ground at the moment
17:39:38 <rovarga> btw. who do I talk to to get BUG-3051 on the blocker list? :)
17:40:22 * rovarga will follow-up :)
17:40:27 <colindixon> #action colindixon to follow up with zxiiro and gzhao about version bumps on friday and monday to see if we need interim solutions
17:40:43 <colindixon> #action colindixon to add bug 3051 the the blocker list and get robert edit access
17:40:46 <tbachman> colindixon: thx!
17:41:00 <tbachman> #topic Infrastructure
17:41:29 <tbachman> #info tykeal says last night there were issues with slaves not working right — resulting in a huge queue today
17:41:43 <tbachman> #info colindixon asks how long until this this resolves itself
17:41:51 <edwarnicke> jenkins is building as fast as it can ;)
17:41:54 <tbachman> #info tykeal says maybe by midnight — but hard to know for sure
17:42:00 <tbachman> run jenkins, run!
17:42:56 <colindixon> #info rovarga asks if we could expand the support staff so that we could reach peopel for issues 24x7
17:43:24 <colindixon> #action colindixon to take the issue of more staff for added hours to board
17:44:09 <tbachman> #link https://lists.opendaylight.org/pipermail/tsc/2015-May/003109.html email from ttkacik about LF infra
17:44:34 * ChrisPriceAB thinks no news is good news... :s
17:44:37 <colindixon> #topic berullium release plann
17:44:43 <tbachman> #undo
17:44:43 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x1ba02d0>
17:44:44 <tbachman> #topic Beryllium Release Planning and Board Requests
17:44:52 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan the draft release plan
17:45:13 <tbachman> #info colindixon asks people to look over it and comment on mailing lists
17:45:36 <ChrisPriceAB> eek, mid January...
17:45:46 <tbachman> #info colindixon says there’s also an issue that some of the document may not reflect the project lifecycle changes
17:45:56 <tbachman> #action colindixon to draft changes to language around project lifecycles
17:46:29 <tbachman> #info edwarnicke says he feels very bad about voting on that by next Wednesday, as he’s been heads down in development mode
17:46:39 <tbachman> :)
17:47:29 <alagalah> Did someone say JIRA
17:47:31 <alagalah> ???
17:47:32 <alagalah> :)
17:47:34 <tbachman> #topic Moving to Jira
17:48:07 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-February/002554.html mailing list thread started here
17:48:07 <tbachman> #info rovarga says he’d like to get feedback from the community about using bugzilla vs. Trello vs. other tools
17:48:13 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-March/002730.html and moved here
17:48:18 <tbachman> colindixon: thx!
17:48:21 <colindixon> #link https://lists.opendaylight.org/pipermail/tsc/2015-May/003106.html before ending here
17:48:25 <tbachman> :)
17:49:26 <alagalah> #info alagalah would use JIRA for GBP if ODL got a FOSS license from Atlassian
17:49:37 <tbachman> #info rovarga says this discussion has been brought up on the mailing lists 2 or 3 times, and has stalled each time; would like to get closure on this — worth moving to Jira?  Too much of a disturbance, etc.?
17:49:43 * ChrisPriceAB has been working in Jira recently. Finds it quote useful and can help with the project activity planning and tracking.
17:49:57 * colindixon notes that his OF plugin build (kicked off when I found out that yangtools version was also bumped) just succeeded, so yay
17:49:57 <tbachman> #info rovarga also would like to know how the TSC and PTLs feel about using Jira
17:50:29 <tbachman> #info edwarnicke  says we can split this into two things: can we switch from bugzilla to jira; the other is: how do we manage migrating from bugzilla to jira
17:50:47 <tbachman> #info colindixon says there’s another piece — running and operating jira
17:51:05 <tbachman> #info colindixon says there’s a cost to migrate from bugzilla to jira, and an operational cost for running jira
17:51:22 <ChrisPriceAB> Do we have 4 Questions?  going once... going twice...  Thanks Ed!
17:51:33 <tbachman> #info edwarnicke says that in the absence of the cost, there’s the question of using jira vs. bugzilla
17:51:37 <tbachman> ChrisPriceAB: lol!
17:51:43 * edwarnicke likes Jira :)
17:51:44 <alagalah> ChrisPriceAB: Is that a 5th question ? <<<---- 6
17:51:48 <abhijitkumbhare> why are you surprised colindixon that the OF plugin build succeeded? :)
17:51:49 <ChrisPriceAB> lol
17:52:41 <tbachman> #info colindixon says that his perception from the mailing list was that people preferrred Jira, but there’s a big cost
17:52:58 * ChrisPriceAB likes the cross project tracking in Jira.
17:53:09 <tbachman> #info colindixon asks that cost aside, are folks opposed to moving to Jira
17:53:20 <tbachman> #info alagalah asks if we’d adopt it to everything, or just use it for bug-tracking
17:53:44 <tbachman> #info rovarga says we could start with bug-tracking, and add features as the community becomes more comfortable with it
17:54:18 <tbachman> #info ChrisPriceAB recommends using Jira for planning as well
17:54:34 <tbachman> #info colindixon says that his understanding is that not all plugins are available for opensource
17:54:51 <ChrisPriceAB> lol edwarnicke
17:55:07 <snoble> there should be no cost
17:55:20 <snoble> atlassian is free for opensource/non-profits
17:55:26 <colindixon> snoble: all of it?
17:55:32 <tykeal> no not all of it
17:55:32 <snoble> yes
17:55:41 <tbachman> #info abhijitkumbhare says that most people have used bugzilla but not used Jira
17:55:43 <tykeal> most of it
17:55:48 <snoble> ok, maybe tykeal knows more about it
17:55:52 <dneary> The difficulties of Bugzilla are related to scalability as you get more projects/projects, versions, workflows
17:56:05 <snoble> we use plugins from other companies that have cost but we get them free
17:56:09 * tykeal notes we run several jira instances for various projects
17:56:29 <tbachman> #info dneary says that bugzilla has difficulties related to scalability as you get more projects, versions, workflows
17:56:37 <tbachman> #info tykeal notes that they run several jira instances for various projects
17:56:53 <dneary> ChrisPriceAB, I'm not a fan of Jira in general (personal opinion, not based on a huge amount of recent experience)
17:56:54 <tykeal> oh gosh no, I didn't mean for that to become an info!
17:56:55 <tykeal> :P
17:57:03 <tbachman> #info rovarga recommends setting up some sort of sandbox where people can try out how their workflows would be
17:57:07 <tbachman> tykeal:  lol
17:57:08 <colindixon> #action phrobb to investigate what it takes to get to the license, and what the licence would be for
17:57:19 <tbachman> tykeal: you are an authority ;)
17:57:26 * tykeal cries about that
17:57:28 <tbachman> lol
17:57:30 <ChrisPriceAB> hehe dneary, I'm not a fan of any tool I have tried in this space tbh.
17:57:46 <dneary> #info What tykeal meant is that dneary said that most of Bugzilla complaints are related to the UI failing to scale well to many projects, versions, complex workflows, etc
17:57:56 <tykeal> hehe
17:58:04 <cdub> rovarga: find a small working group to focus, pull project leaders to review, etc...
17:58:07 <dneary> So my question was: how many projects, issues, versions are we talking about?
17:58:10 <colindixon> #info we’d like to set up a sandbox and maybe do a TWS call where we show it off
17:58:12 <cdub> something like that
17:58:28 * tbachman can’t keep up
17:58:55 * ChrisPriceAB thinks we should involve aricg from the OPNFV team who is driving an instance today
17:59:14 <tbachman> #endmeeting