Bug 1317022 - add to the documentation an exemple of openstack deployment through REST api
add to the documentation an exemple of openstack deployment through REST api
Status: NEW
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation (Show other bugs)
5.5.0
All All
unspecified Severity medium
: GA
: cfme-future
Assigned To: Red Hat CloudForms Documentation
Red Hat CloudForms Documentation
doc
:
Depends On: 1297335 1335471
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-11 12:42 EST by Felix Dewaleyne
Modified: 2016-10-11 12:03 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Felix Dewaleyne 2016-03-11 12:42:16 EST
Description of problem:
as raised in a customer case attached to this ticket, we do not include enough exemples in document https://access.redhat.com/documentation/en/red-hat-cloudforms/version-4.0/red-hat-cloudforms-rest-api/#sect_provisioning_requests

we should include more details about the possible values or guidance on where and how the person reading the document can find and build the query depending their needs.

Document URL: https://access.redhat.com/documentation/en/red-hat-cloudforms/version-4.0/red-hat-cloudforms-rest-api/#sect_provisioning_requests

Section Number and Name: 3.5 - provision requests

Describe the issue: 

 - not all elements used in cloudforms are listed there and there ; there is no mention that other elements and how to find out some values have to be passed in some way (e.g. cloud_networks for openstack).

Suggestions for improvement: 

amend the documentation to mention that not all elements are listed and give general guidance to locate a value and how to provide it in the api call

Additional information:

Note You need to log in before you can comment on or make changes to this bug.