Command-line argument parsing no longer verifies arguments correctly

[GoogleCodeExporter]

When deploying over Eucalyptus, argument handling breaks down in a number
of ways:

1) If neither --machine or $APPSCALE_MACHINE are specified, run-instances
should fail. It currently tries to euca-run and runs until the timeout
kills appscale-run-instances.

2) If a configuration file is provided, min and max should be set to the
number of nodes given. This currently breaks in two ways:

2a) If given a config file with one box, it says it can't go on since min is 4.

2b) If given a config file with eight boxes, it says it can't go on since
max is 4.

Original issue reported on code.google.com by shattere...@gmail.com on 6 May 2010 at 4:49

[GoogleCodeExporter]

Just to clarify #2. We were previously defaulting min/max to be four if it was 
not
specified. This should remain the case if a yamls file is not provided. If one 
is
provided then min/max should default to the number of nodes in the yaml file. 
Is that
accurate?

Original comment by jmkupfer...@gmail.com on 6 May 2010 at 5:53

[GoogleCodeExporter]

Yes, that is correct.

Original comment by shattere...@gmail.com on 6 May 2010 at 5:56

[GoogleCodeExporter]

Fix for issue 2 has been pushed to the tools in revno 136.

Original comment by jmkupfer...@gmail.com on 6 May 2010 at 6:25

[GoogleCodeExporter]

Testing out fix for part 1. Working on catching scenarios where the requested VM
can't run due to the wrong instance type being selected.

Original comment by shattere...@gmail.com on 6 May 2010 at 7:32

[GoogleCodeExporter]

Fixed.

Original comment by shattere...@gmail.com on 12 May 2010 at 5:25

• Changed state: Fixed