During a recent installation of Synergy on a standard CentOS 7 cluster
it appeared that python dependencies present in both EPEL and OpenStack
repositories were not installed correctly.
This commit makes the dependencies more explicit and result in a correct
installation procedure.
Note that since the Synergy code has not changed since the last version,
only the package "dist" version is changed.
Change-Id: I1d10fdc7e98788ce83c245aa3606351e358603e1
This fix updates the packaging of synergy service making it compliant with the indigo-2 requirements.
Change-Id: Ide701fe90c23eb4375bcdf9ff9bfd010cd7290ac
Sem-Ver: bugfix
Small tweak to the docker CLI invokation when packaging to make it less
verbose.
Related: I6a9bc7d3686a1b116d664db77f072b004b30fd25
Sem-Ver: bugfix
Change-Id: Ida07b3b439949fe83066039350647901693d4816
Synergy is now expected to work on either CentOS 7 and Ubuntu 16.04.
Both of these OS ship with Systemd so we can get rid of the SysV init
and Upstart scripts we had.
Sem-Ver: bugfix
Change-Id: I8e51acc4c86ee82c2484ee09036f902156580ce0
The synergy.conf must configure just the service whereas the
managers must be configured with separate configuration files.
- removed all scheduler managers sections
- added support to read all configuration files in /etc/synergy
- removed service automatic restart after installation or update
bug #1663581
Depends-On: I7ceb140182db306567d7f7a6b5bfcf0871249a05
Sem-Ver: feature
Change-Id: I4491606402314d29363420aeb5cb943ae3a9090f
On CentOS 7, upgrading Synergy would cause the Synergy log file to be
overwritten. We fix this behaviour in this commit.
Note that now the Synergy log file is created during Synergy first run,
not during the first installation of Synergy.
fixes bug #1664502
Sem-Ver: bugfix
Change-Id: Id1a4fc3871a141f1d5fd0f2c95c10464e86dda8e
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: I8863d6a101e8d85573d8547bab1a667060648018
- pbr was not installed, but is now required.
- clean .eggs directory
- update packaging doc for CentOS
Sem-Ver: bugfix
Change-Id: I6a1ec486847a28f76283b8acb96c56af6a5e4e4c
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 all the requirements.
In the future, if a specific dependency version if causing some issue
we should reintroduce the version for this dependency to block the
unstable version.
Sem-Ver: bugfix
Change-Id: Ia42509bf2bf9012cc03c8bb25b84f465425e2aad
It was missing git, which is necessary since we now rely on it to get
the current version of synergy-service.
Change-Id: Ifd334dd646ca9e9629e9224163f01380c2e5f1b6
Sem-Ver: bugfix
The required version for CentOS was 0.18, but only 0.17 is available
in the repositories.
Change-Id: I94ced14b0f0c520e431c7ef2fd94c11d6721af9c
Sem-Ver: bugfix
Commit 670f608252 introduced this bug.
We previously relied on the "version: " line of setup.cfg, but this
was removed due to using pbr.
We now get the synergy version from the git tag.
Change-Id: I31fc9215269b05acabba8c4288af540f4de9c0c4
Sem-Ver: bugfix
- ubuntu Dockerfile didn't have the Ubuntu OpenStack repository.
- required version of setuptools was too high wrt the versions
available for CentOS and Ubuntu.
Change-Id: I7ab657e53e48658c08c02020256be97cd5d3af66
Sem-Ver: bugfix
As per RPM documentation, it is advised to not clutter the output
when removing packages.
This commit fixes this by redirecting the errors to /dev/null,
effectively getting rid of errors like:
```
userdel: synergy mail spool (/var/spool/mail/synergy) not found
userdel: synergy home directory (/home/synergy) not found
groupdel: group 'synergy' does not exist
```
Change-Id: I41508c13e971b3740d3e37448b62d5a9b841db37
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.
This commit also removes non relevant warnings when uninstalling
Synergy.
[1]: https://www.python.org/dev/peps/pep-0440/#compatible-release
Change-Id: Icb1dd16d7d8d7246914058a11534bcd099b1f18c
We get rid of the build_env.sh script that need to be changed after
each release.
This commit also:
- remove unecessary files when packaging (.tox etc...)
- fix CentOS Dockerfile to get the OpenStack repo
Change-Id: Idd8c4004e2ddca33fb779c13a895e2e0afdb9651
Rename bin/synergy to bin/synergy-service.
Add the synergy client command as bin/synergy.
Impact changes to the packaging.
Change-Id: If3b6c3799906a40481c5e0fb4c67de2f6a0ccba9
In addition to importing the project, this commit also includes fixes
to pass PEP8 and unit tests on OpenStack CI.
Commit history that was imported from the launchpad project:
. The first commit's message is:
first Synergy implementation
. This is the 2nd commit message:
added README file
. This is the 3rd commit message:
added new logging configuration support
. This is the 4th commit message:
added new logging configuration support
. This is the 5th commit message:
Synergy repository restructured
. This is the 6th commit message:
Synergy repository restructured
. This is the 7th commit message:
TimeManager
. This is the 8th commit message:
first service implementation
. This is the 9th commit message:
package synergy.managers.scheduler removed
. This is the 10th commit message:
Keystone and MYSQL configuration removed
. This is the 11th commit message:
Clean up setup.py
- remove all directory creation, chmoding, etc. This will be handled by
the system package.
- rename `scripts` as `bin` to follow best practices.
. This is the 12th commit message:
Fix systemd unit file
- remove all the directory creation since it will be done by the system
package.
. This is the 13th commit message:
Move synergy source to parent directory
Follow the standard of having the source package directory at the root.
This also make it easier to work with setuptools.
. This is the 14th commit message:
Add dependencies in setup.py
. This is the 15th commit message:
Add RPM spec file for packaging
. This is the 16th commit message:
debian/ubuntu package
. This is the 17th commit message:
add oslo.log as a requirement
. This is the 18th commit message:
deb pkg: explicit naming for oslo.*
. This is the 19th commit message:
rename deb package to python-synergy-service
. This is the 20th commit message:
fix debian package configure step
. This is the 21st commit message:
remove unecessary init & upstart scripts
We will target Ubuntu >= 15.04 and EL >= 7. Both use systemd by default,
so we do not need initv and upstart scripts.
. This is the 22nd commit message:
changed license field: GPL->Apache 2
. This is the 23rd commit message:
change license to Apache 2 for rpm & deb
. This is the 24th commit message:
rename python package to "synergy-service"
This is the name that will be used on PyPI.
. This is the 25th commit message:
oslo_log dependence removed
. This is the 26th commit message:
remove oslo.log dependency from packaging
. This is the 27th commit message:
remove oslo package renaming
Both python-oslo-* and python-oslo.* are supported on Ubuntu >= 15.04,
but only python-oslo.* are supported on Ubuntu 14.04.
. This is the 28th commit message:
fix oslo imports for Ubuntu14.04
This concerns 2 python packages:
- oslo config
- oslo messaging
Both packages cannot be imported using their "oslo_PKG" name in Ubuntu
14.04.
These packages can be imported on both Ubuntu 14.04 and 15.04 using
"oslo.PKG".
. This is the 29th commit message:
fix manager config setup
We check for manager in the conf file using the oslo config package.
Previously, we relied on a private variable to list the managers.
However, this private variable is not present on the oslo.config
packaged shipped with ubuntu 14.04.
In this commit we change the way we list managers to be compatible with
both Ubuntu 14.04 and 15.04.
. This is the 30th commit message:
Revert "fix oslo imports for Ubuntu14.04"
This reverts commit 6ee3b4d54765993d165169a56d54efdfb2653c89.
We are going to use try/except imports to deal with oslo{.,_}PKG
. This is the 31st commit message:
use try/except imports for oslo{.,_} packages
The oslo packages are imported using "oslo.PKG" for versions < 2.0.0,
but are imported using "oslo_PKG" for versions >= 2.0.0.
We use try/except statements to try to import "oslo_PKG" first, and fail
over to "oslo.PKG".
. This is the 32nd commit message:
add packaging README
. This is the 33rd commit message:
add cleaning functions in packaging scripts
This way when a container as finished building, when can easily do a
rebuild with: docker start -a -i container_id
. This is the 34th commit message:
various fixes on packaging
- deb: postinst depends on "adduser" package
- deb: add upstart & systemv init scripts in deb package
- deb: postrm purge now removes init script
- deb: override lintian error about systemd/init script
- rpm: fix the cleaning stage
- rpm: fix /var/lib/synergy not being created and preventing systemd
from starting the synergy service
. This is the 35th commit message:
use entry points to discover managers
Also add the TimerManager to the manager entry point.
fix centos docker builder
The .git repo would not get cleaned up after a failed build, resulting
in incapacity of starting the container again.
add base files for OpenStack CI
Most of the files were created with cookiecutter.
http://docs.openstack.org/infra/manual/creators.html#preparing-a-new-git-repository-using-cookiecutter
fix centos docker builder
The .git repo would not get cleaned up after a failed build, resulting
in incapacity of starting the container again.
fix setup.py failing to build due to pbr
rename service to "synergy"
Previously it was either "python-synergy-service" or "synergy"
depending on the platform.
Change-Id: Iebded1d0712a710d9f71913144bf82be31e6765b
ervin