You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Table of contents


Release history and use in Alma

This is the second ACS development to be used in Cycle 10. Below is the list of addressed tickets.

Summary of Changes

  • Obsolescence management 
    • ACS to offer C++17 standard
    • ACE/TAO (7.0.6)
    • OmniORBpy (4.3.0)
    • PyEnv (2.2.4-1)
    • Tcl/Tk can now be used from the O.S.
    • Python Dependencies (13)
    • Java Dependencies (15)
  • Functionality for ensuring proper CORBA connection after servant forceful restart on C++
  • ACS Smart Pointers are now based on std::shared_ptr by default and are compatible with std::unique_ptr as well
  • BulkDataNT Improvements
    • Throughput doubled
    • RHEL 8 fixes (std::set and iterator corrections)
    • Notification channel proper disconnection
  • Scripts for ACS component skeleton generation
    • C++ and Java
  • RHEL 8 compatibility improvements
  • Log4j2 ACS wrapper works even if enabled after use of native log4j2 logger
  • New Makefile bug-fixes
  • RHEL 8 tests stabilization
  • Regular Jenkins job now working for Debian 10/11 and Ubuntu 20.04/22.04

Addressed JIRA tickets

key summary type created updated assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Release Notes


git status
On branch integration/COMMON-2022APR
Your branch is up to date with 'origin/integration/COMMON-2022APR'.

git log --no-merges --oneline --reverse origin/master..origin/integration/COMMON-2022APR -- ACS

git log --no-merges --oneline --reverse origin/master..origin/integration/COMMON-2022APR -- ARCHIVE

git log --no-merges --oneline --reverse origin/master..origin/integration/COMMON-2022APR -- ICD


OS Support:

  • The officially supported OS is the 64 bit version of "Red Hat Enterprise Linux Server release 8.5 (Ootpa)"
    • The binary distribution of ACS (tarball) is made for this OS
    • We also successfully use its clone "CentOS Stream 8"
    • For all machines the expected kernel is 4.18.0
  • Unofficially, "CentOS Stream 9" has also been used successfully

The expected and actual versions of compilers, ORBs and various RPMs can be found by running the command =acsConfigReport=, both for required RPMs and for software shipped together with ACS. To get a rough overview before installing ACS, here are the most basic ones:

  • Gcc: 8.5 RHEL 8.5.0
  • Java: openjdk-11.0.4
  • Python: 3.8.6
  • ACE: 6.5.11
  • TAO: 2.5.11
  • JacORB: 3.9
  • omniorb: 4.2.4

The operating system dependencies are:

  • redhat-lsb-core
  • ksh
  • gcc
  • gcc-c++
  • gcc-fortran
  • libX11-devel
  • libffi-devel
  • perl
  • readline-devel
  • bzip2
  • bzip2-devel
  • openssl-devel
  • openldap-devel
  • libxml2-devel
  • freetype-devel
  • libxslt-devel
  • sqlite-devel
  • expat-devel
  • bison
  • flex
  • autoconf
  • unzip
  • dos2unix
  • tcl-devel
  • tk-devel
  • procmail
  • cppunit-devel
  • doxygen
  • graphviz

There are new requirements needed to replace swig, boost, astyle and xerces-c (Since 2022FEB):

  • astyle
  • boost-devel
  • swig
  • xerces-c-devel

If you need to build doxygen/graphviz instead of installing at OS level, you also need (Since 2022FEB):

  • cmake
  • libarchive

There are new requirements needed to replace Tcl/Tk (Since 2022APR):

  • tcl-devel *
  • tk-devel *

* Although these dependencies were already publicized as required, they were actually ignored during ACS installation. They are now being taken advantage of and so we announce they're as a requirement of 2022APR+ ACS releases

Problems

Problems Found And Fix Version in This Release

key summary type created updated assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Problems Found And Fix Version in Future Releases

key summary type created updated assignee reporter priority status resolution fixversions

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels