Task #6875
closed
Task #6869: Challenge OpenStack and OpenNebula with ucloud
Create ucloud-scheduler
Added by Nico Schottelius over 5 years ago.
Updated almost 5 years ago.
Description
Reads / watches keys below /v1/vm (later probably as well /v1/networks?)
The JSON of the VM should contain a "status" field. On submit, the status should be "REQUESTED_NEW" (-> need to update ucloud-api).
Creating VM¶
The scheduler watches for changes on the key prefix. If the status is REQUEST_NEW, find a suitable host for deploying the VM to.
Update the status field to "SCHEDULED_DEPLOY". Also add a new field "host" that contains the hostname of the host the VM should be running on.
Deleting VM¶
The scheduler watches for changes on the key prefix. If the status is REQUEST_DELETE, do nothing -> ucloud-vm needs to react and will update the field.
APIs¶
ucloud scheduler only reacts on etcd changes and does not have a direct accessible API.
- Status changed from New to Seen
To be solved / undefined at the moment:
- Which component writes information about hosts? Do we have a key prefix /v1/host/<id>?
- If yes, do we need ucloud-host?
- Or do we use (existing) consul?
- consul is indeed an alternative to etcd for us as well
For the start:
- Create /v1/host and fill it up manually -- Balazs might also have some ideas on this
- Status changed from Seen to In Progress
Now, using etcd3 instead of using coreos/etcd python binding because the latter does not have support to watch a prefix e.g /v1/vm
This has implication that we can't access etcd v2 data from v3 API and vice versa. So, instead of usual `etcdctl` we need to use `ETCDCTL_API=3 etcdctl`.
v1 is ready. It can be found here
@william and @llnu is notified to verify its working.
- % Done changed from 0 to 50
- Status changed from In Progress to Waiting
- Status changed from Waiting to Feedback
- Status changed from Feedback to In Progress
- Status changed from In Progress to Closed
Also available in: Atom
PDF