Hi folks, The RPM packages provided on bird.network.cz have a single init script for managing both bird and bird6. This script has some heuristic rules to determine which daemon(s) to manage, but its status subcommand is unable to recognize "I am managing only one daemon" from "the other one has crashed". Basically, "service bird status" is broken; furthermore, the "one init script for two daemons" model makes it awkward to manage BIRD with Puppet. I have rebuilt the latest package locally with separate init scripts for bird and bird6 as a workaround for this issue. I have also ripped out the whole "check whether we need this daemon" logic as it makes no real sense with separate services. HTH, -- A
On 1.8.2013 16:32, Arnaud Gomes-do-Vale wrote:
Hi folks,
Hi Arnaud, Thank you, I will look at it. However init script are deprecated at Fedora. Ondrej
The RPM packages provided on bird.network.cz have a single init script for managing both bird and bird6. This script has some heuristic rules to determine which daemon(s) to manage, but its status subcommand is unable to recognize "I am managing only one daemon" from "the other one has crashed". Basically, "service bird status" is broken; furthermore, the "one init script for two daemons" model makes it awkward to manage BIRD with Puppet.
I have rebuilt the latest package locally with separate init scripts for bird and bird6 as a workaround for this issue. I have also ripped out the whole "check whether we need this daemon" logic as it makes no real sense with separate services.
HTH,
On 08/01/2013 05:35 PM, Ondrej Filip wrote:
Hi Arnaud, Thank you, I will look at it. However init script are deprecated at Fedora.
Ondrej Maybe they do deprecated but there is a reason why lot's of people do use CentOS for their primary Infrastructure servers.
Fedora is a very good OS but with very new ideas which not all admins can adopt in a sec and takes a while to migrate a stable system that works for about 5+ years to a less stable or a more frequently updated system. I do not see many admins just "update" their working perfectly systems to a less perfected system. This is one of the differences between ISP and ENTERPRISE environments. Eliezer
Hey guys, First of all I fully agree with Arnaud's changes, it is definetely a neater design. I haven't look at the init script yet but if the code follows his ideas then it is an improvement (especially for puppet mgt). Merci Arnaud.
[..] However init script are deprecated at Fedora is a very good OS but with very new ideas [..] Ondrej, Eliezer, To summarize all RHELs are still using init.d script however RHEL7 and EL clones will use systemd. So Q1 2014 or so, the systemd script will start to be more relevant for people that use RHEL in production (like 90% of the audience that use a RedHat OS or clone in production).
Indeed Fedora is designed for Workstation, not servers IMO. Fedora is a testbed for improvements that will be carefully selected for the next RHEL. Thomas
I agree with Thomas. I think that discarding old RHEL init.d (upstart) support is a hasty decision: bird is for production systems and linux distro for production environment which uses RPM packages is RHEL or it clones (mostly). Although it is no matter for me because I'm not using bird rpm package provided by developers. I'm rebuilding it from src.rpm with bgp summary patch (by the way, does a honorable developers plans to implement 'bgp summary' command in vanilla bird?) and my initscript patch. 2013/8/2 Thomas Guthmann <tguthmann@iseek.com.au>
Hey guys,
First of all I fully agree with Arnaud's changes, it is definetely a neater design. I haven't look at the init script yet but if the code follows his ideas then it is an improvement (especially for puppet mgt). Merci Arnaud.
[..] However init script are deprecated at
Fedora is a very good OS but with very new ideas [..]
Ondrej, Eliezer, To summarize all RHELs are still using init.d script however RHEL7 and EL clones will use systemd. So Q1 2014 or so, the systemd script will start to be more relevant for people that use RHEL in production (like 90% of the audience that use a RedHat OS or clone in production).
Indeed Fedora is designed for Workstation, not servers IMO. Fedora is a testbed for improvements that will be carefully selected for the next RHEL.
Thomas
On 2.8.2013 07:11, Stanislav Datskevich wrote:
I agree with Thomas. I think that discarding old RHEL init.d (upstart) support is a hasty decision: bird is for production systems and linux distro for production environment which uses RPM packages is RHEL or it clones (mostly).
Although it is no matter for me because I'm not using bird rpm package provided by developers. I'm rebuilding it from src.rpm with bgp summary patch (by the way, does a honorable developers plans to implement 'bgp summary' command in vanilla bird?) and my initscript patch.
I will look at the initscripts. But we haven't agreed to accept 'bgp summary'. It is not align with BIRD philosophy. But will continue discussing about it. Ondrej
2013/8/2 Thomas Guthmann <tguthmann@iseek.com.au <mailto:tguthmann@iseek.com.au>>
Hey guys,
First of all I fully agree with Arnaud's changes, it is definetely a neater design. I haven't look at the init script yet but if the code follows his ideas then it is an improvement (especially for puppet mgt). Merci Arnaud.
[..] However init script are deprecated at
Fedora is a very good OS but with very new ideas [..]
Ondrej, Eliezer, To summarize all RHELs are still using init.d script however RHEL7 and EL clones will use systemd. So Q1 2014 or so, the systemd script will start to be more relevant for people that use RHEL in production (like 90% of the audience that use a RedHat OS or clone in production).
Indeed Fedora is designed for Workstation, not servers IMO. Fedora is a testbed for improvements that will be carefully selected for the next RHEL.
Thomas
participants (5)
-
Arnaud Gomes-do-Vale -
Eliezer Croitoru -
Ondrej Filip -
Stanislav Datskevich -
Thomas Guthmann