Skip to content

Latest commit

 

History

History
75 lines (67 loc) · 3.91 KB

poc.md

File metadata and controls

75 lines (67 loc) · 3.91 KB
Raw

POC Agenda

Updated 2017, March 15 by Matthew Ward

Summary

The Mid-Market Specialist SA team is skilled in but not equipped, staffing wise, to handle a steady stream of POCs. Free POC should be used tactically and as a tool for particularly complex deals. The purpose of the POC is to prove that our technology can do what's advertised in their own environment. In most cases the customer is better served with a customized demo showing the particular feature demonstrated by the customer.

Restrictions

  • This POC will not be conducted on a production environment.
  • Upon completion of the POC testing phase, the customer will remove the POC environment.
  • All POCs must be approved by the regional Mid-Market Sales Specialist and the Mid-Market Specialist Solution Architect.
  • Customer and Red Hat Specialist team must agree to POC Scope of Work and adhere to those guidelines. When the CloudForms Specialist SA leaves, there will be no on-going support for the POC environment.
  • POC must be performed using the customer 'Supported Evaluation Subscription'.

Requirements

This section must be completed by the customer or partner before the Red Hat Cloud Specialist resource comes on site. This is to help maximize the time for meeting POC expectations along with required troubleshooting.

  • Customer/Partner will download and import the Red Hat CloudForms virtual Appliance into the environment.
  • Customer/Partner will provide Red Hat configuration information for all systems.
    • Network information (IP, DNS, Subnet, and Gateway)
    • Additional Services (NTP and SMTP)
  • Customer/Partner will setup the required network, compute and storage configuration in preparation to the POC.
  • The customer will prepare all for all required access for the Partner and Red Hat Team doing the POC.

Basic POC

Purpose of this section is to outline what will be done in a POC. This POC is designed to be completed in one (1) day. For multiple day POC, Day 1 will be the Basic Setup and the remaining time will adding the Advanced Features

  • Basic Configuration
    • Configure Appliance
      • Configure Networking
      • Configure Database Appliance
      • Configure Compute Appliance
    • Connect Provider
      • Connect up to 2 Infrastructure providers (VMWare, Red Hat Virutalization or Red Hat OpenStack)
      • Validate the VMs from the Virtual Environment are discovered in CloudForms.
  • CloudForms Configuration
    • Settings
      • Set 'Basic' information
      • Set 'Server Roles'
      • Set Additional information
        • NTP and outgoing SMTP Server
    • Tenants and Projects
      • Implement pre-agreed on Tenants and Projects
      • Set Quota for Projects or Tenants
    • User, Groups and Roles
      • Implement pre-agreed on Users and Groups.
      • Assign groups to Pre-made Roles.
    • Tags and C & U
      • Implement pre-agreed on Tags
      • Turn on Collection and Utilization
  • Cloud Intel Configuration
    • Chargeback Reporting
      • Create one (1) Custom Chargeback report.
      • Help customer create an Assignment Policy for the Chargeback reports.
    • Reports
      • Create one (1) Custom Report.
      • Create a schedule for the Custom Report to run.
      • Queue report, if customer desires.
  • Compute
    • Tour the user interface.
    • Provision an Instance for a customer. (If Desired)
    • Set a 'Retirement' date on the provision system (If Desired)
    • Start a 'SmartState Analysis' on selected VMs.
  • Policy Management
    • Implement pre-agreed upon Compliance or Control Policy.
    • Test policy against agreed upon VM.
    • Apply policy against agreed upon VM.

Advanced POC Features

  • Service
    • Build Custom Service Catalog for deploying a Service.
    • Configure Service Catalog for AWS, OpenStack, RHEV, or VMWare.
    • Convert a pre-written Orchestration Template for Azure, AWS, or OpenStack into a Service Catalog.(Note I will not write an Orchestration Template)
  • Automation
    • Customize email information.