Closed Bug 1508790 Opened 6 years ago Closed 5 years ago

Write provider for packet.net

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: coop, Assigned: wcosta)

References

Details

Now that we are running production workloads in packet.net, we need to stand up a real provider so we're only paying for useful capacity. Based on the series of bugs filed for the GCP provider, the packet.net will require the following methods: * request an instance (bug 1487694) * terminate an instance (bug 1487695) * suggest bids (bug 1487696) * accept bids (bug 1487697) * derive credentials (bug 1487698) * list instance status (bug 1487699) The bidding portion can likely be pretty naive at this point until we have more experience with packet.net pricing. Wander: I suspect you can make some progress here even in the absence of the dependent bugs being fixed. Playing with the packet.net API would be a good first step.
Depends on: 1509311
Depends on: 1522850
Depends on: 1522852
Depends on: 1523264
Depends on: 1523569
Component: AWS-Provisioner → Services

I just want to highlight bug 1523569 as a big dependency here. We currently spin up instances from scratch when we need them and that's too inefficient for the provider model.

Blocks: 1554706
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.