Planning Your Fedora Deployment


Before planning the specific steps of an installation, you need to make decisions about the type of deployment you want to undertake. Computing needs dictate the type of hardware and software solutions required for a successful deployment, but before making the plunge, some fundamental questions need to have been asked and answered, such as, "How will you use Fedora?" You learn more about these issues in the sections that follow. These sections also include a table you can use as a predeployment planning checklist and some final advice for planning the installation.

Business Considerations

Choosing an operating system for your business to use is a pretty major decision and one that should be taken with the utmost care. Thought should be given to the consequences that using a different system can have, including how you will work with suppliers. Unfortunately there is no tried and tested way of ensuring that everything will go to plan, but simple common sense and a level head will ensure that the deployment will be successful. Every company is different, and what suits you might be totally wrong for another company. The key is to look closely at what the business benefits will be from the new system and also to identify what impact it will have on existing resources.

Note

Browse to Red Hat's Migration Center at http://www.redhat.com/business/utol/success/ to read success stories, market analyses, and technical reports on using Red Hat's Enterprise Linux products for business.


Thankfully, Linux and open source software is pervasive enough to provide plenty of flexibility should you decide to test the water before diving in. Nowadays, popular open source applications such as OpenOffice.org are available for both Windows and Mac platforms, allowing you to try the software before deciding to switch. Also consider the ability to change back-end systems across to Linux-based alternatives. There are many Linux equivalents to Microsoft Exchange, for example, that can handle email and calendaring. Other popular servers ripe for moving across to Linux include file and print servers, web servers, and firewalls. Of course, if you use Fedora, you largely go it alone in terms of support (although if you go down the Red Hat Enterprise Linux route, doing so opens up support channels from Red Hat). Do not think that you have to switch everything over in one go. Thankfully Linux plays well in a mixed environment (including Mac OS X and Windows XP), so you can quite safely plan a step-by-step migration that allows you to implement each phase one at a time.

Some of the ideas, issues, and concerns surrounding any Linux deployment are listed in Table 2.1, titled "Deploying Fedora." Perhaps the major thing to think about is how Fedora will actually meet a need. Software projects are nearly always successful when you have a clear set of objectives that you intend to meet by deploying software. Something else to think about is how it will affect your existing users. Are your users die-hard Windows power users, for whom any attempt to move them from their platform of choice will result in problems? Do you have the full support of management (something that can make or break any small- or large-scale deployment)? Of course, the changes that users cannot see and do not even notice are the best ones and you are best advised to focus on these opportunities first in your efforts to win over management.

Table 2.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 an intranet? Bandwidth requirements? Wireless? Mobile?

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?


One of the key buzzwords to have come out of the dot com era is Total Cost of Ownership, and it is one that is fiercely debated when people talk about Linux. Those against Linux argue that although the software is free, the real cost comes in the amount of retraining and support necessary to move users to a new operating system. This can be circumvented by implementing Linux in situations where the end users are not directly affected, such as that web server that you have been planning to retire or the file and print server that needs more drive space. What is also often unseen is the increased availability that Linux-based systems offer companies. Quite simply they very rarely go down, unlike their Windows counterparts. Stability counts for a lot in this modern world of e-commerce where even a few minutes can cost thousands of dollars in lost orders and new customers. Talking about stability, one of the great things about Linux is that it does not necessarily need the latest hardware to function effectivelyI have a router at home that is based on an old 486 machine that I bought sometime in 1994! Think how many computers are needlessly disposed of that could be used as print servers or Internet gateways. The savings generated by sensibly recycling existing hardware are very tempting, and easily obtainable if you choose the Linux route.

In all of this, you need to be very clear what the objectives are. Specify exactly what you want to achieve from the project, what the Linux implementation will deliver, and how it will be used to replace any existing machines. What is the Linux machine replacing and what resources will be needed to maintain and support it? If you are rolling out to end users, what specific applications will they be using that you will have to provide support for?

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.

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. Some of them are listed in Table 2.1. 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 workstations 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 2.1 provides a minimal checklist you can use to help plan a deployment.

Do not forget to address follow-up issues on your migration roadmap. You should pay attention to how satisfied or how well new users, especially those new to Linux, are adapting if a new desktop is used. However, if Fedora is deployed in a mixed environment, many users might not even know (or need to know) that Linux is being used!

Planning the Installation

There are many factors in favor of using Fedora as a computing solution. Fedora Core 5 can fill many different roles on various tiers and hardware platforms because its preconfigured installation scripts are a tailored fit for development, workstation, e-commerce, server, and mobile platformsonly the required software will be installed.

Addressing concerns beforehand can help quell any worries or fears felt by new users. Some key factors for a successful installation include

  • Preparation Thoroughly discuss the migration or deployment, along with benefits, such as greater stability and availability of service.

  • Preconfiguration If possible, give users a voice in software choices or categories and poll for comments regarding concerns.

  • Correct installation Ensure that the installed systems are working properly, including access permissions, password systems, or other user-related issues and interaction with the deployment.

  • The right hardware to do the job Make sure that users have the hardware they need for their work, and that computers match the tasks required. For example, developers will have workstation requirements vastly different from administrative personnel.



Red Hat Fedora 5 Unleashed
Red Hat Fedora 5 Unleashed
ISBN: 067232847X
EAN: 2147483647
Year: 2004
Pages: 362

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net