create instance min/max count defaulting logic is reversed in EC2 and native OS APIs

[Eoghan Glynn]

EC2 API: default max to 1, default min to max

OS API: default min to 1, default max to min

It would seem more logical to keep to these two defaulting strategies consistent.

[Sean Dague (sdague)]

Any progress so far?

[Bhuvan Arumugam (bhuvan)]

Shall we go with following defaults, for both API?
     default min to 1, default max to min

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/10618

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/10620

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/10620
Committed: http://github.com/openstack/nova/commit/045b084d34c08aee910cee2362cf209fd80d3c6d
Submitter: Jenkins
Branch: master

commit 045b084d34c08aee910cee2362cf209fd80d3c6d
Author: isethi <email address hidden>
Date: Tue Jul 31 19:52:49 2012 +0000

    Changes default behavior of ec2

    Changes the default behaviour of create instance min/max count logic
    in ec2 to match the default behavior of OS API

    Fixes bug 989799

    Change-Id: I1aa42c7d47674ce68442367fab487152b3e7fa67