Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016 at 8:21 PM, Ben Swartzlander wrote: > > > If you think Perl is "nice" or "easy" you better get you head checked. > Each language has its strength and weakness, so just use the right tool for the job. In fact the system at the investment bank worked

Re: [openstack-dev] [tc] supporting Go

On Mon, May 9, 2016 at 4:57 AM, Thomas Goirand wrote: > > Do you know if that's already in use in some distros? Since the Go toolchain is pretty self-contained, most people just follow the official instructions to get it installed... by a one-step: # tar -C /usr/local -xzf

Re: [openstack-dev] [tc] supporting Go

On Sun, May 8, 2016 at 5:16 AM, Thomas Goirand wrote: > I've heard that upstream for > Golang was working on implementing shared libs, but I have no idea what > the status is. Does anyone know? In Go 1.5, the -buildmode option was introduced (eg. -buildmode=shared):

Re: [openstack-dev] [tc] supporting Go

> --John > > > > > On 3 May 2016, at 9:16, Rayson Ho wrote: > > > I like Go! However, Go does not offer binary compatibility between point > > releases. For those who install from source it may not be a big issue, > but > > for commercial distributions that pre

Re: [openstack-dev] [tc] supporting Go

I like Go! However, Go does not offer binary compatibility between point releases. For those who install from source it may not be a big issue, but for commercial distributions that pre-package & pre-compile everything, then the compiled Go libs won't be compatible with old/new releases of the Go

Re: [openstack-dev] [Nova] FPGA as a resource

On Wed, Apr 6, 2016 at 6:37 AM, Daniel P. Berrange wrote: > Most of the > work to support FPGA will be internal to nova, to deal with modelling > of assignable devices and their scheduling / allocation. I think the EPA blueprint already covers some of the FPGA device

[openstack-dev] [nova] New resource tracker

I found that even in the latest git tree, the resource_tracker is still marked as "deprecated and will be removed in the 14.0.0" in releasenova/conf/compute.py . With the Mitaka release coming up this week, is it still true that the code will be removed? I googled and found this status update