config.js

@@ -764,7 +764,8 @@ config.NSFS_REMOVE_PARTS_ON_COMPLETE = true;
 config.NSFS_BUF_POOL_WARNING_TIMEOUT = 2 * 60 * 1000;
 config.NSFS_SEM_WARNING_TIMEOUT = 10 * 60 * 1000;
 // number of rename retries in case of deleted destination directory
-config.NSFS_RENAME_RETRIES = 3;
+config.NSFS_RENAME_RETRIES = 10;
+config.NSFS_MKDIR_PATH_RETRIES = 3;
 
 config.NSFS_VERSIONING_ENABLED = true;
 config.NSFS_UPDATE_ISSUES_REPORT_ENABLED = true;
@@ -904,6 +905,8 @@ config.QUOTA_MAX_OBJECTS = Number.MAX_SAFE_INTEGER;
 //////////////////////////
 
 config.STS_DEFAULT_SESSION_TOKEN_EXPIRY_MS = 60 * 60 * 1000; // 1 hour
+config.STS_MIN_DURATION_SECONDS = 15 * 60; // 15 minutes
+config.STS_MAX_DURATION_SECONDS = 12 * 60 * 60; // 12 hours
 
 /////////////////////////
 // BLOCK STORE FS      //

docs/NooBaaNonContainerized/S3Ops.md

@@ -95,7 +95,7 @@ Warning: this policy allows `<account-name>` to run all S3 operations.
 ##### Principal Field:
 A bucket policy defines which principals can perform actions on the bucket. The Principal element specifies the user or account that is either allowed or denied access to a resource.
 Currently we support a couple of options:
-1. Grant anonymous permissions (all principals): either `"Principal": { "AWS": "*" }` or `"Principal": { "*" }`.
+1. All principals (includes anonymous account): either `"Principal": { "AWS": "*" }` or `"Principal": "*"`.
 2. Principal by account name: `"Principal": { "AWS": [ "<account-name-1>", "<account-name-2>", ... ,"<account-name-n>"] }`
 3. Principal by account ID: `"Principal": { "AWS": [ "<account-ID-1>", "<account-ID-2>", ... ,"<account-ID-n>"] }`
 

docs/dev_guide/ceph_s3_tests/ceph_s3_tests_guide.md

@@ -8,6 +8,7 @@
      4) Debug a Single Ceph S3 Test
      5) Compare to AWS Response (Inside Tester Pod)
      6) Examples
+     7) Run a Single Ceph S3 Test in NC deployment Manually
 * This guide describes developer steps to run Ceph S3 on a Noobaa system on minikube.
 
 ## General Settings For Ceph S3 Tests
@@ -287,4 +288,48 @@ S3TEST_CONF=${PWD}/src/test/system_tests/ceph_s3_tests/test_ceph_s3_config.conf
 
 Notice that even though test commands succeeded the test itself was skipped. The test prints `1 skipped` meaning one test was skipped
 
+## Run a Single Ceph S3 Test in NC deployment Manually
+
+### NC local on your machine
+#### Account creation
+Create the needed accounts for the Ceph configurations, for example: 
+1. ceph (main account)
+2. ceph_alt (an account that is used on tests when two different accounts are needed, this is the alternative account - for example I saw it used in one of the bucket policy tests)
+3. ceph_tenant  
+
+In cases that you don't need additional account you can simply copy the main account access keys in the ceph configuration file.
+
+To create the accounts in NC with access key and secret key that you chose is by running:  
+`sudo node src/cmd/manage_nsfs account add --name ceph --new_buckets_path <new-buckets-path> --access_key <access-key> --secret_key <secret-key> --uid <uid> --gid <gid>`   
+(more information can be found in [NooBaa CLI](./../../NooBaaNonContainerized/NooBaaCLI.md))  
+for example:  
+`sudo node src/cmd/manage_nsfs account add --name ceph --new_buckets_path /private/tmp/nsfs_root1 --access_key <access-key> --secret_key <secret-key> --uid 1001 --gid 1001`.  
+Note: before creating the account need to give permission to the `new_buckets_path`, in this example: `mkdir -p /private/tmp/nsfs_root1; sudo chmod 777 /private/tmp/nsfs_root1`.
+
+#### NSFS Server
+Start the NSFS server with: `sudo node src/cmd/nsfs --debug 5`  
+Note: on every code change you would need to stop the server (ctrl + c) and run it again.
+
+### Ceph S3 repository:
+1) Clone the repository [ceph/s3-test](https://github.com/ceph/s3-tests):  
+`git clone https://github.com/ceph/s3-tests.git`
+
+2) Edit the attached config, you can rename it and use this config only in the commands that you run, for example:  
+`cp s3tests.conf.SAMPLE test_nsfs_ceph_s3_config.conf`, inside the file change the following values `vi test_nsfs_ceph_s3_config.conf`:
+  - host = localhost
+  - port = 6443
+  - is_secure = True
+  - ssl_verify = False
+  - bucket prefix = your-name-{random}
+  - under "[s3 main]" under "main AWS access key" add the ceph account credentials
+  - under "[s3 alt]" under "alt AWS access key set in vstart.sh" add the ceph_alt credentials (if your tests do not need it you can copy the ceph credentials)
+  - under "[s3 tenant]" under "tenant AWS secret key set in vstart.sh" add 3. ceph_tenant credentials (if your tests do not need it you can copy the ceph credentials)
+  - user_id - it depends if your tests uses it and for what purpose, usually you can add the account id, I saw a case where it was for principal in bucket policy and there you can add the account name
+
+3) Run a single test by running:  
+`S3TEST_CONF=<configuration-file> tox -- <test-full-name>`  
+for example:  
+`S3TEST_CONF=test_nsfs_ceph_s3_config.conf tox -- s3tests_boto3/functional/test_s3.py::test_versioning_multi_object_delete_with_marker_create`.  
+Make sure that you run it from the Ceph repo: `pwd` will be `<path-to-ceph-S3-repo>/s3-tests`.  
+Note: In case you need install boto3 and tox: `python3 -m pip install boto3` and `python3 -m pip install tox`