10 More Discussions You Might Find Interesting
1. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
2. AIX
We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2
Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies
3. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
4. AIX
Hi,
Existing several p5 server with lpar (aix5.3), also implemented with hacmp.
And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server.
My question is, how to perform data migration from old server/SAN to new server/SAN.
Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies
5. Shell Programming and Scripting
Hi,
I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually.
After doing manual changes i have to find the wheather the change is dont or not and also clode review process.
Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies
6. UNIX for Advanced & Expert Users
Hi ,
There is going to be a server migration from Solaris 8.0 to Solaris10.0.
Could anyone give me some tips and documents regarding the steps to be remembered,tips to be followed etc.
like
syntax differences
any new changes to the existing commands and tools we use
whatever the... (1 Reply)
Discussion started by: mohanpadamata
1 Replies
7. AIX
Hello All,
We want to upgrade our 44p Model 270 from AIX 5.2 to 5.3. This is a standalone devlopment server but downtime is something we don't want because we have a short development deadline looming. I have no tape drive to make backups to. I myself am a developer and don't have any... (4 Replies)
Discussion started by: Fred Vogel
4 Replies
8. UNIX for Advanced & Expert Users
Hi all,
Would appreciate advise on my situation.
Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies
9. UNIX for Advanced & Expert Users
hi,
is there any tool that i can use to update my scripts (SH scripts)
form Unix to linux.
please mention any useful websites.
thanx in advance (2 Replies)
Discussion started by: omran
2 Replies
10. UNIX for Dummies Questions & Answers
Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies
OCF_HEARTBEAT_VIRTUA(7) OCF resource agents OCF_HEARTBEAT_VIRTUA(7)
NAME
ocf_heartbeat_VirtualDomain - Manages virtual domains through the libvirt virtualization framework
SYNOPSIS
VirtualDomain [start | stop | status | monitor | migrate_to | migrate_from | meta-data | validate-all]
DESCRIPTION
Resource agent for a virtual domain (a.k.a. domU, virtual machine, virtual environment etc., depending on context) managed by libvirtd.
This resource agent may be configured for native migration if available in the cluster manager. For Pacemaker, the allow-migrate="true"
meta attribute enables native migration.
SUPPORTED PARAMETERS
config
Absolute path to the libvirt configuration file, for this virtual domain.
(unique, required, string, no default)
hypervisor
Hypervisor URI to connect to. See the libvirt documentation for details on supported URI formats. The default is system dependent.
Determine the system's default uri by running 'virsh --quiet uri'.
(optional, string, no default)
force_stop
Always forcefully shut down ("destroy") the domain on stop. The default behavior is to resort to a forceful shutdown only after a
graceful shutdown attempt has failed. You should only set this to true if your virtual domain (or your virtualization backend) does not
support graceful shutdown.
(optional, boolean, default 0)
migration_transport
Transport used to connect to the remote hypervisor while migrating. Please refer to the libvirt documentation for details on transports
available. If this parameter is omitted, the resource will use libvirt's default transport to connect to the remote hypervisor.
(optional, string, no default)
migration_network_suffix
Use a dedicated migration network. The migration URI is composed by adding this parameters value to the end of the node name. If the
node name happens to be an FQDN (as opposed to an unqualified host name), insert the suffix immediately prior to the first period (.)
in the FQDN. At the moment Qemu/KVM and Xen migration via a dedicated network is supported.
Note: Be sure this composed host name is locally resolveable and the associated IP is reachable through the favored network.
(optional, string, no default)
monitor_scripts
To additionally monitor services within the virtual domain, add this parameter with a list of scripts to monitor.
Note: when monitor scripts are used, the start and migrate_from operations will complete only when all monitor scripts have completed
successfully. Be sure to set the timeout of these operations to accommodate this delay.
(optional, string, no default)
autoset_utilization_cpu
If set true, the agent will detect the number of domainU's vCPUs from virsh, and put it into the CPU utilization of the resource when
the monitor is executed.
(optional, boolean, default true)
autoset_utilization_hv_memory
If set true, the agent will detect the number of *Max memory* from virsh, and put it into the hv_memory utilization of the resource
when the monitor is executed.
(optional, boolean, default true)
migrateport
This port will be used in the qemu migrateuri. If unset, the port will be a random highport.
(optional, integer, no default)
snapshot
Path to the snapshot directory where the virtual machine image will be stored. When this parameter is set, the virtual machine's RAM
state will be saved to a file in the snapshot directory when stopped. If on start a state file is present for the domain, the domain
will be restored to the same state it was in right before it stopped last. This option is incompatible with the 'force_stop' option.
(optional, string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 90000.
stop
Stops the resource. Suggested minimum timeout: 90000.
status
Performs a status check. Suggested minimum timeout: 30. Suggested interval: 10.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
migrate_from
Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 60.
migrate_to
Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a VirtualDomain resource using the crm(8) shell:
primitive p_VirtualDomain ocf:heartbeat:VirtualDomain
params
config=string
meta allow-migrate="true"
op monitor depth="0" timeout="30" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/VirtualDomain_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_VIRTUA(7)