<div dir="ltr"><div style>I put it here </div><a href="https://etherpad.openstack.org/gate-tempest-devstack-vm-quantum-full">https://etherpad.openstack.org/gate-tempest-devstack-vm-quantum-full</a><br><div><br></div><div style>
Ala</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/19 Miguel Lavalle <span dir="ltr"><<a href="mailto:miguel@mlavalle.com" target="_blank">miguel@mlavalle.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">No, we haven't put this document in etherpad. But it's a great idea. This way other folks can jump in with ideas. I'll put it up in eteherpad over the next few days<br></div><div class="HOEnZb">
<div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 10:10 AM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is great stuff! You guys have this up in etherpad somewhere?<br>
<br>
Really great to see people organizing around this. I'd reviewed a bunch of Jordan's code, so I knew he was in the mix, sorry for not realizing there were other folks working on this as well.<br>
<br>
-Sean<div><div><br>
<br>
On 06/19/2013 10:27 AM, Miguel Lavalle wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
Hi,<br>
<br>
As of last week, we have organized a team to deal with the Quantum in<br>
full gate issues. There are 3 people working on this: Jordan Pittier,<br>
Ala.Rezmerita and myself. Below you will find a document describing all<br>
the identified issues and who is assigned to fix them. Of cource, we can<br>
use more hands / heads. If anyone wants to help or has identified other<br>
issues not listed below, please get in touch with us.<br>
<br>
Regards<br>
<br>
Fix Jenkins gate-tempest-devstack-vm-<u></u>quantum-full<br>
<br>
<br>
This document lists all the Tempest tests that are failing on a Devstack<br>
+ Quantum Trunk setup. The goal is to make these tests pass for the<br>
Havana Milestone 3. Alla, Miguel and Jordan are working on this.<br>
<br>
<br>
For each test :<br>
<br>
*<br>
<br>
Provide the full path of the test. If the test has a double<br>
interface (JSON and XML), it’s enough to provide only the JSON path.<br>
<br>
*<br>
<br>
Provide a small stacktrace or a link to a Paste service such as<br>
<a href="http://paste.openstack.org/" target="_blank">http://paste.openstack.org/</a><br>
<br>
*<br>
<br>
Would be great to provide the CURL URL that triggers the bug<br>
<br>
*<br>
<br>
Provide a small analysis of what the bug may be and the components<br>
involved (Quantum, Quantum API on Nova’s side, Nova-network etc.)<br>
<br>
*<br>
<br>
As far as possible, provide the file and the line number where the<br>
Python exception is raised or translated (“casted”)<br>
<br>
*<br>
<br>
If already filed, an URL to the bug report in Launchpad<br>
<br>
<br>
Tests related to the Fixed IPs Compute API extension (Miguel)<br>
<br>
<br>
1)<br>
tempest.api.compute.admin.<u></u>test_fixed_ips:<u></u>FixedIPsTestJson.test_list_<u></u>fixed_ip_details<br>
<br></div></div>
*<br>
<br>
Trace: <a href="http://paste.openstack.org/show/38363/" target="_blank">http://paste.openstack.org/<u></u>show/38363/</a><br>
<br>
*<br>
<br>
curl-H "X-Auth-Token:$TOKEN" -X GET<br>
http://$IP:8774/v2/$TENANT_ID/<u></u>os-fixed-ips/<a href="http://10.0.0.3" target="_blank">10.0.0.3</a> <<a href="http://10.0.0.3" target="_blank">http://10.0.0.3</a>><br>
<br>
*<br>
<br>
API: <a href="http://api.openstack.org/api-ref.html#ext-os-fixed-ips" target="_blank">http://api.openstack.org/api-<u></u>ref.html#ext-os-fixed-ips</a><div><br>
<br>
*<br>
<br>
Explanation: Call to<br>
nova.api.openstack.compute.<u></u>contrib.fixed_ips.<u></u>FixedIPController::show()<br>
This file doesn’t use the Quantum API nor the Nova-Network API. It<br>
interacts directly with the DB, which is bad.<br>
<br>
*<br>
<br>
A possible fix would be to :<br>
<br></div>
1.<div><br>
<br>
Change<br>
nova.api.openstack.compute.<u></u>contrib.fixed_ips.<u></u>FixedIPController::show()<br>
to use either nova.network.api.API::get_<u></u>fixed_ip() (for Nova<br>
Network) or nova.network.quantumv2.api.<u></u>API:get_fixed_ip() (for<br>
Nova Network)<br>
<br></div>
2.<div><br>
<br>
Implement nova.network.quantumv2.api.<u></u>API:get_fixed_ip() which<br>
currently raises a NotImplementedError exception<br>
<br>
2)<br>
tempest.api.compute.admin.<u></u>test_fixed_ips:<u></u>FixedIPsTestJson.test_set_<u></u>reserve<br>
<br></div>
*<br>
<br>
Trace: <a href="http://paste.openstack.org/show/38372/" target="_blank">http://paste.openstack.org/<u></u>show/38372/</a><br>
<br>
*<br>
<br>
curl-H "X-Auth-Token:$TOKEN" -X POST<br>
http://$IP:8774/v2/$TENANT_ID/<u></u>os-fixed-ips/<a href="http://10.0.0.3/action" target="_blank">10.0.0.3/action</a><br>
<<a href="http://10.0.0.3/action" target="_blank">http://10.0.0.3/action</a>><br>
<br>
*<br>
<br>
API: <a href="http://api.openstack.org/api-ref.html#ext-os-fixed-ips" target="_blank">http://api.openstack.org/api-<u></u>ref.html#ext-os-fixed-ips</a><div><br>
<br>
*<br>
<br>
Possible Fix: Should call<br>
nova.api.openstack.compute.<u></u>contrib.fixed_ips.<u></u>FixedIPController::_set_<u></u>reserved()<br>
(once the result of db.fixed_ip_get_by_address() is made through the<br>
API). Here the problem is that neither Nova-Network nor Quatum API<br>
implement an equivalent of db.fixed_ip_update()<br>
<br>
3)<br>
tempest.api.compute.admin.<u></u>test_fixed_ips:<u></u>FixedIPsTestJson.test_set_<u></u>unreserve<br>
<br>
*<br>
<br>
Same as 2)<br>
<br>
<br>
<br>
Tests related to Quotas Admin(Miguel)<br>
<br>
<br>
4)tempest.api.compute.admin.<u></u>test_quotas:<u></u>QuotasAdminTestJSON.test_<u></u>security_groups_exceed_limit<br>
<br>
5)tempest.api.compute.admin.<u></u>test_quotas:<u></u>QuotasAdminTestJSON.test_<u></u>security_groups_rules_exceed_<u></u>limit<br>
<br>
<br>
Tests related to Floating IPs<br>
<br>
<br>
6)tempest.api.compute.<u></u>floating_ips.test_floating_<u></u>ips_actions:<u></u>FloatingIPsTestJSON.test_<u></u>associate_ip_to_server_<u></u>without_passing_floating_ip<br>
<br></div>
*<br>
<br>
Trace Tempest <a href="http://paste.openstack.org/show/38431/" target="_blank">http://paste.openstack.org/<u></u>show/38431/</a><br>
<br>
*<br>
<br>
Bug : <a href="https://bugs.launchpad.net/quantum/+bug/1190242" target="_blank">https://bugs.launchpad.net/<u></u>quantum/+bug/1190242</a><br>
<br>
*<br>
<br>
curl-H "Content-Type: application/json" -H "X-Auth-Token:$TOKEN" -X<br>
POST http://$IP:8774/v2/$TENANT_ID/<u></u>servers/$SERVER_ID/action<br>
<<a href="http://10.1.59.157:8774/v2/de6c5fbc55a34cbcaa3d79eb6b21a784/servers/0b2ad3b6-c14a-4d89-b2a0-c015f0a88a1f/action" target="_blank">http://10.1.59.157:8774/v2/<u></u>de6c5fbc55a34cbcaa3d79eb6b21a7<u></u>84/servers/0b2ad3b6-c14a-4d89-<u></u>b2a0-c015f0a88a1f/action</a>>-d<br>
‘{"addFloatingIp": {"address": ""}}’<div><br>
<br>
*<br>
<br>
Notice that the address of the FloatingIP is empty.<br>
<br></div>
*<br>
<br>
API : <a href="http://api.openstack.org/api-ref.html#ext-floating-ips" target="_blank">http://api.openstack.org/api-<u></u>ref.html#ext-floating-ips</a><div><br>
<br>
*<br>
<br>
Explanation : Mismatch in the 2 API. If there is only one IP in the<br>
pool, Quantum allows the floating IP to be empty and returns the one<br>
and only IP in the pool. Nova-network doesn’t allow this and returns<br>
a 404<br>
<br>
*<br>
<br>
Review <a href="https://review.openstack.org/#/c/32740/" target="_blank">https://review.openstack.org/#<u></u>/c/32740/</a><br>
<br>
<br>
7)tempest.api.compute.<u></u>floating_ips.test_floating_<u></u>ips_actions:<u></u>FloatingIPsTestJSON.test_<u></u>delete_floating_ip<br>
<br></div>
*<br>
<br>
Trace Tempest : <a href="http://paste.openstack.org/show/38505/" target="_blank">http://paste.openstack.org/<u></u>show/38505/</a><br>
<br>
*<br>
<br>
Bug : <a href="https://bugs.launchpad.net/tempest/+bug/1160309(see" target="_blank">https://bugs.launchpad.net/<u></u>tempest/+bug/1160309(see</a> comment #2)<div><br>
<br>
*<br>
<br>
This is related to bug 9)<br>
<br>
<br>
8)tempest.api.compute.<u></u>floating_ips.test_floating_<u></u>ips_actions:<u></u>FloatingIPsTestJSON.test_<u></u>delete_nonexistant_floating_ip<br>
<br>
<br>
*<br>
<br>
Related to 9)<br>
<br>
<br>
9)tempest.api.compute.<u></u>floating_ips.test_list_<u></u>floating_ips:<u></u>FloatingIPDetailsTestJSON.<u></u>test_get_nonexistant_floating_<u></u>ip_details<br>
<br></div>
*<br>
<br>
Bug :<a href="https://bugs.launchpad.net/tempest/+bug/1160309" target="_blank">https://bugs.launchpad.net/<u></u>tempest/+bug/1160309</a><br>
<br>
*<br>
<br>
Trace tempest:<a href="http://paste.openstack.org/show/38430/" target="_blank">http://paste.<u></u>openstack.org/show/38430/</a><br>
<br>
*<br>
<br>
Trace nova: <a href="http://paste.openstack.org/show/38433/" target="_blank">http://paste.openstack.org/<u></u>show/38433/</a><div><br>
<br>
*<br>
<br>
Curl:curl -H "X-Auth-Token:$TOKEN" -X GET<br>
http://$IP:8774/v2/$PROJECT_<u></u>ID/os-floating-ips/<u></u>99987878787878<br>
<br>
Proposed Fix: <a href="https://review.openstack.org/33024" target="_blank">https://review.openstack.org/<u></u>33024</a><br>
<br>
<br>
Tests Related to Security Groups (Jordan)<br>
<br>
<br>
10)tempest.api.compute.<u></u>security_groups.test_security_<u></u>group_rules:<u></u>SecurityGroupRulesTestJSON.<u></u>test_security_group_rules_<u></u>create_with_invalid_id<br>
<br></div>
*<br>
<br>
TRACE: <a href="http://paste.openstack.org/show/38373/" target="_blank">http://paste.openstack.org/<u></u>show/38373/</a><br>
<br>
*<br>
<br>
curl-H "Content-Type: application/json" -H "X-Auth-Token:$TOKEN" -X<div><br>
POST http://$IP:8774/v2/$TENANT_ID/<u></u>os-security-group-rules -d<br>
‘{"security_group_rule": {"from_port": 22, "ip_protocol": "tcp",<br>
"to_port": 22, "parent_group_id": "9991393497170", "cidr": null,<br>
"group_id": null}}’<br>
<br>
*<br>
<br>
Explanation: Notice that the parent_goup_id is a numerical ID and<br>
not a UUID. Quantum has an additional check to validate that the ID<br>
is an UUID (see<br>
nova/network/security_group/<u></u>quantum_driver.py::validate_<u></u>id())<br>
<br></div>
*<br>
<br>
API: <a href="http://api.openstack.org/api-ref.html#ext-os-security-groups" target="_blank">http://api.openstack.org/api-<u></u>ref.html#ext-os-security-<u></u>groups</a><br>
<br>
*<br>
<br>
Bug: <a href="https://bugs.launchpad.net/tempest/+bug/1182384" target="_blank">https://bugs.launchpad.net/<u></u>tempest/+bug/1182384</a><div><br>
<br>
*<br>
<br>
Review: <a href="https://review.openstack.org/#/c/29899/" target="_blank">https://review.openstack.org/#<u></u>/c/29899/</a><br>
<br>
<br>
11)tempest.api.compute.<u></u>security_groups.test_security_<u></u>group_rules:<u></u>SecurityGroupRulesTestJSON.<u></u>test_security_group_rules_<u></u>delete_with_invalid_id<br>
<br></div>
*<br>
<br>
<a href="http://paste.openstack.org/show/38424/" target="_blank">http://paste.openstack.org/<u></u>show/38424/</a><div><br>
<br>
*<br>
<br>
curl -H "X-Auth-Token:$TOKEN" -X DELETE<br>
http://$IP:8774/v2$TENANT_ID/<u></u>os-security-group-rules/<u></u>9991407551273<br>
<br>
*<br>
<br>
Explanation : Same bug as 10<br>
<br></div>
*<br>
<br>
API: <a href="http://api.openstack.org/api-ref.html#ext-os-security-groups" target="_blank">http://api.openstack.org/api-<u></u>ref.html#ext-os-security-<u></u>groups</a><div><br>
<br>
*<br>
<br>
Review: <a href="https://review.openstack.org/#/c/29899/" target="_blank">https://review.openstack.org/#<u></u>/c/29899/</a><br>
<br>
12)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_delete_nonexistant_<u></u>security_group<br>
<br></div>
*<br>
<br>
Same as bug 10<div><br>
<br>
*<br>
<br>
Review: <a href="https://review.openstack.org/#/c/29899/" target="_blank">https://review.openstack.org/#<u></u>/c/29899/</a><br>
<br>
<br>
13)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_security_group_get_<u></u>nonexistant_group<br>
<br></div>
*<br>
<br>
Same as bug 10<div><br>
<br>
*<br>
<br>
Review: <a href="https://review.openstack.org/#/c/29899/" target="_blank">https://review.openstack.org/#<u></u>/c/29899/</a><br>
<br>
<br>
14)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_security_group_create_<u></u>with_duplicate_name<br>
<br>
Security Group with duplicate name should not be created, but two groups<br>
with the same name can be created in quantum. We have here the same<br>
problem as in 15 and in 16. With Quantum, there is no validation that a<br>
group with given name exists already or if the given SG name is empty<br>
or is composed of white spaces or is more than 255 chars.<br>
<br>
<br>
In the description of bug<br>
</div><a href="https://bugs.launchpad.net/nova/+bug/1161411this" target="_blank">https://bugs.launchpad.net/<u></u>nova/+bug/1161411this</a> issue is generally<div><br>
discussed. SecurityGroup API are based on the ID and not the names,<br>
except for adding an instance to a security group. In order to solve<br>
the last problem the bug <a href="https://bugs.launchpad.net/nova/+bug/1161473was" target="_blank">https://bugs.launchpad.net/<u></u>nova/+bug/1161473was</a><br>
added.<br>
<br>
<br>
The major question is if these 3 tests (14, 15, 16) : does the name of a<br>
security group is really that important? If so, we must add some<br>
validation methods. If not the test suit concerning this part must be<br>
disable in tempest. What do you think Miguel?<br>
<br>
<br>
<br>
15)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_security_group_create_<u></u>with_invalid_group_description<br>
<br>
16)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_security_group_create_<u></u>with_invalid_group_name<br>
<br>
BUG:<a href="https://bugs.launchpad.net/nova/+bug/1161411+" target="_blank">https://bugs.launchpad.<u></u>net/nova/+bug/1161411+</a><br>
<a href="https://bugs.launchpad.net/nova/+bug/1161473" target="_blank">https://bugs.launchpad.net/<u></u>nova/+bug/1161473</a><br>
<br>
Traceback(tempest) :<a href="http://paste.openstack.org/show/38423/" target="_blank">http://paste.openstack.org/<u></u>show/38423/</a><br>
<br>
The Security Group should not be created with group name an empty string<br>
or with white spaces/chars more than 255<br>
<br>
CURL:curl -H "Content-Type: application/json" -H "X-Auth-Token:$TOKEN"<br>
-X POST http://$IP:8774/v2/$PROJECT_<u></u>ID/os-security-groups -d<br>
'{"security_group": {"name": " ", "description":<br>
"description-1554950088"}}'<br>
<br>
curl -H "Content-Type: application/json" -H "X-Auth-Token:$TOKEN" -X<br>
POST http://$IP:8774/v2/$PROJECT_<u></u>ID/os-security-groups -d<br>
'{"security_group": {"name": " ", "description":<br>
"description-1554950088"}}'<br>
<br>
<br>
17)tempest.api.compute.<u></u>security_groups.test_security_<u></u>groups:SecurityGroupsTestJSON.<u></u>test_server_security_groups<br>
<br></div>
*<br>
<br>
Tempest Trace : <a href="http://paste.openstack.org/show/38427/" target="_blank">http://paste.openstack.org/<u></u>show/38427/</a><br>
<br>
*<br>
<br>
Fixed by <a href="https://review.openstack.org/#/c/32288/(merged" target="_blank">https://review.openstack.org/#<u></u>/c/32288/(merged</a> on June,12th)<div><br>
<br>
<br>
<br>
Tests related to servers(Ala)<br>
<br>
<br>
18)tempest.api.compute.<u></u>servers.test_list_server_<u></u>filters:<u></u>ListServerFiltersTestXML.test_<u></u>list_servers_filtered_by_ip_<u></u>regex<br>
<br></div>
*<br>
<br>
BUG: <a href="https://bugs.launchpad.net/quantum/+bug/1182883" target="_blank">https://bugs.launchpad.net/<u></u>quantum/+bug/1182883</a><br>
<br>
*<br>
<br>
BP: <a href="https://blueprints.launchpad.net/quantum/+spec/like-op-list" target="_blank">https://blueprints.launchpad.<u></u>net/quantum/+spec/like-op-list</a><div><br>
<br>
*<br>
<br>
CURL : GET http://$IP:8774/v2/$PROJECT_<u></u>ID/servers?ip=10.<br>
<br>
*<br>
<br>
Explanation: The regex search is not supported by Quantum. Thus<br>
Quantum returns a 404 Not Found (0 server match) where Tempest<br>
expects one server to be found.<br>
<br>
*<br>
<br>
Possible Fix : For "search port by IP with regex" feature, I think<br>
the best place to hack it would be in file<br>
quantum/db/db_base_plugin_v2.<u></u>py::_get_ports_query()<br>
<br>
<br>
19)tempest.api.compute.<u></u>servers.test_servers_negative:<u></u>ServersNegativeTest.test_<u></u>create_with_nonexistent_<u></u>security_group<br>
<br>
FIXED : <a href="https://review.openstack.org/#/c/30271/" target="_blank">https://review.openstack.org/#<u></u>/c/30271/</a><br>
<br>
<br>
20)tempest.api.compute.<u></u>servers.test_virtual_<u></u>interfaces:<u></u>VirtualInterfacesTestXML.test_<u></u>list_virtual_interfaces<br>
<br></div>
*<br>
<br>
TRACE (NOVA): <a href="http://paste.openstack.org/show/38371/" target="_blank">http://paste.openstack.org/<u></u>show/38371/</a><br>
<br>
*<br>
<br>
BUG: <a href="https://bugs.launchpad.net/tempest/+bug/1183436" target="_blank">https://bugs.launchpad.net/<u></u>tempest/+bug/1183436</a><div><br>
<br>
*<br>
<br>
CURL: GET<br>
http://$IP:8774/v2/$PROJECT_<u></u>ID/servers/$SERVER/os-virtual-<u></u>interfaces<br>
<br>
*<br>
<br>
Explanation: This HTTP request calls the Quantum API<br>
(nova/nova/network/quantumv2/<u></u>api.py) and specifically the<br>
get_vifs_by_* methods which are not implemented (raise<br>
NotImplementedError())<br>
<br></div>
*<br>
<br>
Possible Fix:<div><br>
<br>
o<br>
<br>
skip this test if Quantum is enabled as set in Tempest<br>
configuration. Or<br>
<br>
o<br>
<br>
Implement the get_vifs_by_* methods<br>
<br>
PATCH: (still not approved) <a href="https://review.openstack.org/#/c/31755/" target="_blank">https://review.openstack.org/#<u></u>/c/31755/</a><br>
<br>
<br>
On Tue, Jun 18, 2013 at 5:56 PM, Sean Dague <<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a><br></div><div><div>
<mailto:<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>>> wrote:<br>
<br>
On 06/18/2013 03:32 PM, Monty Taylor wrote:<br>
<br>
<br>
<br>
On 06/18/2013 03:14 PM, David Ripton wrote:<br>
<br>
On 06/18/2013 12:43 PM, Martina Kollarova wrote:<br>
<br>
Jenkins keeps running all the tests, even if the basic<br>
pep8 test fails,<br>
and runs all of the (very slow) Tempest Quantum tests,<br>
even though<br>
almost all of them are failing.<br>
<br>
I propose that it should fail and stop all of the other<br>
tests once there<br>
is a failure in a voting test. For non-voting tests, it<br>
should stop only<br>
itself, not the others.<br>
<br>
This would decrease the feedback loop and we wouldn't<br>
have to wait for<br>
the non-voting Quantum tests to see that they failed as<br>
always.<br>
<br>
<br>
-1<br>
<br>
In addition to the other objections, we currently get a lot<br>
of false<br>
positives (fail, retry, fail, retry, succeed), and it would<br>
be harder to<br>
debug these problems if the output was truncated differently<br>
each time.<br>
<br>
Is anyone working on fixing the perma-failing Quantum test?<br>
When the<br>
Postgres test was perma-failing, one of the infrastructure<br>
folks gave us<br>
an ultimatum that if nobody fixed it soon, it would be<br>
disabled. (Happy<br>
ending: Mauro fixed it before it got disabled.)<br>
<br>
<br>
That was brought up a little while ago, but we had already spent<br>
so much<br>
effort to get it working in the first place, none of us had the<br>
heart to<br>
put in such an ultimatum. But seriously- it might be time for an<br>
all-hands-on-deck dogpile to figure out what's up the the<br>
quantum gate.<br>
<br>
<br>
The biggest cause of the Quantum vs. Full Tempest runs is that a lot<br>
of the network api's in nova currently don't do translation of<br>
errors. So under nova-network certain data validation and error<br>
codes are returned, when quantum is used others are returned.<br>
<br>
This is a nova-api, so it needs to be consistent regardless of<br>
backend (i.e. we don't return different API responses on different<br>
databases).<br>
<br>
Issues like this one -<br></div></div>
<a href="https://bugs.launchpad.net/__nova/+bug/1160309" target="_blank">https://bugs.launchpad.net/__<u></u>nova/+bug/1160309</a><div><br>
<<a href="https://bugs.launchpad.net/nova/+bug/1160309" target="_blank">https://bugs.launchpad.net/<u></u>nova/+bug/1160309</a>><br>
<br>
Jordan Pittier has been working on some of these issues (he's the<br>
only one I've seen working them from a Tempest / nova side), and got<br>
to the crux of the problem. It could use more hands though to<br>
organize the rest of those and get them banged out.<br>
<br>
I'm sure there are other issues once we get past this class. But<br>
that would go a long way.<br>
<br>
-Sean<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br></div>
______________________________<u></u>___________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.<u></u>__org<br>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><div>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</div></blockquote><div><div>
<br>
<br>
-- <br>
Sean Dague<br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div style="color:rgb(136,136,136)">Ala Rezmerita<br></div><div style="color:rgb(136,136,136)">Ingénieur </div><div style="color:rgb(136,136,136)">
CloudWatt</div><div style="color:rgb(136,136,136)">Tel : 06 77 43 23 91</div></div>
</div>