![]() It is also the only space residing outside the Logical Volume Manager (LVM) The volumes will initially be sliced up as follows:īoot - This will remain static in size. This will allow the file systems (through automated scripts) to grow as needed and give the administrators some time to add more drives if necessary or shrink other volumes to get more space. ![]() The file systems will also not take up 100% of the logical volume. Filling up the root volume on a *nix system is a very bad thing and should be avoided at all costs. Pushing the other folders into their own volumes will be done so their dynamic growth will not affect the root partition. Isolating the root volume to mainly just static data that will not grow much over time is the central concern. Long-term life and growth of the system as well as budgeting concerns have to be taken into consideration. Being caught offguard with a scenario where space is filled up with no immediate option other than deleting files is never a good thing. ![]() This following design allows for dynamic growth and fine-tuning if need be. This documentation will focus on partitioning the drives in such a way that it allows for growth depending on what is needed for the specific application. The large decision over the configuration of Ubuntu is how the hard drive space is sliced up (partitioned). ![]() If professional support is needed, there is an option to buy support for the Long-Term Support (LTS) versions of the operating system. The Ubuntu Server Long-Term Support (LTS) is great choice for companies because it is a solid operating system that happens to be free. If not, you will need to beef up your skill set () or use a different editor in place of it. It is also assumed that the reader knows how to use the VI editor. NOTE: Ubuntu Forums does not allow me to use color tags in code blocks like on my forums so be careful about missing these placeholders based on color. Wherever you see RED in this document, you need to substitute it for what your company uses. This is just a checklist template you need to have answered before you start the install process. They are place-holders for the real thing. Under no circumstance should you use the actual values listed below. This variable data will be noted in this section and highlighted in red throughout the document as a reminder that you should plug-in your own value rather than actually using these "place-holder" values. This documentation will need to make use of some very-specific information that will most-likely be different for each person / location. The list below are sources of information that helped me configure this system as well as some places that might be helpful to me later on as this process continues. Portable PuTTY () 0.62 (0.63 was too buggy ()) This document will also cover some custom scripts to help automate tasks such as backing up, automatically growing the file system when free space is low, etc. Although there are some VMware-specific and VirtualBox-specific steps, they are very few and the majority of this documentation will work for other Virtual Machines or even directly installed onto a physical machine (e.g. Notes will also be supplied for doing the same thing for Oracle's VirtualBox on a Windows 10 PC. The server will be installed inside a virtual machine using vSphere running on ESXi servers. This will be the "base" installation of the server as a prerequisite for other documents that will build upon it (e.g. This document will cover installation of a dedicated Ubuntu server. Link to original post: HammondsLegacy Forums () (best when viewed at original location due to custom formatting) I hope this thread will be helpful to those who follow in my foot steps as well as getting any advice based on what I have done / documented.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |