4 Application Development

WHAT’S IN THIS CHAPTER?                   

  • Legacy applications
  • Why do you need migration to clouds?
  • Migrate-to-cloud methodology
  • Convert your application into an OpenStack app
  • Building applications from scratch
  • Development stack
  • Application network connectivity
  • Application security
  • Hands-on application deployment

In this chapter you will be explicitly shown how to perform a legacy application migration from a self-maintained proprietary environment to an OpenStack environment. But before diving in, let’s make sure we understand the full meaning of the term “legacy application.” In computer science, legacy applications are those that come from platforms and techniques that exist earlier than the current technology stack, and in general these are applications that are serving critical business needs in an organization. Okay, let’s get started.


When the word “legacy” appears within any context, the first thought is that we’re talking about something very old that can’t be adjusted to the current state of things. But if we’re talking about software, a legacy application is not necessarily defined by age. Legacy may refer to the lack of vendor support or a system’s incapacity to meet organizational requirements. Legacy conditions refer to a system’s difficulty (or inability) to be maintained, supported or improved. A legacy application is usually incompatible with newly purchased systems. An organization ...

Get OpenStack Cloud Application Development now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.