some tech tokens are getting split based on ":"

Tableau:SI

SI gets separated from Tableau in recommendation

We need to capture versions for entities in the following order

1. OS
2. App
3. App Servers
4. Runtime
5. PLs

1. Whether SonarQube is an open source not.
2. if not we need to find an equivalent static code analysis tool.

As a user I should be able to get containerization recommendation for APIs

The recommendation has some bottlenecks. It takes .6 sec for processing 1 record. This is only for compose-app module. The rest of the modules are pretty fast. Thanks to @Salai123 for reporting it.

Older code with old mentions (2k+)

Request Received 1631602243.2549899
Triggered Planning 1631602243.2552867
call containerization plan  1631602243.3072283
detect access token 1631602243.3079007
detected access token 1631602243.3079774
composed app 1631602243.4333582
missing infer tech 1631602243.4339461
app validate 1631602243.434026
assessment ui 1631602243.4362257
planning ui 1631602243.4396195
return final response  1631602243.4432805

New Code with new mentions (6k+)

Request Received 1631609691.3319073
Triggered Planning 1631609691.3320363
call containerization plan  1631609691.3685682
detect access token 1631609691.368657
detected access token 1631609691.368682
composed app 1631609691.911315
app validate 1631609691.911479
assessment ui 1631609691.9115021
return final response  1631609691.9117076

One of the unit test has an old API

app_data = [
{
'application_id': 'App ID 0114',
'application_name': 'App Name 0114',
'application_description': 'App Desc 0114',
'component_name': 'Comp 1',
'operating_system': 'RHEL',
'programming_languages': 'Java',
'middleware': 'WebSphere Application Server',
'database': 'db2 10.0',
'integration_services_and_additional_softwares': 'Redis',
'technology_summary': 'angularJs,express.js,jenkins',
'versioning_tool_type': '1',
'application_inbound_interfaces': 5,
'application_outbound_interfaces': 1,
'devops_maturity_level': 'Moderate',
'devops_tooling': 'Jenkins, Git, JIRA',
'test_automation_%': '50%',
'performance_testing_enabled': 'No'
}

Can we change it?

1. We will add all information from refactored KG to ACA DB. It will be 2 DBs. One community DB and another enterprise DB.

The documents for the containerization API needs to be updated.

1. ACA backend API (Salai)
2. KG utils (Lambert)

Given the generated mentions, we need to add more entities to the current KG.

1. We need to verify the mentions and QIDs.

Update tests for the containerization API.

1. We have to address various labels for 6Rs. One of them being upgrade (refactor).

Expanded the operators' catalog to add new operators

As a user I should be able to get the containerization recommendation for my legacy apps.

{
"status": 201,
"message": "Container recommendation generated!",
"containerization": [
{
"Name": "App",
"Desc": "string",
"Cmpt": "string",
"Valid": true,
"Ref Dockers": "1. {'openjdk_Linux': 'https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/openjdk-11'}",
"Confidence": 0.56,
"Reason": "Containerization feasibility unknown for COTS applications: Apache Tomcat, MySQL",
"Recommend": "Partially Containerize"
}
]
}

1. We have few utility files and sim applier duplicate in both entity standardization and back end api

Either an API or a script to generate JSON representations

Dear Team,

1. What would be expected for technology summary here as it seems to unable to create an output?
2. How to upload bulk files onto the page? Here I can see only one input is allowed

Input : -
[
{
"application_name": "Sample",
"application_description": "This is a Sample App",
"component_name": "Framework",
"operating_system": "RHEL",
"programming_languages": "Java",
"middleware": "Kafka",
"database": "PostGreSQL",
"integration_services_and_additional_softwares": "",
"technology_summary": "Web"
}
]

Output : -
{
"status": 201,
"message": "Assessment completed successfully!",
"assessment": [
{
"Name": "Sample",
"Desc": "This is a Sample App",
"Cmpt": "Framework",
"OS": "{'RHEL': {'Linux|Red Hat Enterprise Linux': ''}}",
"Lang": "{'Java': {'Java': ''}}",
"App Server": "{}",
"Dependent Apps": "{'Kafka': {'Apache Kafka': ''}, 'PostGreSQL': {'PostgreSQL': ''}}",
"Runtime": "{}",
"Libs": "{}",
"Reason": "Reason 101: Medium or low confidence for the inferred data: {"Web": {"Java|Java Web Start": "", "Apache HTTP Server": "", "Java|Google Web Toolkit (GWT)": ""}}",
"KG Version": "1.0.0"
}
]
}

This will involve connecting to DB and generating files required for the containerization API

1. We need to refactor the ACA original to add data for community edition. We need to generate the enterprise edition as well for GBS consumption.

We dont need to release version complexity as of now. We can remove it entirely.

Hi @kaliaanup , I'm onboarding to the Tackle project along with @jortel and @mansam right now.

We are working to learn how the Tackle App Inventory can interface with other tools in the Tackle suite, and trying to define the requirements of the App Inventory data model.

It would be helpful to have a reference doc on the public interface of TCA so that we can get an idea of how TCA this would tie in with Tackle Inventory, and what changes might be needed to the Tackle Inventory data model:

• Expected inputs / outputs of TCA (examples would be useful)
• Methods for invoking TCA (REST? CLI? Something else?)
• Is there a Quay.io container auto-build set up so we can consume TCA easily running as a Pod on OpenShift?
• Is there a deploy YAML available with a deployment definition for TCA and any required auxiliary OpenShift resources (e.g. namespaces, services, routes). This would let us quickly play around with TCA using other info provided. We may be able to assist here if needed.

Do documents detailing the public interface of TCA exist? Even some simple examples would be useful to get started.

cc @rromannissen @jwmatthews @PhilipCattanach

Deploy ACA

There are many binary, metadata, and other duplicate files in this repository that should never have been checked in like:

• Python binaries in multiple __pycache__ folders
• Sphinx _build folders
• Log files *.log
• Database binaries *.db
• Duplicate data folders like aca_db and ontologies
• OS specific metadata like .DS_Store

Once deleted, a proper .gitignore file should be added to keep these files out of the repo for good.

Expanded the operators catalog to add new operators

The urls have been changed. We need to update them.

We need to create a framework to add entities and the other aspects such as mentions, relations, docker images, openshift images, operators and versions.

<img width="784" alt="docker_env_variable" src="https://user-images.githubusercontent.com/85893516/139103125-cef00aee-3add-4239-8547-f85dc5bb6aa4.png"

As a user I should have be able to access the data for containerization from the existing ACA database