Bug 1339605 - [API] use case for accepting a node via API is not clear and should be fully documented
Summary: [API] use case for accepting a node via API is not clear and should be fully ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3
Assignee: gowtham
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1298114 1312404
TreeView+ depends on / blocked
 
Reported: 2016-05-25 12:37 UTC by Martin Bukatovic
Modified: 2017-03-23 04:05 UTC (History)
4 users (show)

Fixed In Version: rhscon-core-0.0.34-1.el7scon.x86_64 rhscon-ceph-0.0.33-1.el7scon.x86_64 rhscon-ui-0.0.47-1.el7scon.noarch
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 04:05:15 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1312404 0 unspecified CLOSED [API] tasks Accept Node finish before node is actually ready 2021-02-22 00:41:40 UTC

Internal Links: 1312404

Description Martin Bukatovic 2016-05-25 12:37:50 UTC
Description of problem
======================

The process of accepting a node via skyring REST API is not straightforward
and so we need to document this use case with extra care.

For the sake of the BZ, all API calls related to the process needs to be
documented, and an example with full description of the process should be
given in a separate section of the API documentation.

Version-Release
===============

rhscon-core-0.0.19-1.el7scon.x86_64

Comment 2 Martin Bukatovic 2016-06-23 14:43:36 UTC
(In reply to gowtham from comment #1)
> Documentation link:
> 
> https://github.com/skyrings/skyring/wiki/Node-Acceptance-and-Initialization-
> Guide

Thanks for documenting the use case. QE team is going to review it and then
change component of this BZ to documentation, as the doc team would have an
upstream docs to evaluate and reuse to create downstream docs. Moreover based
on decision done for BZ 1298114, we will move this BZ out of rhsc 2.0.


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