The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Confiiguration Manamgent & cPanel/WHM

Discussion in 'General Discussion' started by OffbeatAdam, Jul 15, 2009.

  1. OffbeatAdam

    OffbeatAdam Active Member

    Joined:
    Jan 24, 2006
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    San Antonio, TX
    Greetings,

    I'm deploying Puppet (similar to cfengine) within our infrastructure to better maintain our servers as well as make new-server deployment and management much faster (through the additional use of a pxe kickstart system of course).

    Unfortunately this lends the habit of controlling configuration files under the /etc directory and under many other locations (the home directory for administration users, for example).

    Is there a readily available list of primary OS files - for example, /etc/passwd, that would be best ignored by puppet (or maintained in a different fashion?)

    Obviously in a shared hosting environment I won't be maintaing users across the infrastructure, so /etc/passwd is merely an example.

    Thanks!
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Our technical analysts can provide you with this information: http://tickets.cPanel.net/submit
     
  3. OffbeatAdam

    OffbeatAdam Active Member

    Joined:
    Jan 24, 2006
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    San Antonio, TX
    This just doesn't seem to be a very well thought out response to me.

    My question, at least I feel, would be a relatively valuable piece of information to anyone else who may be attempting to do the same thing. I've searched the forums and found in the past very little information related to this.

    I know that it is relatively recent for cPanel to give useful information to its users through the use of even something so simple as a changelog, but it would seem to me that it would be relatively smart and, well, less time consuming on your hands to give a simple listing of files within /etc/ that cPanel is concerned with rather than have someone submit a ticket to have a response written by a developer many times over.

    Seems inefficient to me, and well, I thought thats why forums and wiki's, as well as the ability to search, were invented... so that information need be typed but only once?

    A simple file listing doesn't seem too much to ask to require me to log in and submit a support ticket - something which I'm sure support has some more important things to deal with (rather than encounter a full support ticket with what I would assume is higher urgency and therefore possibly impacting someone who, may or may not, have a more urgent issue than something of mere curiosity).

    Believe you me, I have absolutely no hesitation in just simply loading up puppet and breaking cpanel for a few weeks while I figure it out for myself - because for such a menial piece of information I refuse to open a support ticket.
     
  4. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    I agree, it initially seems most practical to post this information to the forums so everyone can have this information and free up the ticket queue from requests for this information.

    However, as this information is always changing, it is best to contact our technical analysts whenever this information is needed so whomever seeking this information receives the most updated and accurate information available. It would be a bad experience for someone to review this information later, acquiring outdated information and perhaps break their production web server in the process. This would create a bigger headache than simply asking for the information via a support ticket when it is desired.
     
  5. moonsoft

    moonsoft Member

    Joined:
    Nov 10, 2004
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Support ticket

    I guess I don't see why you would be worried about posting it in a forum the level of information he is asking for should prove that this is not some SIMPLE question, and the the person searching for it would probably be smart enough to determine if this would apply to thier version of Cpanel.

    This is indeed worthy information for the PUBLIC, not everyone out there will "break" thier production server, especially since this is relating to PXE it wouldn't BE a production server if you are working with PXE

    Please post this info, or create something where users can find a repository of files that cpanel rebuilds, that you have to check changes into, and thus if were editted outside of cpanel would not keep the changes.

    Cpanel is built wholely on integration and EASE, so please just post the info here and make it easy...
     
  6. thepatriot

    thepatriot Member

    Joined:
    Jun 16, 2006
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    I agree. I would like to not have to always submit support tickets for this type of info. In the good old days you could search the forum and find answers to problems but at present more and more threads end with "submit a support ticket" with no specific details...
    On the flip-side to this you guys (cpanel) are doing a much better job at providing stable/tested updates - so the servers require much less back-end tinkering from admins.
     
  7. cPanelGregK

    cPanelGregK Administrator
    Staff Member

    Joined:
    Sep 8, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    This is a tough one to answer, and depends on the level of control you're going to be implementing on your cPanel servers. I have puppet currently managing a number of servers, but haven't written modules for cPanel as of yet. If you could let me know what types of rules you're going to be using (i.e. file content rules, file permissions, ownership, etc), I'd be happy to do some testing and report back to the forums.
     

Share This Page