ocurrent / ocurrent/ocurrent-deployer

Migrate unikernel builds to cluster

Open
#58 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
OCaml
Stars
24
Forks
18
Avg merge
16m
Merged PRs (30d)
2

Description

I've moved all the Docker services from the old deployer on toxis to the new one on ci3.

The only thing the old service is still doing is deploying the unikernels. This code is now on the old-master branch.

The old service builds the unikernels locally with Docker and then rsyncs to the host. However, the new deployer host isn't suitable for building things. Instead, it should use the cluster. We need to decide how to get the resulting binaries from the workers to the host.

Some options:

  1. Push to Docker hub and have the unikernel host pull them (requires Docker on the host though).
  2. Have the worker transfer directly to the host (will probably want some kind of short-lived session key for the transfer).
  3. Transfer from the worker to the deployer and rsync from there as before. Avoids having to make changes on the unikernel host.

@hannesm do you have a preference here? I think you mentioned that you were planning some kind of unikernel registery which we could push to...

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.

Research direction

Start by reviewing the deployer code on the old-master branch and comparing the old service on toxis with the new deployer on ci3. Evaluate the three listed ways to transfer unikernel binaries, then verify that builds run on the cluster and the resulting binaries reach the unikernel host.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, ocaml
Domain
build-system, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.