Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've recently started a new position and I'm attempting to establish some best practices; specifically with CentOS/RHEL in vSphere 6.7. I'm trying to set up templates for Linux servers. However, I'm getting varying suggestions on the partitioning schemes.
I'm a bit overwhelmed and trying to keep all this straight. I want to establish a procedure, but I also want to make sure that the server is constructed with proper partitions for an Enterprise level Linux Server with full file structure and all the appropriate safety 'guard rails' that people sometimes forget to put in their partitions. I know that it's easier to just choose "automatic", but I prefer to do it the right way and then teach Ansible and Terraform how I want it done.
If anyone has some good experience with this and doesn't mind dumbing it down to my newbie status, I would be quite grateful.
I'd stick with automatic until you acquire enough experience to make a definitive decision that you completely understand. Because when you mention becoming overwhelmed, it gives me the impression that you're not going to be any less overwhelmed with an additional number of opinions from responders here. Also presuming that the opinions you're receiving now may be from co-workers who do set up servers for the same environment?
Use the tools provided. It's why they call it "enterprise". Varying advice because storage and best practices used to be different. Multiple devices to compensate for slow devices. Special allocations for high traffic things likely to break devices. And other concerns addressed by the filesystems that things sit on top of now. You should probably research those filesystems before trying to figure out space allocations. lvm2, zfs (ZoL), btrfs, xfs, ext4, and lots of other fs's like glusterfs.
I've recently started a new position and I'm attempting to establish some best practices; specifically with CentOS/RHEL in vSphere 6.7. I'm trying to set up templates for Linux servers. However, I'm getting varying suggestions on the partitioning schemes.
I'm a bit overwhelmed and trying to keep all this straight. I want to establish a procedure, but I also want to make sure that the server is constructed with proper partitions for an Enterprise level Linux Server with full file structure and all the appropriate safety 'guard rails' that people sometimes forget to put in their partitions. I know that it's easier to just choose "automatic", but I prefer to do it the right way and then teach Ansible and Terraform how I want it done.
If anyone has some good experience with this and doesn't mind dumbing it down to my newbie status, I would be quite grateful.
Agree 100% with rtmistler and Shadow_7. What you're essentially asking is, "How high is up?" Fact is, you are NEVER going to have a template that's a one-size-fits-all, because every server is different. You have to accommodate the needs of the users/application, not force things into a cookie-cutter mold...that will only cause you a gazillion other problems later.
For example, for an Oracle database server, you may not even FORMAT the disks, but leave them raw, and let the DBA's use the disks for the Oracle 'file system'. Any partitioning you do will just cause them headaches and more work. Got a server that does nothing but NTP and DNS? You can probably use whatever the installer suggests...not going to be challenging there. And once you get SAN's, RAID arrays, etc., etc., involved, who knows where it takes you? Rule of thumb years ago was to have swap twice the size of your memory....now, that'll probably just slow your system down, and be pointless.
A very special thank you to rtmistler, Shadow_7 and TB0ne. I'm so thankful to all of you for replying so quickly. I've been using Linux for years, but I don't consider myself to be anything more than a novice who is trying to become far more. Many principles and commands I have forgotten and it's very nice to know that there are many people here who are willing to help. I will be applying the guidance that you've all shared with me...particularly applying the "KISS" principle for now.
Maraming salamat po (many thanks, respectfully),
mvelezwhiteSBS
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.