Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Thank you for bringing this suggestion to the mailing list, Samveen. There have been parallel discussions occurring in the GitHub issue and the mailing list and it is difficult to tell if everyone is following along with both discussions. I agree that handing off the xCAT ecosystem to a new entity is a question that will need to be resolved if we can identify a new set of maintainers to continue the project. When discussing how we might handle handing off the project internally, Software in the Public Interest (SPI) was discussed as a possible avenue to pursue. If a critical mass of new maintainers can be achieved, I think there are a variety of options that would be workable. For package signing keys, I would suggest transitioning to a new set of keys and a public announcement about the transition. The interest in continuing the project is well received and IBM is interested in continuing to participate in the project in a reduced capacity if the project is able to continue. From: Samveen Gulati via xCAT-user Sent: Monday, October 2, 2023 1:52 PM To: xcat-user@lists.sourceforge.net Cc: Samveen Gulati Subject: [EXTERNAL] Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023 Hi all, There are a few sticking points for handing off the xCAT ecosystem to any entity outside IBM. The important bits that I can immediately think of are as below: - Continuity of package repositories and Package signing keys. - Ownership of the Github XCAT2 organization and all attached resources - Project ownership of the Sourceforge project - Domains attached to xCAT (xcat.org et. al.) - License ownership >From IBM's perspective, all these need to be handed of to a trustworthy >entity, as any entity in control of this intellectual equity can easily >destroy the ecosystem at best, and easily and silently spread malware across >all the clusters at worst. My suggestion for a solution to this problem was that xcat community join an existing umbrella project that can ensure that both IBM as well as the community are safe and secure during and after any transition period (some more info at https://github.com/xcat2/xcat-core/issues/7405#issuecomment-1715422156 ). However, this will require some amount of prep work. If anyone has any experience with umbrella projects, it'll be great to have some guidance on how to proceed. Kilian Cavalotti (Stanford University HPC) checked with Stanford's organizational entities, but there isn't any entity that might be able to handle something like this. Apache's Incubator might be nice, but it's a long process, and the code will need to be re-licensed to something compatible with ASL to be allowed into the incubator. I haven't the legal skills to compare, but if someone has the bandwidth to audit the licensing, it would be another task off the ToDo list (which is yet to be made). In the meantime, I'm reading the docs at https://www.spi-inc.org/ already, but would greatly appreciate non-neophyte help. 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 ..) ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
in the greater HPC marketplace we have many customers that rely on xCAT and we will need to work with them to identify an alternative should xCAT discontinue. I’ve reached out to the IBM team as well as Jarrod from Lenovo and others in the community. I am very interested in putting together a plan that would continue to provide an open source option that is platform agnostic. With respect to Jarrod’s comments about using Confluent as a starting point for future development of xCAT, there are a number of considerations. Here are a few. * Is Lenovo committed to keeping Confluent open-source * Is Lenovo open to integration of features/capabilities of non-Lenovo vendors * Governance. Who controls changes to the code base and future development directions * Does xCAT remain it’s own project and share code with Confluent or do they become one project There are definitely other considerations, but I just wanted to get a few thoughts out there. My opinion is that Jarrod’s idea is one that should be given significant thought and debate. xCAT2 was, according to everything I’ve read, a complete rewrite of the original xCAT. Therefore, adopting Confluent as the next version is not a bridge too far, in my opinion. I also can’t speak to the original intentions of IBM when xCAT2 was released with respect to multi-vendor support. I can say that as a member of the xCAT community I would like to see the project continue as open source and vendor agnostic. I would really like to hear from anyone that is interested in keeping the project alive. I’m hopeful that we can reach a solution as a community. Best Regards, Don Avart CTO RedLine Performance Solutions, LLC (703) 634-5686 dav...@redlineperf.com<mailto:dav...@redlineperf.com> On Sep 21, 2023, at 10:59 AM, Jarrod Johnson mailto:jjohns...@lenovo.com>> wrote: There are at least some options I've heard discussed, if anyone has feedback: -Someone to take over the xCAT 2.x codebase as-is, adding some missing stuff like Ubuntu 20+ support, RHEL9, etc. I don't know that anyone has volunteered to go all in on all that exactly yet. -Try to establish a community around confluent (potentially as 'xCAT 3'). This may suggest some sort of rebranding and/or governance changes, but basically starting from confluent instead of xCAT 2 for the xCAT-like experience. Not precisely xCAT-like but was designed "by one of the designers of xCAT 2" with a lot of sensibilities preserved. Given that there's not much in the way of 'backwards compatibility', I'm cautious about the 'xCAT 3' branding, and while I would be a consistent contributor across xCAT 2.0 through 2.8 and then confluent, it would technically be a change from an IBM to Lenovo contributions, which I could see being a challenge. -The current default trajectory is an archived project and people having to decide for themselves what to do next (only 'all-in-one' options that I know to be cross-platform are Bright and Confluent, if just OS deployment, then I commonly see Foreman used for diskful, with Warewulf being an option for mostly diskless scenario). Obviously, I like Confluent best, but of course I would. From: Brian Joiner mailto:martinitime1...@gmail.com>> Sent: Thursday, September 21, 2023 9:57 AM To: xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net> mailto:xcat-user@lists.sourceforge.net>> Subject: [External] Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023 This is the saddest thing I've hear in some time. I've had the chance to support customers with Bright, HP cluster manager, and xCAT. xCAT was by far the best. Thank you for all your work, I hope that a transition can happen! Thanks, Brian J On 9/1/23 11:49 AM, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://lists.sourceforge.net/lists/listinfo/xcat-user> ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net> https://lists.sourceforge.net/lis
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
I can get Confluent to deploy a node with the firewall off, but not on. Does anyone know the rule that should let this through? I have enabled all the relevant services in firewalld (with iptables backend) sshd, tftp, https, dhcp, etc. I even opened ports 69, but no joy. public (active) target: default icmp-block-inversion: no interfaces: ens192 ens224 sources: services: cockpit dhcp dhcpv6-client https ssh tftp ports: 427/udp 1900/udp 69/tcp 69/udp 4011/tcp protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Success logs: Sep 29 14:11:05 confluent01 systemd[1]: Stopping firewalld - dynamic firewall daemon... Sep 29 14:11:06 confluent01 systemd[1]: firewalld.service: Deactivated successfully. Sep 29 14:11:06 confluent01 systemd[1]: Stopped firewalld - dynamic firewall daemon. Sep 29 14:11:06 confluent01 systemd[1]: firewalld.service: Consumed 12.819s CPU time. Sep 29 14:11:17 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:11:18 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.103 to 00:0c:29:7f:c8:10 via ens224 Sep 29 14:11:19 confluent01 dhcpd[4966]: DHCPREQUEST for 10.13.13.11 (10.13.13.5) from 00:0c:29:7f:c8:10 via ens224: unknown lease 10.13.13.11. *Sep 29 14:11:20 confluent01 in.tftpd[13121]: tftp: client does not accept options** **Sep 29 14:11:20 confluent01 in.tftpd[13122]: Client :::10.13.13.11 finished confluent/x86_64/ipxe.kkpxe* Sep 29 14:11:22 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:11:22 confluent01 dhcpd[4966]: DHCPREQUEST for 10.13.13.11 (10.13.13.5) from 00:0c:29:7f:c8:10 via ens224: unknown lease 10.13.13.11. Sep 29 14:11:23 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.104 to 00:0c:29:7f:c8:10 via ens224 Failed attempt: no in.tftpd Sep 29 14:23:00 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:01 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.103 to 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:02 confluent01 dhcpd[4966]: DHCPREQUEST for 10.13.13.11 (10.13.13.5) from 00:0c:29:7f:c8:10 via ens224: unknown lease 10.13.13.11. Sep 29 14:23:07 confluent01 dhcpd[4966]: DHCPRELEASE of 10.13.13.11 from 00:0c:29:7f:c8:10 via ens224 (not found) Sep 29 14:23:07 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:07 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.103 to 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:11 confluent01 dhcpd[4966]: DHCPREQUEST for 10.13.13.11 (10.13.13.5) from 00:0c:29:7f:c8:10 via ens224: unknown lease 10.13.13.11. Sep 29 14:23:19 confluent01 dhcpd[4966]: DHCPRELEASE of 10.13.13.11 from 00:0c:29:7f:c8:10 via ens224 (not found) Sep 29 14:23:19 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:19 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.103 to 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:27 confluent01 dhcpd[4966]: DHCPREQUEST for 10.13.13.11 (10.13.13.5) from 00:0c:29:7f:c8:10 via ens224: unknown lease 10.13.13.11. Sep 29 14:23:43 confluent01 dhcpd[4966]: DHCPRELEASE of 10.13.13.11 from 00:0c:29:7f:c8:10 via ens224 (not found) Sep 29 14:23:43 confluent01 dhcpd[4966]: DHCPDISCOVER from 00:0c:29:7f:c8:10 via ens224 Sep 29 14:23:43 confluent01 dhcpd[4966]: DHCPOFFER on 10.13.13.103 to 00:0c:29:7f:c8:10 via ens224 Other than this firewall rule, the setup was fairly easy. The next step will be the replacement method for postscripts. Thanks, Brian J On 9/21/23 8:57 AM, Brian Joiner wrote: This is the saddest thing I've hear in some time. I've had the chance to support customers with Bright, HP cluster manager, and xCAT. xCAT was by far the best. Thank you for all your work, I hope that a transition can happen! Thanks, Brian J On 9/1/23 11:49 AM, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
This is the saddest thing I've hear in some time. I've had the chance to support customers with Bright, HP cluster manager, and xCAT. xCAT was by far the best. Thank you for all your work, I hope that a transition can happen! Thanks, Brian J On 9/1/23 11:49 AM, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
This is TBD and long term it depends on what happens with this mailing list, the needs of the xCAT community, and the needs of the confluent community. In the meantime, feel free to discuss confluent on this mailing list. From: Daniel Letai Sent: Monday, September 4, 2023 12:56 AM To: xcat-user@lists.sourceforge.net Subject: [EXTERNAL] Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023 Will this mailing list continue to serve confluent users, or is there another mailing list? On 01/09/2023 19: 49: 46, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few ZjQcmQRYFpfptBannerStart This Message Is From an Untrusted Sender You have not previously corresponded with this sender. <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2Y-hArQfanP6MEYbuOFvTd0i9H_npgHrRqV3_X95mC_M_Err7orq-l7gHZUBwJBECPOPmGOTynLgKkzaB7x50zFHBAVSWGlJSg4$> Report Suspicious ZjQcmQRYFpfptBannerEnd Will this mailing list continue to serve confluent users, or is there another mailing list? On 01/09/2023 19:49:46, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net<mailto:xCAT-user@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/xcat-user<https://lists.sourceforge.net/lists/listinfo/xcat-user> -- Regards, Daniel Letai +972 (0)505 870 456 ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Hi Kurt, Speaking for myself only, I would like to see xCAT continue on with a new set of maintainers. However, maintaining xCAT requires effort, and I want to make sure that any new team that forms to take over responsibility for the project has a good chance of success. A few xCAT contributors have indicated they are interested in helping to keep the project going here: https://github.com/xcat2/xcat-core/issues/7405 I have also discussed this privately with some other xCAT contributors that have indicated they could potentially assist the project going forward. A viable proposal would need to include 6+ people who have been actively using, contributing to, or maintaining xCAT for a few years. Ideally everyone in the group would be using xCAT regularly in a professional capacity. Having formal organizational backing would be a huge asset but is not a hard requirement. Without formal organizational backing, everyone would presumably be supporting xCAT as a part time activity in addition to other responsibilities. In a situation where the team is mostly made up of part-time volunteers, having more people to share the workload would be an asset. Prior experience with maintaining an open-source project would also be an asset but is not a hard requirement. Ideally the community will recognize the members of the group from previous activity on the project. As a first step, I would suggest that anyone that feels they are a good fit for maintaining or contributing to the project going forward and has the willingness and ability to dedicate time to the project should take a few minutes to reply with a brief introduction and a statement about how much time they think they can devote to project per week along with any areas of interest (specific operating systems, hardware configurations, or xCAT features they use regularly). I can assist in the transition, but I think it will be best for the prospective new maintainers to self-organize and develop a process and plan for how they would envision running the project in the future. If a critical mass of prospective new maintainers is able to form, I can share information about how we have been handling different aspects of the project. Areas to consider: xcat.org website xcat-user mailing list xcat2 github Issue triage Fix, test, verify issues New feature implementation Community support Release planning Test hardware for manual and automated testing Daily build automation Daily test automation Finally, while I personally would like to see the project continue, I have to operate within certain constraints imposed by my employment. The exact mechanics of how certain pieces of the project could be transitioned is still TBD. I will need to pitch any proposal to other interested parties at my employer for final approval. From: Kurt H Maier via xCAT-user Sent: Friday, September 1, 2023 3:00 PM To: xCAT Users Mailing list Cc: Kurt H Maier Subject: [EXTERNAL] Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023 On Fri, Sep 01, 2023 at 04:49:46PM +, Nathan A Besaw via xCAT-user wrote: > We would consider transitioning responsibility for the project to a new group > of maintainers if members of the xCAT community can develop a viable proposal > for future maintenance. Can you describe what you'd like to see in such a proposal in order for you to consider it viable? Thanks, khm ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Will this mailing list continue to serve confluent users, or is there another mailing list? On 01/09/2023 19:49:46, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user -- Regards, Daniel Letai +972 (0)505 870 456 ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
I’m also interested in understanding what you all are looking for. Glad to setup a zoom call to get more details. Best Regards, Don Avart CTO RedLine Performance Solutions, LLC (703) 634-5686 dav...@redlineperf.com > On Sep 1, 2023, at 3:00 PM, Kurt H Maier via xCAT-user > wrote: > > On Fri, Sep 01, 2023 at 04:49:46PM +, Nathan A Besaw via xCAT-user wrote: >> We would consider transitioning responsibility for the project to a new >> group of maintainers if members of the xCAT community can develop a viable >> proposal for future maintenance. > > Can you describe what you'd like to see in such a proposal in order for > you to consider it viable? > > Thanks, > khm > > > ___ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
On Fri, Sep 01, 2023 at 04:49:46PM +, Nathan A Besaw via xCAT-user wrote: > We would consider transitioning responsibility for the project to a new group > of maintainers if members of the xCAT community can develop a viable proposal > for future maintenance. Can you describe what you'd like to see in such a proposal in order for you to consider it viable? Thanks, khm ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Really sad news. Sent from my iPhone On 1 Sep 2023, at 13:52, Nathan A Besaw via xCAT-user wrote: Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
Re: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Wow !! its really said to read that friends . Wish you all the best . From: Nathan A Besaw via xCAT-user Sent: Friday, 1 September 2023 19:50 To: xCAT Users Mailing list Cc: Nathan A Besaw Subject: [xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023 Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. זהירות: מקור הדואל הזה הוא מחוץ למטריקס. חל איסור ללחוץ על קישורים או לפתוח קבצים מצורפים אלא אם כן השולח מוכר והתוכן בטוח Caution: The source of this email is from outside Matrix. it is forbidden to click on links or open attachments unless you recognize the sender and know the content is safe. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
[xcat-user] Announcement: xCAT Project End-Of-Life planned for December 1, 2023
Mark Gurevich, Peter Wong, and I have been the primary xCAT maintainers for the past few years. This year, we have moved on to new roles unrelated to xCAT and can no longer continue to support the project. As a result, we plan to archive the project on December 1, 2023. xCAT 2.16.5, released on March 7, 2023, is our final planned release. We would consider transitioning responsibility for the project to a new group of maintainers if members of the xCAT community can develop a viable proposal for future maintenance. Thank you all for you support of the project over the past 20+ years. ___ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
