Changes from Version 1 of WhyPackaging

Show
Ignore:
Author:
skvidal (IP: 98.122.179.90)
Timestamp:
01/26/11 08:07:34 (7 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WhyPackaging

    v0 v1  
     1= analogy = 
     2 It is sort of like a viewpoint. You're zoomed very close in - atomic scale, you pull back you see the molecule that the atom makes up. 
     3 You pull back more you see what the molecule is (water, for example) 
     4 You pull back even more and you see what the water molecules are actually suspended in cloud-form. 
     5 
     6 
     7 systems were atoms - unique, hard to predict and impossible to KNOW entirely 
     8 
     9 then they were molecules - sets that depended on each other and worked together 
     10 
     11 then they were groups of the same molecules, acting the same way and being uniform 
     12 
     13 now they are groups of diverse molecules that create clouds of systems 
     14 
     15 
     16= unix history = 
     17 older unixes practically came embedded on the hw :) 
     18 manual patching 
     19 suffering to update so stability was critical 
     20 relatively few actual systems so it was possible to maintain one at a time. 
     21 major system updates were A HUGE deal 
     22 
     23= sysadmin history = 
     24 lots of apps added by hand - most of the gnu apps were added constantly and right away with any new system 
     25 maintaining thousands of them was a pain - projects like stow were done to help facilitate that under solaris, ultrix, slackware linux, etc. 
     26 
     27= where scale of num of systems pushed deployment needs = 
     28 as computational clusters of boxes were being added it stopped scaling to install each of them separately - but hw was reving too fast for the same 'ghosted' full-system-image install to work. So the installers needed to be able to do a lot, very quickly, and cope with the diverse hw. 
     29 
     30= where num of available human-hours pushed maintenance needs = 
     31 as the number of systems went up the number of admins did not. So they had to make tools and policies to handle managing LOTS of systems the same way. A lot of admins addressed this with tools like cfengine - but more and more they did it by homogenizing their systems. Reducing the 15 different oses and standardizing on as few as possible. More importantly as the number of systems scales WAY up it became impossible to track them all in your head. They had to be completely anonymous and consistent. Faceless rather than unique.  
     32 
     33= why linux won so much vs other unixes = 
     34Red Hat's Kickstart installer really made a big difference. Kickstart was a pun off of jumpstart from Solaris - but the difference was: 
     35 1. kickstart worked really well on diverse hw 
     36 2. kickstart was vastly simpler to work with 
     37 3. the cheap hw is what people wanted to buy and deploy - not expensive sun hw. 
     38 
     39kickstart and pxe made it possible to boot a cluster of machines and have them all up and running w/o actually touching any hw and most importantly have them all be identical in all the important ways. It didn't require careful image creation and then going through and purging out the changes you made simply by creating the image. 
     40 
     41You knew the image was completely pristine b/c it was using the same process as the installer. 
     42 
     43= why we continue to win now = 
     44 
     45Now deploying 1000 diverse boxes was doable. 
     46 
     47Then the trick became maintaining them. Our packaging tools made that happen. Knowing you can use the rules in the packaging system so that an update won't break the world and will apply consistently even if the package set on any 2 boxes is not QUITE the same is what was critical on the individual system scale. 
     48 
     49Add to that good config mgmt tools and we got even further. 
     50 
     51= what tools matter = 
     52Now everyone is working on more tools for managing sets of systems and for deploying clouds of them. The scale is pulling back to an even larger size. 
     53 
     54The tools that matter will let an admin deal with clouds of systems at a time and be able to cope with what they are doing inside them w/o having to worry too much about the minutiae. 
     55