[openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Michael Krotscheck
This post contains the current working draft of the JavaScript roadmap which myself and Beth Elwell will be working on in Newton. It’s a big list, and we need help - Overall themes for this cycle are Consistency, Interoperability, and engaging with the JavaScript community at large. Our end goal is

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Hayes, Graham
On 21/04/2016 15:39, Michael Krotscheck wrote: [...] > New: js-openstacklib > > This new project will be incubated as a single, gate-tested JavaScript > API client library for the OpenStack API’s. Its audience is software > engineers who wish to build their own user interface using modern > javascr

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Monty Taylor
On 04/21/2016 10:05 AM, Hayes, Graham wrote: On 21/04/2016 15:39, Michael Krotscheck wrote: [...] New: js-openstacklib This new project will be incubated as a single, gate-tested JavaScript API client library for the OpenStack API’s. Its audience is software engineers who wish to build their ow

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Michael Krotscheck
On Thu, Apr 21, 2016 at 8:10 AM Hayes, Graham wrote: > On 21/04/2016 15:39, Michael Krotscheck wrote: > > python-openstackclient does require the creation of a new repo for each > project (unless you are one of the chosen few). > > Does this mean you will accept all projects to the library, or ju

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Michael Krotscheck
On Thu, Apr 21, 2016 at 8:28 AM Monty Taylor wrote: > On 04/21/2016 10:05 AM, Hayes, Graham wrote: > > On 21/04/2016 15:39, Michael Krotscheck wrote: > >> used piecemeal, however trying to maintain code consistency across > >> multiple different projects is a hard lesson that others have already

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Monty Taylor
On 04/21/2016 10:32 AM, Michael Krotscheck wrote: On Thu, Apr 21, 2016 at 8:10 AM Hayes, Graham mailto:graham.ha...@hpe.com>> wrote: On 21/04/2016 15:39, Michael Krotscheck wrote: python-openstackclient does require the creation of a new repo for each project (unless you are one of

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Monty Taylor
On 04/21/2016 10:35 AM, Michael Krotscheck wrote: On Thu, Apr 21, 2016 at 8:28 AM Monty Taylor mailto:mord...@inaugust.com>> wrote: On 04/21/2016 10:05 AM, Hayes, Graham wrote: > On 21/04/2016 15:39, Michael Krotscheck wrote: >> used piecemeal, however trying to maintain code con

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-04-21 Thread Michael Krotscheck
On Thu, Apr 21, 2016 at 10:21 AM Monty Taylor wrote: > Neat! Maybe let's find a time at the summit to sit down and look through > things. I'm guessing that adding a second language consumer to the > config will raise a ton of useful questions around documentation, data > format, etc - but those w

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Anton Zemlyanov
Hi, I have a question on js-openstacklib. If it is intended for browsers, there will be lots of issues with cross-domain security policy, browser cannot just go to any REST resource it wants. There is either some server-side proxy required or cooperation of the all the REST services we want to tal

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Michael Krotscheck
Hello there, Anton- In Mitaka, most of OpenStack's services have landed CORS support. While it's not yet "Automagic" (i.e. it still requires some manual configuration), we no longer have to rely on any server component to render a user interface. The big outstanding things we need to do for CORS

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Thomas Goirand
Hi, If I may bring some insights from the distro's viewpoint... On 04/21/2016 04:35 PM, Michael Krotscheck wrote: > New: Xenial Build Nodes > > As of two weeks ago, OpenStack’s Infrastructure is running a version of > Node.js and npm more recent than what is available on Trusty LTS. > Ultimately

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Michael Krotscheck
Responses inline: On 04/21/2016 04:35 PM, Michael Krotscheck wrote: > > New: Xenial Build Nodes > > > > As of two weeks ago, OpenStack’s Infrastructure is running a version of > > Node.js and npm more recent than what is available on Trusty LTS. > Update: We're now on xenial. Yay LTS! > > Ultim

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Jeremy Stanley
On 2016-05-12 16:27:43 + (+), Michael Krotscheck wrote: [...] > Has anyone agreed to do the work to include debian nodes in infra? > I know we've got Centos7 and Fedora23 now, adding Debian doesn't > seem like a huge stretch. We have "debian-jessie" images and workers in Nodepool already.

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-13 Thread Thomas Goirand
On 05/12/2016 06:27 PM, Michael Krotscheck wrote: > Responses inline: > > On 04/21/2016 04:35 PM, Michael Krotscheck wrote: > > New: Xenial Build Nodes > > > > As of two weeks ago, OpenStack’s Infrastructure is running a > version of > > Node.js and npm more recent than wha