Scribd
Upload
139 views

TC3094en-Ed01 Software Orchestration Tool S.O.T-OVA Creation On Low Hardware Mode

Uploaded by

Tallat Masood
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
139 views

TC3094en-Ed01 Software Orchestration Tool S.O.T-OVA Creation On Low Hardware Mode

Uploaded by

Tallat Masood
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Release Note Software Orchestration Tool

TC3094 ed.01 Release 3.2 and above

Software Orchestration Tool (S.O.T.) – OVA


creation on low hardware mode

This document presents a new feature of the S.O.T. tool available from version 3.2.002.002. It gives all necessary information
for the creation of an OVA on S.O.T. with constraints of hardware check being removed.

Revision History
Edition 1: February 6, 2024 Creation of this document

Legal notice:
www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other
trademarks used by affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other
trademarks are the property of their respective owners. The information presented is subject to change without notice. Neither
ALE Holding nor any of its affiliates assumes any responsibility for inaccuracies contained herein. © Copyright 2024 ALE
International, ALE USA Inc. All rights reserved in all countries.
Table of contents
1 OVA CREATION UNTIL 3.2.002.002 .......................................................................................................... 3
2 OVA CREATION: UPDATE on HARDWARE NEEDS ...................................................................................... 3
3 INSTALLATION & USE ............................................................................................................................. 3
3.1 Deploy SOT OVA & manage the SOT vm ............................................................................................ 3
3.1.1 Adding a new virtual disk to the SOT vm ...................................................................................... 4
3.1.2 Switch to “templateFactory”: ....................................................................................................... 5
3.2 Start a project. ................................................................................................................................. 7
3.3 Get the result files. ............................................................................................................................ 7
4 MAINTENANCE/ SERVICEABILITY/ SECURITY ........................................................................................... 7

4.1 In case the OVA creation fails: ........................................................................................................... 7


4.2 Free disk space ................................................................................................................................. 8

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 2/9
1 OVA CREATION UNTIL 3.2.002.002
Until version 3.2.002.002 the creation of an OVA is submitted to several constraints in term of hardware where
the SOT is installed:
- 500Gb of hard drive, 16 Gb of RAM, 8 core cpu.
That feature is available only through the deployment of the
“softwareOrchestrationToolWithTemplateFactory.ova” OVA

This way of using OVA creation is mostly used on servers with a need to offer multiple OVA files to technicians
for download.

2 OVA CREATION: UPDATE on HARDWARE NEEDS


The new development appeared in version 3.2.002.002 consists of a bypass of those hardware needs that are
hard coded in order to be able to build OVA on any server or laptop … etc. with less constraints.
The hardware requirements are no more controlled. Anyway, a specific warning is visible on the home page of
the browser.

That development needs a little management to take effect. Also, it is available through the
“softwareOrchestrationTool.ova” and NOT the other “Template” OVA mentioned above.

OVA creation can be performed on any computer using either VMware ESXi or VMware Player, workstation etc.
Though the control of hw needs is removed the time spent to build the OVA depends strongly on the machine
(RAM, number of proc/core).

For a laptop with 16Gb of RAM, 6 cores it takes around 40mn.


For less memory as 8Gb, 4 cores it can take up to 3 hours.
Those results are just informative.
It is recommended to have at least 40Gb of free hard disk on PC (but 50Gb mandatory in vm management).

At the end 2 OVA (compressed file in extension “.tgz”) are created : 1 for VMware & the other to be used by
kvm virtualization systems.

The process of OVA project creation, deployment & final files retrieval is the same on both methods. What
differs is the use of the “regular” SOT OVA & the management to do to access to the template factory feature
with no hardware control.

3 INSTALLATION & USE

3.1 Deploy SOT OVA & manage the SOT vm


It is important to follow those steps in that order:
- Start by deploying the “softwareOrchestrationTool.ova”
- Add a new virtual disk of 50Gb.

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 3/9
- Start the SOT vm
- In the SOT console type “templateFactory”
 The vm will start with the new feature being available.

3.1.1 Adding a new virtual disk to the SOT vm

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 4/9
3.1.2 Switch to “templateFactory”:
Screenshots from the VMware console
Before:

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 5/9
After:

Type “Y” and then:

In the browser the new feature can be seen:

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 6/9
3.2 Start a project.
Start a new project, select “Template Factory” etc.
Once the project is started if the status display is lost by selecting other options in menu … that deployment
status can be seen & refreshed again by clicking here:

3.3 Get the result files.


When the popup message is seen:

Retrieve the 2 .tbz files by clicking on it.

4 MAINTENANCE/ SERVICEABILITY/ SECURITY

4.1 In case the OVA creation fails:


- Get logs from the SOT web page.
- Give the time spent on project before it stops.
- Give the machine characteristics: RAM/cores/free space on disk.
- The removal of hardware check means also that the result depends on the machine: if the deployment
of OVA takes too much time it means that this server/PC is not qualified to support that feature. No
software modification on SOT will be done.

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 7/9
Creation of oxe OVA: internal installation of ALL products is limited with a timeout of 2h. After that time, the
project stops, free all files. A timeout error is stored at the end of the file <result file-
date>/var/log/engine/install.log (result file being decompressed)
A project creation can take more than 2h though because after the oxe installation the process continues by
generation, conversion & compression of OVA.

Limit of disk space is reached: check in the file “templateFactory.log” under “/var/log/engine”

This kind of information is found in the compressed file generated by the action of “reports”

4.2 Free disk space


Remove the result files unless it is necessary to keep them.
Restart or stop the vm to free disk space.

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 8/9
Submitting a Service Request
Please connect to our eService Request application.

Before submitting a Service Request, please be sure:


− The application has been certified via the AAPP if a third party application is involved.
− You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
− You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
− You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.

- END OF DOCUMENT -

Software Orchestration Tool - Release 3.2 and above TC3094 ed.01


© Copyright 2024 ALE International, ALE USA page 9/9

You might also like