<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Hi Jan,</div><div><br></div><div>Thanks for your replies!!</div><div><br></div><div>I have couple of concerns more to answer, please help!</div><div><br></div><div><br></div><div>1) In CMAN, there was meta attribute - autostart=0 (This parameter disables the start of all services when RGManager starts). Is there any way for such behavior in Pacemaker?</div><div><br></div><div>I tried to explore is-manged=0 but when I start the cluster through pcs cluster start OR pcs cluster start --all, my all of the resources gets started (even the one which has meta attribute configured as is-managed=false). Any clue to achieve such behavior?</div><div><br></div><div>What does is-manged=false do?</div><div><br></div><div>2) Please put some alternatives to exclusive=0 and __independent_subtree? what we have in Pacemaker instead of these?</div><div><br></div><div>My cluster depends on these meta attributes and I am getting nothing in pacemaker as an alternative to these one. Please see, if it is feasible to achieve such meta attributes in Pacemaker.</div><div><br></div><div><br></div><div>Thanks</div><div>Jaspal</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 24/01/16 16:54 +0530, jaspal singla wrote:<br>
> Thanks Digimer for letting me about the tool. I was unaware of any such<br>
> tools!! And because of that I was able to search clufter-cli tool for the<br>
> migration.<br>
><br>
> Thanks a lot John for explaining each and everything in detailed manner. I<br>
> am really admired the knowledge you guys have!!<br>
><br>
> I also noticed that clufter tool is written by you :). I am very thankful<br>
> to you as it would save the ass of millions people like me who may have had<br>
> difficulties in migration of their legacy programs from CMAN to Pacemaker.<br>
<br>
Glad to hear this, indeed :)<br>
<br>
> As suggested I tried to migrate my existing cluster.conf file from CMAN to<br>
> Pacemaker through the use of clufter. But have couple of queries going<br>
> forward, would appreciate if you could answer these.<br>
><br>
> Please find In-line queries:<br>
<br>
Answers ditto...<br>
<br>
>> Date: Fri, 22 Jan 2016 21:52:17 +0100<br>
>> From: Jan Pokorn? <<a href="mailto:jpokorny@redhat.com">jpokorny@redhat.com</a>><br>
>> Subject: Re: [ClusterLabs] Cluster resources migration from CMAN to<br>
>> Pacemaker<br>
>> Message-ID: <<a href="mailto:20160122205217.GE28856@redhat.com">20160122205217.GE28856@redhat.com</a>><br>
>><br>
>> yes, as Digimer mentioned, clufter is the tool you may want to look<br>
>> at. Do not expect fully automatic miracles from it, though.<br>
>> It's meant to show the conversion path, but one has to be walk it<br>
>> very carefully and make adjustments every here and there.<br>
>> In part because there is not a large overlap between resource agents<br>
>> of both kinds.<br>
>><br>
>> On 22/01/16 17:32 +0530, jaspal singla wrote:<br>
>>> I desperately need some help in order to migrate my cluster configuration<br>
>>> from CMAN (RHEL-6.5) to PACEMAKER (RHEL-7.1).<br>
>>><br>
>>> I have tried to explore a lot but couldn't find similarities configuring<br>
>>> same resources (created in CMAN's cluster.conf file) to Pacemaker.<br>
>>><br>
>>> I'd like to share cluster.conf of RHEL-6.5 and want to achieve the same<br>
>>> thing through Pacemaker. Any help would be greatly appreciable!!<br>
>>><br>
>>> *Cluster.conf file*<br>
>>><br>
>>> ######################################################################<br>
>>><br>
>><br>
>> [reformatted configuration file below for better readability and added<br>
>> some comment in-line]<br>
>><br>
>>> <?xml version="1.1"?><br>
>> ^^^<br>
>> no, this is not the way to increase config version<br>
>><br>
>> This seems to be quite frequented mistake; looks like configuration<br>
>> tools should have strictly refrained from using this XML declaration<br>
>> in the first place.<br>
>><br>
>>> <cluster config_version="1" name="HA1-105_CLUSTER"><br>
>>> <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/><br>
>>> <clusternodes><br>
>>> <clusternode name="<a href="http://ha1-105.test.com" rel="noreferrer" target="_blank">ha1-105.test.com</a>" nodeid="1" votes="1"><br>
>>> <fence/><br>
>>> </clusternode><br>
>><br>
>> (I suppose that other nodes were omitted)<br>
>><br>
><br>
> No, its Single-Node Cluster Geographical Redundancy Configuration.<br>
><br>
> The geographical redundancy configuration allows us to locate two Prime<br>
> Optical instances at geographically remote sites. One server instance is<br>
> active; the other server instance is standby. The HA agent switches to the<br>
> standby Element Management System (EMS) instance if an unrecoverable<br>
> failure occurs on the active EMS instance. In a single-node cluster<br>
> geographical redundancy configuration, there are two clusters with<br>
> different names (one on each node), each containing a server.<br>
<br>
Ah, it's more me not being familiar with rather exotic uses cases and<br>
I definitely include degenerate single-node-on-purpose case here.<br>
<br>
>>> </clusternodes><br>
>>> <cman/><br>
>>> <fencedevices/><br>
>>> <rm log_facility="local4" log_level="7"><br>
>>> <failoverdomains><br>
>>> <failoverdomain name="Ha1-105_Domain" nofailback="0" ordered="0" restricted="0"/><br>
>><br>
>> TODO: have to check what does it mean when FOD is not saturated<br>
>> with any cluster node references<br>
><br>
> No worries of using FOD as I don't think, it will be in use as we have<br>
> groups in pacemaker.<br>
<br>
FYI, I checked the code and it seams utterly useless to define an<br>
empty failover domain and to refer to it from the resource group.<br>
Based on its properties, just the logged warnings may vary.<br>
Furthermore, enabling restricted property may prevent associated<br>
groups to start at all.<br>
<br>
Added a warning and corrected the conversion accordingly:<br>
<a href="https://pagure.io/clufter/92dbe66b4eebb2b935c49bd4295b96c7954451c2" rel="noreferrer" target="_blank">https://pagure.io/clufter/92dbe66b4eebb2b935c49bd4295b96c7954451c2</a><br>
<br>
>>> </failoverdomains><br>
>>> <resources><br>
>>> <script file="/data/Product/HA/bin/ODG_IFAgent.py" name="REPL_IF"/><br>
>><br>
>> General LSB-compliance-assumed commands are currently using a path hack<br>
>> with lsb:XYZ resource specification. In this very case, it means<br>
>> the result after the conversion refers to<br>
>> "lsb:../../..//data/Product/HA/bin/FsCheckAgent.py".<br>
>><br>
>> Agreed, there should be a better way to support arbitrary locations<br>
>> beside /etc/init.d/XYZ.<br>
>><br>
><br>
> Configured resources as LSB as you suggested.<br>
>><br>
>>> <script file="/data/Product/HA/bin/ODG_ReplicatorAgent.py" name="ORACLE_REPLICATOR"/><br>
>>> <script file="/data/Product/HA/bin/OracleAgent.py" name="CTM_SID"/><br>
>>> <script file="/data/Product/HA/bin/NtwIFAgent.py" name="NTW_IF"/><br>
>>> <script file="/data/Product/HA/bin/FsCheckAgent.py" name="FSCheck"/><br>
>>> <script file="/data/Product/HA/bin/ApacheAgent.py" name="CTM_APACHE"/><br>
>>> <script file="/data/Product/HA/bin/CtmAgent.py" name="CTM_SRV"/><br>
>>> <script file="/data/Product/HA/bin/RsyncAgent.py" name="CTM_RSYNC"/><br>
>>> <script file="/data/Product/HA/bin/HeartBeat.py" name="CTM_HEARTBEAT"/><br>
>>> <script file="/data/Product/HA/bin/FlashBackMonitor.py" name="FLASHBACK"/><br>
>>> </resources><br>
>>> <service autostart="0" domain="Ha1-105_Domain" exclusive="0" name="ctm_service" recovery="disable"><br>
>><br>
>> autostart="0" discovered a bug in processing towards "pcs commands"<br>
>> output:<br>
>> <a href="https://pagure.io/clufter/57ebc50caf2deddbc6c12042753ce0573a4a260c" rel="noreferrer" target="_blank">https://pagure.io/clufter/57ebc50caf2deddbc6c12042753ce0573a4a260c</a><br>
><br>
><br>
> I don't want to start my some of the configured services when Pacemaker<br>
> starts ( like it had happen in RGManager), I want to manually starts the<br>
> services. Is their any way I can do that?<br>
><br>
> Also, I am trying to start the cluster but "Resource Group:<br>
> SERVICE-ctm_service-GROUP" is going into unmanaged state and cannot be<br>
> started. Could you please give me some clue of it like why its going in<br>
> unamanged state and how it can be rectified?<br>
<br>
Just a quick suggestion for now if it helps:<br>
<br>
pcs resource manage SERVICE-ctm_service-GROUP<br>
<br>
or alternatively:<br>
<br>
pcs resource meta SERVICE-ctm_service-GROUP is-managed=true<br>
<br>
<br>
Will get back to you with answer for __independent_subtree later.<br>
<br>
--<br>
Jan (Poki)<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: application/pgp-signature<br>
Size: 819 bytes<br>
Desc: not available<br>
URL: <<a href="http://clusterlabs.org/pipermail/users/attachments/20160125/5299880a/attachment-0001.sig" rel="noreferrer" target="_blank">http://clusterlabs.org/pipermail/users/attachments/20160125/5299880a/attachment-0001.sig</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 25 Jan 2016 16:49:11 -0500<br>
From: Digimer <<a href="mailto:lists@alteeve.ca">lists@alteeve.ca</a>><br>
To: Cluster Labs - Users <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br>
Subject: [ClusterLabs] Moving Anvil! and Striker development to this<br>
list<br>
Message-ID: <<a href="mailto:56A69857.10308@alteeve.ca">56A69857.10308@alteeve.ca</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Hi all,<br>
<br>
The Anvil! and Striker (and now ScanCore) projects used to have their<br>
own low-volume mailing list. Recently it started getting some use and,<br>
being the one who advocated the strongest for the merger of lists, I<br>
decided to close it down and migrate over to here.<br>
<br>
To give a brief overview of what Anvil!, Striker and ScanCore is;<br>
<br>
The "Anvil!" is the name of our 2-node HA cluster based on this[1]<br>
tutorial. It's also the term we generally use for the full HA stack<br>
we've built.<br>
<br>
Striker[2] is a web-based front-end for Managing Anvil! clusters and<br>
the servers that run on them. It has been in very heavy development the<br>
last year and change and we're getting close to the version 2 release<br>
"real soon now(tm)".<br>
<br>
ScanCore[3] is a new component that runs on both Anvil! nodes and<br>
Striker dashboards. It was initially announced at the HA Summit in Brno<br>
in 2015 is it's release will coincide with Striker v2's release. It is<br>
an alert, predictive failure and mitigation program that is technically<br>
stand-alone but has been built into the heart of the Anvil! platform. It<br>
is inherently redundant does things like watch for faults, try to<br>
recover from known problems autonomously and alert users to these issues.<br>
<br>
I've been somewhat reluctant to move our list over because Alteeve,<br>
our company and the company that builds and maintains the Anvil!,<br>
Striker and ScanCore is for-profit. However, _everything_ we do is open<br>
source, so I hope that won't be held against us. :)<br>
<br>
If anyone has any comments or concerns about us moving our project<br>
discussion to this list, please let me know and I'll do what I can to<br>
make sure we address those concerns.<br>
<br>
Cheers!<br>
<br>
digimer<br>
<br>
1. <a href="https://alteeve.ca/w/AN!Cluster_Tutorial_2" rel="noreferrer" target="_blank">https://alteeve.ca/w/AN!Cluster_Tutorial_2</a><br>
2. <a href="https://github.com/digimer/striker" rel="noreferrer" target="_blank">https://github.com/digimer/striker</a><br>
3. <a href="https://github.com/digimer/striker/tree/master/ScanCore" rel="noreferrer" target="_blank">https://github.com/digimer/striker/tree/master/ScanCore</a><br>
<br>
--<br>
Digimer<br>
Papers and Projects: <a href="https://alteeve.ca/w/" rel="noreferrer" target="_blank">https://alteeve.ca/w/</a><br>
What if the cure for cancer is trapped in the mind of a person without<br>
access to education?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 12, Issue 42<br>
*************************************<br>
</blockquote></div><br></div></div>