Cluster Server 7.3.1 Bundled Agents Reference Guide - Linux
- Introducing Bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- LVMLogicalVolume agent
- LVMVolumeGroup agent
- Sample configurations for LVMVolumeGroup agent
- Mount agent
- Sample configurations for Mount agent
- VMwareDisks agent
- SFCache agent
- AWS EBSVol agent
- AzureDisk agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- Notes for the NIC agent
- Sample configurations for NIC agent
- IPMultiNIC agent
- MultiNICA agent
- IP Conservation Mode (ICM) for MultiNICA agent
- Performance Mode (PM) for MultiNICA agent
- Sample configurations for MultiNICA agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- AWSIP agent
- AWSRoute53 agent
- AzureIP agent
- AzureDNSZone agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- KVMGuest agent
- Notes for KVMGuest agent
- Sample configurations for KVMGuest environment
- Sample configurations for RHEV environment
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- AzureAuth agent
- Infrastructure and support agents
- Testing agents
- Replication agents
- RVG agent
- RVGPrimary agent
- RVGSnapshot
- RVGShared agent
- RVGLogowner agent
- RVGSharedPri agent
- VFRJob agent
- Dependencies for VFRJob agent
- Notes for the VFRJob agent
Using the hadockersetup utility
Use the hadockersetup
utility to configure or unconfigure the container resource. The utility is provided along with the agents.
The default path of the utility is: /opt/VRTSvcs/bin/hadockersetup
Use the hadockersetup --help command to display the help for the utility.
The following is the output:
--configure|-C : Configure the Docker instance service group --genapp|-g : Configure the application resource along with Docker instance service group --unconfigure|-U : Unconfigure the Docker instance service group --help|-h : Print help message
The container should be created on the host.
To monitor the application inside the container, the utility establishes a communication channel between the container and the host. For this purpose, the utility needs VRTSperl, VRTSvcs, VRTSvlic, and VRTSvcsag packages of the same OS as of the container and also the same InfoScale Availability version as of host.
Disable the firewall.
The hadockersetup utility performs the following tasks when you use the --configure option:
Populates the list of containers created on the system. Select the container.
Adds Docker daemon resource to VCS configuration if not already present.
Sets communication channel between the host and the container by installing the packages listed in the Prerequisites section. When prompted, enter the path of the packages listed in the Prerequisites section.
Adds VCS user.
Adds container resource and sets dependency (online local firm) with the Docker daemon group.
Note:
Optional: You can also configure application resource through the utility. The utility will not prompt for confirmation of application resource configuration if you provide genapp as the option.
See Sample output of the hadockersetup utility.
Use the --unconfigure option to unconfigure the container resource along with application resource (if configured).
Note:
The VCS user created during configuration will not be removed. You must use the hauser - delete username command to remove the user.
You will be able to configure application resource only through MonitorProgram. You cannot provide PID or process name.
You will not be able to reconfigure the container. Unconfigure the resource and then configure the resource again using the utility.
The utility cannot monitor the same application inside Docker and host if the user is the same. The user must be different.
If wrong OS or wrong InfoScale Availability version packages are provided, the utility partially installs the packages. You must manually uninstall the partially-installed packages before configuring the container using the utility.
The application resource does not report the resource as faulted if the user does not exist.
Unconfiguring the container resource does not remove the VCS user created during configuration. You must use the following command to remove the user:
hauser - delete username
Establishing a communication channel between the host and container may fail if firewall is enabled.
The utility does not verify OS RPMs and RPM versions.
The utility does not check the correctness of StartProgram/StopProgram provided during application resource configuration.