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

User integration details of Kahu with NTT MEC #30

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

Conversation

sushanthakumar
Copy link
Contributor

What type of PR is this?
This PRs add the User integration details of Kahu with NTT MEC
/kind documentation

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Test Report Added?:

/kind TESTED

Test Report:

Special notes for your reviewer:

- Restoration of the application from a specified backup
- Execution of pre hook and post hook during backup and restore
- Testing on MEC has not been conducted yet and will be carried out in the future
- In the MEC, since we cannot directly access the storage appliance, there is a need to set up an NFS server
Copy link
Contributor

Choose a reason for hiding this comment

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

This line looks like ending abruptly

@@ -0,0 +1,22 @@
# SODA Kahu Project Integration with NTT
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we have topology diagrams for these user case integrations or link to the details?


**User :** NTT MEC

**Use case :** To experience the container workload backup/restore for applications using kahu
Copy link
Contributor

Choose a reason for hiding this comment

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

Experience?

Can we provide the steps to replicate a similar env?

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