if using nova boot --num-instances and neutron instances count are truncated to port quota

[Aaron Rosen]

If using nova with neutron and you run the following command:

nova boot --image cirros-0.3.1-x86_64-uec --flavor 1 --nic net-id=41b95a61-c052-4cfa-8361-493e8d7298e3 --nic net-id=4658b15d-1a0c-4a13-bd28-b5dd41b5feee --nic net-id=70da3b11-531c-471c-89cb-8146183c5470 --flavor 100 vmx --num-instances 30

and you do not have enough quota it would be nice if nova-api would raise an error or perhaps actually try and launch 30 instances. Instead you get some number of instances up to your port-quota.

[Joe Gordon (jogo)]

This is a novaclient bug, the nova API has min_count and max_count. if min_count is over the quota limit the command will fail. So novaclient should be updated to support min_count and max_count flags and deprecate num-instances (as an alias for max count)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/90836
Committed: https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=1e7ad37b8a842094963d3296cf127614f49e10fe
Submitter: Jenkins
Branch: master

commit 1e7ad37b8a842094963d3296cf127614f49e10fe
Author: Joe Gordon <email address hidden>
Date: Mon Apr 28 22:17:50 2014 +0000

    Deprecate num-instances in favor of min/max count

    For 'nova boot', num_instances only set max_count, which will try to
    launch up to max_count instances. But sometimes users want to either
    launch min_count instances or nothing. So deprecate --num-instances
    and use --min-count and --max-count instead.

    DocImpact: deprecate '--num-instances' for 'nova boot'

    Change-Id: If0088aef554a528258799b22c6e793541474cb0d
    Closes-bug: #1309244