Citrix Synergy 2014 - Syn230 Building successful clouds based on citrix consulting methodology

Editor's Notes

• #2: http://www.citrix.com/tv/#videos/8605
• #5: Here is a quick look at a few of the customers who are running Citrix cloud offerings today in their environment, BT and TaTa on the public cloud front, Spotify and Edmunds.com are some of our web 2.0s and we’ve seen a lot of growth in the enterprise and education market over the last year with the likes of Nokia and Autodesk.
• #6: A key element in the success of Citrix Consulting is the proven methodology which takes each project through the critical steps from inception through operations. Our approach focuses on ensuring that projects are properly planned and designed before implementation begins, so that the end project minimizes your risk and delivers maximum business impact.Define: Citrix Consulting can assist in the definition of the strategy that will help your business take full advantage of virtualization and cloud technologies through:Solution developmentRoadmap initiatives and strategic planningHardware and storage estimationPrioritization.Asses: Think of the center of our diagram as the heart of your project. During the Assess phase, Citrix Consulting reviews your current environment, identifies use cases, and gathers detailed requirements for your project. This information allows us to elaborate on the project success criteria and set goals for your Citrix deployment, upgrade, or expansion.Design: The design phase defines the architecture and operational processes required to implement and maintain the production environment that will meet and hopefully exceed your success criteria. Topics such as environment scalability, redundancy and high availability are addressed. Citrix Consulting will apply best practices for performance tuning to help your environment perform at its best. That means that your environment is rigorously tested during this phase to make sure your deployment runs smoothly.Monitor: Citrix Consulting can be engaged to perform continued monitoring and administrative tasks in several different capacities for the long-term health of your Citrix environment. We have the experience to keep your environment stable and your users happy with onsite and remote delivery capabilities.
• #7: Here we have the architecture lifecycle process that many of you probably follow for new services delivery.>>We start with Architecture Requirements aka Utilitas, the clients need for structure. These requirements can be for a new service, service upgrade, process related, or infrastructure related. Key considerations for the architecture would be the Cloud Offerings and all the standard architecture methodology to include >>Capacity>>Availability>>Scalability >>Performance/Efficiency>>Security >>We apply the architecture methodology to create the >>Design aka Venustas, the design arranged to meet functional needs>>Then we apply our implementation Standards aka Firmitas, materials and logistics of construction to >>deliver the structure>>After deployment we conduct sustaining operations for an enduring structure>>At each part of the lifecycle we apply well defined >>business, >>technology, and >>operations criteria for a successful cloud implementation
• #8: X-axis identifies the type of workloadY-axis is placement of InfrastructureWorkload TypesCloud-era is fail fast applicationsTraditional is N-Tier Bootstrapped can be DaaS, SaaS Custom can be bare-metalMultiple Hybrid DesignsTypical Cloud Services illustratedStakeyour organizations’ cloud positioning. The cloud Positioning will create emphasis on different success criteria. Its IMPORTANT to establish a proper perspective/point-of-view to this graph. >>Enterprise customers need to view this graph as if they were delivering cloud services as a Service provider to the internal organizationService Providers need to view this graph as if they were delivering commercial cloud services to external organizationsBe careful not to confuse multiple points-of-view for the same responses as the interpretation will be misleading.>>Workloads to the left of Y-axis may be traditional N-Tier applications migrated to cloud OR redeveloped applications to take advantage of elasticity/elastic scale/fail-fast >>Workloads to the right of Y-axis may be elastic scaled single purpose application (e-commerce site) or enterprise SaaS type applicationEnterprises will be below the X-axis for Internally hosted Private Clouds. Custom may be a PaaS in bare metal cases
• #9: The three tracks Business, Operations, and Technology overlay and interact with each other during the life of the project. The oculus of the project moves from one layer to the next as the project matures over timeSuccessful cloud projects have well defined criteria in their respective layers>>Business Layer criteria applies to the provider organization (Enterprise or Service Provider) and covers subscriber interaction with the cloud offering. >>Technology Layer criteria cover all aspects of the Infrastructure/Software/services required to build and enable the cloud platform>>Operational Layer criteria cover all aspects of the ongoing health,autonomic management and operations interactions with the cloud technology and business processLightning bolts represent ideas or objectives Connectors represent guidance from one layer to anotherTriangles represent requirements handoff from one layer to anotherFor the purposes of this talk we will focus on the Enterprise
• #10: Industrial policyThe Business Layer focus is on objectives and goals specifically around subscriber interaction with the cloud offering.>>These are sample considerations for the business layerThere can be multiple Service(s) catalog since the enterprise will want to merchandise multiple cloud services includingInfrastructure as a ServiceDesktops as a ServiceStorage as a ServiceNetwork as a ServicePlatform as a ServiceOperations as a Service…..IT or completely Self-serviceUse CasesCloud user experienceCloud ServicesIaaS / DaaS / PaaS / STaaS / *aaSROI / MonetizationChargeback / Showback / Credit/Debit CardAccount and User lifecycleSelf/Assisted SignupResource Sharing ModelCloud Management Access – *IaaSCloud Workload/Apps Access – *DaaSProduct ManagementService(s) OfferingsService(s) CatalogIntegrationsHelp DeskAuthenticationBilling SystemsCustom WorkflowsReporting
• #11: These are the best practices we see in citrix cloud services consulting. Three to Five Customer Value goals -> use casesInvolve customers early in Beta preview program -> validate cloud offeringConsider back office integrations early (AD Integration, Invoicing, …)Phased approach to Implementation (Features, Infrastructure, Operations)Do not create dependencies to first launch based on product futures/roadmapHave a plan for running on your own -> avoid lengthy services engagementBusiness requirements are clearly articulated to Technology team
• #12: The Technology layer presents the most skill for IT and can present the most challenges for transformation thinkingInfrastructure will be virtualized or bare metal (specialized workloads) so thinking in the cloud way is the first step to breaking the barrier>>Technology Layer criteria cover all aspects of the Infrastructure/Software/services required to build and enable the cloud platformIsolation Model refers to Basic/Advanced/Advanced Shared/Advances Shared with Security Groups zone typeCloud Services Automation refers Application specific Automation (Example, Chef/puppet/etc)Technology Integrations to other Infrastructure management devices required in the physical datacenterOther grouping commonly used in the fieldVirtual Datacenter AbstractionTenant Isolation ModelInfrastructure Deployment DesignCloud Services AutomationSelf-Service CapabilitiesTechnology IntegrationsService Level Agreement (SLA)Security ConsiderationsPerimeter API Whitelist/Blacklist
• #13: Agnostic Infrastructure design to support workload typesNeed for migration (tools) from legacy environments to cloud platform Be realistic in Infrastructure requirements (Pentium, 100MB NIC, 2GB hosts wont work in Traditional IaaS cloud) Simple Infrastructure Architecture is better than complex dozens of interdependent silos. Capacity based pods are good options.Consider loose coupling to legacy back office systems to support upgradesHave a plan for running on your own -> avoid lengthy services engagementMonitoring and Management requirements are clearly articulated to Operations team
• #14: Cloud Infrastructure requires a different way to look at management and monitoring of Cloud InfrastructureThe M’s of the 4 Horsemen of cloud are Compute, network, Storage and Applications>>Operational Layer criteria cover all aspects of the ongoing health,autonomic management and operations interactions with the cloud technology and business processIntegrated NOC DashboardsCustomer SupportEscalation ProcessTriage processMaintenanceMonitoringMeasurementCloud Infrastructure ManagementVirtual Resources ManagementOperations as a Services
• #15: Ensure operations will take ownership (clouds need operations staff)Provide integrated view of cloud with legacy systems -> single NOC dashboardConduct training and review support and escalation proceduresCreate appropriate deployment documentationInvest in utilities and scripts development to support more “autonomic” operationsMake sure operational and services level agreements are realisticConsider Operations as a Service to increase customer visibility into their cloud resources
• #16: This is a difficult activity for most organizations!It is best conducted in a workshop environment to get good results.
• #20: The key points here are the CSA is the discovery process for cloud. The CSA is driven by exchange of information. CSA is most effective with lots of information exchange between citrix and the client.Assess includes the Business case processIn Business Case process Customers will take the Cloud strategy output and generate Business Case/justifications for moving forward with cloudAssess phase (Cloud Offerings definition) customers decide on key features that make it into the initial cloud offerings and those that will be released over the various phases. Customers typically conduct a POC or CCP/CPBM Assessments during the Assess phase.Design phase (Infrastructure, Support, logistics definition) customer gets specific on the design choices determined by the service description. The Cloud Architecture is a key document in the design phase.Deploy phase (CS/CPBM installation/customizations) customer deploy the cloud orchestration and management software. CCP Implementation services get the customer running quicklyMonitor phase (Cloud Offering in commercial Market) customer goes live with the Cloud offering and end user subscribers start using the services.