-
Notifications
You must be signed in to change notification settings - Fork 44
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
feature(storage): config support for generating physical volumes #1652
feature(storage): config support for generating physical volumes #1652
Conversation
d713541
to
6e01867
Compare
Pull Request Test Coverage Report for Build 11249392029Details
💛 - Coveralls |
8e21647
to
832a140
Compare
{ | ||
"name": "system", | ||
"physicalVolumes": [ | ||
"pv1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm actually not sure we currently support combining manually defined PVs and generated ones. I'm pretty sure it would be technically possible but probably it does not work with the current implementation of yast/yast-storage-ng#1392.
The algorithm now can combine EXISTING PVs (for a reused VG) with generated ones (for growing that existing VG). But likely no new manual PVs and automatic ones.
I will check how hard would be to add it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect it would be easy, but I have to double check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked and it would be possible by modifying the yast2-storage-ng algorithm a bit. But we decided to leave it for later, as part of a separate task internally tracked at https://trello.com/c/XAaoYdCL/578-storage-profile-improve-support-for-generating-lvm-physical-volumes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have adapted the schema to allow either aliases or 'generate'.
service/lib/agama/storage/config_conversions/from_json_conversions/volume_group.rb
Outdated
Show resolved
Hide resolved
387cec8
to
ea76bd1
Compare
- Solving encryption and filesystem configs is now done by the config solver. - JSON conversion only applies the values provided by the JSON data and expands 'generate' for partitions and logical volumes.
7ea8721
to
8f737ba
Compare
8f737ba
to
e4fe3db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#1652 adds support for configuring the automatic generation of LVM physical volumes. Read there the details about how the feature works. This pull request implements a first version of the functionality described there, including a couple of unit tests. Depends on yast/yast-storage-ng#1392
Update to release version 11. * #1495 * #1564 * #1617 * #1618 * #1625 * #1626 * #1627 * #1628 * #1630 * #1631 * #1632 * #1633 * #1634 * #1635 * #1636 * #1639 * #1640 * #1641 * #1642 * #1643 * #1644 * #1645 * #1646 * #1647 * #1648 * #1649 * #1650 * #1651 * #1652 * #1654 * #1655 * #1656 * #1657 * #1660 * #1663 * #1666 * #1667 * #1668 * #1670 * #1671 * #1673 * #1674 * #1675 * #1676 * #1677 * #1681 * #1682 * #1683 * #1684 * #1687 * #1688 * #1689 * #1690 * #1691 * #1692 * #1693 * #1694 * #1695 * #1696 * #1698 * #1699 * #1702 * #1703 * #1704 * #1705 * #1707 * #1708 * #1709 * #1710 * #1711 * #1712 * #1713 * #1714 * #1715 * #1716 * #1717 * #1718 * #1720 * #1721 * #1722 * #1723 * #1727 * #1728 * #1729 * #1731 * #1732 * #1733 * #1734 * #1735 * #1736 * #1737 * #1740 * #1741 * #1743 * #1744 * #1745 * #1746 * #1751 * #1753 * #1754 * #1755 * #1757 * #1762 * #1763 * #1764 * #1765 * #1766 * #1767 * #1769 * #1771 * #1772 * #1773 * #1774 * #1777 * #1778 * #1785 * #1786 * #1787 * #1788 * #1789 * #1790 * #1791 * #1792 * #1793 * #1794 * #1795 * #1796 * #1797 * #1798 * #1799 * #1800 * #1802 * #1803 * #1804 * #1805 * #1807 * #1808 * #1809 * #1810 * #1811 * #1812 * #1814 * #1815 * #1821 * #1822 * #1823 * #1824 * #1825 * #1826 * #1827 * #1828 * #1830 * #1831 * #1832 * #1833 * #1834 * #1835 * #1836 * #1837 * #1838 * #1839 * #1840 * #1841 * #1842 * #1843 * #1844 * #1845 * #1847 * #1848 * #1849 * #1850 * #1851 * #1854 * #1855 * #1856 * #1857 * #1860 * #1861 * #1863 * #1864 * #1865 * #1866 * #1867 * #1871 * #1872 * #1873 * #1875 * #1876 * #1877 * #1878 * #1880 * #1881 * #1882 * #1883 * #1884 * #1885 * #1886 * #1888 * #1889 * #1890
Add support to the storage config for using a generate section for physical volumes.
The generate section allows to indicate the target devices in which to automatically create physical volumes, if needed. Agama will try to create physical volumes to allocate the defined logical volumes. If an encryption section is provided by the generate section, then the new physical volumes will be encrypted.
Notes: