Merge "Change links to point to new install guide"
This commit is contained in:
Jenkins
Gerrit Code Review
commit
ed1c9d9cdd
@ -189,7 +189,7 @@ If you are using the Neutron DHCP provider (the default) you will also need to
|
||||
ensure you have configured a cleaning network. This network will be used to
|
||||
boot the ramdisk for in-band cleaning. You can use the same network as your
|
||||
tenant network. For steps to set up the cleaning network, please see
|
||||
:ref:`CleaningNetworkSetup`.
|
||||
`Configure the Bare Metal service for cleaning`_.
|
||||
|
||||
.. _InbandvsOutOfBandCleaning:
|
||||
|
||||
@ -328,3 +328,5 @@ to allow it to be scheduled by nova.
|
||||
|
||||
The node will begin automated cleaning from the start, and move to
|
||||
``available`` state when complete.
|
||||
|
||||
.. _`Configure the Bare Metal service for cleaning`: http://docs.openstack.org/project-install-guide/baremetal/draft/configure-cleaning.html
|
||||
|
||||
@ -83,8 +83,8 @@ interface as stated above):
|
||||
cleaning_network_uuid=$CLEAN_UUID
|
||||
provisioning_network_uuid=$PROVISION_UUID
|
||||
|
||||
Please refer to :ref:`CleaningNetworkSetup` for more information about
|
||||
cleaning.
|
||||
Please refer to `Configure the Bare Metal service for cleaning`_ for more
|
||||
information about cleaning.
|
||||
|
||||
.. note::
|
||||
The "provisioning" and "cleaning" networks may be the same neutron
|
||||
@ -224,3 +224,5 @@ Configuring nodes
|
||||
After these steps, the provisioning of the created node will happen in the
|
||||
provisioning network, and then the node will be moved to the tenant network
|
||||
that was requested.
|
||||
|
||||
.. _`Configure the Bare Metal service for cleaning`: http://docs.openstack.org/project-install-guide/baremetal/draft/configure-cleaning.html
|
||||
|
||||
@ -118,5 +118,7 @@ information, see :ref:`automated_cleaning`.
|
||||
If ironic is configured with automated cleaning enabled (defaults to True) and
|
||||
to use Neutron as the DHCP provider (also the default), you will need to set the
|
||||
`cleaning_network_uuid` option in the ironic configuration file before starting
|
||||
the Kilo ironic service. See :ref:`CleaningNetworkSetup` for information on
|
||||
how to set up the cleaning network for ironic.
|
||||
the Kilo ironic service. See `Configure the Bare Metal service for cleaning`_
|
||||
for information on how to set up the cleaning network for ironic.
|
||||
|
||||
.. _`Configure the Bare Metal service for cleaning`: http://docs.openstack.org/project-install-guide/baremetal/draft/configure-cleaning.html
|
||||
|
||||
@ -89,4 +89,6 @@ The following sequence of commands can be used to enroll a UCS Standalone node.
|
||||
|
||||
ironic port-create -n $NODE -a <MAC_address_of_Ucs_server's_NIC>
|
||||
|
||||
For more information about enrolling nodes see "Enrolling a node" in the :ref:`install-guide`
|
||||
For more information about enrolling nodes see `Enrolling a node`_ in the install guide.
|
||||
|
||||
.. _`Enrolling a node`: http://docs.openstack.org/project-install-guide/baremetal/draft/enrollment.html#enrolling-a-node
|
||||
|
||||
@ -208,11 +208,12 @@ Target Users
|
||||
|
||||
The PXE driver passes management information in clear-text to the
|
||||
bare metal node. However, if swift proxy server and glance have HTTPS
|
||||
endpoints (See :ref:`EnableHTTPSinSwift`, :ref:`EnableHTTPSinGlance` for more
|
||||
information), the ``iscsi_ilo`` driver provides enhanced security by
|
||||
exchanging management information with swift and glance endpoints over HTTPS.
|
||||
The management information, deploy ramdisk and boot images for the instance
|
||||
will be retrieved over encrypted management network via iLO virtual media.
|
||||
endpoints (See `Enabling HTTPS in Swift`_, `Enabling HTTPS in Image
|
||||
service`_ for more information), the ``iscsi_ilo`` driver provides enhanced
|
||||
security by exchanging management information with swift and glance
|
||||
endpoints over HTTPS. The management information, deploy ramdisk and boot
|
||||
images for the instance will be retrieved over encrypted management network
|
||||
via iLO virtual media.
|
||||
|
||||
Tested Platforms
|
||||
~~~~~~~~~~~~~~~~
|
||||
@ -241,10 +242,10 @@ Features
|
||||
* UEFI Secure Boot Support
|
||||
* Passing management information via secure, encrypted management network
|
||||
(virtual media) if swift proxy server and glance have HTTPS endpoints. See
|
||||
:ref:`EnableHTTPSinSwift`, :ref:`EnableHTTPSinGlance` for more info. User
|
||||
image provisioning is done using iSCSI over data network, so this driver has
|
||||
the benefit of security enhancement with the same performance. It segregates
|
||||
management info from data channel.
|
||||
`Enabling HTTPS in Swift`_, `Enabling HTTPS in Image service`_ for more
|
||||
information. User image provisioning is done using iSCSI over data network,
|
||||
so this driver has the benefit of security enhancement with the same
|
||||
performance. It segregates management info from data channel.
|
||||
* Supports both out-of-band and in-band cleaning operations. For more details,
|
||||
see :ref:`InbandvsOutOfBandCleaning`.
|
||||
* Remote Console
|
||||
@ -368,11 +369,11 @@ Target Users
|
||||
|
||||
The PXE based agent drivers pass management information in clear-text to
|
||||
the bare metal node. However, if swift proxy server and glance have HTTPS
|
||||
endpoints (See :ref:`EnableHTTPSinSwift`, :ref:`EnableHTTPSinGlance` for more
|
||||
information), the ``agent_ilo`` driver provides enhanced security by
|
||||
exchanging authtoken and management information with swift and glance
|
||||
endpoints over HTTPS. The management information and deploy ramdisk will be
|
||||
retrieved over encrypted management network via iLO.
|
||||
endpoints (See `Enabling HTTPS in Swift`_, `Enabling HTTPS in Image
|
||||
service`_ for more information), the ``agent_ilo`` driver provides enhanced
|
||||
security by exchanging authtoken and management information with swift and
|
||||
glance endpoints over HTTPS. The management information and deploy ramdisk
|
||||
will be retrieved over encrypted management network via iLO.
|
||||
|
||||
Tested Platforms
|
||||
~~~~~~~~~~~~~~~~
|
||||
@ -1548,3 +1549,5 @@ use the ``proliant-tools`` element in DIB::
|
||||
|
||||
disk-image-create -o proliant-agent-ramdisk ironic-agent fedora proliant-tools
|
||||
|
||||
.. _`Enabling HTTPS in Swift`: http://docs.openstack.org/project-install-guide/baremetal/draft/enabling-https.html#enabling-https-in-swift
|
||||
.. _`Enabling HTTPS in Image service`: http://docs.openstack.org/project-install-guide/baremetal/draft/enabling-https.html#enabling-https-in-image-service
|
||||
|
||||
@ -46,7 +46,7 @@ Requirements
|
||||
------------
|
||||
|
||||
Using IPA requires it to be present and configured on the deploy ramdisk, see
|
||||
:ref:`BuildingDeployRamdisk` for details.
|
||||
`Building or downloading a deploy ramdisk image`_.
|
||||
|
||||
Using proxies for image download in agent drivers
|
||||
=================================================
|
||||
@ -125,3 +125,4 @@ example, the below command sets this configuration in a specific node::
|
||||
|
||||
ironic node-update <UUID or name> add driver_info/deploy_forces_oob_reboot=True
|
||||
|
||||
.. _`Building or downloading a deploy ramdisk image`: http://docs.openstack.org/project-install-guide/baremetal/draft/deploy-ramdisk.html
|
||||
|
||||
@ -53,7 +53,7 @@ None.
|
||||
Configuring and Enabling the driver
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
1. Build or download a deploy image, see :ref:`BuildingDeployRamdisk`
|
||||
1. Build or download a deploy image, see `Building or downloading a deploy ramdisk image`_.
|
||||
|
||||
2. Upload these images to Glance::
|
||||
|
||||
@ -113,3 +113,5 @@ References
|
||||
==========
|
||||
.. [1] Python-seamicroclient - https://pypi.python.org/pypi/python-seamicroclient
|
||||
.. [2] DiskImage-Builder - http://docs.openstack.org/developer/diskimage-builder/
|
||||
|
||||
.. _`Building or downloading a deploy ramdisk image`: http://docs.openstack.org/project-install-guide/baremetal/draft/deploy-ramdisk.html
|
||||
|
||||
@ -91,7 +91,7 @@ Setting up development environment
|
||||
``/etc/ironic/ironic.conf``, and restart Ironic conductor.
|
||||
|
||||
* Set up flat networking on ``eth1``. For details on how to do this, see
|
||||
:ref:`NeutronFlatNetworking`.
|
||||
`Configure Networking to communicate with the bare metal server`_.
|
||||
|
||||
* Enroll a VirtualBox node. The following examples use the ``pxe_vbox``
|
||||
driver.
|
||||
@ -117,3 +117,5 @@ Setting up development environment
|
||||
Ironic (during provisioning), VirtualBox will automatically pop up a
|
||||
dialog box asking to 'Select start-up disk'. Just press 'Cancel' to
|
||||
continue booting the VM.
|
||||
|
||||
.. _`Configure Networking to communicate with the bare metal server`: http://docs.openstack.org/project-install-guide/baremetal/draft/configure-integration.html#configure-networking-to-communicate-with-the-bare-metal-server
|
||||
|
||||
Loading…
Reference in New Issue
Block a user