Scribd
Upload
113 views

Cloud Computing - Digital Talent Training Kominfo

This document discusses considerations for cloud computing and digital talent training on the KOMINFO platform. It outlines general considerations like workload limits and compatibility. It also discusses migration scenarios from on-premises, physical and virtual servers to Azure. The document details migration approaches like lift and shift to IaaS and establishing new targets for PaaS. It covers governance considerations involving role-based access control and best practices for resource manager policies, locks, tagging, auditing and automation. Additional planning factors are outlined like regions, operating systems, databases, workloads, storage, on-premises dependencies, clustering, scalability, and networking.

Uploaded by

Andi Faqtur Rahman
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
113 views

Cloud Computing - Digital Talent Training Kominfo

This document discusses considerations for cloud computing and digital talent training on the KOMINFO platform. It outlines general considerations like workload limits and compatibility. It also discusses migration scenarios from on-premises, physical and virtual servers to Azure. The document details migration approaches like lift and shift to IaaS and establishing new targets for PaaS. It covers governance considerations involving role-based access control and best practices for resource manager policies, locks, tagging, auditing and automation. Additional planning factors are outlined like regions, operating systems, databases, workloads, storage, on-premises dependencies, clustering, scalability, and networking.

Uploaded by

Andi Faqtur Rahman
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

CLOUD COMPUTING | DIGITAL TALENT TRAINING KOMINFO

AGENDA |
GENERAL GOVERNANCE
CONSIDERATIONS CONSIDERATIONS
1 2

ADDITIONAL
PLANNING
CONSIDERATIONS
3
General Considerations
Workload limit
• Batas Workload terbagi menjadi default dan hard limit. Memastikan
workload tidak melebihi batas maksimum adalah penting
Workload compatibility
• not all workloads are supported by Microsoft, but many can run in
Azure. An example of this is Windows Server 2003
over- or under provision prevention
• over-provisioning a VM will add additional cost that will reduce
return on investment (ROI). Under-provisioning will degrade the
performance and reliability of a workload
Migration Scenarios
This topic answers the question of what the source environment is in the
case of a migration, as well as whether it is a virtualized environment.
Possible answers for the migration scenario include:
• On-premises to Azure • AWS to Azure
• Physical servers • Google to Azure
• Virtual servers • Azure to Azure
• Hyper-V based • Classic (v1) to Resource Manager
• VMware based • Region to region
• KMS based
• XenServer based
Migration Approaches
IaaS
• ReAccomplishing a lift and shift, by copying VM disks into Azure
storage and creating VMs from them.
• installing the workload onto IaaS servers.
• Using tools like Azure Site Recovery to synchronize VM disk copies
into Azure, then failing over workloads as a method of migration.
• Establishing a new target for continuous deployment (CD) tools and
processes.
PaaS
• Establishing a new target for continuous deployment (CD) tools and
processes.
Governance Considerations
Role Based Access Control
• RBAC is configured by selecting a role, then associating the role with a
user, group, or service principal.
• Finally, this combination of role and user/group/service principal is scoped
to either the entire subscription, a resource group, or specific resources
within a resource group.
Governance in Azure
Governance in Azure
Resource Manager Policies in Azure
• Resource manager policies allow an organization to create
conventions which control behavior for resources
• Resource manager policies apply these conventions to a scope,
such as the subscription, a resource group or to specific
resources
• Resource manager policies essentially define what actions are
allowed and are a default allow system. They are described via
policy definitions and applied through policy assignments.
Governance in Azure
Resource Manager Locks
• Locks come in two varieties.
• The available types of resource manager locks include Read-
Only and CanNotDelete. And just like resource manager
policies, locks are scoped at the subscription, resource group,
and resource levels.
• Read-Only, which prevents any changes to the resource. Authorized
users can't delete or modify a resource.
• CanNotDelete, which prevents deletion. Authorized users can change
but not delete a resource.
Other Governance Best Practices
Naming Standards
• well-designed naming standards enable the identification of resources
in the portal, on a bill, and within scripts. Most organizations already
leverage a naming standard for on-premises deployments.
Auditing
• all create, read, update, and delete (CRUD) operations are
automatically logged in Azure so that sensitive operations can be
reported on where required.
Other Governance Best Practices
Use of Resource Tags
• as users in an organization add resources to the subscription, it
becomes increasingly important to associate resources with the
appropriate department, customer, and environment. Customers can
attach metadata to resources through tags and use them to provide
information about the resource or the owner.
Purposeful Resource Group Usage
• Without a policy on how Resource Groups will be used, they can
quickly become a management burden. Properly utilized, resource
groups enable organizations to put resources into meaningful groups
for management, billing, or natural affinity.
Other Governance Best Practices
Automation
• provides a way for organizations to automate the manual, long-running,
error-prone, and frequently repeated tasks that are commonly
performed in a cloud and enterprise environment. Automation saves
time and increases the reliability of regular administrative tasks and
schedules can be used so that tasks are automatically performed at
regular intervals.
ADDITIONAL
PLANNING CONSIDERATIONS
11

REGION OS & SERVER DATABASE WORKLOAD DATA


ROLES NEEDS PERFORMANCE STORAGE

ON-PREMISES CLUSTERING SCALABILITY & NETWORK


DEPENDENCIES / LOAD ELASTICITY LATENCY
BALANCING
Terimakasih :D

You might also like