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

Platform Awareness #183

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

mansam
Copy link
Contributor

@mansam mansam commented Jun 12, 2024

No description provided.

Signed-off-by: Sam Lucidi <slucidi@redhat.com>
@mansam mansam marked this pull request as ready for review June 26, 2024 14:21

#### "Platform"

An application's deployment environment. For instance, a k8s cluster or
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm missing Application Servers here: WAS, EAP, Weblogic...

Analysis of an application that is able to inspect the application's
deployment environment and identify issues that may prevent it from
being rehosted or replatformed cleanly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should add add a use case around enabling Konveyor to retrieve information about applications directly from the platform in which they are running, like deployment configuration and runtime configuration.

application-scoped analysis. For instance, a platform analysis might
examine cluster-scoped resources, network or security assumptions,
or compute resources.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, I'm missing something about how applications are deployed in the platform.

Additionally, it should be possible to perform analysis of platforms
outside of the context of a specific application, the results of which
would be reported in a new interface for platform analysis results.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also include an application discovery use case: given the coordinates of a given platform, allow the system to discover the applications deployed on it and populate the inventory accordingly.

Automated analysis of the deployment environment can tell us about the
application's resource requirements, its security and availability
characteristics, and other traits which may be present in the live
environment but not in source control or other documentation. Combining
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Application configuration is a must as well, especially if we intend to tackle assets generation.

create and select analysis rulesets for platforms.
* It should be possible to run analysis of a platform with analysis rule sets
targeting migration to other platforms.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hub should be able to retrieve deployment and runtime information about applications and store it in canonical form, for it to be used to output potential assets in subsequent stages of the migration process.

Copy link
Contributor

@rromannissen rromannissen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good start for the k8s side of platform awareness an the integration with tools such as Crane, but it's completely missing everything related to application deployment and runtime configuration.

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

Successfully merging this pull request may close these issues.

2 participants