Shell Commands › Utilities › iso2class: Appliance Distro Creation Utility › iso2class Reference - Operation

iso2class Reference - Operation

iso2class is an interactive utility which progresses through the following steps:

1. iso2class creates and starts the named application. This application includes a singleton containing a boot volume (the ISO image) and a target volume for the OS install.
2. The user performs the OS install by accessing the console of the singleton iso2class within the application. To access the console, either:
   • Select the application within the application list in the CA 3Tera AppLogic GUI. Next, click the icon for Login (text) or Login (graphic).
   • Or, open the application in the CA 3Tera AppLogic editor. Select the singleton iso2class. Use the pull-down Appliance menu to select Login (text) or Login (graphic).
3. Only iso_volume1 is available during the install. If iso_volume2 or iso_volume3 or iso_volume4 was specified on the command line, the singleton is restarted, using the target volume of the OS install as the boot volume, and including the additional iso_volumes.
4. If installing a Windows OS, the user should install the Windows Server MSI. For complete instructions on creating Windows appliances for CA 3Tera AppLogic, see Windows Installation Reference topic.
5. Upon user confirmation of a completed installation, iso2class stops the application and requires user input to indicate how the finished appliance should be managed by CA 3Tera AppLogic:
   • fully managed - the appliance has the appropriate APK installed. For Windows, the APK is included in the Windows Server MSI.
   • unmanaged - the appliance has no APK installed (it uses field engineering code 4, does not send events to the CA 3Tera AppLogic controller, does not auto-configure its interfaces, and does not obtain properties from its boundary configuration).
6. iso2class modifies the singleton as follows:
   • The target volume of the OS install os_install is made the boot volume of the singleton.
   • The external interface is disabled.
   • in, out, net and mon terminals are added.
   • The appropriate field engineering code is set.
7. The application is started.

The resulting singleton uses HVM virtualization (hardware emulation).