Skip to content

Conversation

@mboisson
Copy link
Member

@mboisson mboisson commented Jun 9, 2025

This is to address #418

It does not yet address the firewall rules. I am not entirely sure I understand what rules should be applied.

@mboisson mboisson changed the title add initial support for client side quotas Add support for client side quotas Jun 9, 2025
@mboisson
Copy link
Member Author

mboisson commented Jun 10, 2025

Looking with netstat -tulpn | grep LISTEN on the management node, there are about 45 open ports. Excluding ports that are open just for local host, we have:

  • alertmanager
  • httpd
  • java
  • kadmind
  • krb5kdc
  • mokey
  • node_exporter
  • ns-slapd
  • prometheus
  • prometheus-sl
  • rsyslogd
  • slurmctld
  • slurmdbd
  • sshd
    to which we add rpc.rquotad.

Seems like the ports are always the same on different clusters.
Also, it seems that rpc.rquotad always uses the same port (815, contrary to 111 state in the RH doc).

@cmd-ntrf, I guess we would need to close down the firewall to all ports first, and only open the firewall in the puppet code that enables each of those services ?

@mboisson
Copy link
Member Author

Note for future self, firewall rules will wait on #406 when iptables is replaced with nftables

@mboisson mboisson force-pushed the client_quotas branch 2 times, most recently from a46b50d to df163d5 Compare June 10, 2025 19:47
@cmd-ntrf cmd-ntrf merged commit 7078d24 into ComputeCanada:main Aug 25, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Install quota-rpc and activate rpcbind to allow quota queries from nodes other than the NFS server

2 participants