OpsCenter

Oracle Ops Center Example

Oracle Ops Center can be used to deploy, maintain and manage assets including Solaris operating environments, virtualized environments and harware systems.

Ops Center is comprised of: Enterprise Controller, proxy Controller and a Repository. All three components can exist on the same server.

Prepare to install

You can run Ops Center on Linux, but in this example I've used Solaris 10 SPARC 64bit, entire plus OEM, colocated EC and PC, with a remote repository. Server requirement:
- 4G RAM minimum, 6G if colocating EC and PC.
- "/" with 50G free minimum (to store lots of image files, allocate a LUN to the host, mount /var/opt/sun/xvm/locallib)
- a remote Oracle 11g database is required (650MB)
After installing Solaris, set LANG=C in /etc/default/init, set umask in /etc/profile and /etc/.login.

Installation

1) Install Oracle 11201 64bit client, added tnsnames.ora, test access.
2) Downloaded Oracle OpsCenter 12c packages, Oracle 11204 database software,
  enterprise-controller.Solaris.sparc.*.tar
  proxy-controller.Solaris.sparc.*.tar
3) Extract EC and PC to /var/tmp/OC/, follow online doco to install EC with Customer Managed Database (uses licensed DB). Note passwords. docs.oracle.com/cd/E24628_01/doc.121/e25140/install_config-shared.htm
4) Check services (start, stop, status), start it up,
  /opt/SUNWxvmoc/bin/ecadm status
  /opt/SUNWxvmoc/bin/satadm status
5) Check the GUI is available, http://<opscenter-host>, login as root or ocadmin, select co-located, await config completion.

Upgrading Ops Center

1) Download via web interface or manually, save to this location,
  $ ls /var/opt/sun/xvm/images/productUpdate/
2) Backup data,
  $ /opt/SUNWxvmoc/binecadm backup -o /path/file
3) Check for software or service issues prior upgrade,
  $ cd /var/opt/sun/xvm/OCDoctor ; ./OCDoctor.sh --upgrade ; ./OCDoctor.sh --troubleshoot
  Note - dont make the ssl.conf change, causes Apache to fail. You may need to disable cert checking in java config, if this is flagged in the log.
4) Using the GUI, select Navigation > administration > enterprise controller.
  Select Upgrade, then version. Wait for the login page to return (?mins).
  Check for errors in GUI when available, otherwise,
  $ tail -f /var/opt/sun/xvm/update-saved-state/updatelog_stdout.txt

Troubleshooting Ops Center

1) run "svcs -a" to check SMF services, restart EM, PC if required,
  /opt/SUNWxvmoc/bin/proxyadm stop -w -v
  /opt/SUNWxvmoc/bin/ecadm stop -w -v
  /opt/SUNWxvmoc/bin/ecadm start -w -v
  /opt/SUNWxvmoc/bin/proxyadm start -w -v

2) Check service logs, "svcs -x" and these logfiles,
  tail -f /var/cacao/instances/oem-ec/logs/cacao.0  
  tail -f /var/cacao/instances/scn-proxy/logs/cacao.0
3) Run ocdoctor,
  cd /var/opt/sun/xvm/OCDoctor ; ./OCDoctor.sh --troubleshoot

Configuring Ops Center

As root, ensure you have internet access (eg. export http_proxy in .profile). You can upload Solaris ISO files into the library, or download into the local library from Oracle.

Libraries > Software Libraries > Initial EC Library > Upload ISO

Add some login credentials in the Administration section, for access to service processors of server assets. Next, define some networks for Ops Center,

Network > Default (domain) > Fabrics > add fabric
Network > Default (domain) > define network (eg. SSH, 192.168.1.0/24, Corporate LOM)

Create profiles for your environment

Create a discovery profile, OS config profile, and OS provisioning profile

Plan management > Profile > Discovery > select profile, review the range, or edit.

Plan management > Profiles > OS configuration > Create. Configure auto management, MPxIO, deploy agent controller, static IP net_0.
Plan management > Profiles > OS Provisioning > Create. Configure OS, eg.
  image (eg. Sol10u11), terminal vt100, baud rate 9600, English (Au ISO8859.1),
  Timezone, port ttya, distribution (entire+oem), dynamic NFS4.
  Configure Jet params: "base_config_profile_zfs_disk, any any", and
  "base_config_profile_zfs_pool, rpool". Filesystems are swap (40G) and "/"
  (remainder). You can override settings at deployment.
Plan management > Profiles > Update profiles > create.

Create deployment plans

Plan management > Install server > create from template > configure a name and "stop on failure", choose the OS Provisioning profile, choose the OS Config profile. Select Install Software, choose a software profile, and then replicate the step to install more software profiles. Select the new step and
  "Associate targets", associating with our OS Configuration profile. Repeat for additional "software install" and "Post install" actions, eg. security.

Provision a Solaris SPARC Server

Add the network management IP to /etc/hosts on the Ops Center server.
OpsCenter > Add Asset > Add and manage various > select suitable discovery profile, specify hostname/IP, auto network discovery, review credentials and IP range > add now. Afterward, review status and firmware version, optionally add appropriate tags to the asset, eg.
Assets > R-click asset > Edit tags > Add, legacy.tags, virtualizationcontroller zone

Plan management > Deployment plans > Install Server > select the plan and Apply Deployment Plan > Choose the server asset domain, add to target list > Choose minimal interaction unless you want to override settings > Specify the IP for LAN access, and the hostname > choose defaults through the remainder of dialogs > Run now, apply.

Your server should be accessible on the LAN in a couple of hours.

You can create a separate patching job, and apply it,

Plan management > Profile and plicies > Update profiles > select job > select New OS Update job > select targets > run.

Maintain the deployment plan, include patch tasks so that new servers are deployed at the same patch revision as maintained server.

Final words

There is a lot more you can do with Ops Center, and a  lot of documentation, if the system is configured and maintained it will make your life as Solaris admin much easier.