[Spacewalk-list] HA Solution to Spacewalk

[Rick van der Linde]

Thanks for your input (list).

 
I will figure out/investigate the posibilities of the Inter Satellite Sync stuff. It may be a solution te consider in my case as split management of SW clients may be considered as an alternative (thus reregistration of clients in DR scenario may be needed to manage them).

 
Rick
 
-----Oorspronkelijk bericht-----
Aan: spacewalk-list at redhat.com; 
CC: Rick van der Linde <rick at rilp.nl>; 
Van: Paul Robert Marino <prmarino1 at gmail.com>
Verzonden: wo 05-03-2014 20:54
Onderwerp: Re: [Spacewalk-list] HA Solution to Spacewalk
yes and no on the HA solution.
there is a way but its not really formalized.
on the database it depends on if you are using Oracle or PostgreSQL.
If you are using PostgreSQL 9.2 or higher I highly suggest using 3
database servers in cascading hot replication mode with pgpool acting
as a loadbalancer and managing the failover and recovery.


On the Spacewalk server side thats more complicated there are a couple
of options.
read these

1) syncing multiple satellite servers via inter-satellite-sync
   WARNING: This will not sync the hosts managed between them just
the channels, kickstart profiles erratas, etc..

   https://access.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/html/Getting_Started_Guide/sect-Getting_Started_Guide-Multiple_Satellites-ISS_Use_Cases.html

   https://access.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/html/Installation_Guide/sect-Installation_Guide-Example_Topologies-Multiple_Satellite_Horizontally_Tiered_Topology.html

  https://access.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/html/Installation_Guide/sect-Installation_Guide-Maintenance-Backing_Up_the_Satellite.html


2) True HA configuration

   https://access.redhat.com/site/documentation/en-US/Red_Hat_Network_Satellite/5.5/html/Installation_Guide/sect-Installation_Guide-Maintenance-Establishing_Redundant_Satellites_with_Stand_Alone_DB.html

   I use Gluster for the shared volumes :-)
   I also use keepalived as the loadbalancer and also to handle
taskomatic with some custom scripts since it can only run on one host
at a time.
   I also found it usefull to use a shared volume for
/var/www/html/pub/ as well.
   the one bad thing about this is Ive found that some things have
been left out of this doc for example it mentions noting about like
clustering jabber for osa-dispacher




On Wed, Mar 5, 2014 at 11:49 AM, Nelson Marques <nmo.marques at gmail.com> wrote:
> Hi,
>
> Load Balancing should be with 'sticky sessions' and Tomcats need to be
> clustered for session management (I'm not sure is the webapps play any role
> on that, though someone can point it). That in theory should work. I'm going
> for a similar architecture, though currently I'm struggling with updating to
> SW2.1 (schema update).
>
> NM
>
>
> 2014-03-05 14:44 GMT+00:00 Rick van der Linde <rick at rilp.nl>:
>>
>> Hi all,
>>
>>
>>
>>
>>
>> Since more and more intellectual capital is situated in my spaealk
>> solution I wonder if it's possible to make ik HA.
>>
>>
>>
>> Let me explain what I;m thinking of:
>>
>>
>>
>> Seperated DB that is (synchroneously) replicated. Tha (DB) service address
>> will switchover to the other server when something occurs. In my opinion
>> this is a "proven" concept. But the trick part is next:
>>
>>
>>
>> I want to build the spacewalk application onto multiple servers with
>> shared storage. In front of these I would like to "load-balance" the
>> connections. Most bequtifull would be that sessions get handled by multiple
>> servers, but according to me sessions are not stateless. Load balancing will
>> then be possible with connection affinity set. (That is once connected all
>> requests will be handled by the server connected till the session ends). Do
>> you know is this is possible?
>>
>>
>>
>> last is which filesystems should be shared across the load balanced
>> servers to keep them in sync?
>>
>>
>>
>> Filesystems I can mention are:
>>
>>
>>
>> /var/satellite
>>
>> /var/lib/cobbler
>>
>> /var/lib/tftpboot
>>
>>
>>
>> Clients should then access the LBR address.
>>
>>
>>
>> Thanks in advance,
>>
>>
>>
>>
>>
>> Rick
>>
>>
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140306/c64838d6/attachment.htm>