Interestingly, there's a race condition here. After the bootstrap finishes (status = SUCCESS), the new host(s) don't always show up in GET /api/v1/hosts immediately. Is this a bug or is there something else I need to be doing?
Greg On 8/25/14 8:52 AM, "Greg Hill" <[email protected]> wrote: >Thanks Yusaku, this helps. I'm working on adding the ability to poll >long-running tasks from the python client, so I'll smooth over the >differences in the client so it's not obvious to the end user. > >Greg > >On 8/22/14 7:55 PM, "Yusaku Sako" <[email protected]> wrote: > >>Hi Greg, >> >>Unfortunately, the bootstrap API is a bit unconventional and does not >>follow the standard API framework. >>To check on the bootstrap status, you just need to make a GET call >>like this: /api/v1/bootstrap/1 (replace 1 with the requestId returned >>by the POST /api/v1/bootstrap call). >>I hope this helps. >> >>Yusaku >> >> >>On Fri, Aug 22, 2014 at 12:26 PM, Greg Hill <[email protected]> >>wrote: >>> The bootstrap hosts method returns a request id, but that request isn't >>>associated with any cluster. How do I get the status of it? There >>>aren't any API docs I can find for the bootstrap method. >>> >>> Thanks in advance. >>> >>> Greg >>> >> >>-- >>CONFIDENTIALITY NOTICE >>NOTICE: This message is intended for the use of the individual or entity >>to >>which it is addressed and may contain information that is confidential, >>privileged and exempt from disclosure under applicable law. If the reader >>of this message is not the intended recipient, you are hereby notified >>that >>any printing, copying, dissemination, distribution, disclosure or >>forwarding of this communication is strictly prohibited. If you have >>received this communication in error, please contact the sender >>immediately >>and delete it from your system. Thank You. >
