Re: [ClusterLabs] Announcing ClusterLabs Summit 2020

2019-11-07 Thread Damien Ciabrini 
On Thu, Nov 7, 2019 at 12:57 PM Jehan-Guillaume de Rorthais 
wrote:

> On Thu, 7 Nov 2019 04:14:30 +0100
> Damien Ciabrini  wrote:
>
> > On Wed, Nov 6, 2019 at 8:03 AM Michele Baldessari 
> > wrote:
> >
> > > On Tue, Nov 05, 2019 at 08:35:55PM +0100, Valentin Vidić wrote:
> > > > On Mon, Nov 04, 2019 at 08:07:51PM -0600, Ken Gaillot wrote:
> > > > > A reminder: We are still interested in ideas for talks, and rough
> > > > > estimates of potential attendees. "Maybe" is perfectly fine at this
> > > > > stage. It will let us negotiate hotel rates and firm up the
> location
> > > > > details.
> > > >
> > > > Not sure if I would be able to attend but I would be interested to
> > > > know if there is some framework for release testing resource agents?
> > > > Something along the lines:
> > > >
> > > > - bring up 3 VMs
> > > > - configure a cluster using ansible for service X
> > > > - destroy node2
> > > > - wait some time
> > > > - check if the service is still available
> > >
> > >
> > Not sure how much time Damien has to polish it up and make it more
> > > suitable for general use, but we (Openstack team @RH) are using
> > > https://github.com/dciabrin/ra-tester quite a bit to validate any
> > > changes we make to resource agents. It's indeed worth discussing this
> in
> > > Brno.
> > >
> >
> > Right, we have this small tool that automates creation of VMs, and builds
> > on top of CTS to runs regression tests for the resource agents we consume
> > in OpenStack (galera, rabbitmq, redis).
>
> You built on top of CTS? Did you add custom scenario? Did you patched CTS
> in
> some way?
>

Yes some helper classes on top of CTS concept of Scenarios and Test, to
match
my needs (resilient to exceptions, different setup/teardown for the same
scenario)
And I've also added SSH support for connecting to the cluster's VM, rather
than using
qarsh.

It's currently in a rough shape [1], but you're interested in looking at
how it works
we can chat on IRC, I'm dciabrin on freenode

[1] https://github.com/dciabrin/ra-tester/tree/refactor-ra

-- 
Damien
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Announcing ClusterLabs Summit 2020

2019-11-06 Thread Damien Ciabrini 
On Wed, Nov 6, 2019 at 8:03 AM Michele Baldessari 
wrote:

> On Tue, Nov 05, 2019 at 08:35:55PM +0100, Valentin Vidić wrote:
> > On Mon, Nov 04, 2019 at 08:07:51PM -0600, Ken Gaillot wrote:
> > > A reminder: We are still interested in ideas for talks, and rough
> > > estimates of potential attendees. "Maybe" is perfectly fine at this
> > > stage. It will let us negotiate hotel rates and firm up the location
> > > details.
> >
> > Not sure if I would be able to attend but I would be interested to
> > know if there is some framework for release testing resource agents?
> > Something along the lines:
> >
> > - bring up 3 VMs
> > - configure a cluster using ansible for service X
> > - destroy node2
> > - wait some time
> > - check if the service is still available
>
>
Not sure how much time Damien has to polish it up and make it more
> suitable for general use, but we (Openstack team @RH) are using
> https://github.com/dciabrin/ra-tester quite a bit to validate any
> changes we make to resource agents. It's indeed worth discussing this in
> Brno.
>

Right, we have this small tool that automates creation of VMs, and builds
on top of CTS to runs regression tests for the resource agents we consume
in OpenStack (galera, rabbitmq, redis).
It's arguably rough, but it comes in handy whenever we want to validate a
resource agent change or reproduce a cluster behaviour.


> cheers,
> Michele
> --
> Michele Baldessari
> C2A5 9DA3 9961 4FFB E01B  D0BC DDD4 DCCB 7515 5C6D
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/



-- 
Damien
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Antw: Re: Announcing ClusterLabs Summit 2020

2019-11-06 Thread Damien Ciabrini 
Hey folks,


On Wed, Nov 6, 2019 at 4:41 PM Ken Gaillot  wrote:

> This topic sounds promising. Maybe we could do a round table where 3 or
> 4 people give 15-minute presentations about their technique?
>
Jehan-Guillaume, Damien, Ulrich, would you possibly be interested in
> participating? I realize it's early to make any firm commitments, but
> we could start considering the possibilities.
>
>
Absolutely, I'd be delighted to discuss how we validate our resource agent
changes with ra-tester.
I like the 15min approach, good to ignite discussion and not get people
bored :)


> On Wed, 2019-11-06 at 08:22 +0100, Ulrich Windl wrote:
> > > > > Valentin Vidic  schrieb am
> > > > > 05.11.2019 um
> >
> > 20:35
> > in Nachricht <20191105193555.gg27...@valentin-vidic.from.hr>:
> > > On Mon, Nov 04, 2019 at 08:07:51PM ‑0600, Ken Gaillot wrote:
> > > > A reminder: We are still interested in ideas for talks, and rough
> > > > estimates of potential attendees. "Maybe" is perfectly fine at
> > > > this
> > > > stage. It will let us negotiate hotel rates and firm up the
> > > > location
> > > > details.
> > >
> > > Not sure if I would be able to attend but I would be interested to
> > > know if there is some framework for release testing resource
> > > agents?
> > > Something along the lines:
> > >
> > > ‑ bring up 3 VMs
> > > ‑ configure a cluster using ansible for service X
> > > ‑ destroy node2
> > > ‑ wait some time
> > > ‑ check if the service is still available
> >
> > Nothing like that, but I wrote thios wrapper to do some pre-release
> > testing
> > for my RAs:
> > The first parameter is the RA name (required)
> > If followed by "debug" the script is run by "bash -x"
> > If followed by "manual" the following parameter is the action to test
> > If no parameters follow ocf-tester is used
> >
> > The actual parameters are written to files named "ocf/${BASE}-
> > test*.params"
> > ($BASE is the RA name, and it's expected that the testing RA (not
> > inmstalled
> > yet) lives in sub-directory ocf/). The parameter files by themselves
> > contain
> > lines like "name=value" like this example, and the tests are
> > performed in
> > "shell order":
> >
> > dest="www/80"
> > source="localhost/0"
> > tag="HA"
> > mask="I"
> > logging="F"
> > log_format="TL"
> > options="K:120"
> >
> > And finally the script (local commit 39030162, just for reference.
> > You'll have
> > to replace "xola" with the proper prefix to use RAs installed
> > already):
> > > cat tester
> >
> > #!/bin/sh
> > # wrapper script to test OCF RA
> > if [ $# -lt 1 ]; then
> > echo "$0: missing base" >&2
> > exit 1
> > fi
> > BASE="$1"; shift
> > for ra in "ocf/$BASE" "/usr/lib/ocf/resource.d/xola/$BASE"
> > do
> > if [ -e "$ra" ]; then
> > RA="$ra"
> > break
> > fi
> > done
> > INSTANCE="$BASE"
> > PARAM_FILES="ocf/${BASE}-test*.params"
> > if [ X"$RA" = X ]; then
> > echo "$0: RA $BASE not found" >&2
> > exit 1
> > fi
> > case "$1" in
> > debug)
> > DEBUG="bash -x"
> > MODE=$1
> > shift
> > ;;
> > manual)
> > MODE=$1
> > shift
> > ;;
> > *)
> > MODE=AUTO
> > esac
> > echo "$0: Using $INSTANCE ($RA) in $MODE mode"
> > for PARAM_FILE in $PARAM_FILES
> > do
> > echo "$0: Using parameter file $PARAM_FILE"
> > if [ $MODE != AUTO ]; then
> > for action
> > do
> > eval OCF_ROOT=/usr/lib/ocf
> > OCF_RESOURCE_INSTANCE="$INSTANCE" \
> > $(sed -ne 's/^\([^#=]\+=.\+\)$/OCF_RESKEY_\1/p'
> > "$PARAM_FILE")
> > \
> > $DEBUG $RA "$action"
> > echo "$0: Exit status of $action is $?"
> > done
> > else
> > if [ $# -eq 0 ]; then
> > eval /usr/sbin/ocf-tester -n "$INSTANCE" \
> > $(sed -ne 's/^\([^#=]\+=.\+\)$/-o \1/p'
> > "$PARAM_FILE") \
> > $RA
> > echo "$0: Exit status is $?"
> > else
> > echo "$0: Extra parameters: $@" >&2
> > fi
> > fi
> > echo "$0: Parameter file $PARAM_FILE done"
> > done
> > ###
> >
> > Regards,
> > Ulrich
> >
> > >
> > > ‑‑
> > > Valentin
> > > ___
> > > Manage your subscription:
> > > https://lists.clusterlabs.org/mailman/listinfo/users
> > >
> > > ClusterLabs home: https://www.clusterlabs.org/
> >
> >
> >
> > ___
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > ClusterLabs home: https://www.clusterlabs.org/
> --
> Ken Gaillot 
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/



-- 
Damien
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Galera 10.1 cluster

2017-01-06 Thread Damien Ciabrini 
Hey Oscar,

- Original Message -
> Hi,
> 
> Anybody has been able to set up a Galera cluster with the latest available
> version of Galera?
> 
> Can anybody paste the configuration?
> 
> I have tested it but I have not been able to make it run resiliently.
> 
Can you be more specific on why it wouldn't run "resiliently"? 
I just saw you've asked question on codership group re. bootstrapping the
cluster, is it related?

> Any help will be welcome!
> 
> Thanks a lot.
> 
> 
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://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
> 

___
Users mailing list: Users@clusterlabs.org
http://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

Re: [ClusterLabs] OCF Resource Agent for Galera

2015-12-01 Thread Damien Ciabrini 
Sorry for the spam :)

- Original Message -
> 
> 
> - Original Message -
> > On 29/11/15 21:32 +0530, Mayank Katyal wrote:
> > > I am facing error with the following OCF resource agent for Galera using
> > > it
> > > with Pacemaker and Heartbeat for setting up High Availability with
> > > MariaDB
> > > database server with multi Master on Debian Wheezy:
> > > 
> > > Galera Resource Agent
> > > 
> > > 
> > > The error I am getting in Heartbeat Logs is:
> > > 
> > > Waiting on node  to report database status before Master
> > > instances can start.
> > > 
> > > 
> > > Can anybody help? Thanks a lot.
> > 

Mayank, the message you're seeing is logged at the very beginning of the
bootstrap of the cluster.

The resource agent has to determine what is the last transaction on all
the galera nodes before it can elect a bootstrap node (the one with the
most recent version of the database).

This is a fairly normal message that is logged until all nodes have 
been probed by the resource agent.

If you keep seeing this message, that probably means one of the node
cannot be probed by the resource agent. If so, crm_mon -A -1 may tell 
you which one. 


> > Moving the question over to the users-centered cluster/HA list with
> > a broader audience.  It is a better fit for the question as the OCF
> > list, as I understand it, rather deals with OCF standard itself
> > (structure of agents' metadata, etc.) and is a low-to-no traffic
> > one[*].
> > 
> > [*] Not that there are no challenges for OCF ahead that could bring
> > better user experience at the configuration front-ends and what
> > not, but it doesn't seem to be worth the attention currently.
> > 
> > --
> > Jan (Poki)
> > 
> > ___
> > Users mailing list: Users@clusterlabs.org
> > http://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
> > 
> 

--
Damien

___
Users mailing list: Users@clusterlabs.org
http://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