You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(227) |
Sep
(185) |
Oct
(259) |
Nov
(168) |
Dec
(163) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(94) |
Feb
(92) |
Mar
(121) |
Apr
(83) |
May
(158) |
Jun
(72) |
Jul
(150) |
Aug
(64) |
Sep
(81) |
Oct
(98) |
Nov
(79) |
Dec
(27) |
2004 |
Jan
(93) |
Feb
(81) |
Mar
(85) |
Apr
(43) |
May
(71) |
Jun
(28) |
Jul
(89) |
Aug
(156) |
Sep
(51) |
Oct
(50) |
Nov
(48) |
Dec
(56) |
2005 |
Jan
(59) |
Feb
(180) |
Mar
(68) |
Apr
(58) |
May
(44) |
Jun
(59) |
Jul
(50) |
Aug
(103) |
Sep
(100) |
Oct
(66) |
Nov
(41) |
Dec
(33) |
2006 |
Jan
(41) |
Feb
(51) |
Mar
(133) |
Apr
(66) |
May
(40) |
Jun
(34) |
Jul
(86) |
Aug
(28) |
Sep
(62) |
Oct
(54) |
Nov
(24) |
Dec
(23) |
2007 |
Jan
(72) |
Feb
(81) |
Mar
(33) |
Apr
(64) |
May
(23) |
Jun
(67) |
Jul
(33) |
Aug
(54) |
Sep
(38) |
Oct
(40) |
Nov
(108) |
Dec
(84) |
2008 |
Jan
(49) |
Feb
(44) |
Mar
(65) |
Apr
(43) |
May
(75) |
Jun
(171) |
Jul
(121) |
Aug
(86) |
Sep
(189) |
Oct
(326) |
Nov
(172) |
Dec
(178) |
2009 |
Jan
(86) |
Feb
(154) |
Mar
(159) |
Apr
(112) |
May
(113) |
Jun
(64) |
Jul
(147) |
Aug
(170) |
Sep
(157) |
Oct
(153) |
Nov
(149) |
Dec
(184) |
2010 |
Jan
(196) |
Feb
(234) |
Mar
(191) |
Apr
(233) |
May
(95) |
Jun
(200) |
Jul
(134) |
Aug
(189) |
Sep
(158) |
Oct
(135) |
Nov
(104) |
Dec
(135) |
2011 |
Jan
(101) |
Feb
(142) |
Mar
(157) |
Apr
(142) |
May
(145) |
Jun
(195) |
Jul
(306) |
Aug
(268) |
Sep
(128) |
Oct
(80) |
Nov
(125) |
Dec
(112) |
2012 |
Jan
(93) |
Feb
(125) |
Mar
(94) |
Apr
(102) |
May
(134) |
Jun
(85) |
Jul
(80) |
Aug
(130) |
Sep
(104) |
Oct
(104) |
Nov
(133) |
Dec
(107) |
2013 |
Jan
(136) |
Feb
(127) |
Mar
(172) |
Apr
(183) |
May
(158) |
Jun
(84) |
Jul
(132) |
Aug
(143) |
Sep
(46) |
Oct
(94) |
Nov
(42) |
Dec
(61) |
2014 |
Jan
(248) |
Feb
(89) |
Mar
(93) |
Apr
(102) |
May
(59) |
Jun
(44) |
Jul
(131) |
Aug
(69) |
Sep
(199) |
Oct
(88) |
Nov
(38) |
Dec
(59) |
2015 |
Jan
(54) |
Feb
(57) |
Mar
(70) |
Apr
(71) |
May
(63) |
Jun
(79) |
Jul
(85) |
Aug
(106) |
Sep
(69) |
Oct
(72) |
Nov
(48) |
Dec
(28) |
2016 |
Jan
(42) |
Feb
(70) |
Mar
(89) |
Apr
(87) |
May
(114) |
Jun
(57) |
Jul
(47) |
Aug
(60) |
Sep
(38) |
Oct
(36) |
Nov
(12) |
Dec
(28) |
2017 |
Jan
(32) |
Feb
(44) |
Mar
(135) |
Apr
(101) |
May
(98) |
Jun
(42) |
Jul
(54) |
Aug
(21) |
Sep
(23) |
Oct
(83) |
Nov
(89) |
Dec
(15) |
2018 |
Jan
(18) |
Feb
(2) |
Mar
(35) |
Apr
(12) |
May
(52) |
Jun
(103) |
Jul
(65) |
Aug
(35) |
Sep
(47) |
Oct
(81) |
Nov
(86) |
Dec
(44) |
2019 |
Jan
(34) |
Feb
(63) |
Mar
(58) |
Apr
(21) |
May
(39) |
Jun
(30) |
Jul
(43) |
Aug
(22) |
Sep
(26) |
Oct
(62) |
Nov
(39) |
Dec
(47) |
2020 |
Jan
(40) |
Feb
(27) |
Mar
(30) |
Apr
(20) |
May
(42) |
Jun
(24) |
Jul
(60) |
Aug
(26) |
Sep
(60) |
Oct
(29) |
Nov
(15) |
Dec
(7) |
2021 |
Jan
(34) |
Feb
(31) |
Mar
(54) |
Apr
(8) |
May
(40) |
Jun
(49) |
Jul
(14) |
Aug
(26) |
Sep
(25) |
Oct
(13) |
Nov
(46) |
Dec
(19) |
2022 |
Jan
(45) |
Feb
(8) |
Mar
(20) |
Apr
(25) |
May
(8) |
Jun
(12) |
Jul
(10) |
Aug
(11) |
Sep
(4) |
Oct
(11) |
Nov
(3) |
Dec
(3) |
2023 |
Jan
|
Feb
(25) |
Mar
(7) |
Apr
(16) |
May
(7) |
Jun
(8) |
Jul
(31) |
Aug
(11) |
Sep
(32) |
Oct
(18) |
Nov
(25) |
Dec
(6) |
2024 |
Jan
(48) |
Feb
(31) |
Mar
(7) |
Apr
(1) |
May
(22) |
Jun
(8) |
Jul
(3) |
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
From: Kilian C. <kil...@gm...> - 2024-05-13 20:37:49
|
On Fri, May 10, 2024 at 11:52 AM Laurence Horrocks-Barlow via xCAT-user <xca...@li...> wrote: > The future > The consortium is finalising: > - Its decision to rebase Confluent as it’s start for the next cluster management and administration tooling. > - 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!) I know that ship has probably sailed already, and I don't want to challenge or question things that have already been decided, but Confluent and xCAT have diverged to a point they're now *very* different tools. I'm not sure that bringing features over from xCAT to Confluent will be less work or be more achievable with a limited team of volunteers than trying to fix the existing xCAT issues and supporting newer distributions over time. Nor that moving existing xCAT users and installations to a new system down the line will be a very easy transition path. Adding I'm a bit concerned that adding configuration management tooling into the mix and renaming it all doesn't really look like it's going in the direction of a xCAT project continuation, I'm afraid. :\ Cheers, -- Kilian |
From: Calvin S. <c.s...@qm...> - 2024-05-13 09:36:16
|
Hi We've just migrated to a fresh 2.16.5 in a Rocky9.3 VM using imports from the previous 2.16.3, which has been mostly successful. We can rinstall and perform most r-commands Our test cluster which this xcat manages is comprised of older hardware and is meant to serve as a dress rehearsal for upgrading similarly in our production cluster with newer-gen hardware For the most part, 2.16.5 has been working fine with the notable exception of rcons. Both system types in the test cluster work fine with rcons under 2.16.3 user CentOS7, but under 2.16.5: Flex System x240 and NeXtScale nx360 M5 respond on C3 only, C17 is inoperative (and verified using ipmitool) with error: Error: Unable to establish IPMI v2 / RMCP+ session Error in open session response message : no matching cipher suite Testing on other hardware is complicated by many accepting both C3 and C17 (dell iDrac is one). More contemporary IMM2 allows both cipher suites as well This leads me to think that rcons is still somewhere hardwired to C3. We downloaded and patched IPMI.pm with the one from https://github.com/xcat2/xcat-core but the issue persists. However, I also don't understand exactly which system or xcat-specific components are involved in operation of goconserver or establishing an rcons connection to track down where the cipher suite is set Cal Sawyer ITS Research Platforms Manager Queen Mary University of London |
From: Don A. <da...@re...> - 2024-05-11 04:31:13
|
Jarrod, Just a thought, and you’ve probably considered it already... How about Conflu-X … keeps the ex sound and IMHO sounds better than flux. With an official/long name Conflu-X Administration Toolkit (CAT) it keeps the CAT option open for logos, etc. My $.02 -Don ---- Don Avart CTO RedLine Performance Solutions, LLC (703) 634-5686 da...@re... > On May 10, 2024, at 5:01 PM, Jarrod Johnson <jjo...@le...> wrote: > > > - 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://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/> > <https://www.linkedin.com/company/ocf-limited/> <https://twitter.com/ocf_hpc?lang=en> > > 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 > > > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user |
From: Samveen G. <sa...@ya...> - 2024-05-11 01:40:53
|
Jarrod, Taking into account what you said about the history of naming of confluent back in the initial zoom meeting, xCAT has history and is unique with no namespace collisions. Why not use your previous suggestion of xCAT with a postfix like 3, or if not a number, then xcat-ng or even xcat-confluent? |
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 |
From: Laurence Horrocks-B. <lho...@oc...> - 2024-05-10 18:53:30
|
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 its 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 |
From: Laurence Horrocks-B. <lho...@oc...> - 2024-05-10 18:51:00
|
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 |
From: Samveen G. <sa...@ya...> - 2024-05-03 10:28:45
|
Hi Keith, Most client commands of xCAT are essentially thin clients to the xCAT server's API. That is true for nodeset as well. What you're seeing is the client waiting for server responses on the connection's file descriptor (which is usually 3, after std{in,out,err}). Network communication waits are usually implemented as select calls on the fdset and then reading from the FDs in the set, in case there is any change in the state of any descriptor in the fdset. You should take a look at the xcat daemon log In a second terminal while the command execution is on. More details on the debugging facilities of xCAT can be found at https://xcat-docs.readthedocs.io/en/stable/guides/admin-guides/references/man8/xcatdebug.8.html Regards, -- Samveen S. Gulati-- The best-laid schemes o' mice an 'men Gang aft agley, An'lea'e us nought but grief an' pain, For promis'd joy! -- Robert Burns (The best laid plans of mice and men often go awry, and bring nothing but grief and pain of the ..) On Thursday, May 2, 2024 at 09:07:36 PM GMT+5:30, kei...@lm... <kei...@lm...> wrote: I have 2 different xcat boot servers (we’ll call them boot1 and boot2) both running xcat 2.16.5 who were upgraded from 2.10. boot2 was upgraded directly, while boot 1 was upgraded but then xcat was removed completely then installed 2.16.5 fresh. I am having an issue with nodeset on boot1. For some reason, nodeset on a single node on boot 1 takes over a minute, while nodeset on the same node on boot2 takes less than a second. I can’ seem to find the cause of this. I tried stracing the nodeset and I get long timeouts on a resource being temporarily unavailable but I can’t seem to figure out the resource. [root@boot1 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 proc5201_p: netboot rhels7.4-x86_64-compute real 0m50.636s user 0m0.064s sys 0m0.038s [root@boot2 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 proc5201_p: netboot rhels7.4-x86_64-compute real 0m0.799s user 0m0.060s sys 0m0.033s on boot1: select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) Has anyone seen this before and can help explain why this is happening? _______________________ - Keith Hannum - kei...@lm... _______________________________________________ xCAT-user mailing list xCA...@li... https://lists.sourceforge.net/lists/listinfo/xcat-user |
From: Blayne P. <bl...@pu...> - 2024-05-02 16:38:13
|
See if you can find out what file descriptor 3 is earlier in that strace output. That might give you a hint. --- Blayne Puklich Minneapolis, MN PGP Key ID: 0xC52CA6C1 * mailto:blayne at puklich.com I'd explain it to you, but your brain would explode. On 2 May 2024, at 9:58, kei...@lm... wrote: > I have 2 different xcat boot servers (we'll call them boot1 and boot2) > both running xcat 2.16.5 who were upgraded from 2.10. boot2 was > upgraded directly, while boot 1 was upgraded but then xcat was removed > completely then installed 2.16.5 fresh. > > I am having an issue with nodeset on boot1. For some reason, nodeset > on a single node on boot 1 takes over a minute, while nodeset on the > same node on boot2 takes less than a second. I can' seem to find the > cause of this. I tried stracing the nodeset and I get long timeouts on > a resource being temporarily unavailable but I can't seem to figure > out the resource. > > [root@boot1 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 > proc5201_p: netboot rhels7.4-x86_64-compute > > real 0m50.636s > user 0m0.064s > sys 0m0.038s > > [root@boot2 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 > proc5201_p: netboot rhels7.4-x86_64-compute > > real 0m0.799s > user 0m0.060s > sys 0m0.033s > > > on boot1: > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > read(3, 0x20de033, 5) = -1 EAGAIN (Resource > temporarily unavailable) > select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) > > > Has anyone seen this before and can help explain why this is > happening? > > _______________________ > - Keith Hannum > - kei...@lm... > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user |
From: <kei...@lm...> - 2024-05-02 15:37:01
|
I have 2 different xcat boot servers (we'll call them boot1 and boot2) both running xcat 2.16.5 who were upgraded from 2.10. boot2 was upgraded directly, while boot 1 was upgraded but then xcat was removed completely then installed 2.16.5 fresh. I am having an issue with nodeset on boot1. For some reason, nodeset on a single node on boot 1 takes over a minute, while nodeset on the same node on boot2 takes less than a second. I can' seem to find the cause of this. I tried stracing the nodeset and I get long timeouts on a resource being temporarily unavailable but I can't seem to figure out the resource. [root@boot1 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 proc5201_p: netboot rhels7.4-x86_64-compute real 0m50.636s user 0m0.064s sys 0m0.038s [root@boot2 ~]# time nodeset -V proc5201_p osimage=rhel7-ia2 proc5201_p: netboot rhels7.4-x86_64-compute real 0m0.799s user 0m0.060s sys 0m0.033s on boot1: select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) read(3, 0x20de033, 5) = -1 EAGAIN (Resource temporarily unavailable) select(8, [3], NULL, NULL, {0, 500000}) = 0 (Timeout) Has anyone seen this before and can help explain why this is happening? _______________________ - Keith Hannum - kei...@lm... |
From: Glick, B. <bg...@il...> - 2024-05-02 15:33:05
|
How is the xCAT Consortium effort going? I had the impression we’d hear approximately monthly updates about its progress, but I haven’t seen any updates since this message in December. - Bill Glick From: Markus Hilger <mar...@me...> Date: Monday, December 11, 2023 at 11:07 AM To: xCAT Users Mailing list <xca...@li...> Subject: [xcat-user] xCAT Consortium Update Dear xCAT community, it is one month ago, since we met at Supercomputing ’23 to announce that a consortium led by RedLine, OCF and MEGWARE is willing to take over the ownership of the current xCAT project to provide continuity for existing xCAT 2 based clusters. And we are still thrilled having seen so many of you during this event who have shown their interest and support, both in presence and online. On the technical side, we have started to dive into the IBM-internal integration setup for compiling and testing xCAT releases. Our goal is to replicate and extend this infrastructure at RedLine, OCF and MEGWARE to provide even wider test coverage on more hardware infrastructures for future releases. At the same time, we continue to investigate the various legal aspects of the transition. During our SC’23 meeting, we have also announced that in addition to our efforts surrounding xCAT 2, we would work with LENOVO towards making Confluent a suitable, community backed, xCAT 2 replacement for future cluster systems. For this reason, we invited LENOVO to become a full member of our consortium from the beginning. Understandably, this plan is a significant step for the Confluent team that requires thorough preparation and careful consideration and we will share further updates as this effort takes shape. We would also like to take this opportunity to thank the team at IBM, namely Nathan A Besaw, for their continued support during the transition. Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<https://urldefense.com/v3/__http:/www.megware.com/__;!!DZ3fjg!408lxur06Jk8-bQWQGKw6CU6hJUpB8yNM9CuibvOFzrB8wxMVavWBFshC-oqQggakVDDlr1jpM49BBSszZMCWMo_ObU$> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 |
From: Imam T. <tec...@gm...> - 2024-05-02 15:09:46
|
Hello, Markus, Thank you. I think I can wait till 2.17 comes out officially. Glad to see that xCAT is moving forward. --imam On Thu, May 2, 2024 at 6:16 AM Markus Hilger <mar...@me...> wrote: > Hi, > > you can already try the latest dev release: > https://xcat.org/files/xcat/xcat-core/devel/Linux/core-snap/core-rpms-snap.tar.bz2 > It passes all tests, and we use it in production for quite a few clusters. > > There are still a couple of things missing for the next release though. > You can check the progress here: > https://github.com/xcat2/xcat-core/milestone/53 > > > Mit freundlichen Grüßen / Kind regards > > *Markus Hilger* > > > > HPC Engineer > > > > MEGWARE Computer Vertrieb und Service GmbH > > Tel: +49 3722 528-47 > > > > Nordstraße 19 > mar...@me... > > > > 09247 Chemnitz-Röhrsdorf, Germany > > www.megware.com > > > > Geschäftsführer: André Singer, Dr. Axel Auweter > > > > > > Amtsgericht: Chemnitz HRB 584 > > ------------------------------ > *Von:* Imam Toufique <tec...@gm...> > *Gesendet:* Dienstag, 30. April 2024 07:36 > *An:* xCAT Users Mailing list <xca...@li...> > *Betreff:* Re: [xcat-user] [External] next xcat release timeline > > Hello again, > Are there any updates for the next xCAT release timeline? > thanks. > > On Fri, Mar 29, 2024 at 7:19 AM Noah, Stuart via xCAT-user < > xca...@li...> wrote: > > I agree. I have two cluster upgrade projects, development, and production > in the works. > > Jumping over RHEL 8 to RHEL 9 will add considerably to the expected > lifespan of the new > > installations. In an environment that that is becoming increasingly > complicated by review > > and restrictions, increasing the time between major upgrades increases my > productivity. > > > > *From:* Imam Toufique <tec...@gm...> > *Sent:* Thursday, March 28, 2024 8:10 PM > *To:* xCAT Users Mailing list <xca...@li...> > *Subject:* [External] [xcat-user] next xcat release timeline > > > > Hello, we are eagerly waiting for the next release of xcat. My > understanding was that RHEL 9 will be supported in the new release. Is > there a timeline decided for the new release? thanks > > > ZjQcmQRYFpfptBannerStart > > *WARNING: New Sender * > > You have not previously corresponded with this sender. > > ZjQcmQRYFpfptBannerEnd > > Hello, > > we are eagerly waiting for the next release of xcat. My understanding was > that RHEL 9 will be supported in the new release. Is there a timeline > decided for the new release? > > thanks > > > > > > > IMPORTANT WARNING: This message is intended for the use of the person or > entity to which it is addressed and may contain information that is > privileged and confidential, the disclosure of which is governed by > applicable law. If the reader of this message is not the intended > recipient, or the employee or agent responsible for delivering it to the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this information is strictly prohibited. Thank > you for your cooperation. > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > > > > -- > Regards, > *Imam Toufique* > *213-700-5485* > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > -- Regards, *Imam Toufique* *213-700-5485* |
From: Markus H. <mar...@me...> - 2024-05-02 13:15:11
|
Hi, you can already try the latest dev release: https://xcat.org/files/xcat/xcat-core/devel/Linux/core-snap/core-rpms-snap.tar.bz2 It passes all tests, and we use it in production for quite a few clusters. There are still a couple of things missing for the next release though. You can check the progress here: https://github.com/xcat2/xcat-core/milestone/53 Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Dr. Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Imam Toufique <tec...@gm...> Gesendet: Dienstag, 30. April 2024 07:36 An: xCAT Users Mailing list <xca...@li...> Betreff: Re: [xcat-user] [External] next xcat release timeline Hello again, Are there any updates for the next xCAT release timeline? thanks. On Fri, Mar 29, 2024 at 7:19 AM Noah, Stuart via xCAT-user <xca...@li...<mailto:xca...@li...>> wrote: I agree. I have two cluster upgrade projects, development, and production in the works. Jumping over RHEL 8 to RHEL 9 will add considerably to the expected lifespan of the new installations. In an environment that that is becoming increasingly complicated by review and restrictions, increasing the time between major upgrades increases my productivity. From: Imam Toufique <tec...@gm...<mailto:tec...@gm...>> Sent: Thursday, March 28, 2024 8:10 PM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Subject: [External] [xcat-user] next xcat release timeline Hello, we are eagerly waiting for the next release of xcat. My understanding was that RHEL 9 will be supported in the new release. Is there a timeline decided for the new release? thanks ZjQcmQRYFpfptBannerStart WARNING: New Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hello, we are eagerly waiting for the next release of xcat. My understanding was that RHEL 9 will be supported in the new release. Is there a timeline decided for the new release? thanks IMPORTANT WARNING: This message is intended for the use of the person or entity to which it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is strictly prohibited. Thank you for your cooperation. _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user -- Regards, Imam Toufique 213-700-5485 |
From: Imam T. <tec...@gm...> - 2024-04-30 05:37:21
|
Hello again, Are there any updates for the next xCAT release timeline? thanks. On Fri, Mar 29, 2024 at 7:19 AM Noah, Stuart via xCAT-user < xca...@li...> wrote: > I agree. I have two cluster upgrade projects, development, and production > in the works. > > Jumping over RHEL 8 to RHEL 9 will add considerably to the expected > lifespan of the new > > installations. In an environment that that is becoming increasingly > complicated by review > > and restrictions, increasing the time between major upgrades increases my > productivity. > > > > *From:* Imam Toufique <tec...@gm...> > *Sent:* Thursday, March 28, 2024 8:10 PM > *To:* xCAT Users Mailing list <xca...@li...> > *Subject:* [External] [xcat-user] next xcat release timeline > > > > Hello, we are eagerly waiting for the next release of xcat. My > understanding was that RHEL 9 will be supported in the new release. Is > there a timeline decided for the new release? thanks > > > ZjQcmQRYFpfptBannerStart > > *WARNING: New Sender * > > You have not previously corresponded with this sender. > > ZjQcmQRYFpfptBannerEnd > > Hello, > > we are eagerly waiting for the next release of xcat. My understanding was > that RHEL 9 will be supported in the new release. Is there a timeline > decided for the new release? > > thanks > > > > > > > IMPORTANT WARNING: This message is intended for the use of the person or > entity to which it is addressed and may contain information that is > privileged and confidential, the disclosure of which is governed by > applicable law. If the reader of this message is not the intended > recipient, or the employee or agent responsible for delivering it to the > intended recipient, you are hereby notified that any dissemination, > distribution or copying of this information is strictly prohibited. Thank > you for your cooperation. > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > -- Regards, *Imam Toufique* *213-700-5485* |
From: Noah, S. <Stu...@cs...> - 2024-03-29 14:18:03
|
I agree. I have two cluster upgrade projects, development, and production in the works. Jumping over RHEL 8 to RHEL 9 will add considerably to the expected lifespan of the new installations. In an environment that that is becoming increasingly complicated by review and restrictions, increasing the time between major upgrades increases my productivity. From: Imam Toufique <tec...@gm...> Sent: Thursday, March 28, 2024 8:10 PM To: xCAT Users Mailing list <xca...@li...> Subject: [External] [xcat-user] next xcat release timeline Hello, we are eagerly waiting for the next release of xcat. My understanding was that RHEL 9 will be supported in the new release. Is there a timeline decided for the new release? thanks ZjQcmQRYFpfptBannerStart WARNING: New Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hello, we are eagerly waiting for the next release of xcat. My understanding was that RHEL 9 will be supported in the new release. Is there a timeline decided for the new release? thanks IMPORTANT WARNING: This message is intended for the use of the person or entity to which it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is strictly prohibited. Thank you for your cooperation. |
From: Imam T. <tec...@gm...> - 2024-03-29 03:10:27
|
Hello, we are eagerly waiting for the next release of xcat. My understanding was that RHEL 9 will be supported in the new release. Is there a timeline decided for the new release? thanks |
From: Markus H. <mar...@me...> - 2024-03-23 03:03:13
|
Hi, The status is more or less unchanged. The PR works well, but it still needs some polishing (e.g. documentation). However, it is planned for the next release. Maybe we can have a development version built with it so that early adopters can use the PR more easily ;) Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Russell Jones <arj...@gm...> Gesendet: Freitag, 22. März 2024 14:42 An: xCAT Users Mailing list <xca...@li...> Betreff: [xcat-user] ARM support status? Hi developers, What is the "official" status of ARM support? With nvidia's Grace systems, that support has become more important than ever for us. It looks like perhaps the pull request that was made hasn't been merged yet as best I can tell. > From: Markus Hilger <mar...@me...><mailto:mar...@me...> Sent: Friday, February 23, 2024 6:43 PM To: Gilad Berman <gb...@le...><mailto:gb...@le...>; xCAT Users Mailing list <xca...@li...><mailto:xca...@li...> Cc: Matthew Alton <ma...@oc...><mailto:ma...@oc...> Subject: AW: [xcat-user] [External] Re: RHEL9 support in xcat Hi, with https://github.com/xcat2/xcat-core/pull/7257 arm deployment is pretty much working for stateless and stateful deployment via grub2. On a x86 management node you can even cross-build arm stateless images. Only discovery doesn't work for arm. Feel free to test these changes. I would like to merge these changes as alpha state arm support. I think stateless and stateful deployment covers 90% of use cases already 😉 |
From: Russell J. <arj...@gm...> - 2024-03-22 13:42:59
|
Hi developers, What is the "official" status of ARM support? With nvidia's Grace systems, that support has become more important than ever for us. It looks like perhaps the pull request that was made hasn't been merged yet as best I can tell. > *From:* Markus Hilger <mar...@me...> <mar...@me...> *Sent:* Friday, February 23, 2024 6:43 PM *To:* Gilad Berman <gb...@le...> <gb...@le...>; xCAT Users Mailing list <xca...@li...> <xca...@li...> *Cc:* Matthew Alton <ma...@oc...> <ma...@oc...> *Subject:* AW: [xcat-user] [External] Re: RHEL9 support in xcat Hi, with https://github.com/xcat2/xcat-core/pull/7257 arm deployment is pretty much working for stateless and stateful deployment via grub2. On a x86 management node you can even cross-build arm stateless images. Only discovery doesn't work for arm. Feel free to test these changes. I would like to merge these changes as alpha state arm support. I think stateless and stateful deployment covers 90% of use cases already 😉 |
From: Markus H. <mar...@me...> - 2024-03-22 01:03:33
|
Hi, this documentation should help: https://xcat-docs.readthedocs.io/en/stable/advanced/migration/migration.html I would just setup latest xCAT in your Rocky9 VM and then copy/paste all the data and configs and make sure it still works. But be careful, you probably don't want to copy all the OS related configs as some of them changed between 7.9 and 9. Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Calvin Sawyer <c.s...@qm...> Gesendet: Donnerstag, 21. März 2024 13:03 An: xca...@li... <xca...@li...> Betreff: [xcat-user] xcat upgrade/migration? Hello We're running slightly stale xcat 2.16.3 in CentOS 7.9 on bare metal and would ideally like to migrate it wholesale to a Rocky9 VM (including DHCP config and DNS records) Is there any form of documented procedure for accomplishing this? Any suggestions as to what steps we'd need to walk through to get there? thank you! Cal Sawyer ITS Research Platforms Manager Queen Mary University of London |
From: Calvin S. <c.s...@qm...> - 2024-03-21 17:37:18
|
Hello We're running slightly stale xcat 2.16.3 in CentOS 7.9 on bare metal and would ideally like to migrate it wholesale to a Rocky9 VM (including DHCP config and DNS records) Is there any form of documented procedure for accomplishing this? Any suggestions as to what steps we'd need to walk through to get there? thank you! Cal Sawyer ITS Research Platforms Manager Queen Mary University of London |
From: Christian C. <cca...@le...> - 2024-03-14 05:02:52
|
Action Items: * The 1Gb provisioning connection for stor204lgc1n1 is down. * The 100Gb ports for DC1 apprear not to support jumbo frames. This evening, I was able to: * Install & configure SN1 * Discover & install DSS nodes * Verify SAS & Drive topology * Verify Drives w/ read/write I/O test * Verify drive & enclosure firmware levels Tomorrow, I will be working on stor0010 at DC1. I'll be at DC2 Friday evening to continue work on stor204. Regards, Christian Caruthers Lenovo Professional Services Mobile: +1 757-289-9872 |
From: Markus H. <mar...@me...> - 2024-02-28 01:20:42
|
We plan to do so for 2.17. It won't be "official" support, but more like a tech preview / alpha state though 😄 btw, if someone wants to test latest changes, xCAT devel package builds are working again: https://xcat.org/files/xcat/repos/yum/devel/core-snap/ Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Russell Jones <rus...@jo...> Gesendet: Montag, 26. Februar 2024 14:52 An: xca...@li... <xca...@li...> Betreff: Re: [xcat-user] [External] Re: RHEL9 support in xcat Glad to know that worked! We have some GH nodes coming in as well. If we can stick to xcat we definitely want to do that. Hope to see these changes merged and "officially" supported soon. On 2/24/24 1:28 AM, Gilad Berman wrote: THX for that! Indeed works 😊 (grace-hopper node, rhel9.3) Gilad Berman HPC Architect, Lenovo EMEA gb...@le...<mailto:gb...@le...> +972-522554262 [cid:par...@jo...] From: Markus Hilger <mar...@me...><mailto:mar...@me...> Sent: Friday, February 23, 2024 6:43 PM To: Gilad Berman <gb...@le...><mailto:gb...@le...>; xCAT Users Mailing list <xca...@li...><mailto:xca...@li...> Cc: Matthew Alton <ma...@oc...><mailto:ma...@oc...> Subject: AW: [xcat-user] [External] Re: RHEL9 support in xcat Hi, with https://github.com/xcat2/xcat-core/pull/7257 arm deployment is pretty much working for stateless and stateful deployment via grub2. On a x86 management node you can even cross-build arm stateless images. Only discovery doesn't work for arm. Feel free to test these changes. I would like to merge these changes as alpha state arm support. I think stateless and stateful deployment covers 90% of use cases already 😉 Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Matthew Alton via xCAT-user <xca...@li...<mailto:xca...@li...>> Gesendet: Freitag, 23. Februar 2024 12:23 An: Gilad Berman <gb...@le...<mailto:gb...@le...>>; xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Betreff: Re: [xcat-user] [External] Re: RHEL9 support in xcat Hi Gilad, There are no immediate plans for arm. Our focus will be primarily on x86 whilst we are in a transitional state and clearing some of the backlogged issues. After we have fully established the maintenance of project, we will be determining what a longer-term roadmap looks like and how we plan to further develop xCAT. Regards, Matt. Matthew Alton MBCS | Research & Development Lead [https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/> Phone: +44 (0)114 257 2200 Mobile: +44 (0)7943 594 084 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. From: Gilad Berman <gb...@le...<mailto:gb...@le...>> Sent: Friday, February 23, 2024 10:56 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Subject: RE: [xcat-user] [External] Re: RHEL9 support in xcat Any chance arm support is also being looked at? Gilad Berman HPC Architect, Lenovo EMEA gb...@le...<mailto:gb...@le...> +972-522554262 [cid:par...@jo...] From: Matthew Alton via xCAT-user <xca...@li...<mailto:xca...@li...>> Sent: Friday, February 23, 2024 11:31 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Subject: Re: [xcat-user] [External] Re: RHEL9 support in xcat Good morning mailing list, We, xCAT consortium, are working on various activities in the background to be able to maintain xCAT fully. We have introduced a new milestone of xCAT 2.17 that will be our first maintenance release. The main objective of this release is to move RHEL9 and directly derived operating systems (Rocky, Alma, Oracle) into officially supported by xCAT. RHEL9 support is being worked on under https://github.com/xcat2/xcat-core/issues/7416. RHEL9 has been reliably deployed from xCAT but there are a couple of known bugs with workarounds we plan to fix. This week we have been merging several PRs relating to RHEL9 and some other useful low hanging fruit sort of fixes. A full announcement will be made when all our testing is completed and we are ready to release 2.17. Regards, Matt. Matthew Alton MBCS | Research & Development Lead [https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/> Phone: +44 (0)114 257 2200 Mobile: +44 (0)7943 594 084 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. From: Imam Toufique <tec...@gm...<mailto:tec...@gm...>> Sent: Friday, February 23, 2024 5:25 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Subject: Re: [xcat-user] [External] Re: RHEL9 support in xcat I haven’t heard or seen any updates. Perhaps there is one in the horizon. Thanks Regards, Imam Toufique 213-700-5485 On Fri, Feb 23, 2024 at 7:02 AM Noah, Stuart via xCAT-user <xca...@li...<mailto:xca...@li...>> wrote: Hello Markus, Are there any new updates on EL9 support since 1/11. I know that it hasn’t been much time but I’m trying to put a migration plan together to upgrade our older cluster including the OS. Thank you Sincerely, Stuart From: Imam Toufique <tec...@gm...<mailto:tec...@gm...>> Sent: Thursday, January 11, 2024 10:46 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Subject: [External] Re: [xcat-user] RHEL9 support in xcat Hi all, thank you so much for your prompt responses. I wanted to try out rocky9 , that's why I was wondering. Markus, thanks for your valuable advice. Yeah, I wanted to get an idea about how 'ifcfg' would behave, you explained the ZjQcmQRYFpfptBannerStart WARNING: New Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hi all, thank you so much for your prompt responses. I wanted to try out rocky9 , that's why I was wondering. Markus, thanks for your valuable advice. Yeah, I wanted to get an idea about how 'ifcfg' would behave, you explained the issue exactly. --IT On Thu, Jan 11, 2024 at 10:37 AM Markus Hilger <mar...@me...<mailto:mar...@me...>> wrote: Hi, yes, EL9 distros are working mostly fine. Officially EL9 is in alpha state right now. See: https://github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes<https://urldefense.com/v3/__https:/github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vCpGhZu7$> The next release will most probably move this to the next level, but it will take some more time. Please bear with us. Some special configs like nics.nicextraparms etc. do not work (because ifcfg is deprecated and nicextraparams is not using nmcli yet). But otherwise, management node installation and stateless/stateful node deployment is working fine. Some example default osimage definitions with alma9: # <xCAT data object stanza file> alma9-x86_64-install-compute: objtype=osimage imagetype=linux osarch=x86_64 osdistroname=rhels9-x86_64 osname=linux osvers=rhels9 otherpkgdir=/install/post/otherpkgs/alma9/x86_64 pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist profile=compute provmethod=install synclists=/install/custom/install/alma/compute.alma9.synclist template=/opt/xcat/share/xcat/install/rh/compute.rhels9.tmpl # <xCAT data object stanza file> alma9-x86_64-netboot-compute: objtype=osimage exlist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.exlist imagetype=linux osarch=x86_64 osdistroname=rhels9-x86_64 osname=linux osvers=rhels9 otherpkgdir=/install/post/otherpkgs/alma9/x86_64 permission=755 pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist postinstall=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.postinstall profile=compute provmethod=netboot rootimgdir=/install/netboot/alma9/x86_64/compute synclists=/install/custom/netboot/alma/compute.alma9.synclist Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<https://urldefense.com/v3/__http:/www.megware.com/__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vME0kSu4$> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Ryan Novosielski via xCAT-user <xca...@li...<mailto:xca...@li...>> Gesendet: Donnerstag, 11. Januar 2024 17:40 An: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Ryan Novosielski <nov...@ru...<mailto:nov...@ru...>> Betreff: Re: [xcat-user] RHEL9 support in xcat I don’t know what-all happened at SC or whether a group has come together to continue it, but just remember that there’s a thread on this mailing list about the fact that xCAT is not going to be maintained going forward. -- #BlackLivesMatter ____ || \\UTGERS<file://UTGERS>, |---------------------------*O*--------------------------- ||_// the State | Ryan Novosielski - nov...@ru...<mailto:nov...@ru...> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus || \\ of NJ | Office of Advanced Research Computing - MSB A555B, Newark `' On Jan 10, 2024, at 11:54, Imam Toufique <tec...@gm...<mailto:tec...@gm...>> wrote: Hello, Are there any plans to add RHEL9 support for xcat? If so, will it be available for community use? Thanks Regards, Imam Toufique 213-700-5485 _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> -- Regards, Imam Toufique 213-700-5485 IMPORTANT WARNING: This message is intended for the use of the person or entity to which it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is strictly prohibited. Thank you for your cooperation. _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user |
From: Gilad B. <gb...@le...> - 2024-02-26 16:58:03
|
Will be great to see it merged! As a side note for those interested – Confluent worked as-is with no issues (and can work alongside xcat if needed) Gilad Berman HPC Architect, Lenovo EMEA gb...@le...<mailto:gb...@le...> +972-522554262 [cid:image001.png@01DA68E5.9D935950] From: Russell Jones <rus...@jo...> Sent: Monday, February 26, 2024 3:53 PM To: xca...@li... Subject: Re: [xcat-user] [External] Re: RHEL9 support in xcat Glad to know that worked! We have some GH nodes coming in as well. If we can stick to xcat we definitely want to do that. Hope to see these changes merged and "officially" supported soon. On 2/24/24 1:28 AM, Gilad Berman wrote: THX for that! Indeed works 😊 (grace-hopper node, rhel9.3) Gilad Berman HPC Architect, Lenovo EMEA gb...@le...<mailto:gb...@le...> +972-522554262 [cid:image001.png@01DA68E5.9D935950] From: Markus Hilger <mar...@me...><mailto:mar...@me...> Sent: Friday, February 23, 2024 6:43 PM To: Gilad Berman <gb...@le...><mailto:gb...@le...>; xCAT Users Mailing list <xca...@li...><mailto:xca...@li...> Cc: Matthew Alton <ma...@oc...><mailto:ma...@oc...> Subject: AW: [xcat-user] [External] Re: RHEL9 support in xcat Hi, with https://github.com/xcat2/xcat-core/pull/7257 arm deployment is pretty much working for stateless and stateful deployment via grub2. On a x86 management node you can even cross-build arm stateless images. Only discovery doesn't work for arm. Feel free to test these changes. I would like to merge these changes as alpha state arm support. I think stateless and stateful deployment covers 90% of use cases already 😉 Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<http://www.megware.com/> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Matthew Alton via xCAT-user <xca...@li...<mailto:xca...@li...>> Gesendet: Freitag, 23. Februar 2024 12:23 An: Gilad Berman <gb...@le...<mailto:gb...@le...>>; xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Betreff: Re: [xcat-user] [External] Re: RHEL9 support in xcat Hi Gilad, There are no immediate plans for arm. Our focus will be primarily on x86 whilst we are in a transitional state and clearing some of the backlogged issues. After we have fully established the maintenance of project, we will be determining what a longer-term roadmap looks like and how we plan to further develop xCAT. Regards, Matt. Matthew Alton MBCS | Research & Development Lead [https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/> Phone: +44 (0)114 257 2200 Mobile: +44 (0)7943 594 084 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. From: Gilad Berman <gb...@le...<mailto:gb...@le...>> Sent: Friday, February 23, 2024 10:56 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Subject: RE: [xcat-user] [External] Re: RHEL9 support in xcat Any chance arm support is also being looked at? Gilad Berman HPC Architect, Lenovo EMEA gb...@le...<mailto:gb...@le...> +972-522554262 [cid:image001.png@01DA68E5.9D935950] From: Matthew Alton via xCAT-user <xca...@li...<mailto:xca...@li...>> Sent: Friday, February 23, 2024 11:31 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Matthew Alton <ma...@oc...<mailto:ma...@oc...>> Subject: Re: [xcat-user] [External] Re: RHEL9 support in xcat Good morning mailing list, We, xCAT consortium, are working on various activities in the background to be able to maintain xCAT fully. We have introduced a new milestone of xCAT 2.17 that will be our first maintenance release. The main objective of this release is to move RHEL9 and directly derived operating systems (Rocky, Alma, Oracle) into officially supported by xCAT. RHEL9 support is being worked on under https://github.com/xcat2/xcat-core/issues/7416. RHEL9 has been reliably deployed from xCAT but there are a couple of known bugs with workarounds we plan to fix. This week we have been merging several PRs relating to RHEL9 and some other useful low hanging fruit sort of fixes. A full announcement will be made when all our testing is completed and we are ready to release 2.17. Regards, Matt. Matthew Alton MBCS | Research & Development Lead [https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/> Phone: +44 (0)114 257 2200 Mobile: +44 (0)7943 594 084 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. From: Imam Toufique <tec...@gm...<mailto:tec...@gm...>> Sent: Friday, February 23, 2024 5:25 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Subject: Re: [xcat-user] [External] Re: RHEL9 support in xcat I haven’t heard or seen any updates. Perhaps there is one in the horizon. Thanks Regards, Imam Toufique 213-700-5485 On Fri, Feb 23, 2024 at 7:02 AM Noah, Stuart via xCAT-user <xca...@li...<mailto:xca...@li...>> wrote: Hello Markus, Are there any new updates on EL9 support since 1/11. I know that it hasn’t been much time but I’m trying to put a migration plan together to upgrade our older cluster including the OS. Thank you Sincerely, Stuart From: Imam Toufique <tec...@gm...<mailto:tec...@gm...>> Sent: Thursday, January 11, 2024 10:46 AM To: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Subject: [External] Re: [xcat-user] RHEL9 support in xcat Hi all, thank you so much for your prompt responses. I wanted to try out rocky9 , that's why I was wondering. Markus, thanks for your valuable advice. Yeah, I wanted to get an idea about how 'ifcfg' would behave, you explained the ZjQcmQRYFpfptBannerStart WARNING: New Sender You have not previously corresponded with this sender. ZjQcmQRYFpfptBannerEnd Hi all, thank you so much for your prompt responses. I wanted to try out rocky9 , that's why I was wondering. Markus, thanks for your valuable advice. Yeah, I wanted to get an idea about how 'ifcfg' would behave, you explained the issue exactly. --IT On Thu, Jan 11, 2024 at 10:37 AM Markus Hilger <mar...@me...<mailto:mar...@me...>> wrote: Hi, yes, EL9 distros are working mostly fine. Officially EL9 is in alpha state right now. See: https://github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes<https://urldefense.com/v3/__https:/github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vCpGhZu7$> The next release will most probably move this to the next level, but it will take some more time. Please bear with us. Some special configs like nics.nicextraparms etc. do not work (because ifcfg is deprecated and nicextraparams is not using nmcli yet). But otherwise, management node installation and stateless/stateful node deployment is working fine. Some example default osimage definitions with alma9: # <xCAT data object stanza file> alma9-x86_64-install-compute: objtype=osimage imagetype=linux osarch=x86_64 osdistroname=rhels9-x86_64 osname=linux osvers=rhels9 otherpkgdir=/install/post/otherpkgs/alma9/x86_64 pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist profile=compute provmethod=install synclists=/install/custom/install/alma/compute.alma9.synclist template=/opt/xcat/share/xcat/install/rh/compute.rhels9.tmpl # <xCAT data object stanza file> alma9-x86_64-netboot-compute: objtype=osimage exlist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.exlist imagetype=linux osarch=x86_64 osdistroname=rhels9-x86_64 osname=linux osvers=rhels9 otherpkgdir=/install/post/otherpkgs/alma9/x86_64 permission=755 pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist postinstall=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.postinstall profile=compute provmethod=netboot rootimgdir=/install/netboot/alma9/x86_64/compute synclists=/install/custom/netboot/alma/compute.alma9.synclist Mit freundlichen Grüßen / Kind regards Markus Hilger HPC Engineer MEGWARE Computer Vertrieb und Service GmbH Tel: +49 3722 528-47 Nordstraße 19 mar...@me...<mailto:mar...@me...> 09247 Chemnitz-Röhrsdorf, Germany www.megware.com<https://urldefense.com/v3/__http:/www.megware.com/__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vME0kSu4$> Geschäftsführer: André Singer, Axel Auweter Amtsgericht: Chemnitz HRB 584 ________________________________ Von: Ryan Novosielski via xCAT-user <xca...@li...<mailto:xca...@li...>> Gesendet: Donnerstag, 11. Januar 2024 17:40 An: xCAT Users Mailing list <xca...@li...<mailto:xca...@li...>> Cc: Ryan Novosielski <nov...@ru...<mailto:nov...@ru...>> Betreff: Re: [xcat-user] RHEL9 support in xcat I don’t know what-all happened at SC or whether a group has come together to continue it, but just remember that there’s a thread on this mailing list about the fact that xCAT is not going to be maintained going forward. -- #BlackLivesMatter ____ || \\UTGERS<file://UTGERS>, |---------------------------*O*--------------------------- ||_// the State | Ryan Novosielski - nov...@ru...<mailto:nov...@ru...> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus || \\ of NJ | Office of Advanced Research Computing - MSB A555B, Newark `' On Jan 10, 2024, at 11:54, Imam Toufique <tec...@gm...<mailto:tec...@gm...>> wrote: Hello, Are there any plans to add RHEL9 support for xcat? If so, will it be available for community use? Thanks Regards, Imam Toufique 213-700-5485 _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> -- Regards, Imam Toufique 213-700-5485 IMPORTANT WARNING: This message is intended for the use of the person or entity to which it is addressed and may contain information that is privileged and confidential, the disclosure of which is governed by applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this information is strictly prohibited. Thank you for your cooperation. _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user _______________________________________________ xCAT-user mailing list xCA...@li...<mailto:xCA...@li...> https://lists.sourceforge.net/lists/listinfo/xcat-user |
From: Matthew A. <ma...@oc...> - 2024-02-26 16:34:13
|
Hi Jeff, "has anyone got a working deployment for ubuntu 20 or 22 or has everyone essentially given up on that for the time being?" There are a couple of issues on Github where potential solutions have been discussed but making xCAT provision Ubuntu 20 or 22 is hacky at best and is unsupported in xCAT as it currently stands. There was an encouraging discussion on https://github.com/xcat2/xcat-core/issues/6681 and some of the recommendations in that could work but I personally haven't had the time to be able to run through it. RHEL/Rocky/Alma operating systems are our focus in the short term, and these will carry the highest level of support and workability in xCAT. "Will I save myself a lot of trouble if we just go with CentOS 8 or 9?" Outside RHEL, Rocky and Alma 8/9 carry the most support and, as of the next release, will have the disk image info included in xCAT to make them easier to work with. CentOS Stream hasn't really been adopted within the xCAT project and in theory it should work but I'd recommend using Rocky or Alma if you do not have a specific need for something in CentOS Stream. Regards, Matt. Matthew Alton MBCS | Research & Development Lead [https://ocf.co.uk/media/0i1lzfjz/ocf-logo-strapline-2022-blk.png]<https://www.ocf.co.uk/> Phone: +44 (0)114 257 2200 Mobile: +44 (0)7943 594 084 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. From: Jeff Berry <Jef...@mr...> Sent: Monday, February 26, 2024 10:23 AM To: xCAT Users Mailing list <xca...@li...> Subject: [xcat-user] ubuntu 20 or 22 working for anyone Good morning all, has anyone got a working deployment for ubuntu 20 or 22 or has everyone essentially given up on that for the time being? Will I save myself a lot of trouble if we just go with CentOS 8 or 9? Kind regards, Jeff Berry, Computing Officer, MRC Cognition and Brain Sciences Unit |
From: Russell J. <rus...@jo...> - 2024-02-26 14:54:28
|
Glad to know that worked! We have some GH nodes coming in as well. If we can stick to xcat we definitely want to do that. Hope to see these changes merged and "officially" supported soon. On 2/24/24 1:28 AM, Gilad Berman wrote: > > THX for that! Indeed works 😊 (grace-hopper node, rhel9.3) > > *Gilad Berman * > > HPC Architect, Lenovo EMEA > > gb...@le... <mailto:gb...@le...> +972-522554262 > > *From:* Markus Hilger <mar...@me...> > *Sent:* Friday, February 23, 2024 6:43 PM > *To:* Gilad Berman <gb...@le...>; xCAT Users Mailing list > <xca...@li...> > *Cc:* Matthew Alton <ma...@oc...> > *Subject:* AW: [xcat-user] [External] Re: RHEL9 support in xcat > > Hi, > > with https://github.com/xcat2/xcat-core/pull/7257 arm deployment is > pretty much working for stateless and stateful deployment via grub2. > > On a x86 management node you can even cross-build arm stateless images. > > Only discovery doesn't work for arm. > > Feel free to test these changes. > > I would like to merge these changes as alpha state arm support. I > think stateless and stateful deployment covers 90% of use cases already 😉 > > Mit freundlichen Grüßen / Kind regards > > *Markus Hilger* > > > > > > HPC Engineer > > > > > > MEGWARE Computer Vertrieb und Service GmbH > > Tel: +49 3722 528-47 > > > > > > Nordstraße 19 > > mar...@me... <mailto:mar...@me...> > > > > > > 09247 Chemnitz-Röhrsdorf, Germany > > www.megware.com <http://www.megware.com/> > > > > > > Geschäftsführer: André Singer, Axel Auweter > > > > > > Amtsgericht: Chemnitz HRB 584 > > ------------------------------------------------------------------------ > > *Von:*Matthew Alton via xCAT-user <xca...@li...> > *Gesendet:* Freitag, 23. Februar 2024 12:23 > *An:* Gilad Berman <gb...@le...>; xCAT Users Mailing list > <xca...@li...> > *Cc:* Matthew Alton <ma...@oc...> > *Betreff:* Re: [xcat-user] [External] Re: RHEL9 support in xcat > > Hi Gilad, > > There are no immediate plans for arm. Our focus will be primarily on > x86 whilst we are in a transitional state and clearing some of the > backlogged issues. After we have fully established the maintenance of > project, we will be determining what a longer-term roadmap looks like > and how we plan to further develop xCAT. > > Regards, > > Matt. > > *Matthew Alton MBCS | **Research & Development Lead* > > > > <https://www.ocf.co.uk/> > > *Phone:* > > > > +44 (0)114 257 2200 > > *Mobile:* > > > > +44 (0)7943 594 084 > > *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> > > > > /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./ > > *From:* Gilad Berman <gb...@le...> > *Sent:* Friday, February 23, 2024 10:56 AM > *To:* xCAT Users Mailing list <xca...@li...> > *Cc:* Matthew Alton <ma...@oc...> > *Subject:* RE: [xcat-user] [External] Re: RHEL9 support in xcat > > Any chance arm support is also being looked at? > > *Gilad Berman * > > HPC Architect, Lenovo EMEA > > gb...@le... <mailto:gb...@le...> +972-522554262 > > *From:* Matthew Alton via xCAT-user <xca...@li...> > *Sent:* Friday, February 23, 2024 11:31 AM > *To:* xCAT Users Mailing list <xca...@li...> > *Cc:* Matthew Alton <ma...@oc...> > *Subject:* Re: [xcat-user] [External] Re: RHEL9 support in xcat > > Good morning mailing list, > > We, xCAT consortium, are working on various activities in the > background to be able to maintain xCAT fully. We have introduced a new > milestone of xCAT 2.17 that will be our first maintenance release. The > main objective of this release is to move RHEL9 and directly derived > operating systems (Rocky, Alma, Oracle) into officially supported by xCAT. > > RHEL9 support is being worked on under > https://github.com/xcat2/xcat-core/issues/7416. RHEL9 has been > reliably deployed from xCAT but there are a couple of known bugs with > workarounds we plan to fix. This week we have been merging several PRs > relating to RHEL9 and some other useful low hanging fruit sort of fixes. > > A full announcement will be made when all our testing is completed and > we are ready to release 2.17. > > Regards, > > Matt. > > *Matthew Alton MBCS | **Research & Development Lead* > > > > <https://www.ocf.co.uk/> > > *Phone:* > > > > +44 (0)114 257 2200 > > *Mobile:* > > > > +44 (0)7943 594 084 > > *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> > > > > /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./ > > *From:* Imam Toufique <tec...@gm...> > *Sent:* Friday, February 23, 2024 5:25 AM > *To:* xCAT Users Mailing list <xca...@li...> > *Subject:* Re: [xcat-user] [External] Re: RHEL9 support in xcat > > I haven’t heard or seen any updates. Perhaps there is one in the horizon. > > Thanks > > Regards, > > */Imam Toufique/* > > */213-700-5485/* > > On Fri, Feb 23, 2024 at 7:02 AM Noah, Stuart via xCAT-user > <xca...@li...> wrote: > > Hello Markus, > > Are there any new updates on EL9 support since 1/11. I know that > it hasn’t been much time but I’m trying to put a migration plan > together to upgrade our older cluster including the OS. > > Thank you > > Sincerely, > > Stuart > > *From:* Imam Toufique <tec...@gm...> > *Sent:* Thursday, January 11, 2024 10:46 AM > *To:* xCAT Users Mailing list <xca...@li...> > *Subject:* [External] Re: [xcat-user] RHEL9 support in xcat > > Hi all, thank you so much for your prompt responses. I wanted to > try out rocky9 , that's why I was wondering. Markus, thanks for > your valuable advice. Yeah, I wanted to get an idea about how > 'ifcfg' would behave, you explained the > > ZjQcmQRYFpfptBannerStart > > *WARNING: New Sender * > > You have not previously corresponded with this sender. > > ZjQcmQRYFpfptBannerEnd > > Hi all, > > thank you so much for your prompt responses. I wanted to try out > rocky9 , that's why I was wondering. > > Markus, thanks for your valuable advice. Yeah, I wanted to get an > idea about how 'ifcfg' would behave, you explained the issue exactly. > > --IT > > On Thu, Jan 11, 2024 at 10:37 AM Markus Hilger > <mar...@me...> wrote: > > Hi, > > yes, EL9 distros are working mostly fine. > > Officially EL9 is in alpha state right now. See: > https://github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes > <https://urldefense.com/v3/__https:/github.com/xcat2/xcat-core/wiki/XCAT_2.16.5_Release_Notes__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vCpGhZu7$> > > The next release will most probably move this to the next > level, but it will take some more time. Please bear with us. > > Some special configs like nics.nicextraparms etc. do not work > (because ifcfg is deprecated and nicextraparams is not using > nmcli yet). > > But otherwise, management node installation and > stateless/stateful node deployment is working fine. > > Some example default osimage definitions with alma9: > > # <xCAT data object stanza file> > > alma9-x86_64-install-compute: > > objtype=osimage > > imagetype=linux > > osarch=x86_64 > > osdistroname=rhels9-x86_64 > > osname=linux > > osvers=rhels9 > > otherpkgdir=/install/post/otherpkgs/alma9/x86_64 > > pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 > > pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist > > profile=compute > > provmethod=install > > synclists=/install/custom/install/alma/compute.alma9.synclist > > template=/opt/xcat/share/xcat/install/rh/compute.rhels9.tmpl > > # <xCAT data object stanza file> > > alma9-x86_64-netboot-compute: > > objtype=osimage > > exlist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.exlist > > imagetype=linux > > osarch=x86_64 > > osdistroname=rhels9-x86_64 > > osname=linux > > osvers=rhels9 > > otherpkgdir=/install/post/otherpkgs/alma9/x86_64 > > permission=755 > > pkgdir=/install/repos/almalinux/9/BaseOS/x86_64/os,/install/repos/almalinux/9/AppStream/x86_64/os,/install/repos/almalinux/9/CRB/x86_64/os,/install/repos/epel/9/Everything/x86_64 > > pkglist=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.pkglist > > postinstall=/opt/xcat/share/xcat/netboot/rh/compute.rhels9.x86_64.postinstall > > profile=compute > > provmethod=netboot > > rootimgdir=/install/netboot/alma9/x86_64/compute > > synclists=/install/custom/netboot/alma/compute.alma9.synclist > > Mit freundlichen Grüßen / Kind regards > > *Markus Hilger* > > > > > > HPC Engineer > > > > > > MEGWARE Computer Vertrieb und Service GmbH > > Tel: +49 3722 528-47 > > > > > > Nordstraße 19 > > mar...@me... <mailto:mar...@me...> > > > > > > 09247 Chemnitz-Röhrsdorf, Germany > > www.megware.com > <https://urldefense.com/v3/__http:/www.megware.com/__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vME0kSu4$> > > > > > > Geschäftsführer: André Singer, Axel Auweter > > > > > > Amtsgericht: Chemnitz HRB 584 > > ------------------------------------------------------------------------ > > *Von:*Ryan Novosielski via xCAT-user > <xca...@li...> > *Gesendet:* Donnerstag, 11. Januar 2024 17:40 > *An:* xCAT Users Mailing list <xca...@li...> > *Cc:* Ryan Novosielski <nov...@ru...> > *Betreff:* Re: [xcat-user] RHEL9 support in xcat > > I don’t know what-all happened at SC or whether a group has > come together to continue it, but just remember that there’s a > thread on this mailing list about the fact that xCAT is not > going to be maintained going forward. > > -- > #BlackLivesMatter > > ____ > || \\UTGERS <file://UTGERS>, > |---------------------------*O*--------------------------- > ||_// the State | Ryan Novosielski - nov...@ru... > || \\ University | Sr. Technologist - 973/972.0922 (2x0922) > ~*~ RBHS Campus > || \\ of NJ | Office of Advanced Research Computing - MSB > A555B, Newark > `' > > On Jan 10, 2024, at 11:54, Imam Toufique > <tec...@gm...> wrote: > > Hello, > > Are there any plans to add RHEL9 support for xcat? If so, > will it be available for community use? > > Thanks > > Regards, > > */Imam Toufique/* > > */213-700-5485/* > > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > <https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> > > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > <https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/xcat-user__;!!KOmnBZxC8_2BBQ!25BwoiPLOKWtPbLRQiEnPEYPnknXT57_gsd0f6_UtdrYX6kscFJJjsQs0FfYrHyebEaW7NZmvln8vFNBcfEV$> > > > -- > > Regards, > > */Imam Toufique/* > > */213-700-5485/* > > > > IMPORTANT WARNING: This message is intended for the use of the > person or entity to which it is addressed and may contain > information that is privileged and confidential, the disclosure of > which is governed by applicable law. If the reader of this message > is not the intended recipient, or the employee or agent > responsible for delivering it to the intended recipient, you are > hereby notified that any dissemination, distribution or copying of > this information is strictly prohibited. Thank you for your > cooperation. > > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user > > > > _______________________________________________ > xCAT-user mailing list > xCA...@li... > https://lists.sourceforge.net/lists/listinfo/xcat-user |