OVSvApp monitoring changes to support fault tolerance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-vsphere |
Fix Committed
|
Undecided
|
Romil Gupta |
Bug Description
With the introduction of OVSvApp solution, which consists of
a service VM hosted on ESX hosts within a data center.
To address the Fault Tolerance and High Availablity of OVSvApp.
OVSvApp solution caters to the following failure scenarios:
OVSvApp agent crash:
- upstart mechanism tries to bring up the agent back.
Open vSwitch process crash:
- Child process of OVSvApp agent will monitor the OpenvSwitch
and tries to restart it when crashed.
- This will help us to re-populate the flows at the earliest
to resume the tenant VM data network connectivity.
OVSvApp VM crash:
- Agent monitoring mechanism will put ESX host in maintenance mode
or powers off as per "esx_maintenanc
By default, 'esx_maintenanc
maintenance mode.
- vCenter DRS will migrate tenant VMs to other ESX hosts within the
cluster and safeguards traffic from being blackholed.
- Agent monitoring can be turned on/off using the configuration
"enable_
By default, it is enabled.
Changed in networking-vsphere: | |
assignee: | nobody → Romil Gupta (romilg) |
Changed in networking-vsphere: | |
status: | New → In Progress |
description: | updated |
summary: |
- OVSvApp Agent monitoring changes to support fault tolerance + OVSvApp monitoring changes to support fault tolerance |
Reviewed: https:/ /review. openstack. org/213124 /git.openstack. org/cgit/ openstack/ networking- vsphere/ commit/ ?id=f3072cdaf71 b2ca52a3825d9f5 8aca1f2df9aa4a
Committed: https:/
Submitter: Jenkins
Branch: master
commit f3072cdaf71b2ca 52a3825d9f58aca 1f2df9aa4a
Author: Romil Gupta <email address hidden>
Date: Fri Aug 14 05:33:58 2015 -0700
Fix ovsvapp_monitor.py
Updated the ovsvapp_monitor.py to read a correct
configuration from an agent.
Partial-bug: #1485433
Change-Id: I2d5a1f619cf89d 6dc660ff52768e4 aaa3108c1c2