Open Stack

Javelin2 lives in tempest, currently the following additional fixes are
needed for it to pass the server & image creation in grenade -
https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:javelin_img_fix,n,z

Those were posted for review last Friday, need eyes on them. This is
still basically the minimum viable code there, and additional unit tests
should be added. Assistance there appreciated.

There is a grenade patch that will consume that once landed -
https://review.openstack.org/#/c/97317/ - local testing gets us to an
unrelated ceilometer bug. However landing the 2 tempest patches first
should be done.

Sorry this has been slow, I spent a lot of the last month trying to
debug some of the races we were exposing in the gate. So also more
assistance there would also be appreciated, as it frees time other places.

	-Sean

On 07/14/2014 12:35 PM, Chris Dent wrote:
> 
> A recent thread about javelin2[1] ended with "the takeaway here is
> that we should consider javelin2 still very much a WIP...we should be
> hesitant to add new features and functionality to it."
> 
> One of the items on my todo list is to add some functionality (for
> ceilometer[2]) to javelin2, therefore I'd like to help in whatever way to
> make it more mature and useful and move it along. To that end I have
> some questions:
> 
> * I understand that javelin2 is or will be run as part of Grenade.
>   Where (what code) do I look to see that integration? If it hasn't
>   happened yet, where will it happen?
> 
>   Will that integration be done as if javelin2 is part of a test suite
>   or will a bit of shell code be wrapping it and checking exit codes?
> 
> * Will grenade provide its own resources.yaml or is the plan to use
>   the one currently found in the tempest repo?
> 
> Basically I'd like to see this move along and I'm happy to do the leg
> work to make it so, but I need a bit of guidance on where to push.
> 
> Thanks.
> 
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2014-July/039078.html
> [2] The TC did some gap analysis and one of the areas that needs work
>     is in resource survivability.
> 


-- 
Sean Dague
http://dague.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 482 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140714/3f57a1ef/attachment.pgp>