[openstack-dev] [all] Small steps for Go
Davanum Srinivas
davanum at gmail.com
Wed Mar 15 17:52:58 UTC 2017
Bruno,
Here it is: https://etherpad.openstack.org/p/go-and-containers (it
was on the first email of this thread)
Thanks,
Dims
On Wed, Mar 15, 2017 at 1:46 PM, Bruno Morel <bmorel at internap.com> wrote:
> Still, I’m intrigued by this apparent duplication of efforts...
> esp since the discussions at the committee level tended to go the ‘inclusive’ way toward other communities (http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ section “Adjacent technologies”), can someone point me to the rational of doing gophercloud work ?
>
> *No judging here :) *
> I’m guessing someone has done the work already but I can’t find the etherpad Steve is talking about (when will those etherpad be searchable ? :P)
>
> Just trying to understand if we’re doing it for explicit, visible and logical reasons and where to put our efforts if we need to participate in the ‘golang for OpenStack’ efforts :)
>
> Tks
>
> Bruno
>
>
> On 2017-03-13, 8:13 PM, "Steve Gordon" <sgordon at redhat.com> wrote:
>
> ----- Original Message -----
> > From: "Steve Gordon" <sgordon at redhat.com>
> > To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> > Sent: Monday, March 13, 2017 8:11:34 PM
> > Subject: Re: [openstack-dev] [all] Small steps for Go
> >
> > ----- Original Message -----
> > > From: "Clint Byrum" <clint at fewbar.com>
> > > To: "openstack-dev" <openstack-dev at lists.openstack.org>
> > > Sent: Monday, March 13, 2017 1:44:19 PM
> > > Subject: Re: [openstack-dev] [all] Small steps for Go
> > >
> > > Excerpts from Davanum Srinivas's message of 2017-03-13 10:06:30 -0400:
> > > > Update:
> > > >
> > > > * We have a new git repo (EMPTY!) for the commons work -
> > > > http://git.openstack.org/cgit/openstack/golang-commons/
> > > > * The golang-client has little code, but lot of potential -
> > > > https://git.openstack.org/cgit/openstack/golang-client/
> > > >
> > >
> > > So, we're going to pretend gophercloud doesn't exist and continue to
> > > isolate ourselves from every other community?
> >
> > I'd add that gophercloud [1] is what the Kubernetes cloud provider framework
> > implementation for OpenStack [2] uses to talk to the underlying cloud*. This
> > would seem like a pretty good area for collaboration with other communities
> > to expand on what is there rather than start over?
> >
> > -Steve
> >
> > [1] https://github.com/gophercloud/gophercloud
> > [2]
> > https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/openstack
>
> Nevermind I see this train of thought also made its way to the etherpad...
>
> -Steve
>
> __________________________________________________________________________
> 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
>
>
> __________________________________________________________________________
> 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
--
Davanum Srinivas :: https://twitter.com/dims
More information about the OpenStack-dev
mailing list