openstack team mailing list archive

[Ghe Rivero <ghe.rivero@xxxxxxxxxxxx>]

I think is time (after essex release) to rethink the way plugins are
integrated into "mainline code". This problem, an outdated plugin, it's not
new  (Hyper-V), and with the increasing numbers of them (storage like
Zadara, Nexenta... network with Nicira, BigSwitch, Citrix...) we need a
policy to deal with this. From the vendor point of view, it's not easy to
follow the development release cycle that OpenStack has now days, with so
many changes day after day. Maybe plugins should be out of OpenStack code,
and let vendors to publish them after the release.

Ghe Rivero

On Thu, Mar 15, 2012 at 5:53 PM, Kevin L. Mitchell <
kevin.mitchell@xxxxxxxxxxxxx> wrote:

> On Thu, 2012-03-15 at 09:02 -0700, Vladimir Popovski wrote:
> > I was not aware of any issue with VSA code in diablo/stable (or at least
> > major issues).
>
> I'll point out that the code we're concerned about is the code in trunk,
> not the code in diablo/stable.  There have been substantial changes to
> the code since diablo was released, which has resulted in bitrot in the
> VSA code and the attendant breakages to which Vish is referring.
> --
> Kevin L. Mitchell <kevin.mitchell@xxxxxxxxxxxxx>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Ghe Rivero
*OpenStack & Distribution Engineer
**www.stackops.com | * ghe.rivero@xxxxxxxxxxxx <diego.parrilla@xxxxxxxxxxxx>
** | +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.