View Only
  • 1.  VM traffic in case of overload

    Posted Mar 16, 2019 11:42 AM

    My topic and find a way to redirected the traffic in case of overload (use more than 80% of the use of RAM) of a machine Vm in (private cloud OVH - vmware) to another machine vm this time in (public cloud - openstack)

    The first step C to create an alarm in vmware Decliding a script or processing to a load balancer which, in turn Declanche an instance in openstack

    Is this a good track?

    If not, are there any other interesting tracks?

    Thanks for sharing ideas or documents that see useful.

  • 2.  RE: VM traffic in case of overload

    Posted Mar 20, 2019 09:18 PM

    I think you have to use "vmware integrated opnstack"

    who and it is true ?

    we are waiting for the experts

  • 3.  RE: VM traffic in case of overload

    Posted Mar 20, 2019 09:42 PM

    I would probably solve this in the following way:

    1. A load balancer must sit in front of the two or more real servers. The load balancer must have an API that can deactivate members from the pool.
    2. Use vRealize Operations to monitor the two VMs in question.
    3. Use the management pack for vRealize Orchestrator and connect vROps to vRO.
    4. Create a workflow that uses whatever method/plug-in is supported by the load balancer to deactivate a member. The input to this workflow would be the name of the VM that has reached 80% utilization memory.
    5. Create an alarm in vROps that uses this threshold as a threshold. Have it call said workflow.
    6. Now, when a VM in that group reaches the utilization threshold you want, vROps can call out to vRO and supply in its payload the name of the VM. The vRO workflow will in turn call out to your load balancer and deactivate that member in the pool.
    7. Caveat here is that you'd need automation logic that restores that member to the pool once the condition is no longer true. Also further logic that ensures at least one member in the pool is always available regardless of any triggering events.

    As you can see, there are quite a lot of steps with some degree of complexity, but it's entirely possible.

  • 4.  RE: VM traffic in case of overload

    Posted Mar 20, 2019 10:05 PM

    thank you for your reply

    your proposal is a complex one as you said

    -so the component vmwre intgrated openstack is not a solution to follow ???

    on the other hand in its documentation it offers the possibility to interact directly with opnstack

    so my idea was just to create an alarm to startup secend VM  that I cloned and deploy previously - manual in (openstack) with "component vmwre intgrated openstack"

    and then I'll see how to do load balancing between the two different cloud VMs

    what are you thinking about and thank you

  • 5.  RE: VM traffic in case of overload

    Posted Mar 20, 2019 10:17 PM

    VIO is just OpenStack. I'm not an OpenStack user so you will need to get other input regarding that.