Bug 1396584 - add firewalld service file for corosync
Summary: add firewalld service file for corosync
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Friesse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 16:37 UTC by Paolo Bonzini
Modified: 2016-11-18 21:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-18 21:36:54 UTC
Type: Bug


Attachments (Terms of Use)

Description Paolo Bonzini 2016-11-18 16:37:47 UTC
Adding a service file enables configuring firewalld like

   sudo firewall-cmd --zone=public --add-service=corosync --permanent

The file looks should be ini /usr/lib/firewalld/services/corosync.xml and should look like this:

<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>corosync</short>
  <description>The Corosync Cluster Engine Executive is a Group Communication System with additional features for implementing high availability within applications. Enable this option if your machine is a node in a Corosync cluster.</description>
  <port protocol="udp" port="5404-5406"/>
</service>

Comment 1 Andrew Price 2016-11-18 16:43:40 UTC
There is a high-availability service file in firewalld. Does that suffice?

$ rpm -qf /usr/lib/firewalld/services/high-availability.xml
firewalld-0.4.4.1-1.fc24.noarch
$ cat /usr/lib/firewalld/services/high-availability.xml
<?xml version="1.0" encoding="utf-8"?>
<service>
  <short>Red Hat High Availability</short>
  <description>This allows you to use the Red Hat High Availability (previously named Red Hat Cluster Suite). Ports are opened for corosync, pcsd, pacemaker_remote, dlm and corosync-qnetd.</description>
  <port protocol="tcp" port="2224"/>
  <port protocol="tcp" port="3121"/>
  <port protocol="tcp" port="5403"/>
  <port protocol="udp" port="5404"/>
  <port protocol="udp" port="5405"/>
  <port protocol="tcp" port="21064"/>
</service>

Comment 2 Paolo Bonzini 2016-11-18 21:36:54 UTC
Sure, sorry I missed that.


Note You need to log in before you can comment on or make changes to this bug.