The following feedback items were provided during review of the Bare Metal Provisioning document. The items should be considered and applied, where appropriate, to the documentation.


In A.6. SSH AND VIRSH

I think it may confuse customer to mention about libvirt suddenly at this section.

Can we explain about 2 types of provisioning on real server and on VMs on libvirt before hands , if possible?

""
Bare Metal Provisioning can access a host that is running libvirt and use virtual machines as nodes. Virsh controls the power management of the nodes.
""

Also, if possible it may be nice if we mention about libvirt way in Director's installation document ( https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/index.html#sect-Scenario_1_Using_the_Web_UI_to_Create_a_Test_Overcloud ) or upstream ? ( http://docs.openstack.org/developer/tripleo-docs/basic_deployment/basic_deployment_cli.html ) since it's overwrapped.

And will we have any minimum system requirement section for libvirt , for real server ?

For VM, like this:
http://docs.openstack.org/developer/tripleo-docs/environments/virtual.html

Also, it may be sort of offtopic, but can we explain about osp director , tripleo and ironic , if possible to clarify the whole picture of this solution ?