Hi guys,

We (CloudFounders) have been working on developing a storage solution
that we want to integrate in OpenStack (we will release the software
component as open source).

>From what i saw in the mailing list here we missed the Juno release so
i guess we'll have to wait until Kilo.

The status of the "integration" is currently:

- driver: minimal functionality required for J (95%, small issues with

- unit testing and automated testing: covered minimal functionality,
validation on backend (failing test for upload)

- certification tests: passing, except 4 tests for upload

- cinder unit tests and integration tests: passing

- blueprint/specs: in progress

- third-party CI: almost complete

- company CLA and user CLA: almost complete

Now for some questions:

- first, did i miss anything in the "checklist" above?

- once functionality is complete and tests are passing, the next steps
are to create the blueprint and create a blueprint topic branch and
get the code reviewed? or is there something else required first?

- should we include also the automated tests in the code commit? (we
have tests that setup the backend and require our software component
to be installed, this wouldn't make sense to run on other setups since
all tests would be failing due to missing dependencies)

The code is available at the moment on a bitbucket repo but we're
moving to github as soon as possible.



*Eduard Biceri Mate, Senior Software Developer*
 | eduard.ma...@cloudfounders.com

*CloudFounders, The Private Cloud Software Company*

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
If you are not the named addressee or an employee or agent responsible
for delivering this message to the named addressee, you are hereby
notified that you are not authorized to read, print, retain, copy or
disseminate this message or any part of it. If you have received this
email in error we request you to notify us by reply e-mail and to
delete all electronic files of the message. If you are not the
intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the content of this
message, and shall have no liability for any loss or damage suffered
by the user, which arise as a result of e-mail transmission.
OpenStack-dev mailing list

Reply via email to