Connection
Participants
Agenda
Discussion
- Should ACS forward the cbStop callback to the receivers when coming from the unexpected StartState / StopState states?
-
ICT-21093
-
Getting issue details...
STATUS
-
ICT-20598
-
Getting issue details...
STATUS
- Stakeholders will read about the tickets and give feedback about the issue at hand
- ACS wants to change lib/python/site-packages for the official lib/pythonX.Y/site-packages
- RHEL upgrade scheme
- Starting with RHEL 9 the delivery cycle is going to be faster (~3 years)
- A discussion needs to be held probably in 6-18 months in the future
Short Term (2022OCT)
- Maintenance (Bug-fixing / Improvements)
- Obsolescence Management
- Java Dependencies (12)
- Replace deprecated JMS selector: Remove csselector and make use of activemq's selector
- Python Dependencies <=2020 (13)
- Also adding unfixed version of transitive dependencies (68)
- Extjars to be installed through Maven
- Cleaner installation of third party dependencies on ARCHIVE and ICD
- Upload Cycle 9 ACS / ARCHIVE / ICD / CONTROL artifacts – 2022OCT
- Continue NC implementation study – 2022OCT
- Make the coverage mechanics work again – 2022OCT
Mid Term (2022DEC --> 2023FEB)
- C++ Modernization
- Logging Service refactoring/change of technology – 2022OCT → 2023APR
- Development and Community OS Support
- Jenkins Build + Phase A tests
- ComponentCaller API Security Implementation – 2022DEC
Long Term (TBD)
- Java 17 – 2023APR+
- Will be scheduled for some point during 2023 aiming to Cycle 11 (2024-10 deployment) – 2023APR+
- Jakarta EE 9+ / Hibernate 6+ / Spring 6+ / Springboot 3+ / Tomcat 10+ (Java-17 and Jakarta EE 9 baseline for spring framework 6) – 2023JUN+
- ACS Services Modernization
- ZeroMQ-based BulkData transfer implementation
- CDB API alternative (REST, SOAP, G-RPC, Falcor, ICE, etc.)
- Logging system technology replacement (Boost::Log, etc.)
- Interface Repository (???)
- Naming Service (???)
De-scoped:
Not Relevant
Conclusions
2022OCT
* Tentative base for 2022OCT until the meeting has been held
Key
|
Summary
|
T
|
Created
|
Updated
|
Due
|
Assignee
|
Reporter
|
P
|
Status
|
Resolution
|
Priorities
- Maintenance
- Obsolescence Management
- Upload Cycle 9 artifacts to artifactory
- NC Implementation Study
- Component Caller API Security Proposal Discussion
- Testing Coverage Work
Action Items
1 Comment
Kris Haskins
Regarding cbStop, I think we should continue to propagate the cbStop to the receiver clients. They should be aware of what is happening, and take whatever action is appropriate for them.
In the ICT-20598 case, it appears that Archive somehow mishandled the cbStop for InterferometricStream1, and it caused problems over on InterferometricStream3. We shouldn't be attempting to work around this type of problem by changing ACS.
That's my perspective, feel free to try and persuade me otherwise .