ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000049ClearOSapp-storage - Storagepublic2010-03-25 15:172013-04-26 19:44
Reporteruser2 
Assigned Todloper 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version6.4.0 Alpha 1Fixed in Version6.4.0 Alpha 1 
Summary0000049: Add centralized volume management architecture
DescriptionPart of the problem with Linux system is the diverse and varied ways in which user data is stored on the system. Because of a long legacy with POSIX standards, code ends up being placed in many and varied locations depending on the distribution and also between versions. Moreover, because the data is stored in varied locations volume management becomes a chore and being able to get to your data centrally can cause grief as and administrator tries to shuffle around data and partitions.

From this problem it would seem that the solution is to, once and for all, move the data. This notion is completely untenable because third party applications will want to reference this data in areas that are 'standard' unto themselves.

Solution
----------------------------

We propose a standard for volume management that keeps user and customer data centralized. This gives the customer the following advantages.

  * Centralized data is easier to locate and is therefore easier to backup
  * Centralized data can be added nicely to clustered volumes
  * Additional storage can be added and shows up in the same general location
  * Easier data and service migrations between servers

With this centralized data, Webconfig will use the 'bind mount' method to allocate the data where it is supposed to go.

TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2010-03-25 15:17 user2 New Issue
2010-03-25 15:17 user2 Status new => assigned
2010-03-25 15:17 user2 Assigned To => dloper
2010-05-20 11:40 user2 Target Version 5.2 => 6.0
2012-12-04 12:04 user2 Target Version 6 Future => 6.4.0 Alpha 1
2012-12-04 12:05 user2 Status assigned => resolved
2012-12-04 12:05 user2 Fixed in Version => 6.4.0 Alpha 1
2012-12-04 12:05 user2 Resolution open => fixed
2013-04-26 19:44 user2 Status resolved => closed