Re: [openstack-dev] [tripleo][networking] Organizing the networking squad
On Mon, Oct 16, 2017 at 2:44 PM, Harald Jensas wrote: > Include me as well Brent. > > > // > Harald > > On 16 Oct 2017 3:41 p.m., "Saravanan KR" wrote: > > Thanks for initiating Brent. Yes, I would participate in the networking > squad. > > Regards, > Saravanan KR > > On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote: > > Hi, > > > > On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles > wrote: > >> > >> Hi all, > >> > >> The list of TripleO squads includes a "networking squad". In previous > >> cycles, coordinating outside of IRC and email conversations seemed > >> unnecessary as there were only a few contributors and a small number of > >> initiatives. However, with future container related work, increased > usage of > >> ansible, ongoing efforts like routed networks and NFV, os-net-config > related > >> issues, and the increasing number of backends and networking related > >> services being added to TripleO, the world of TripleO networking seems > >> increasingly busy. I propose that we start organizing properly with > periodic > >> sync-ups and coordinating efforts via etherpad (or similar) as well as > >> reporting into the weekly tripleo meeting. > >> > >> Cheers, > >> > >> Brent > > > > > > This was initially not directed at anyone in particular but I've added > > possible interested parties to this thread in case it gets lost in the > > noise! Please reply if you are interested in participating in the > networking > > squad. Proposed first orders of business are: > > > > - establish the squad's scope > > - agree on whether we need a scheduled sync up meeting and if so, sort > out > > a meeting time time > > - outline initial areas of interest and concern and action items > > > > Cheers, > > > > Brent > > Thanks for the replies everyone! The squad has a status etherpad! See https://etherpad.openstack.org/p/tripleo-networking-squad-status. It is very sparse for now as we are just getting organized, but I've added a visually grepped list of blueprints that seem likely related as an illustration of just how much is planned or underway! I'll be reaching out to you all over the next few days to try and coordinate a meeting time. As always, timezones may prove a challenge but we should be able to sort something out. Thanks again for your interest and participation! Cheers, Brent __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][networking] Organizing the networking squad
Include me as well Brent. // Harald On 16 Oct 2017 3:41 p.m., "Saravanan KR" wrote: Thanks for initiating Brent. Yes, I would participate in the networking squad. Regards, Saravanan KR On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote: > Hi, > > On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote: >> >> Hi all, >> >> The list of TripleO squads includes a "networking squad". In previous >> cycles, coordinating outside of IRC and email conversations seemed >> unnecessary as there were only a few contributors and a small number of >> initiatives. However, with future container related work, increased usage of >> ansible, ongoing efforts like routed networks and NFV, os-net-config related >> issues, and the increasing number of backends and networking related >> services being added to TripleO, the world of TripleO networking seems >> increasingly busy. I propose that we start organizing properly with periodic >> sync-ups and coordinating efforts via etherpad (or similar) as well as >> reporting into the weekly tripleo meeting. >> >> Cheers, >> >> Brent > > > This was initially not directed at anyone in particular but I've added > possible interested parties to this thread in case it gets lost in the > noise! Please reply if you are interested in participating in the networking > squad. Proposed first orders of business are: > > - establish the squad's scope > - agree on whether we need a scheduled sync up meeting and if so, sort out > a meeting time time > - outline initial areas of interest and concern and action items > > Cheers, > > Brent > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][networking] Organizing the networking squad
Thanks for initiating Brent. Yes, I would participate in the networking squad. Regards, Saravanan KR On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles wrote: > Hi, > > On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote: >> >> Hi all, >> >> The list of TripleO squads includes a "networking squad". In previous >> cycles, coordinating outside of IRC and email conversations seemed >> unnecessary as there were only a few contributors and a small number of >> initiatives. However, with future container related work, increased usage of >> ansible, ongoing efforts like routed networks and NFV, os-net-config related >> issues, and the increasing number of backends and networking related >> services being added to TripleO, the world of TripleO networking seems >> increasingly busy. I propose that we start organizing properly with periodic >> sync-ups and coordinating efforts via etherpad (or similar) as well as >> reporting into the weekly tripleo meeting. >> >> Cheers, >> >> Brent > > > This was initially not directed at anyone in particular but I've added > possible interested parties to this thread in case it gets lost in the > noise! Please reply if you are interested in participating in the networking > squad. Proposed first orders of business are: > > - establish the squad's scope > - agree on whether we need a scheduled sync up meeting and if so, sort out > a meeting time time > - outline initial areas of interest and concern and action items > > Cheers, > > Brent > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][networking] Organizing the networking squad
Hi, On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles wrote: > Hi all, > > The list of TripleO squads includes a "networking squad". In previous > cycles, coordinating outside of IRC and email conversations seemed > unnecessary as there were only a few contributors and a small number of > initiatives. However, with future container related work, increased usage > of ansible, ongoing efforts like routed networks and NFV, os-net-config > related issues, and the increasing number of backends and networking > related services being added to TripleO, the world of TripleO networking > seems increasingly busy. I propose that we start organizing properly with > periodic sync-ups and coordinating efforts via etherpad (or similar) as > well as reporting into the weekly tripleo meeting. > > Cheers, > > Brent > This was initially not directed at anyone in particular but I've added possible interested parties to this thread in case it gets lost in the noise! Please reply if you are interested in participating in the networking squad. Proposed first orders of business are: - establish the squad's scope - agree on whether we need a scheduled sync up meeting and if so, sort out a meeting time time - outline initial areas of interest and concern and action items Cheers, Brent __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tripleo][networking] Organizing the networking squad
Hi all, The list of TripleO squads includes a "networking squad". In previous cycles, coordinating outside of IRC and email conversations seemed unnecessary as there were only a few contributors and a small number of initiatives. However, with future container related work, increased usage of ansible, ongoing efforts like routed networks and NFV, os-net-config related issues, and the increasing number of backends and networking related services being added to TripleO, the world of TripleO networking seems increasingly busy. I propose that we start organizing properly with periodic sync-ups and coordinating efforts via etherpad (or similar) as well as reporting into the weekly tripleo meeting. Cheers, Brent __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
