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

lvm guide #1177

Merged
merged 1 commit into from
Nov 28, 2016
Merged

lvm guide #1177

merged 1 commit into from
Nov 28, 2016

Conversation

ywk253100
Copy link
Contributor

No description provided.

# Expand the Hard Disk of Virtual Appliance

If you install Harbor with OVA, the persistent data(such as images and database) is stored in a hard disk which is mounted on directory "/data", and the default size is 50GB. As more and more images are pushed into it, the capacity may not meet your requirements. You can refer to this guide to expand the size of the hard disk.

Copy link
Contributor

Choose a reason for hiding this comment

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

add a step and screen showing how to find out if the space is almost used up.


(1) Log in vSphere web client. Power off Harbor's virtual appliance.
(2) Right click on the VM and select "Edit Settings".
(3) Select "New Hard Disk", and click "OK".
Copy link
Contributor

Choose a reason for hiding this comment

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

add an example here, saying adding a 10GB new hard disk

@coveralls
Copy link

Coverage Status

Coverage remained the same at 51.126% when pulling d01bb30 on ywk253100:161118_lvm into 454f041 on vmware:master.

@ywk253100 ywk253100 force-pushed the 161118_lvm branch 3 times, most recently from f1829fa to e82e169 Compare November 28, 2016 06:34
@hainingzhang
Copy link
Contributor

LGTM

@coveralls
Copy link

Coverage Status

Coverage remained the same at 51.126% when pulling 988ad46 on ywk253100:161118_lvm into 454f041 on vmware:master.

@reasonerjt reasonerjt added this to the 0.5.0 milestone Nov 28, 2016
@coveralls
Copy link

Coverage Status

Coverage remained the same at 51.126% when pulling 988ad46 on ywk253100:161118_lvm into 454f041 on vmware:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 51.126% when pulling 988ad46 on ywk253100:161118_lvm into 454f041 on vmware:master.

@ywk253100 ywk253100 merged commit 871c18d into goharbor:master Nov 28, 2016
@coveralls
Copy link

Coverage Status

Coverage remained the same at 51.126% when pulling 988ad46 on ywk253100:161118_lvm into 454f041 on vmware:master.

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

Successfully merging this pull request may close these issues.

5 participants