Cleanup copy and pasted token

Correctly use fixtures instead.

Change-Id: If726b1365cb7659a9db011bdcb37252563f84ef4
Use discovery fixture

Use the provided fixtures rather than copying code out of
keystoneclient.

Change-Id: I550edc355f008d94d6c0b834494d693137c29111
Make help for agent-update more verbose

Amended the description of the command to reflect what it
really does.
Added two optional aguments:
    * admin-state-down - sets admin state up of the agent to false
    * description - provides the description for the agent

Added a unit test.

Change-Id: Ie9f30f30102bef6735dc9ed538eca9a1183c2780
Closes-Bug: #1254241
Add unit tests for agent related commands

Added unit tests to cover:
    * agent show;
    * agent delete.

Change-Id: I98879cfe1bb1e7c085404aa73786a1eeaae1f40e
Closes-Bug: #1206110
Fix issues with Unicode compatibility for Py3

HTTP arguments should not be encoded because:
 * requests library does it automatically replacing unicode
   characters with utf-8 sequences
 * on py3 encoding function replaces string with byte array,
   thus breaking keystone client

Closes bug 1398854

Change-Id: I747778259656f1c9803bcf990cdd85f87a77fd1a
Router create distributed accepts lower case

Neutron router-create optional argument distributed
does not accept "true/false" anymore.
It only accepts value with Camel case "True/False".

This patch will allow the users to provide both
True/true or False/false.

Change-Id: I79577bd70a796543b9dea53b4839512eb8944d7c
Closes-bug: #1368934
Merge "Router create distributed accepts lower case"
Merge "Cleanup copy and pasted token"
Merge "Use discovery fixture"
subnet: allow --enable-dhcp=False/True syntax, again

Till neutronclient 2.3.4, we allowed the following syntax to enable or
disable DHCP: --enable-dhcp=False or --enable-dhcp=True. Since
I52d05ec2284b6910a33df4a5cb7dc3888737acb6 was merged, it's not the case
anymore.

Client libraries should be backwards compatible.

The change that introduced the regression cannot be reverted. First,
because it's correct in essence and fixed a valid bug in neutron client
CLI, and second (and more importantly), we don't want to break backwards
compatibility for users that currently use 2.3.5+ version that already
included the new style of the argument.

So we need to support both new and old styles for setting the attribute.

It's sad, but argparse module that we use to parse CLI arguments does
not allow to distinguish between '--enable-dhcp=smth' and '--enable-dhcp
smth' variants of the argument. This limitation means that an argument
with nargs=argparse.OPTIONAL that would be useful to cover both styles
with single entry would consume the next argument from the command line
if it's present and does not seem to be another option argument defined
for the parser. Meaning, it would break some cases, f.e. when
--enable-dhcp is passed right before subnet name. In that specific case,
the argument would consume the name as the value of the argument and
break the client.

That's why for this specific fix, we're forced to use
--enable-dhcp=False and --enable-dhcp=True as argument *names*. It's
ugly as hell, so let's hide that mess from users by suppressing help
entries for new arguments.

PS: And Oh Lord the Mighty, thank you for only two possible values for
boolean attributes!)

Closes-Bug: #1401555
Change-Id: Ib374d1cc499e4f1e5242f1b438bc65512c109e40
firewall policy update for a rule is not working

If user specifies one rule to update it is not taking but more than one rule
it is accepting as a list and updating the policy. Modified policy-update to
behave same as policy-create command for "--firewall-rules" option

Change-Id: Ia6a1c726be310d60b3b56ce677f843e818079fbe
Closes-bug: 1318617
Merge "subnet: allow --enable-dhcp=False/True syntax, again"
Merge "firewall policy update for a rule is not working"
Updated from global requirements

Change-Id: I1c29fbdbd0413b2c58dbf3acf979759aa45123ae
Merge "Fix issues with Unicode compatibility for Py3"
Merge "Updated from global requirements"