Guidelines

The as-a-Service environment is a mix of shared and dedicated workload specific infrastructure.

Shared infrastructure

The shared infrastructure available includes networking, SAN fabrics, virtualized compute, and storage arrays.

Dedicated infrastructure

There are specific dedicated infrastructure silos within the environment for specialized workloads. Also upon approval, dedicated environments can be setup and configured as needed on a project by project basis.

Stewardship

As this is a shared environment, please be wise stewards of the infrastructure and consume only the resources that are specifically needed for your project(s). Also once a project is complete and resources no longer needed, please clean up any physical infrastructure, VMs or storage no longer in use.

Naming conventions

All objects created within a shared environment must follow strict naming conventions. By adhering to naming conventions, it will speed up the time to troubleshoot any issues.

For example, if a vSphere datastore is named oracle-ds01 that doesn't indicate which array the volume resides on and then time is spent identifying which array (is it coming from the Nimble, Primera, Alletra, etc.) and then which volume on the array it maps to. This also applies when looking in reverse at the volumes on the array, with proper names volumes can easily be tracked to infrastructure, application(s), and owner(s). As more and more users use the shared infrastructure, standardized names will be critical in order to track and troubleshoot.

Basic information for a name regardless of the object type:

  • Virtual or physical environment (virt or phy)
  • Array name (system name of Nimble, Primera, Alletra, etc)
  • Owner (i.e. your name, project name, etc)
  • Volume, host, hostset ID unique identifier (i.e. vol01, vol02, vol#)

Examples:

  • Host name: ftc-tmaas-mc1.hpelab.local
  • Array volume name: virt-alletra-9060-oracle-zerto-vol1 (virtual)
  • Array volume name: phy-alletra-9060-ezmeral-vol1 (physical)
  • Hostset name: virt-alletra-9060-oracle-zerto-hostset
  • vSphere datastore name: virt-alletra-9060-oracle-zerto-vol1 (matches the array volume name)

Monitoring

All infrastructure within the as-a-Service environment is regularly monitored for utilization for capacity and compliance. Any activity within the environment that causes adverse affect upon other users will be investigated and appropriate action will be taken to ensure minimal impact on others.