Re: [Openstack] Nexenta Driver proposal

[Yuriy Taraday]

Hello again, everyone.

We finally got our pass to integrate the driver with Essex release. What
should we do to target our blueprint to Essex release to pass through
feature freeze at essex-3?
We're going to provide code no later than Feb 15, so we'll have enough time
to be ready before code freeze at essex-4.
My guess is that our blueprint should be approved and targeted at essex-4,
can somebody do that?

Kind regards, Yuriy.



On Tue, Nov 15, 2011 at 21:58, Caitlin Bestler
wrote:

> Passing standard integration tests that shows an option dealing with a
> special installation has no adverse
> effect on a reference environment makes sense.
>
> It may be possible to support central test equipment in this case, but
> that will definitely not be the
> case for every possible enhancement. We probably need to also talk in
> terms of test scripts that
> come from the central team that you expect someone supporting an option to
> run on their own
> test equipment.
>
> How often would such a remote test be needed? After each nightly build
> might be a bit too often,
> and only once per release cycle might not be frequent enough.
>
>
> ___
> 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

Re: [Openstack] Nexenta Driver proposal

[Caitlin Bestler]

Passing standard integration tests that shows an option dealing with a special 
installation has no adverse
effect on a reference environment makes sense.

It may be possible to support central test equipment in this case, but that 
will definitely not be the
case for every possible enhancement. We probably need to also talk in terms of 
test scripts that
come from the central team that you expect someone supporting an option to run 
on their own
test equipment.

How often would such a remote test be needed? After each nightly build might be 
a bit too often,
and only once per release cycle might not be frequent enough.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nexenta Driver proposal

[Monty Taylor]

Hi!

A few thoughts here, purely from a dev-process and CI perspective. I'm
personally thrilled to have driver around that has a team of folks
supporting it - but for OpenStack that has a few specific meanings.

First of all, I'm not in charge, but I'm pretty certain that there is no
way to get this added for diablo. The only things being merged into the
stable/diablo branch are backported fixes from trunk... so I'd
definitely focus your efforts on essex in the master branch.

To get the code into essex, you'll need to submit the code as a patch
via gerrit: http://wiki.openstack.org/GerritWorkflow
When you are ready, you'll want to rebase and squash this into a single
commit on top of master. (it looks like it's a single commit in your
stable/diablo branch already, so you may be in good shape there)

Once you get it ready for master, there is the question of testing. The
CI team has been working with hooking in specialized hardware or
environments from vendors with needs into the OpenStack Jenkins. The
biggest needs we'll have here in order for this to be a first-class
citizen are:

- unittests for this code that can run in a normal x86-based ubuntu
cloud server
- a functional/integration test environment owned and operated by you
that is connected to and triggered by our jenkins on which versions of
openstack to be tested can be installed. I would expect this to be an
environment with solaris/nexenta and an installation of openstack
configured to use it.

We can totally work with you on figuring out how to integrate your
resources into our environment. As a starting place, check out how we're
doing this with our first bare-metal integration environment, which is a
set of machines provided by rackspace:

http://ci.openstack.org/jenkins.html#integration-testing

The specific steps don't need to look like that at all, but it might
give you a better idea of what we'll need to figure out how to get set up.

I don't think the integration environment needs to be a blocker to
getting stuff merged - after all, we're still working on getting that
for the mainline trunk - but ensuring that we've got unittests that are
runnable as part of our normal set of gating tests is essential, from my
point of view.

Thanks for the work so far!

Monty

On 11/14/2011 01:48 PM, Yuriy Taraday wrote:
> All driver code is stamped with Apache Public License 2.0. Is it
> compatible with OpenStack licensing model?
> Currently driver supports Diablo branch of Nova, but we're working on
> changes to make it work on master.
> This driver was developed and tested in tight cooperation with Nexenta
> team, and will be supported by Nexenta.
> 
> Kind regards, Yuriy.
> 
> PS: Lost CC to mail list in my previous message, sorry.
> 
> 2011/11/14 Diego Parrilla Santamaría
>  >
> 
> Thank you Yuriy, it sounds really interesting. You have our support
> to move, test and improve this code in order to integrate it with
> master branch of Essex (and backport it to Diablo if necessary) once
> you release the code under the Openstack licensing model.
> 
> It would be great if Nexenta supports this project too. Meanwhile,
> we will continue using the Solaris derivative version that also runs
> smoothly in the Nexenta Core Platform ;-)
> 
> Regards
> Diego
> 
> -- 
> Diego Parrilla
> *CEO*
> **www.stackops.com*
>  | * diego.parri...@stackops.com
>  | +34 649 94 43 29
> | skype:diegoparrilla*
> * 
> *
> 
> 
> 
> *
> 
>  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. 
> 

Re: [Openstack] Nexenta Driver proposal

[Yuriy Taraday]

All driver code is stamped with Apache Public License 2.0. Is it compatible
with OpenStack licensing model?
Currently driver supports Diablo branch of Nova, but we're working on
changes to make it work on master.
This driver was developed and tested in tight cooperation with Nexenta
team, and will be supported by Nexenta.

Kind regards, Yuriy.

PS: Lost CC to mail list in my previous message, sorry.

2011/11/14 Diego Parrilla Santamaría 

> Thank you Yuriy, it sounds really interesting. You have our support to
> move, test and improve this code in order to integrate it with master
> branch of Essex (and backport it to Diablo if necessary) once you release
> the code under the Openstack licensing model.
>
> It would be great if Nexenta supports this project too. Meanwhile, we will
> continue using the Solaris derivative version that also runs smoothly in
> the Nexenta Core Platform ;-)
>
> Regards
>  Diego
>
> --
> Diego Parrilla
> *CEO*
> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * 
> *
>
> *
>
>  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.
>
>
>
>
>
> 2011/11/14 Yuriy Taraday 
>
>> We already noted this version of Nexenta driver.
>> We found out number of points which proof that this version of driver is
>> better that modified Solaris driver:
>> 1). it connects to Nexenta through Nexenta API, not SSH.
>> It's faster, requires no extra overhead on both server and client sides.
>> 2). it uses Nexenta services, not Solaris system tools directly.
>>  This assures that NexentaStor is aware of all operations and authorizes
>> and accounts them accordingly. It is the recommended way to interact with
>> Nexenta.
>> 3). it supports snapshot operations.
>> The snapshotting is totally missing from Solaris driver. Our driver
>> supports it as much as it is possible.
>> 4). it provides better error handling.
>> All Nexenta-specific errors are wrapped in separate exception tree and
>> are handled accordingly.
>>
>> Our driver is well-tested and waits for the first production deployment.
>> We are ready to provide all necessary help and information on this.
>>
>> If you want to get some more details on it, you can attend this webinar:
>> https://www3.gotomeeting.com/register/389257862. We're open for
>> collaboration too.
>>
>> Kind regards, Yuriy.
>>
>>
>>
>> 2011/11/14 Diego Parrilla Santamaría > >
>>
>>> Hi all,
>>>
>>> we have modified the Solaris volume driver code to work with Nexenta
>>> Block Storage. Actually, we have succesfully deployed solutions with
>>> Nexenta and Nova already.
>>>
>>> You can check the code here:
>>>
>>> https://github.com/StackOps/nova/tree/stable/diablo
>>>
>>> So, we are happy to collaborate on this.
>>>
>>> Regards
>>> Diego
>>> --
>>> Diego Parrilla

Re: [Openstack] Nexenta Driver proposal

[Diego Parrilla Santamaría]

Hi all,

we have modified the Solaris volume driver code to work with Nexenta Block
Storage. Actually, we have succesfully deployed solutions with Nexenta and
Nova already.

You can check the code here:

https://github.com/StackOps/nova/tree/stable/diablo

So, we are happy to collaborate on this.

Regards
Diego
-- 
Diego Parrilla
*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* 
*

*

 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.



On Mon, Nov 14, 2011 at 12:31 PM, Yuriy Taraday  wrote:

> Hello.
>
> The Openstack block volume storage demands high reliability and management
> automation. This can be achieved with specialized storage solutions, but
> Openstack still lacks integration with this type of storage back-ends.
>
> We have created a blueprinton 
> new volume driver for Nova that uses Nexenta appliance as storage.
> Driver is finished and working with Diablo version of Nova.
>
> We’re looking forward to any comments and suggestions. We hope our code
> can eventually be merged into master development branch with our support.
>
> Kind regards, Yuriy.
>
> ___
> 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

[Openstack] Nexenta Driver proposal

[Yuriy Taraday]

Hello.

The Openstack block volume storage demands high reliability and management
automation. This can be achieved with specialized storage solutions, but
Openstack still lacks integration with this type of storage back-ends.

We have created a blueprint
on new volume driver
for Nova that uses Nexenta appliance as storage.
Driver is finished and working with Diablo version of Nova.

We’re looking forward to any comments and suggestions. We hope our code can
eventually be merged into master development branch with our support.

Kind regards, Yuriy.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp