Showing posts with label azure. Show all posts
Showing posts with label azure. Show all posts

Friday, May 19, 2017

Azure Terminology

IaaS – infrastructure as a service
https://azure.microsoft.com/en-us/overview/what-is-iaas/
PaaS - platform as a service
https://azure.microsoft.com/en-us/overview/what-is-paas/
SaaS stands for software as a service
https://azure.microsoft.com/en-us/overview/what-is-saas/

IaaS is comprised of highly automated and scalable compute resources, complemented by cloud storage and network capability which can be self-provisioned, metered, and available on-demand.
PaaS functions at a lower level than SaaS, typically providing a platform on which software can be developed and deployed. PaaS providers abstract much of the work of dealing with servers and give clients an environment in which the operating system and server software, as well as the underlying server hardware and network infrastructure are taken care of, leaving users free to focus on the business side of scalability, and the application development of their product or service.
SaaS has a main difference of being hosted by a vendor where iPaaS is cloud-based. Applications that are on-premise hosted can be integrated and allow for free flow of data. The application or service is made available to customers over a network, usually the internet.

aPaaS - application platform as a service
iPaaS - integration platform as a service

aPaaS allows for rapid application development and delivery. This form has high productivity and high control. The coding process for platforms as a service can slow down delivery, but aPaaS brings automation for the application lifecycle. aPaaS offers a faster way to build apps
iPaaS is a cloud-based integration solution, unlike SaaS which is hosted by a vendor on-premise. It iPaaS allows applications that reside on the cloud or on-premise to integrate and have data flow freely between them. It does not need any download, it is simply deployed. This is the most balanced offering because it can bring differently hosted software solutions or applications together.

Reference

Cloud Service Models (IaaS, SaaS, PaaS)https://www.cmswire.com/cms/information-management/cloud-service-models-iaas-saas-paas-how-microsoft-office-365-azure-fit-in-021672.php

Azure Glossary
https://docs.microsoft.com/en-us/azure/azure-glossary-cloud-terminology

Cloud computing terms
https://azure.microsoft.com/en-us/overview/cloud-computing-dictionary/
Compare AWS and Azure
https://www.cloudyn.com/blog/azure-terminology-for-aws-speakers/
Windows Azure Platform Glossary for IT Pros
https://blogs.technet.microsoft.com/yungchou/2011/04/21/windows-azure-platform-glossary-for-it-pros/
https://ryvit.com/the-difference-between-ipaas-apaas-and-saas/
https://www.computenext.com/blog/when-to-use-saas-paas-and-iaas/
https://msdn.microsoft.com/en-us/magazine/ee309870.aspx

Azure Maintenance

Use TRIM with unmanaged standard disks
https://docs.microsoft.com/en-us/azure/storage/storage-about-disks-and-vhds-windows

Thursday, April 9, 2015

Azure Basic - Definitions

Reference
https://technet.microsoft.com/en-us/magazine/hh509051.aspx

Essential Characteristics:
  • On-demand self-service -- A consumer can independently and unilaterally provision computing capabilities, such as compute time, network connectivity and storage, as needed automatically without requiring human interaction with each service’s provider
  • Broad network access --Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms
  • Resource pooling -- The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources, but may be able to specify location at a higher level of abstraction (e.g., country, state, region or datacenter). Examples of computing resources include storage, processing (compute), memory, network bandwidth, and virtual machines
  • Rapid elasticity -- Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out, and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time
  • Measured Service -- Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, compute, bandwidth, active user accounts, etc.). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service
Service Models - Define Saas, PaaS, IaaS
  • Cloud Software as a Service (SaaS)--The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of provider-defined user-specific application configuration settings
  • Cloud Platform as a Service (PaaS)--The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations
  • Cloud Infrastructure as a Service (IaaS)--The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud physical infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components
Deployment Models:
  • Private cloud -- The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise
  • Community cloud --The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise
  • Public cloud --The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services
  • Hybrid cloud-- The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds)

Thursday, March 5, 2015

Azure – Start Here

More from the cloud engineer

Basics (legacy)
http://thecloudengineer.blogspot.com/2015/04/azure-basic-definitions.html

Labs

http://thecloudengineer.blogspot.com/2017/04/azure-labs.html

http://thecloudengineer.blogspot.com/2011/09/great-sharepoint-2010-sp1-vhd.html

Spending Limits - Piece of Mind
http://azure.microsoft.com/en-us/pricing/spending-limits/

Early Experts
Great Site from Keith Meyer – Microsoft Evangelist
http://blogs.technet.com/b/keithmayer/archive/2015/01/12/early-experts-study-guide-for-microsoft-specialist-certification-exam-70-534-architecting-microsoft-azure-solutions.aspx

Labs from IT GURU

Description and Live links to Series

- See more at: http://itproguru.com/expert/2015/02/it-camp-azure-labslab-5-building-application-workloads-deploy-data-access-appstep-by-step/#sthash.Htz6f0FL.dpuf

Screen by Screen Labs – Yung Chou and others
https://yungchou.wordpress.com/2015/03/02/screen-by-screen-guided-labs-for-us-it-camps-in-spring-of-2015/

Online version is also at http://aka.ms/FY15Q3Labs. In addition,

Lab 1

Create a virtual network, allocate a storage account and configure a cloud service. Which builds a foundation for deploying resources in Azure.

Lab 2

Deploy a VM with custom script to configure an AD forest. This AD environment is to mimic an on-premises Active Directory establishment for Lab 3 to configure DIrSync with Azure AD in cloud.

Lab 3

Create an azure AD directory followed by configuring DirSyn and MFA, i.e. multi-factor authentication. The click-through includes the deployment of an Active Directory forest, identical to the one in Lab 2 to make Lab 3 a self-contain module for learning DirSync and MFA.

Lab 4

Configure the connectivity between Azure VMs of a SQL server and an IIS server to form a web application.

Lab 5 – Soon

Deploy a web application to the web server configured in Lab 4. The click-through is to be available. Subscribe the page to receive the updates.