[openstack-dev] Pecan Evaluation for Marconi

Doug Hellmann doug.hellmann at dreamhost.com
Wed Mar 19 15:00:34 UTC 2014

On Wed, Mar 19, 2014 at 7:31 AM, Thierry Carrez <thierry at openstack.org>wrote:

> Kurt Griffiths wrote:
> > Kudos to Balaji for working so hard on this. I really appreciate his
> candid feedback on both frameworks.
> Indeed, that analysis is very much appreciated.
> From the Technical Committee perspective, we put a high weight on a
> factor that was not included in the report results: consistency and
> convergence between projects we commonly release in an integrated manner
> every 6 months. There was historically a lot of deviation, but as we add
> more projects that deviation is becoming more costly. We want developers
> to be able to jump from one project to another easily, and we want
> convergence from an operators perspective.

> Individual projects are obviously allowed to pick the best tool in their
> toolbox. But the TC may also decide to let projects live out of the
> "integrated release" if we feel they would add too much divergence in.

As Thierry points out, an important aspect of being in the integrated
release is being aligned with the rest of the community. The evaluation
gives "community" considerations the lowest weight among the criteria
considered. Does that ranking reflect the opinion of the entire Marconi
team? If so, what benefits do you see to being integrated?

The evaluation does not discuss any of the infrastructure tooling being
built up around OpenStack's use of Pecan. For example, what will Marconi do
for API documentation generation?

Pecan is currently gating changes against projects that use it, so we can
be sure that changes to the framework do not break our applications. This
does not appear to have been factored into the evaluation.

> > After reviewing the report below, I would recommend that Marconi
> > continue using Falcon for the v1.1 API and then re-evaluate Pecan for
> > v2.0 or possibly look at using swob.
> The report (and your email below) makes a compelling argument that
> Falcon is a better match for Marconi's needs (or for a data-plane API)
> than Pecan currently is. My question would be, can Pecan be improved to
> also cover Marconi's use case ? Could we have the best of both worlds
> (an appropriate tool *and* convergence) ?

We had several conversations with Kurt and Flavio in Hong Kong about
adding features to Pecan to support the Marconi team, and Ryan prototyped
some of those changes shortly after we returned home. Was any of that work
considered in the evaluation?


> If the answer is "yes, probably", then it might be an option to delay
> inclusion in the integrated release so that we don't add (even
> temporary) divergence. If the answer is "definitely no", then we'll have
> to choose between convergence and functionality.
> --
> Thierry Carrez (ttx)
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140319/4053350f/attachment.html>

More information about the OpenStack-dev mailing list