Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation needed to interface with tackle-diva from Tackle Inventory #29

Open
djwhatle opened this issue Sep 28, 2021 · 3 comments
Open
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@djwhatle
Copy link

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

(Note: I'm not sure if tackle-diva is meant to be integrated with tackle-inventory or if it's more tied to windup. Looking for information on this)

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 tackle-diva (TD) so that we can get an idea of how TD this would tie in with Tackle Inventory, and what changes might be needed to the Tackle Inventory data model:

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

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

cc @rromannissen @jwmatthews @PhilipCattanach

@djwhatle djwhatle added the documentation Improvements or additions to documentation label Sep 28, 2021
@YasuKatsuno
Copy link
Collaborator

YasuKatsuno commented Sep 29, 2021

Hi @djwhatle thank you for contacting us.

We are now having active discussions/works with @PhilipCattanach @rromannissen @mrizzi to integrate into windup.
https://github.com/konveyor/tackle-diva/tree/main/windup
https://github.com/akihikot/windup/tree/diva

Please find out answers.

Expected inputs / outputs of TD (examples would be useful)

Input: directory path that contains a set of application source codes
Output: 6 files about data-centric analysis results: contexts.yml, transaction.json, transaction_summary.dot, database.json transaction.yml, transaction_summary.pdf.

Please check the blog article for the details.
https://opensource.com/article/21/6/tackle-diva-kubernetes

Methods for invoking TD (REST? CLI? Java API? Something else?)

CLI and REST

Is there a Quay.io container auto-build set up so we can consume TD easily running as a Pod on OpenShift?

TD is built as a Docker image and executed as a Docker container. It's easy to build/run it.

Is there a deploy YAML available with a deployment definition for TD and any required auxiliary OpenShift resources

The Dockerfile is ready, although YAML files for OpenShift are not yet.

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

You can easily try Tackle-DiVA, following the "Getting Started" section in README. The prerequisite is the only Docker runnable environment like macOS.

@PhilipCattanach
Copy link

@djwhatle There is no direct link between the Application Inventory and DIVA. The plan is to integrate DIVA into the Application Analysis tool (WINDUP/MTA).

@djwhatle
Copy link
Author

Thanks for the info @YasuKatsuno @PhilipCattanach . Follow-up question: is there intent to integrate App Inventory and MTA/Windup?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants