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? Thanks, Dims On Sat, Mar 25, 2017 at 12:10 PM, Chris Hoge <ch...@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-requ...@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+unsubscr...@googlegroups.com. > To post to this group, send email to > kubernetes-sig-openst...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
