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
This commit restores the method setQuotaTypeServer() which set the
server type as metadata.
Change-Id: I09dfafdbe73d59eb43c09c79a50a5449e63833e4
Sem-Ver: bugfix
The oldest requests should be processed quite first as soon as
the user priority increases. This commit fixes the issue.
BUG: #1717464
Change-Id: Iafc74531775d00aeb653cc92092b2bc7775f52d8
Sem-Ver: bugfix
In synergy is missing a useful mechanism which allows the user to
perform some actions (e.g. exporting data) into the VMs before
Synergy deletes them from the shared quota once their TTL is expired.
This commit implements such mechanism.
BUG: #1717253
Change-Id: Iabd0eb5eeda53c483189725446cb6f459c1053e8
Sem-Ver: feature
This commit updates the default values of some parameters
defined in synergy_scheduler.conf
Change-Id: I2673fc4e45b3f2c1278a61eea0ce483ef364bff3
Sem-Ver: bugfix
If, for some reasons, the termination of one of the expired VMs fails,
the iteration finishes by reporting the message error. This fix lets
Synergy to continue on terminating the remaining VMs.
BUG: #1715823
Change-Id: I1dbd984f6fb5c7588349b025828887e21d950f84
Sem-Ver: bugfix
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 typo lead to the following message when Synergy started:
> ERROR - unrecoverable error: 'KeystoneManager' object has no attribute 'project_domaini_name'
Change-Id: I49fe371b662291a16b2111e9eece134040c7d45f
Sem-Ver: bugfix
This commit updates the packaging files for supporting the new
authorization mechanism based on policy.json
Change-Id: I001fba11b9c59ef34a10bf92ab7241f37efd4668
Sem-Ver: feature
This commit includes an advanced Keystone based authorization plugin.
Bug: #1691352
Change-Id: Icb5d534c2a684f5efe7abf3b64227d66a3fbc2b6
Sem-Ver: feature
Replaced any occurrence of "raise Exception" with "raise SynergyError".
Bug: #1690795
Change-Id: I064a7219de1323670660dacd02f2513e56981d0c
Sem-Ver: bugfix
Partition Director, the INDIGO-DataCloud service, requires the setting
of the Synergy configuration (e.g. the list of projects allowed the
access the shared quota, their values, etc) through the RESTful API.
This implies some changes at configuration level of Synergy: some
parameters must be drop out from the synergy_scheduler.conf file and
the stored into a database. The use of the database for storing
configuration parameters will be useful even for configuring Synergy
in high availability mode.
Bug: #1690123
Change-Id: Id8f9c6b0e0a2804b43984f7353dc3fc0882cd651
Sem-Ver: feature
This update enables KeystoneManager to receive asynchronous
notifications about the users and projects status from Keystone
service
Change-Id: Ia75b89c825bb8536e0462eff7a873699b219d781
Sem-Ver: bugfix
nova_manager.py implements the NovaManager which interacts with Nova
service but even provides the MessagingAPI class which interacts with
the AMQP system. This fix moves the MessagingAPI in common/messaging.py.
Bug: 1690133
Change-Id: Ifed11126a1af227950c03ccffc48d577fb631ded
Sem-Ver: bugfix
Sometimes the SchedulerManager doesn't receive the "compute.instance.delete.end"
notifications of VMs destroyed before to be active.
Bug: #1690126
Change-Id: If874d436b825e2f430e246ccc7663df1bebd461c
Sem-Ver: bugfix
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
The new "synergy_topic" parameter simplifies the Synergy integration with Nova.
Bug: #1672409
Change-Id: I00f7e6ce7b6c4b22d9267d2b956c599fb71c68a2
Sem-Ver: feature
It may happen that a VM instance goes in error during the building phase.
Although the server is deleted by Synergy, the compute node may not send
the notification about the cancellation by leaving the shared quota not
consistent. This fix addresses this issue.
Bug: #1668199
Change-Id: I9ff9eed7b234117e24ae629fdd3e00ae7ce528cd
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
This fix solves the problem of the calculation of the user
share which keeps memory of deleted users.
bug: #1663644
Change-Id: Ie591b60a413ab16c90fa6adc5a1f5be3046e0122
Sem-Ver: bugfix
On Newton, the startup of Synergy fails and the reported message in synergy.log is:
"ERROR - manager 'NovaManager' instantiation error: arguments already parsed: cannot
register CLI option". We fix this bug in this commit.
- removed unuseful conductor interfaces
bug: #1664567
Change-Id: I501196c40efd6fbd0e3e3669005441e7a8c23364
Sem-Ver: bugfix
This commit fixes the bug concerning the use of a wrong logging format
into the SchedulerManager.
Bug: #1664608
Change-Id: Id39fab710571e21be1e4580621a2f698febf2a7a
Sem-Ver: bugfix
The Scheduler manager should specify all configuration parameters on a
dedicated configuration file.
Bug: #1663589
Change-Id: I7ceb140182db306567d7f7a6b5bfcf0871249a05
Sem-Ver: feature
Previously, one could encounter the following error:
"NumaTopologyNotFound: Instance does not specify a NUMA topology"
Bug: #1659794
Change-Id: I065e4ed0cfe56c3026b9eefc473fe6baf0889baf
Sem-Ver: bugfix
OpenDev Sysadmins