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

[FEATURE]: Add an existing protect volume to a storage group #51

Open
SerDroide opened this issue Oct 25, 2024 · 0 comments · May be fixed by #52
Open

[FEATURE]: Add an existing protect volume to a storage group #51

SerDroide opened this issue Oct 25, 2024 · 0 comments · May be fixed by #52
Labels
needs-triage Triage required type/feature-request This is the default label associated with a feature request issue.

Comments

@SerDroide
Copy link

Describe the solution you'd like
I would like that this condition should not raise an error when volume is srdf protected

Describe alternatives you've considered
I was not able to find any valid alternative

Additional context
With current collection implementation it is not possible to handle two hosts/clusters that have volumes that share the same protection (rdf groups). The change I propose will allow that, because will be possible to create a new volume attached to the shared SG and later add it also to the child sg.

Shared SG

classDiagram
  port_group_1 -- mv_1
  port_group_1 -- mv_2

  child_sg_1 -- volume1
  child_sg_1 -- volume2

  host_group_1 -- host_1

  shared_sg_1 -- volume2
  shared_sg_1 -- volume1
  shared_sg_1 -- volume3
  shared_sg_1 -- volume4

  rdf_group_1 -- shared_sg_1
  rdf_group_2 -- shared_sg_1

  parent_sg_1 -- child_sg_1

  host_1 -- mv_1
  mv_1 -- parent_sg_1

  parent_sg_2 -- child_sg_2
  child_sg_2 -- volume3
  child_sg_2 -- volume4

  mv_2 -- parent_sg_2
  mv_2 -- host_group_1

  style rdf_group_1 fill:blue
  style rdf_group_2 fill:blue

  style volume1 fill:green
  style volume2 fill:green
  style volume3 fill:green
  style volume4 fill:green

  style shared_sg_1 fill:Black

  style mv_1 fill:DeepPink
  style mv_2 fill:DeepPink

  style child_sg_1 fill:DarkCyan
  style child_sg_2 fill:DarkCyan

  style parent_sg_1 fill:CornflowerBlue
  style parent_sg_2 fill:CornflowerBlue

  style host_1 fill:SaddleBrown
  style host_group_1 fill:Chocolate

  style port_group_1 fill:RebeccaPurple

  class volume1{
    host volume
  }

  class volume2{
    host volume
  }

  class volume3{
    shared volume
  }

  class volume4{
    shared volume
  }

  class child_sg_1{
    srp: SRP_1
    service_level: Diamond
    compression: true
  }

  class child_sg_2{
    srp: SRP_1
    service_level: Diamond
    compression: true
  }

  class shared_sg_1{
    srp: None
    service_level: None
    compression: false
  }

  class parent_sg_1{
    srp: None
    service_level: None
    compression: false
  }

  class parent_sg_2{
    srp: None
    service_level: None
    compression: false
  }

  class rdf_group_1{
    Asynchronous
  }

  class rdf_group_2{
    Active
  }

  class mv_1{
  }

  class mv_2{
  }

  class host_1{
    flags
    initiators
    - aaaaaaaaaaaaaaa9
    - aaaaaaaaaaaaaaa8
  }

  class host_group_1{
  }

  class port_group_1{
  }
Loading
@SerDroide SerDroide added needs-triage Triage required type/feature-request This is the default label associated with a feature request issue. labels Oct 25, 2024
@SerDroide SerDroide linked a pull request Oct 25, 2024 that will close this issue
9 tasks
@anupamaloke anupamaloke linked a pull request Oct 25, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Triage required type/feature-request This is the default label associated with a feature request issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant