Making an OVS Node Unavailable for vServer Placement in Exalogic Virtual Environments using EMOC
(Doc ID 1551724.1)
Last updated on OCTOBER 20, 2020
Applies to:Oracle Exalogic Elastic Cloud Software - Version 126.96.36.199.0 and later
Enterprise Manager Ops Center - Version 12.2 to 12.2 [Release 12.0]
Oracle Virtual Server(x86-64)
This document describes how to make an OVS node unavailable for vServer placement. It also describes how to make an OVS node unavailable to HA-enabled vServers by placing the OVS node in maintenance mode.
Steps listed in this MOS Note will put the Dom0 Compute node into Maintenance mode from EMOC only. So any stop/start or create vserver actions done from EMOC will not place the vserver on the compute node which is put in maintenance mode (using steps in this Note). Please note, that the steps in this MOS note will NOT put Dom0 Compute node in maintenance mode from OVS or OVM level.
So if there are events like HA VM crash or Dom0 node crash/reboot events, any VMs which are flagged as HA can still get started on Dom0 compute node which is put in maintenance mode from EMOC, because HA set at OVS level will kick in.
This is expected behavior and working as designed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Making an OVS Node Unavailable for vServer Placement|
|Making an OVS Node Unavailable to HA-enabled vServers|