Use for/else rather than a guard value

Python has a useful for/else pattern that will execute the else block
if break inside the loop wasn't called, which allows us to dispose of
the guard value used to tell if a node has been created.

Change-Id: Ie29c9eed54911c64a420ce93f2920e640a5c9aac
Work toward Python 3.4 support and testing

Change-Id: I44d436137a0eff808352d7b893d80f52fac64071
Add documentation for setup-neutron

There was no documentation added for setup-neutron when the code
landed, which is terrible. Fix that by writing some.

Drive-by a missing word in the Keystone PKI section.

Change-Id: I5d4d67827e1911283533e022bd7d4750f9619eb5
Modify gitignore to ignore cover

Prevent generated coverage report files from being imported.

Change-Id: I9b69c91c95e5dbaac8c52cdc461dd89abd0f4d1c
register-nodes: add support for iboot

This updates the register-nodes command to support
use of the pxe_iboot driver with Ironic.

Change-Id: I253734f0d85e46b6af68e07ad7899b5f5afba65c
Merge "Add documentation for setup-neutron"
Merge "register-nodes: add support for iboot"
Merge "Use for/else rather than a guard value"
Merge "Modify gitignore to ignore cover"
Merge "Work toward Python 3.4 support and testing"
Do not create the _member_ role

Keystone will automatically create the _member_ role if it does not
exist, so there's no need to do it in os-cloud-config. Further,
explicitly creating it will cause an issue when you go to create the
first user in Keystone.

Keystone will try to add the user to the _member_ role, but use the
default *id*:
http://git.openstack.org/cgit/openstack/keystone/tree/keystone/assignment/core.py#n261

Since os-cloud-config has precreated the role, it has a different id, so
then when Keystone will try and create _member_ again, and failing with
a duplicate entry.

This change was introduced in os-cloud-config via commit:
Ia4d965335f900e03465f45c701f0bd5a3a4a0ea6

Instead of just reverting that commit, I figured we could remove the
_member_ role creation entirely.

We aren't seeing this failure scenario in CI, because we haven't had a
os-cloud-config release in a while apparently and we don't use
os-cloud-config from git (for better or worse).

Change-Id: Iaa05c71173140e68e47357ac8a9ab3fdb276c838

Conflicts:
	os_cloud_config/cmd/init_keystone.py
	os_cloud_config/keystone.py
	os_cloud_config/tests/test_keystone.py