WikiPrint - from Polar Technologies

DRM4G Internal Meetings


Meeting 2017-03-02

Place
IFCA
Date and time
2nd of March, 11:30
Estimated duration
60 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#6091
The logger is not configured properly


Meeting 2017-02-23

Place
IFCA
Date and time
23rd of February, 11:00
Estimated duration
40 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#6054
Get the DRM4G to create VMs in parallel
#6091
The logger is not configured properly
#6093
Modifying cloud resources while being used
#6095
Sometimes the VMs won't create themselves
#6100
Add setup.py to the WRF4G

Decisions made
Actions made
Forthcoming actions to be done


Meeting 2017-02-07

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

    #6054
    Get the DRM4G to create VMs in parallel
    #6091
    The logger is not configured properly

Actions done
  1. Tested the changes made for ticket #6086 with IBERGRID resources
  2. Creation of tickets #6093 and #6094
Forthcoming actions to be done
  1. Merge the branches "decouple_openssh" and "reorganize_cream" and test it out
  2. Publish the release 2.6.3


Meeting 2017-02-02

Place
IFCA
Date and time
2nd of February, 12:30
Estimated duration
90 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#5992
The command "drm4g stop" doesn't work sometimes
#6025
Add a way in which to dinamically create and destroy VMs
#6091
The logger is not configured properly

Decisions made


Meeting 2017-01-25

Place
IFCA
Date and time
25th of January, 12:00
Estimated duration
90 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#6019
Enable the DRM4G to dinamically create VMs
#6025
Add a way in which to dinamically create and destroy VMs
#6066
Use case for Cloud resources

Decisions made


Meeting 2017-01-20

Place
IFCA
Date and time
20th of January, 12:00
Estimated duration
90 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#6019
Enable the DRM4G to dinamically create VMs
#6025
Add a way in which to dinamically create and destroy VMs
#6040
Open tickets in FedCloud
#6048
Requirements for establishing a tcp connection using OpenSSH
#6064
Remove openssh communicator modifications
#6066
Use case for Cloud resources
#6084
Fallo gw_im
#6086
Reorganize CREAM

Decisions made
Forthcoming actions to be done


Meeting 2017-01-09

Place
IFCA
Date and time
9th of January, 13:00
Estimated duration
60 minutes
Summoned attendees
Antonio Minondo and Carlos Blanco
Discussed topics

#6047
Add test scripts to DRM4G's package
#6063
Merge scheduler fix branch
#6082
Cloud resource keys
#6086
Reorganize CREAM

Decisions made
Forthcoming actions to be done


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

Decisions made
Forthcoming actions to be done
  1. Integrate cloud connectors for each cloud service provider such as EC2, Openstack, OpenNebula, OCCI, etc.
    1. We will restructure the current package structure and add a "drm4g.connector" package
    2. The "fedcloud" package will become the "rocci" package and will be moved to this new folder
    3. We are going to analyze the packages EC3, Libcloud and Boto3 to implement the new connectors.
  2. We've decided to modify some of the keys of the configuration file, to make them more understandable (ticket #6082).


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