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

Separate persistent data to individual disks on the vSphere Integrated Containers Appliance #743

Closed
dbarkelew opened this issue Sep 6, 2017 · 8 comments · Fixed by #960
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers

Comments

@dbarkelew
Copy link
Contributor

dbarkelew commented Sep 6, 2017

Tracking for separating the MySQL DB for the registry and management portal to second vDisk and separate the log files to a third vDisk.

Use case to mitigate issues if the root disk becomes full.

Bug Ref# 1954150

@andrewtchin
Copy link
Contributor

andrewtchin commented Sep 6, 2017

User Statement:

As a user I want a separate persistent disk for each logs and databases on the appliance.

Details:

Acceptance Criteria:

  • Limit log size
  • Limit database size
  • Separate disks
  • Handles upgrade
  • Documentation

@andrewtchin andrewtchin added product/ova Related to the OVA packaging of vSphere Integrated Containers kind/enhancement Behavior that was intended, but we want to make better priority/medium labels Sep 6, 2017
@corrieb
Copy link
Contributor

corrieb commented Sep 6, 2017

We need to consider the needs of backup here - what is ephemeral data vs persistent data. I would suggest for example that logs could just go in a separate logical partition from images and be on the same VMDK - no need for either to be backed up. Any database info should be on a VMDK that can be backed up independently.

@dbarkelew
Copy link
Contributor Author

dbarkelew commented Sep 6, 2017

I have had customers look at logs as important particularly ones that have SLAs with their clients and need to account for any issues. If the logs do not take that much space, including them in the backup would benefit the customer who require RCAs for any downtime.

@corrieb
Copy link
Contributor

corrieb commented Sep 6, 2017

@dbarkelew Interesting. I know customers consider logs important, but didn't know that there was a backup strategy in place around those. Good input. Just wanted to make sure that the business needs fit the solution

@mdubya66
Copy link
Contributor

mdubya66 commented Oct 6, 2017

adding to 1.3 and making high priority per @pdaigle

@andrewtchin andrewtchin assigned ghost Oct 11, 2017
@andrewtchin andrewtchin added this to the Sprint 19 Lifecycle milestone Oct 11, 2017
This was referenced Oct 18, 2017
@ghost ghost closed this as completed in #960 Oct 31, 2017
ghost pushed a commit that referenced this issue Oct 31, 2017
Adds separate persistent disks to the vic product appliance. These
disks include a data disk, a database disk, and a log disk. Fixes #743.
@andrewtchin
Copy link
Contributor

@stuclem This will need docs on the different disks now used by the appliance

@ghost
Copy link

ghost commented Nov 1, 2017

@stuclem The layout is consistent with the ova design doc, but in short we have four disks now.
/ - root disk
/storage/data/ - data disk; a catch-all disk containing, among other things, the harbor registry.
/storage/log/ - logging disk; contains the harbor and admiral directories for component logs.
/storage/db/ - database disk; contains harbor's mysql, clair, and notary databases.

@andrewtchin
Copy link
Contributor

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants