Re: [openstack-dev] [kuryr] Nominate Kirill Zaitsev as kuryr-tempest-core reviewer

+1 On Tue, Jul 4, 2017 at 12:28 PM, Daniel Mellado wrote: > Hi Team, > > I wanted to nominate Kirill for kuryr-tempest-core reviewer. He's been a > great help from start both contributing and reviewing. > > Please voice your support or concerns if any > > Best! > >

Re: [openstack-dev] [Dragonflow] Nominating Xiao Hong Hui for core of Dragonflow

+1 On Thu, Feb 9, 2017 at 12:16 PM, Omer Anson wrote: > Hello, > > I would like to nominate Xiao Hong Hui as a core reviewer for Dragonflow. > > Since he has joined, Xiao has helped move the project forwards with > important commits and very helpful reviews. He has shown

Re: [openstack-dev] [kuryr] Ocata cycle ending and proposing new people as Kuryr cores

+1 for both. On Sun, Jan 15, 2017 at 9:05 AM, Irena Berezovsky wrote: > > > On Fri, Jan 13, 2017 at 6:49 PM, Antoni Segura Puimedon < > celeb...@gmail.com> wrote: > >> Hi fellow kuryrs! >> >> We are getting close to the end of the Ocata and it is time to look back >> and

[openstack-dev] [Kuryr][Dragonflow] - PTL Non Candacy

Hello all, I would like to announce that i will not be running for projects Kuryr or Dragonflow PTL. I believe that both projects shows great value and progress compared to the time they exists mostly thanks to the great communities actively working on both of them. I also strongly believe that

[openstack-dev] [Dragonflow] - Design summit rooms allocation

Hello all, I have opened the following etherpad in order to brainstorm topics and sessions for Barcelona summit: https://etherpad.openstack.org/p/dragonflow-barcelona Feel free to edit/add anything you would like to discuss about. Thanks Gal.

Re: [openstack-dev] [Kuryr] Proposing vikasc for kuryr-libnetwork core

The entire core team voted +1. I have added Vikas to Kuryr core team, Congrats and keep up the good work Thanks Gal. On Thu, Aug 18, 2016 at 7:56 PM, Mohammad Banikazemi wrote: > +1 > Vikas has been working on various aspects of Kuryr with dedication for > some time. So yes

[openstack-dev] [Kuryr] - Design summit rooms allocation

Hello all, We need to decide on the number of rooms we need for the design summit. I have started the below etherpad so we can all brainstorm the sessions we would like to conduct (and who is going to chair them): https://etherpad.openstack.org/p/kuryr-barcelona (For the Austin summit we had 1

Re: [openstack-dev] [Kuryr] Proposing vikasc for kuryr-libnetwork core

+1 , Vikas has been doing a great work on the project and is a good addition to the team. On Wed, Aug 17, 2016 at 12:54 AM, Antoni Segura Puimedon wrote: > Hi Kuryrs, > > I would like to propose Vikas Choudhary for the core team for the > kuryr-libnetwork subproject. Vikas

[openstack-dev] [Dragonflow] - No IRC Meeting Today (1/8/2016)

Hello All, Due to some members not able to attend today's meeting, we will cancel it and continue the meetings the week after. If you need an update regarding anything, feel free to stop by #openstack-dragonflow Thanks Gal.

[openstack-dev] [Kuryr] - Addition of Fuxi as a subproject

Hello everyone, The following is a governance request to add project Fuxi as a storage solution part for Kuryr (part of Kuryr deliverable) [1] I hope this can lead to other initiatives that want to work on drivers and glue code that connects containers orchestration engines and OpenStack

[openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

Hello all, I am writing this out to provide awareness and hopefully get some work started on the above topic. We have merged a spec about supporting nested containers and integration with Magnum some time ago [1] , Fawad (CCed) led this spec. We are now seeking for volunteers to start

[openstack-dev] [Dragonflow] - No IRC meeting today (06/13)

Hello all, Sorry for the late notice but we will not have an IRC meeting today. We will continue the IRC meetings next week. Thanks Gal. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Neutron] neutron-lib and dependencies in neutron reference implementation

For example references to the various different agents which are an implementation details to me On Wed, Jun 8, 2016 at 8:51 PM, Henry Gessau <hen...@gessau.net> wrote: > Gal Sagie <gal.sa...@gmail.com> wrote: > > Hello all, > > > > I have recently came across

[openstack-dev] [Neutron] neutron-lib and dependencies in neutron reference implementation

Hello all, I have recently came across some missing constants in neutron-lib and sent a patch but i wanted to try and understand the scope of the lib. I see that the Neutron lib consist of many definitions which are actually part of the reference implementation and are not really "generic"

[openstack-dev] [Kuryr] - IRC Meeting time change

Hello Everyone, Just wanted to let you all know we changed our even biweekly IRC meeting time. It is now one hour earlier. The new meeting time is *every even Monday at 14:00 UTC in #openstack-meeting-4* You can see the changing patch here [1] Thanks Gal. [1]

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Hi Hongbin, Thank you for starting this thread. The person that is going to work on this integration is Fawad (CC'ed) and hopefully others will help him (We have another person from Huawei that showed intrest in working on this). I think Fawad, given that he is the primary person working on this

[openstack-dev] [Infra][Kuryr] New sub projects created

Hello all, We have created the following repositories as part of Kuryr: https://github.com/openstack?utf8=%E2%9C%93=kuryr Would love if anyone from Infra that has access can allow kuryr-core team to also be able to review/merge code in these new repositories. Would also love if the TC can

[openstack-dev] [Dragonflow] - IRC Meeting time

Hello All, During the summit we received feedback that many people from the US time zone would like to attend our IRC meetings. Our current time is 0900 UTC which is good for Europe/Israel/China where most of our contributors come from. If you are in the US and would like to participate in our

[openstack-dev] [Dragonflow] - No IRC Meeting (5/9)

Hello Everyone, We will not have an IRC meeting in the upcoming Monday (5/9), we will continue doing IRC meeting in our regular time the week after. Thanks Gal. __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Infra][Kuryr] - Sub repositories

Hello all, Following the summit discussions and after summit checking we decided its better for us to try a sub repositories model for Kuryr (better for packaging and requirement/dependencies management). We would like to create additional sub repositories under Kuryr and i was wondering if the

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

Maybe it can help if instead of trying to define criteria to which projects dont fit into the stadium, try to define in your spec what IT IS, and for what purpose its there. On Mon, May 2, 2016 at 8:53 PM, Kyle Mestery wrote: > On Mon, May 2, 2016 at 12:22 PM, Armando M.

[openstack-dev] [Kuryr] - Austin Design Summit

Hello everyone, We have split our design summit sessions into topics (and sub topics) for each session Please review the topics and agenda here: https://etherpad.openstack.org/p/kuryr-design-summit This is still a tentative schedule/agenda, so if you have any ideas/comments on that agenda or

[openstack-dev] [Neutron][Dragonflow] - Austin Design Summit

Hello everyone, We have started writing an agenda for our design summit sessions, please feel free to raise ideas/comments/questions in the following etherpad: https://etherpad.openstack.org/p/dragonflow-design-summit If you are a user/operator and would like to raise questions regarding our

[openstack-dev] [Openstack-operators] - Containers Sessions in Austin Ops@Summit

Hello all, We are going to have two sessions in the ops summit about containers deployment with OpenStack. (Monday, probably going to be 4:40-6:10) In order to make these sessions useful i think the most important topic that i want to tackle is feedback from operators running OpenStack and

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

we can > choose from: > > · 11:00 – 11:40 > > · 11:50 – 12:30 > > · 3:10 – 3:50 > > > > Please let us know if some of the slots don’t work well with your schedule. > > > > Best regards, > > Hongbin > > > > *From:* Ga

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Anything you pick is fine with me, Kuryr fishbowl session is on Thursday 4:10 - 4:50, i personally think the Magnum integration is important enough and i dont mind using this time for the session as well. Either way i am also ok with the 11-11:40 and the 11:50-12:30 sessions or the 3:10-3:50 On

[openstack-dev] Gal Sagie candidacy for the TC

Hello All, I have been working on OpenStack for the past year, currently the PTL of two projects part of the big-tent: Dragonflow and Kuryr and contributing to OVN and to Neutron core. The past year is by no doubt the best year of my career, working with the community and doing so openly for

[openstack-dev] [Kuryr] - IRC Meeting canceled today

Hello all, Since there is a number of members that cant attend the IRC meeting today we will cancel it. Sorry for the late announcement. I have updated the agenda for the meeting, lets postpone the same agenda for the meeting next week. Thanks Gal.

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (3/28) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 3/28) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Kuryr] - Austin design summit sessions

Hello all, We have started this etherpad [1] in order to asses the number of sessions needed for Kuryr. We have received 5 work sessions and 1 fishbowl session. [2] Lets brainstorm and propose more ideas on the etherpad and start splitting the subjects to sessions with priorities. Anyone that

Re: [openstack-dev] [Kuryr] Clarification of expanded mission statement

Hi Russell, Thanks for starting this thread, i have been wanting to do so myself. First, to me Kuryr is much more then just providing a "libnetwork driver" or a "CNI driver" in the networking part. Kuryr goal (to me at least) is to simplify orchestration, management and performance and avoid

[openstack-dev] [Kuryr] PTL Candidacy for Gal Sagie

I would like to propose my candidacy for Kuryr PTL position. Kuryr has only recently joined OpenStack big-tent and i would like to receive the official trust of the community and continue serving as the PTL for a full release cycle. I think that Kuryr serve an important role in current OpenStack

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (3/14) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 3/14) at 0900 UTC in #openstack-meeting-4 I personally will not be able to attend, Eran Gampel will chair it instead. Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last

[openstack-dev] [Kuryr] IRC Meeting tomorrow (3/14) - 1500 UTC

Hello All We will have an IRC meeting tomorrow (3/14) at 1500UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [Kuryr] IRC Meeting Tuesday (3/8) - 0300 UTC

Hello All We will have an IRC meeting in Tuesday (3/8) at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (3/7) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 3/7) at 0900 UTC in #openstack-meeting-4 I personally will not be able to attend, Eran Gampel will chair it instead. Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (2/29) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 2/29) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Kuryr] IRC Meeting tomorrow (2/29) - 1500 UTC

Hello All We will have an IRC meeting tomorrow (Monday, 2/29) at 1500 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hi Swami, Any luck on this? we plan to share our results soon and want to see we cover all cases and tests results are good On Fri, Feb 19, 2016 at 7:49 PM, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote: > Hi Gal Sagie, > > Let me try to p

[openstack-dev] [Kuryr] Now part of OpenStack big-tent

Hello Everyone, Just wanted to update you that Kuryr [1] was officially accepted yesterday as a big tent project. We are currently facing some interesting challenges and times and if you are running containers in OpenStack in mixed environments you most certainly want to look and examine Kuryr.

Re: [openstack-dev] [dragonflow] db consistency progress

Hi Li Ma, Great job on this! I think Rally is the correct way to test something like that, what you could use to check the end to end solution is try to restart the DF DB server for timeouts during API configurations. At this point of time, i think this is really advance testing and i wouldn't

Re: [openstack-dev] [Kuryr] will we use os-vif in kuryr

Yes, the intention from the start was to see if we can converge and use os-vif and i certainly see us using it. On Thu, Feb 18, 2016 at 12:32 PM, Daniel P. Berrange wrote: > On Thu, Feb 18, 2016 at 09:01:35AM +, Liping Mao (limao) wrote: > > Hi Kuryr team, > > > > I

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (2/22) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 2/22) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

I think setting these limits is wrong, some companies have more overall representation then others. The core reviewer job should be on a personal basis and not on a company basis, i think the PTL of each project needs to make sure the diversity and the community voice is heard in each project and

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

it will give us at least an estimation where we are at) Thanks Gal. On Thu, Feb 18, 2016 at 9:34 PM, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote: > Hi Gal Sagie, > > Yes there was some performance results on DVR that we shared with the >

[openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hello All, We have started to test Dragonflow [1] data plane L3 performance and was wondering if there is any results and scenarios published for the current Neutron DVR that we can compare and learn the scenarios to test. We mostly want to validate and understand if our results are accurate and

[openstack-dev] [Kuryr] - IRC Meeting (2/23) - 0300 UTC (#openstack-meeting-4)

Hello All, We will have an IRC meeting on 2/23 at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [Kuryr] IRC Meeting today (2/15) - 1500 UTC

Hello All We will have an IRC meeting today (Monday, 2/15) at 1500 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [Neutron][Dragonflow] IRC Meeting today (2/15) - 0900 UTC

Hello All, We will have an IRC meeting today (Monday, 2/15) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

Re: [openstack-dev] [Neutron] Distributed Multicast and IGMP Support in Dragonflow

This is a work we are doing in Dragonflow and is relatively simple to implement leveraging Dragonflow current infrastructure and reactive local controller. This will significantly reduce duplicating packets for IGMP aware VMs. and hence reduce multicast load. We would love to help and bring this

[openstack-dev] [Kuryr] IRC Meeting tomorrow (2/8) - 0300 UTC

Hello All, We will have an IRC meeting tomorrow (Tuesday, 2/8) at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meeting s/Kuryr You can view last meeting action items and logs

Re: [openstack-dev] [Kuryr] IRC Meeting tomorrow (2/9) - 0300 UTC

As Mike spotted, the date for the meeting is February 9!! and not the 8th in the original email Thanks for the correction! On Mon, Feb 8, 2016 at 5:44 PM, Gal Sagie <gal.sa...@gmail.com> wrote: > Hello All, > > We will have an IRC meeting tomorrow (Tuesday, 2/8) at 0300 UTC

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

If you compare the number of people that come to mid-cycles with the number of people that come to the summit and attend the design summit, i am sure (without knowing exact numbers) that there is a big difference in favor of the design summit. I also think that its important that users/operators

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting Canceled (2/8)

Hello all, Since many members (and also myself) cant make it for tomorrows meeting, we have decided to cancel it. For any urgent matters, feel free to send your question to the mailing list. We will have a meeting next week (2/15) as usual. Thanks Gal

Re: [openstack-dev] [Neutron] Evolving the stadium concept

ng related projects "near" the group of people that has the best context to review / help and comment, its obviously not working and thats fine, lets try something different... On Thu, Feb 4, 2016 at 8:18 PM, Armando M. <arma...@gmail.com> wrote: > > > On 4 Februa

Re: [openstack-dev] [Neutron] Evolving the stadium concept

. On Thu, Feb 4, 2016 at 11:31 AM, Assaf Muller <amul...@redhat.com> wrote: > On Thu, Feb 4, 2016 at 10:20 AM, Assaf Muller <amul...@redhat.com> wrote: > > On Thu, Feb 4, 2016 at 8:33 AM, Gal Sagie <gal.sa...@gmail.com> wrote: > >> As i have commented on the patch

Re: [openstack-dev] [Neutron] Evolving the stadium concept

As i have commented on the patch i will also send this to the mailing list: I really dont see why Dragonflow is not part of this list, given the criteria you listed. Dragonflow is fully developed under Neutron/OpenStack, no other repositories. It is fully Open source and already have a community

Re: [openstack-dev] [Neutron] Integrating physical appliance into virtual infrastructure

There is a project that aims at solving your use cases (at least from a general view) Its called L2GW and uses OVSDB Hardware VTEP schema (which is supported by many physical appliances for switching capabilities) Some information: https://wiki.openstack.org/wiki/Neutron/L2-GW There are also

[openstack-dev] [Kuryr] IRC Meeting - Monday (2/1) 1500 UTC (#openstack-meeting-4)

Hello All, We are going to have an IRC Meeting tomorrow (2/1) at 1500 UTC in #openstack-meeting-4 The meeting agenda can be seen here [1]. We are going to focus most of the meeting on the Kubernetes-Kuryr integration. You can view the logs from our specific Kuryr-Kubernetes integration IRC

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tommorrow (1/2) - 0900 UTC (#openstack-meeting-4)

Hello All, We will have an IRC meeting tomorrow (Monday, 1/2) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow We are going to have a busy meeting, many new specs/design, i have put the links to all specs in

Re: [openstack-dev] [Kuryr] IRC Meeting - Tuesday (1/26) 0300 UTC (#openstack-meeting-4)

ty are switched. > > Can it be that the calendar has to be updated, or it is because I am > completely > unable to deal with organization tools? > > Regards, > > > [1]: http://eavesdrop.openstack.org/calendars/kuryr-team-meeting.ics > > On Mon, 25 Jan 2016 13:51, Gal Sagie wrote: &

Re: [openstack-dev] [kuryr] Does Kuryr support multi-tenant

Hi Liping Mao, The question is what you mean by multi-tenancy, if you mean that different tenants each control their own bare-metal server then Kuryr already support this. (by tenant credential configuration) If what i think you mean, and thats running multi tenants on the same bare-metal then

[openstack-dev] [Kuryr] IRC Meeting - Tuesday (1/26) 0300 UTC (#openstack-meeting-4)

Hello All, We are going to have an IRC meeting tomorrow. I have updated the agenda for the upcoming meeting [1] Please review and add any additional topics you might want to cover. Last meeting action items can be seen here [2] Thanks and see you there! [1]

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (25/1) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 25/4) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Neutron][Dragonflow] - Status Update and Meetups in China

Hello Everyone, We are just back from a week in China where we met with various local community members to discuss about Dragonflow roadmap and design. We will have a nice number of people from different companies joining us on the development of Dragonflow and some are planning to deploy it. We

Re: [openstack-dev] [neutron] BGP Dynamic Routing Development Going Forward

The real question that needs to be asked (at least for me) is how this feature can work with other plugins/ML2 drivers that are not the reference implementation. How hard (possible) it is to take the API part (or maybe even the agent) and use that in another Neutron implementation. Then focus on

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting Cancelled (1/11)

Hello All, Just wanted to let everyone know that we wont have a Dragonflow IRC meeting next week (Monday, 1/11) We will continue with the meetings the week after (1/18) Thanks Gal. __ OpenStack Development Mailing List (not

[openstack-dev] [Kuryr] IRC Meeting - Monday (1/4) 1500 UTC (#openstack-meeting-4)

Hello All, The first Kuryr IRC meeting of this year is going to take place tomorrow :) I have updated the agenda for the upcoming meeting [1] Please review and add any additional topics you might want to cover. Last meeting action items can be seen here [2] See you there! [1]

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (1/4) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 1/4) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Neutron][Dragonflow] Security Groups Design for Scale

Hello all, We are iterating on a design document for Security Groups implementation in Dragonflow. [1] This design leverage the fact that Dragonflow distribute policy level abstraction to the local controllers and has Security Group as a first class citizen. The design tries to tackle the

Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

Hi Li Ma, I think its a good idea. I suggest for first stage, pass the CONF as optional parameter in addition to the db_ip and db_port. This way you will have minimum code changes at first patch. If we see its working ok, we can later remove db_ip and db_port and adjust the other drivers in

Re: [openstack-dev] [Neutron] [Dragonflow] Atomic update doesn't work with etcd-driver

Hi Li Ma, I haven't investigated the root problem yet as i seen it at the end of day yesterday. However if you look at this test : https://review.openstack.org/#/c/261997/ it verify that the correct number of flows are installed after a clean devstack process. What i noticed with this patch is

[openstack-dev] [Kuryr] Progress Update and Kubernetes Integration

Hello everyone, Just wanted to give you all some progress update at what we have been doing in Kuryr, We conducted an IRC meeting today, you can see the logs here [1] 1) We got Docker pluggable IPAM support in Kuryr thanks to Vikas Choudhary, there are still some small points to address but

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting today (12/28) - 0900 UTC

Hello All, We will have an IRC meeting today (Monday, 12/28) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

Re: [openstack-dev] [Neutron] [Dragonflow] Support configuration of DB clusters

Hi Li Ma, This approach makes sense to me, i was also thinking about the ability for the user to specify additional arguments and parameters to the DB driver. Feel free to register a bug and work on that. Thanks Gal. On Fri, Dec 25, 2015 at 1:07 PM, Li Ma wrote: > Hi

[openstack-dev] [Kuryr] IRC Meeting - Monday 1500 UTC (#openstack-meeting-4)

Hello All, I have updated the agenda for the upcoming Kuryr IRC meeting [1] Please review and add any additional topics you might want to cover. Last meeting action items can be seen here [2] I personally wont be able to attend the meeting and we expect low participant volume due to holidays

Re: [openstack-dev] [OpenStack-dev][Neutron] Is there a tool of generating network topology?

Depends what you mean "Network topology" , Horizon UI has virtual network topology graph/diagram. If you mean the physical topology, thats a bit harder but i remember there was a talk proposal for the previous summit on that area (i think garyk (CCed) was one of the proposed talkers so maybe he

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting tomorrow (12/21) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 12/21) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Magnum][Kuryr] Help with using docker-python client in gate

Hello Everyone, We are trying to add some gate testing for Kuryr and hopefully convert these also to Rally plugins. What i am facing in the gate right now is this: I configure the docker client: self.docker_client = docker.Client( base_url='unix://var/run/docker.sock') And call this:

[openstack-dev] [Neutron][Dragonflow] - IRC Meeting tomorrow (12/14) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 12/14) at 0900 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last meeting action items and logs here:

[openstack-dev] [Kuryr] IRC Meeting - Tuesday 0300 UTC (12/15)

Hello All, I have updated the agenda for the upcoming Kuryr IRC meeting [1] Please review and add any additional topics you might want to cover. Also please go over last meeting action items [2] , there are still patches (IPAM) that are looking for review love :) Since this is the week we do

[openstack-dev] [Neutron][Dragonflow] - Documentation

Hello All, We have recently uploaded a big amount of documents and diagrams to Dragonflow repository in order to expose what we are doing and make it as simple as we can for new contributors and users to start using Dragonflow. I have created a wiki page for Dragonflow [1]. Some recommended

[openstack-dev] [openstack-infra] Using Neutron client in the gate

Hello All, I would like to run some "fullstack" integration tests for Kuryr and run them in the gate. For the tests i would like to use the Neutron client for communicating with the working devstack Neutron service. What is the best way to instantiate the client in terms of auth_url and

[openstack-dev] [Kuryr] Testing, Rally and Wiki

Hello everyone, As some of you have already noticed one of the top priorities for Kuryr this cycle is to get our CI and gate testing done. I have been working on creating the base for adding integration tests that will run in the gate in addition to our unit tests and functional testing. If you

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

ntext plugin and client and other parts that are >> probably needed by other projects (like Magnum) >> I think it would be great if we can combine forces on this. > > > What this context is going to do? > > > Best regards, > Boris Pavlovic > > On Thu, De

[openstack-dev] [openstack-infra] Functional tests in the gate

Hello all, I want to write functional tests that will run in the gate but only after a devstack environment has finished. Basically i want to interact with a working enviorment, but i don't want the tests that i write to fail the python27 gate tests. (I guess like the Neutron full stack tests,

Re: [openstack-dev] [openstack-infra] Functional tests in the gate

VSTACK_GATE_TEMPEST=1 > export DEVSTACK_GATE_TEMPEST_NOTESTS=1 > first line tells to install tempest > and second tells that job should not run it > > and then 'post_test_hook' defines commands to run. > > On Sun, Dec 6, 2015 at 7:06 PM, Gal Sagie <gal.sa...@gmail.com&

Re: [openstack-dev] [Neutron] Evolving the stadium concept

To me, and i could got it wrong, the stadium means two main things: (At this point in time) 1) Remove/ease the burden of OpenStack governance and extra job for projects/drivers that implement Neutron and are "relatively small" This saves the projects that just want to implement Neutron to be

Re: [openstack-dev] [Neutron] Security Groups OVS conntrack support

Hi Fawad, >From what i could understand from Miguel Angel Ajo, someone is working on this integration and it is suppose to be delivered as part of Mitaka. I don't remember the person name, Miguel will sure update shortly. Gal. On Sun, Nov 22, 2015 at 7:05 PM, Fawad Khaliq

Re: [openstack-dev] [kuryr] mutihost networking with nova vm as docker host

The current OVS binding proposals are not for nested containers. I am not sure if you are asking about that case or about the nested containers inside a VM case. For the nested containers, we will use Neutron solutions that support this kind of configuration, for example if you look at OVN you

Re: [openstack-dev] [networking-onos]: Proposing new cores for networking-onos

+1 for both from me On Thu, Nov 5, 2015 at 2:53 PM, Vikram Choudhary wrote: > Hi All, > > I would like to propose Mr. Ramanjaneya Reddy Palleti and Mr. Dongfeng as > new cores for networking-onos project. Their contribution was significant > in the last Liberty cycle w.r.t to

[openstack-dev] [Neutron][Kuryr] - Design Summit etherpad

Hello All, It was great meeting everyone in the summit, it ended too fast.. We had a free design talk on Friday about Kuryr. (Thanks to everyone that participated) We have created this etherpad with all the related tasks: https://etherpad.openstack.org/p/mitaka-neutron-unplugged-track-kuryr If

Re: [openstack-dev] [neutron][networking-sfc] API clarification questions

Hi Pino, Just one note on the order of the pipeline, shouldnt the security part be before the service chaining (and also after)? (Unless you only meant egress security and you still do the ingress before) Gal. On Wed, Oct 28, 2015 at 10:14 AM, Giuseppe (Pino) de Candia < gdecan...@midokura.com>

[openstack-dev] [Neutron][Kuryr] IRC Meeting - Canceled for next week (10/26)

Hello Everyone, Just wanted to share with anyone that wasn't in the meeting this week, that we decided to cancel the IRC meeting on the 10/26. See you all in the summit. Gal. __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 7:37 PM, Armando M. <arma...@gmail.com> wrote: > > > On 21 October 2015 at 04:12, Gal Sagie <gal.sa...@gmail.com> wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > [Gal] Because

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

Do we also want to consider Project Kuryr part of this? We already started sending Kuryr spec to the Neutron repository and I think it would make sense to manage it as part of Neutron spec process. Any opinions on that? Gal. On Tue, Oct 20, 2015 at 11:10 PM, Armando M.

[openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

Hello All, In OpenStack Tokyo summit we will have a design summit session for containers networking and containers orchestration engines integration with Neutron [1]. Please feel free to edit the session etherpad [2] with relevant topics, if you are working and have any gaps or needs from

Re: [openstack-dev] [neutron][networking-ovn][l3] Add/delete router interface

plugin. This patch was initially worked on by > Gal Sagie (*https://review.openstack.org/#/c/206919/* > <https://review.openstack.org/#/c/206919/>) and we took over > to take it completion. > > There are bunch of gate tests that are failing as a result of this > patch an

Re: [openstack-dev] [kuryr] Proposing Taku Fukushima as Kuryr core

+1 Taku is a great addition to the team and hoping to see him continue deliver high quality contribution in all aspects of the project. On Tue, Oct 13, 2015 at 4:52 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > Hi fellow Kurýrs, > > I would like to propose Taku Fukushima

[openstack-dev] [Neutron][Kuryr] - IRC Meetings

Hello Everyone, Our current IRC meeting time is 15:00 UTC every Monday. I have received several requests from US people saying its hard for them to attend at this early time. We want to allow anyone that shows interest in the project to join, so we discussed this in yesterday's IRC meeting and

  1   2   >