openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #02530
Re: OpenStack API, Reservation ID's and Num Instances ...
Hmm, not sure I like changing the return type based on the input type. Return types should be consistent.
________________________________________
From: Ed Leafe
> If we are going to add an optional parameter to specify the number of instances, would it be acceptable to specify that when that parameter is included, a reservation ID is returned instead of an instance ID? IOW, existing calls will work the same, but calls that take advantage of this new option would expect a different result.
Follow ups
References
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jorge Williams, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jay Pipes, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jorge Williams, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Ed Leafe, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jorge Williams, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Ed Leafe, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Brian Schott, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jay Pipes, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Vishvananda Ishaya, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Jorge Williams, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Eric Day, 2011-05-23
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Brian Lamar, 2011-05-24
-
Re: OpenStack API, Reservation ID's and Num Instances ...
From: Ed Leafe, 2011-05-24