Learning Outcomes assessed:
3. Formulate scripted solutions to automate operating system services.
4. Implement practical solutions based on the client/server model to solve a given problem.
Scenario
You have recently begun a graduate internship in SysOps for a cloud provider – CloudAnywhere. Their operating system platform infrastructure is Linux-based and uses hypervisor technologies to dynamically deploy Virtual Machine applications as and when needed by clients.
CloudAnywhere has advertised a permanent position. The chosen candidate should be capable of configuring and implementing client/server applications, skilled in scripting and should have a good working knowledge of operating systems utilities. Accordingly, they have provided a series of tasks to test your competence in shell scripting, requiring: appropriate use of programming constructs including sequence, selection and iteration; and effective use of built-in utilities including pipe, tail, grep, sort, awk, echo and sed.
Instructions
There are five (5) tasks. To support your evidence, incorporate relevant screenshots of scripting code (with embedded comments) and corresponding annotated screenshots of scripts in execution. Include your final script in your report and a create screencasts of your testing process.
You need to demonstrate your program and explain how it works during the practical session during your lesson. No demonstration means zero mark.
Task 1 of 5 – Resource Monitoring Application [25%]
CloudAnywhere recognises that built-in OS resource monitoring tools are functional but are neither very intuitive nor focused for their requirements. To address this, you have been tasked to script a bespoke application to display the following details in real-time with a 1 second refresh rate:
• Host name
• Kernel version
• Number of tasks running
• System up-time
• Total and available RAM
• Total CPU usage
• Total and available disk size
• Process details including:
PID
User
%CPU %RAM
process command
Task 2 of 5 – New User Automation Tool [25%]
CloudAnywhere has mentioned that their current process for adding new users is inefficient. They have now developed a web-based system that allows clients to bulk-upload users’ details which then creates a text file on the server with new user information.
They have asked you to script an automated solution which periodically checks for new user information files and adds users. Results should be documented in a separate time-stamped log for audit purposes.
Task 3 of 5 – Audit Log [20%]
CloudAnywhere recognises the importance of security and would like a logging tool for audit purposes. Script a solution that will document/log:
• Start time and end time of user session
• User details
• Process details
• Process end time
• Process start time
• PID#
Task 4 of 5 – File Size Monitor [10%]
CloudAnywhere has had instances where performance has degraded as a result of file system space deficiencies. Consequently, they have asked you to script a solution that will continuously monitor the file system and send a notification to administrator when resources are 50+% utilised.
Task 5 of 5 – FTP Server [20%]
CloudAnywhere would like to store log files on a dedicated server for later analysis and have suggested using FTP. The SysOps team has allayed concerns regarding the security implications linked to the use of FTP. They have explained that all servers involved will be behind the organisation’s firewall, so the concern of Man-in-themiddle attack is reduced; furthermore, data that is being transferred is not of a sensitive nature so encryption is unnecessary.
Implement a FTP server showing all steps including installation, configuration and testing. Additionally, script an automated process demonstrating copying a log file (text file) from one server to another at a specified interval.
Formatting requirements
• A title page identifying the programme name, module title, assessment title, student ID, marking tutor and the date of submission must be included.
• Your Student ID number should be placed in the header section of each page.
• Page numbers should be inserted in the centre of the footer section of each page.
• Font style used should be either Arial or Calibri Light. Font size should be 12. Text should be doublespaced.
• The Harvard referencing format must be used to credit secondary research sources. In-text citations should be included within your discussion (where relevant) using the author-date format and full reference details should be included in your bibliography. For further details, click here.
• A Table of Contents should be included.
• All diagrams should be captioned and referred to within your discussion.
• You should include a word-count at the end of the assessment section where a word count applies. This should exclude references, figures and appendices.
Word limits
Where a word limit is specified, the following penalty systems applies:
• Up to 10% over the specified word limit = no penalty.
• 10 – 20% over the specified indicative word length = 5 marks subtracted (but if the assessment would normally gain a pass mark, then the final mark to be no lower than the pass mark for the assessment).
• More than 20% over the indicative word length = if the assessment would normally gain a pass mark or more, then the final mark will be capped at the pass mark for the assessment.
Submission
Please submit each completed task to the relevant Turnitin assignment submission section on the Moodle course page.
Issues with submission
• Unless otherwise notified by your Module Tutor, electronic copies of assignments should be saved as word documents and uploaded into Turnitin via the Moodle class area. If you experience problems in uploading your work, then you must send an electronic copy of your assessment to your Module Tutor via email BEFORE the due date/time.
• Please note that when you submit your work to Moodle, it will automatically be checked for matches against other electronic information. The individual percentage text matches may be used as evidence in an academic misconduct investigation.
Grading
A percentage mark will be provided based on General Assessment Guidelines for Written Assessments. Grading is as follows:
A: 70 – 100%
B: 60 – 69%
C: 50 – 59%
D: 40 – 49%
Marks below 40% will be classed as fail.
The post automate operating system services appeared first on My Assignment Online.