Hi all,
Here's another "resurrecting" email thread, after exactly a month!
Aaron had a very interesting observation concerning error codes raised from the
Quantum API. We currently use several 4xx codes to describe Quantum-specific
errors, such as "NetworkNotFound" or "PortNotFound"; we ensured
Ideally I would choose the 2nd route as well.
However, this kind of reminds me of the discussions we were having at the
design summit over whether we should rely on a new service/extension of the
Quantum API for achieving feature parity (e.g. The ‘L3 service’) or try to
re-use as much as possibl
Hi,
First of all, apologies for a much-delayed reply. I'm officially back in office
today, and I'm slowly catching up with my todo list.
Please see my replies inline.
The next time in my todo list is to push a preview of the code (I still need to
add unit tests to make it gerrit-pushable).
Sal
I pushed some code for the api-filters feature into a github repo.
You can find the code in the bp/api-filters here:
git://github.com/salv-orlando/MyRepo.git
Please note this code is not final yet (unit tests will come, pep8 and pylint
will be improved).
I'm sharing this to give you a feel of th
4 matches
Mail list logo
