When using ctags, it will provide a 'tags' file in the directory.
It should be added to .gitignore.
Change-Id: Iaffac082948745c1b9171834504234570b795065
As Cyborg is switching to new policy, this is required
to avoid breaking the existing deployment using policy
file in json format and relying on default value of
'CONF.oslo_policy.policy_file'.
Default value of 'CONF.oslo_policy.policy_file' config option
has been changed from 'policy.json' to 'policy.yaml'. If new default
file 'policy.yaml' does not exist but old default 'policy.json' exist
then fallback to use old default file.
An upgrade checks is added to check the policy_file format and
fail upgrade checks if it is JSON formatted.
Added a warning in policy doc about JSON formatted file is deprecated,
also removed all the reference to policy.json file in doc as well as
in tests.
Related Blueprint: https://blueprints.launchpad.net/oslo.policy/+spec/policy-json-to-yaml
Change-Id: I865227e516dc7505c463ac279309169d95ea6a22
In this U version, Improve UT for important Cyborg module is
an important task.
It is necessary to add openstack-cover-jobs to zuul. This way
we can easily view the unit test coverage of each file.
such as nova:
https://github.com/openstack/nova/blob/master/.zuul.yaml#L374
Change-Id: I854a51a2105628c5e5e9c30282e0f4b259c33ed3
Once all the ARQs for an instance have either bound or failed to bind,
Cyborg sends a notification event to Nova indicating success
or failure.
Change-Id: I05cce190d328ae16738959ba806d13a5ae99053c
Ensure the documentation is kept up to date by automatically
generating it from the source when the docs are built.
This patch:
1.replace oslosphinx with openstackdocstheme since oslosphinx is obsolete
2.add oslo_config.sphinxconfiggen to generate sample conf file
3.add oslo_policy.sphinxpolicygen to generate sample policy file
Change-Id: I39f03023f0a85e4c8943925268ab3e9066975630
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I8b0f96f05799b892acfae03522726c17010f0df3
The concept of quota gives the possibility to limit the maximum number of
acceleration resources that one project/tenant can prossess.
It will also give the admin users the ability to increase the resource count
on-demand, given that the system constraints are not exceeded.
Change-Id: I554b9d4603d5e65f69c2b924fba66565f7f6c3c4
Partially-Implements: blueprint cyborg-resource-quota
This is not needed to be under version control, remove it.
pbr generates it automatically as needed.
Change-Id: I76abd7738448034d9cabe2bcc39564af9976512c
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
songwenping