Fix help for register-nodes

The help for the --service-host arg for register-nodes seemed too
specific to Nova baremetal.

Change-Id: I137f2f78fbb9790459a2f92aaab046649460e51d
Updated from global requirements

Change-Id: Id140f410c68982ff07a2334614fc927f4b4ed15f
Create _member_ role instead of Member

Horizon moved to role _member_ in place of Member. With this change,
os-cloud-config creates _member_ instead of Member during Keystone
initialization.

Change-Id: Ia4d965335f900e03465f45c701f0bd5a3a4a0ea6
Allow use custom ssh_virt_type when register node

In register_ironic_node, ssh_virt_type is hard coded.
This fixes it.

Change-Id: Ie1b00e0c7baef0e93187e5cb8e252db3aa44e7b4
Closes-Bug: #1367586
Correct intent of function names in nodes

_create_or_register_{bm,ironic}_node does not express the intent
of the function, since creating a node is the same as registering it.
Fix this thinko by calling the functions
_update_or_register_{bm,ironic}_node.

Change-Id: Ifa5932b78a103655885af3742eeda8156b457822
Merge "Create _member_ role instead of Member"
Support custom nameservers in setup-neutron

Allow the network description to pass in the nameserver to be used
for the subnet, falling back to the default of 8.8.8.8 for floating
networks if one is not specified.

Change-Id: Ibd8a33b0f1a3e26fb14b5050dd7e536828a3f3eb
Merge "Correct intent of function names in nodes"
Add a new blocking argument to register_all_nodes

Currently, if the nova-baremetal and ironic services are not
available when registering a node, the function calls will sleep
for ten seconds. Make this behaviour configurable by use of a
blocking flag that default to True.

Change-Id: I87b05acf61ef7424243cb040e10ab84a73a68ec3
Merge "Updated from global requirements"
Merge "Allow use custom ssh_virt_type when register node"
Merge "Support custom nameservers in setup-neutron"
Set iboot_relay_id and iboot_port

When register-nodes, Optional parameters of iboot_relay_id and iboot_port
were not set correctly. This fixes it.

Change-Id: I7246f026102d1cf434405b78fc2a5911a4cac91a
Closes-Bug: #1370304
Merge "Add a new blocking argument to register_all_nodes"
Updated from global requirements

Change-Id: If91358f27864cff105fe50d6ae49421fafdc3785
Merge "Fix help for register-nodes"
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
Merge "Do not create the _member_ role"
Merge "Set iboot_relay_id and iboot_port"