I will say that EL7 hasn't been tested and thus we haven't pushed updates since
3.8.0, but 3.8.0 should be plenty.
The confluent you have going is already enough to start examining OS deployment
profiles. If you would like to, you can use commands like osdeploy initialize
and osdeploy import and even imgutil build, and it won't mess with xCAT.
When you get to nodedeploy, that is the time when you have to start planning
around potential disruption as xCAT and confluent might fight over who gets to
deploy a system, and that can be confusing. We should document formally how to
mask a node from xCAT ('!*NOIP*' in mac table) to let one kick the tires with a
node...
I can help look at a few people kicking tires, certainly seems worthy of
documentation or video example...
________________________________
From: David Magda <dmagda+x...@ee.torontomu.ca>
Sent: Thursday, October 26, 2023 11:22 AM
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Subject: [External] Re: [xcat-user] xCAT-Confluent
Yes, there was perhaps auto-completion with regards Confluent/Confluence.
I currently have a (legacy?) ‘joint’ xCAT-Confluent (3.6) installation on RHEL
7 that I inherited; if one wants to fully move from xCAT to Confluent, is there
document on how to ‘extract’ oneself from xCAT? I don’t see anything that jumps
out at:
https://hpc.lenovo.com/users/
https://hpc.lenovo.com/users/documentation/
Should I simply abandon the previous installation and do a fresh install? While
there is some documentation, the system leans towards being heavily vendor-used
so people completely new to it have a steep learning curve (xCAT is/was also
challenging to get into since it was fairly vendor-focused).
> On Oct 25, 2023, at 08:51, Jarrod Johnson <jjohns...@lenovo.com> wrote:
>
> Yeah, the naming at the time was knowingly close to confluence, but thought
> the 't' was distinct. The Apache Confluent was unforseen... I'm too lazy to
> drive a name change, but perhaps one will happen one day.
>
> As far as confluent, it's been historically in github.com/xcat2/confluent,
> also pull requests. As far as discussions, currently on this list for now.
> There may be some tweaks based on conversations over the coming weeks, but
> it'll be something along those lines.
>
> The pull requests that are pending are actively being discussed, though
> admittedly we've been using chat instead of the public pull request to do
> quicker back and forth.
> From: Ryan Novosielski via xCAT-user <xcat-user@lists.sourceforge.net>
> Sent: Tuesday, October 24, 2023 12:40 PM
> To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
> Cc: Ryan Novosielski <novos...@rutgers.edu>
> Subject: Re: [xcat-user] [External] Re: Announcement: xCAT Project
> End-Of-Life planned for December 1, 2023
>
> Bear in mind that this is called “Confluent” (pronounced Con-FLU-ent), and
> not Confluence, which is a part of the Jira suite of tools (nor Apache
> Confluent — this namespace seems a little crowded).
>
> --
> #BlackLivesMatter
> ____
> || \\UTGERS, |---------------------------*O*---------------------------
> ||_// the State | Ryan Novosielski - novos...@rutgers.edu
> || \\ University | Sr. Technologist - 973/972.0922 (2x0922) ~*~ RBHS Campus
> || \\ of NJ | Office of Advanced Research Computing - MSB A555B, Newark
> `'
>
>> On Oct 24, 2023, at 12:07, David Magda <dmagda+x...@ee.torontomu.ca> wrote:
>>
>> Where is the ‘community’ for Confluence gathering? Any mailing lists? Where
>> does the code live? Bug reports and patches / pull requests?
>>
>>
>>> On Sep 21, 2023, at 17:13, Jarrod Johnson <jjohns...@lenovo.com> wrote:
>>>
>>> Yes, we are committed to it being open source ongoing. I won't rule out
>>> proprietary things built on top of it, but at least in all the ways that
>>> exist today and the CLI I don't imagine any changes. Currently, the GUI is
>>> not technically open sourced (though everyone gets the source code, but no
>>> redistribution). I do hope to at least open source our upcoming browser
>>> library that makes writing a webui with all the async behaviors a bit more
>>> trivial (which is what the next WebUI will be written with).
>>>
>>>
>> […]
>>> From: Don Avart <dav...@redlineperf.com>
>>> Sent: Thursday, September 21, 2023 1:05 PM
>>> To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
>>> Subject: Re: [xcat-user] [External] Re: Announcement: xCAT Project
>>> End-Of-Life planned for December 1, 2023
>>>
>>> I couldn’t agree more with Brian’s sentiment about xCAT. We, RedLine, have
>>> been xCAT users, integrators and occasional contributors since the end of
>>> IBM’s CSM. We’ve deployed it on numerous vendor platforms and it just
>>> works. As a small business 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.
[…]
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fxcat-user&data=05%7C01%7Cjjohnson2%40lenovo.com%7Cfb389f9ba22c4b83c4bd08dbd63794bb%7C5c7d0b28bdf8410caa934df372b16203%7C0%7C0%7C638339306446926262%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PIAAytgeyZlgTghsBfZwGFCHerw2fv043lI0seZYhb0%3D&reserved=0<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
