Operating System and Docker Containers Coursework

Functions of Operating System

The purpose of this coursework is to introduce you to the functions performed by an operating system and, in particular, to give you practical experience of the associated command language, the file system facilities and Docker Containers.

On completion of this coursework, you will be able to:

(a) Use the facilities provided by a Linux-based system and particularly the file attributes and directory structures.

(b) Use the command line associated with a Linux-based system, including some commonly used commands and the widely encountered structures.

(c) Use Docker containers and their interaction mechanics.

(d) Appreciate the strategy associated with testing systems software and the need to build robust products.

(e) Understand and implement ‘best practice’ housekeeping procedures to prevent user/system misuse or mistakes.

As the book sales are going up, your publisher has asked you to deliver the book you promised a couple of years ago, and they are after your next bestseller. There is one problem, you have done nothing so far,and you need to save the day. The solution to your problem will be your knowledge of operating systems and Docker containers.

Instead of writing your bestseller, you have spent the past few years experimenting with Docker containers and scripts. Inside three of your Docker containers, you have stored several text files which were going to be used for your book. Somehow you need to arrange those filesand create a small book chapter so you can buy some time for yourself. Mother luck might be able to help you… but how?

Description

You need to use the scheduling algorithms as a tool towards your redemption, and your matriculation number will be the key for the algorithms to work. On Moodle, you will find three folders with text files inside them. The text files have random names. Each folder corresponds to each of the Docker containers you need to create. You have three folders, thus leading you to create three Docker containers and upload the content of those folders to them.

Your task is to assemble your texts in one unified text file. The technique that you are going to follow is Round Robin. To create your book chapter, you need to create your Final Book Chapter text file from all the Docker containers attached to your Linux distribution. Following the Round Robin algorithm that you learned fromscheduling, with quantum as two text files, you need to gather two files in each round from each Docker container and attach them to a Final Book Chapter text file. As an illustration, you need to collect the text of the first twotext files of your first Docker container, then the text of the first two text files of your second Docker container, then the text of the first two textfiles of your third Docker container, then the text of the third and fourth text files of your first Docker container, the text of the third and fourth text files of your second Docker container, the text of the third and fourth text files of your third Docker container etc. You should be careful as the number of text files is different for each Docker container.

Practical Experience of Command Language and File System Facilities

Taking a closer look at your text files folders, you will notice that their names are randomized, and you need an efficient way to tide them up. To achieve that goal, an efficient way is to rearrange them accordingto the size of their text files. You will use your matriculation number, which you are going to divide by three. If the remainder of the division is:

You will leave the files of your Docker container 1 intact (First Come First Served),

You will rearrange the files of your Docker container 2 with Shortest Job Next (first the file with the smallest length, then the file with the second smallest length, etc.),

You will rearrange the files of your Docker container 3 with Shortest Job Next (first the file with the smallest length,  then the file with the second smallest length, etc.)

You will rearrange the files of your Docker container 1 with Shortest Job Next (first the file with the smallest length, then the file with the second smallest length, etc.),

You will rearrange the files of your Docker container 2 with Shortest Job Next (first the file with the smallest length, then the file with the second smallest length, etc.),

You will leave the files of your Docker container 3 intact (First Come First Served)

You will rearrange the files of your Docker container 1 with Shortest Job Next (first the file with the smallest length, then the file with the second smallest length, etc.),

You will leave the files of your Docker container 2 intact (First Come First Served),

Rearrange the files of your Docker container 3 with Shortest Job Next (first the file with the smallest length, then the file with the second smallest length, etc.) You should develop scripts that achieve the described functionalities and present to the user what is happening at each time. For example:

Would you like to remove any text from Game of Dockers?

Would you like to add any text to Game of Dockers?

Would you like to terminate the program?

From the example, you can see that you also need to create a terminal user interface so you can help yourself with the chapter writing. Initially, the terminal user interface should reflect all the necessary steps that create the initial text. Soon afterwards, you should implement the option that lets the user read the textthrough the terminal user interface. The next option is for the user to search and remove text from the book chapter, and the last option lets the user add text to the end of the book chapter.

The communication between the user and the terminal is presented in an abstract way on purpose to give you the flexibility to design your script according to your taste.

Your script should cover all of these functionalities:

• Load the files to the appropriate Docker containers
• Create the final text according to the described algorithm
• Allow the text to be removed or added

Your script should contain comments that explain the functionalities that you have implemented. Along with your script, you should submit a documentation file (a word document). The documentation file will explain your work plan, and if necessary, code parts that you think are not clarified by your comments. The length of your documentation file should be at least 400 words up to 600 words. Without the documentation file, your coursework will not be marked.