On Thu, Jun 7, 2018 at 3:52 AM, Peng Liu wrote:
> Cool.
> I'll start to prepare a BP for this, so we can have more detailed
> discussion.
Great!
>
> On Wed, Jun 6, 2018 at 11:08 PM, Antoni Segura Puimedon
> wrote:
>>
>> On Wed, Jun 6, 2018 at 2:37 PM, Iren
On Wed, Jun 6, 2018 at 2:37 PM, Irena Berezovsky wrote:
> Sounds like a great initiative.
>
> Lets follow up on the proposal by the kuryr-kubernetes blueprint.
I fully subscribe what Irena said. Let's get on this quick!
>
> BR,
> Irena
>
> On Wed, Jun 6, 2018 at 6:47 AM, Peng Liu wrote:
>>
>> H
On Mon, Jan 22, 2018 at 3:46 PM, Daniel Mellado
wrote:
> +1
>
>
> El 21/1/18 a las 8:13, Irena Berezovsky escribió:
>
> +1
>
> On Fri, Jan 19, 2018 at 9:42 PM, Hongbin Lu wrote:
>>
>> Hi Kuryr team,
>>
>> I think Kuryr-libnetwork is ready to move out of beta status. I propose to
>> make the first
Hi fellow kuryrs,
Due to illness of one of the key contributors in todays sessions,
we'll postpone the sessions today. As soon as he recovers we'll
publish the new time.
Regards,
Toni
__
OpenStack Development Mailing List (
).
>
> Sorry for the noise!
>
> Daniel
>
> On 10/02/2017 03:30 AM, Hongbin Lu wrote:
>> Hi Toni,
>>
>> The time of a few proposed sessions look inconsistent with the etherpad.
>> Could you double check?
>>
>> On Thu, Sep 28, 2017 at 5:48 AM, Antoni
with the etherpad.
> Could you double check?
>
> On Thu, Sep 28, 2017 at 5:48 AM, Antoni Segura Puimedon
> wrote:
>>
>> Hi fellow Kuryrs!
>>
>> It's that time of the cycle again where we hold our virtual project team
>> gathering[0]. The dates this tim
Hi fellow Kuryrs!
It's that time of the cycle again where we hold our virtual project team
gathering[0]. The dates this time are:
October 2nd, 3rd and 4th
The proposed sessions are:
October 2nd 13:00utc: Scale discussion
In this session we'll talk about the recent scale testing we have perf
HI Kuryrs!
Since most of the people are on PTO today, we'll skip the weekly IRC
meeting and hold it next week. I don't have PTO, so if there's
anything you want to discuss, you are very welcome to come to
#openstack-kuryr
Regards,
Toni
___
Hi fellow kuryrs!
I present my PTL candidacy for the Queens Cycle.
We've done well in this past cycle getting close to our first release
adding things like:
- Kubernetes service support,
- Token authentication support,
- A lot of devstack improvements like multinode
- pod-in-VM neutron trunk and
On Tue, Jul 4, 2017 at 12:23 PM, Gal Sagie wrote:
> +1
+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 su
Hi Kuryrs,
Today Irena and I are attending the OpenStack Israel day and won't be
able to chair the meeting. We can catch up tomorrow on IRC during the
day.
Toni
__
OpenStack Development Mailing List (not for usage questions)
Hi Kuryrs!
Most of you have holidays on May 1st, so due to that, we'll adjourn
the weekly IRC meeting.
The following one is in the summit week. I'll check if I don't have a
talk at the same time as the meeting. If I do. I'll have to cancel as
well.
Regards,
Toni
Hi Kuryrs,
Tomorrow there's going to be a meeting to discuss Ilya's proposal for
a refactor of Kuryr controller entities based on the actor model. The
meeting will be held at:
https://bluejeans.com/826701641
12:00 UTC
I'll post the recording probably the day after.
See you there,
Toni
__
Hi Kuryrs,
I'm on PTO on the mountains with limited connectivity, hence I won't
be able to make it to the weekly IRC meeting.
Regards and sorry for the short notice,
Toni
__
OpenStack Development Mailing List (not for usage
On Friday, March 24, 2017 at 3:59:18 PM UTC+1, Graham Hayes wrote:
>
> On 24/03/17 10:27 -0400, Davanum Srinivas wrote:
> >Folks,
> >
> >As discussed in the etherpad:
> >https://etherpad.openstack.org/p/go-and-containers
> >
> >Here's a request for a repo in OpenStack:
> >https://review.op
Hi Kuryrs!
Thanks a lot for the hard work in last week's VTG sessions. We created
quite a few Action items and tomorrow will be the time to sort them:
https://trello.com/b/1Ij919E8
I'll try to eventually move it to storyboard, but we need to get some
stuff created.
The session will be held as v
Hi Kuryrs,
Thank you all for participating in the VTG. Here you can find the last
two recordings:
https://youtu.be/ti4oOK6p_Dw
https://youtu.be/iEdOTngEw4I
Let's discuss the priority of all the action items next week!
Toni
__
Hi Kuryrs!
Thanks again for joining the Virtual team Gathering sessions. Here you
have the links to the recordings:
https://youtu.be/o1RKNOAhqho
https://youtu.be/ovbK5kk5AZ0
See you today on the last day of this first VTG!
Toni
_
Hi Kuryrs!
Thank you all for joining yesterday. For those unable to make it, here
are the recordings for the sessions:
https://youtu.be/Hdn9LOnCrSc
https://youtu.be/6D5iGEkKtGc
See you at today's sessions!
Toni
__
OpenSta
Hello Kuryrs,
Due to preparations for this week's VTG, today's meeting is cancelled.
Looking forward to see you all tomorrow!
Toni
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
Hi all!
An impromptu conversation started between Omer and I about l4 and l7 load
balancers for serving Kubernetes workloads (both services and ingress
controllers) and we thought it would be nice to have more feedback on the
discussion, particularly from Octavia folks.
Omer kindly offered to hav
Hi Kuryrs!
The VTG sessions[0] will be held in bluejeans:
https://bluejeans.com/5508709975
You can also join by phone finding a local number in [1] and entering the
meeting id "5508709975" followed by a '#'.
The sessions will be
┌──┬─┐
On Fri, Feb 10, 2017 at 3:24 PM, Flavio Percoco wrote:
> On 09/02/17 09:57 +0100, Flavio Percoco wrote:
>
>> Greetings,
>>
>> I was talking with Tony and he mentioned that he's recording a new demo
>> for
>> kuryr and, well, it'd be great to also use the containerized version of
>> TripleO
>> for
On Thu, Feb 9, 2017 at 10:00 PM, Dan Sneddon wrote:
> Pete, thanks for mentioning network isolation and segmentation. That's
> my area of interest, since I'm focused on underlay networking for
> TripleO and bare-metal networking in Ironic.
>
> Network isolation is going to be important for severa
On Thu, Feb 9, 2017 at 7:48 AM, Antoni Segura Puimedon
wrote:
>
>
> On Tue, Feb 7, 2017 at 5:30 PM, Antoni Segura Puimedon > wrote:
>
>> Hi all,
>>
>> In the last weekly IRC meeting it was agreed to hold a videoconf meeting
>> about resource management
On Tue, Feb 7, 2017 at 5:30 PM, Antoni Segura Puimedon
wrote:
> Hi all,
>
> In the last weekly IRC meeting it was agreed to hold a videoconf meeting
> about resource management. For those unaware, the topic revolves around the
> reutilization of Neutron resources like ports and s
Hi all,
In the last weekly IRC meeting it was agreed to hold a videoconf meeting
about resource management. For those unaware, the topic revolves around the
reutilization of Neutron resources like ports and subports as well and
virtual devices like veths. This allows for things like batching neutr
On Thu, Jan 26, 2017 at 12:41 PM, Davanum Srinivas
wrote:
> Team,
>
> A bit of history, we had a client generated from swagger definition for a
> while in Magnum, we plucked it out into python-k8sclient which then got
> used by fuel-ccp, kuryr etc. Recently the kuberneted team started an effort
>
Hi Kuryrs!
I am putting forward my candidacy[1] for a second term as the PTL. It is
great to work with all of you every day to make kuryr deliver on its
mission.
Over this current cycle, we've managed to rebuild the team after we had
some core departures and I think we are in a very good place, w
Hi Kuryrs!
Due to traveling restrictions, we opted not to take part in the Atlanta
PTG. However, the design work sessions won't disappear :-)
Please go through its etherpad[0] and propose, vote, comment about
sessions, format and scheduling.
Regards,
Toni
[0] https://etherpad.openstack.org/p/k
e:
>
>> +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
Hi fellow kuryrs!
We are getting close to the end of the Ocata and it is time to look back
and appreciate the good work all the contributors did. I would like to
thank you all for the continued dedication and participation in gerrit, the
weekly meetings, answering queries on IRC, etc.
I also want
On Mon, Dec 12, 2016 at 6:49 PM, Antoni Segura Puimedon
wrote:
> Hi fellow kuryrs!
>
> December 14th at 11:00 UTC we'll be having a video meeting [1] to sync
> about the current Kubernetes integration.
>
We're moving the meeting to bluejeans [3] so that we can have a
Hi fellow kuryrs!
December 14th at 11:00 UTC we'll be having a video meeting [1] to sync
about the current Kubernetes integration. There is an etherpad for the
topics that we'll be covering [2]. Feel free to add topics and +1 the
topics that you want to have discussion on.
The objective of the me
On Tue, Dec 6, 2016 at 9:10 AM, Mikhail Fedosin wrote:
> Hi folks!
>
Hi Mikhail!
>
> We at Samsung are trying to integrate containers in OpenStack and at this
> moment we are looking at Kubernetes deployed by Magnum, which works good
> enough for now.
>
> One challenge we have faced recently i
On Thu, Nov 3, 2016 at 4:29 AM, Vikas Choudhary
wrote:
>
>
> On Thu, Nov 3, 2016 at 12:33 AM, Antoni Segura Puimedon
> wrote:
>>
>> Hi magna and kuryrs!
>>
>> Thank you all for joining last week meetings. I am now writing a few
>> emails to have per
Hi magna and kuryrs!
Thank you all for joining last week meetings. I am now writing a few
emails to have persistent notes of what was talked about and discussed
in the Kuryr work sessions. In the Magnum joint session the points
were:
Kuryr - Magnum joint work session
=
On Wed, Sep 21, 2016 at 11:53 AM, Daly, Louise M
wrote:
> Hi everyone,
>
>
>
> As promised here is a link to the code PoC for the Kuryr-IPVlan proposal.
>
> https://github.com/lmdaly/kuryr-libnetwork
>
>
>
> Link to specific commit
>
> https://github.com/lmdaly/kuryr-libnetwork/commit/1dc895a6d8bf
Hi,
We recently made the first release (0.1.0) of kuryr-lib on which no
project depends except openstack/kuryr-libnetwork. Now, kuryr-lib by
itself is not more than a base library and its release is only to
serve kuryr-libnetwork and kuryr-kubernetes.
Now we are in the process of releasing kuryr-
Hi Kuryrs!
Yet again I'm late in posting the agenda, sorry. Here goes today's meeting
agenda[1]. As always, feel free to add items or bring them up during the
open discussion, I'll be checking the agenda for updates just before
the meeting starts at 14utc.
See you in the meeting,
Toni
[1]
http
On Mon, Sep 12, 2016 at 7:04 PM, Steven Dake (stdake) wrote:
> To the OpenStack Community,
>
>
>
> Consider this email my self non-nomination for PTL of Kolla for
>
> the coming Ocata release. I let the team know in our IRC team meeting
>
> several months ago I was passing the on baton at the con
On Tue, Sep 13, 2016 at 5:05 PM, Hongbin Lu wrote:
>
>
> On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary
> wrote:
>>
>>
>>
>> On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote:
>>>
>>> Ivan,
>>>
>>> Thanks for the proposal. From Magnum's point of view, this proposal
>>> doesn't seem to require
On Mon, Sep 12, 2016 at 1:42 PM, Antoni Segura Puimedon
wrote:
> On Mon, Sep 12, 2016 at 1:29 PM, Coughlan, Ivan
> wrote:
>>
>>
>> Overview
>>
>> Kuryr proposes to address the issues of double encapsulation and exposure of
>> containers as neutron entit
in-VM support.
- Participate more in upstream container orchestration engine communities.
I look forward to work with all of you to make Kuryr into the things
all of us want and need from it.
[1] https://review.openstack.org/#/c/368825/
Antoni Segura Pui
On Mon, Sep 12, 2016 at 1:29 PM, Coughlan, Ivan wrote:
>
>
> Overview
>
> Kuryr proposes to address the issues of double encapsulation and exposure of
> containers as neutron entities when containers are running within VMs.
>
> As an alternative to the vlan-aware-vms and use of ovs within the VM,
Hi Kuryrs!
On September 5th's weekly IRC meeting Irena Berezovsky suggested that
we should take a decision regarding the location of specs and devrefs.
Currently we default to putting all the specs and devrefs for:
- Kuryr
- Kuryr-libnetwork
- Kuryr-kubernetes
to openstack/kuryr. Fuxi is still b
Hi Kuryrs!
Sorry I didn't get to post it earlier, here goes today's meeting
agenda. As always, feel free to add items or bring them up during the
open discussion, I'll be checking the agenda for updates just before
the meeting starts at 14utc.
See you in the meeting,
Toni
__
On Mon, Sep 12, 2016 at 10:31 AM, Gal Sagie wrote:
> 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 communit
Hi Kuryrs!
Yesterday in the meeting we discussed about the need to design a way for the
functional testing to happen for the Kuryr-Kubernetes integration. I studied
the possibilities today and came up with the following proposal (After the
proposal I'll put more detailed explanations).
Prerequisi
Hi Kuryrs,
Last Thursday, we had a very productive Kuryr-Kubernetes integration
meeting. I want to thank a lot to all the people that joined the meeting
for how well they prepared the meeting and the good points that were raise.
We used some slides to guide the meeting points[1]. The key takeaway
Hi Kuryrs,
Sorry I didn't get to post this on Fridays due to traveling. Here you can
find the weekly IRC meeting agenda for today:
https://wiki.openstack.org/wiki/Meetings/Kuryr#Meeting_September_5th.2C_2016
Remember! Today we meet at the regular 14:00 UTC!
Antoni Segura Pui
e nice if the community would have a
recommendation for OSt upstream and it's downstreams.
>
>
> Regards,
>
> Jaume Devesa
> Software Engineer @ Midokura
>
> On Aug 30 2016, at 4:44 pm, Antoni Segura Puimedon
> wrote:
>
>> Hi fe
erybody is welcome to add items to it (Though if there are too many
some may get pushed a week).
Have fun coding and reviewing!
Antoni Segura Puimedon
PS: There is a nice .ics that you can use to add the meetings to your
calendar[3]
[1] https://review.openstack.org/362852
[2] https://wiki.ope
Hi fellow kuryrs!
This email is gonna be a bit long, so I'll put it in parts.
Kubernetes integration components
==
As you know, we are now in the process of upstreaming the Kuryr Kubernetes
PoC that the Kuryr team at Midokura did. This PoC upstreaming effort has
two main
ally, I could see a nice clean separation with the former, but I have
to say that at the current stage, after all the friction we got from the
repository split, the best option in my mind is to go with the latter
option.
[1] https://review.openstack.org/#/c/3
team for the kuryr-kubernetes
subproject since he has experience in the day to day work with kubernetes
and can help with the review and refactoring of the prototype upstreaming.
Regards,
Antoni Segura Puimedon
__
OpenStack
On Tue, Aug 16, 2016 at 2:56 PM, Steven Dake (stdake)
wrote:
> Hey kuryrians,
>
> Kolla has a kuryr review in our queue and its looking really solid from
> Hui Kang. The last key problem blocking the merge (and support of Kuryr in
> Kolla) is that Kolla only supports keystone v3 (and later when
On Tue, Aug 16, 2016 at 6:29 AM, Liping Mao (limao) wrote:
> Hi Kuryr team,
>
> I just notice, this can be fixed in kuryr bind code.
> I submit a bug to track this:
> https://bugs.launchpad.net/kuryr-libnetwork/+bug/1613528
>
> And patch sets are here:
> https://review.openstack.org/#/c/355712/
>
On Wed, Aug 3, 2016 at 11:00 PM, Heidi Joy Tretheway wrote:
> *Steve Hardy wrote:*
> *"I have one question regarding the review process for the logos when
> they are drafted? In the cases where projects have their existing community
> generated logos I can imagine there will be a preference to st
On Tue, Jul 26, 2016 at 12:53 PM, Vikas Choudhary <
choudharyvika...@gmail.com> wrote:
> +1
> On 26 Jul 2016 15:45, "Liping Mao (limao)" wrote:
>
>> Hi Team,
>>
>> Currently, kuryr team meeting time is as following:
>>
>> Every two weeks (on even weeks) on Tuesday at 0300 UTC in
>> #openstack-mee
On Mon, Jul 4, 2016 at 11:59 AM, Julien Danjou wrote:
> On Mon, Jul 04 2016, Antoni Segura Puimedon wrote:
>
> > for the neutron clients now we use a thread executor from the asyncio
> loop
> > any time
> > we do neutron client request.
>
> It's a good trade
On Mon, Jul 4, 2016 at 11:16 AM, Julien Danjou wrote:
> On Sun, Jun 26 2016, Denis Makogon wrote:
>
> > I know that some work in progress to bring Python 3.4 compatibility to
> > backend services and it is kinda hard question to answer, but i'd like to
> > know if there are any plans to support a
On Fri, Jul 1, 2016 at 7:58 PM, Doug Hellmann wrote:
> Excerpts from Jeremy Stanley's message of 2016-07-01 15:05:30 +:
> > On 2016-07-01 08:26:13 -0500 (-0500), Monty Taylor wrote:
> > [...]
> > > Check with Doug Hellman about namespaces. We used to use them in some
> > > oslo things and had
On Fri, Jul 1, 2016 at 3:26 PM, Monty Taylor wrote:
> On 07/01/2016 08:10 AM, Antoni Segura Puimedon wrote:
> > Hi fellow kuryrs!
> >
> > In order to proceed with the split of kuryr into a main lib and it's
> kuryr
> > libnetwork component, we've cloned t
On Fri, Jul 1, 2016 at 3:10 PM, Antoni Segura Puimedon <
toni+openstac...@midokura.com> wrote:
> Hi fellow kuryrs!
>
> In order to proceed with the split of kuryr into a main lib and it's kuryr
> libnetwork component, we've cloned the contents of openstack/kur
Hi fellow kuryrs!
In order to proceed with the split of kuryr into a main lib and it's kuryr
libnetwork component, we've cloned the contents of openstack/kuryr over to
openstack/kuryr-libnetwork.
The idea is that after this, the patches that will go to openstack/kuryr
will be to trim out the kury
On Tue, Jun 28, 2016 at 11:54 AM, Vikas Choudhary <
choudharyvika...@gmail.com> wrote:
>
>
> On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segura Puimedon <
> toni+openstac...@midokura.com> wrote:
>
>>
>>
>> On Mon, Jun 27, 2016 at 11:10 AM, Vikas Cho
_driver
>>> │common (traffic tagging utilities and binding)
>>> │
>>> │kubernetes(cni)
>>> │
>>> │libnetwork(network and ipam driver)(for network related
>>> services making api calls)
>>> │
>&g
On Mon, Jun 13, 2016 at 12:10 AM, Hongbin Lu wrote:
> Hi team,
>
>
>
> During the team meetings these weeks, we collaborated the initial project
> roadmap. I summarized it as below. Please review.
>
>
>
> * Implement a common container abstraction for different container
> runtimes. The initial i
On Sun, Jun 12, 2016 at 9:39 PM, Mike Spreitzer wrote:
> Antoni Segura Puimedon wrote on
> 06/11/2016 07:39:41 PM:
>
> > Well, with a label you can make the Neutron Port have an SG that
> > forbids pinging.
>
> Wait, what? Labels on what can do what?
There are
On Fri, Jun 10, 2016 at 6:45 PM, Bilal Baqar wrote:
> Hey James
>
> No problem on my side for this change.
>
> Regards
>
> On Fri, Jun 10, 2016 at 3:25 PM, Neil Jerram wrote:
>
>> Me too.
>>
>> On Fri, Jun 10, 2016 at 10:32 AM Cory Benfield wrote:
>>
>>>
>>> > On 8 Jun 2016, at 11:20, James Pag
On Sat, Jun 11, 2016 at 3:03 PM, Mike Spreitzer wrote:
> What about pinging? BTW, from where would the pings come?
>
> In the Docker/Swarm API today there is no way to disable ping. However,
> once Kuryr's libnetwork plugin is updated so that `docker network connect
> --ip=W.X.Y.Z ...` will lat
On Fri, Jun 10, 2016 at 5:18 PM, Neil Jerram wrote:
> Yes, that all makes sense - thanks for explaining.
>
> Neil
>
>
> On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi wrote:
>
>> Hi Neil,
>>
>> Currently, when a docker libnetwork "join" operation in Kuryr is
>> returned, it is not guara
On Sat, Jun 4, 2016 at 5:17 AM, Liping Mao (limao) wrote:
> Hi Kuryr team,
>
> I notice kuryr did not detect neutron tag plugin in devstack[1].
> This is because when kuryr process start up in devstack,
> neutron-server did not finish load tag plugin.
> Kuryr use api call to detect neutron tag, s
On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary wrote:
> Hi All,
>
> Recently, Banix observed and brought into notice this issue [1].
>
> To solve this, i could think of two approaches:
> 1. Modifying the libnetwork apis to get PoolID also at network creation.
> OR
> 2. Enhancing the /netwo
On Wed, May 25, 2016 at 11:20 AM, Jaume Devesa wrote:
> Hello Akshay,
>
> responses inline:
>
> On Wed, 25 May 2016 10:48, Akshay Kumar Sanghai wrote:
> > Hi,
> > I have a 4 node openstack setup (1 controller, 1 network, 2 compute
> nodes).
> > I want to install kuryr in liberty version. I cannot
On Sat, May 14, 2016 at 7:13 PM, Clint Byrum wrote:
> Excerpts from Dieterly, Deklan's message of 2016-05-14 01:18:20 +:
> > Python 2.x will not be supported for much longer, and let¹s face it,
> > Python is easy, but it just does not scale. Nor does Python have the
> > performance characteri
On Thu, May 12, 2016 at 4:50 PM, Neil Jerram wrote:
> I'm trying Kuryr with networking-calico and think I've hit an unhelpful
> inconsistency. A Neutron port has 'id' and 'device_id' fields that are
> usually different. When Nova does VIF binding for a Neutron port, it
> generates the Linux devic
On Mon, May 2, 2016 at 8:11 PM, Mike Spreitzer wrote:
> I am looking at
> https://www.openstack.org/videos/video/project-kuryr-docker-delivered-kubernetes-next,
> around 28:00. You have said that overlay networks are involved, and are
> now talking about load balancers. Is this Neutron LBaaS?
On Thu, Apr 21, 2016 at 9:30 PM, Fox, Kevin M wrote:
> +1.
>
> From: Hongbin Lu [hongbin...@huawei.com]
> Sent: Thursday, April 21, 2016 7:50 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [magnum][app-c
On Fri, Mar 4, 2016 at 5:01 AM, Vikas Choudhary
wrote:
> Since libnetwork talks to cluster store independent of plugin, I think no
> changes are required on Kuryr side.
That's right. Docker handles all the KV storage interaction from the
data it receives from
Kuryr. In fact, it is expressly forbi
On Fri, Feb 26, 2016 at 10:44 AM, Miguel Angel Ajo Pelayo
wrote:
>
>> On 26 Feb 2016, at 02:38, Sean McGinnis wrote:
>>
>> On Thu, Feb 25, 2016 at 04:13:56PM +0800, Qiming Teng wrote:
>>> Hi, All,
>>>
>>> After reading through all the +1's and -1's, we realized how difficult
>>> it is to come up
On Wed, Feb 24, 2016 at 4:51 PM, Gal Sagie wrote:
> Hello Everyone,
>
> Just wanted to update you that Kuryr [1] was officially accepted yesterday
> as a
> big tent project.
We should probably get Kuryr to be selectable as a tag to subscribe to in
http://lists.openstack.org/cgi-bin/mailman/optio
On Tue, Feb 2, 2016 at 7:26 AM, Mars Ma wrote:
> hi Vikas,
>
> ubuntu@kuryr1:~$ docker network create --driver=kuryr --ipam-driver=kuryr
> --subnet 10.10.0.0/16 --gateway 10.10.0.1 --ip-range 10.10.0.0/24 foo
> 68f14fe701710d6f3472d1626c33f0036a145aaa8d81265429e509cf759adfe1
> ubuntu@kuryr1:~$ do
Jan 26, 2016 at 4:29 PM, Antoni Segura Puimedon
> wrote:
>>
>> On Tue, Jan 26, 2016 at 8:13 AM, Baohua Yang wrote:
>> > Hi hua
>> > Thanks for the suggestion!
>> > Yes, root wrap is also a good candidate.
>> > We will compare to choose the proper s
On Tue, Jan 26, 2016 at 8:13 AM, Baohua Yang wrote:
> Hi hua
> Thanks for the suggestion!
> Yes, root wrap is also a good candidate.
> We will compare to choose the proper solution.
> Thanks!
>
> On Tue, Jan 26, 2016 at 1:59 PM, 王华 wrote:
>>
>> Hi Baohua,
>>
>> I think https://wiki.openstack.org/
On Mon, Dec 14, 2015 at 6:07 PM, Jaume Devesa wrote:
> +1
>
> I think it is good compromise. Thanks Ryu!
>
> I understand the CLI will belong to the external part. I much prefer to
> have
> it in a separate project rather than into the plugin. Even if the code is
> tiny.
>
Let me summarize it:
On Wed, Dec 9, 2015 at 2:41 PM, Antoni Segura Puimedon <
toni+openstac...@midokura.com> wrote:
>
>
> On Tue, Dec 8, 2015 at 1:58 PM, Galo Navarro wrote:
>
>> Hi Sandro,
>>
>> >> 1) (Downstream) packaging: midonet and python-midonetclient are two
>>
On Tue, Dec 8, 2015 at 1:58 PM, Galo Navarro wrote:
> Hi Sandro,
>
> >> 1) (Downstream) packaging: midonet and python-midonetclient are two
> >> distinct packages, and therefore should have distinct upstream
> >> tarballs - which are compiled on a per repo basis.
>
> This is actually not accurate
On Tue, Dec 1, 2015 at 10:59 AM, Ivan Kelly wrote:
> +1 for #2
>
PS: Beware of the top-posting! It makes vote counting harder ;-)
>
> On Tue, Dec 1, 2015 at 10:57 AM, Sandro Mathys
> wrote:
> > Hi,
> >
> > Our IRC channels have been neglected for a long time, and as a result
> > we lost owner
On Mon, Nov 9, 2015 at 3:07 AM, Baohua Yang wrote:
> Hi, kuryr guys
> I may not attend tmr's IRC meeting, hence make a quick sync here.
> One task is to investigate the docker python lib support to libnetwork.
> I checked the code here at https://github.com/docker/docker-py.
> The
On Fri, Nov 6, 2015 at 1:20 PM, Baohua Yang wrote:
> It does cause confusing by calling container-inside-vm as nested
> container.
>
> The "nested" term in container area usually means
> container-inside-container.
>
I try to always put it as VM-nested container. But I probably slipped in
some m
On Thu, Nov 5, 2015 at 10:38 AM, Vikas Choudhary wrote:
> ++[Neutron] tag
>
>
> On Thu, Nov 5, 2015 at 11:33 AM, Vikas Choudhary <
> choudharyvika...@gmail.com> wrote:
>
>> Hi All,
>>
>> I would appreciate inputs on following queries:
>> 1. Are we assuming nova bm nodes to be docker host for now?
On Thu, Nov 5, 2015 at 10:47 AM, Vikas Choudhary wrote:
> ++ [Neutron] tag
>
>
> On Thu, Nov 5, 2015 at 10:40 AM, Vikas Choudhary <
> choudharyvika...@gmail.com> wrote:
>
>> Hi all,
>>
>> By network control plane i specifically mean here sharing network state
>> across docker daemons sitting on d
e meeting on Friday. Next Monday it will be
held as usual
and the following week we start alternating (we have yet to get a room for
that one).
>
> On Wed, Nov 4, 2015 at 9:27 PM, Antoni Segura Puimedon <
> toni+openstac...@midokura.com> wrote:
>
>> Hi Kuryrs,
>>
>>
Hi Kuryrs,
Last Friday, as part of the contributors meetup, we discussed also code
contribution etiquette. Like other OpenStack project (Magnum comes to
mind), the etiquette for what to do when there is disagreement in the way
to code a blueprint of fix a bug is as follows:
1.- Try to reach out s
Hi fellow Kuryrs,
I want to remind you that we'll be meeting up at some corner of [1] to
discuss all things kuryr. The agenda will be:
- Current challenges with multinode
- The path to Mitaka:
+ Functional testing
+ COE Integrations
+ VM nested containers.
[1] http://sched.co/4Qan
Regard
Hi fellow Kurýrs,
I would like to propose Taku Fukushima for the core Kuryr team due to his
unparalleled dedication to the project. He has written most of the code and
battled through the continuous libnetwork API changes. He will be a great
addition to the reviewing tasks.
Current core members,
r usage questions)" <
> openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>,
> Eran Gampel mailto:eran.gam...@huawei.com>>,
> Antoni Segura Puimedon mailto:t...@midokura.com>>,
> Irena Berezovsky mailto:ir...@midokura.com>>,
> Moham
On Fri, Sep 18, 2015 at 8:30 PM, Gal Sagie wrote:
> Hello everyone,
>
> We have a spec for project Kuryr in Neutron repository [1] , we have been
> iterating on it
> internally and with the great help and feedback from the Magnum team.
>
> I am glad to say that we reached a pretty good step where
1 - 100 of 112 matches
Mail list logo
