You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than importing existing VGs we now create the PV's and the VG itself.
On destruction, if the VG has no non-mayastor LVs then we destroy it, otherwise
we leave it behind, untagged.
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
Users can create new Mayastor pools with the LVM backend type.
34
+
35
+
2. LVM Integration
36
+
37
+
Extend Mayastor to integrate with LVM.
38
+
Implement LVM-specific logic for pool and replica creation, replica resizing, and snapshot management.
39
+
Ensure seamless interaction between Mayastor and LVM.
40
+
41
+
3. Replication (HA)
42
+
43
+
Extend Mayastor’s replication mechanisms to work with LVM-backed logical units.
44
+
In short, make LVM backed volumes highly available across nodes.
45
+
46
+
4. Volume Management
47
+
48
+
Mayastor will expose LVM volume management features through its pool API.
49
+
Users can resize volumes online.
50
+
Snapshots are managed transparently.
51
+
52
+
## Conclusion
53
+
54
+
By integrating LVM with Mayastor, you can leverage the benefits of both technologies. LVM provides dynamic volume management, while Mayastor abstracts storage complexities, allowing you to focus on your applications.
0 commit comments