This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: If914b6973758c46d7d7b973fa39d159a45439521
The new stable upper-constraints file is only available
after the openstack/requirements repository is branched.
This will happen around the RC1 timeframe.
Recheck and merge this change once the requirements
repository has been branched.
The CI system will work with this patch before the requirements
repository is branched because zuul configues the job to run
with a local copy of the file and defaults to the master branch.
However, accepting the patch will break the test configuration
on developers' local systems, so please wait until after the
requirements repository is branched to merge the patch.
Change-Id: If1f8db57cbf55b006ba4a772b8b44c51e08427a2
Use openstack-tox-cover template, this runs the cover job
in the check queue only.
Remove jobs and use template instead.
Change-Id: I28111ced5dececccaa38e0033aac920279c45381
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ib8ea06691a7082d43db336070e60b415941677e5
Story: #2002586
Task: #24312
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: I8229b64e652d27c72248659ff1bcbcd69f874865
Story: #2002586
Task: #24312
We will manage the eventlet version using constraints now. See the
thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html
for more details.
Additionally:
* remove lower constraint for oslo.config
* remove lower constraint and exclusion for reno
Change-Id: I187a6bd4eedcc139383efc25b6dbffe1c8cd39bc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I82b0b798da177404ca2a73b22c23906c7c22afbc
Provide basic endpoint:
/v1.0/events/
/healthcheck
/version
Endpoint reads request and returns HTTP code 200.
Provide code to run application in gunicorn mode.
Story: 2001112
Task: 4863
Change-Id: Ic7c344360b5acec5af7751a825e2dff8346cf1f7
Depends-On: I18d9f4ec543c76bfe1311ed1ee940827d4162298
'pip install -U' ugrades specified packages, this is not necessary
since we use constraints, remove the parameter '-U' from the line.
With tools/tox_install.sh - which a previous change of mine removed -
the -U was not harmful, but with the current set up, it might cause
upgrades, so remove it.
Change-Id: Ib894a4a99bef001183b892fcf53708f5d699db4d
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: I8732c7032bd45ce1186f3751f4953348ef4ef1cc
Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated. Update references
to include the extension.
Change-Id: Ica021c2913cb4866b10b8014333e36df9d7dfc5d
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: I6158691a389bd8a6c16253284673b3d621907080
!Parts of code taken from monasca-api and monasca-log-api!
Also create a dummy implementataion for version endpoint
so that the deployment can be tested.
Story: 2001112
Task: 4808
Change-Id: Ic35f6388c34c4d4c1198401a1c6972b802a54c67
Provide new endpoint to monasca-events-api.
Endpoint accept events in a bulk mode.
Provide HTTP response codes and examples about request
body.
Story: 2001112
Task: 4803
Change-Id: I18d9f4ec543c76bfe1311ed1ee940827d4162298
Add policies to the api based on oslo.policies.
Small changes in documentation. Provide generator for
sample policies file.
Add policies for agent and admin.
Story: 200112
Task: 4807
Depends-On: I76d737bf9d1216b041bc1a518cc2098f28e7da7b
Change-Id: Idf5c4ec1b663ad9ed3ab25744bdf0b7f28cdb1a2
Following change aims at setting up the
tooling for events-api againts latest
requirements and guideliness from OpenStack.
Removing old code , add basic structure of the python
modules. Add basic documentation and release notes.
Prepare to use oslo-config-generator.
Add devstack basic setup to the project.
Story: 2001112
Task: 4798
Change-Id: I76d737bf9d1216b041bc1a518cc2098f28e7da7b
OpenDev Sysadmins
OpenStack Release Bot