38 CLOUD COMPUTING
38 CLOUD COMPUTING
Scripting adds complexity Since current script writers don ’ t fully understand scripts written by previous script writers , they tend to write new ‘ helper scripts ’ rather than risk breaking an existing one . The result is scripts on top of scripts , which creates everincreasing complexity .
These points aren ’ t to say that scripting is never useful in IT . Scripting simply isn ’ t an effective means of automating complex service provisioning processes that must continually be modified in response to changing business and technology requirements .
Scripting is personal and opaque Script writers almost never document their work or explain it clearly to others . Therefore , it ’ s only really useful to the writers themselves , and when they leave it becomes useless or impossible to maintain .
Scripting is brittle and ungovernable Because scripting hard codes a specific way of doing a specific task , it can ’ t be easily adapted to new processes or similar tasks . This again inhibits adaptability , forcing IT staff to go back to the drawing board over and over .
IT isn ' t the only cloud stakeholder
3
Businesses don ’ t adopt the cloud simply to make life easier for IT ; they adopt it to benefit the wider business , making it faster and more scalable . Therefore , any cloud automation needs to fulfil the needs of both IT , and non-IT stakeholders .
Automation that depends on IT isn ’ t really automation because it still interposes manual steps between cloud provisioning and cloud consumers in the lines of business . Cloud automation must therefore include business selfservice , allowing business users and managers to activate services where it makes sense to do so . Where appropriate , Lines of Business ( LOBs ) managers should also be given the ability to approve or reject user requests .
HR administers take care of hiring , promotion , transfer and termination of employees . People must be given an initial set of services when they ’ re hired , and today many of those are cloud based . Their service permissions must be changed when they ’ re promoted or transferred . And when they are terminated , all service permissions / accounts must be eliminated across all internal and external servers .
IT isn ’ t the only stakeholder in cloud automation , but it ’ s a big one . Routine tasks consume IT resources , and limit its ability to move ahead with higher-impact strategic projects . Cloud automation should therefore fully meet the IT department ' s needs for functional completeness , ease of deployment and management .
TS IT - Network Rack
Make IT fast .... Make IT simple .... Make IT adapta
.... Make IT ea
ENCLOSURES POWER DISTRIBUTION
CLIMATE CONTROL