Comment 17 for bug 1645339
Revision history for this message
| Shannon Mitchell (shannon-mitchell) wrote | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
To add to that, most admins have not had a lot of experience with pacemaker or redhat clustering. This might cause reservation on initial POC deployments for people as it can get complicated quickly. Its also more difficult to maintain as I have seen it used in production on mysql master/slave configs in an openstack environment. Both admins and developers didn't know enough about it to properly manage it, which lead to many broken clusters that just ended up staying that way to keep from impacting SLA. You may have a few techs with experience, but by the time someone brings them in things are already broken.
It might be nice to have a simple haproxy setup(w/keepalived) along with any software specific clustering in place(galara, rabbit....) to lower the barrier to entry. This may be more preferable to a lot of customers as they still treat servers like pets and fencing off a compute node is undesirable.
It would also be nice to have the pacemaker options available in the documentation as well for those more experienced users that want the extra automation available in those solutions. Give them an option and pro's cons of each.