Virtualization and Cloud Computing

Questions: The Department of Spatial Information (DSI) has considered your assessment of the deployment model, risk management and security issues for the Online Spatial Delivery System (OSDS). They have decided that they need an additional assessment on the technical management and the SLA. You have been assigned the task of providing DSI Executive Management with an assessment of the management requirements and the provisions of the SLA for the chosen cloud vendor. You are to: 1. Discuss the requirements for remote administration, resource management and SLA management. It may be useful to consider Morad and Dalbhanjans operational checklists for DSIs OSDS. This section should be no more than two to three pages in length. 2. Discuss briefly how you will consider application resilience, backup and disaster recovery for your chosen provider in relation to OSDS. This section should be no more than two to three pages in length. 3. Use Erls SLA guidelinesto assess the SLA for your chosen provider. This section should be no more than two to three pages in length. 4. Provide a covering one to two page executive summary of these two assessmentsto DSI Executive Management and summarise the major opportunities and risks that have been identified in your assessments. Answers: 1. Introduction: The study comprises of the demonstration and analysis of the remote administration, SLA and resource management. The study also holds the requirements of SLA, resource management, and remote administration. The requirements of each entity are very crucial to setup the cloud computing specifically. The provider installs a portal for establishing a remote administration (Li et al., 2014). Service Level Agreement or SLA refers to the agreement which comprises of the information that both the provider agreed upon in terms of providing service, integrity, and loyalty (Garg, VersteegBuyya, 2013). Hardware, software, deployment model together refers to the resources of a cloud computing service. On the basis of this resources, the flexibility and capability of the consumer's system are calculated (Schiffman et al., 2013). 2. Remote Administration: The basic responsibility of remote administration is to provide approved services. The consumer gets the service not directly through the cloud system rather the installed portal provides the cloud services to the client organization. So from the above statements, it is clear that the remote administration gets installed in between the cloud service and the customer (Erl, PuttiniMahmood, 2013). The primary underlying work of the remote administration is to provide agreed SLA services and resources. The usage and administration portal are the main keys to managing the resource. In addition, those portals are also coming under the category of requirements. Deployment, delivery, remote administration systems interface and the granted level of access control are the things that are required for establishing the remote administration system (Schiffman et al., 2013). 2.1 Requirements: The requirement for successfully installing the remote administration system are described in the following points. As per the demand, release and delivery of IT and other resources. Properly keeping track of performance and status of services. In addition, monitoring the usage is crucial (Sookhak et al., 2015). The client organizations selected delivery and deployment model. The process of choosing the deployment and delivery model is crucial as it can never be changed. Monitoring the QoS or quality of service and service level agreement is also another vital requirement (Schiffman et al., 2013). Choosing the interface that is suitable remote administration system needs. The required interface in terms of the management system (Erl, PuttiniMahmood, 2013). Allowing the agreed access control (Sookhak et al., 2015). 3. Service Level Agreement or SLA: The Service Level Agreement is stored as a document which holds the terms and condition that both the provider and client approved while signing the service initiation (Garg, VersteegBuyya, 2013). It will also provide the opportunity to DSI to change the provider if it feels not satisfied with the provided service. Also, DSI can claim damage. The data identified with accessibility, security, compactness of the information, exercises of deciding the issues, intervention debate procedure and a great deal more will be recorded through the SLA or administration level understanding (Gill, 2015). 3.1 The Service Level Agreement Requirements: What information and activity are exactly required for creating service level agreement are as following. A quality of service or QoS's metric and brink. The continuous and reliable performance of SLS is very essential (Garg, VersteegBuyya, 2013). Adding on-demand video as well as the unified message, services of next generation, in the cloud. The information regarding the divided responsibilities of the client and provider. Control, guaranties, discount, definition, reporting and validation about service decay (Latif et al., 2014). The administration is estimating and marking down approaches to be useful if the SLA people group are not satisfied (Garg, VersteegBuyya, 2013). 4. Resource Management: From the above statements the concept of resources that are used in the cloud services has already been clarified. Now the management is all about increasing or reducing the resources as per the need of the client organizations current business (Sookhak et al., 2015). Suppose, the workload of DSI is very high, and it needs more storage then the provider will allocate more storage hardware to DSI cloud service. 4.1 Resource Management Requirement: The adequate information of selected activities that DSI needs to do through the cloud system. In addition, the information of selected backup and disaster recovery plan (Schiffman et al., 2013). For assigning the required resources, the information of the processes is required. The quality of service that DSI intends to have from the provider. The requirement also depends on upon whether DSI chooses SaS, PaS or SaS (Sookhak et al., 2015). 5. Data Backup with RAID 10: For string, the data as a backup the DSI will go for the RAID 10. It is obvious that being a government department, and the data loss will be a huge issue. So, in any case, DSI must protect its data. In addition, the performance factor is also very crucial in this case. So from the requirements, it is clear that the RAID 1+0 will be the best option for DSI to store its data as backup. RAID 10 has incorporated both the concept mirroring and stripping (ShenShu, 2014). Through mirroring, it saves all the gathered into a separate section so that is the running disk gets damaged then the data stored in the separate disk can be used for retrieving or repeating the storage process. The stripping is the process through which the storage and the retrieving process get quicker (Tadros et al., 2013). In terms of redundancy, the RAID 10 is also very flexible. DSI will need at least fifty storage disks for storing the departments data. The data in the RAID 10 will be stored in chunks and retrieve d as a whole (ShenShu, 2014). 6. Resilience: The continuous development of IT resources into the physical location is called as the Resilience Computing. The resources of the information technology that DSI will use will be pre-configured (JhawarPiuri, 2013). The resources are pre-configured as the activities of the running tasks may be allocated to another redundant IT resources. All the concern regarding the resilience gets involved in the project at the time of planning and scheduling. The resilience also describes the capacity of the system which refers to individual entities of the system. The entities have a connection with the provider's or third party disaster and disaster recovery deliberations (JhawarPiuri, 2013). As the data must also need to be stored for backup and disaster considerations. 7. Disaster Recovery: The disaster recovery planning will be conducted in five consecutive phases. Information Safety needs: The essentials of DSI will be accumulated at this stage. The gathered information will be key in choosing the segments that will empower cloud based data security. The need of protection is essential because the data will travel from DSI to Cloud server through the internet (Aldrich, 2012). Choosing the cloud provider: The provider has been already chosen. Calculating the required capital: The cost of the activities will be given to the organization gave either by month to month enrollment, the measure of VMs, web transmission limit, and storage space (Sahebjamnia, TorabiMansouri, 2015). At the cost estimation time, DSI and provider will focus I the periods were DSI will need to increase and reduce resources. Developing bandwidth management plan: In this movement, the organization of the web information exchange limit regarding the OSDS requirements will be finished (Chandra et al., 2013). The more the transmission capacity, the more the solid and recovering procedure will be. Logistics necessity identification: For performing hard and fast failovers to the cloud DSI will consider a couple of logistics necessities while doing the logistical masterminding. The requirements are powerful registry synchronization and cloud based list organizations (Sahebjamnia, TorabiMansouri, 2015). 8. Service Level Agreement: Cloud service level provider and DSIs service level agreement comprise of various information some have been discussed earlier, and some are stated here. First, the adequate and exact recognition and definition regarding particular constraints that are to be used in the cloud system of DSI. Second, the architecture of the DSI's cloud system (Garg, VersteegBuyya, 2013). The architecture will be the base of the whole system, all the processes, and transaction of information will be carried out based on the designed architecture. Third, defining the privileges regarding retrieving the information from the server. Fourth, creating and defining the rights for administrating the component (Latif et al., 2014). Fifth, the steps to be taken against provider or consumer if they break any regulation. Sixth, the information that both of them agreed upon regarding quality, availability, and integrity (Garg, VersteegBuyya, 2013). The use of the Erls SLA guidelines have done in the following way. Customer based SLA: The provider makes a concurrence with the clients bunch (Colman-Meixner et al. 2015). This affirmation is done between the supplier and additionally fund office for the administrations, taken as an example, money framework, finance framework and additionally a charging framework. Service based SLA: It is conformity for every one of the customers utilizing the administrations that are given by the administration suppliers. Corporate level SLA: It covers every one of the SLA issues that are precise to each of the clients through the association (Newcombe et al. 2015). Customer level SLA: It covers every one of the SLA issues that are precise to each of the clients through the association (Newcombe et al. 2015). Service level SLA: It covers every one of the SLA issues that are particular to the administrations, for example, client bunches (Janiesch and Niemann, 2012). Observing, and in addition providing details regarding the cloud execution, depends on the experience of the end client capacity with a specific end goal to expend the assets. 9. Conclusion: From the above study, I can be concluded that the concentration of DSI must be on choosing the resources as per their system. The remote administration is the key to managing the various systems authorization to the resources. Resilience refers to the need of the resources regarding the organizations cloud system. SLA will be the key to keeping both the provider and consumer loyal to each other. The data recovery is also important as the information of DSI will be stored in the cloud and it may get removed or corrupted. In that case, data recovery come into use. As DSI will be using the RAID 10, the data will be more secure and the performance of data storing, and recovery will get increased. The disaster and data recovery are not much different from each other but in disaster recovery, DSI will get more safety regarding the information. The adaptability is just the shrouded thought under fortification and catastrophe recovery supplier's structures limit. References: Aldrich, D. P. (2012).Building resilience: Social capital in post-disaster recovery. University of Chicago Press. Azevedo, L. G., Diirr, T., Baio, F., Santoro, F. (2014). A Business Model for Managing SOA Initiatives.iSys-Revista Brasileira de Sistemas de Informao,7(1), 4-33. Chandra, A., Williams, M., Plough, A., Stayton, A., Wells, K. B., Horta, M., Tang, J. (2013). Getting actionable about community resilience: the Los Angeles county community disaster resilience project.American journal of public health,103(7), 1181-1189. Colman-Meixner, C., Develder, C., Tornatore, M., Mukherjee, B. (2015). A Survey on Resiliency Techniques in Cloud Computing Infrastructures and Applications. Erl, T., Puttini, R., Mahmood, Z. (2013).Cloud computing: concepts, technology, architecture. Pearson Education. Garg, S. K., Versteeg, S., Buyya, R. (2013). A framework for ranking of cloud computing services.Future Generation Computer Systems,29(4), 1012-1023. Gill, S. S. (2015). Autonomic Cloud Computing: Research Perspective.arXiv preprint arXiv:1507.01546. Janiesch, C., Niemann, M. (2012). Supporting USDL by a Governance Framework. InHandbook of Service Description(pp. 415-444). Springer US. Jhawar, R., Piuri, V. (2013). Fault tolerance and resilience in cloud computing environments.Computer and Information Security Handbook,, 125-141. Kruse, D. F. (2014). The repack challenge. InJournal of Physics: Conference Series(Vol. 513, No. 4, p. 042028). IOP Publishing. Latif, R., Abbas, H., Assar, S., Ali, Q. (2014). Cloud computing risk assessment: a systematic literature review. InFuture Information Technology(pp. 285-295). Springer Berlin Heidelberg. Li, T., Keahey, K., Sankaran, R., Beckman, P., Raicu, I. (2014). A cloud-based interactive data infrastructure for sensor networks.IEEE/ACM Supercomputing/SC,14, 14-15. Newcombe, C., Rath, T., Zhang, F., Munteanu, B., Brooker, M., Deardeuff, M. (2015). How Amazon web services uses formal methods.Communications of the ACM,58(4), 66-73. Sahebjamnia, N., Torabi, S. A., Mansouri, S. A. (2015). Integrated business continuity and disaster recovery planning: Towards organizational resilience.European Journal of Operational Research,242(1), 261-273. Schiffman, J., Sun, Y., Vijayakumar, H., Jaeger, T. (2013). Cloud verifier: Verifiable auditing service for iaas clouds. InServices (SERVICES), 2013 IEEE Ninth World Congress on(pp. 239-246). IEEE. Shen, Z., Shu, J. (2014). Hv code: An all-around mds code to improve efficiency and reliability of raid-6 systems. InDependable Systems and Networks (DSN), 2014 44th Annual IEEE/IFIP International Conference on(pp. 550-561). IEEE. Sookhak, M., Gani, A., Talebian, H., Akhunzada, A., Khan, S. U., Buyya, R., Zomaya, A. Y. (2015). Remote data auditing in cloud computing environments: a survey, taxonomy, and open issues.ACM Computing Surveys (CSUR),47(4), 65. Stankovski, V., Taherizadeh, S., Taylor, I., Jones, A., Mastroianni, C., Becker, B., Suhartanto, H. (2015). Towards an Environment Supporting Resilience, High-Availability, Reproducibility and Reliability for Cloud Applications. In2015 IEEE/ACM 8th International Conference on Utility and Cloud Computing (UCC)(pp. 383-386). IEEE. Tadros, G., Salama, R. A., Kingston, P., Mustafa, N., Johnson, E., Pannell, R., Hashmi, M. (2013). Impact of an integrated rapid response psychiatric liaison team on quality improvement and cost savings: the Birmingham RAID model.The Psychiatrist Online,37(1), 4-10.