IBM smartcloud init uses configuration data by using startup scripts at startup

IBM Smartcloud™init (an IBM SmartCloud support package) is the first startup script developed from an Open-source cloud-init package. It was originally developed in the form of icon bundle in the integration context between Image construction and composition Tools (icon) and IBM SmartCloud Provisioning 1.2, and later expanded to A key component of IBM SmartCloud Provisioning 2.1.

IBM SmartCloud Init is a simple, stand-alone component that executes when a virtual machine (VM) is started to use a multipurpose Internet Mail Extension (MIME) configuration data that is formatted as multiple parts. IBM SmartCloud Init obtains this input data and looks at the content types associated with each section. If the content type is known, IBM SmartCloud Init invokes the associated consumer.

Possible use cases with IBM smartcloud init scripts

The first use case and the associated MIME type are open Virtualization format (OVF) mirrors that support ICON generation. The current implementation handles only one content type (application/ovf-param) and one user to process the OVF metadata and saves the related part as the ovf-env.xml of the Activation Engine (AE).

You can use IBM SmartCloud init to initialize a cloud instance that performs a series of actions at startup. For example, install a series of Red Hat packages (RPM), execute commands at startup, or download and execute scripts at startup (this is useful for converting virtual machines to virtual machines). Alternatively, you can extend the script to support the queued list of packages, for example:

IBM tivoli®endpoint Manager (TEM or BigFix) Fixlet (by deploying BIGFIX agents and Fixlet when the VM is started) Chef Recipes Puppet policy icon/image Construction and Composition Tool (ICCT) bundle (for installing any IBM middleware, such as IBM db2® or websphere® Application Server) Maestro bundle IBM Workload Deployer (IWD) script package RPM and Debian native package

You can download a package for execution by using a Uniform resource identifier that points to the repository search order. Other use cases include supporting Maestro using any mirror that contains IBM SmartCloud Init's first boot script, which downloads and installs the Maestro agent and extends the IBM SmartCloud Provisioning installer to create a basic Red Hat Enterprise Linux mirroring, which has an installed IBM SmartCloud init package. In this way, any new instance created from the mirror can automatically perform the task when it is activated.

IBM SmartCloud init Deliverables

Scp-cloud-init is a simple component that can be used for Linux and Windows. Scp-cloud-init in Linux contains file scp-cloud-init. The easiest way to install this file in mirrors that use levels 3 and 5 is to run the following command:

cp-f scp-cloud-init.sh/etc/init.d/scp-cloud-init 2>/dev/nullchkconfig scp-cloud-init on

If you have mounted the disk and cannot use Chkconfig, you can manually generate the RC#.D link using the command shown in Listing 1.

Listing 1. To manually generate a RC#.D link command

if [-D/ETC/RC3.D]; Then Ln-fs. /init.d/scp-cloud-init/etc/rc3.d/s11scp-cloud-init chmod 755/etc/rc3.d/s11scp-cloud-init 2>/dev/nullfiif [D/ ETC/INIT.D/RC3.D]; Then Ln-fs. /scp-cloud-init/etc/init.d/rc3.d/s11scp-cloud-init chmod 755/etc/init.d/rc3.d/s11scp-cloud-init 2>/dev/ Nullfiif [-D/ETC/RC5.D]; Then Ln-fs. /init.d/scp-cloud-init/etc/rc5.d/s11scp-cloud-init chmod 755/etc/rc5.d/s11scp-cloud-init 2>/dev/nullfiif [D/ ETC/INIT.D/RC5.D]; Then Ln-fs. /scp-cloud-init/etc/init.d/rc5.d/s11scp-cloud-init chmod 755/etc/init.d/rc5.d/s11scp-cloud-init 2>/dev/nullfi # The s## adjective should is after the "receptacle" but unreported any activation.* (AE) scripts.

Scp-cloud-init in Windows contains files Scp-cloud-init.cmd and Scp-cloud-init.vbs. To install these files in a mirror so that they can be run at startup, do the following:

Copy the scp-cloud-init.* file to a directory, such as C:\WINDOWS\SETUP\IBM. Add scripts that will be run using the Group Policy Editor at startup by running Gpedit.msc. Click Computer Revisit > Windows Settings > Scripts, and then double-click Startup. Click Add, and then type C:\Windows\Setup\IBM\scp-cloud-init.cmd as the program (no parameters). Click OK, click OK again to exit the Startup script window, and then exit the GPEdit application.

The previous method of adding a registry key to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run (as shown below) appears to execute scripts only when an administrator logs on. Scripts are not executed automatically at system startup.

"reg add hkey_local_machine\software\microsoft\windows\currentversion\run/f/V a-cloud-init/d c:\windows\setup\ Ibm\scp-cloud-init.cmd "

Scp-cloud-init is provided as an RPM package in Linux and is provided as an. msi file in Windows.