On 7/4/2017 7:13 PM, Takashi Natsume wrote:
On 2017/07/04 21:12, Alex Xu wrote:
2017-07-04 15:40 GMT+08:00 Ghanshyam Mann :
On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume
wrote:
In Nova API reference, there is inconsistency in
whether to define parameters added in new microversion as 'optio
On 2017/07/04 21:12, Alex Xu wrote:
2017-07-04 15:40 GMT+08:00 Ghanshyam Mann :
On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume
wrote:
In Nova API reference, there is inconsistency in
whether to define parameters added in new microversion as 'optional' or
not.
Those should be defined based
2017-07-04 15:40 GMT+08:00 Ghanshyam Mann :
> On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume
> wrote:
> > Hi, all.
> >
> > In Nova API reference, there is inconsistency in
> > whether to define parameters added in new microversion as 'optional' or
> not.
>
> Those should be defined based on how
On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume
wrote:
> Hi, all.
>
> In Nova API reference, there is inconsistency in
> whether to define parameters added in new microversion as 'optional' or not.
Those should be defined based on how they are defined in respective
microversion. If they are 'opti
Hi, all.
In Nova API reference, there is inconsistency in
whether to define parameters added in new microversion as 'optional' or not.
In the case that the parameter is always included in the response after
a certain microversion,
some parameters(e.g. 'type' [1]) are defined as 'required', but
