Using the node's IPs would not work. The software being made HA must keep its IPs the same no matter what node its running on. Could script an IP change, but then we're putting IP logic and monitoring in two places: The cluster software and in our custom scripting. That's not a clean solution and is rather going backwards.
We may as well just do our own HA if we were starting down that road. When we sell our product the customer must also purchase Redhat Support for their OS and cluster software. I would think Redhat should pony up to get this done as the product we are selling is selling well and inducing Redhat Support sales.
An official feature request has been submitted to Redhat.
Also, I'm working on the /usr/share/cluster/ip.sh script myself to add the feature. Hopefully it works out.
On Thu, Jun 17, 2010 at 2:09 AM, Kit Gerrits <kitgerrits gmail com> wrote:In that case, might it be easier to simply use the host IP adresses and not the cluster IP's?(the application will need to handle up/down events itself)Regards,Kit
From: linux-cluster-bounces redhat com [mailto:linux-cluster-bounces redhat com] On Behalf Of Dustin Henry Offutt
Sent: dinsdag 15 juni 2010 14:40
To: linux clustering
Subject: Re: [Linux-cluster] Higher Grained Definition ofIP AddressAssignmentsI've spent the past year architecting an HA cluster with RHCS and it's working wonderfully. I have not seen anything superior.
Due to a new customer-driven feature of our software, we need to add the ability for a cluster service/resource group to have up to eight distinct IPs on one particular network due to the software being made highly available via RHCS performing its own load balancing. Placing the load balancing elsewhere is not an option due to the nature of the product.
Regarding "OCF_RESKEY_," will google more on this and appreciate the tip. Must work this out some way.
C. Handel wrote:[define interface of cluster controlled ip resource]/usr/share/cluster/ip.sh appears to perform the link-monitoring in theThis is a resource agent script. What attributes a resource agent accepts can be found by calling it with the option meta-data /usr/share/cluster/ip.sh meta-data There is no attribute interface. The agent will add the additional address to the first interface that is in the same subnet. You could edit the script and add a parameter interface yourself. Add a new parameter into the XML at the beginning and access it in the script with OCF_RESKEY_... I don't understand what you are trying to do. If you are only handling network interfaces as services, then rhcs is most likely the wrong tool. If you would explain your goal we could probably suggest other solutions. Greetings Christoph -- Linux-cluster mailing list Linux-cluster redhat com https://www.redhat.com/mailman/listinfo/linux-cluster
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.829 / Virus Database: 271.1.1/2939 - Release Date: 06/15/10 08:35:00
Linux-cluster mailing list
Linux-cluster redhat com