Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Flavio Percoco]

On 10/02/17 15:24 +0100, 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 the demo.

His plan is to have this demo out by next week and that may be too tight for the
containerized version of TripleO (it may be not, let's try). That said, I think
it's still a good opportunity for us to sit down at the PTG and play with this a
bit further.

So, before we set a date and time for this, I wanted to extend the invite to
other folks and see if there's some interest. It be great to also have folks
from Kolla and openstack-helm joining.

Looking forward to hearing ideas and hacking with y'all,
Flavio


So, given the interest and my hope to group as much folks from other teams as
possible, what about we just schedule this for Wednesday at 09:00 am ?

I'm not sure what room we can crash yet but I'll figure it out soon and let
y'all know.

Any objections/observations?
Flavio


Ok, one more heads up here. We have a room!

I've put the projects names in one of the cross-teams collaboration rooms[0].

The room name is Macon and it's setup in fishbowl style. It can fit 50, which
seemed more than enough for this session.

Looking forward to seeing y'all there,
Flavio

[0] https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms


--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Pete Birley]

Flavio,

Sounds great to me, look forward to catching up and plotting some
collaborative hacking :)

Catch you all at the PTG!

Cheers

Pete

On Fri, Feb 10, 2017 at 2: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 the demo.
>>
>> His plan is to have this demo out by next week and that may be too tight
>> for the
>> containerized version of TripleO (it may be not, let's try). That said, I
>> think
>> it's still a good opportunity for us to sit down at the PTG and play with
>> this a
>> bit further.
>>
>> So, before we set a date and time for this, I wanted to extend the invite
>> to
>> other folks and see if there's some interest. It be great to also have
>> folks
>> from Kolla and openstack-helm joining.
>>
>> Looking forward to hearing ideas and hacking with y'all,
>> Flavio
>>
>
> So, given the interest and my hope to group as much folks from other teams
> as
> possible, what about we just schedule this for Wednesday at 09:00 am ?
>
> I'm not sure what room we can crash yet but I'll figure it out soon and let
> y'all know.
>
> Any objections/observations?
>
> Flavio
>
> --
> @flaper87
> Flavio Percoco
>
> __
> 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
>
>


-- 

[image: Port.direct] 

Pete Birley / Director
pete@port.direct / +447446862551

*PORT.*DIRECT
United Kingdom
https://port.direct

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. Port.direct is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.
__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Antoni Segura Puimedon]

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 the demo.
>>
>> His plan is to have this demo out by next week and that may be too tight
>> for the
>> containerized version of TripleO (it may be not, let's try). That said, I
>> think
>> it's still a good opportunity for us to sit down at the PTG and play with
>> this a
>> bit further.
>>
>> So, before we set a date and time for this, I wanted to extend the invite
>> to
>> other folks and see if there's some interest. It be great to also have
>> folks
>> from Kolla and openstack-helm joining.
>>
>> Looking forward to hearing ideas and hacking with y'all,
>> Flavio
>>
>
> So, given the interest and my hope to group as much folks from other teams
> as
> possible, what about we just schedule this for Wednesday at 09:00 am ?
>
> I'm not sure what room we can crash yet but I'll figure it out soon and let
> y'all know.
>
> Any objections/observations?


Sounds good to me!


>
> Flavio
>
> --
> @flaper87
> Flavio Percoco
>
> __
> 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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Flavio Percoco]

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 the demo.

His plan is to have this demo out by next week and that may be too tight for the
containerized version of TripleO (it may be not, let's try). That said, I think
it's still a good opportunity for us to sit down at the PTG and play with this a
bit further.

So, before we set a date and time for this, I wanted to extend the invite to
other folks and see if there's some interest. It be great to also have folks
from Kolla and openstack-helm joining.

Looking forward to hearing ideas and hacking with y'all,
Flavio


So, given the interest and my hope to group as much folks from other teams as
possible, what about we just schedule this for Wednesday at 09:00 am ?

I'm not sure what room we can crash yet but I'll figure it out soon and let
y'all know.

Any objections/observations?
Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Pete Birley]

Dan,

There's no way I could have put that any better than Tony!
Though he's given me a bit too much credit, I actually just extended his
work to make use of Lbaasv2, and never got round to fully making use of
OVN's native LoadBalancing.

Cheers

Pete

On Fri, Feb 10, 2017 at 12:34 AM, Antoni Segura Puimedon  wrote:

>
>
> 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 several reasons:
>>
>> 1) Separation of control and data plane in deployments
>> 2) Tenant isolation in multi-tenant Ironic BMaaS
>> 3) Network Function Virtualization (NFV) use cases
>>
>> The intention of the isolated networking model for TripleO was to
>> separate control and data plane, as well as tenant from administrative
>> traffic. A secondary goal was to make this highly configurable and
>> customizable. This has been well received by many operators who have
>> rigid security isolation requirements (such as PCI-DSS for financial
>> transactions), or those who customize their underlay network to
>> integrate into an existing networking topology. I'm thinking about how
>> to do something similar in Kubernetes, perhaps with Kuryr.
>>
>> The Harbor project looks very interesting. Do you have any more
>> information about how Harbor uses Raven to achieve isolation? Also, are
>> you saying that Harbor uses an older (prototype) version of Raven, or
>> are you referring to Raven itself as a prototype?
>>
>
> I can answer to some of that :-)
>
> Raven was the Python 3 asyncio based prototype my team built back
> when I was at Midokura for integrating Kubernetes and Neutron as
> something to then upstream to Kuryr with the help of the rest of the
> community (taking the lessons learned from the PoC and improving
> on it). So yes, Raven itself was a prototype (a quite functional one)
> and led to what we know today in Kuryr as the kuryr-kubernetes
> controller, which is now almost at the same level of features, missing
> just two patches for the service support.
>
> I have to note here, that Pete did some interesting modifications to
> Raven like OVN support addition and leveraging the watcher model
> to make, IIRC, the cluster services use the native OVN load balancer
> rather than neutron-lbaas.
>
> The Kuryr-kubernetes controller is built with pluggability in mind and it
> has a system of drivers (using stevedore) for acquiring resources.  This
> makes things like what Pete did easier to achieve with the new codebase
> and also pick yourself the level of isolation that you want. Let's say
> that you want
> to have the different OSt components pick different networks or even
> projects, you would just need to make a very small driver like [0] or [1]
> that could, for example, make an http request to some service that held
> a mapping, read some specific annotation, etc.
>
> In terms of isolation for deployments, we are starting discussion about
> leveraging the new CNI support for reporting multiple interfaces (still not
> implemented in k8s, but playing is fun) so that we can put the pods that
> need it both in the control and in the data plane, we'll probably need to
> tweak the interface of the drivers so that they can return an iterable.
>
>
> [0] https://github.com/openstack/kuryr-kubernetes/blob/master/
> kuryr_kubernetes/controller/drivers/default_project.py#L39
> [1] https://github.com/openstack/kuryr-kubernetes/
> blob/master/kuryr_kubernetes/controller/drivers/default_subnet.py#L56
>
>>
>> I'll be at the PTG Tuesday through Friday morning. I'm looking forward
>> to having some conversations about this topic.
>>
>> --
>> Dan Sneddon |  Senior Principal OpenStack Engineer
>> dsned...@redhat.com |  redhat.com/openstack
>> dsneddon:irc|  @dxs:twitter
>>
>> On 02/09/2017 09:56 AM, Pete Birley wrote:
>> > Hi Flavio,
>> >
>> > I've been doing some work on packaging Kuryr for use with K8s as an
>> > underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
>> > project I showed you used Tony's old Raven Prototype to provide the
>> > network isolation and segmentation in K8s. I've since begun to lay the
>> > groundwork for OpenStack-Helm to support similar modes of operation,
>> > allowing both service isolation and also combined networking between
>> > OpenStack and K8s, where pods and VMs can co-exist on the same Neutron
>> > Networks.
>> >
>> > I'm not sure I will have things fully functional within OpenStack-Helm
>> > by the PTG, but it would be great to sit down and work out how we can
>> > ensure that not only do we not end up replicating work needlessly, but
>> > also find further opportunities to collaborate. I'll be in Atlanta all
>> > week, though I think some of the OS-Helm and Kolla-K8s developers will
>> > be 

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Antoni Segura Puimedon]

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 several reasons:
>
> 1) Separation of control and data plane in deployments
> 2) Tenant isolation in multi-tenant Ironic BMaaS
> 3) Network Function Virtualization (NFV) use cases
>
> The intention of the isolated networking model for TripleO was to
> separate control and data plane, as well as tenant from administrative
> traffic. A secondary goal was to make this highly configurable and
> customizable. This has been well received by many operators who have
> rigid security isolation requirements (such as PCI-DSS for financial
> transactions), or those who customize their underlay network to
> integrate into an existing networking topology. I'm thinking about how
> to do something similar in Kubernetes, perhaps with Kuryr.
>
> The Harbor project looks very interesting. Do you have any more
> information about how Harbor uses Raven to achieve isolation? Also, are
> you saying that Harbor uses an older (prototype) version of Raven, or
> are you referring to Raven itself as a prototype?
>

I can answer to some of that :-)

Raven was the Python 3 asyncio based prototype my team built back
when I was at Midokura for integrating Kubernetes and Neutron as
something to then upstream to Kuryr with the help of the rest of the
community (taking the lessons learned from the PoC and improving
on it). So yes, Raven itself was a prototype (a quite functional one)
and led to what we know today in Kuryr as the kuryr-kubernetes
controller, which is now almost at the same level of features, missing
just two patches for the service support.

I have to note here, that Pete did some interesting modifications to
Raven like OVN support addition and leveraging the watcher model
to make, IIRC, the cluster services use the native OVN load balancer
rather than neutron-lbaas.

The Kuryr-kubernetes controller is built with pluggability in mind and it
has a system of drivers (using stevedore) for acquiring resources.  This
makes things like what Pete did easier to achieve with the new codebase
and also pick yourself the level of isolation that you want. Let's say that
you want
to have the different OSt components pick different networks or even
projects, you would just need to make a very small driver like [0] or [1]
that could, for example, make an http request to some service that held
a mapping, read some specific annotation, etc.

In terms of isolation for deployments, we are starting discussion about
leveraging the new CNI support for reporting multiple interfaces (still not
implemented in k8s, but playing is fun) so that we can put the pods that
need it both in the control and in the data plane, we'll probably need to
tweak the interface of the drivers so that they can return an iterable.


[0]
https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/default_project.py#L39
[1]
https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/default_subnet.py#L56

>
> I'll be at the PTG Tuesday through Friday morning. I'm looking forward
> to having some conversations about this topic.
>
> --
> Dan Sneddon |  Senior Principal OpenStack Engineer
> dsned...@redhat.com |  redhat.com/openstack
> dsneddon:irc|  @dxs:twitter
>
> On 02/09/2017 09:56 AM, Pete Birley wrote:
> > Hi Flavio,
> >
> > I've been doing some work on packaging Kuryr for use with K8s as an
> > underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
> > project I showed you used Tony's old Raven Prototype to provide the
> > network isolation and segmentation in K8s. I've since begun to lay the
> > groundwork for OpenStack-Helm to support similar modes of operation,
> > allowing both service isolation and also combined networking between
> > OpenStack and K8s, where pods and VMs can co-exist on the same Neutron
> > Networks.
> >
> > I'm not sure I will have things fully functional within OpenStack-Helm
> > by the PTG, but it would be great to sit down and work out how we can
> > ensure that not only do we not end up replicating work needlessly, but
> > also find further opportunities to collaborate. I'll be in Atlanta all
> > week, though I think some of the OS-Helm and Kolla-K8s developers will
> > be leaving on Wed, would a particular day/time work best for you?
> >
> >
> > Cheers
> >
> > Pete (portdirect)
> >
> >
> > On Thu, Feb 9, 2017 at 8:57 AM, 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 the demo.
> >
> > 

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Dan Sneddon]

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 several reasons:

1) Separation of control and data plane in deployments
2) Tenant isolation in multi-tenant Ironic BMaaS
3) Network Function Virtualization (NFV) use cases

The intention of the isolated networking model for TripleO was to
separate control and data plane, as well as tenant from administrative
traffic. A secondary goal was to make this highly configurable and
customizable. This has been well received by many operators who have
rigid security isolation requirements (such as PCI-DSS for financial
transactions), or those who customize their underlay network to
integrate into an existing networking topology. I'm thinking about how
to do something similar in Kubernetes, perhaps with Kuryr.

The Harbor project looks very interesting. Do you have any more
information about how Harbor uses Raven to achieve isolation? Also, are
you saying that Harbor uses an older (prototype) version of Raven, or
are you referring to Raven itself as a prototype?

I'll be at the PTG Tuesday through Friday morning. I'm looking forward
to having some conversations about this topic.

-- 
Dan Sneddon |  Senior Principal OpenStack Engineer
dsned...@redhat.com |  redhat.com/openstack
dsneddon:irc|  @dxs:twitter

On 02/09/2017 09:56 AM, Pete Birley wrote:
> Hi Flavio,
> 
> I've been doing some work on packaging Kuryr for use with K8s as an
> underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
> project I showed you used Tony's old Raven Prototype to provide the
> network isolation and segmentation in K8s. I've since begun to lay the
> groundwork for OpenStack-Helm to support similar modes of operation,
> allowing both service isolation and also combined networking between
> OpenStack and K8s, where pods and VMs can co-exist on the same Neutron
> Networks.
> 
> I'm not sure I will have things fully functional within OpenStack-Helm
> by the PTG, but it would be great to sit down and work out how we can
> ensure that not only do we not end up replicating work needlessly, but
> also find further opportunities to collaborate. I'll be in Atlanta all
> week, though I think some of the OS-Helm and Kolla-K8s developers will
> be leaving on Wed, would a particular day/time work best for you?
> 
> 
> Cheers
> 
> Pete (portdirect)
> 
> 
> On Thu, Feb 9, 2017 at 8:57 AM, 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 the demo.
> 
> His plan is to have this demo out by next week and that may be too
> tight for the
> containerized version of TripleO (it may be not, let's try). That
> said, I think
> it's still a good opportunity for us to sit down at the PTG and play
> with this a
> bit further.
> 
> So, before we set a date and time for this, I wanted to extend the
> invite to
> other folks and see if there's some interest. It be great to also
> have folks
> from Kolla and openstack-helm joining.
> 
> Looking forward to hearing ideas and hacking with y'all,
> Flavio
> 
> -- 
> @flaper87
> Flavio Percoco
> 
> __
> 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
> 
> 
> 
> 
> 
> -- 
> 
> Port.direct 
> 
>   
> 
> Pete Birley / Director 
> pete@port.direct  / +447446862551
> 
> *PORT.*DIRECT 
> United Kingdom 
> https://port.direct
> 
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended
> recipient(s). Any unauthorized disclosure, dissemination, distribution,
> copying or the taking of any action in reliance on the information
> herein is prohibited. E-mails are not secure and cannot be guaranteed to
> be error free as they can be intercepted, amended, or contain viruses.
> Anyone who communicates with us by e-mail is deemed to have accepted
> these risks. Port.direct is not responsible for errors or omissions in
> this message and denies any responsibility for any damage arising from
> the use of e-mail. Any opinion and other statement contained in this
> message and any attachment are solely those of the author and do not
> necessarily represent those of the 

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Pete Birley]

Michal,

It's actually really easy to achieve in k8s, provided we make some
concessions: at least one keystone and neutron API pod needs to run in the
host's network namespace (and the supporting DB's). This may not be
acceptable for Tripple-O, but I'm pretty sure we could find a workable
solution without too much hair-loss :) I'd need to revisit to the Kolla-K8s
options but it would be really easy to add an additional region with
OpenStack-helm to provide further separation of roles if required.

Cheers

Pete

On Thu, Feb 9, 2017 at 6:04 PM, Michał Jastrzębski  wrote:

> So from kolla (and kolla-k8s) point of view, this is chicken egg problem:)
> We could use kuryr for our networking, but who will deploy kuryr? We don't
> have undercloud concept in any of kollas so far. With Kolla-ansible we
> really use host networking all the way and for k8s we have k8s networking
> infra.
>
> That being said, deployment of kuryr with kolla is well within our mission
> and well... it's there:) https://github.com/openstack/kolla-ansible/tree/
> master/ansible/roles/kuryr .
>
> If we consider tripleo case, where kuryr can be part of undercloud, we
> gain bunch of new possibilities, I'd love to have this discussion.
>
> Cheers,
> Michal
>
> On 9 February 2017 at 09:56, Pete Birley  wrote:
>
>> Hi Flavio,
>>
>> I've been doing some work on packaging Kuryr for use with K8s as an
>> underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
>> project I showed you used Tony's old Raven Prototype to provide the network
>> isolation and segmentation in K8s. I've since begun to lay the groundwork
>> for OpenStack-Helm to support similar modes of operation, allowing both
>> service isolation and also combined networking between OpenStack and K8s,
>> where pods and VMs can co-exist on the same Neutron Networks.
>>
>> I'm not sure I will have things fully functional within OpenStack-Helm by
>> the PTG, but it would be great to sit down and work out how we can ensure
>> that not only do we not end up replicating work needlessly, but also find
>> further opportunities to collaborate. I'll be in Atlanta all week, though I
>> think some of the OS-Helm and Kolla-K8s developers will be leaving on Wed,
>> would a particular day/time work best for you?
>>
>>
>> Cheers
>>
>> Pete (portdirect)
>>
>>
>> On Thu, Feb 9, 2017 at 8:57 AM, 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 the demo.
>>>
>>> His plan is to have this demo out by next week and that may be too tight
>>> for the
>>> containerized version of TripleO (it may be not, let's try). That said,
>>> I think
>>> it's still a good opportunity for us to sit down at the PTG and play
>>> with this a
>>> bit further.
>>>
>>> So, before we set a date and time for this, I wanted to extend the
>>> invite to
>>> other folks and see if there's some interest. It be great to also have
>>> folks
>>> from Kolla and openstack-helm joining.
>>>
>>> Looking forward to hearing ideas and hacking with y'all,
>>> Flavio
>>>
>>> --
>>> @flaper87
>>> Flavio Percoco
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>>
>> [image: Port.direct] 
>>
>> Pete Birley / Director
>> pete@port.direct / +447446862551 <+44%207446%20862551>
>>
>> *PORT.*DIRECT
>> United Kingdom
>> https://port.direct
>>
>> This e-mail message may contain confidential or legally privileged
>> information and is intended only for the use of the intended recipient(s).
>> Any unauthorized disclosure, dissemination, distribution, copying or the
>> taking of any action in reliance on the information herein is prohibited.
>> E-mails are not secure and cannot be guaranteed to be error free as they
>> can be intercepted, amended, or contain viruses. Anyone who communicates
>> with us by e-mail is deemed to have accepted these risks. Port.direct is
>> not responsible for errors or omissions in this message and denies any
>> responsibility for any damage arising from the use of e-mail. Any opinion
>> and other statement contained in this message and any attachment are solely
>> those of the author and do not necessarily represent those of the company.
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> 

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Michał Jastrzębski]

So from kolla (and kolla-k8s) point of view, this is chicken egg problem:)
We could use kuryr for our networking, but who will deploy kuryr? We don't
have undercloud concept in any of kollas so far. With Kolla-ansible we
really use host networking all the way and for k8s we have k8s networking
infra.

That being said, deployment of kuryr with kolla is well within our mission
and well... it's there:)
https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/kuryr .

If we consider tripleo case, where kuryr can be part of undercloud, we gain
bunch of new possibilities, I'd love to have this discussion.

Cheers,
Michal

On 9 February 2017 at 09:56, Pete Birley  wrote:

> Hi Flavio,
>
> I've been doing some work on packaging Kuryr for use with K8s as an
> underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
> project I showed you used Tony's old Raven Prototype to provide the network
> isolation and segmentation in K8s. I've since begun to lay the groundwork
> for OpenStack-Helm to support similar modes of operation, allowing both
> service isolation and also combined networking between OpenStack and K8s,
> where pods and VMs can co-exist on the same Neutron Networks.
>
> I'm not sure I will have things fully functional within OpenStack-Helm by
> the PTG, but it would be great to sit down and work out how we can ensure
> that not only do we not end up replicating work needlessly, but also find
> further opportunities to collaborate. I'll be in Atlanta all week, though I
> think some of the OS-Helm and Kolla-K8s developers will be leaving on Wed,
> would a particular day/time work best for you?
>
>
> Cheers
>
> Pete (portdirect)
>
>
> On Thu, Feb 9, 2017 at 8:57 AM, 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 the demo.
>>
>> His plan is to have this demo out by next week and that may be too tight
>> for the
>> containerized version of TripleO (it may be not, let's try). That said, I
>> think
>> it's still a good opportunity for us to sit down at the PTG and play with
>> this a
>> bit further.
>>
>> So, before we set a date and time for this, I wanted to extend the invite
>> to
>> other folks and see if there's some interest. It be great to also have
>> folks
>> from Kolla and openstack-helm joining.
>>
>> Looking forward to hearing ideas and hacking with y'all,
>> Flavio
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
>
> [image: Port.direct] 
>
> Pete Birley / Director
> pete@port.direct / +447446862551 <+44%207446%20862551>
>
> *PORT.*DIRECT
> United Kingdom
> https://port.direct
>
> This e-mail message may contain confidential or legally privileged
> information and is intended only for the use of the intended recipient(s).
> Any unauthorized disclosure, dissemination, distribution, copying or the
> taking of any action in reliance on the information herein is prohibited.
> E-mails are not secure and cannot be guaranteed to be error free as they
> can be intercepted, amended, or contain viruses. Anyone who communicates
> with us by e-mail is deemed to have accepted these risks. Port.direct is
> not responsible for errors or omissions in this message and denies any
> responsibility for any damage arising from the use of e-mail. Any opinion
> and other statement contained in this message and any attachment are solely
> those of the author and do not necessarily represent those of the company.
>
> __
> 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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Pete Birley]

Hi Flavio,

I've been doing some work on packaging Kuryr for use with K8s as an
underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor
project I showed you used Tony's old Raven Prototype to provide the network
isolation and segmentation in K8s. I've since begun to lay the groundwork
for OpenStack-Helm to support similar modes of operation, allowing both
service isolation and also combined networking between OpenStack and K8s,
where pods and VMs can co-exist on the same Neutron Networks.

I'm not sure I will have things fully functional within OpenStack-Helm by
the PTG, but it would be great to sit down and work out how we can ensure
that not only do we not end up replicating work needlessly, but also find
further opportunities to collaborate. I'll be in Atlanta all week, though I
think some of the OS-Helm and Kolla-K8s developers will be leaving on Wed,
would a particular day/time work best for you?


Cheers

Pete (portdirect)


On Thu, Feb 9, 2017 at 8:57 AM, 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 the demo.
>
> His plan is to have this demo out by next week and that may be too tight
> for the
> containerized version of TripleO (it may be not, let's try). That said, I
> think
> it's still a good opportunity for us to sit down at the PTG and play with
> this a
> bit further.
>
> So, before we set a date and time for this, I wanted to extend the invite
> to
> other folks and see if there's some interest. It be great to also have
> folks
> from Kolla and openstack-helm joining.
>
> Looking forward to hearing ideas and hacking with y'all,
> Flavio
>
> --
> @flaper87
> Flavio Percoco
>
> __
> 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
>
>


-- 

[image: Port.direct] 

Pete Birley / Director
pete@port.direct / +447446862551

*PORT.*DIRECT
United Kingdom
https://port.direct

This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended recipient(s).
Any unauthorized disclosure, dissemination, distribution, copying or the
taking of any action in reliance on the information herein is prohibited.
E-mails are not secure and cannot be guaranteed to be error free as they
can be intercepted, amended, or contain viruses. Anyone who communicates
with us by e-mail is deemed to have accepted these risks. Port.direct is
not responsible for errors or omissions in this message and denies any
responsibility for any damage arising from the use of e-mail. Any opinion
and other statement contained in this message and any attachment are solely
those of the author and do not necessarily represent those of the company.
__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Brandon B. Jozsa]

Flavio,

This is a great opportunity, and we would very much like to contribute. In 
fact, there are developers that span both Kolla-Kubernetes and Openstack-Helm 
and I am sure they would be perfect resources for what you’re looking for. What 
is a good “next step” for getting involved? I believe one of our developers has 
already reached out to the TripleO team, and I think there are some great 
opportunities for collaboration.

Looking forward to this, and thank you for reaching out and including us.

Brandon


On February 9, 2017 at 10:56:53 AM, Steven Dake (stdake) 
(std...@cisco.com<mailto:std...@cisco.com>) wrote:

Flavio,

I think Michal (inc0) was planning to reach out to the TripleO team to at least 
get one or more design sessions in Wednesday. Kolla’s PTG schedule for Monday 
and Tuesday is packed with a wait list of topics. I depart IIRC Wednesday at 
11AM – I had asked inc0 if we do these we do them Wednesday in the morning 
around 8-10 or 9-10 to catch the people that are leaving early. As there isn’t 
a CP Design Track at the PTG (that I saw in the schedule), I believe the last 
proposal from someone (forgot who, apologies there) in the TripleO team was to 
shave a couple hours off Wednesday morning to sort out CP collaboration work.

If that isn’t what your proposal is about, wfm – I’d like to attend in any 
regard. My travel is locked in as my daughter is performing Thursday so I need 
to be home by then (and BOS->AZ = 6 hr flight). Other folks from Kolla have 
shown interest in participation in a cross-project effort on Wednesday and will 
be there all week.

Regards
-steve

-Original Message-
From: Flavio Percoco <fla...@redhat.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Thursday, February 9, 2017 at 1:57 AM
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on 
containers leaveraging kuryr

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 the demo.

His plan is to have this demo out by next week and that may be too tight for the
containerized version of TripleO (it may be not, let's try). That said, I think
it's still a good opportunity for us to sit down at the PTG and play with this a
bit further.

So, before we set a date and time for this, I wanted to extend the invite to
other folks and see if there's some interest. It be great to also have folks
from Kolla and openstack-helm joining.

Looking forward to hearing ideas and hacking with y'all,
Flavio

--
@flaper87
Flavio Percoco


__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Steven Dake (stdake)]

Flavio,

I think Michal (inc0) was planning to reach out to the TripleO team to at least 
get one or more design sessions in Wednesday.  Kolla’s PTG schedule for Monday 
and Tuesday is packed with a wait list of topics.  I depart IIRC Wednesday at 
11AM – I had asked inc0 if we do these we do them Wednesday in the morning 
around 8-10 or 9-10 to catch the people that are leaving early.  As there isn’t 
a CP Design Track at the PTG (that I saw in the schedule), I believe the last 
proposal from someone (forgot who, apologies there) in the TripleO team was to 
shave a couple hours off Wednesday morning to sort out CP collaboration work.

If that isn’t what your proposal is about, wfm – I’d like to attend in any 
regard.  My travel is locked in as my daughter is performing Thursday so I need 
to be home by then (and BOS->AZ = 6 hr flight).  Other folks from Kolla have 
shown interest in participation in a cross-project effort on Wednesday and will 
be there all week.

Regards
-steve

-Original Message-
From: Flavio Percoco <fla...@redhat.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Thursday, February 9, 2017 at 1:57 AM
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on 
containers leaveraging kuryr

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 the demo.

His plan is to have this demo out by next week and that may be too tight 
for the
containerized version of TripleO (it may be not, let's try). That said, I 
think
it's still a good opportunity for us to sit down at the PTG and play with 
this a
bit further.

So, before we set a date and time for this, I wanted to extend the invite to
other folks and see if there's some interest. It be great to also have folks
from Kolla and openstack-helm joining.

Looking forward to hearing ideas and hacking with y'all,
Flavio

-- 
@flaper87
Flavio Percoco


__
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][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

[Flavio Percoco]

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 the demo.

His plan is to have this demo out by next week and that may be too tight for the
containerized version of TripleO (it may be not, let's try). That said, I think
it's still a good opportunity for us to sit down at the PTG and play with this a
bit further.

So, before we set a date and time for this, I wanted to extend the invite to
other folks and see if there's some interest. It be great to also have folks
from Kolla and openstack-helm joining.

Looking forward to hearing ideas and hacking with y'all,
Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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