This document provides instructions for running a Habitat application called "My Tutorial Project" in any operational environment. It describes building the application artifact in the Habitat studio and then running the application natively on hardware, in a VM/cloud instance, or inside a container. The application runtime requirements are listed as a 64-bit Linux kernel version greater than 2.6.32. Users are instructed to enter the Habitat studio, where the application plan has already been built, to access the generated application artifact.
89. Deploying and maintaining apps is hard.
My developer sent me this application to
run in production, but nothing seems to be
working correctly and I can’t figure out
why!
Deploying and maintaining production apps
shouldn’t be so stressful.
90. Write a plan to simplify the process.
With Habitat, the developer describes
everything the app needs to run.
91. Package up everything your app needs.
Next, she packages up the app along with
all the necessary management tools.
92. Distribute it in a variety of formats.
Then she ships the package to a central
location where it is stored alongside all of
its dependencies.
93. Assemble and run your app anywhere.
The ops team retrieves the package, quickly
assembles the entire app, and deploys it to
any environment.
94. Habitat packages are portable and aware.
The application is portable and able to
establish relationships with its peers.
95. Built-in features make management easy.
Once running, ops can easily monitor,
configure and care for the app throughout
its lifecycle.
96. Stop worrying about deploying your app.
With Habitat, deploying and maintaining
apps is safer and more complete, which
makes everybody happy!
97. Habitat: Automation that travels with the app
• Ease the burden of managing microservice apps and
bring benefits of apps architected for microservices to
legacy applications
–Gain consistent management of new and legacy
applications across lifecycle
–Provides application portability for new and
legacy apps
–Autonomous nodes self-manage runtime state
of application based upon policy you define
–APIs expose application behaviors as data for
better management
• Works in tandem with infrastructure automation
• Makes applications running on containers, PaaS, virtual
machines, bare metal, … better