Hi Nixon, The allocation of secondary IP to the VM (which Jithin suggested) on the same network should instruct ACS not to use that IP elsewhere. Please see if that works.
Regards, Jayanth Reddy From: Nixon Varghese K S <[email protected]> Date: Tuesday, 2 July 2024 at 12:57 PM To: [email protected] <[email protected]> Subject: Re: Floating IP Assigning for Instance on Cloudstack Hi Jayanth, Thank you... Could you please elaborate on how we can let cloudstack know that the IP is being used? In my case, after setting up floating IP, CloudStack VR is not aware of that setup. When I spin up another virtual machine, it leases this IP to the new virtual machine, resulting in an IP conflict. With Regards, Nixon Varghese On Tue, Jul 2, 2024 at 12:24 PM Jayanth Babu A <[email protected]> wrote: > Hello Nixon, > We tried a similar scenario in the past with keepalived to float the IPs > across instances. As long as you’re saying to CloudStack that the IP is > allocated somewhere, this should be okay and you should be able to float > the IPs between or among instances on your own. > Is there anything else you would want to achieve like NAT for example? > > Regards, > Jayanth Reddy > > From: Nixon Varghese K S <[email protected]> > Date: Tuesday, 2 July 2024 at 12:08 PM > To: [email protected] <[email protected]> > Subject: Re: Floating IP Assigning for Instance on Cloudstack > Hi Jithin, > > Thank you for the update. > > Yes, I did try that, and the interface would get an additional IP address. > However, we are unable to add the same IP to another VM as a secondary. > For instance, in case of a DB cluster > VM 1 (DB1) with nic ens3 and IP 10.1.1.6 > VM 2 (DB2) with nic ens3 and IP 10.1.1.7 > For these two virtual machines, I need to set up a floating IP with > pacemaker, such as 10.1.1.8. As a result, my application can connect to > this floating IP, and the pacemaker will display the IP address on VM2 > (DB2) in the event that VM1 goes down. > Hope you got my senario > > With Regards, > Nixon Varghese > > On Tue, Jul 2, 2024 at 11:57 AM Jithin Raju <[email protected]> > wrote: > > > Hi Nixon, > > > > Could you try acquiring the required IP as a secondary IP address in one > > of the instances? I think that should work. > > > > -Jithin > > > > From: Nixon Varghese K S <[email protected]> > > Date: Tuesday, 2 July 2024 at 11:38 AM > > To: [email protected] <[email protected]> > > Subject: Floating IP Assigning for Instance on Cloudstack > > Hello, > > > > We have a requirement to run same service on a different instance and we > > need floating IP between them to connect. We were successful in setting > up > > communication and floating IP on the virtual machine. CloudStack VR is > not > > aware of the floating IP configuration since it was done at the VM OS > > level. As a result, we noticed that VR would use DHCP to assign the same > IP > > to another VM. Is it possible to add floating IP to an interface in a way > > that makes CloudStack VR aware of it? I received very little > documentation > > regarding the same. Would someone kindly share their thoughts with me? > > > > Thank you.... > > -- > > With Regards, > > Nixon Varghese > > > > > > > > > > -- > With Regards, > Nixon Varghese > Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL > INFORMATION intended solely for the use of the addressee(s). If you are not > the intended recipient, please notify the sender by e-mail and delete the > original message. Further, you are not authorised to copy, disclose, or > distribute this e-mail or its contents to any other person and any such > actions are unlawful and strictly prohibited. This e-mail may contain > viruses. NxtGen Datacenter & Cloud Technologies Private Ltd (“NxtGen”) has > taken every reasonable precaution to minimize this risk but is not liable > for any damage you may sustain as a result of any virus in this e-mail. You > should carry out your own virus checks before opening the e-mail or > attachment. NxtGen reserves the right to monitor and review the content of > all messages sent to or from this e-mail address. Messages sent to or from > this e-mail address may be stored on the NxtGen e-mail system. *** End of > Disclaimer ***NXTGEN*** > -- With Regards, Nixon Varghese Disclaimer *** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not authorised to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful and strictly prohibited. This e-mail may contain viruses. NxtGen Datacenter & Cloud Technologies Private Ltd (“NxtGen”) has taken every reasonable precaution to minimize this risk but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. NxtGen reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the NxtGen e-mail system. *** End of Disclaimer ***NXTGEN***
