[ClusterLabs] How to generate RPMs for Pacemaker release 2.x on Centos

[Ken Gaillot]

On Mon, 2018-10-15 at 14:39 +0200, Klaus Wenninger wrote:
> On 10/15/2018 01:52 PM, Lopez, Francisco Javier [Global IT] wrote:
> > Hello guys !
> > 
> > We are planning to use Pacemaker as a base HA Software in our
> > Company.
> > 
> > Our requirements will be:
> > 
> > - Centos-7
> > - PostgreSql-10
> > 
> > We did several tests with Pacemaker release 1.1.8 and fixed the
> > problems found with
> > the RA. We finally created new RPMs from source (4.x).
> > 
> > Now we want to test Pacemaker release 2.x but, as we will have to
> > create some clusters,
> > we want to create new RPMs for this release instead of doing manual
> > installation on
> > each new box. As per what I see the RPMs for our Centos have not
> > been created yet.
> > 
> > We could run 'autogen' + 'configure' but I do not find the way to
> > generate the RPMs.
> > Anyone could share with me the correct paths to do this please ?
>  
> The spec-file found in the pacemaker-github-repo should work straight
> forward
> using mock to build against the repos of your Centos-Version.
> Just check that you are on current corosync, libqb, knet, ...
> Pacemaker 2 seems to build well against the packages coming with
> Centos 7.5.
> Maybe others can comment on how advisable it is running that combo
> though.
> 
> Klaus

Also, there is a convenient target for building RPMs from the spec
file, you can just run "make rpm" (after autogen.sh + configure).

> 
> > Perhaps there are some steps written somewhere and I did not find
> > them out ...
> > 
> > Appreciate your help.
> > 
> > Regards
> > Javier
> >         Francisco Javier	 	Lopez	  IT System E
> > ngineer	 | 	Global IT	  O: +34 619 728 249	
> >  | 	M: +34 619 728 249	 | 
> > franciscojavier.lopez at solera.com	 | 	Solera.com	
> >   Audatex Datos, S.A.	 | 	Avda. de Bruselas, 36, Sali
> > da 16, A‑1 (Diversia)	, 	Alcobendas	, 	
> > Madrid	, 	28108	, 	Spain		
> >  
> > 
> > "This e-mail, any associated files and the information contained in
> > them are confidential and is intended for the addressee(s) only. If
> > you have received this message in error please notify the
> > originator and delete the email immediately. The unauthorised use,
> > disclosure, copying or alteration of this message is strictly
> > forbidden. E-mails to and from the company are monitored for
> > operational reasons and in accordance with lawful business
> > practices. Any opinions expressed are those of the individual and
> > do not necessarily represent the views of the company. The company
> > does not conclude contracts by email and all negotiations are
> > subject to contract. We make every effort to maintain our network
> > free from computer viruses but accept no responsibility for any
> > viruses which might be transferred by this e-mail."
> > 
> > 
> > _______________________________________________
> > Users mailing list: Users at clusterlabs.org
> > https://lists.clusterlabs.org/mailman/listinfo/users
> > 
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratc
> > h.pdf
> > Bugs: http://bugs.clusterlabs.org
>  
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.
> pdf
> Bugs: http://bugs.clusterlabs.org
-- 
Ken Gaillot <kgaillot at redhat.com>