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

2018-10-17 Thread Ken Gaillot 
On Wed, 2018-10-17 at 15:58 +, Lopez, Francisco Javier [Global IT]
wrote:
> Hello guys.
> 
> I finally created the RPMs for Pacemaker and Resource Agents. I will
> paste
> in this thread the way to do that so it can help any other like me :-
> )
> 
> I need a final update, hopefully, from you guys about this issue ...
> 
> I need to know if there is any compatibility or certification matrix
> somewhere.
> I'm asking this because as I'm creating the packages from source, I
> need to be
> sure that Pacemaker, PCS, Corosync, the Agents, ... releases match.
> This would
> guarantee that if we find an issue using the product, the problem is
> not a 
> compatibility among them.

For the most part, each component is written to be independent of other
components' versions.

The big exception is pcs, which is closely tied to both corosync and
pacemaker versions.

The pcs 0.9 series is compatible with corosync 2 and pacemaker 1.1,
while the pcs 0.10 series is compatible with the new kronosnet project,
corosync 3, and pacemaker 2.0. pcs may work "most of the time" with
other versions, but full compatibility requires that line-up.

I'd say your choices from easiest to hardest are:

* Stick with what you have. If a pcs command works, you're fine. If a
pcs command fails, figure out how to do the same thing with direct
editing of corosync.conf and the pacemaker CLI tools.

* Switch to the pacemaker 1.1 series (either distro-provided or your
own build), and keep everything else as you have it. You don't lose
much, since most bug fixes and some features from 2.0 have been
backported to 1.1. This will likely continue for at least the next year
or two, though at some point the frequency of backports will decline.
This would buy you enough time for the distros to catch up to the newer
versions of everything.

* Build kronosnet, corosync 3, and pcs 0.10 yourself. This would put
you on the "way of the future" but obviously is more maintenance for
you when it comes to updates, and you lose the early release of
backported bugfixes that distro packages include.

> 
> These are the releases I have now:
> 
> - Pacemaker: 2.0.0, created by me.
> - Resource Agents: 4.1.1, created by me.
> - Corosync: corosynclib-2.4.3-2.el7_5.1.x86_64
>     corosync-2.4.3-2.el7_5.1.x86_64
>   Installed from repos.
> - PCS: pcs-0.9.162-5.el7.centos.1.x86_64
>   Installed from repos.
> 
> As before, I appreciate all your help
> 
> Best regards
> 
> 
> Francisco Javier      Lopez     IT System Eng
> ineer  |  Global IT     O: +34 619 728 249
>  |    M: +34 619 728 249   | 
> franciscojavier.lo...@solera.com   |  Solera.com  
>   Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida
>  16, A‑1 (Diversia)   ,   Alcobendas  ,   Madr
> id,   28108   ,   Spain     On
> 15/10/18 16:42, Ken Gaillot wrote:
> > On Mon, 2018-10-15 at 14:37 +, Lopez, Francisco Javier [Global
> > IT]
> > wrote:
> > > Klaus/Ken.
> > > 
> > > Thx. for you reply.
> > > 
> > > The issue is ...
> > > 
> > > - I downloaded the source from GIT.
> > > - Downloaded the OS required packages.
> > > - Unzipped the source.
> > > - ./autogen.sh + ./configure ---> OK
> > > - Then, indeed, I tried: make rpm 
> > >   But I got thousands of errors:
> > 
> > Ah, I forgot it uses information from the repository. Rather than
> > download the source, you'd have to git clone the repository, and
> > run
> > from there. By default you'll be in the latest master branch; if
> > you
> > prefer to run a released version, you can check it out like "git
> > checkout Pacemaker-2.0.0".
> > 
> > > $ make rpm
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > fatal: Not a git repository (or any of the parent directories):
> > > .git
> > > /bin/sh: -c: line 0: syntax error near unexpected token
> > > `Pacemaker-*'
> > > /bin/sh: -c: line 0: `case  in Pacemaker-*) echo '' | cut -c11-;; 
> > > *)
> > > git log --pretty=format:%h -n 1 '';; esac'
> > > ...
> > > ...
> > > 
> > > What made me think, that downloading the source to the box I'm
> > > testing could not be the
> > > best, so I decided to ask the experts.
> > > 
> > > Best Regards
> > > 
> > > Francisco Javier      Lopez     IT System
> > >  Eng
> > > ineer  |  Global IT     O: +34 619 728 249
> > >  |    M: +34 619 728 249   | 
> > > franciscojavier.lo...@solera.com   |  Solera.com  
> > >   Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Sa
> > > lida
> > >  16, A‑1 (Diversia)   ,   Alcobendas  ,   
> > > Madr
> > > id,   28108   , 

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

2018-10-17 Thread Lopez, Francisco Javier [Global IT] 
Hello guys.

I finally created the RPMs for Pacemaker and Resource Agents. I will paste
in this thread the way to do that so it can help any other like me :-)

I need a final update, hopefully, from you guys about this issue ...

I need to know if there is any compatibility or certification matrix somewhere.
I'm asking this because as I'm creating the packages from source, I need to be
sure that Pacemaker, PCS, Corosync, the Agents, ... releases match. This would
guarantee that if we find an issue using the product, the problem is not a
compatibility among them.

These are the releases I have now:

- Pacemaker: 2.0.0, created by me.
- Resource Agents: 4.1.1, created by me.
- Corosync: corosynclib-2.4.3-2.el7_5.1.x86_64
corosync-2.4.3-2.el7_5.1.x86_64
  Installed from repos.
- PCS: pcs-0.9.162-5.el7.centos.1.x86_64
  Installed from repos.

As before, I appreciate all your help

Best regards


Francisco Javier​   Lopez

IT System Engineer   |  Global IT

O: +34 619 728 249|  M: +34 619 728 
249|

franciscojavier.lo...@solera.com   
 |  Solera.com

Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida 16, A‑1 
(Diversia),   Alcobendas  ,   Madrid  ,   28108   , 
  Spain


[cid:image336898.png@3855FCA3.73CA15EA]



On 15/10/18 16:42, Ken Gaillot wrote:

On Mon, 2018-10-15 at 14:37 +, Lopez, Francisco Javier [Global IT]
wrote:


Klaus/Ken.

Thx. for you reply.

The issue is ...

- I downloaded the source from GIT.
- Downloaded the OS required packages.
- Unzipped the source.
- ./autogen.sh + ./configure ---> OK
- Then, indeed, I tried: make rpm
  But I got thousands of errors:



Ah, I forgot it uses information from the repository. Rather than
download the source, you'd have to git clone the repository, and run
from there. By default you'll be in the latest master branch; if you
prefer to run a released version, you can check it out like "git
checkout Pacemaker-2.0.0".



$ make rpm
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
/bin/sh: -c: line 0: syntax error near unexpected token `Pacemaker-*'
/bin/sh: -c: line 0: `case  in Pacemaker-*) echo '' | cut -c11-;; *)
git log --pretty=format:%h -n 1 '';; esac'
...
...

What made me think, that downloading the source to the box I'm
testing could not be the
best, so I decided to ask the experts.

Best Regards

Francisco JavierLopez IT System Eng
ineer|  Global IT O: +34 619 728 249
 |  M: +34 619 728 249   |
franciscojavier.lo...@solera.com   
 |  Solera.com
  Audatex Datos, S.A.|  Avda. de Bruselas, 36, Salida
 16, A‑1 (Diversia) ,   Alcobendas  ,   Madr
id  ,   28108   ,   Spain On
15/10/18 16:27, Ken Gaillot wrote:


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 JavierLopez IT Syst
em E
ngineer  |  Global IT O: +34 619 728 249

 |  M: +34 619 728 249   |
franciscojavier.lo...@solera.com   
 |  Solera.com
  Audatex Datos, S.A.|  Avda. de

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

2018-10-15 Thread Lopez, Francisco Javier [Global IT] 
He he.

Sounds like that will do the trick then.

I could not do that way as this box does not have access to Internet.
Will see how to deal with this.

Guys I really appreciate your replies and help.

Cheers

Francisco Javier​   Lopez

IT System Engineer   |  Global IT

O: +34 619 728 249|  M: +34 619 728 
249|

franciscojavier.lo...@solera.com   
 |  Solera.com

Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida 16, A‑1 
(Diversia),   Alcobendas  ,   Madrid  ,   28108   , 
  Spain


[cid:image090871.png@C4C98636.2963693A]



On 15/10/18 16:42, Ken Gaillot wrote:

On Mon, 2018-10-15 at 14:37 +, Lopez, Francisco Javier [Global IT]
wrote:


Klaus/Ken.

Thx. for you reply.

The issue is ...

- I downloaded the source from GIT.
- Downloaded the OS required packages.
- Unzipped the source.
- ./autogen.sh + ./configure ---> OK
- Then, indeed, I tried: make rpm
  But I got thousands of errors:



Ah, I forgot it uses information from the repository. Rather than
download the source, you'd have to git clone the repository, and run
from there. By default you'll be in the latest master branch; if you
prefer to run a released version, you can check it out like "git
checkout Pacemaker-2.0.0".



$ make rpm
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
/bin/sh: -c: line 0: syntax error near unexpected token `Pacemaker-*'
/bin/sh: -c: line 0: `case  in Pacemaker-*) echo '' | cut -c11-;; *)
git log --pretty=format:%h -n 1 '';; esac'
...
...

What made me think, that downloading the source to the box I'm
testing could not be the
best, so I decided to ask the experts.

Best Regards

Francisco JavierLopez IT System Eng
ineer|  Global IT O: +34 619 728 249
 |  M: +34 619 728 249   |
franciscojavier.lo...@solera.com   
 |  Solera.com
  Audatex Datos, S.A.|  Avda. de Bruselas, 36, Salida
 16, A‑1 (Diversia) ,   Alcobendas  ,   Madr
id  ,   28108   ,   Spain On
15/10/18 16:27, Ken Gaillot wrote:


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 JavierLopez IT Syst
em E
ngineer  |  Global IT O: +34 619 728 249

 |  M: +34 619 728 249   |
franciscojavier.lo...@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

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

2018-10-15 Thread Ken Gaillot 
On Mon, 2018-10-15 at 14:37 +, Lopez, Francisco Javier [Global IT]
wrote:
> Klaus/Ken.
> 
> Thx. for you reply.
> 
> The issue is ...
> 
> - I downloaded the source from GIT.
> - Downloaded the OS required packages.
> - Unzipped the source.
> - ./autogen.sh + ./configure ---> OK
> - Then, indeed, I tried: make rpm 
>   But I got thousands of errors:

Ah, I forgot it uses information from the repository. Rather than
download the source, you'd have to git clone the repository, and run
from there. By default you'll be in the latest master branch; if you
prefer to run a released version, you can check it out like "git
checkout Pacemaker-2.0.0".

> $ make rpm
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> fatal: Not a git repository (or any of the parent directories): .git
> /bin/sh: -c: line 0: syntax error near unexpected token `Pacemaker-*'
> /bin/sh: -c: line 0: `case  in Pacemaker-*) echo '' | cut -c11-;; *)
> git log --pretty=format:%h -n 1 '';; esac'
> ...
> ...
> 
> What made me think, that downloading the source to the box I'm
> testing could not be the
> best, so I decided to ask the experts.
> 
> Best Regards
> 
> Francisco Javier      Lopez     IT System Eng
> ineer  |  Global IT     O: +34 619 728 249
>  |    M: +34 619 728 249   | 
> franciscojavier.lo...@solera.com   |  Solera.com  
>   Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida
>  16, A‑1 (Diversia)   ,   Alcobendas  ,   Madr
> id,   28108   ,   Spain     On
> 15/10/18 16:27, Ken Gaillot wrote:
> > 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 Syst
> > > > em E
> > > > ngineer  |  Global IT     O: +34 619 728 249
> > > > 
> > > >  |  M: +34 619 728 249   | 
> > > > franciscojavier.lo...@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

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

2018-10-15 Thread Lopez, Francisco Javier [Global IT] 
Klaus/Ken.

Thx. for you reply.

The issue is ...

- I downloaded the source from GIT.
- Downloaded the OS required packages.
- Unzipped the source.
- ./autogen.sh + ./configure ---> OK
- Then, indeed, I tried: make rpm
  But I got thousands of errors:

$ make rpm
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
/bin/sh: -c: line 0: syntax error near unexpected token `Pacemaker-*'
/bin/sh: -c: line 0: `case  in Pacemaker-*) echo '' | cut -c11-;; *) git log 
--pretty=format:%h -n 1 '';; esac'
...
...

What made me think, that downloading the source to the box I'm testing could 
not be the
best, so I decided to ask the experts.

Best Regards

Francisco Javier​   Lopez

IT System Engineer   |  Global IT

O: +34 619 728 249|  M: +34 619 728 
249|

franciscojavier.lo...@solera.com   
 |  Solera.com

Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida 16, A‑1 
(Diversia),   Alcobendas  ,   Madrid  ,   28108   , 
  Spain


[cid:image824429.png@9010732B.855BF16B]



On 15/10/18 16:27, Ken Gaillot wrote:

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 JavierLopez IT System E
ngineer  |  Global IT O: +34 619 728 249
 |  M: +34 619 728 249   |
franciscojavier.lo...@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@clusterlabs.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.clusterlabs.org%2Fmailman%2Flistinfo%2Fusersdata=01%7C01%7C%7C83b5c8abd9ff48080f2008d632aa4a43%7Cc45b48f313bb448b9356ba7b863c2189%7C1sdata=W%2FtkThOis%2FEkM5maP7dVWggwYg8cOR3%2FAJjAn1Jxaf0%3Dreserved=0

Project Home: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.clusterlabs.orgdata=01%7C01%7C%7C83b5c8abd9ff48080f2008d632aa4a43%7Cc45b48f313bb448b9356ba7b863c2189%7C1sdata=X6bGa81egPcfwyAZvo6Ce4cH2PfQXvvQlNo6KPWXxvg%3Dreserved=0
Getting started: