Oh, okay. I thought you meant some different ones.
--
Eric Robinson
Chief Information Officer
Physician Select Management, LLC
775.885.2211 x 112
-Original Message-
From: Kristoffer Grönlund [mailto:kgronl...@suse.com]
Sent: Friday, August 25, 2017 9:56 AM
To: Eric Robinson
Eric Robinson writes:
> Hi Kristoffer --
>
> If you would be willing to share your AWS ip control agent(s), I think those
> would be very helpful to us and the community at large. I'll be happy to
> share whatever we come up with in terms of an Azure agent when we're
Eric Robinson writes:
> I deployed a couple of cluster nodes in Azure and found out right away that
> floating a virtual IP address between nodes does not work because Azure does
> not honor IP changes made from within the VMs. IP changes must be made to
> virtual
Hello everyone,
The summit is coming closer, and I thought I should send out a brief
mail about how to find the event area once you are in Nuremberg.
Finding the office
==
The SUSE office is within walking distance from the conference hotel and
the old town center. The closest
Thanks. Leon sent me the same one earlier but I hadn't mentioned it yet (just
got it a short while ago). I'll be able to use it as a template to build one
for Azure. I have already installed the Azure CLI and it is working from my
Linux cluster nodes, so I'm maybe a third of the way there.
--
There's the awsvip agent that can handle secondary private IP
addresses this way (to be used with order/colocation constraints with
IPaddr2).
https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/awsvip
There's also the awseip for Elastic IPs that can assign your Elastic
IP to