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

Change VG names for readability #811

Merged
merged 3 commits into from
Jan 15, 2024
Merged

Change VG names for readability #811

merged 3 commits into from
Jan 15, 2024

Conversation

toshipp
Copy link
Contributor

@toshipp toshipp commented Jan 11, 2024

We used different VG names on kind and minikube and the names are too agnostic, so it is hard to maintain. This PR assigns readable names and use same names on both kind and minikube.

Previously, the dc3 device-class was defined for DS LVMd, but not for
the systemd-service LVMd, except on node3. This was because we wanted to
schedule a pod using dc3 on a specific node to simplify the writing of
tests. However, since this can be achieved using nodeSelector, we can
now remove dc3 and synchronize the LVMd configuration.

Signed-off-by: Toshikuni Fukaya <toshikuni-fukaya@cybozu.co.jp>
We used different names in the kind and minikube environments. But it is
not a technical requirement, we should use same names to improve
readability.

Signed-off-by: Toshikuni Fukaya <toshikuni-fukaya@cybozu.co.jp>
The previous names are too agnostic. To make them easier to understand,
change their names according to their characters.

Signed-off-by: Toshikuni Fukaya <toshikuni-fukaya@cybozu.co.jp>
@@ -105,7 +102,7 @@ func testThinProvisioning() {
By("deploying multiple PVCS with total size < thinpoolsize * overprovisioning")
// The actual thinpool size is 4 GB . With an overprovisioning limit of 5, it should allow
// PVCs totalling upto 20 GB for each node
nodeName := "topolvm-e2e-worker2"
nodeName := "topolvm-e2e-worker"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We create a namespace for each It and delete the namespace after the spec of the It ends. Therefore, it is ok to use the same node.

@@ -191,7 +185,7 @@ func testThinProvisioning() {
It("should check overprovision limits", func() {
By("Deploying a PVC to use up the available thinpoolsize * overprovisioning")

nodeName := "topolvm-e2e-worker3"
nodeName := "topolvm-e2e-worker"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

ditto

@toshipp toshipp marked this pull request as ready for review January 12, 2024 01:37
@toshipp toshipp requested a review from a team as a code owner January 12, 2024 01:37
@daichimukai daichimukai merged commit bd1fee7 into main Jan 15, 2024
24 checks passed
@daichimukai daichimukai deleted the vgname branch January 15, 2024 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

3 participants