Rename install role to bifrost-ironic-install

Since the install role is specifically geared to install ironic
in a way that bifrost uses, we should name the role appropriately.

Note: This will be followed up with a change to revise the
README file for the role as changing and renaming the file
will result in issues with the file history.

Change-Id: I553a29206a045b5aa0e679ce05e984c7dd4b9df3
Depends-On: Ia6226a8573753ff02da19dcb3c2b5abfb9b3c297

playbooks/install.yaml

@@ -6,7 +6,7 @@
   gather_facts: yes
   roles:
     - { role: bifrost-prep-for-install, when: skip_install is not defined }
-    - ironic-install
+    - bifrost-ironic-install
     - { role: bifrost-create-dib-image, dib_imagename: "{{ deploy_image }}", dib_imagetype: "qcow2", dib_os_element: "{{ dib_os_element|default('debian') }}", dib_elements: "vm serial-console simple-init {{ extra_dib_elements|default('') }}", dib_packages: "{{ dib_packages|default('') }}", when: create_image_via_dib == true and transform_boot_image == false }
   environment:
     http_proxy: "{{ lookup('env','http_proxy') }}"

playbooks/roles/bifrost-configdrives-dynamic/README.md

@@ -88,9 +88,9 @@ Dependencies
 ------------
 
 This role is expected to be executed on a system that has had the
-ironic-install role executed upon it, however as the configuration
+bifrost-ironic-install role executed upon it, however as the configuration
-drive creation step is fairly self contained, it can be executed
+drive creation step is fairly self contained, it can be executed as a
-as a separate step.
+separate step.
 
 Example Playbook
 ----------------

playbooks/roles/bifrost-deploy-nodes-dynamic/README.md

@@ -7,8 +7,8 @@ installed by Bifrost.
 Requirements
 ------------
 
-This role is expected to be executed on a node that the "ironic-install" node
+This role is expected to be executed on a node that the
-has been executed upon.
+"bifrost-ironic-install" node has been executed upon.
 
 This role expects to be executed in a sequence with
 bifrost-configdrives-dynamic, however that is un-necessary IF the host has a
@@ -53,10 +53,11 @@ instance_info: A dictionary containing the information to define an instance.
 Dependencies
 ------------
 
-This role is intended to be executed upon a node that the ironic-install role
+This role is intended to be executed upon a node that the
-has been executed upon.  The configuration that is leveraged by this role
+bifrost-ironic-install role has been executed upon.  The configuration that
-utilizes a configuration drive to place network configuration and an SSH key on
+is leveraged by this role utilizes a configuration drive to place network
-the newly deployed host.  As such, the bifrost-configdrives role is required.
+configuration and an SSH key on the newly deployed host.  As such, the
+bifrost-configdrives role is required.
 
 Example Playbook
 ----------------

playbooks/roles/bifrost-prep-for-install/README.md

@@ -61,7 +61,7 @@ Example Playbook
   gather_facts: yes
   roles:
     - { role: bifrost-prep-for-install, when: skip_install is not defined }
-    - role: ironic-install
+    - role: bifrost-ironic-install
       cleaning: false
       testing: true
 

playbooks/roles/bifrost-setup-nodes/README.md

@@ -7,8 +7,8 @@ baremetal_csv_file utilizing the os_ironic_node installed by Bifrost.
 Requirements
 ------------
 
-This role is expected to be executed on a node that the "ironic-install" node
+This role is expected to be executed on a node that the
-has been executed upon.
+"bifrost-ironic-install" node has been executed upon.
 
 As configured, this role requires the "bifrost-configdrives" role be executed
 prior to this role, utilizing the baremetal_csv_file variable which defines the
@@ -50,10 +50,11 @@ deploy_image: This is the full path to the image to be deployed to the system.
 Dependencies
 ------------
 
-This role is intended to be executed upon a node that the ironic-install role
+This role is intended to be executed upon a node that the
-has been executed upon.  The configuration that is leveraged by this role
+bifrost-ironic-install role has been executed upon.  The configuration that
-utilizes a configuration drive to place network configuration and an SSH key on
+is leveraged by this role utilizes a configuration drive to place network
-the newly deployed host.  As such, the bifrost-configdrives role is required.
+configuration and an SSH key on the newly deployed host.  As such,
+the bifrost-configdrives role is required.
 
 Example Playbook
 ----------------

playbooks/roles/bifrost-unprovision-node-dynamic/README.md

@@ -23,7 +23,7 @@ Dependencies
 ------------
 
 This role has no roles that it is directly dependent upon, but expects that the
-environment has been installed with the ironic-install role.
+environment has been installed with the bifrost-ironic-install role.
 
 Example Playbook
 ----------------

playbooks/roles/ironic-enroll-dynamic/README.md

@@ -63,8 +63,8 @@ driver required.
 Dependencies
 ------------
 
-This role is presently dependent upon the ironic-install role which installs
+This role is presently dependent upon the bifrost-ironic-install role which
-the necessary requirements.
+installs the necessary requirements.
 
 Example Playbook
 ----------------

playbooks/test-bifrost-dynamic.yaml

@@ -48,7 +48,7 @@
       when: ci_testing is defined
   roles:
     - role: bifrost-create-vm-nodes
-    - role: ironic-install
+    - role: bifrost-ironic-install
       cleaning: false
       testing: true
     - { role: bifrost-create-dib-image, dib_imagetype: "qcow2", dib_imagename: "{{deploy_image}}", dib_os_element: "{{ dib_os_element|default('debian') }}", dib_elements: "vm serial-console simple-init {{ extra_dib_elements|default('') }}", dib_packages: "{{ dib_packages|default('') }}", when: create_image_via_dib == true and transform_boot_image == false }