User talk:Tutor banga

Automation of Infrastructure and Management Name: Class/Course Name: Professor (Tutor): School (University): Location: Date:

Infrastructure automation The process of designing setting of information technology structures in operating system installation, setting up and configuration of servers, and configuration of coordination between software. Infrastructure automation dictates configuring either to a single node of to many. The description of the design of the infrastructure and configuring it to a particular set ups so that the settings can be increased in an error free manner (Duvall 2012). Automation of infrastructure introduces swiftness in the development and operations as it facilitates modification by the administrators in implementing better improvement practices including versioning and analysing of the infrastructure. Automation infrastructure mostly occurs in cloud computing. Automation infrastructure involves scripting in targeted areas of automation in instrumentation and workflow. It also sets up a layout which cloud follows. It calls for understanding of the process, procedures and also the best tools to be used in automation. Scaling and updating of the infrastructure are done using configuring tools. Using several configuration and set-up tools eliminates system malfunctions. Automation depends on the stability, protection and efficacy for better service delivery. Automation of infrastructure ecology incorporates both open and also closed source tools allowing provision, organisation, description, monitoring and auditing of resolutions. The automation facilitates costuming of workflows to incorporate the tools that enable basic management through end-to-end computerization (Marschall 2015). Various software have been built to integrate a number of tools to work unanimously since no distinct tool in existence that meets all the necessities like management of configuration, allocation of codes, and even automated dimensions. There tools are dictated by the architecture and infrastructure provisions (Devopscube 2014). The various tools are

Chef Chef deals with managing the configuration which utilizes cookbooks perception where infrastructure’s domain specific language in incorporated with programing. The cookbooks dictates how configuration will be done. After chef is ran on all the servers, the cookbooks are withdrawn and the configuration are ran on the server to reach a specific desired purpose. Puppet Puppet is also a configuration management tool where puppet domain specific language is used to write configuration codes and then they are wrapped in modules. The puppet is customized while featuring the administrator. Puppet agent is ran in all servers to configure them and the retrieves the compiled module from the dummy server. The acquired software suites specific to a certain module are then installed to the achievement of a specific purpose. Saltstack It is an open configuration tools which provisions for remote execution of command mostly used in python operating system. Compiling of codes and their configuration is much faster as the codes can be sunk to several nodes concurrently. Ansible It is both an orchestration and configuring tool which uses playbooks that are written in YAML format comparatively easily written in comparison with other configuring tools. Juju Canonical developed orchestration tool operation on python, possessing UI which agree used to orchestrate applications in cloud settings. It is also used in configuration, allocation and scaling application. Others are Jenkins, Vagrant, Docker, New Relic and Sunsu which are all used in cloud computing. Scalability With the new emergence of automation and virtualization, the templates of the servers have to be marginalized to avoid replication of compiled codes with bad configuration being copied severally and causing problems to numerous servers. Scalability is the ability to get the correct automation instructions for the infrastructure. Configuration drift is where automation infrastructure keeps on being updated while other infrastructure are unable to keep up with its constant diversity and growth. In order to make a system scalable, the systems needs to be tested due to changes in two specific area, requirements and implementation of the system. If a test done to these changing aspects unsynchronized with the test people stop trusting the system in order to create a stronger suit for the tests, they need to be made more stable (Pronschinske 2014). The stability involves for instance testing the framework alongside with its libraries. The test cases are to be kept constant which facilitates addition of new test which are not dependent to the present tests. As automation becomes more essential in facilitating better management of settings. Introduction of new tools to facilitate orchestration and configuration of the servers makes it super easy to automate and provide for modification of the system modules and place appropriate tools for automation. Updating the skills of the administrators on the new automation tools enables the administrators to come up with new applications to service their customers. Flexibility Flexibility is important in four aspects of infrastructure 2.0: application, network, TCP/1P and accessibility terminals. The infrastructure should be capable of adapting to the changing environment in data to adapt the settings and also the difference in the data centres having different architecture and the dynamism of the technological devices. The infrastructure should be flexible enough to change with networking and configuration of the applications (Sabharwal & Wadhwa 2014). Different infrastructures need to be operating different range of applications as well as intermingle with other infrastructures The infrastructures should have the ability to send and receive packages from numerous connections while watching on the security requirements and policies governing the different infrastructure. The automated infrastructure need to be equipped with particular rank of intellect to be used to make decisions on successful fulfilment of the request in an effective and efficient manner. The infrastructure need to be able to execute functions from commands received from other infrastructure. It should be able to work into conjunction with the rest of the infrastructure to execute by itself functions depending with changes in applications and accessing terminals and also the infrastructure. The infrastructure should be able to provide security that satisfy the needs of the clients in their management of information management. There should be established standards supporting multiple protocols within the similar interface to ensure there is uniform security established for all clients.

Rapid deployments Developing in workflow needs rapid deployment of codes for production to facilitate the transfer of the idea from the developer to other clients for utilization. Continuous delivery of the products is a method of accepting automated deployment through the several level of software or application provision process. Automated deployment facilitates repeated and trustworthy method of delivery of the applications. The certainty of a software being accepted and used by clients is by letting them use the software thus automated deployment comes in handy in the distribution of the products (Etmajer 2014). Automated delivery can be best be described in the following five stages of continuous delivery pipeline Stage 1 is the commit stage where the existing automation system surveys the storehouse to provisional manual and assembles the cypher and effect quick run, does the unit tests then discharges artefacts and registration is automatically generated. Stage 2 is where test is done to approve the scripts which are subjected to smoke tests to quantify the software and the services offered are running smoothly then acceptance tests to quantify that the software is actually meting the organizational customer watch routine. Stage 3 tests the aptitude there test are done to quantify that the services provided by the software are defined under policies that govern the level of the invention. At stage 4 the customers are given the products to test their validity in meeting their need. At the final stage it is where the actual release takes place making them present at the binary repository. Some of the challenges experienced the deployment is configuration drift, as releasing of constituted applications may be challenged by inability of an organization to track the changes occurring to the middleware settings. The errors are detected at the testing and acceptance settings. Configuration drift way also be caused by disaster recovery (Open Group 2008). Programming software used in disaster recovery such as computer-assisted auditing tools (CAAT) to test software and intelligence, utilizes examination of information or re-enactments. However using inappropriate examining devices, review used in inspecting techniques to survey the controls can turn out to be more expensive than anticipated in financially savvy way. Changes Deployment in the recent business software services are expensive, thus most organizations prefer to use payment on the different automation services. It provides clients with faster access, cheaper, timely, flexible and scalable services delivery to the customers. It comes along with reduction of constraints in upgrading and variety of options to choose from including fast availability of the needed products or services. Rossi (2015) outlines the following factors: Actual automation designs are conducted from the previous automation of product to automation of the executing commands where the administrators are seamlessly become more of auditor of the automation system used in deployment of products and testing of the software that are released. The automation takes place in the creation of infrastructure are per the requirements of the software and also in the incorporation of orchestration tools used in automation. Chef and Puppet are configuring tools are becoming more popular are set to be more of advantage to automation systems. The tools facilitates the capabilities of the organizations to migrate to automated infrastructure. There tools facilitate acquisition of the better compiled codes for the installation of the applications to the servers of the organizations and business enterprises As automation is taking a new era, big organization are moving from competition in provision of automating tools and the infrastructure to even the best selling price of the particular services. These have prompted the organizations to provide more advance services at a cheaper price and better support services There is anticipation in the use of flash storage in a few years to come as opposed to the traditional storage in disks. The workloads are prompted to using utilizing the flash storage in the projection of supporting the infrastructure need of the particular organizations. Flash storage provide better opportunities to the business in storage of their organizational resources apart from the use in infrastructure automation. There have been a grown contradiction to the clients of cloud computing as the number of product that are provided in the service are so many and contain the same provision in terms of the services they produce. The market place has provided product that allow for sharing of the workloads in order to expand on the terminals to hosted settings drawing even more interest in the impact that outreach clients outside the setting. All these factors are consolidated together in order provide a strategic data centre I n some years to come. The flash storage is not viewed as just another tool in automation but its impact in the next generation to come and what the achievement could have been made from using these automation advancement in the infrastructure. The clients can take an advantage of the competition that is battled between the big service provides to suggest for better services and products at a cheaper price. References Rossi, B. (2015). 5 critical changes to IT infrastructure usage you should be aware of in 2015. Technology: Data Centre and IT Management. Retrieved from: http://www.information-age.com/technology/data-centre-and-it-infrastructure/123458866/5-critical-changes-it-infrastructure-usage-you-should-be-aware-2015 Lanning, B. (2015). Building a Scalable Infrastructure. Zorto, Blog. Retrieved from: http://www.zerto.com/blog/dr/building-a-scalable-infrastructure/ Eberlei, B. (2014). Why you need infrastructure and deployment automation https://qafoo.com/blog/065_infrastructure_automation.html Sabharwal, N. & Wadhwa, M. (2014). Automation through Chef Opscode: A Hands-on Approach to Chef. Book. Marschall, M. (2015). Chef Infrastructure Automation Cookbook - Second Edition.