Community Services Infrastructure Standards

Legal Notice

Copyright (c) 2009 by Fedora Project. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Community Services Infrastructure Standards
1. CSI Introduction
1.1. Introduction
1.2. What to do
1.3. External Sources and References
2. Language and Terms
2.1. Introduction
2.2. External Sources and References
Host Lifecycle
1. Host Lifecycle Standard
1.1. Introduction
1.2. Host Deployment
1.2.1. Host Purchasing
1.2.1.1. Specifications
1.2.1.2. Quote Request
1.2.1.3. Ordering
1.2.2. Physical Deployments
1.2.2.1. Physical Deployments
1.2.2.2. Firmware Updates
1.2.2.3. Physical Racking
1.2.2.4. Post Racking Checklist
1.2.3. Host Installation
1.2.3.1. Host Preinstallation
1.2.3.2. Host Kickstart
1.3. Maintanence
1.4. External Sources and References
2. Host Lifecycle Rational
2.1. Introduction
2.2. Target
2.3. Details

Community Services Infrastructure Standards

1. CSI Introduction
1.1. Introduction
1.2. What to do
1.3. External Sources and References
2. Language and Terms
2.1. Introduction
2.2. External Sources and References

Chapter 1. CSI Introduction

1.1. Introduction
1.2. What to do
1.3. External Sources and References

1.1. Introduction

The Community Services Infrastructure (CSI) standards are a group of documents designed to be implemented by the largest set of technology users in the world. They focus entirely around Red Hat compatable operating systems (Red Hat Enterprise Linux, Fedora, and CentOS, among others). Unlike most documentation, CSI aims to be standards based. Often checklists can be printed and checked off one by one to ensure compliance. There are three typical target audiences for CSI: System administrators; end users; and management, legal, and other oversight entities.
CSI is developed using open source methods. Any changes or suggestions should be directed to the CSI mailing list. Any questions regarding how or why to implement these changes should be directed to fedora-infrastructure-list@redhat.com.

1.2. What to do

You have been directed to read this document because it contains instructions or procedures you are expected to follow. Read through the items below and make note of any discrepancies or confusing items. It is important that you read, understand, and follow each step carefully. Do not make assumptions about whether a procedure has been completed. Check with the appropriate contacts or responsible parties to ensure proper compliance. It is recommended that you print a copy of these checklists and mark off each step as it is completed. In the event that a response to an item indicates non-compliance, make note of it and take appropriate steps to return to compliance.

1.3. External Sources and References

Chapter 2. Language and Terms

2.1. Introduction
2.2. External Sources and References

2.1. Introduction

In order to avoid ambiguity, this document has been put together to explicitly define common words found throughout CSI.

2.2. External Sources and References

Host Lifecycle

1. Host Lifecycle Standard
1.1. Introduction
1.2. Host Deployment
1.2.1. Host Purchasing
1.2.1.1. Specifications
1.2.1.2. Quote Request
1.2.1.3. Ordering
1.2.2. Physical Deployments
1.2.2.1. Physical Deployments
1.2.2.2. Firmware Updates
1.2.2.3. Physical Racking
1.2.2.4. Post Racking Checklist
1.2.3. Host Installation
1.2.3.1. Host Preinstallation
1.2.3.2. Host Kickstart
1.3. Maintanence
1.4. External Sources and References
2. Host Lifecycle Rational
2.1. Introduction
2.2. Target
2.3. Details

Chapter 1. Host Lifecycle Standard

Mike McGrath

Fedora Infrastructure Lead
Fedora Project
1.1. Introduction
1.2. Host Deployment
1.2.1. Host Purchasing
1.2.1.1. Specifications
1.2.1.2. Quote Request
1.2.1.3. Ordering
1.2.2. Physical Deployments
1.2.2.1. Physical Deployments
1.2.2.2. Firmware Updates
1.2.2.3. Physical Racking
1.2.2.4. Post Racking Checklist
1.2.3. Host Installation
1.2.3.1. Host Preinstallation
1.2.3.2. Host Kickstart
1.3. Maintanence
1.4. External Sources and References
This book is a standard for something.

1.1. Introduction

A little something about something.

1.2. Host Deployment

The following steps should be followed whenever deploying a new system. This includes systems that are being repurposed or rebuilt.

1.2.1. Host Purchasing

Please use the following guidelines and checklists when purchasing new hardware.

1.2.1.1. Specifications

A little something about something.

1.2.1.2. Quote Request

A little something about something.

1.2.1.3. Ordering

A little something about something.

1.2.2. Physical Deployments

When deplying a new physical host, the following requrements must be met. This is in addition to the normal host deployments below.

1.2.2.1. Physical Deployments

Each of the below items is to be inventoried. Include brief description. Model number, manufacturer/vendor and serial number.
Inventory Items
CompletePartAdditional
Packaging IntegretyEnsure packaging that the server was shipped in is not damaged and that everything on the manifest is in the box.
ChasisInclude serial number, part numbers, manufacturer, etc.
DrivesInclude information from each drive in the host.

1.2.2.2. Firmware Updates

Ensure every part of the system is up to date prior to use.
Firmware Updates
CompletePartDescription
BIOSEnsure the bios is at the latest available version.
DrivesEnsure each physical drive is up to date.
Remote AccessEnsure any remote access modules are updated including BMC, RSA-II, DRAC, iLo, etc.

1.2.2.3. Physical Racking

While racking the server, ensure each requirement is met.
Inventory Items
CompleteStepRequirementDescription
Rail KitMustInstall rail kit in rack, install on server.
MountingMustPlace server in rack.
Vendor Cable ManagementShouldAny vendor provided cable management should be installed with the server (usually as an arm on the back of the server). It is acceptable to exclude this if your organizations cable management policies are in conflict with these devices or if they, for whatever reason, are physically unable to fit in the rack.
Network ConfigurationMustUsing cable management policies, run cable from your switch or drop points to the ports on the server. Ensure the cable has enough length to remain connected while the server's rail kit is in the fully extended position. Cables should be no more then 3 inches longer then this required length. Follow a common cable coloring standard (not presently covered by CSI)
KVMMayThose wishing to use a KVM (keyboard, mouse and monitor) may hook them up. Use the provided cable management and ensure the cables are no more then 3 inches longer then required to have the server in it's full out position.
Serial/RemoteShouldIn addition to the remote access modules, servers should have an additional remote management method. Serial consoles are popular for this. Ensure the cabling required for this uses provided cable management and is no more then 3 inches longer then required to have the server in it's full out position.
PowerMustOnce the host is installed, ensure power is properly supplied via the provided cable management. Cables should be no more then 3 inches longer then required for the server to be in it's full out position.

1.2.2.4. Post Racking Checklist

Once the server is fully racked and installed, the following checklist must be completed.
Post Install Checklist
CompleteTaskDescription
PDU Port ConfigEnsure each PDU port is inventoried and configured. If the PDU is managable, ensure the ports are properly labeled.
Serial ConsoleIf using serial console, ensure it is working (check bios baud rate and cyclades baud rate).

1.2.3. Host Installation

Host installation covers all aspects of deploying an operating system and getting it prepared to be put to use. It is to be combined with the services development lifecycle document to be placed into production. There is some overlap though this host deployment section attempts to focus on dependencies to the service.

1.2.3.1. Host Preinstallation

The idea here is running a website has certain requisites, an operating system for example. This document describes the steps required before a host is ready to run those services.
Prekickstart Checklist
CompletePartAdditional
RAID ConfigurationIf applicable, set up software raid on the host.
Storage PreparationEnsure proper storage has been allocated for the host.
Memory CheckEnsure proper memory has been allocated for this host.
CPU CheckEnsure processors are present and properly allocated.

1.2.3.2. Host Kickstart

The idea here is running a website has certain requisites, an operating system for example. This document describes the steps required before a host is ready to run those services. There is a preference to using kickstart scripts for all installations though manual installation is acceptable when an automated installation is inapproperate.
Kickstart Procedure
CompletePartAdditional
Network ConfigurationDetermine IP address (if not using DHCP), network, gateway, resolver.
Source VerificationVerify the new host has access to the kickstart scripts and installation media.
Verify the new host has access to the kickstart scripts and installation media.
# CSI Docs
# http://fedorahosted.org/csi/
# GPLv2
install
vnc --password VNC_PASSWORD
key --skip
lang en_US.UTF-8
rootpw Your_Temporary_Password_Here
firewall --disabled
authconfig --enableshadow --enablemd5
timezone --utc UTC

# Left commented for data protection
# Normal fresh installs should have this section uncommented
#clearpart --linux --drives=xvda --initlabel
#part /boot --fstype ext3 --size=256 --ondisk=xvda
#part swap --fstype swap --size=2048 --ondisk=xvda
#part pv.01 --size=100 --grow --ondisk=xvda
#volgroup GuestVolGroup00 pv.01
#logvol / --fstype ext3 --size=100 --vgname=GuestVolGroup00 --name=root --grow
#bootloader
# end disk bits

keyboard us
selinux --permissive
mouse none
skipx
reboot

%packages --resolvedeps --nobase

1.3. Maintanence

todo

1.4. External Sources and References

Chapter 2. Host Lifecycle Rational

Mike McGrath

Fedora Infrastructure Lead
Fedora Project
2.1. Introduction
2.2. Target
2.3. Details

2.1. Introduction

Something is very important to do something.

2.2. Target

The target of some thing is to do another thing.

2.3. Details

If you want a pony, start with something.