It's not ported to the V3 API because we only support neutron in the V3 API
and fixed ip related queries/settings can be made directly to the neutron
API.
I think adding the reserved status for the fixed IP would be ok. It would
have to be handled in the usual way for extending the V2 API though - eg
adding another extension so it can be detected when that feature will be
available.
More broadly speaking we discussed at summit perhaps closing V2 API
development at the end of I-2 (assuming V3 is looking good by that stage) -
except for bug fixes of course.
Answer from Chris Yeoh on the mailing list:
It's not ported to the V3 API because we only support neutron in the V3 API
and fixed ip related queries/settings can be made directly to the neutron
API.
I think adding the reserved status for the fixed IP would be ok. It would
have to be handled in the usual way for extending the V2 API though - eg
adding another extension so it can be detected when that feature will be
available.
More broadly speaking we discussed at summit perhaps closing V2 API
development at the end of I-2 (assuming V3 is looking good by that stage) -
except for bug fixes of course.