infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Abstract
http://www.infrastructures.org/bootstrap/abstract.shtml
When deploying and administering systems infrastructures it is still common to think in terms of individual machines rather than view an entire infrastructure as a combined whole. This standard practice creates many problems, including labor-intensive administration, high cost of ownership, and limited generally available knowledge or code usable for administering large infrastructures. Section of the web site. Ad Hoc Change Tools. Search www.infrastructures.org. In partnership with TerraLuna, LLC.
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Papers
http://www.infrastructures.org/bootstrap/papers.shtml
This site is based in part on the paper Bootstrapping an Infrastructure. Why Order Matters: Turing Equivalence in Automated Systems Administration. Was cited by Robin Miller on NewsForge. Ad Hoc Change Tools. Search www.infrastructures.org. In partnership with TerraLuna, LLC.
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Introduction
http://www.infrastructures.org/bootstrap/introduction.shtml
There is relatively little prior art in print which addresses the problems of large infrastructures in any holistic sense. Thanks to the work of many dedicated people we now see extensive coverage of individual tools, techniques, and policies [nemeth]. But it is difficult in practice to find a "how to put it all together" treatment which addresses groups of machines larger than a few dozen. We will discuss the sequence that we developed and offer a brief glimpse into a few of the many tools and technique...
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Enterprise Infrastructures Workshop
http://www.infrastructures.org/bootstrap/workshop.shtml
The workshop page has been moved to http:/ www.infrastructures.org/workshop". Ad Hoc Change Tools. Search www.infrastructures.org. In partnership with TerraLuna, LLC.
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Systems Administrator, or Infrastructure Architect?
http://www.infrastructures.org/bootstrap/career.shtml
Systems Administrator, or Infrastructure Architect? There's a career slant to all of this. Good architects seem to be motivated by impatience and efficiency; they hate doing the same thing twice, and are always looking for a better way. But at the same time, they must have the patience that comes with good people skills, a dedication to the organization's mission, and the hard-nosed pragmatism needed to preserve and improve return on investment for the business. Infrastructure architects tend to spend mo...
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Chaos
http://www.infrastructures.org/bootstrap/chaos.shtml
Outside the systems administration field, it's not well known that computer systems management is generally ad-hoc. Administration tends to be reactive in nature, based on monitoring and helpdesk trouble calls. Little effort is allocated for proactively automating the management of systems in order to prevent problems and expedite solutions. A well-run IT department is like air - it's taken for granted. It smoothly provides services which are always reliable and never delivered late, performance of s...
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Disaster Recovery
http://www.infrastructures.org/bootstrap/recovery.shtml
The fewer unique bytes you have on any host's hard drive, the better - always think about how you would be able to quickly (and with the least skilled person in your group) recreate that hard drive if it were to fail. The test we use when designing infrastructures is "Can I grab a random machine that's never been backed up and throw it out the tenth-floor window. Without losing sysadmin work? If the answer to this was "yes", then we knew we were doing things right. In tests we were able to recover the en...
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Migrating From an Existing Infrastructure
http://www.infrastructures.org/bootstrap/migrating.shtml
Migrating From an Existing Infrastructure. Think of a migration as building a new enterprise cluster, and migrating your old hardware into the new cluster, one node at a time. If you are migrating existing machines from an old infrastructure (or no infrastructure) into a new infrastructure, you will want to set up the infrastructure-wide services (like NIS, DNS, and NFS) first. Then, for each desktop host:. Have the user log off. Migrate their data from their old workstation to an NFS server.
infrastructures.org
Infrastructures.Org: Best Practices in Automated Systems Administration and Infrastructure Architecture: Home
http://www.infrastructures.org/index.shtml
Most IT organizations still install and maintain computers the same way the automotive industry built cars in the early 1900's: An individual craftsman manually manipulates a machine into being, and manually maintains it afterward. This is expensive. The automotive industry discovered first mass production, then mass customization using standard tooling. The standards and practices described here are the standarized tooling needed for mass customization within IT. This tooling enables:. If you want to jo...
