Open Stack

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 <inc007 at gmail.com> 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 <pete at port.direct> 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 <flavio at redhat.com> 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-request at lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>>
>> [image: Port.direct] <https://port.direct>
>>
>> Pete Birley / Director
>> pete at 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-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

[image: Port.direct] <https://port.direct>

Pete Birley / Director
pete at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170209/e9918314/attachment-0001.html>