TritonDataCenter / TritonDataCenter/node-triton

`triton start -w --snapshot SNAPNAME INST` doesn't wait for the reboot

Open
#96 0 comments 0 reactions 1 assignee View on GitHub

@marsell is already working on this.

Since Mar 1, 2016.

Dominant language
JavaScript
Stars
60
Forks
36
Avg merge
3d 8h
Merged PRs (30d)
1

Description

    $ triton start -w --snapshot 20160209T23089Z trent0
    Start instance trent0 (35c66e4e-7b61-4197-8038-8883b776cafe, 884ms)
    $

This didn't wait at all. MachineAudit doesn't have exposed (job) ids, so it would
be flaky to use. Polling on 'state' naively fails immediately on the first
GetMachine. Perhaps it could require that INST.updated changes to know that a
current running state is not the rebooted instance.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.