Project

General

Profile

Actions

Cleanup #64708

closed

mgr/dashboard: Mark placement targets as non-required

Added by Afreen Misbah about 2 months ago. Updated 24 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Component - RGW
Target version:
-
% Done:

100%

Tags:
backport_processed
Backport:
squid,reef
Reviewed:
Affected Versions:
Pull request ID:

Description

What are Placement Targets ?

Placement targets control which Pools are associated with a particular bucket. A bucket’s placement target is selected on creation, and cannot be modified.
Where are they set ? Where to edit them ?
Zonegroup and zones

Placement target details are present in zonegroup and zone. Be default a default placement target is created and used.
Users

RGW Users can also se a default placement for themseleves which will the put a Location constraint on the buckets and then buckets will use that placement target only
LocationConstraint

Passing a particular placement target in LocationConstraint will override above two and use the passed one for bucket.

Ceph dashboard UI allows easy way to set that!
Having said that, in case users dont set this then it will go to:

1. Users’ default placement

2. If that is not found, it will default to zonegroup’s default placement which is always present.

Working of placement targets

1. Create a bucket without specifying any placement target and choose a user which has no default placement set

This will create a bucket with default placement target present on zonegroup

2. Create a bucket without specifying any placement target and choose a user which has a default placement set

This will create a bucket with default placement target present in user’s config

3. Create a bucket specifying any placement target and choose a user which has a default placement set

This will create a bucket with placement target selected by user overriding what present on user and zonegroup

For UI

- It makes sense to mark it as optional and not required as per above findings

- Also, since this setting has various defaults we can move it to advanced


Related issues 2 (0 open2 closed)

Copied to Dashboard - Backport #65210: squid: mgr/dashboard: Mark placement targets as non-requiredResolvedAfreen MisbahActions
Copied to Dashboard - Backport #65211: reef: mgr/dashboard: Mark placement targets as non-requiredResolvedAfreen MisbahActions
Actions #1

Updated by Afreen Misbah about 2 months ago

  • Description updated (diff)
Actions #2

Updated by Afreen Misbah about 2 months ago

  • Status changed from New to In Progress
Actions #3

Updated by Afreen Misbah about 2 months ago

  • Description updated (diff)
Actions #4

Updated by Afreen Misbah about 2 months ago

  • Description updated (diff)
Actions #5

Updated by Afreen Misbah about 2 months ago

  • Status changed from In Progress to Fix Under Review
  • % Done changed from 0 to 80
Actions #6

Updated by Afreen Misbah about 2 months ago

  • Pull request ID set to 55953
Actions #7

Updated by Afreen Misbah about 1 month ago

  • % Done changed from 80 to 90
Actions #8

Updated by Afreen Misbah about 1 month ago

  • Subject changed from mgr/dashboard: Improvement in Placement targets in bucket form to mgr/dashboard: Mark placement targets as non-required
  • Description updated (diff)
Actions #9

Updated by Afreen Misbah about 1 month ago

  • Description updated (diff)
Actions #10

Updated by Afreen Misbah about 1 month ago

  • Status changed from Fix Under Review to Resolved
  • % Done changed from 90 to 100
Actions #11

Updated by Afreen Misbah about 1 month ago

  • Tracker changed from Tasks to Cleanup
  • Status changed from Resolved to Pending Backport
  • Backport set to squid,reef
Actions #12

Updated by Backport Bot about 1 month ago

  • Copied to Backport #65210: squid: mgr/dashboard: Mark placement targets as non-required added
Actions #13

Updated by Backport Bot about 1 month ago

  • Copied to Backport #65211: reef: mgr/dashboard: Mark placement targets as non-required added
Actions #14

Updated by Backport Bot about 1 month ago

  • Tags set to backport_processed
Actions #15

Updated by Nizamudeen A 24 days ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF