Attendees
...
(In order of importance)
Minutes
Schedule review
- Breakdown :: https://cloudrouter.atlassian.net/wiki/display/CPD/CloudRouter+Roadmap
- Key milestones :: https://cloudrouter.atlassian.net/wiki/display/RM/CloudRouter+Release+Management
Proposed targets for next release [December 2015]
Jira Legacy server JIRA (cloudrouter.atlassian.net) jqlQuery filter=
...
11000 count true serverId 8d719645-383c-39ee-9dce-64c2ff67f441
Time permitting
- Discuss proposed community website changes, including moving environment to AWS
- Package analysis against other solutions to determine where we can improve
Action Items
- Type your task here, using "@" to assign to a user and "//" to select a due date
...
- shainesus to split out https://cloudrouter.atlassian.net/browse/CR-3
- shainesus to file JIRA to track plugin development plan
- shainesus to run to ground https://cloudrouter.atlassian.net/browse/CR-114 as it is an upstream Fedora issue
- shainesus to file JIRA to track creation of custom groups where all non-essential packages are stripped
- shainesus to set up regularly occuring meeting to discuss 'use case scenarios' that are then placed in some form of timeline
- demolitiongirl to work on cloudrouter.org site content and layout changes
- shainesus to follow-up w/ demolitiongirl, juliettkilotango, and dfj on https://cloudrouter.atlassian.net/projects/WEB/issues/WEB-34?filter=allopenissues
...
Targeted For Next Release [December 2015]
- Agreed: https://cloudrouter.atlassian.net/browse/CR-3
- Agreed: https://cloudrouter.atlassian.net/browse/CR-9
- Agreed: https://cloudrouter.atlassian.net/browse/CR-53
- Agreed: https://cloudrouter.atlassian.net/browse/CR-63
- Agreed: https://cloudrouter.atlassian.net/browse/CR-72
- Agreed: https://cloudrouter.atlassian.net/browse/CR-114
- Agreed: https://cloudrouter.atlassian.net/browse/CR-123
- Agreed: https://cloudrouter.atlassian.net/browse/CR-124
- Agreed: https://cloudrouter.atlassian.net/browse/CR-125
- Agreed: https://cloudrouter.atlassian.net/browse/CR-128
- Agreed: https://cloudrouter.atlassian.net/browse/CR-138
- Agreed: https://cloudrouter.atlassian.net/browse/OSV-1
Full Log
------------------- Meeting Started @ 16:00 UTC -------------------
shainesus 16:00
.topic CloudRouter v3 Planning -- https://cloudrouter.atlassian.net/issues/?filter=11000
chair shaines ckannan jkt
Greetings all!
For those playing at home, the list above I have sorted with CR-3 being at the top. We currently have 14 JIRA's targeted for the next release. Lets jump in:
----------------------
juliettkilotango 16:01
The gang is all here!!
----------------------
ckannan 16:01
here
----------------------
shainesus 16:01
https://cloudrouter.atlassian.net/browse/CR-3 :: Additional software (JIRA unassigned)
I think we all agree we want these enhancements, but should we break these asks out into seperate JIRAs?
(queue Jeopardy theme)
----------------------
juliettkilotango 16:02
Yes, any additional components need to be separate JIRA tickets so we can proceed through the new package addition process
----------------------
shainesus 16:03
ok. any of these we don't wish to target for this upcoming release?
----------------------
abn 16:03
i would say we get the basics installed by default
----------------------
juliettkilotango 16:04
With the exception of softflowd, all should be easy, and already packaged in Fedora/CentOS, so just a matter of picking up.
----------------------
ckannan 16:04
Ack.
----------------------
shainesus 16:04
Roger that. Noted. I'll take the action to split these out.
https://cloudrouter.atlassian.net/browse/CR-9 :: Add SDX to CloudRouter (JIRA unassigned)
In or out? If in, who owns?
----------------------
abn 16:05
i can attempt the packaging if required
----------------------
shainesus 16:05
@juliettkilotango still targeting this?
----------------------
juliettkilotango 16:06
I would like to . . . and I think the dependency chain is pretty light.
----------------------
shainesus 16:06
ok
next up:
https://cloudrouter.atlassian.net/browse/CR-31 :: BIRD feature request (JIRA unassigned)
----------------------
ckannan 16:06
would like to include https://cloudrouter.atlassian.net/browse/CR-138 in this discussion
----------------------
shainesus 16:06
ok
----------------------
abn 16:06
i think 138 +1
----------------------
juliettkilotango 16:06
I do not see CR-138 landing for CR.next
Cool. @abn just volunteered!
----------------------
abn 16:07
CR-31 is a hard ask for CR3
darn me and my fat fingers
:smile:
----------------------
shainesus 16:08
just to be clear, CR-138 is in, yes?
----------------------
ckannan 16:09
upstream has rpm support. so it should be fairly easy i think
----------------------
shainesus 16:09
ok.
is CR-31 in as well?
----------------------
ckannan 16:10
need a volunteer for that ...we have to write bird code
----------------------
abn 16:10
@ckannan better to defer that to next
----------------------
SiegristJ 16:10
Let's leave CR-31 out.. and if we come back around to it before the BETA, then we will see if it fits in
----------------------
juliettkilotango 16:11
Ugh . . . that is what I meant!
I'm all for CR-138 . . . previous comment about 138 should have been in-reference to CR-31
Next up? OSV-1?
----------------------
abn 16:12
that was fixed upstream
----------------------
shainesus 16:12
ok.
----------------------
abn 16:12
we either need to add a patched version of the jar in our build or see if ODL consumed the upstream fix
so its do-able
----------------------
shainesus 16:13
ok, we'll leave targeted.
@juliettkilotango votes for ODL first, carry patch second, but yes, both are doable in the v.next timeframe
----------------------
abn 16:13
just saying would have been easier if we did fedora packaging
:smile:
----------------------
shainesus 16:13
ah, ok.
https://cloudrouter.atlassian.net/browse/CR-53 :: Split out components into separate repositories (JIRA unassigned)
I see @SiegristJ jumped on this and is now resolved.
https://cloudrouter.atlassian.net/browse/CR-63 :: [New Package Request] Ostinato
----------------------
juliettkilotango 16:14
That explains why it is not in my list!
----------------------
abn 16:14
gives @SiegristJ a cookie
----------------------
shainesus 16:14
do-able?
----------------------
abn 16:14
Ostinato - valid spec exists
----------------------
shainesus 16:14
ok
----------------------
juliettkilotango 16:14
CR-63 . . . Ostinato has deps on QT, but that is shipped with both Fedora and CentOS, so fairly easy. Not sure about the load of the package review, however
----------------------
SiegristJ 16:15
still requires a security review
----------------------
juliettkilotango 16:15
Yep. And anything described as "Wireshark in reverse" scares the daylights out of me from a security perspective.
----------------------
abn 16:15
+1
----------------------
shainesus 16:15
lets leave it and make it a stretch goal then.
----------------------
abn 16:16
especially its a GUI app
----------------------
juliettkilotango 16:16
There is no compelling reason to ship it other than coolness factor
----------------------
shainesus 16:16
ok, so out?
----------------------
abn 16:16
out +1
----------------------
juliettkilotango 16:16
That is my vote.
----------------------
ckannan 16:16
kick it
----------------------
juliettkilotango 16:16
out +0.04
----------------------
shainesus 16:16
https://cloudrouter.atlassian.net/browse/CR-71 :: Integration of Cockpit Management Console into CloudRouter
----------------------
abn 16:16
@juliettkilotango heh
----------------------
shainesus 16:16
i know we chatted about this.
but is there anything from a pre-config standpoint we want to consider?
----------------------
ckannan 16:17
we wanted a plugin of sorts..iirc
----------------------
abn 16:17
yeah we should defer this till we figure out what the plugin is
----------------------
juliettkilotango 16:17
Yep. Plugin is the way to go.
----------------------
SiegristJ 16:17
is there value in shipping it without any specific CloudRouter plugin?
----------------------
juliettkilotango 16:17
Agreed. Kick the can.
----------------------
shainesus 16:17
makes sense. i don't see a JIRA for the plugin plan.
happy to file.
@SiegristJ well cockpit is in Fedora by default, no?
----------------------
abn 16:18
Available Packages
cockpit.x86_64 0.71-1.el7 extras
^ centos
----------------------
shainesus 16:18
i was thinking more on the CentOS side.
oh!
cool.
----------------------
ckannan 16:18
ya its on both fedora and centos
----------------------
abn 16:18
its in extras
----------------------
shainesus 16:18
ok, so we defer until we have a plugin plan, yes?
----------------------
ckannan 16:18
ya
----------------------
abn 16:19
yeah i would drop that issue completely
or rebrand it
----------------------
shainesus 16:19
ok.
----------------------
abn 16:19
:p
----------------------
shainesus 16:19
i'll take that action.
https://cloudrouter.atlassian.net/browse/CR-72 :: CloudRouter - provide as coreOS containers
----------------------
juliettkilotango 16:19
Re-imagine the issue
----------------------
abn 16:19
CR-72 - we have bird ACI
----------------------
juliettkilotango 16:19
CR-72 should happen
----------------------
SiegristJ 16:19
not if there isn't any community demand yet
----------------------
juliettkilotango 16:20
Quick someone . . . demand :smile:
----------------------
abn 16:20
@SiegristJ deliver ahead of demand
I WANT IT
----------------------
juliettkilotango 16:20
A solution in search of a problem
----------------------
abn 16:20
@SiegristJ already done really > https://github.com/cloudrouter/cloudrouter-aci
:smile:
we need more specific tasks though
----------------------
shainesus 16:21
it would be interesting to see if its at all raised @ AWS re:Invent in some way. :wink:
----------------------
juliettkilotango 16:21
I'll certainly keep my ears open on that topic.
----------------------
shainesus 16:21
ok, will leave targeted unless there is an objection.
----------------------
juliettkilotango 16:21
Might even seed a few conversations
----------------------
shainesus 16:21
next up:
https://cloudrouter.atlassian.net/browse/CR-114 :: Unable to launch CloudRouter image in OpenStack
----------------------
juliettkilotango 16:21
Upstream Fedora issue
Which is still open
----------------------
shainesus 16:22
hmm...i can chase up?
----------------------
abn 16:22
@juliettkilotango beat them with a stick?
----------------------
ckannan 16:22
we can help them
----------------------
shainesus 16:22
ok, will leave on the list and track.
----------------------
juliettkilotango 16:22
Yep
----------------------
shainesus 16:22
https://cloudrouter.atlassian.net/browse/CR-123 :: Change fastnetmon.conf defaults
Here again I see @SiegristJ addressed this already. Thanks!
----------------------
juliettkilotango 16:22
Resolved already
----------------------
shainesus 16:23
https://cloudrouter.atlassian.net/browse/CR-124 :: Upgrade DPDK to 2.1 and build dpdk-tools,dpdk-examples and igb_uio.ko kernel module
----------------------
juliettkilotango 16:23
Prior to 2.0 launch
----------------------
abn 16:23
+1 for CR-124
----------------------
ckannan 16:23
+1
----------------------
shainesus 16:23
ok.
----------------------
juliettkilotango 16:23
Agreed. That stuff is becoming more important by the day.
----------------------
shainesus 16:23
https://cloudrouter.atlassian.net/browse/CR-125 :: Build and package dpdk pktgen
same i take it.
----------------------
juliettkilotango 16:24
Yep
----------------------
shainesus 16:24
ok.
https://cloudrouter.atlassian.net/browse/CR-127 :: SnabbSwitch - New package request
----------------------
juliettkilotango 16:24
Needs security review . . . might be best to defer given we already have higher priority packages
----------------------
abn 16:24
+1
----------------------
shainesus 16:24
ok.
----------------------
abn 16:25
moving to new workflow
----------------------
shainesus 16:25
https://cloudrouter.atlassian.net/browse/CR-128 :: Reduce base image size
----------------------
abn 16:25
you know my vote
----------------------
juliettkilotango 16:25
@abn ?
abn 16:25
+1
----------------------
juliettkilotango 16:25
Containers?
Or coffee?
----------------------
ckannan 16:25
containers and vm's both
----------------------
abn 16:25
all of the above wold be good
----------------------
juliettkilotango 16:25
Ah, I know . . . big green button!
----------------------
abn 16:25
NOOOOOO!
IT BURNS
but yes reduce size on containers and vms
----------------------
juliettkilotango 16:26
Smaller image means different "flavors" . . . or better yum groups, maybe? 'yum install dpdk-offload'
----------------------
ckannan 16:26
yummy groups
----------------------
juliettkilotango 16:26
s/'yum install/'yum groupinstall/
----------------------
SiegristJ 16:27
the low hanging fruit is custom groups
where all non-essential packages are stripped
even if they're in '@core' or '@base'
----------------------
shainesus 16:27
i like that idea. i assume doable in the v3 timeframe?
----------------------
juliettkilotango 16:27
Yes. Should be.
----------------------
shainesus 16:27
ok.
----------------------
ckannan 16:27
ack
----------------------
shainesus 16:28
https://cloudrouter.atlassian.net/browse/OSV-1 :: JLine spews stacktrace when using the OpenDaylight appliance (JIRA unassigned)
----------------------
abn 16:28
thought we discussed that
----------------------
shainesus 16:28
we did?
you went out of order?!?
----------------------
abn 16:29
@juliettkilotango votes for ODL first, carry patch second, but yes, both are doable in the v.next timeframe
----------------------
ckannan 16:29
isn't it fixed ?
----------------------
shainesus 16:29
it was fixed by Unassigned? Who's Unassigned? :wink:
----------------------
abn 16:30
no one knows
----------------------
ckannan 16:30
not me
----------------------
juliettkilotango 16:30
Our newest associate.
----------------------
shainesus 16:30
ok, so i'll leave as is.
----------------------
abn 16:30
she is a borrower
----------------------
shainesus 16:30
and just to be clear -- https://cloudrouter.atlassian.net/browse/CR-138 :: New Package : RYU SDN Framework -- is also in, correct?
----------------------
abn 16:31
yeah it is
i can look into if required
----------------------
juliettkilotango 16:31
yep
----------------------
ckannan 16:31
yes
----------------------
shainesus 16:31
ok. that's the list. any additional suggestions?
If nothing else to propose, we'll close it out at .5 hours!
----------------------
ckannan 16:32
we should probably investigate opennsl
----------------------
shainesus 16:32
link of any sort?
----------------------
ckannan 16:32
https://github.com/Broadcom-Switch/OpenNSL
@shainesus makes note
----------------------
abn 16:32
interesting
----------------------
shainesus 16:32
any objections?
to at least investigate for possible v3 inclusion?
----------------------
ckannan 16:33
and the SAI from microsoft -- https://azure.microsoft.com/en-us/blog/microsoft-furthers-open-networking-specification/
https://github.com/opencomputeproject/OCP-Networking-Project-Community-Contributions/tree/master/sai/doc
----------------------
abn 16:34
@ckannan does OpenNSL fit in our near term use cases for CR?
----------------------
ckannan 16:34
i know we have a longer term roadmap item to do a whitebox CR
this might fit in there.
near term == probably not
----------------------
shainesus 16:35
ok, so file for future consideration.
----------------------
abn 16:35
yes
----------------------
ckannan 16:35
yeah...at least we can keep an eye on the community
----------------------
abn 16:35
do we have the roadmap documented yet?
----------------------
ckannan 16:36
Nothing outside of this - https://cloudrouter.atlassian.net/wiki/display/CPD/CloudRouter+Roadmap
----------------------
shainesus 16:36
depends on what you are defining as "roadmap".
----------------------
abn 16:36
i think i am more interested in "use case scenarios" put into some form of time line
----------------------
ckannan 16:36
more like a wishlist item
----------------------
shainesus 16:38
we should schedule a meeting to discuss this off-line. its one of the things i wanted to kick-off and have regular discussion around.
----------------------
abn 16:38
cool
----------------------
ckannan 16:38
i like it
----------------------
demolitiongirl 16:38
You guys mean like user stories?
----------------------
shainesus 16:38
yes
----------------------
abn 16:38
@demolitiongirl yes
----------------------
shainesus 16:39
@demolitiongirl i failed to include in the agenda about the site changes.
anything you desire input on?
----------------------
demolitiongirl 16:39
I can help develop user stories, just let me know what you need
----------------------
shainesus 16:39
ok, cool!
----------------------
demolitiongirl 16:40
So I just wanted to make sure everybody would be fine with me asking Brendan to do some shuffling of the site to organise the info a bit better
----------------------
shainesus 16:40
+1.1!
----------------------
demolitiongirl 16:40
My main question is, how does everyone feel about the front page being the news/blog instead of the static content we have now?
----------------------
shainesus 16:40
i'm all for improving look and navigation.
----------------------
ckannan 16:41
we should look at how other communities are organized
but ya i'm all for improvements as well
----------------------
shainesus 16:41
are we talking cr.org or https://cloudrouter.atlassian.net ?
----------------------
juliettkilotango 16:41
yes
----------------------
demolitiongirl 16:41
cr.org - it'd involve moving some content around too
----------------------
juliettkilotango 16:42
Actually the atlassian site is pretty solid. Needs some content updates, but the site is solid.
----------------------
abn 16:42
+1 for cr.org changes
----------------------
demolitiongirl 16:42
Well my idea was to have the wiki as a rough draft area and for the planning stuff, and then have good stable cleaned up docs hosted in github on the main website
----------------------
shainesus 16:42
work needs to be done on https://cloudrouter.atlassian.net, but agree, cr.org needs the most attention.
----------------------
ckannan 16:43
Can we redirect cr.org to https://cloudrouter.atlassian.net/ ?
and maintain the content on https://cloudrouter.atlassian.net/
----------------------
demolitiongirl 16:43
ckannan I wouldn't want to do that
----------------------
shainesus 16:43
@ckannan https://cloudrouter.atlassian.net isn't a customizable. doesn't make for a good marketing tool.
s/a/as
we still need cr.org or some facsimile.
----------------------
demolitiongirl 16:44
Yeah that, and wikis cause all sorts of problems down the track as the project gets bigger, especially relating to translation and accessibility
----------------------
abn 16:44
yeah cr.org should be a separate site
----------------------
demolitiongirl 16:45
As a technical writer, I hate wikis, but I understand they have their use cases (for example I think it's better to have the roadmap and meeting docs in there)
----------------------
shainesus 16:45
lets do this - here again, lets discuss off-line. i want to ensure other stakeholders are ok with such. put a proposal in front of them before we do anything.
----------------------
demolitiongirl 16:46
No worries
----------------------
juliettkilotango 16:46
Ugh. I thought Atlassian had a proper website offering, but it does not seem that is the case. Agreed that doing a website as a wiki is a pain in the rump!
----------------------
shainesus 16:47
thanks for checking @juliettkilotango. bummer. well, if no objections, and no additional topics, we can close it out.
----------------------
ckannan 16:47
yup
----------------------
juliettkilotango 16:47
I second the closure of the meeting.
----------------------
shainesus 16:47
Thanks for all who participated! Meeting archive will be available @ https://cloudrouter.atlassian.net/wiki/x/B4Cl
------------------- Meeting Ended @ 16:47 UTC -------------------
----------------------
sonoble 17:34
Sorry I missed the meeting, if you want input on OpenNSL/OF-DPA, I can give some color there.
----------------------
ckannan 18:48
Sure. Please do. Either here or by email would be great.
----------------------
sonoble 19:11
The problem with how Broadcom releases them is that the binaries only work with a specific kernel and to get the code to compile it yourself you need an agreement with Broadcom, to distribute it, you need another agreement.. lots of legal fun.
----------------------
sonoble 19:31
It's also worthwhile to note that running linux on whitebox switches sounds easy, but harkens back to the days of having to know what IRQ your modem was using..
you can run linux, but having it interpret the hardware and behave correctly is a lot of work. Carlos from Cumulus gave a good talk on it, essentially saying it takes about 90 days of work to get the basics working on any new device they get
----------------------
ckannan 21:41
Ah.. Thanks for the insights sonoble. Appreciated.
----------------------
abn 00:59
Yeah useful insights thanks @sonoble
----------------------