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

[Enhancement] Egeria file layout proposal to simplify deployment #7766

Closed
dwolfson opened this issue Jun 28, 2023 · 4 comments
Closed

[Enhancement] Egeria file layout proposal to simplify deployment #7766

dwolfson opened this issue Jun 28, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request no-issue-activity Issues automatically marked as stale because they have not had recent activity. triage New bug/issue which needs checking & assigning

Comments

@dwolfson
Copy link
Member

Existing/related issue?

No response

Please describe the new behavior that that will improve Egeria

On today's community call we discussed a proposal to update the file layout of Egeria to simplify deployment in a production environment. We are currently considering these changes for the 4.3 release of Egeria (tentatively planned for September, 2023). Updates would be required to the Egeria's assembly, labs and helm charts.

The current file layout is:

image

While the current layout works, we propose changes to clarify and simplify the structure. The proposal suggests grouping of:

  • optional components
  • log storage locations
  • convenient directory mount points
  • more use of common conventions

The following diagram shows the proposed changes.

image

Suggested changes include:

  • a var directory for logs and ssl information
  • an opt directory for optional components such as samples and pre-built metadata archives
  • Boxes colored green are suggested directory mount points. For example, logs may often be shared or aggregated with others.
  • Clearer separation between the Egeria OMAG Server Platform and the Egeria UI Application.

As always, we are looking for feedback from the community as we explore these proposals. Attached below is a draw.io file with the source for the diagrams above. We look forward to your thoughts and comments - and especially welcome your ideas on how we can continue to simplify deployment.

egeria_file_layout_community.drawio.zip

Alternatives

No response

Any Further Information?

No response

Would you be prepared to be assigned this issue to work on?

Yes

@dwolfson dwolfson added enhancement New feature or request triage New bug/issue which needs checking & assigning labels Jun 28, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Aug 28, 2023
@mandy-chessell mandy-chessell removed the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Aug 28, 2023
@mandy-chessell
Copy link
Contributor

These are the current new layouts implemented so far.

For the OMAG Server Platform runtime (see new module https://github.com/odpi/egeria/tree/main/open-metadata-distribution/omag-server-platform) the assembly includes samples and utilities designed to allow someone to explore the platform capabilities. It includes the Docker file to build a new docker container from the assembly.

For the UI Application (see new module https://github.com/odpi/egeria/tree/main/open-metadata-distribution/egeria-ui-application) simply provides the application jar and associated files.

mandy-chessell added a commit to mandy-chessell/egeria that referenced this issue Aug 29, 2023
mandy-chessell added a commit that referenced this issue Aug 29, 2023
Enhance omag-server-platform assembly (#7766)
lpalashevski pushed a commit to lpalashevski/egeria that referenced this issue Sep 7, 2023
lpalashevski pushed a commit to lpalashevski/egeria that referenced this issue Sep 8, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the no-issue-activity Issues automatically marked as stale because they have not had recent activity. label Oct 28, 2023
@mandy-chessell
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-issue-activity Issues automatically marked as stale because they have not had recent activity. triage New bug/issue which needs checking & assigning
Projects
None yet
Development

No branches or pull requests

2 participants