In this blog, I will cover:
Major Cloud hardware components are Compute, Storage and Network. There are 2 models of building Cloud infrastructure.
In this blog, I will cover the considerations for developing and deploying applications for the Cloud along with the newer deployment models like Devops and Paas based approach.
Developing applications for the cloud is little similar to developing applications for the web but its not exactly the same. In the cloud, there are considerations like failure handling, traffic unpredictability, resource distribution which does not apply to typical web based application. Can we take any enterprise application and directly put them in the cloud and make it an Cloud based application? This normally does not work unless the enterprise application has the cloud application characteristics which I have described below.
Following are some of the important characteristics of a Cloud based application:
Continue reading Developing and Deploying applications for the Cloud
In this blog, I will cover basics of Cloud OS, how Enterprise Cloud is different from private/public clouds from Cloud providers and comparison of the major Open source cloud OS available today.
Cloud OS:
Just like Operating system for a desktop or server manages the resources associated with it, Cloud OS manages the resources associated with the cloud. Major cloud resources are compute, storage and network. Compute includes servers and hypervisors associated with the servers that allows for VM creation. Storage includes local storage, Storage area network and Object storage. Network includes vlans, firewalls, load balancers etc. Cloud OS is also responsible for giving the cloud characteristics like Elasticity, self service provisioning model etc. Cloud OS is also responsible for other items like image management, authentication, security, billing etc.
In this blog, I will cover common methods of accessing AWS services using AWS console, AWS CLI and AWS Python SDK. The basic requirement is to have the AWS free account already created.
AWS console:
With AWS console, all activities could be done using the web interface. This approach becomes cumbersome when dealing with hundreds of VMs. Also, we cannot have a programmatic model with this approach.
AWS CLI:
AWS CLI for Windows or Linux can be downloaded from here. Using AWS CLI, all AWS services can be invoked using CLI.
Amazon AWS is the leader in Cloud provider marketspace. AWS started out with IaaS but have also become a PaaS player now. Amazon’s services extends Computing, Storage, Database, Analytics and Application services. There are multiple granular services under each of the above categories. The best way to get familiar with the cloud services is by trying them out. AWS has an excellent 1 year free tier program where users can try AWS services. The free subscription is with the smallest performance VM and it cannot be used for business purposes, but its a great tool to experiment and get familiar. I could not find the free option with Google compute engine. With Microsoft Azure, they have 1 month trial option.
In this blog, I will cover a comparison of IaaS, PaaS, SaaS cloud services.
Following diagram nicely illustrates the layers and target customers associated with these 3 cloud services.
In this blog, I will cover different models for deploying Cloud services.
Following are the broad categories for deploying Cloud services.
Cloud Computing is the most talked about buzzword today. Though there is a deluge of information available in Cloud computing everywhere, I found it difficult to pick the practical and relevant information I need. Following are some topics that I will explore in the next series of blogs(not in the same order). I am not an expert in any of these topics, I am writing this blog as I am learning more on each of these topics.
In this blog, I will cover the evolution of Openflow(from 1.0-1.4). Also, I will cover the hands-on stuff that I tried with Openflow.
Openflow is a protocol by which we can control a Switch’s data plane with the Switch exposing flow tables as mentioned in Openflow protocol. Flow tables provide an abstraction and It is not necessary to expose internals of the switch.
In 1 of the previous posts, I had indicated that its difficult to resize the VM hard disk that was created during VM creation. My friend pointed me to few links on how to do this. It turned out be pretty straightforward.
Also, I learnt that when we try different applications and different configurations in the VM, its very easy for the VM OS to be screwed up and it is necessary to either take snapshots, backups, clones and restore them to be on the safe side.
In this blog, I will try to cover some of the common tasks that we would need from VM management perspective like VM backup and restore, resizing VM hard disk. I will say this in the context of Virtualbox, lot of these would apply to other VM hosting software like VMware player, etc. Also, I will cover some things that I have learnt in Virtual box along the way..
