-
Notifications
You must be signed in to change notification settings - Fork 36
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
base: master
Are you sure you want to change the base?
Platform Awareness #183
Conversation
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
|
||
#### "Platform" | ||
|
||
An application's deployment environment. For instance, a k8s cluster or |
There was a problem hiding this comment.
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. | ||
|
There was a problem hiding this comment.
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. | ||
|
There was a problem hiding this comment.
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. | ||
|
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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. | ||
|
There was a problem hiding this comment.
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.
There was a problem hiding this 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.
No description provided.