This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Iae87fbc18b7b14bca10e043b5438892259f5fc3c
Story: #2002586
Task: #24291
add api unit test to validate the accelerator_post function.
1. load a test app for pecan framework test
2. mock out the accelerator_create function in Conductor RPCAPI
3. post test request to '/accelerators' endpoint
4. do the check between request and response
Change-Id: I5d565d0d7ed56c27555666e52e34f5fd67005dcf
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>
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: I5644f38cf56f1e3b6a31252523a3bf28248e9f08
Add authtoken middleware for integrating with the OpenStack Identity API
and handling authorization enforcement based upon the data within the
OpenStack Identity tokens
Change-Id: I8056d69657d0a98b4446a494877f7b965ceb786f
Add release note for Pike and architecture documentation
and diagram.
Change-Id: Ia5756ed7acf176f3910dfe2436da8186467377c8
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
This deploys cyborg services across various hosts and sets them up
as boot time services configured to access the local rabbit and mysql
instances and then runs some validations to ensure
that everything started correctly.
This does not have any saftey for multi-controller setups yet, right now
if you hand the playbook 3 hosts under 'controller' it will deploy three
api endpoints and three agents. Which probably won't work right.
Change-Id: I79b6b1ce9bb6766d5e608c89504c4bbaeaba5599
So right now flake8 is in our tox.ini but not in the upstream
infra config. Meaning if you run tox locally with the hope of
finding and fixing linter errors in your patch you get about
100 lines of docstring errors that aren't actually enforced
when you upload your patch to gerrit. We need to either chose
to enforce those rules on gerrit (and write a lot of docstrings)
or change the tox.ini to reflect the actual gates better so that
we can more easily debug locally.
Change-Id: Id0456f53d176eb1d13c3bc22ef43b62772a86b89
add these for further expansion:
1. give an initial version of v1 to api service,
2. add Config and PublicUrl hook to app.
3. add resource endpoint in response body.
Change-Id: I2b84508a07bbbf0f5133c828a8217a23398564db
This commit adds sqlalchemy as a database backend, the database connection
url is loaded from the config file in the same format as any other service.
The accelerator class has been given tags that allow sqlalchemy to map it to
a table in the database and perform saving out/queries automatically.
For further work I'll want either an api or a driver to start integrating with
don't want to get too deep into buisness logic before we know exactly what those
will look like.
Change-Id: I6a9712de0b4f985bab80178845f59e10c05032a5
This is a set of stubs for the Cyborg conductor with working
rpc and message handling although nothing really
to do with those messages until the DB component is formalized
and created in the next patch.
Change-Id: I0df68a165881697c7b199189a89471baf9ece2af
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>
So I think this has the most functionality we can expect of a stub
at this point, it accepts a configured transport URL and node id
then takes rpc commands to modify the state of the agent.
What needs to be added is a accelerator handler class that runs
in the main loop to perform the various ongoing tasks of the Agent
but I can't really write that until I have a driver to link against.
Change-Id: I35438c01ca2765ca3dd2575bf2fac63099a30d29
Since I want this to be a common class shared between each
component I split it out into it's own commit to be merged
in stub form so that we can each rebase on it and extend
with our own functions/properties as required.
Change-Id: I0f396afcc4c4ae38183ce85414ba3d8741279103
The directory openstack/common was used to keep codes from oslo-incubator,
we have retired oslo-incubator,so don't use this directory any more.
Change-Id: I288970e37f67c8bdf5da172f55919700fd5ee134
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
OpenDev Sysadmins