Reports

Report is an organized, detailed information of project, hosts and processes which includes Executive summary, About customer, Discovery findings, Hosts classifications, Complexity calculations, Technology stacks, Application distributions, Topology and Nodes information available to the user.

• OmniDeq provides two type of reports.

  1. DART Report : DART (Discovery, Assessment and Rationalization Tool ) report.

  2. Practitioners Report : Practitioners are teams in customer's IT team that are responsible for working on initiatives that will deliver the modernization and/or application transformation and they typically are people who are intimately familiar and passionate about the success of the transformation initiative. The information they seek and the value they derive from practitioners report is much more details about applications and the technical details.

• User can perform multiple actions on reports like Edit the report, Download PDF copy of the report.
  
  

Prerequisite

• Reports can only be generated when the Discovery is complete. If this prerequisite is not met Generate CXO Report and Generate Practitioner Report buttons are disabled.

Recommendations

• Before you start we recommend you to complete below actions to capture maximum data in the report.

• X-Ray

• Host classification

View Report

• CXO Report here
• Practitioners Report here

Containerization Complexity

The final goal of the Discover and Transform stages is to build a container out of each OS process and it's internal and external dependencies. The complexity of the containerization process, termed as containerization complexity is calculated ( High/Medium/Low ) as follows. The process metadata and internal/external dependencies for process containerization are detected at the Discover stage and used for complexity calculations.

The overall complexity = Base complexity + Weighted average of the complexity of each specific parameter mentioned in recommendation report against each process. Example : 32 bit library/package dependency, hard coding of IP address detected.

• The base complexity ( High/Medium/Low ) is influenced by,

• Choice of base container

• Adding the appropriate package dependencies for the process along with its versions and it’s availability for base container image
• Adding the process binaries selectively into the container at an appropriate location

• Adding the process env variables, port, start command and so on in order to get the process started in the container

• For each of specific parameter the complexity ( High/Medium/Low ) is calculated based on the following criteria. This is purely based on CH containerization experience. Also the efforts assumed are manual.

• The nature of work : Whether it is a single line change or multiline change. Whether it is standards based change or application specific change.

• The efforts involved : Whether any RnD is involved to get it to work or enough documentation is available for making the change.
• External dependency : Should the logic take path A or path B based on the external dependency. Example on-prem database connection Vs local database connection.
• Efforts beyond image creation : Changes needed in container runtime to make the container run in K8 environment.
• Application code changes if any to make the container work in K8s environment.