fwaas:In firewall-rule-create cli --disabled should be removed

[Rajkumar]

 In neutron firewall-rule-create cli --disabled should be removed. Though we can able to disable the firewall rule using this option, we cannot enable it again. However using --enabled True|False we can either enable or disable the firewall rule.
 And also --enable should be shown as optional arguments in help instead of --disable.

[Shivakumar M (shiva-m)]

Its better to provide CLI option --enable (True/False). --disabled is not required.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/103769
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=6260c207fb7d089cc56e08f89fcb755c0086c733
Submitter: Jenkins
Branch: master

commit 6260c207fb7d089cc56e08f89fcb755c0086c733
Author: Koteswara Rao Kelam <email address hidden>
Date: Tue Jul 1 00:21:29 2014 -0700

    Remove "--disabled" for firewall create rule

    Allow "--enabled True/False" and remove "--disabled" for consistency across
    all commands. Even in other neutron commands, we are using only --enabled
    option but not --disabled. firewall-rule-show displays only "enabled" attribute
    and there is no "disabled" attribute.

    Change-Id: Ie591d827660466a774e431dcb40e04e09773e5f7
    Closes-bug: 1327056