Good day All,
Welcome back!!!
As sysadmins we all must have done lot of Server builds so let's see if have to do the same in cloud how it differs
On Premises Server build Steps:
1. On Premises Architect will understand Application requirement , and work with Business and get a Approval to Create a new VM
2. Build document from Business which will list out Server Name, Number of CPU, Memory.Number of IP's ,Network Details,Hard disk Specifications, Additional Windows Component request , and all business tools.
3. ITIL Process,
4. As most of the environment would be VMware i am just taking that as example here.As Sysadmins you would check for a template , convert the template to Virtual Machines and configure the Virtual machines as per Build documents and hand it over to Client.
In Cloud everything you do will cost you money and this is were Architects play a major role.
Still confused lets me explain more.
As sysadmins did you ever think about business requirement like CPU,Memory,Hard disk,IOPS etc.. nope we just followed the build documents but in Cloud you need to pay attention to every bit and pieces of these things and if wrongly provisioned you looking at burning money to company.
Terrified??? In Cloud all these are referred as compute resource and you need to buy with different Server model available.
Still confused let me see if i can explain.. so if you have to build a Server you will have to pick certain Size Virtual machine in market place which is kind of bundle with OS,Memory, CPU,IOPS of the Hard disk examples as below
General Purpose VM
Compute Optimized VM
Memory Optimized VM
Storage Optimized VM
GPU Optimized VM
High Performance Compute VM
In Cloud Server build Steps:
1. On Premise Architect will have to do a major upgrade to understand Cloud and will have to work with Business , Understand Application requirements and its Compute resource requirement like CPU,Memory,Hard disk,IOPS it required and come with Cost optimized Virtual Machine Sizes before getting approval for a VM.
2. Build documents will now have VM Size to pick in Cloud and rest of the details like Server Name, IP details and Install Tools will remain same.
3.ITIL process will be same as On Premises.
4. As sysadmin you will login to Cloud, Pick the VM mentioned in Build document and just do couple of clicks and your VM will be provisioned. Post joining to domain, tools install will be same as you do in on premises.
As a Sysadmins it's not a major learning curve but if you want to be a Cloud Architect then yes a very big learning curve
Hopefully this helps someone, until next one you all have a good day!!!!!!!!!!!!!!!!!!!!!!!!!!
Note: Above steps i mentioned is if Business requirement is for a IAAS offering for VM. If Architects further analyzing the Application may even look at PAAS offering then the whole Build process will change
Welcome back!!!
As sysadmins we all must have done lot of Server builds so let's see if have to do the same in cloud how it differs
On Premises Server build Steps:
1. On Premises Architect will understand Application requirement , and work with Business and get a Approval to Create a new VM
2. Build document from Business which will list out Server Name, Number of CPU, Memory.Number of IP's ,Network Details,Hard disk Specifications, Additional Windows Component request , and all business tools.
3. ITIL Process,
4. As most of the environment would be VMware i am just taking that as example here.As Sysadmins you would check for a template , convert the template to Virtual Machines and configure the Virtual machines as per Build documents and hand it over to Client.
In Cloud everything you do will cost you money and this is were Architects play a major role.
Still confused lets me explain more.
As sysadmins did you ever think about business requirement like CPU,Memory,Hard disk,IOPS etc.. nope we just followed the build documents but in Cloud you need to pay attention to every bit and pieces of these things and if wrongly provisioned you looking at burning money to company.
Terrified??? In Cloud all these are referred as compute resource and you need to buy with different Server model available.
Still confused let me see if i can explain.. so if you have to build a Server you will have to pick certain Size Virtual machine in market place which is kind of bundle with OS,Memory, CPU,IOPS of the Hard disk examples as below
General Purpose VM
Compute Optimized VM
Memory Optimized VM
Storage Optimized VM
GPU Optimized VM
High Performance Compute VM
In Cloud Server build Steps:
1. On Premise Architect will have to do a major upgrade to understand Cloud and will have to work with Business , Understand Application requirements and its Compute resource requirement like CPU,Memory,Hard disk,IOPS it required and come with Cost optimized Virtual Machine Sizes before getting approval for a VM.
2. Build documents will now have VM Size to pick in Cloud and rest of the details like Server Name, IP details and Install Tools will remain same.
3.ITIL process will be same as On Premises.
4. As sysadmin you will login to Cloud, Pick the VM mentioned in Build document and just do couple of clicks and your VM will be provisioned. Post joining to domain, tools install will be same as you do in on premises.
As a Sysadmins it's not a major learning curve but if you want to be a Cloud Architect then yes a very big learning curve
Hopefully this helps someone, until next one you all have a good day!!!!!!!!!!!!!!!!!!!!!!!!!!
Note: Above steps i mentioned is if Business requirement is for a IAAS offering for VM. If Architects further analyzing the Application may even look at PAAS offering then the whole Build process will change
No comments:
Post a Comment