Re: [openstack-dev] [tc] supporting Go
On Mon, May 9, 2016 at 8:21 PM, Ben Swartzlanderwrote: > > > 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 quite well. If we were to write the whole system in C/C++, there would be a lot more bugs and a lot more lines of code. Parsing market data does not always need the fastest code, so Perl served us (and I am sure it will continue to do its job) very well. Lastly, I think people that are insulting on mailing lists should get their head checked first. No? :-) Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html __ 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
Re: [openstack-dev] [tc] supporting Go
On Mon, May 9, 2016 at 4:57 AM, Thomas Goirandwrote: > > 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 go$VERSION.$OS-$ARCH.tar.gz (Ref: https://golang.org/doc/install ) IMO, that the beauty of Go (the Go compiler is itself written in Go) -- as the compiler generates static binaries, deployment is usually done by copying the binaries to the remote machine. And looks like Ubuntu 16.04 has official binaries for Go 1.6. Again, I've never installed Go from apt-get or yum! https://launchpad.net/ubuntu/xenial/+source/golang-1.6 Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > Cheers, > > Thomas > > > __ > 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 __ 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
Re: [openstack-dev] [tc] supporting Go
On Sun, May 8, 2016 at 5:16 AM, Thomas Goirandwrote: > 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): https://golang.org/cmd/go/#hdr-Description_of_build_modes And the design doc: https://golang.org/s/execmodes Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > > Cheers, > > Thomas Goirand (zigo) > > > __ > 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 __ 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
Re: [openstack-dev] [tc] supporting Go
On Tue, May 3, 2016 at 12:24 PM, John Dickinson <m...@not.mn> wrote: > That's an interesting point. I'm not very familiar with Golang itself yet, > and I haven't yet had to manage any Golang projects in prod. These sorts of > questions are great! > > See: https://golang.org/doc/go1compat > If a distro is distributing pre-compiled binaries, isn't the compatibility > issue up to the distros? OpenStack is not distributing binaries (or even > distro packages!), so while it's an important question, how does it affect > the question of golang being an ok language in which to write openstack > source code? > I mean a commercial OpenStack distro... OpenStack does not distribute binaries today (because Python is an interpreted language), but Go is a compiled language. So may be I should simplify my question -- in what form should a commercial OpenStack distro distribute OpenStack components written in Go? Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > --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-package & pre-compile everything, > > then the compiled Go libs won't be compatible with old/new releases of > the > > Go compiler that the user may want to install on their systems. > > > > Rayson > > > > == > > Open Grid Scheduler - The Official Open Source Grid Engine > > http://gridscheduler.sourceforge.net/ > > http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > > > > > > > > > On Tue, May 3, 2016 at 11:58 AM, John Dickinson <m...@not.mn> wrote: > > > >> TC, > >> > >> In reference to > >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html > >> and Thierry's reply, I'm currently drafting a TC resolution to update > >> > http://governance.openstack.org/resolutions/20150901-programming-languages.html > >> to include Go as a supported language in OpenStack projects. > >> > >> As a starting point, what would you like to see addressed in the > document > >> I'm drafting? > >> > >> --John > >> > >> > >> > >> > >> > __ > >> 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 > >> > >> > > > __ > > 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 > > __ > 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 > > __ 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
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 compiler that the user may want to install on their systems. Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html On Tue, May 3, 2016 at 11:58 AM, John Dickinsonwrote: > TC, > > In reference to > http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html > and Thierry's reply, I'm currently drafting a TC resolution to update > http://governance.openstack.org/resolutions/20150901-programming-languages.html > to include Go as a supported language in OpenStack projects. > > As a starting point, what would you like to see addressed in the document > I'm drafting? > > --John > > > > > __ > 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 > > __ 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
Re: [openstack-dev] [Nova] FPGA as a resource
On Wed, Apr 6, 2016 at 6:37 AM, Daniel P. Berrangewrote: > 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 discovery & scheduling functionality needed. https://wiki.openstack.org/wiki/Enhanced-platform-awareness-pcie However, I was reading the Intel ONP whitepapers earlier, and found that Intel has dropped coverage of the EPA functionality in 2.1: -> https://download.01.org/packet-processing/ONPS2.1/Intel_ONP_Release_2.1_Reference_Architecture_Guide_Rev1.0.pdf EPA is mentioned in section "6.3 Enhanced Platform Awareness" in 2.0: -> https://download.01.org/packet-processing/ONPS2.0/Intel_ONP_Release_2.0_Reference_Architecture_Guide_Rev1.0-1.pdf Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > Regards, > Daniel > -- > |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| > |: http://libvirt.org -o- http://virt-manager.org :| > |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| > |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| > > __ > 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 __ 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
[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 sent to the list ( http://lists.openstack.org/pipermail/openstack-dev/2016-February/086371.html ), but I was wondering if the new resource tracker is documented or should I just refer to the blueprints. Thanks, Rayson == Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html __ 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