Automating web server deployment

I locate i am frequently setups up virtually virtually the same web servers and also VPSs for a variety of my customers and also it can be really time consuming. Usually the only point that transforms in between each deployment is the various internet site that is to be offered. Exists a very easy means to automate all this and also take the monotonous uniformity of establishing 56 the same web servers?

The web servers i have actually released until now have actually just been Ubuntu, yet it might be feasible that i start to make use of various other linux OSs or perhaps Windows. Until now i have actually considered Capistrano, yet it appears to be concentrated on creating little ruby programs to do the work with, and also i have no expertise in all

0
2019-05-06 23:07:29
Source Share
Answers: 7

For automating installment relying on the target system :

  • Debian/Ubuntu : FAI or d - i preseeding
  • RedHat/Fedora : Kickstart
  • Novell/openSuSE : AutoYaST
  • Solaris : Jumpstart
  • Windows : unattended.sourceforge.net

For the arrangement monitoring in addition to that I would certainly recommend making use of creature.

0
2019-12-04 07:36:54
Source

I've had success with Puppet. Chef is a new one to arise. For a much longer checklist of alternatives and also a contrast graph, see the Wikipedia write-up, Comparison of open source configuration management software .

0
2019-12-04 04:41:09
Source

Another choose Puppet below. We utilize it thoroughly to execute all web server and also application installment and also arrangement monitoring. 200+nodes and also checking. Windows assistance is evidently in growth, though in what state I'm not exactly sure.

We are still checking into the first OS bootstrap side of points, yet as stated over Cobbler looks intriguing. We are presently making use of a mix of PXE starting with Debian/Ubuntu preseeding, yet it is rarely optimum.

0
2019-12-03 05:45:08
Source

Where I am operating at the minute, we need to take care of the Linux section of our web server ranch which is simply over 300 Linux web servers. This consists of primarily HP Proliants, adhered to by IBM 3850s, some IBM blades, VMware ESX, and also some KVM for our inner monitoring web servers.

cobbler

We considered cobbler yet the trouble there was that cobbler is really RHEL/Red Hat details. We require to sustain RHEL and also SLES at the least, and also Ubuntu is next.

creature

We did take into consideration creature, nonetheless later on determined versus it as it relies on Ruby, which suggests that an upgrade of Ruby, can possibly damage our monitoring system.

hotwire

Hotwire is what we make use of (created inside, yet is open - resource), and also have actually done so for the last couple of years. It to start with supplies the systems that are mosting likely to be constructed, which suggests inventorying the information - facility, shelf, equipment, running system, network, etc, and also second of all execute the quick construct & release. As soon as the system is constructed, hotwire is vehicle - supply maintains the supply in - sync, while cfengine keeps them. Hotwire finds out about the web server equipment by talking with the SMBIOS/DMI information in the Bios using python-dmidecode.

The incentive factors are that it is incorporates the supply and also construct procedure right into one, so there is much less to take care of, and also the real-time - supply attribute is wonderful as we understand if something is not fairly appropriate.

The negative aspects are that the customer - user interface still requires sprucing up, and also there are pests occasionally, yet growth is still warm, and also pests reported are dealt with reasonably quickly.

cfengine

We make use of cfengine due to the fact that apart from it, and also creature, there is absolutely nothing else. It in fact is an excellent device, yet "good" just as a function of just how excellent your plans are - if you set unsafe plans, after that a tiny blunder can create alot of damages. As an example, by plan, we do not "modify" documents, we either change them, or we do not. Additionally all documents changed have a header that makes anybody editing and enhancing it recognize that it will certainly be changed the next time it runs (it is run using cron per hour).

The arrangement and also all documents pressed out by cfengine to the web servers are additionally maintained in a SCM, and also making use of blog post - devote hooks, where feasible, we examine the syntax and also if that falls short, after that the devote is denied. This is very easy for wonderful applications such as Apache, yet not so very easy for the majority of venture applications.

0
2019-12-03 05:16:10
Source

We usage Cobbler and also Puppet for construct and also arrangement automation of both actual and also digital equipments.

Cobbler loop DHCP, PXE boot and also Kickstart to make deployment absolutely nothing greater than including an equipment account and also striking the power switch. For VMs, the koan command does the (in our instance) Xen magic to get the installment began - - on the dom0 I simply type:

koan --system vps.fqdn --server cobbler --no-gfx

after that virsh console to see a VPS structure with no communication.

We make use of RHEL and also have a number of account set up to dividing disks, set up networking and also install base plans for various web server courses. Cobbler sustains Debian and also Ubuntu types yet I've never ever attempted it. An apart: various other intriguing usages for Cobbler include running memtest ISOs and also HP firmware updates.

As soon as our systems are constructed with Cobbler Puppet takes control of to set up the applications, system daemons, register package with RHN, etc Puppet runs as a daemon which occasionally checks that the systems is arrangement matches the specified shows up - - you recognize your updates have actually mosted likely to all web servers. It is additionally a wonderful means to be particular that a box that is been down for upkeep has the proper arrangement prior to you return it to live solution.

Creature actually is outstanding. You do not require to get every facet of your arrangement under its control - - start by having it take care of something straightforward that you require to set up on every box (sudoers is the approved instance) and also take it from there. See to it your Puppet shows up are versioned, also ; absolutely nothing is far better than being conveniently able to curtail to a well-known - excellent arrangement without needing to remember what to readjust.

0
2019-05-31 15:19:12
Source

Puppet appears excellent wherefore you're attempting to do, with the caution that since now, there is no assistance for Windows.

In your instance, you would certainly specify a Server node in regards to every one of the plans that equal throughout the equipments. After that, you specify the specific hosts as nodes which acquire from Server, and also set up the details one-of-a-kind points for it.

Creature is declarative - it permits you to define of your boxes in regards to the sources each box need to have So if you desire ssh - you write a class for that source - and also inside the class you can include reasoning concerning just how ssh is called a little various on FreeBSD vs Ubuntu. It additionally recognizes to make use of yum inside Redhat and also apt-get inside Debian based distros, and also ports in the BSDs. Currently in your Server node, you'll simply have a line like include ssh - and also creature will certainly do the appropriate point and also placed SSH on the equipment without you needing to bear in mind if that's Ubuntu or Redhat or FreeBSD.

What's wonderful is that every one of the Server things stays in one area - and also if at any kind of factor you include in the Server node definition, ALL equipments would certainly upgrade their arrangement as necessary.

Now, I'm just taking care of 3 boxes making use of Puppet - yet it's currently repaid. After investing a week establishing a box we'll be making use of for stimulation discussion in an experiment, it ended up the graphics card vehicle driver was also old in the variation of Ubuntu I place on it (8.04 ). I needed to install the most up to date Ubuntu (9.04 ), yet afterwards I simply needed to proper - get and also run creature - and also every little thing I had actually invested a week establishing was recovered.

Creature does have a little of an understanding contour, yet I've efficiently stayed clear of finding out Ruby - I recognize I'm utilizing it, because that's what creature is created in - yet until now I've achieved success in simply changing the examples in the documentation and the recipes on the wiki. An additional disadvantage is that creature does take a bit longer to do points the very first time. The advantage is that every little thing you transform throughout every one of your equipments is saved in one area - it's typical technique to maintain your creature arrangement in a variation control system - so you can constantly recall and also see just how you've set up web servers in the previous - or roll - back some not successful adjustments.

Ultimately, below is a quick video that does a straightforward creature trial that obtained me. began promptly.

0
2019-05-12 01:01:15
Source

I'm having a great deal of success with Puppet, yet you do need to write a great deal of config.

0
2019-05-08 20:03:53
Source