API Content Gaps stx-metal

[Abraham Arce]

Brief Description
-----------------
As a result of time spent within stx-metal, there are API reference content gaps

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
Written down in http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/002032.html

Expected Behavior
------------------
Waiting for your comments and changes to fix either the code or the API reference documentation.
See our API Contributor Guide: https://docs.starlingx.io/contributor/api_contribute_guide.html

Actual Behavior
----------------
Stated in http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/002032.html

Reproducibility
---------------
100% Reproducible.

System Configuration
--------------------
Controller Storage

Branch/Pull Time/Commit
-----------------------
Any

Timestamp/Logs
--------------
See http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/002032.html

[Ghada Khalil (gkhalil)]

Marking as release gating; missing API documentation.

Assigning to Abraham to address or to hand off to the right person in the doc team.

[Ghada Khalil (gkhalil)]

This may already be covered by:
https://storyboard.openstack.org/#!/story/2004877

If so, I suggest marking this bug as Invalid

[Abraham Arce (xe1gyq)]

Hi Ghada,

Reason to raise this bug is keep track of our mailing list discussion, once we have an answer from stx-metal team we can close based in their feedback to our email:
http://lists.starlingx.io/pipermail/starlingx-discuss/2018-November/002032.html

Yes, https://storyboard.openstack.org/#!/story/2004877
is the place where we are tracking these changes. stx-metal story 29152 to be assigned once we have a clear path to changes needed.

[Erich Cordoba (ericho)]

I sent a reminder to the mailing list trying to get the feedback from the community.

[Abraham Arce (xe1gyq)]

Any objection to close this bug?