Case Study: Provisioning MySQL Enterprise Server Using Sun xVM Ops Center v2.0


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Case Study: Provisioning MySQL Enterprise Server Using Sun xVM Ops Center v2.0
# 1  
Old 08-20-2009
Case Study: Provisioning MySQL Enterprise Server Using Sun xVM Ops Center v2.0

This case study shows how to use Sun xVM Ops Center v2.0 to provision a user application (MySQL Enterprise Server software) to the target servers in a data center.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

Ops Center Enterprise Controller Mount Point layout

Hi Guys. I am about to install the Enterprise Controller of Ops Center. I need to know on a 200gb Hard drive what the best possible Mount point layout? I know that /var is suposed to be around 100gb and swap size should be around 6gb ? What about /opt , /tmp and other mount point sizes? ... (5 Replies)
Discussion started by: Junaid Subhani
5 Replies

2. Solaris

Sun Ops Center

Hi, Can anyone share the link to download sun ops centre i have sun partner account, but i unable find the link Thanks RJS (3 Replies)
Discussion started by: rajasekg
3 Replies

3. Solaris

Sun xVM Ops Center 1.1

I have 180 Solaris 7, 8 and 9 servers to patch and am looking at using xVM Ops Center. Has anyone here had any experience with it? (1 Reply)
Discussion started by: mr_crosby
1 Replies
Login or Register to Ask a Question
dr(7d)								      Devices								    dr(7d)

NAME
dr, drmach, ngdr, ngdrmach - Sun Enterprise 10000 dynamic reconfiguration driver SYNOPSIS
dr drmach ngdr ngdrmach DESCRIPTION
The dynamic reconfiguration (DR) driver consists of a platform-independent driver and a platform-specific module. The DR driver uses stan- dard features of the Solaris operating environment whenever possible to control DR operations and calls the platform specific module as needed. The DR driver creates minor nodes in the file system that serve as attachment points for DR operations. The DR driver provides a pseudo-driver interface to sequence attach and detach operations on system boards using file system entry points referred to as "attachment points." The attachment point form depends on the platform. Sun Enterprise 10000 Server On the Sun Enterprise 10000 server, the DR driver consists of a platform-independent driver (ngdr) and a platform-specific module (ngdr- mach). The domain configuration server (DCS) accepts DR requests from the system services processor (SSP) and uses the libcfgadm(3LIB) interface to initiate the DR operation. After the operation is performed, the results are returned to the SSP. For more information about the DCS on the Sun Enterprise 10000, refer to the dcs(1M) man page and the Sun Enterprise 10000 Dynamic Reconfiguration User Guide. The DR driver creates physical attachment points for system board slots that takes the following form: /devices/pseudo/ngdr@0:SBx Where x represents the slot number (0 to 15) for a particular board. The cfgadm_sbd(1M) plugin creates dynamic attachment points that refer to components on system boards, including CPUs, memory, or I/O devices. Refer to the cfgadm_sbd(1M) man page for more details. SEE ALSO
cfgadm_sbd(1M), ioctl(2), libcfgadm(3LIB) Sun Enterprise 10000 Dynamic Reconfiguration User Guide SunOS 5.11 29 Sep 2003 dr(7d)