...

Contact Information

...

• 2020JUN Release
• ACS Python 3 Porting
  • 2020APR and 2020JUN tested against ALMA SW
  • No further bug-fixes have been found
  • Test behavior consistent in Python 2 and 3

• ACS Changes

  • Compatibility and new capabilities for the new Makefile being developed

    • Added rules.mk file to all modules, to factor out common code in the current and new Makefile being developed to allow a smoother transition between them

  • Exposing problems in the Java RemoteLogDispatcher

  • Prevent Logging crash in "at exit" handlers

• CentOS / RHEL 8
  • As of 2020AUG ACS is fully compatible with CentOS / RHEL 8
• COMMON-2020AUG
  
  • CentOS / RHEL 8 Compatibility: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16009

  • acsFindFile Thread Safe: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-17036

  • ExtProd to report building time: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16958

  • Python 3 as Default Interpreter: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16954

  • ACS Bash Profile to ignore user aliases: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16782

  • ComponentCaller to support asynchronous calls: 

    Jira
    server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16673

2020 Planning:

• Communication and Collaboration
  • ACS Workshop
    • Around 50 participants, of which 36 should be participating in the project
    • Joseph Schwarz offered help as instructor for the workshop
  • Issue Tracking platform for the community
    • During the ACS Workshop this will be discussed in the "ACS Issue Tracking and Main Problems" section
    • One alternative is to offer a public project for official JIRA
      • This public project would be public for read, but authorized login to create/comment/etc.
  • Fork/Branches on public repository
    • Workflow is similar to GitHub:
      
      • Fork of the branch and work in your user's version of the repository
      • To be defined how to bring changes back to ALMA. To be discussed in "ACS Issue Tracking and Main Problems" section of ACS Workshop
  • Community Chat
    • Slack as an option
    • Tomas Staig will check possibilities
      
  • Docker Hub
    • Section in the ACS Workshop to discuss the official docker image
• Re-design Notification Channels
  • A bit delayed
  • Consider Kafka and Akka Streams as additional possible candidates
• BulkData
  • As discussed in pending action items section
• Monotonic Clock: 

  Jira
  server ICT serverId b8c705e3451c03fa-ed92a384-32db3e36-b3d095b3-8ff450afc2493ef4dae081ba key ICT-16764

  • Will be tested soon for ALMA. If it works it would be set up as default
  • If it is used, then other projects should check if it affects them in any way

...