Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
SPECfp_rate_base2006 (two-socket) 1x
1.64x
1x
SPECjbb2015 (two-socket) 1.41x
1x
SPECpower_ssj2008 (four-socket) 1.78
These performance and energy-efficiency increases in the Analyzing Existing Applications and Workloads
latest generation of Dell PowerEdge servers demonstrate The first consideration when migrating from a traditional to
the ongoing enhancements to data center results that are an optimized environment is the software running on your
being delivered by successive generations of Dell hardware existing, traditional framework.
technologies.
• If you have a business application developed in-house,
Successful migrations require consideration of the tradeoffs
you can often recompile the source code for re-hosting
involved — for both hardware and software — before
on the new Linux platform.
actually migrating to the new platform. For example, when
building a foundational hardware platform to support an • If you have a commercial application from an ISV, is it
enterprise Linux environment, the main focus should be on available in a version that will run on your platform? If
creating an environment to support key business objectives. a compatible version is not available now or in the near
Initial optimization efforts should focus on determining the future, what is the best replacement?
best way to convert mission-critical business applications
• If you are running a database-intensive core business
and selecting necessary operating system components from
application, you can convert the data structures to a Red
available options based on open standards.
Hat Enterprise Linux environment on an x86 architecture.
Assessing the Potential for Migration
• Are your traditional applications adequately serving their
For most organizations, the optimal timing for a migration is at purpose? If not, it may be an ideal time to switch to an
the end of the maintenance contract for servers that host the open source solution that better meets your requirements
relevant workloads, typically between three and six years from on the new platform.
their date of procurement. Due consideration of the potential
• Are you primarily interested in migrating infrastructure
for migrating those workloads should be undertaken well
applications—such as web servers, domain name
in advance of that milestone, to avoid the need for rushed
servers, Lightweight Directory Access Protocol (LDAP),
decision making or accelerated project timelines. or firewalls? These migrations are typically the simplest,
Potential Approaches to Workload Conversion providing the highest value at the least risk.
Most IT decision makers view their migration projects as In many cases, external dependencies and integrations, as well
multi-stage endeavors, rather than seeking to migrate every as other architectural factors in the environment, may make
workload in the enterprise at once. In addition to mitigating migration more complex than it at first seems. Nevertheless,
risk, this approach allows prioritization of the changes that the availability of Linux versions of existing UNIX software
will generate the most benefit for the least effort. Toward provide a useful first pass at identifying migration candidates. In
that end, identifying the workloads that are particularly good addition, databases that underlie core business applications and
candidates for migration is an early consideration toward that are running on legacy systems may be good candidates
assessing the potential for migration in a given environment. for migration. Despite the relative complexity of multi-tier
migrations, Linux versions of the needed software are typically
As mentioned above, workloads hosted on hardware that is available, as is consulting expertise to assist with the migration,
nearing its end of life are potential candidates for migration. in most cases.
It is also important to consider which applications may be
capacity-constrained or otherwise not adequate to meet Your decisions about which apps to migrate will affect
business needs. Beyond those considerations, the conversion the selection and configuration of a hardware platform to
approach required to migrate specific applications or meet your business needs. For example, moving an older
workloads should contribute to decisions about the value, application that does not take advantage of multithreading
timing, and scope of migration. to the platform will not necessarily require a processor
The level of effort required to complete this conversion can Complexity of Migrating Various Workload Types
vary depending on several considerations, including the In addition to the conversion approach required, the relative
following: complexity of migrating various types of applications and
• Quality and availability of source code documentation. workloads depends in part on the roles they play in the
broader IT environment. For example, moving infrastructure
• Availability of porting tools equipped for conversions. applications such as web servers, firewalls, and backup/
• Availability of developers with the requisite migration skills restore utilities to Linux hosts typically requires little or no
and experience. code conversion and carries little risk, despite providing
high value to the organization. Conversely, custom mission-
• Application age and complexity. critical applications may require significant recoding to make
In some cases, the excess time and effort required to convert them compatible with the post-migration environment while
a traditional application to a version that will run on an open also involving higher potential risk for business disruption.
standards platform will negate any potential benefits. An older, Table 1 provides a point of departure for considering the
poorly documented mainframe application, patched over many ease of migration for various application types, based on
years and written in COBOL, PL/1, or Job Control Language the associated likely magnitudes of risk, effort, cost, and
(JCL) with multiple interdependencies, may be indecipherable downtime.
Learn more about Dell EMC Contact a Dell EMC Expert View more resources Join the conversation
IT Transformation solutions with #ITtransformation
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Red Hat, Red Hat Enterprise Linux, and the
Shadowman logo are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries.
© 2018 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.