Open Stack

Hi Ghe,



I suppose it will be very useful. We are planning to create a new project
for nova-volumes (cider?) and I’m sure it will have same duplicate classes.

Sooner we will have a common openstack layer is better.



Regards,

-Vladimir







*From:* openstack-bounces+vladimir=zadarastorage.com at lists.launchpad.net[mailto:
openstack-bounces+vladimir=zadarastorage.com at lists.launchpad.net] *On
Behalf Of *Ghe Rivero
*Sent:* Tuesday, April 24, 2012 7:28 AM
*To:* Mark McLoughlin
*Cc:* openstack
*Subject:* Re: [Openstack] wsgi code duplication





On Tue, Apr 24, 2012 at 2:40 PM, Mark McLoughlin <markmc at redhat.com> wrote:

Hi Ghe,


On Tue, 2012-04-24 at 12:15 +0200, Ghe Rivero wrote:
> Hi Everyone,
>    i've been looking through wsgi code, and i have found a lot of
> duplicated code between all the projects.

Thanks for looking into this. It sounds quite daunting.

I wonder could we do this iteratively by extract the code which is most
common into openstack-common, move the projects over to that and then
start again on the next layer?

Cheers,
Mark.



I have plans to try to move as much as possible into openstack-common. I
will start with nova as a test bed and see what we get from there. My
future plans include db code and tests (in the case of quantum, plugins
test also have a lot of duplicated code).

I register a bp for the wsgi issue:
https://blueprints.launchpad.net/openstack-common/+spec/wsgi-common



Ghe Rivero






-- 

Ghe Rivero
*OpenStack & Distribution Engineer
www.stackops.com | * ghe.rivero at stackops.com
<diego.parrilla at stackops.com> | +34
625 63 45 23 | skype:ghe.rivero*
* <http://www.stackops.com/>

****

******************** ADVERTENCIA LEGAL ********************
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

***************** PRIVILEGED AND CONFIDENTIAL ****************
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120424/26e71f7d/attachment.html>