Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Defect Milestone-Release2.12 Priority-Medium Component-rapi
New issue 969 by [email protected]: Remove manual RAPI parameter filtering
wherever possible
https://code.google.com/p/ganeti/issues/detail?id=969
RAPI's standard mode of method invocation is to supply some parameters
based on the URL used, and otherwise pass on all the parameters in the
request body.
Some RAPI methods do not do this, and instead hand-pick a small number of
arguments to be used. This is done partially because of some potential for
abuse due to specific instance opcode arguments which are filled in later
and badly verified (name / UUID), and partially because of some very
specific checks used for other values.
The problem with these special methods is that they make the RAPI interface
static, which could be a good thing if applied consistently to every part
of the system and tested correctly, but causes issues in this partial
state. E.g., the interfaces do not support all the standard Ganeti options
(dependencies, reason trails), and since 2.6, they were not maintained to
accept new options,
For the time being, the best option appears to be refactoring these methods
to bring them in line with the rest of RAPI. As this will be done on a
stable version, the refactoring should be done carefully to avoid breaking
the external interface.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
