Ccs336 CSM Unit II Notes - Updated
Ccs336 CSM Unit II Notes - Updated
● Service Function
● Service Economics
● Service chain Entity
DEPARTMENT OF INFORMATION
TECHNOLOGY
UNIT -2
✔ Cloud Strategy
Fundamentals
✔ Cloud Strategy
Management
Framework
✔ Risk Management
✔ IT Capacity and
Utilization
✔ Change Management
✔ Cloud Service
Architecture
● Service Consumption
● Service usage and Billing
● Service Security
● Service monitoring and Control
1. Service Consumption: (how much bandwidth data is consumed)
- Service consumption is based on the usage of cloud resources based on entitlement or subscription.
- Parameters: It includes
b. Consumption component (the way the resources are used – Pay-as-you-Go-, reserved instances,
spot instances, subscription, free tier, etc..)
- It is used to generating bills for the resources used based on predefined policies.
- Functionalities involved:
- It includes
a. Consumer access
- It includes
a. Monitoring boundary
b. Instrumentation
c. Map – Graph representation about utilization of resources status, health and performance.
5. Self-Service
- It includes
✔ Service name 8. Service Economics
✔ Function ▪ Status
✔ Description ▪ Utility
▪ Warranty
- It deals with the principles, costs and benefits of cloud computing.
- It includes
✔ Cost management
✔ Cost model
✔ Charge back / show back
9. Service chain Entity
- It defines a sequence or combination of interconnected cloud services or resources that work together to
deliver a specific functionality or application.
- It includes
✔ Creator
✔ Provider
✔ Supporter
✔ Integrator
✔ Orchestrator
✔ Aggregator
✔ Consumer
✔ Payer
1.CLOUD STRATEGY FUNDAMENTALS (C311.2, PO 1,4,11)
❖ Strategy: It involves setting goals and priorities, determining actions to achieve the goals, and
mobilizing resources to execute the actions.
❖ Cloud strategy: It is the plan an organization follows to host its IT infrastructure in a cloud
environment.
❖ GOAL:
1. Optimize the business outcomes (speed, resilience[elasticity] and agility) (or) Ensure Effective
performance of the infrastructure
2. Enable distributed based cloud architecture for different services
3. Growing the public to improve the skills internally
4. Minimize the risks and challenges
❖ It refers to the core principles and considerations that organizations should take into account when
adopting and implementing cloud technologies.
❖ Cloud Strategy must support (cloud management)
a. Cost
b. Service level
c. Functionalities
❖ CLOUD STRATEGY PRINCIPLES:
a. Trust
b. Enablement
c. Enterprise Risk
d. Capability
e. Cost-benefit
f. Accountability
❖ FUNDAMENTAL ASPECTS FOR STRATEGY FORMULATION
1. Business Objectives and Alignment - align the cloud strategy with the overall business strategy to
ensure that technology decisions are in line with the company's direction.
2. Workload Assessment - Evaluate existing applications and workloads to determine which ones
are suitable for migration to the cloud.
3. Selection of suitable Deployment Models
4. Selection of suitable Service Models to align with the business goals
5. Security and Compliance - Security strategy that addresses data protection, access control,
encryption, and compliance requirements specific to your industry and jurisdiction.
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 or financial 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
❖ MAIN PHASES:
1. Strategy Phase
- It is the initial and foundational part of strategy steps.
- It sets the foundation for successful cloud adoption by aligning technology decisions with business goals and
considering the organization's unique needs and challenges
2. Planning Phase
- Perform the problem analysis & risk analysis for switching to cloud technology
- Steps:
a. Development of Business Architecture
b. Development of IT Architecture
c. QOS development requirement
d. Development of Transformation plan
3. Deployment Phase
❖ Definition: It is a structured approach that guides organizations through the process of developing,
implementing, and managing their cloud strategies.
❖ It provides a systematic way to align business objectives, technology decisions, and operational
considerations when adopting and utilizing cloud services.
❖ It is essential for providing a structured, consistent, and effective approach to managing cloud
services.
❖ It helps organizations mitigate risks, optimize resources, ensure security and compliance, and align
cloud strategies with business objectives in a rapidly evolving technological landscape.
❖ NEED FOR CLOUD SERVICE FRAMEWORK:
1. Need common standard ad practices (wide range of services, technologies and providers)
2. Complexity management (hybrid or multi-cloud setups)
3. Efficiency
4. Scalability
5. Security and compliance
6. Training and onboarding (easy)
7. Change management (adopt with new technologies in cloud)
8. Resource management
❖ COMPONENTS OF CLOUD STRATEGY MANAGEMENT FRAMEWORK:
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
❖ FRAMEWORK ARCHITECTURE:
3.CLOUD POLICY (C311.2, PO 1,3,4,11)
❖ Cloud security policy: It is formal guidelines companies adhere to that help ensure safe and secure operations
in the cloud. (or) set of rules, guidelines, and principles that an organization establishes to govern the use,
management, and security of cloud computing resources and services.
❖ It is an essential part of your cloud security strategy and helps your organization properly store and protect your critical data
assets.
❖ Entire Life cycle: A cloud policy is applicable throughout the entire lifecycle of cloud adoption.
❖ Guidance: It serves as a guiding document that outlines the rules, guidelines, and best practices for
using, securing, and managing cloud resources effectively.
❖ Not adopting cloud policy: If not adopting a cloud policy can result in a lack of consistency, security
vulnerabilities, compliance risks, inefficiencies, and missed opportunities.
❖ POLICY ENSURES
a. Confidentiality
b. Integrity
c. Availability of data stored
d. Accessing of data
e. Manipulation of data
❖ KEY ASPECTS:
❖ Life Cycle: It needs to be applied throughout the entire lifecycle of cloud services management, from the initial
planning and assessment phases to ongoing operations and monitoring.
❖ Continuous process: Risk management is a continuous and integral part of cloud services management.
❖ Risk management life cycle: It is a structured process that organizations follow to identify, assess, mitigate,
monitor, and respond to risks.
b. Cloud vendor security risk – CSP cloud security and risk mitigation affects organization growth
c. Availability - Any internet connection loss disrupts the cloud provider's services, making the services
inoperative
d. Compliance - The service provider might not follow the external audit process, exposing the end user to
security risks
2. Risk Assessment
6. Vendor risk management - evaluate the security practices and certifications of CSP
8. Service availability
9. Change Management – It ensures that updates, changes, and configurations are carefully planned and
tested to avoid disruptions.
10. Business continuity - ensure that critical applications and data can be restored in the event of a disaster.
11. Incident Response
a. Forecast probable issues (identify the risks – helps to implementing appropriate control strategies)
d. Better budgeting
❖ It plays a pivotal role in shaping the strategy, benefits, and outcomes of adopting cloud services.
❖ Business Drivers:
a. Capacity Planning - Estimates the production capacity (storage, infrastructure, hardware, software,
availability of resources) needed for its products to cope with the ever-changing demands in the
market. It depends on
o Level of demand
o Cost of production
o Availability of funds
b. Cost Reduction
c. Organizational Agility - the process by which an organization will adapt and evolve to sudden changes
caused by internal and external factors.
1. Security
3. Efficiency
5. Rapid Recovery
8. Strategic Value [competitive edge to businesses - business agility and customer satisfaction]
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 – Cloud services enables fast provisioning of resources and deployment of
applications. (reduce time for the product enter into market)
❖ key drivers for cloud service adoption are not defined clearly, an organization may face various challenges and uncertainties
when transitioning to the cloud.
b. Unpredictable outcome
e. Missed opportunities
❖ Demand: The amount of computing resources that users require at any given time.
❖ Need for Demand and capacity utilization:
a. User activity
b. Application usage
c. Business operations
❖ General Methods:
❖ Demand Forecasting: It is the process of estimating the future demand for a service or product on
historical data, market trends, customer behavior, and other factors.
❖ Different forecasting models:
❖ Key aspects define the relationship between demand and capacity matching:
❖ Challenges:
❖ Need for effective queue strategies: It is need to fine-tune their queuing strategies and ensure that
resource capacity is adjusted to meet the overall demand over time.
❖ Balance: Need to create a balance between demand queuing and providing timely access to resources
for effective management.
❖ Essential tool: It ensures fair and organized access to resources during times of high demand,
promoting a balanced and efficient service environment.
❖ Need for Queuing Strategies: It helps to manage the situations when the demand for
resources temporarily exceeds the available capacity.
❖ Size of the Queue: It defines the balance between demand and capacity
❖ Size of the queue is measured by counting the number of requests or tasks that are currently waiting
in line to be processed or fulfilled by the cloud service provider.
a. Resource optimization
b. Fairness (FIFO order)
c. Performance stability
d. Reduced service failure (minimize the rejection of services)
❖ Challenges faced if queue mechanism is not implemented:
a. Service rejection
b. Unpredictable access
c. User dissatisfaction
d. Missed business opportunities
e. Inefficient resource utilization
f. Lack of prioritization
g. Unpredictable performance
h. Loss of business opportunities
i. Negative impact in revenue
j. Reduced customer loyalty
a. Maintain control
b. Maintain Stability
c. Maintain security
d. Maintain compliance
❖ Stable and Reliable: It is crucial for maintaining a stable and reliable cloud environment, ensuring
data security and compliance, and facilitating the seamless evolution of cloud-based solutions as
business needs evolve.
❖ Duration of change management: It depends on,
a. Change identification and request (new feature / existing, configuration change or security)
b. Change evaluation – assess the potential impact [Evaluate technical feasibility, risk analysis,
benefits, costs and alignment with business goals]
c. Change planning – develop a plan for implementing the change (it involves defining the
scope, setting priorities, allocating resources and creating timeline)
d. Testing and validation
e. Communication and stakeholder management - Keep all relevant stakeholders informed
about the upcoming change
f. Change deployment – implement the changes in the production based on plan (requires
careful execution to minimize disruptions to ongoing operations)
g. Monitoring and feedback – identify or detect any anomalies, performance degradation or
security issues introduced due to the changes if any
h. Issue Resolution – Address the issue (rollback needed in necessary)
i. Documentation and knowledge management
j. Post- change review
❖ Advantages of Change Management:
a. Continuous improvement
b. Adopt to new technology and innovation
c. Improve vendor relationship
d. Adopt to new infrastructure
e. Helps to improve the security
f. Minimize user impact
g. Helps to reduce the risks
(or)