[Service] Alternative location for volumes#1105
Merged
Conversation
5e39176 to
9821f97
Compare
9821f97 to
35884eb
Compare
cde6b9b to
6c7673e
Compare
6c7673e to
c302e1e
Compare
Contributor
joseivanlopez
left a comment
There was a problem hiding this comment.
Looks good, but I miss a changelog entry. The only bad thing is that I will eat a lot of conflicts with #1068.
|
|
||
| # What to do to allocate the volume | ||
| # | ||
| # @return [Symbol] see .targets |
Contributor
There was a problem hiding this comment.
I think it needs brackets, see {.targets}
| TargetDevice s | ||
| TargetVG s | ||
| Target s | ||
| TargetDevice s (only makes sense if Target is not default) |
Contributor
There was a problem hiding this comment.
The equivalent for the default device are called Target and Device. I am not sure if we should follow the same naming or not.
Contributor
Author
There was a problem hiding this comment.
I like the current names because it shows the relationship between both fields. I mean, TargetDevice is actually some kind of "details" field for the Target one.
Contributor
There was a problem hiding this comment.
Ok, makes sense. Then, I will adapt my PR to follow the same approach.
Merged
imobachgs
added a commit
that referenced
this pull request
May 17, 2024
Prepare for releasing Agama 8. It includes the following pull requests: * #884 * #886 * #914 * #918 * #956 * #957 * #958 * #959 * #960 * #961 * #962 * #963 * #964 * #965 * #966 * #969 * #970 * #976 * #977 * #978 * #979 * #980 * #981 * #983 * #984 * #985 * #986 * #988 * #991 * #992 * #995 * #996 * #997 * #999 * #1003 * #1004 * #1006 * #1007 * #1008 * #1009 * #1010 * #1011 * #1012 * #1014 * #1015 * #1016 * #1017 * #1020 * #1022 * #1023 * #1024 * #1025 * #1027 * #1028 * #1029 * #1030 * #1031 * #1032 * #1033 * #1034 * #1035 * #1036 * #1038 * #1039 * #1041 * #1042 * #1043 * #1045 * #1046 * #1047 * #1048 * #1052 * #1054 * #1056 * #1057 * #1060 * #1061 * #1062 * #1063 * #1064 * #1066 * #1067 * #1068 * #1069 * #1071 * #1072 * #1073 * #1074 * #1075 * #1079 * #1080 * #1081 * #1082 * #1085 * #1086 * #1087 * #1088 * #1089 * #1090 * #1091 * #1092 * #1093 * #1094 * #1095 * #1096 * #1097 * #1098 * #1099 * #1100 * #1102 * #1103 * #1104 * #1105 * #1106 * #1109 * #1110 * #1111 * #1112 * #1114 * #1116 * #1117 * #1118 * #1119 * #1120 * #1121 * #1122 * #1123 * #1125 * #1126 * #1127 * #1128 * #1129 * #1130 * #1131 * #1132 * #1133 * #1134 * #1135 * #1136 * #1138 * #1139 * #1140 * #1141 * #1142 * #1143 * #1144 * #1145 * #1146 * #1147 * #1148 * #1149 * #1151 * #1152 * #1153 * #1154 * #1155 * #1156 * #1157 * #1158 * #1160 * #1161 * #1162 * #1163 * #1164 * #1165 * #1166 * #1167 * #1168 * #1169 * #1170 * #1171 * #1172 * #1173 * #1174 * #1175 * #1177 * #1178 * #1180 * #1181 * #1182 * #1183 * #1184 * #1185 * #1187 * #1188 * #1189 * #1190 * #1191 * #1192 * #1193 * #1194 * #1195 * #1196 * #1198 * #1199 * #1200 * #1201 * #1203 * #1204 * #1205 * #1206 * #1207 * #1208 * #1209 * #1210 * #1211 * #1212 * #1213 * #1214 * #1215 * #1216 * #1217 * #1219 * #1220 * #1221 * #1222 * #1223 * #1224 * #1225 * #1226 * #1227 * #1229
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The storage proposal allows to specify what to do in order to allocate any volume:
Everything is possible, no matter whether the default target is a disk or a new LVM VG.
So far, it was not possible to use the Agama D-Bus settings to specify that to the proposal, so all volumes always used the default location.
Solution
This adds two new attributes to the D-Bus definition of a volume:
TargetandTargetDevice.Internally, this is represented by a new class
VolumeLocationwith two attributes:target: which specifies how to allocate the volumedevice: the name of the target device, the exact meaning depends ontargetThe new class and the possible targets follow the same approach of
SpaceSettingsand its policies.Testing
Screenshots
Hacking the web UI to set Target to
filesystemand TargetDevice to/dev/vdb5(which contains a Btrfs file system).Hacking the web UI to set Target to
new_vgand TargetDevice to/dev/vdc.