Re: [openstack-dev] [Diesel] Proposal for new project
Hi Adrian, Jay and Raj Thanks for your responses on relationship between Solum and Diesel. It does sound like they are in the same domain. My feeling was that it was a very different approach where Solum was aimed at developer, Diesel was aimed at the cloud provider. In some companies these roles are not very different but in others they are completely different and may even work for different companies. I plan to start engaging in Solum project and see how this use model can be addressed or perhaps already is. Thanks, Rob Original message From: Jay Pipes [jaypipes at gmail.com] Sent: Saturday, January 18, 2014 12:15 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Diesel] Proposal for new project Perhaps I'm just missing something, though, so perhaps you might elaboraste? Best, -jay smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
On 01/21/2014 11:31 AM, Raymond, Rob wrote: Hi Adrian, Jay and Raj Thanks for your responses on relationship between Solum and Diesel. It does sound like they are in the same domain. My feeling was that it was a very different approach where Solum was aimed at developer, Diesel was aimed at the cloud provider. In some companies these roles are not very different but in others they are completely different and may even work for different companies. I plan to start engaging in Solum project and see how this use model can be addressed or perhaps already is. My impression is that Solum is certainly intended to be something that a provider could run. It's a service, not just a set of client tools. -- Russell Bryant ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
Diesel seems to be a subset of what Solum delivers. For reference: Solum Wiki: https://wiki.openstack.org/wiki/Solum Solum Roadmap: https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap We should discuss combining efforts instead of duplicating initiatives. From: Jay Pipes [jaypi...@gmail.com] Sent: Saturday, January 18, 2014 12:15 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Diesel] Proposal for new project On Sat, 2014-01-18 at 03:31 +, Raymond, Rob wrote: I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Hi Rob, So I've read through the above wiki page a couple times, and I'm really having trouble understanding how Diesel differs from Solum. In the wiki page, you mention: Solum - Solum is focused on the development lifecycle for the application. The application may be one that Diesel can run. Could you elaborate on how you envision how Diesel differs from Solum in its basic intent? Solum deploys applications into a cloud. Diesel is intended to run applications in clouds, but I'm not sure how there is a difference between deploying an application into a cloud and running one. Perhaps I'm just missing something, though, so perhaps you might elaboraste? Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
Rob, Please contact me, You have completely misunderstood the Solum project. Thanks, Adrian On Jan 17, 2014, at 9:31 PM, Raymond, Rob rob.raym...@hp.com wrote: Hi Raj As I see it, Solum is a set of utilities aimed at developers to use OpenStack clouds but will not be part of OpenStack proper. While Diesel is meant to be a service that is provided by an OpenStack cloud (and at some point becoming part of OpenStack itself). It defines a contract and division of responsibility between developer and cloud. Rob Original message From: Rajesh Ramchandani Date:01/17/2014 8:04 PM (GMT-08:00) To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-dev at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Subject: Re: [openstack-dev] [Diesel] Proposal for new project Hi Rob - there seems be overlap with project Solum. Can you please outline high level differences between Diesel and Solum? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
On Sat, 2014-01-18 at 03:31 +, Raymond, Rob wrote: I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Hi Rob, So I've read through the above wiki page a couple times, and I'm really having trouble understanding how Diesel differs from Solum. In the wiki page, you mention: Solum - Solum is focused on the development lifecycle for the application. The application may be one that Diesel can run. Could you elaborate on how you envision how Diesel differs from Solum in its basic intent? Solum deploys applications into a cloud. Diesel is intended to run applications in clouds, but I'm not sure how there is a difference between deploying an application into a cloud and running one. Perhaps I'm just missing something, though, so perhaps you might elaboraste? Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Diesel] Proposal for new project
I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Please send me email if you would like to collaborate on this and I can set up an IRC meeting. Rob Raymond ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
Hi Rob - there seems be overlap with project Solum. Can you please outline high level differences between Diesel and Solum? Raj Sent from my iPad On Jan 18, 2014, at 9:06 AM, Raymond, Rob rob.raym...@hp.com wrote: I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Please send me email if you would like to collaborate on this and I can set up an IRC meeting. Rob Raymond ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
Please discuss this with the Solum team before proceeding. This sounds like a complete overlap with the app deployment portion of Solum. It would make much more sense to combine efforts than to run this as two projects. -- Adrian Original message From: Rajesh Ramchandani Date:01/17/2014 8:04 PM (GMT-08:00) To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Diesel] Proposal for new project Hi Rob - there seems be overlap with project Solum. Can you please outline high level differences between Diesel and Solum? Raj Sent from my iPad On Jan 18, 2014, at 9:06 AM, Raymond, Rob rob.raym...@hp.com wrote: I would like to gauge interest in a new project named Diesel. https://wiki.openstack.org/wiki/Diesel If you are already familiar with Savanna, the best way to describe it is: Savanna is to map reduce applications as Diesel is to web applications. The mission of Diesel is to allow OpenStack clouds to run applications. The cloud administrator can control the non functional aspects, freeing up the application developer to focus on their application and its functionality. In the spirit of Google App Engine, Heroku, Engine Yard and others, Diesel runs web applications in the cloud. It can be used by cloud administrators to define the application types that they support. They are also responsible for defining through Diesel how these applications run on top of their cloud infrastructure. Diesel will control the availability and scalability of the web application deployment. Please send me email if you would like to collaborate on this and I can set up an IRC meeting. Rob Raymond ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Diesel] Proposal for new project
Hi Raj As I see it, Solum is a set of utilities aimed at developers to use OpenStack clouds but will not be part of OpenStack proper. While Diesel is meant to be a service that is provided by an OpenStack cloud (and at some point becoming part of OpenStack itself). It defines a contract and division of responsibility between developer and cloud. Rob Original message From: Rajesh Ramchandani Date:01/17/2014 8:04 PM (GMT-08:00) To: OpenStack Development Mailing List (not for usage questions) Cc: openstack-dev at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Subject: Re: [openstack-dev] [Diesel] Proposal for new project Hi Rob - there seems be overlap with project Solum. Can you please outline high level differences between Diesel and Solum? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
