Thanks Jarrod.

Opened the issue: https://github.com/xcat2/xcat-core/issues/6445

Just for the sake of completude: what’s the difference between the upstream and 
the Lenovo build? Theres nothing explaining on 
hpc.lenovo.com<http://hpc.lenovo.com>.

It appears to be tight with Confluent. I heard that Confluent would eventually 
replace xcatd and become the xCAT 3.0 release. Is this still true?

Thanks.

On 14 Oct 2019, at 09:38, Jarrod Johnson 
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:

I think it is fine, but on the other hand, I can only personally provide such a 
meta package in the lenovo branches.  I could open a pull request but I can't 
guarantee that it would be accepted.


________________________________
From: Vinícius Ferrão 
<fer...@versatushpc.com.br<mailto:fer...@versatushpc.com.br>>
Sent: Saturday, October 12, 2019 11:13 PM
To: Jarrod Johnson
Cc: xCAT Users Mailing list
Subject: Re: [External] [xcat-user] xCAT forcibly disabling SELinux and 
firewalld

Jarrod, do you think it’s okay to raise an issue on 
https://github.com/xcat2/xcat-core/issues to request this new meta package?
[https://avatars3.githubusercontent.com/u/10124414?s=400&v=4]<https://github.com/xcat2/xcat-core/issues>
Issues · xcat2/xcat-core · GitHub<https://github.com/xcat2/xcat-core/issues>
github.com<http://github.com/>
Code repo for xCAT core packages. Contribute to xcat2/xcat-core development by 
creating an account on GitHub.

Thanks,

On 26 Sep 2019, at 03:54, Jarrod Johnson 
<jjohns...@lenovo.com<mailto:jjohns...@lenovo.com>> wrote:

I've been considering removing all of that from executing on rpm install (also 
enabling services to start on boot just by installing rpm)

It was added for convenience of not asking to run a setup after install but it 
is inconsistent with general rpm behavior and limits ability to use flags to 
customize behavior.

On the flip side, this would be a change that people would have to learn and 
would surprise new installs.

I might make variant of the xCAT meta package with no auto setup so that people 
won't be surprised unless they opt into the other package.

Looking for thoughts.

For wider information, it doesn't yet have os deployment, but confluent has 
been developing and designing specifically with firewall and selinux in mind, 
as well as trying to mitigate the initial setup complexity that drove us to 
create xcatconfig in the first place.  For example no more tls certs required 
for local access and os import will no longer loop mount isos (one of the 
biggest selinux problems) and avoid rewriting other service etc files in daemon 
context.  More straightforward network usage and a documented set of firewalld 
commands.
________________________________
From: Vinícius Ferrão via xCAT-user 
<xcat-user@lists.sourceforge.net<mailto:xcat-user@lists.sourceforge.net>>
Sent: Thursday, September 26, 2019 2:27:10 AM
To: xCAT Users Mailing list
Cc: Vinícius Ferrão
Subject: [External] [xcat-user] xCAT forcibly disabling SELinux and firewalld

Hello,

When installing xCAT in EL7 with yum install xCAT it’s just put SELinux in 
permissive mode and disables firewalld.

It does not even ask about it. It just does.

[root@headnode ~]# getenforce
Permissive
[root@headnode ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor 
preset: enabled)
   Active: inactive (dead)
     Docs: man:firewalld(1)

Sep 26 02:55:55 
headnode.cluster.iq.ufrj.br<http://headnode.cluster.iq.ufrj.br/> systemd[1]: 
Starting firewalld - dynamic firewall daemon...
Sep 26 02:55:56 
headnode.cluster.iq.ufrj.br<http://headnode.cluster.iq.ufrj.br/> systemd[1]: 
Started firewalld - dynamic firewall daemon.
Sep 26 03:09:18 
headnode.cluster.iq.ufrj.br<http://headnode.cluster.iq.ufrj.br/> systemd[1]: 
Stopping firewalld - dynamic firewall daemon...
Sep 26 03:09:21 
headnode.cluster.iq.ufrj.br<http://headnode.cluster.iq.ufrj.br/> systemd[1]: 
Stopped firewalld - dynamic firewall daemon.

There’s a way to avoid this behaviour?

Thanks,

PS: I’m aware of the consequences of firewalld and SELinux in xCAT environments.
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net<mailto: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

Reply via email to