[Pacemaker] Change Hostname

[Dan Frincu]

Hi,

On Thu, Sep 6, 2012 at 1:58 PM, Dan Frincu <df.cluster at gmail.com> wrote:
> Hi,
>
> On Thu, Sep 6, 2012 at 1:35 PM, Thorsten Rehm <thorsten.rehm at gmail.com> wrote:
>> Hi everyone,
>>
>> nobody has an idea?
>> Have I missed something in the documentation?
>
> Put the cluster in maintenance-mode.
> Stop Pacemaker, stop Corosync.
> Change the hostname.
> Check if the change actually worked.
> Start Corosync, start Pacemaker.
> Perform a reprobe and refresh from crm. Remove maintenance-mode.
> Delete old node names from cluster configuration (crm node delete
> $old-hostname).

My bad, you're running on Heartbeat.

>
> Dance.
>
> HTH,
> Dan
>
>>
>> Regards,
>> Thorsten
>>
>>
>> On Tue, Sep 4, 2012 at 10:55 AM, Thorsten Rehm <thorsten.rehm at gmail.com> wrote:
>>> Hi,
>>>
>>> ohh, thanks, but I have heartbeat in use.
>>> "Legacy cluster stack based on heartbeat"
>>> http://www.clusterlabs.org/wiki/File:Stack-lha.png
>>>
>>> So, there is no corosync.conf ;)
>>>
>>> Regards,
>>> Thorsten
>>>
>>> On Tue, Sep 4, 2012 at 10:38 AM, Vit Pelcak <vpelcak at suse.cz> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Dne 4.9.2012 10:28, Thorsten Rehm napsal(a):
>>>>> Hi everyone,
>>>>>
>>>>> I have a cluster with three nodes (stack: heartbeat) and I need to
>>>>> change the hostname of all systems (only the hostname, not the ip
>>>>> address or other network configuration). I have already made
>>>>> several attempts, but so far I have not managed that resources are
>>>>> available without interruption, after I changed the hostname. Is
>>>>> there a procedure that allows me to change the hostname, without
>>>>> loss of resources? If so, how would this look like? Is there a best
>>>>> case?
>>>>
>>>>
>>>> Hm. What about modifying corosync.conf to reflect hostname change on
>>>> all nodes, restarting corosync on all one after another (so you always
>>>> have at least 2 nodes running corosync and resources) and then
>>>> changing that hostname on desired machine and restarting corosync on it?
>>>>
>>>> In general, do not stop corosync on more than 1 node at the time and
>>>> you should be safe.
>>>>
>>>>> Cheers, Thorsten
>>>>>
>>>>> _______________________________________________ Pacemaker mailing
>>>>> list: Pacemaker at oss.clusterlabs.org
>>>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>>>
>>>>> Project Home: http://www.clusterlabs.org Getting started:
>>>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs:
>>>>> http://bugs.clusterlabs.org
>>>>
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>
>>>> iQEcBAEBAgAGBQJQRb4AAAoJEG+ytY6bjOob0AUH+gKl8OXHnGUUkXe4rFNc1qqr
>>>> W1hkafkjDOl2k475kiXiJ9CbgvP4mJSZJ+naMvyh53BJDuWiZH4i3kl1KZVSCvQ6
>>>> DNrZhHG90BmTLXiE6tCeVWP6K5tKamvLCRGBehiu83lW2kdH0X3uF9KqZlPnBFhy
>>>> AeEYvCsJKfM+u7WndNDFeQVdV//FQaHAB8JZBkgSyHmlvN+bnjUzRTOE1qLyv3/b
>>>> nPYVBOYCJgBjmENRRMoP1xWZgAAMeRCzRrpXo2ZSJ8945E/pmc1+9fPDJCqBXqvr
>>>> CFzI7iZcyidfpKq6h1S9dlDDMdRidj9P8kfEokThtHXpy45/LhdzYrMg6LmvuIc=
>>>> =tZ+G
>>>> -----END PGP SIGNATURE-----
>>>>
>>>> _______________________________________________
>>>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>>
>>>> Project Home: http://www.clusterlabs.org
>>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>>> Bugs: http://bugs.clusterlabs.org
>>>
>>>
>>>
>>> --
>>> Mit freundlichen Gruessen / Kind regards
>>> Thorsten Rehm
>>
>>
>>
>> --
>> Mit freundlichen Gruessen / Kind regards
>> Thorsten Rehm
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
>
>
> --
> Dan Frincu
> CCNA, RHCE



-- 
Dan Frincu
CCNA, RHCE