Difference between revisions of "Network/Meetings"
(→Nova Parity (beagles)) |
|||
Line 57: | Line 57: | ||
** These milestones will need to be refined and it may be more clear to separate them into functional groups (i.e. parity-feature-tracking, tempest-parity-test, etc) | ** These milestones will need to be refined and it may be more clear to separate them into functional groups (i.e. parity-feature-tracking, tempest-parity-test, etc) | ||
** An immediate objective would be to round-up what has already been down so far as part of the excellent efforts being made to clean up the tests in the past two weeks | ** An immediate objective would be to round-up what has already been down so far as part of the excellent efforts being made to clean up the tests in the past two weeks | ||
+ | ** As it is relevant for some of the gate failures, I propose that we do a functional tear-down of the integration module (nova/network/neutronv2) starting today and revisit areas where there are differences in behavior, describe them and: | ||
+ | *** examine if the differences are parity-blockers and get "sign-off" by the nova team and whomever else is appropriate, | ||
+ | *** agree that the implementations are still the most appropriate. | ||
+ | ::either might make some of the gate-bug-hunting moot (e.g. the mulitple network thing) | ||
+ | |||
+ | * In addition to the above, there are some networking related operations available through nova that are not implemented "properly" (bulk floating ip operations) and may or may not be "mappable" to neutron. I intend to introduce them at the nova IRC meeting later this week and start the dialogue about how they want to handle them. If anybody is aware of specific issues of this sort that they would like me to include, please ping me via IRC or email before Thursday, 28-11-2013 0900 UTC and I'll get it in there. | ||
=== Neutron Tempest (mlavalle) === | === Neutron Tempest (mlavalle) === |
Revision as of 20:20, 25 November 2013