Open Stack

On 03/29/2017 03:39 PM, Steve Gordon wrote:
> ----- Original Message -----
>> From: "Davanum Srinivas" <davanum at gmail.com>
>> To: "Chris Hoge" <chris at openstack.org>
>> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>,
>> "kubernetes-sig-openstack" <kubernetes-sig-openstack at googlegroups.com>
>> Sent: Wednesday, March 29, 2017 2:28:29 PM
>> Subject: Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes
>>
>> Team,
>>
>> Repo is ready:
>> http://git.openstack.org/cgit/openstack/k8s-cloud-provider
>>
>> I've taken the liberty of updating it with the latest changes in the
>> kubernetes/kubernetes repo:
>> https://review.openstack.org/#/q/project:openstack/k8s-cloud-provider is
>> ready
>>
>> So logical next step would be to add CI jobs to test in OpenStack
>> Infra. Anyone interested?
> 
> One question I have around this - do we have a shared view of what the ideal matrix of tested combinations would like? E.g. kubernetes master on openstack project's master, kubernetes master on openstack project's stable branches (where available), do we also need/want to test kubernetes stable milestones, etc.
> 
> At a high level my goal would be the same as Chris's "k8s gating on OpenStack in the same ways that it does on AWS and GCE." which would imply reporting results on PRs proposed to K8S master *before* they merge but not sure we all agree on what that actually means testing against in practice on the OpenStack side of the equation?

I think we want to have jobs that have the ability to test:

1) A proposed change to k8s-openstack-provider against current master of
OpenStack
2) A proposed change to k8s-openstack-provider against a stable release
of OpenStack
3) A proposed change to OpenStack against current master of
k8s-openstack-provider
4) A proposed change to OpenStack against stable release of
k8s-openstack-provider

Those are all easy now that the code is in gerrit, and it's well defined
what triggers and where it reports.

Additionally, we need to test the surface area between
k8s-openstack-provider and k8s itself. (if we wind up needing to test
k8s against proposed changes to OpenStack then we've likely done
something wrong in life)

5) A proposed change to k8s-openstack-provider against current master of k8s
6) A proposed change to k8s-openstack-provider against a stable release
of k8s
7) A proposed change to k8s against current master of k8s-openstack-provider
8) A proposed change to k8s against stable release of k8s-openstack-provider

5 and 6 are things we can do right now. 7 and 8 will have to wait for GH
support to land in zuul (without which we can neither trigger test jobs
on proposed changes to k8s nor can we report the results back to anyone)

I would recommend that we make 5 and 6 non-voting until such a time as
we are reporting on 7 and 8 back to k8s and have a reasonable
expectation someone will pay attention to failures - otherwise k8s will
be able to wedge the k8s-openstack-provider gate.

>> On Sat, Mar 25, 2017 at 12:10 PM, Chris Hoge <chris at openstack.org> wrote:
>>>
>>>
>>> On Friday, March 24, 2017 at 8:46:42 AM UTC-7, Antoni Segura Puimedon
>>> wrote:
>>>>
>>>>
>>>>
>>>> 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.openstack.org/#/c/449641/
>>>>>>
>>>>>> This request pulls in the existing code from kubernetes/kubernetes
>>>>>> repo and preserves the git history too
>>>>>> https://github.com/dims/k8s-cloud-provider
>>>>>>
>>>>>> Anyone interested? please ping me on Slack or IRC and we can continue
>>>>>> this work.
>>>>>
>>>>> Yeah - I would love to continue the provider work on gerrit :)
>>>>>
>>>>> Is there a way for us to make sure changes in the k8 master don't
>>>>> break our plugin? Or do we need to periodic jobs on the provider repo
>>>>> to catch breakages in the plugin interface?
>>>>
>>>>
>>>> I suppose the options are either:
>>>>
>>>> ask k8s to add select external cloud providers in the CI
>>>> Have a webhook in the k8s repo that triggered CI on the OSt infra
>>>
>>>
>>> Yes please to these. My preference is for the provider to remain upstream
>>> in
>>> k8s, but it's development has stalled out a bit. I want the best provider
>>> possible, but also want to make sure it's tested and visible to the k8s
>>> community that want to run on OpenStack. I've mentioned before that one of
>>> my goals is to have k8s gating on OpenStack in the same ways that it does
>>> on
>>> AWS and GCE.
>>>
>>> -Chris
>>>
>>>
>>>>>
>>>>>
>>>>> Thanks, Graham
>>>>>
>>>>>
>>>>>>> __________________________________________________________________________
>>>>>> 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
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "kubernetes-sig-openstack" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to kubernetes-sig-openstack+unsubscribe at googlegroups.com.
>>> To post to this group, send email to
>>> kubernetes-sig-openstack at googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/kubernetes-sig-openstack/a7b56756-7efe-4179-8467-6a689f1abe63%40googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Davanum Srinivas :: https://twitter.com/dims
>>
>> __________________________________________________________________________
>> 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
>>
>