cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <rwhee...@artifact-software.com>
Subject Re: How to move/replace management server?
Date Mon, 26 Mar 2018 17:16:07 GMT
Would this be a nice short note for the Wiki?

Ron

On 26/03/2018 11:18 AM, Martin Emrich wrote:
> Hi!
>
> Took some time to get some hardware to test, but it basically worked 
> so far (Migrating DB to new host, and setting up an additional MS on 
> the new host):
>
> * Stop old MS
>
> * cloudstack-configure-databases on the new host
>
> * dump databases "cloud" and "cloud_usage" on old host
>
> * stop database on old host
>
> * import databases on new host
>
> * edit db.properties on old host (db.*.host, db.*.slaves)
>
> * start MS on old host, works fine with the DB on the other host
>
> * configure-cloudstack-management on the new host
>
> * new MS works, too.
>
> Awesome :)
>
> Cheers,
>
> Martin
>
>
> Am 02.03.18 um 18:37 schrieb Paul Angus:
>> You can force the issue by stopping the all mgmt. servers, setting 
>> the management_server_id of the hosts in the host table to NULL when 
>> setting the old host to removed then restarting the new mgmt. server.
>>
>> It's generally best practice to keep your mysql and mgmt. servers on 
>> separate hosts to make life easier when moving stuff around (like now).
>>
>> paul.angus@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>>
>>
>> -----Original Message-----
>> From: Martin Emrich <martin.emrich@empolis.com>
>> Sent: 02 March 2018 14:15
>> To: users@cloudstack.apache.org
>> Subject: Re: How to move/replace management server?
>>
>> Hi!
>>
>>
>> Am 02.03.18 um 10:49 schrieb Paul Angus:
>>> Hi Martin,
>>>
>>> At a high level, what I would recommend doing, is building a new 
>>> management host on CentOS7, add it as an additional management 
>>> server.  Update the 'host' entry in the global settings to point to 
>>> the new host.  And then mark the original management server as 
>>> removed (by setting a date in the removed field in the database).
>> Thanks, so I basically upgrade from a single-node-setup to a cluster, 
>> wait a day or so for all components to "learn" that there is a new 
>> guy in town, and then remove the old node? Sounds reasonable...
>>> This assumes your database is on a separate VM/host.
>> The DB is running on the same host, but migrating it should be easy 
>> beforehand.
>>
>> Thanks
>>
>> Martin
>>
>
>

-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


Mime
View raw message