Research is definitely a must before you embark on any project. It is also sensible to set up a test environment so that you can examine the performance of the new machine under set conditions to ensure that it functions in the way that you require. It is crucial that you spend a decent amount of time on testing because doing so will pay off in the long run with fewer bugs to fix and more positive user feedback and end-user experience.
System Considerations
Fedora is flexible enough to cope with a wide range of computing needs, but with any switch of operating system you need to be aware of some of the issues that switching might cause. Table B.1 lists some of these. For example, how you choose to use Fedora could affect your choice of computer hardware, might affect your network configuration, and could dictate software policy issues (such as access, security, and allowable protocols).
Linux-based operating systems can be used to provide many different services. For example, one server might be boot management for a thin-client network in which work stations boot to a desktop by drawing a kernel and remotely mounted file systems over a network. This mechanism is not supported out of the box, so some effort can be expended if such a system is required. Other services more easily implemented (literally in an hour or less) could be centralized server environments for file serving, web hosting for a company intranet, or bridging of networks and routing services.
Linux supports nearly every network protocol, which enables it to be used to good effect even in mixed operating system environments. The security features of the Linux kernel and companion security software also make Linux a good choice when security is a top priority. Although no operating system or software package is perfect, the benefit of open source of the kernel and other software for Linux allows peer review of pertinent code and rapid implementation of any necessary fixes. Even with the secure features of Linux, some effort will have to be made in designing and implementing gateways, firewalls, or secure network routers.
Fedora can serve as a development platform for applications, e-commerce sites, new operating systems, foreign hardware systems, or design of new network devices using Linux as an embedded operating system. Setting up workstations, required servers, source code control systems, and industrial security will require additional effort.
Hardware compatibility can be an issue to consider when setting up a Linux server or building a Linux-based network. Fortunately, most of the larger server manufacturers such as IBM, HP, and even Dell realize that Linux-based operating systems (like other open source operating systems such as BSD) are increasingly popular, support open standards, and offer technologies that can help rapid introduction of products into the market (through third-party developer communities).
Fedora can help ease system administration issues during migration. The latest suite of Fedora's configuration utilities provides intuitive and easy-to-use graphical interfaces for system administration of many common services, such as networking, printing, and Windows-based file sharing. Fedora can also be used to support a legacy application environment, such as DOS, if required.
User Considerations
Humans are creatures of habit. It can be hard to transition a workforce, customer base, or other community to a new environment. The Fedora desktop, however, provides a friendly and familiar interface with menus and icons that new users can readily learn and put to work.
Part of the migration process can involve addressing user concerns, especially if Linux will take over the desktop. Fedora can be deployed in stages to make the migration process a bit easier, but the issue of user training must be addressed early on. This is especially true if users will be required to develop new skills or be aware of any caveats when using Linux (such as deleting all files in one's home directory). Although Fedora can be configured to provide a "turn-key" desktop in which only several graphical applications (such as a web browser, organizer, or word processor) can be used, some users will want and need to learn more about Linux.
You can turn to formal Linux training from commercial vendors. System administrators can get training directly from Red Hat (go to http://www.redhat.com/training). For other issues concerning Linux in larger computing environments, browse to Linas Vepstas's Linux Enterprise Computing pages at http://linas.org/linux/.
A Predeployment Planning Checklist
Table B.1 provides a minimal checklist you can use to help plan a deployment.
TABLE B.1 Deploying Fedora
| Consideration | Description |
|---|---|
| Applicability | How is Fedora going to be used? |
| Boot management | Will remote booting be required? |
| Connectivity | Will the system be used in an internal network, or connected to the Internet? Is there a requirement for wireless connectivity? What about bandwidth? |
| Context | How does this install fit in with academic, business, or corporate needs? |
| Consensus | Are managers and potential users on board with the project? |
| Comparison | Is this install part of platform comparison or benchmarking? |
| Development platform | Will development tools be used? |
| Embedded device | Is it an embedded device project? |
| Hardware | Are there any special hardware or device interfacing requirements? |
| Finance | How much is in the budget? Will cost comparison be required? |
| Marketing | Will a product or service be offered as a result? |
| Networking | What type of networking will be required? |
| Objective | Is there a specific objective of the install? |
| Pilot project | Is this a pilot or test install? |
| Power management | Any special power or energy requirements? |
| Public relations | Does the public need to know? |
| Quality of service | Is high availability or data integrity an issue? |
| Roadmap | What other steps might precede or follow the install? |
| Reporting | Are follow-up reports required? |
| Security | What level or type of security will be required? |
| Server | Is this a server installation? |
| Site considerations | Does the location provide needed temperature and security, or does it even matter? |
| Software | Are any special device drivers needed for success? |
| Storage | Are there size or integrity needs? Has a backup plan been devised? |
| Timeline | Are there time constraints or deadlines to the install? |
| Training | Will special training be required for users or administrators? |
| Users | How many and what type of users are expected? |
| Workstation | Is this a workstation or personal desktop install? Is the workstation portable? |