Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
Module Code: CMT654
Module Title: Dev Ops
Assessment Title: Portfolio Assessment Number: 1/1 Date Set: Wk 3 Submission Date and Time: Thursday 3rd June 2021 (Week 12) at 9:30am. Additional Demo of Pipeline in class Week 11. Feedback Return Date: Friday 1st July This assignment is worth 100% of the total marks available for this module. If coursework is submitted late (and where there are no extenuating circumstances): 1 If the assessment is submitted no later than 24 hours after the deadline, the mark for the assessment will be capped at the minimum pass mark; 2 If the assessment is submitted more than 24 hours after the deadline, a mark of 0 will be given for the assessment. Your submission must include the official Coursework Submission Cover sheet, which can be found here: .pdf Submission Instructions All submission should be via Learning Central. The submission page can be found under ‘Assessment’ in the CMT654 module on Learning Central, and will be available shortly after the contact session in Week 5. The current electronic coursework submission policy can be found at:pdf Your submission should consist of a single .zip file, which should be named [student number].zip containing files as detailed below. Description Type Name Cover sheet Compulsory One PDF (.pdf) file [student number].pdf Scripts Compulsory All scripts associated with the deployment pipeline and other parts of the coursework. These must be within a zipped folder named Scripts Scripts.zip Report Compulsory Report with 3 sections: 1) Pipeline Report 2) Performance Report 3) Research Report Report_[student number].pdf Any deviation from the submission instructions above (including the number and types of files submitted) will result in a reduction in marks for that assessment or question part of 50%. There will also be an in-class demonstration during Week 11’s session where you will be required to demonstrate your working pipeline. Assignment This is an individual assignment. There are no aspects of team submission. For the purposes of this assignment, you will be working with the Spring Boot Client Application that you worked with last semester. This assignment will not assess the Client Application’s functionality. You may use any branch from the Client Application to start from and if you really believe that using your Client Application rather than another team’s will put you at a disadvantage please come and see me. The work is split into four related sections: 35% Deploy your application to the School’s Open Stack cluster, creating a repeatable process (scripted) that creates a Debian test environment and uses Jenkins to pull your project from your Gitlab repository and trigger a build and test of the application. The pipeline should include the build, installation and configuration of all required software to enable the application to run and to enable the application to be tested according to Dev Ops best practices. The pipeline should leave the application running on a server and accessible via a browser via the University’s network. During an in class demonstration session (week 11) you will be asked to open and run the application in the Dev environment (Intelij) make a simple change to the project, push that change to Gitlab and then demonstrate the deployment pipeline. 25% Write a brief report (1000 words) on your pipeline discussing the decisions behind creation of the environment, the testing schedule and the resources used (e.g. web sites used to find instructions). In this report, you should reflect on your choice of methods used in the construction of the pipeline. You should also reflect on the use of the pipeline during the week 11 exercise and it’s limitations. 15% Run performance analysis on the deployed project using a range of appropriate tools. Produce a report (300 words) on your findings detailing your methods, what they hope to show and showing screen shots of tests you have run. 25% Research report on Deployment of Project to the AWS platform (1500 words): Your company is negotiating for VC investment for a rapid expansion. Your OpenStack server is now running out of power for the increasing client base and the application is rapidly expanding its feature set. Your company wishes to migrate to an AWS offering. Write a recommendation on the technologies that you will use, discussing the options and the justifications for your choice. Considerations for: Cost, Reliability, Security, Best Practice, Lock-in and Agile Development should all be discussed. Learning Outcomes Assessed 1. Use and troubleshoot a range of leading-edge DevOps tools for continuous integration (i.e. automated building, packaging, testing and deployment), and justify the rationale for doing so. 2. Use a range of Cloud tools and platforms, critically appraising the benefits of their use. 3. Use of a range of appropriate tools and techniques to measure performance of various system components, and investigate issues. 4. Scale real systems to obviate performance issues, and overcome resource constraints critically analysing the rationale behind design decisions with respect to Reliability, Availability and Performance. 5. Discuss security implications of cloud solutions, utilising mechanisms to mitigate their effects. Criteria for assessment Credit will be awarded against the following criteria. Assessment Criteria Fail (<50%) Pass (50% - 59%) Merit (60% – 69%) Distinction (>69%) Pipeline 35% (As assessed at the demonstration and via submitted scripts) Scripts fail, Application not running Automated pipeline with, attempt at testing. Application running on open stack. Automated pipeline with, appropriate testing (per lectures). Application running on open stack. Fully automated pipeline with, comprehensive, appropriate testing Application running on open stack. Exploring concepts mentioned but not explicitly taught in sessions. Pipeline Report 25% Report shows no understanding of why chosen approach was used. No effort at reflecting on own work. No Reflection on pipeline use. Report shows understanding of why chosen approach was used. Limited reflection on own work. Limited reflection on pipeline use. Report shows understanding and reasoned justification of why chosen approach was used, with knowledge of alternatives. Reasoned reflection on own work. Reasoned reflection on pipeline use. Report shows understanding and reasoned justification of why chosen approach was used in comparison to other approaches. Reasoned reflection on own work with justified suggestions for future improvement. Reasoned reflection on pipeline use tying in to suggestions for future improvement. Performance Report 15% Performance Report gives no evidence of Performance Report gives evidence of tests Performance Report gives evidence of appropriate tests Performance Report gives evidence of, comprehensive, Feedback and suggestion for future learning Feedback on your coursework will address the above criteria. Feedback and marks will be returned by Friday 1st July via email. Feedback from this assignment will be useful for the Dissertation. appropriate tests being conducted. No effort at analysing results. being conducted. Evidence of results analysis. being conducted. Evidence of critical analysis of results. appropriate tests being conducted. Evidence of critical analysis of results discussing realistic limitations. Research Report 25% Report shows superficial research into available offerings and how they could relate to the current deployment. Report details research into offerings that could be used, with limited discussion of how current methods, working practices and scripts could be migrated to the new platform. Report details research into different offerings that could be used, with discussion of how current methods, working practices and scripts could be migrated to the new platform Report details research into offerings that could be used, evaluating options and their benefits. Report has detailed discussion and scripts showing how current methods, working practices and scripts could be migrated to the new platform. Considerations that will affect your marks: The report must be professionally presented and references, with citations, must be used both to credit the ideas of others and to back-up your arguments. (This does not preclude the university’s procedure on academic misconduct).