Don't raise MySQL 2013 'Lost connection' errors

Although this code error is part of the `ping_listener` tests, it was
missing from the list of known - and ignored - connection errors.

The code error 2013 refers to a connection lost during a query, see:
https://dev.mysql.com/doc/refman/5.0/en/error-messages-client.html#error_cr_server_lost

Without this error code, the session won't try to reconnect to mysql,
which makes `max_retries` useless.

Closes-bug: #1276510
Change-Id: I27cad999b30a480ae23250150bfcba2668acabd7
Use six.StringIO/BytesIO instead of StringIO.StringIO

to keep Python 3.x compatibility, use six.StringIO/BytesIO to
replace StringIO.StringIO

StringIO works for unicode
BytesIO works for bytes

Change-Id: I0d1f8a55c3bc41379077b46feb81931779b7ad45
Partial-Bug: #1280100
Clarify and fix the dev-quickstart doc some more

Clarify and fix up the dev-quickstart doc some more
based on user feedback.

Testing examples now use tox rather than invoking the
testr command directly.

Simplified the section on building the documentation by
removing the need to install a web server.

Co-Authored-By: David Shrewsbury <shrewsbury.dave@gmail.com>

Change-Id: Ibdff4b44a26f11a5a0e92efb4c451105f6ab3245
Sync Oslo rpc module to Ironic

Our ironic oslo rpc code is out of date, need to be updated.
Related to blueprint send-data-to-ceilometer

List of changes:
fcf517d72cb81f972fad20caa9ff0341e9b4aa9c
Update oslo log messages with translation domains

7aa82452d0782355a0bf50d88e2d9a3625f9e000
Use Context Manager for reading JSON configs

a0948cb88d414e2a4b1a21340fcbfabfe8fa5aed
lockutils: remove local usage

22e971ac1103336a4859e9c7314ffc52d137405a
safe_log Sanitize Passwords in List of Dicts

8b2b0b743e84ceed7841cf470afed6a5da8e1d07
Use hacking import_exceptions for gettextutils
23f602940c64ba408d77ceb8f5ba0f67ee4a18ef
Use six.seraise() instead of `raise exc, val, tb`

ef406a21782134aeefb944f74b3f1a47d6169318
Create a shared queue for QPID topic consumers

e6494c2bcd52ae25744fe764b9f42cfdf7a6195e
Use six.iteritems to make dict work on Python2/3

e227c0ed7e0ed1f9b8d029336f8aeb60e38c23df
Properly reconnect subscribing clients when QPID broker restarts

16fb43b8b5d38998c690f35e3c21299d5b00550f
Replace data structures' attribute with six module

27b21bc95275a994c750c3f6bb145f4d0179cb55
Unify different names between Python2/3 with six.moves

4bfb7a2a772b40c3d4484876b27ec6f19c1a60a4
Apply six for metaclass

d7d74a752e34d5249fa47c8e8252da491d46012a
Add `versionutils` for version compatibility checks

3cdd157013881c7f1bf55dff0187f6531214e774
Add third element to RPC versions for backports

76972e2949634abe9fcc9ad36c103cca94300237
Support a new qpid topology

284b13adfb88018d58e0c7c4bfe840d1db1e8f6b
Raise timeout in fake RPC if no consumers found

7b0cb37c3015977e526a9473b7756a2fb1e852c8
Don't eat callback exceptions

69abf38814d71a111bb94b61963b93a421aab13d
requeue instead of reject

61c4cdec304d79f43c8a549c2543c939492c4812
Ensure context type is handled when using to_dict

223f9e101a24e403f9f252ecdfc0362ff3183ce2
Clarify precedence of secret_key_file

a035f95fef3944b3bf4d9ac5203726c72edb70c7
Don't shadow cfg import in securemessage

0f8857543b43a2f0e2c567603a0a24de61c31d45
Remove redundant global keyword in securemessage

848c4d530e0c3dd6493289b38366e08260d437ca
Some nitpicky securemessage cleanups

5c71c257e001b16e03ab78be4518736d5256c3bd
Allow non-use of cfg.CONF in securemessage

9157286d1e96246a44ba9891ec302e59a0e5c7be
RPC: Add MessageSecurity implementation

a047a353438d1e9449f94850b29d79bb2dd8f9b1
Make ZeroMQ based RPC consumer threads more robust

And updated ironic.conf.sample using new config generator.

Change-Id: I2200db850aecab912c4796c743c1e87fcb9327eb
Exclude nodes in DEPLOYWAIT state from _sync_power_states

_sync_power_states() periodical task requires exclusive lock, if
this task is running on node in DEPLOYWAIT state callback from
deploy ramdisk in PXE driver will be failed.

Closes-Bug: #1284136
Change-Id: I5921cc4005329ccda3b3ed571e822d9188bd2630
Merge "Use six.StringIO/BytesIO instead of StringIO.StringIO"
Add provision_updated_at field to nodes table

For timeouts handling we need track time when deploy operations
started. This patch add new DateTime field 'provision_updated_at'
to nodes table. update_node() DB API method set this field when
provision state of a node changed.

Change-Id: I0c3dbd5164a8decead2a94449b5717cdd4a1f7a4
Unused 'pxe_key_data' & 'pxe_instance_name' info

This removes references to the pxe driver's 'pxe_key_data' and
'pxe_instance_name' (driver) info, because that information is
never used.

Change-Id: I73c94dab83fb9c72b251e65859475486505bfbc6
Merge "Clarify and fix the dev-quickstart doc some more"
Merge "Exclude nodes in DEPLOYWAIT state from _sync_power_states"
Merge "Don't raise MySQL 2013 'Lost connection' errors"
Merge "Unused 'pxe_key_data' & 'pxe_instance_name' info"
Merge "Add provision_updated_at field to nodes table"
Merge "Sync Oslo rpc module to Ironic"