1. Grid as a Service

2. Agenda Targets Overview and awareness of the obtained material which determines the needs for defining Grid as a service and suggest an immediate name change to avoid future confusion. Demonstrate the need to focus on the management of the OEM/Grid services as a first priority Obtain the support to continue the service development efforts with a visible understanding that there may exist a potential need for future allocation of resources(staff and funding) to mature the defined service offering(s). Obtain a common ground for communication among ourselves and a more clear understanding of a future direction for this service for our customers.

3. What are we trying to do?

4. An “over the wire” health check of an application service(s) that has the ability to record metrics of the application’s use and alert regarding the “health” of the hosted application’s hardware based upon standardized sets of configurations. What is a Grid Service Offering as viewed by the customer ?

5. New or existing service offering? Definition : “Grid as a service” Observation of current status: Confusion as to the use of the word “grid” in this context. Which collides with grid computing. OEM (Oracle Enterprise Manager) as a named service seems to be more appropriate and should be phased into the future vocabulary. The fact of existence of production customer instances not equal a service offering Prototyping grid/OEM features and extended abilities resulting in their implementation in production not equal an offering

6. Although we currently have “grid” services in production, we have no formalized process that documents, manages and would support our customer base in a cost effective manner as our customers increase their use of applications that need the OEM /grid features. Secondly, we need to begin to move away from the use of the term “grid” and introduce more of the OEM (Oracle Enterprise Manager) acronym to correctly represent the intended customer service offering(s). Fact findings lead to a couple initial conclusion(s)

7. A Service is a means of delivering value to customers by facilitating outcomes that customers want to achieve without the ownership of specific costs and risks. The CIT Service Catalog (that is, a list of CIT Services and relevant information about each) may be found at https://forge.cornell.edu/sf/docman/do/listDocuments/projects.cit_svc_catalog/docman.root.service_catalog_current. https://forge.cornell.edu/sf/docman/do/listDocuments/projects.cit_svc_catalog/docman.root.service_catalog_current What defines a CIT service ?

8. Define Service Owner(s), Manager(s), Support provider(s) Finalized the Technical Architecture Obtain Additional Funding as needed Develop Security plan Development/Testing, Training and Deployment methodologies Communication Strategies (internal and external) Creation of Customer Service Level Agreements Definition of service and support tiers and plans Define service delivery metrics/Expectations Become a recognized service and listed in the CIT service catalog Initial needs list for Grid/OEM as a Customer Service

9. Managing the OEM/Grid controls as a Service is the 1 st step Customer app 1 (agent) Customer app 2 (agent) Customer app3 (agent)

10. Managing the OEM/Grid controls as a Service is the 1 st step Customer app 1 (agent) Customer app 2 (agent) Customer app3 (agent)

11. Managing the customer agents Customer app 1 (agent) Customer app 2 (agent) Customer app3 (agent)

12. Initial discovery findings OEM/Grid needs additional work to become a hosted service offering. OEM/Grid agent implementations needed to be researched and decided upon Stand Alone Agent In a stand alone agent setup, the entire setup of the agent is limited to a given host and can only be administered from that host. Shared Agent With a shared agent setup, the binaries for a given OS platform (i.e., Linux, Solaris, HP) are shared on multiple hosts from a single shared NFS mount. This assists with upgrades and patch applications down the road.

13. VM host footprint

14. Overview of initial current status for the service

15. Current Agents in use

16. Hardware in use

17. OS level Summary

18. What are the initial tasks and needs?

19. Where is documentation repository for the initial tasks and needs for this development effort?

20. The initial starting point will be the New Confluence Landing Page

21. Agenda Targets Overview and awareness of the obtained material which determines the needs for defining Grid as a service and suggest an immediate name change to avoid future confusion. Demonstrate the need to focus on the management of the OEM/Grid services as a first priority Obtain the support to continue the service development efforts with a visible understanding that there may exist a potential need for future allocation of resources(staff and funding) to mature the defined service offering(s). Obtain a common ground for communication among ourselves and a more clear understanding of a future direction for this service for our customers.

22. Agenda Targets Overview and awareness of the obtained material which determines the needs for defining Grid as a service and suggest an immediate name change to avoid future confusion. Demonstrate the need to focus on the management of the OEM/Grid services as a first priority Obtain the support to continue the service development efforts with a visible understanding that there may exist a potential need for future allocation of resources(staff and funding) to mature the defined service offering(s). Obtain a common ground for communication among ourselves and a more clear understanding of a future direction for this service for our customers.

23. Tasks to be addressed soon.

24. Agenda Targets Overview and awareness of the obtained material which determines the needs for defining Grid as a service and suggest an immediate name change to avoid future confusion. Demonstrate the need to focus on the management of the OEM/Grid services as a first priority Obtain the support to continue the service development efforts with a visible understanding that there may exist a potential need for future allocation of resources(staff and funding) to mature the defined service offering(s). Obtain a common ground for communication among ourselves and a more clear understanding of a future direction for this service for our customers.

25. Conclusions Existing Staff resources will be needed to assist in forming OEM/Grid as a service. (eg. DBAs, support staff) Need to follow the standard steps for “Launching CIT Services” Immediate focus is needed on the management of the OEM/Grid to define and build the service offering(s) This effort has the potential to expand into a formal project that could require ITGC approval(s). Need decisions and refined definition of this service offering. (Refer to strawman support options on next slide)

26. StrawMan support models options that need definition/refining Customer owned ( self-supported ) Customer asks cit to create (cit supported) Cit consulting is requested by customer.

27. Questions yet to be answered We have activity 2227 currently tracking “grid as a service” staff efforts since October 7. – Where should we track customers that want to use grid as a service & bill the time? (eg. support, develop & configuration time, consult time) Is there a value add to know this info?

28. End of Presentation Do we understand where we are currently with OEM/Grid as a service? Is it clear where the direction of focus will be in the coming weeks/months?