Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Monty Taylor
On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very fact intensive. I was the chair of the User Committee in developing the GPLv3 and I am therefor quite familiar with the legal issues. The

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Mark McLoughlin
On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very fact intensive. I was the chair of the User Committee

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Sean Dague
On 03/20/2014 08:36 AM, Mark McLoughlin wrote: On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain and the determination of the consequences are very fact

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Chuck Thier
I agree this is quite an issue but I also think that pretending that we'll be able to let OpenStack grow with a minimum set of databases, brokers and web servers is a bit unrealistic. The set of supported technologies won't be able to fulfill the needs of all the yet-to-be-discovered

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Russell Bryant
On 03/20/2014 11:11 AM, Chuck Thier wrote: I agree this is quite an issue but I also think that pretending that we'll be able to let OpenStack grow with a minimum set of databases, brokers and web servers is a bit unrealistic. The set of supported technologies won't be able

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Kurt Griffiths
The incorporation of AGPLv3 code Into OpenStack Project is a significant decision To be clear, Marconi does not incorporate any AGPL code itself; pymongo is Apache2 licensed. Concerns over AGPL were raised when Marconi was incubated, and I totally respect that some folks are not comfortable

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Sean Dague
On 03/20/2014 12:29 PM, Kurt Griffiths wrote: The incorporation of AGPLv3 code Into OpenStack Project is a significant decision To be clear, Marconi does not incorporate any AGPL code itself; pymongo is Apache2 licensed. Concerns over AGPL were raised when Marconi was incubated, and I

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Vishvananda Ishaya
On Mar 20, 2014, at 5:52 AM, Sean Dague s...@dague.net wrote: On 03/20/2014 08:36 AM, Mark McLoughlin wrote: On Thu, 2014-03-20 at 12:07 +0100, Thierry Carrez wrote: Monty Taylor wrote: On 03/20/2014 01:30 AM, Radcliffe, Mark wrote: The problem with AGPL is that the scope is very uncertain

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Gil Yehuda
To be clear, Marconi does not incorporate any AGPL code itself; pymongo is Apache2 licensed. Understood, but here's the rub. Someone else is going to want to build on this (which it the point of this open source project). Whereas 'pymongo' is Apache licensed, since the copyright holder, MongoDB

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Stan Lagun
Kurt, Your point is that NoSQL solution may be required for innovative project. And that is MongoDB. But what if come another amazing project that needs CouchDB, neo4j, Riak, (put your favorite NoSQL DB here)? It would be in the same position cause everyone would say hey, we already have NoSQL in

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-20 Thread Amit Gandhi
If we limited Openstack projects to just one database, is that database (e.g. MySQL) going to be the best storage deployment for that job? Or are there cases where other technologies such as Redis, MongoDB, Cassandra, CouchDB, etc make more sense? Marconi has a pluggable storage driver model

Re: [openstack-dev] [legal-discuss] [Marconi] Why is marconi a queue implementation vs a provisioning API?

2014-03-19 Thread Monty Taylor
Ianal, but I know there are some lawyers out there who are concerned that the mechanism of attachment is vague. If there is an issue (I'm not saying there is) I don't think mongodb's view is relevant, as they are quite likely to be bought by someone, say Oracle, who might not share and would