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: I61d325e02dbc0fad1c964aedbe6ff861ddd2bdc7
Synergy:
- fix small typo preventing it from running
Packaging:
- RPM: more specific python dependencies, to make it easier to install
on CentOS 7
- update python-ova dependency to Newton (v14)
- update synergy-service dependency to 1.5
Change-Id: I7c583805cf60298a2af2c032cacc55affcabf474
This commit updates the packaging files for supporting the new
authorization mechanism based on policy.json
Change-Id: I001fba11b9c59ef34a10bf92ab7241f37efd4668
Sem-Ver: feature
Update the required version of synergy-scheduler-manager
Change-Id: I7eb35a6acd96ce29d748a0b68a82dd42717cd80f
Depends-On: I03bbb3d795a8e771ee5a35a085078cc8301f8208
This fix update the Dockerfile for building synergy-scheduler- manager package on Ubuntu 16.04.
Change-Id: I03bbb3d795a8e771ee5a35a085078cc8301f8208
Sem-Ver: bugfix
This fix updates the packaging of synergy scheduler manager making it compliant with the indigo-2 requirements.
Change-Id: I7b74952a635cf097eb7c8d3d14176fa39dc43c74
Sem-Ver: bugfix
Small tweak to the docker CLI invokation when packaging to make it less
verbose.
Related: Ida07b3b439949fe83066039350647901693d4816
Sem-Ver: bugfix
Change-Id: I6a9bc7d3686a1b116d664db77f072b004b30fd25
The Scheduler manager should specify all configuration parameters on a
dedicated configuration file.
Bug: #1663589
Change-Id: I7ceb140182db306567d7f7a6b5bfcf0871249a05
Sem-Ver: feature
When packaging, we can now pass a PKG_VERSION environment variable to
docker to force which version is being packaged.
If this variable is not passed to docker, then the version is the latest
git tag.
Change-Id: Id24a076794006ba7675ff5cc320115108b60dee2
Also update requirements accordingly for the synergy-synergy
dependency.
Change-Id: Iaaff96ee6b57f0745d8de5ad905bec18ccd9a795
Depends-On: If18e6decc4b21ddaa230c4be3819dfe1c24cf5f4
Requirement versions were set in the first place to limit the
buginess. However, after some time it appears that it made more
harm than good, as discussed in:
https://review.openstack.org/#/c/388003/
In this commit we remove the versions for the requirements, except
for the following:
- Nova
- synergy-service
In the future, if a specific dependency version is causing some issue
we should reintroduce the version for this dependency to block the
unstable version.
Sem-Ver: bugfix
Change-Id: If65e670a18a495a5c3f5c08c80b6b1d3abec5747
See this synergy-service commit for the corresponding change:
https://review.openstack.org/#/c/387931/
2e15008a9e69ec16e5f39df9fe216fd392b006a2
Change-Id: I4a26b5f2f8ec703ce3456fa2568e7233c2d1b310
Sem-Ver: bugfix
See the corresponding commit for synergy-service:
https://review.openstack.org/#/c/387882
Change-Id: Ia3f476ef4a7de17200e07a151255afa0c9fad02b
Sem-Ver: bugfix
For CentOS7, we use dependency pinning in the spec file. Note that we
don't do it for Ubuntu as it will use the dependency versions from the
requirements.txt.
We now use the compatible release operator [1] to define versions in
the requirements.txt.
[1]: https://www.python.org/dev/peps/pep-0440/#compatible-release
Change-Id: I33712b923b4d59c09014fa6fcc19c0929df547eb
Ian Wienand