16:03:12 <frankbrockners> #startmeeting BGS team meeting
16:03:12 <collabot> Meeting started Tue Mar 10 16:03:12 2015 UTC.  The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:12 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:03:12 <collabot> The meeting name has been set to 'bgs_team_meeting'
16:03:26 <arnaud_orange> hi guys
16:03:42 <B_Smith_> can you send the connection link?
16:04:11 <frankbrockners> #link https://global.gotomeeting.com/join/156654573
16:04:12 <dfarrell07> https://global.gotomeeting.com/join/156654573
16:04:18 <dfarrell07> tie ;)
16:04:27 <B_Smith_> thanks!
16:04:34 <frankbrockners> #chair dfarrell07
16:04:34 <collabot> Current chairs: dfarrell07 frankbrockners
16:04:44 <dfarrell07> arnaud_orange: hey :)
16:09:36 <frankbrockners> #chair dneary
16:09:36 <collabot> Current chairs: dfarrell07 dneary frankbrockners
16:10:12 <dfarrell07> there's no audio atm, right? not just an issue on my end?
16:10:34 <frankbrockners> #info Arnaud's thoughts: He'd be happy to help others to try OpenSteak. Plans to add documentation
16:10:45 <frankbrockners> dfarrell: Seems to be a problem on your end
16:10:47 <dfarrell07> humm, I must have a connection iossue
16:10:52 * dfarrell07 drops
16:10:53 <frankbrockners> I can hear Arnaud talk
16:11:06 <B_Smith_> audio OK here
16:11:59 <frankbrockners> #info Arnaud looks for help deploying ODL - Dan Farrell is helping. Anyone else with knowledge on Ubuntu?
16:12:34 <dneary> can people hear me or is the sound bad again?
16:12:50 <frankbrockners> dneary: audio from you is good
16:12:59 <dneary> thanks
16:13:13 * dfarrell07 has sound
16:14:51 <frankbrockners> #info Arnaud looked at work of the other teams (e.g. Foreman approach)
16:17:04 <frankbrockners> #info Dan Farrell: Use reasonable size components (using ODL as an example). Better issue tracking: Use Jira.
16:18:09 <dfarrell07> #info dfarrell07 revises "reasonable size" to "reusable", maybe an audio connection issue
16:18:29 <frankbrockners> thanks Dan..
16:19:20 <frankbrockners> #info Dave Neary: Document the issues that people have. Document where things are missing - also from an documentation perspective.
16:20:06 <frankbrockners> #info Dave Neary: Work together on the end-result - i.e. puppet manifests, cookbooks etc.
16:21:45 <dneary> #info dneary: Feedback on the OpenStack + OpenDaylight documentation upstream is welcome and needed.
16:21:54 <dneary> #link https://wiki.opendaylight.org/view/OpenStack_and_OpenDaylight
16:21:56 <dfarrell07> #info A common point many folks are making is to work on common parts of the approaches via their upstream projects (ODL docs for learning ODL+OpenSTack, ODL Puppet mod for deploying ODL, etc)
16:21:57 <frankbrockners> #info Joseph: Look at what is common between the installers. Describe things in words first - even if the tools are different.
16:22:32 <frankbrockners> #info Joseph: Example: Common network layout would be a good starting point.
16:24:08 <frankbrockners> #info Reinaldo: Has ODL background. Was trying to become more active on the project - but it is hard to find a starting point.
16:25:58 <frankbrockners> #info Reinaldo: Better documentation. One installer. If we cannot have one single installer - more documentation on the different approaches.
16:26:39 <frankbrockners> #info Reinaldo: Documentation - incl. what is done, what isn't done, where should I go from now?
16:28:16 <frankbrockners> #info Reinaldo: Be active. Very active projects often become the de-facto agreement.
16:30:23 <frankbrockners> #info Brian: Still in monitoring mode... - there is no one common place to go to find all info.
16:30:47 <frankbrockners> #info Brian: Information is too scattered and changing too rapidly.
16:31:35 <frankbrockners> #info Brian: Try to be more consistent in the tools we use. Create a history page to explain how things evolved - to understand why things are the way they are.
16:32:39 <frankbrockners> #info: Dan: Leverage public issue tracker for maintaining history
16:34:17 <frankbrockners> #info: Tim: More email (for BGS). Overcommunicate on what you do. Avoid "giant updates".
16:34:44 <frankbrockners> #info: Tim: Change "experiments" to "deployment tools"
16:35:14 <frankbrockners> #info: Tim: Break down each installer into individual functions. Identify which pieces are independent from each other
16:35:43 <frankbrockners> #info: Tim: The breakdown into individual functions would be a good way to identify common functions
16:36:01 <frankbrockners> #info: Tim: Move to Jira. Better tool to track issues and assign tasks
16:37:18 <frankbrockners> #info: Uli: Transparency is an issue. Share what are the problems for a particular deployment approach.
16:38:04 <frankbrockners> #info Uli: Hard for an outsider to understand a particular problem and start to help.
16:39:03 <frankbrockners> #info Uli: Recommendation for using Jira if an explicit task can be identified.
16:39:04 <dfarrell07> #link https://github.com/dfarrell07/puppet-opendaylight/issues?q=label%3Agood-for-beginners+ Example of using labels to ID easy to handle issues
16:39:53 <frankbrockners> #info Uli: Find a way to share where current deployment approaches are stuck. Avoid competition.
16:46:30 <frankbrockners> #info Frank: Smaller contributions ease review and identify eventual commonality
16:46:53 <dfarrell07> #info dfarrell07 suggests that as we move to Jira we consider something like a "good for beginners" label for marking TOODs that less-expert community members can likely handle without too much spin-up time
16:47:41 <frankbrockners> #info Josef: For documentation: Let's try to make sure we use one tool for documentation - and avoid divergence there
16:50:30 <dneary> I have to drop off. Thanks for the call!
16:50:39 <frankbrockners> Thanks Dave
16:52:12 <frankbrockners> #topic How can we identify "common" modules (and place them into a common directory tree)
16:52:46 <frankbrockners> #info dfarrel07 - any changes to installers should happen upstream
16:54:50 <B_Smith_> hmmm is that discussion available as a video on line...the red hat installer?
16:54:55 <frankbrockners> #info Reinaldo: Suggestion: Do a detailed step-by-step walk-through presentation of every deployment approach. Helps to understand the big picture
16:55:27 <frankbrockners> B_Smith_: yes for Foreman - but there isn't anything similar for Fuel and OpenSteak
17:00:53 <frankbrockners> #action Tim to setup a series of sessions to describe the Foreman/Quickstack approach
17:01:37 <frankbrockners> #action Arnaud to setup a series of sessions to describe the Foreman/Quickstack approach
17:02:19 <dfarrell07> you can #undo it frankbrockners
17:02:30 <frankbrockners> #undo
17:02:30 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Action object at 0x1df3850>
17:02:43 <frankbrockners> #action Arnaud to setup a series of sessions to describe the OpenSteak approach
17:03:27 <frankbrockners> #endmeeting