Cloud Service Management Notes Unit 3
Cloud Service Management Notes Unit 3
2. Service Provider - The entity that delivers the cloud service, which can be an
internal IT team or a third-party provider.
Conditions:
1. Alignment with Business Needs
2. Continuous Monitoring and Improvement
Different Phases of Cloud service Life Cycle:
1. Planning and Design – It defines the service's purpose, requirements, architecture,
and design.
- The initial plan includes objectives, scope, resources, and a high-level roadmap.
2. Deployment and Provisioning - The service is deployed based on the design,
utilizing infrastructure resources such as virtual machines, containers, and
networking components.
- Provisioning involves setting up users, access controls, and configurations.
3. Management and Operations - It involves day-to-day management, monitoring,
scaling, performance optimization, security enforcement, and compliance
maintenance.
4. Scaling and Optimization - As usage patterns change, the service may need to be
scaled up or down to ensure optimal performance and cost-effectiveness.
Optimization efforts focus on resource utilization and efficiency.
5. Updates and Upgrades - Regular updates, patching, and upgrades are performed to
enhance functionality, security, and compatibility. This includes testing and
validation to prevent disruptions.
6. Monitoring and Analytics - Ongoing monitoring of the service's performance,
usage, and security helps identify issues and trends. Analytics provide insights for
making informed decisions.
7. End-of-Life and Decommissioning - When a service is no longer needed or becomes
obsolete, it is retired in a controlled manner. Data may be migrated, and resources
are released.
8. Configuration and Customization - Once deployed, the resource may require
configuration adjustments and customization to align with specific business needs
and user requirements.
9. Data Management and Backup
10. Cloud Cleanup
BASICS OF CLOUD SERVICE DESIGN
Goal: To create an efficient, reliable, and scalable solutions that leverage the
capabilities of cloud computing to meet the specific needs of an organization or
application. It supports the users through a service catalog.
Primary objectives:
1. Scalability and flexibility
2. Reliability and availability
3. Optimized resource optimization
4. Security
5. Better User experience
6. Effective performance
7. Interoperability
8. Innovation and Agility
9. Disaster recovery and business continuity
10. Elasticity
Steps involved in cloud service design:
1. Assessment and Analysis - Workload assessment (identify current IT
landscape, business needs)
2. Business Objectives and Alignment (vision and objectives)
3. Selection of suitable Deployment Models
4. Selection of suitable Service Models to align with the business goals
5. Governance and policies (security, compliance, data management and
budgeting)
6. Data Management and Governance – Define how data will be managed, stored,
and accessed in the cloud. Establish data governance policies to ensure data
quality, privacy, and compliance.
7. Cost Management
8. Migration Plan
9. Vendor Selection - Evaluate and choose a cloud service provider based on
factors such as service offerings, pricing, geographic availability, reliability,
and support.
10. Performance and Scalability
11. Resilience and Disaster Recovery
12. Training and Skill Development
13. Change Management and Training
14. Performance Monitoring and Management
15. Continuous Improvement
16. Communication and Reporting
A service catalog: It is a listing of services from which a user can choose, thus
initiating the cloud service provisioning process.
Different types of users considered for service catalog:
a. Development team
b. R&D groups
c. The application team in charge of building and maintaining internal applications
Cloud Service Design
It helps the balance between customize offering to the users along with tight controls
on the services in the cloud environment.
Attributes of service catalog:
1. Operating systems
2. Middleware stacks
3. Applications offered
4. Networking options – for both simple network configuration and multi-tenancy
support
5. Compliance packages
6. Monitoring tools
7. Service levels
8. Prices associated with each component, if desired
Advantages:
1. Security
2. Cost Saving or cost Efficiency
3. Efficiency
4. Flexibility and Scalability
5. Rapid Recovery
6. Increased Convenience – easy accessing
7. Speed and Productivity
8. Strategic Value [ competitive edge to businesses - business agility and customer
satisfaction]
9. Multi-tenancy (multiple customer share the underlying models)
10. Service and innovation (use many API and use flexible cloud tools and
environments to build new and innovative applications and process)
11. Standards
12. Sustainability
13. Rapid deployment
14. Access to advanced technologies
15. Reduced IT Management Burden
16. Competitive advantage
DEALING WITH LEGACY SYSTEMS AND SERVICES
Legacy systems: It is any outdated computing system, hardware or software that is
still in use. Ex.: Microsoft windows 7 (no longer supported after 2020)
Example for Legacy Systems : COBOL, SAP, Lotus Notes
Primary challenge in legacy Systems: It often built on outdated technologies and
software, which may not be compatible with modern cloud platforms.
Condition for migration of legacy systems into cloud: Data need to be restructured
or reformatted or re-architected before it can be successfully migrated into the cloud.
Criteria to migrate from legacy systems to cloud:
1. Compatibility assessment (restructure, refactoring, reengineering)
2. Business impact
3. Cost benefit analysis
4. Risk analysis
5. Security and compliance
6. Data migration strategy
7. Performance and scalability
8. Integration strategy
9. User experience
10. Training and knowledge transfer
Steps involved to manage legacy systems in cloud:
1. Assessment and Inventory
2. Prioritization (based on goals, technical feasibility, potential impact) – Analyze
for the suitable for migration
3. Refactoring or replatform
4. Integration strategy (API, middleware tools)
5. Data Migration
6. Hybrid approach (local and cloud services in the legacy systems)
7. Security and compliance
8. Testing and validation
9. Monitoring and management (track the performance)
10. Training and support
11. Retirement strategy (migrate from legacy systems to cloud)
12. Documentation
13. Continuous improvement
14. Communication (maintain communication with stakeholders about the
progress, benefits, challenges of the transition)