WikiPrint - from Polar Technologies

DRM4G Internal Meetings

Meeting 2016-12-14

Place
IFCA
Date and time
14th of December, 11:30
Estimated duration
90 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics
  1. Decide what to do about the following tickets :

    #6007
    Cloud use cases
    #6066
    Use case for Cloud resources
    #6081
    Discuss the use of Libcloud


Meeting 2016-11-29

Place
IFCA
Date and time
29th of November, 11:45
Estimated duration
90 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics
  1. The publishing of the release 2.6.0 (DRM4G-2.6.0) :

Decisions made
Actions made
  1. Changed the level of some log messages in the "Agent" class in the module drm4g.commands
  2. A small error in the code in the module drm4g.utils.message has been fixed
Forthcoming actions to be done
  1. Open ticket explaining the requirements for establishing a connection using OpenSSH (ticket #6048)
  2. Add to the configuration file "resources.conf" a new key value, with which to define which communicator the user wants to use (ticket #6051)
    • ssh - it will choose paramiko?s communicator by default
    • pk-ssh - it will choose paramiko?s communicator
    • op-ssh - it will choose openssh?s communicator
  3. Remove the function "checkOutLock" from all "Communicator" classes, since it's not needed anymore (ticket #6049)
  4. Optimize the modules drm4g.core.tm_mad?s function "_update_com" (ticket #6050)


Meeting 2016-11-25

Place
IFCA
Date and time
25th of November, 12:30
Estimated duration
60 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics
  1. What to include in the milestone DRM4G-2.6.0 :

    and what to leave for DRM4G-2.6.1

  2. Decide what to do about the following tickets :

    #5992
    The command "drm4g stop" doesn't work sometimes
    #6016
    New section for cloud
    #6033
    The list of hosts updates itself too slowly
    #6037
    Create a configuration file from where to read the contextualisation text
    #6038
    An error of the logger is causing problems

Decisions made
Forthcoming actions to be done