Linux Implementation Proposal
The final submission should contain at least 5 to 7 pagesâ€™ worth of text written by the student (not counting title page, images, diagrams, tables, or quotations that may be used). It must be double-spaced, have 1-inch margins, and use 12-point Times New Roman or 10-point Arial/Helvetica font. A title page is required.
- Research and justify whether LSDG will use existing computer hardware that is being used with the Windows XP systems, or if new hardware will be required.
- Plan for migration from Windows XP to Linux.
- Determine the hardware to be used and the installation options.
- How will users log onto the systems? Explain.
- How will systems receive IP addresses? Explain.
- How will DNS be accessed by the LSDG systems? Explain.
- Explain how files on the network may be accessed by LSDG.
- Explain how LSDG can securely share files within their group and other selected groups/users in the company.
- How will printing be handled? Explain.
- What, if any, data will be encrypted? Explain.
Virtual Install Project Format and Content Instructions
Audience: Write your document for a team of implementers who need to retrace your steps.
2. Available resources. Oracleâ€™s virtualbox software is one free hypervisor you can install, but there are others. You are expected to research and install on your own. Then, in your document summarize a few key distinctions between the applications you found.
3. How to write this document. Write in the third personâ€¦ Each sentence you write is a statement of fact. â€œThis plan describes an implementation procedure for â€¦.â€ Not, â€œI am presenting this plan for your approval.â€ There will never be a sentence with â€œIâ€ or â€œweâ€; itâ€™s â€œa team has been formed toâ€¦.â€.
4. How to format this document.
a. APA cover page
b. Executive Summary. It should begin with â€œThis document describes â€¦deployment of a virtual hostâ€¦ onâ€¦â€. A senior exec could choose to not read beyond the executive summary if they understand that:
i. The project is well managed
ii. The project security considerations are solid.
iii. Risks are understood and mitigated
iv. No schedule impact or other resources needed
c. Security Planning. Browse through NIST SP800-125 and reference appropriate sections. Just a few sentences is adequate.
d. Technical Details. Screen captures are great here, but donâ€™t go crazy.
i. Computer Host specs (brief). This is the computer you installed the virtual machine on.
ii. Virtual software options, highlights.
iii. Virtual software install procedure.
iv. Linux OS install procedure.
v. Linux administration procedures. Cite a good reference here. As a minimum include these:
1. User password policy.
2. IP Address assignment.
5. Disk utility.
i. Your thoughtsâ€¦
ii. Capabilities and limitations of a VMâ€¦
iii. How you will apply what youâ€™ve learnedâ€¦
f. Recommendations for Further Research.
Format and Content Instructions for Linux Implementation Proposal
1. What this assignment is: it is an implementation plan that you create. You are the team lead and you are writing a plan to your corporate staff, the ones who funded this project and told you to get rid of XP.
2. How to write this plan. Your academic writing experience will not tell you how to organize a document like this, so I will help you.
a. Each sentence you write is a statement of fact. â€œThis plan describes an implementation procedure for â€¦.â€ Not, â€œI am presenting this plan for your approval.â€ There will never be a sentence with â€œIâ€ or â€œweâ€; itâ€™s â€œa team has been formed toâ€¦.â€.
b. Audience: there are 2 significant stakeholders that you need to consider for this task:
i. The management: they hired you to solve a problem for their business operations. Show confidence, or conversely raise the red flag that the job has risk, then state the risk and your recommendation. Assume you have a budget; it has not been set for you. Pick whatever number you want.
ii. The departments: they run their current XP applications, like MS Office and accounting software and maybe graphics and others. Use your imagination, you can even fictionalize the name of the software, just pin it to a department. You are taking away their software to run something else on linux. Have a little empathy for them. This means that if they are part of the evaluation and selection process. State this right out front, even in the Executive Summary.
3. How to organize this document. This is what your corporate staff wants from you:
a. Executive Summary. Start with â€œThis document describes an implementation plan to replace â€¦XP machinesâ€¦â€
b. Project Schedule (include a GANTT chart)
d. Technical Details
i. Hardware â€“ do not use the minimum hardware specâ€™d for linux; you can summarize the old specs in one sentence and then use a table to state your new CPU/RAM/Disk/monitors/video cards.
Your specâ€™d out new hardware should scale and support your organization for several years.
ii. Software. Specifically mention linux replacement software for Microsoft; example: LibreOffice
e. Risk Management (NIST SP800-53 and SP800-37 are good for a few sentences)
g. Testing and Acceptance Criteria
h. Fallback Plan
i. Conclusion- your conclusion should almost restate the exec summary.
4. The rubric. Itâ€™s right there as a pop-up window on the same page as this document and the assignment. I grade to this rubric. Key points:
a. The most points are in the coverage of the plan, the hardware and the security measures. You absolutely, cannot accept the minimums that will run the OS and nothing else.
b. For security, make some references to NIST SP800-53
c. Mechanics cited there in the rubric. You know what to do. Read them one more time; youâ€™ll need in-line citations, properly formatted.
d. The list of technical items in the Implementation Proposal document (user log on, IP addresses, DNS, accessing files,â€¦) can be mentioned briefing in a bullet list to satisfy the rubric, no need in your proposal to
go into detail or provide command line examples.
a. Use just one sentence to say that management has funded the replacement of XP. There is no need to ramble on about why; we all get it.
b. Add a GANTT schedule (look it up if you donâ€™t know what this is). c. You have to contribute details about the migration task. This means that you have to use your own imagination. Do not just echo back the assignment, you will receive a very low score for your proposal if you do this.
d. Consider how you will stage the migration of hardware and data. Staging means creating an installation template and making it reproducible.
e. Consider a fallback plan. Hereâ€™s a good ideaâ€¦.. keep a stand-alone XP box in each department that they can sneakernet (look it up) their files.
f. The hardware specs given to you in the Proposal document are misleading. Specify processors, RAM, disks and monitors that will run your applications. Trying to save $$ makes not one bit of sense. Scale your operations for several years out from now. If you echo the minimum specs given to you, you will not receive a passing score. Weâ€™re talking RAM, disk, CPU cores, some I/O and decent size monitor with a video card to drive it.