Ensure proper ordering of XML arguments

Random hash ordering can cause the 'encoding' argument to be rendered
in the XML string before the 'version' argument, resulting in XML
deserialization errors on the Keystone side.  This modifies
Document's string rendering to not rely on dict ordering when
constructing the header tag's version + encoding arguments and avoids
XML auth issues when using PYTHONHASHSEED=random.

Change-Id: I66d18a2f8da1088ec5d310a43c84df7e4d6a6f6b
Move API response success check to Neutron client

* Move all API response success validation from Neutron API tests to
  Neutron base/json/xml clients

Partially Implements blueprint: client-checks-success

Change-Id: I784e9b610f64564861e94d20c6200d1e6915e7f7
Client response checking for orchestration service

Updated all orchestration tests to remove the response checks
and move those to respective clients.

Partially Implements blueprint: client-checks-success

Change-Id: If74df1644c6f61b03388e47768f1cffa91fad99c
Merge "Client response checking for orchestration service"
Merge "Ensure proper ordering of XML arguments"
Add ipv4access and ipv6access in test_rebuild_servers.
Implement test_resize_server_revert_from_stoped in test_server_actions
remove create_test_server_group in compute/base.py
add test for creating server with block device mapping v2
I wrote func test_list_servers_filter_by_server_marker------sunchun
Add test for creating servers with extended attribute
Add support for creating instances with a default network id

Nova api refuses to create a new instance when more than one network available.

We must specify a network id to avoid failure of creating test servers.
Add tests for volume attachments of servers
Add test_can_create_server_with_a_personality_file
Fix default_network_id config in xml
Fix some typo in test_verify_extended_attributes
Complement for some changes in xml interface
Change the device name of device_name_mapping_v2 to avoid issues
use relative path instead of absolute path when locating 'addresses'

There are two different xml structures sharing this translating-function:

<server ...>
...
</server>

and

<servers ...>
    <server ...>
    ...
    </server>
</servers>

It is inappropriate to locate the attribute 'addresses' using the absolute path.
Fix 'os-extended-volumes:volume_attached' mismatch between json and xml interface