Open Stack

Kudos to Balaji for working so hard on this. I really appreciate his candid feedback on both frameworks.

After reviewing his report, I would recommend that Marconi continue using Falcon for the v1.1 API and then re-evaluate Pecan for v2.0. Pecan will continue to improve over time. We should also look for opportunities to contribute to the Pecan ecosystem.

Kurt G. | @kgriffs | Marconi PTL

From: Balaji Iyer <balaji.iyer at RACKSPACE.COM<mailto:balaji.iyer at RACKSPACE.COM>>
Reply-To: OpenStack Dev <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, March 18, 2014 at 11:55 AM
To: OpenStack Dev <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Marconi] Pecan Evaluation for Marconi

I work for Rackspace and Im fairly new to Openstack Ecosystem. Recently, I came across an opportunity to evaluate Pecan for Marconi and produce a comprehensive report. I have not worked with Pecan or Falcon prior to this evaluation, and have no vested interest in these two frameworks.

Evaluating frameworks is not always easy, but I have strived to cover as many details as applicable.  I have evaluated Pecan and Falcon only on how it fits Marconi and this should not be treated as a general evaluation for all products. It is always recommended to evaluate frameworks based on your product's requirements and its workload.

Benchmarking is not always easy, hence I have spent a good amount of time benchmarking these two frameworks using different tools and under different network and load conditions with Marconi. Some of the experiences I have mentioned in the report are very subjective and it narrates mine - you may have had a different experience with these frameworks, which is totally acceptable.

Full evaluation report is available here - https://wiki.openstack.org/wiki/Marconi/pecan-evaluation

Thought of sharing this with the community in the hope that someone may find this useful.

Thanks,
Balaji Iyer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140318/1e9af1f4/attachment.html>