Bug 1170154

Summary: [RHCI] Implement feedback from review of the newly created use case articles
Product: Red Hat CloudForms Management Engine Reporter: Andrew Dahms <adahms>
Component: DocumentationAssignee: bmoss
Status: CLOSED CURRENTRELEASE QA Contact: Andrew Dahms <adahms>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.4.0CC: dajohnso, lcarlon, mfeifer, obarenbo, xlecauch
Target Milestone: GA   
Target Release: 5.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-06 00:24:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1174605    
Deadline: 2014-12-18   

Description Andrew Dahms 2014-12-03 12:35:06 UTC
The following feedback has been received regarding the newly created RHCI use case articles, and must be implemented -


Providers (https://access.redhat.com/articles/1278483)
* 1. Number of hosts
  * seems slightly shifted to the right
* Authenticating Red Hat Enterprise Virtualization Hosts
  * Should this be part of the hosts article?


Hosts (https://access.redhat.com/articles/1278513)
* Discovering hosts is only supported for standalone vmware esx servers, we should probably note that somewhere


Provisioning (https://access.redhat.com/articles/1278573)
* The web interface uses virtual thumbnails to represent...
  * By default, the web interface.....
  * Not sure if you want to mention this, but this is configurable on the Configuration > My Settings page
* 1. Operating system of the Virtual Machine
  * Does it seem shifted to the right slightly?
* Post-processing activates the VMDB instance and emails the user.
  * Emails only if notifier server role is enabled and smtp settings are configured
* Click the Environment tab and select Choose Automatically in the Placement field to let CloudForms Management Engine choose where the new virtual machine resides.
  * Auto-placement only works if environment objects are tagged with provisioning scope tags.
  * Assuming this is for a quick, start... note that ^ but tell them to select specifically where to place the new vm
* Click the Network tab and select rhevm as the vLan adapter.
  * So this seems to have a assumption of working with RHEV?
* To select an appropriate template, choose from the list in the custom specification area.
  * Should we point to where these are defined?
* After a user creates a provisioning request, an administrator must approve the request before provisioning begins.
  * This is wrong.  Users can provision a single instance which will be pre-approved.  If they choose to provision more than one instance at one time, they will need to be approved by a administrator.
  * Not sure if you want to mention this, but it is configurable in the Automate.

Comment 3 bmoss 2014-12-19 02:11:31 UTC
Providers (https://access.redhat.com/articles/1278483)
* 1. Number of hosts
  * seems slightly shifted to the right

- It does.  Unfortunately, it appears that this is how KBase renders numbered lists.  I've filed a bug asking them to adjust the alignment: https://bugzilla.redhat.com/show_bug.cgi?id=1175022

-----

* Authenticating Red Hat Enterprise Virtualization Hosts
  * Should this be part of the hosts article?

- I added this section to the hosts article, with appropriate changes as the user may not be accessing the option from Infrastructure -> Providers

-----

Hosts (https://access.redhat.com/articles/1278513)
* Discovering hosts is only supported for standalone vmware esx servers, we should probably note that somewhere

- Edit: "CloudForms Management Engine automatically adds hosts from discovered providers. However, you can also discover hosts directly if not using a provider. Discovering hosts is only supported for standalone VMware ESX servers."

-----

Provisioning (https://access.redhat.com/articles/1278573)
* The web interface uses virtual thumbnails to represent...
  * By default, the web interface.....
  * Not sure if you want to mention this, but this is configurable on the Configuration > My Settings page

- Added "By default".  In this article we won't mention that it can be configured, as these use cases are intended to be as streamlined as possible, providing one path to complete the task.

-----

* 1. Operating system of the Virtual Machine
  * Does it seem shifted to the right slightly?

- It does.  Looks like the same rendering issue as in the providers article.

-----

* Post-processing activates the VMDB instance and emails the user.
  * Emails only if notifier server role is enabled and smtp settings are configured

- removed the reference to email

-----

* Click the Environment tab and select Choose Automatically in the Placement field to let CloudForms Management Engine choose where the new virtual machine resides.
  * Auto-placement only works if environment objects are tagged with provisioning scope tags.
  * Assuming this is for a quick, start... note that ^ but tell them to select specifically where to place the new vm

- Edit:
  "Click the **Environment** tab. As automatic placement can only be used if environment objects are tagged with provisioning scope tags, you must select a location for the requested VM manually.
  a. Datacenter: select Default
  b. Cluster: select Default
  c. Host: select the desired host
  d. Datastore: select the desired datastore"

-----

* Click the Network tab and select rhevm as the vLan adapter.
  * So this seems to have a assumption of working with RHEV?

- Yep, the RHCI docs target the components of RHCI (Satellite, RHEV, RHEL-OSP, CloudForms).

-----

* To select an appropriate template, choose from the list in the custom specification area.
  * Should we point to where these are defined?

- Added "You can create and edit customization templates by navigating to Infrastructure -> PXE, and selecting Customization Templates from the accordion menu."

-----

* After a user creates a provisioning request, an administrator must approve the request before provisioning begins.
  * This is wrong.  Users can provision a single instance which will be pre-approved.  If they choose to provision more than one instance at one time, they will need to be approved by a administrator.
  * Not sure if you want to mention this, but it is configurable in the Automate.

- Updated to clarify that a single instance request is pre-approved, but that a multi-instance request requires admin approval.  Configuring request approval is outside the scope of this article.

Comment 4 Andrew Dahms 2015-01-06 00:25:42 UTC
Checked in:

https://access.redhat.com/articles/1278483
https://access.redhat.com/articles/1278513
https://access.redhat.com/articles/1278573

The requested changes have been made, and all notes in the above comment noted.