Partition Director requires configuring Synergy through RESTful API

Bug #1690123 reported by Lisa Zangrando on 2017-05-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Synergy Scheduler Manager
High
Lisa Zangrando

Bug Description

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.

summary: - Partition Director requires the setting of the projects through RESTful
- API
+ Partition Director requires to configure Synergy through RESTful API
summary: - Partition Director requires to configure Synergy through RESTful API
+ Partition Director requires configuring Synergy through RESTful API
description: updated
Lisa Zangrando (lisa-zangrando) wrote :

Fix #463984

Changed in synergy-scheduler-manager:
assignee: nobody → Lisa Zangrando (lisa-zangrando)
importance: Undecided → High

Fix proposed to branch: master
Review: https://review.openstack.org/485153

Changed in synergy-scheduler-manager:
status: New → In Progress

Reviewed: https://review.openstack.org/485153
Committed: https://git.openstack.org/cgit/openstack/synergy-scheduler-manager/commit/?id=94456be8fc2cdd87715ab8d8dbbac1250255731f
Submitter: Jenkins
Branch: master

commit 94456be8fc2cdd87715ab8d8dbbac1250255731f
Author: Lisa Zangrando <email address hidden>
Date: Wed Jul 19 12:39:53 2017 +0200

    Partition Director requires configuring Synergy through RESTful API

    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

Changed in synergy-scheduler-manager:
status: In Progress → Fix Released
Changed in synergy-scheduler-manager:
milestone: none → 2.5.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers