I would add that the Horizon team has been hard at work in the Essex release cycle to support this "ecosystem" concept as well. The Essex release has been completely re-architected for extensibility; any project can easily add their own dashboards, panels, etc. via reusable components. We'll be talking lots about that at the next summit.
Maintaining a solid "core" OpenStack is absolutely important, but it shouldn't be the bottleneck to successful projects. - Gabriel > -----Original Message----- > From: openstack-bounces+gabriel.hurley=nebula....@lists.launchpad.net > [mailto:openstack- > bounces+gabriel.hurley=nebula....@lists.launchpad.net] On Behalf Of > Jesse Andrews > Sent: Monday, February 06, 2012 10:13 AM > To: Oleg Gelbukh > Cc: openstack@lists.launchpad.net > Subject: Re: [Openstack] Atlas-LB - what's the project status? > > Hi Oleg, > > NOTE: this is my opinion - I do not speak for all of OpenStack! > > While our focus is on a successful Essex, the RCB team has started thinking > about Folsom. Our current thoughts is focusing on enabling an eco-system > **around** core. OpenStack shouldn't try to be IaaS, PaaS and SaaS - > instead a solid base to build these other systems on. > [1] > > OpenStack is about "Essential Infrastructure Services" (currently compute, > storage, network) and supporting tools/apis/docs. > Determining if LB is considered Infrastructure (vs. platform) and if it is > Essential (a fuzzy word - what is essential to one isn't essential to another) > > That said - regardless of whether Atlas land in core [2], my team wants to > add: > > * documentation/tutorials/examples about how to add a new (iaas or > paas) services to a cloud > * simple integration of LB service (for instance an optional devstack > component). > * an opensource backend for the LB service (haproxy, pound, ...) > > The thought is that an entire eco-system of components that plug into a > cloud is more powerful than having OpenStack "choose winners" that > become "core". [3] > > I look forward to conversations about LBaaS and the definition of OpenStack. > > Jesse Andrews > Rackspace Cloud Builders > > [1] the analogy I use is that the Apache Web Server doesn't try to be Django > or Rails, but instead be a great web server to run rails on top of. > [2] in addition to the question about if lbaas belongs in core, the incubation > process would need to be gone through > http://wiki.openstack.org/Governance/Approved/Incubation > [3] rather than blessing project X to be an official platform component, > enable many projects to run on top and let open source / market dynamics > determine winners. > > On Mon, Feb 6, 2012 at 9:48 AM, Oleg Gelbukh <ogelb...@mirantis.com> > wrote: > > Hello, everyone > > > > What is the status of this LBaaS project for the OpenStack? As far as > > I know, the open-source version is compatible with OpenStack. But is > > it possible to merge the Java code in the OpenStack ecosystem? Is > > someone working on re-implementing Atlas-LB in Python and eventually > > adding to the projects incubator, or there are some other lbaas projects > out there? > > > > Thanks in advance, > > > > -- > > Oleg Gelbukh > > Mirantis Inc. > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openstack Post to : > > openstack@lists.launchpad.net Unsubscribe : > > https://launchpad.net/~openstack More help : > > https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp