You should separate your configuration and data from the code by placing your data in a separate placeholder volume. In addition, you should separate your code from the os on a read only instantiable volume.
Placeholder volumes are intended for persistent storage as well as provide fixed contents, such as html files for a web server. In addition, placeholder volumes are places where volumes can be attached. Those volumes are used for appliance specific content, such as files and databases that belong to the application, rather than to the appliance class.
Instantiable volumes, unlike placeholder volumes, belong to the appliance class and are copied and migrated with the catalog class.
Important The instantiable volume can be lost between launches of the appliance and will not be preserved when copying and migrating the application where the appliance resides. The only exception is the singleton where instantiable volumes are always preserved.
Follow these steps:
The Volumes tab displays.
The Create Volumes dialog displays
Type of volume. For example: Placeholder
Unique name of the volume. For example: data
Size of the volume in megabytes or gigabytes. For example: 100M
Filesystem that the volume is formatted with. For example: ext3
Click Next and then Close.
The Volumes tab displays.
The Infrastructure Editor displays.
vol manage appliancename.volumename --rw
mkdir content
The Infrastructure Editor displays.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|