Re: [openstack-dev] [Tuskar][Horizon] Javascript linter

2014-04-02 Thread Kevin Conway
the JS*int projects from OpenStack? On 4/2/14 8:43 AM, Radomir Dopieralski openst...@sheep.art.pl wrote: On 02/04/14 15:26, Kevin Conway wrote: What licensing issues were brought up that prevent the use of JSLint or JSHint? Both are MIT licensed. Granted, JSLint has an additional clause

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

2014-02-06 Thread Kevin Conway
. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Conway ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

2014-02-04 Thread Kevin Conway
On 2/4/14 12:07 PM, victor stinner victor.stin...@enovance.com wrote: The purpose of replacing eventlet with asyncio is to get a well defined control flow, no more surprising task switching at random points. I disagree with this. Eventlet and gevent yield the execution context anytime an IO

[openstack-dev] [Trove] API extention update in order to support multi-databases integration

2014-02-03 Thread Kevin Conway
Denis, It seems that you are hitting on a couple of points here. 1) You aren't a fan of the fact that calls to user/db are routed through an extensions written for mysql. 2) This creates a conflict when a datastore does not support those calls. I am confused about your solution. Your suggestion

Re: [openstack-dev] [trove] scheduled tasks redux

2014-01-24 Thread Kevin Conway
Will we be doing more complex things than every day at some time? ie, does the user base see value in configuring backups every 12th day of every other month? I think this is easy to write the schedule code, but i fear that it will be hard to build a smarter scheduler that would only allow X

Re: [openstack-dev] [Trove] How users should specify a datastore type when creating an instance

2013-10-21 Thread Kevin Conway
What is the major motivation not to simply use a glance image named MySQL 5.5 or MongoDB 2.4? Wouldn't that give service providers all the flexibility they need for providing different types? For example, I could offer a simple MySQL image that creates a MySQL instance. If all my users use the