Menu
▾
▴
Re: [xcat-user] [External] xCAT Consortium update
|
From: Jarrod J. <jjo...@le...> - 2024-05-10 22:38:42
|
> - Any Confluent rebase will likely be renamed to respect existing product name and intellectual properties. (Yes we’re looking for names!)
I'll throw into the ring:
Conflux (Confluent^H^H^HxCAT^H^H^H)
If Conflux is not unique enough, then it can have a "long name" of:
Conflux Administration Toolkit (CAT)
Of course, I'm sure IBM would also be cool with "Alternative Implementation of xCAT (AIX)".
________________________________
From: Laurence Horrocks-Barlow via xCAT-user <xca...@li...>
Sent: Friday, May 10, 2024 2:18 PM
To: xca...@li... <xca...@li...>
Cc: Laurence Horrocks-Barlow <lho...@oc...>
Subject: [External] [xcat-user] xCAT Consortium update
Dear xCAT community,
First, we’d like to first start out with an apology, since the consortium’s announcement in November, IBM’s EoL extension and some smaller communications we haven’t updated the mailing list. This is mostly due to the consortium finding it’s feet with the project and transitioning the assets; for this we would like to thank IBM and Lenovo for their valued input and support.
To this effect we’d like this mail to serve as an update of where we are and invite the community to ask us questions.
What is the consortium about?
In September 2023 IBM announced it’s End of Life plan for xCAT; this spur ’ed conversation within the community and lead to 3 independent companies Megware, OCF and Redline discussing the possibility of combining development resources to continue on the project; as each of the companies had committed to the xCAT project and each also had a vested interest in it’s continuation. This led to the proposal of approaching IBM to discuss a formation of a consortium to take ownership of the xCAT project whilst also acknowledging that the consortium wanted to focus on the future for cluster management and administration tooling; this also led to further approaching Lenovo to discuss their willingness to contribute confluent to this cause. Both IBM and Lenovo have been fantastic in supporting the consortium and its goals.
What are the consortium’s goals?
We have 3 main goals,
- Provide extended maintenance, development, and support for xCAT 2
- There are no plans to add “new” features the focus is around bug fixing and stability
- There are no plans to support any operating systems past those that are already supported, i.e. no EL10, no SLES16
- Create the next version cluster management and administration tooling
- We acknowledge both IBM xCAT and Lenovo Confluent being excellent cluster management tooling in their own rights with hours of committed development being applied to both; the consortium is aiming to take the best features from both projects to develop the next community driven tooling
- Some details of “where to start” is still being figured out
- Everything has to be free, open and vendor agnostic
What’s been going on?
It’s been a busy time for the consortium members, Megware, OCF, Redline and our supporting partners IBM and Lenovo; we’ve been meeting weekly to discuss:
Logistical/Commercial
Agree any transitions and how they will happen.
Contact other stakeholders and asset owners to seek agreement.
Discuss within all commercial entities of the consortium.
Create a new workspace for all members to collaborate in whilst providing everyone equal access to assets.
Finalising a memorandum of understanding between the consortium members to outline responsibilities and mutual goals.
Technical
Receive training on the current xCAT development and maintenance.
Implement testing services and CI pipelines.
Implement a new contribution license agreement system.
Update assets reflecting the new consortium.
Updating xCAT nightly build to include latest fixes and development - https://xcat.org/files/xcat/xcat-core/devel/Linux/core-snap/core-rpms-snap.tar.bz2
Target Summer 2024 for xCAT 2.17 (milestone 53) to include Better EL 9 supports, Support for more secure IPMI ciphers, Initial ARM support
The future
The consortium is finalising:
- Its decision to rebase Confluent as it’s start for the next cluster management and administration tooling.
- The language to continue using?
- This will almost certainly be python.
- What features to port over from xCAT?
- Which configuration management tooling should be included as a base?
- Any Confluent rebase will likely be renamed to respect existing product name and intellectual properties. (Yes we’re looking for names!)
How can you help?
We are looking for community input:
- What are your priorities? What features are you looking for?
- Can you help us bug fix? Document? Create features?
- Do you think we’re doing the right thing? What would you do differently?
Let us know on the mailing list, or alternatively 2 of the consortium members are at ISC next week so why not come and talk to us in person?
ISC, Congress Center Hamburg from June 10-13, 2025.
Megware – B30
OCF – G50
Laurence Horrocks-Barlow | Technical Director
[https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/>
Phone:
0114 257 2200
Address:
OCF Limited, Unit 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield S35 2PG
Website:
www.ocf.co.uk<http://www.ocf.co.uk/>
[LinkedIn icon]<https://www.linkedin.com/company/ocf-limited/> [Twitter icon] <https://twitter.com/ocf_hpc?lang=en>
[https://ocf.co.uk/media/imkoyi2j/line.jpg]
OCF Limited is a company registered in England and Wales. Registered number 4132533, VAT number GB 780 6803 14. Registered office address: OCF Limited, 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield, S35 2PG.
This message is private and confidential. If you have received this message in error, please notify us immediately and remove it from your system.
-------------
Scheduled Annual Leave:
Click to see my full annual leave calendar<https://calendar.google.com/calendar/u/0/embed?src=j5g...@im...&ctz=Europe/London>
"It is well known that a vital ingredient of success is not knowing that what you're attempting can't be done."
-- Sir Terry Pratchett
|
