Difference between revisions of "Meetings/ServiceFunctionChainingMeeting"

Revision as of 18:26, 8 October 2015

Weekly Neutron Service Function Chaining Meeting Info

 Weekly on Thursday at 1700 UTC in #openstack-meeting-4 (IRC webclient)
 Chair (to contact for more information): Cathy Hong Zhang (cathy-h-zhang), Louis Fourie (louis-fourie)
 Logs from past meetings: http://eavesdrop.openstack.org/meetings/service_chaining/2015/

Agenda for the next Networking - Service Function Chaining Meeting

Reminders from Previous Meeting

• Change to publish networking-sfc/doc/source documents to http://docs.openstack.org/developer/networking-sfc has merged
• Documentation is now being published
• Link from http://docs.openstack.org/developer/openstack-projects.html to docs.openstack.org/developer/networking-sfc is now present and working
• Meeting page http://eavesdrop.openstack.org/#Neutron_Service_Chaining_meeting is updated with link to meeting logs and this agenda wiki page

Topics for Next Meeting

• Python 3 jobs - Zuul is currently setup to NOT run python3 jobs. Do we want to add these jobs? See http://docs.openstack.org/infra/manual/creators.html#configure-zuul-to-run-jobs for example setup documentation that includes configuring python3 jobs
• FYI: Zuul is also not configured to run translation jobs. At some point we'll need to address translations.

Changes Needing Review

Thanks to Louis for splitting out the monster patch into manageable chunks

• This change https://review.openstack.org/207251 is replaced by the changes below
• https://review.openstack.org/#/c/227069/
• https://review.openstack.org/#/c/227074/
• https://review.openstack.org/#/c/227097/
• https://review.openstack.org/#/c/227098/
• https://review.openstack.org/#/c/227100/
• https://review.openstack.org/#/c/227285/

Also needing review:

• https://review.openstack.org/#/c/210008/ - Command line support
• https://review.openstack.org/#/c/225254/ - Documentation update (for http://docs.openstack.org/developer/networking-sfc)

Discussion Topics

• Corrections to spec documents when issues are discovered during coding. Proposal: Make corrections to the spec immediately and include the revised spec doc in the same commit as the code changes. This allows the reviewers to provide feedback on both the spec and the code simultaneously and make sure that both are in agreement before merging. See comments on https://review.openstack.org/#/c/210008/ for example.