fuel openstack-config --execute doesn't support --force option

[Sergey Slipushenko]

fuel openstack-config --execute doesn't support --force option

Both v1 and v2 clients should be fixed

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/258607
Committed: https://git.openstack.org/cgit/openstack/python-fuelclient/commit/?id=1c66fee11bebf9e66db81f3d937ffaeacef28fd6
Submitter: Jenkins
Branch: master

commit 1c66fee11bebf9e66db81f3d937ffaeacef28fd6
Author: sslypushenko <email address hidden>
Date: Wed Dec 16 18:18:34 2015 +0200

    Add --force option to OpenStack config update command

    Both v1 and v2 clients are fixed

    Closes-bug: #1526871
    Related-Bug: #1523131

    Depends-on: I2ef06b7084b0cafa576172c9f2db40aa4ccd6db8

    Change-Id: I5c9594f0ce65c893a5d7d2c7424533c7a36d4f2d

[Ksenia Svechnikova (kdemina)]

Verify force option on ISO#435

Steps:
  1. Deploy cluster
  2. Run provisioning task on one compute
  3. Upload config
    fuel openstack-config --role controller --env 1 --upload --file mongo.yaml
  4. Execute config with force option for controller or sepate node:

    [root@nailgun ~]# fuel openstack-config --execute --env 1 --node-id 5 --force
    Openstack configuration update is started.
    [root@nailgun ~]# fuel openstack-config --execute --env 1 --node-id 5 --forc^C
    Openstack configuration update is started.