More patches might follow
Update 0(pacth 1):
1.remove unnecessary files
2.reorg doc directory
Update 1(patch 2):
add releasenotes and cleanup the internal-api spec
Update 2(patch 3):
1.added a new releasenote for generic-driver
2.fixed errors in the other four earlier releasenotes
3.add comment in cyborg/object/accelerator.py and deployable.py to
let user better know the meanings of the table entries.
Change-Id: I45a104f9f77a0a163008657c681cf109f941dd11
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
Dramatically revised from this
https://review.openstack.org/#/c/448228/3/specs/proposal/cyborg-nova-interaction.rst
My goal with this spec is to have it be only where we interact with nova without
details of other components, otherwise we just get into a monolithic spec for
everything.
I plan to expand this into exact api calls and a detailed workflow, especially
for the new API call we will have to make in nova to register whitelisted
devices live. That being said we may need to reboot the machine to change the
grub config anyways so maybe we should be looking at how to make that work
first.
Change-Id: I22037109b613d7b33d7c620b78493ec7e96e735e
In a general, Cyborg, as the hardware (like FPGA) and software
(like DPDK, SPDK) acceleration framework, can help backend to
improve performance. And SPDK driver can help Cyborg to manage
SPDK accelerator through calling the py-spdk[0].
Based upon the above reasoning, this patch accomplish two things:
(1) When Cinder uses Ceph as its backend, the Cyborg SPDK driver
can discover, list the SPDK accelerator backend.
(2) When Cinder directly uses SPDK blobstore as its backend, the
Cyborg SPDK driver can discover, list, attach, detach and update
the SPDK accelerator backend.
[0] https://review.gerrithub.io/#/c/379741/
Change-Id: I76a40327bf5c267888fd6293f0ed918bc8cca7ae
Signed-off-by: heluwei <heluwei@huawei.com>
Several clean up performed in this patch:
* remove readme in the doc/source
* move installation.rst and usage.rst to the new userdoc/
* add api.rst to userdoc/
* add introduction.rst in doc/source
* add index.rst in every folder
* add release info in every spec
Change-Id: I9ea96993f916b753cc1aa16c2ea2983b93922f23
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
This spec proposes the initial design for the
cyborg api. The cyborg api should support the basic
operations concerning accelerators, and does not
necessarily have to be user facing api at the early
stage.The api should support functionalities such as
provision, attach, detach, list and update.
This spec also contains the proposal for a simple DB for
Cyborg. Note that although we propose a DB schema for Cyborg,
in implementation it should be aligned with resource provider
db schema as much as possible.
APIImpact
Change-Id: I98c74df91f4548ecef42d2e3f96facf9023a346a
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
Cyborg Agent resides on various compute hosts and monitors them for accelerators.
If an accelerator is present but not setup Cyborg Agent will notify the operator
that intervention is required. If the accelerators are prepared for use Cyborg
Agent will begin monitoring their status and reporting it to Cyborg Conductor
which will manage use this information to assist with scheduling and operation.
Change-Id: I9596297b8fc64571035d800a24c3e54142dfb0e2
This is the straightfoward spec for the Cyborg conductor,
responsible for handling database interaction and general
statefullness in the API.
Change-Id: I80a1a87d69fee43fc62cb33b9b8b218b6ed10813
This patch also contains the rock proposal from Huawei,
other approved proposals will go into sandbox/ in the
following patches.
Change-Id: I045e4c15c09cb9d827398b552619d8ea9772b38e
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
zhipengh