add and change the configuration steps to enable latest version of QAT
driver on QAT based encryption and compression
Signed-off-by: Miaomiao Liu <miaomiao.liu@intel.com>
This changes the string
"tenant$<user>"
to
'tenant$<user>'
in order to avoid users running into confusing
shell expansion behavior.
Hat tip to IcePic.
Signed-off-by: Zac Dover <zac.dover@gmail.com>
rgw: Add rgw rate limiting per user and per bucket
Reviewed-by: Daniel Gryniewicz <dang@redhat.com>
Reviewed-by: Yuval Lifshitz <ylifshit@redhat.com>
Reviewed-by: Casey Bodley <cbodley@redhat.com>
After working with notification configurations, it seemed to make
more sense to organize the different lifecycle notification sub-types
along the same lines as the official AWS ones. So, there are now
ObjectExpirationCurrent and ObjectExpirationNoncurrent types, and
an ObjectExpiration wildcard. Similarly, ObjectTransition
contains Current and Noncurrent sub-types.
Note that I have defined an ObjectExpirationAbortMPU notification
sub-type, but do not currently generate it--this is to avoid changing
the rgw::sal interface, but most likely we would support this in
future.
Signed-off-by: Matt Benjamin <mbenjamin@redhat.com>
The new resource returns an array of informational data, which
currently consists of the RADOS cluster fsid as "cluster_fsid."
Fixes: https://tracker.ceph.com/issues/51432
Signed-off-by: Matt Benjamin <mbenjamin@redhat.com>
in f13c6914eba9ad05c7bcff6eda81bb858f0f2349, we switched to a static 64k
parse buffer. this gives us a lot of room to raise the header_limit
above 4k
adds a "max_header_size" frontend option with default 16k and maximum
value equal to the 64k parse buffer size
Signed-off-by: Casey Bodley <cbodley@redhat.com>
With commit#81ad226, aws auth v4 rquires region name for remote
endpoint connection. Include the same in the tier parameters.
& misc fixes
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
For versioned and locked objects, similar semantics as that of LifecycleExpiration are applied as stated below -
If the bucket versioning is enabled and the object transitioned to cloud is
- current version, irrespective of what the config option "retain_object" value is, the object is not deleted but instead delete marker is created on the source rgw server.
- noncurrent version, it is deleted or retained based on the config option "retain_object" value.
If the object is locked, and is
- current version, it is transitioned to cloud post which it is made noncurrent with delete marker created.
- noncurrent version, transition is skipped.
Also misc rebase fixes and cleanup -
* Rename config option to "retain_head_object"
to reflect its functionality to keep head object post transitioning
to cloud if enabled
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
Currently the transition is supported to cloud providers
that are compatible with AWS/S3. Hence change the tier-type to
cloud-s3 to configure the S3 style endpoint details.
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
If the object is versioned, to avoid objects getting overwritten
post transition to cloud, append object versionID to the target
object name
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
Also to avoid object name collisions across various buckets
post cloud transition, add bucket name to the object prefix.
Signed-off-by: Soumya Koduri <skoduri@redhat.com>
Admins may setup different pools for RGW objects and
having the StorageClass field mutable allows the steering
of RGW objects to the proper pools.
Signed-off-by: Curt Bruns <curt.e.bruns@gmail.com>
The adminOps API for Modify User checks for user-caps value in the
request but does handle that in later code path. Caps have seperate apis
add_cap and remove_cap already present to modify exisitng caps in user.
Hence removing unused cap variables in RGWOp_User_Modify::execute().
Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
