Ctrl K
ComunidadGuías…

config/s3tests.toml

Rama main · réplica de lectura del repositorio original.

Archivo original ↗Preguntar a KiBot
# Single-host profile for the ceph/s3-tests conformance suite.
#
#     ./scripts/start.sh -w s3tests
#     ./scripts/s3-tests.sh
#
# It differs from 1host.toml in one way that matters: three service accounts
# rather than one. Large parts of s3-tests are about what one account may do
# to another account's bucket, and with a single account those cases do not
# fail — they error in fixture setup and report nothing about predastore.
#
# RS(1,0) is one shard on one node with no parity. The suite measures the S3
# surface, not durability, so the narrowest stripe is the right one: it makes
# the run fast and keeps a shard-placement failure out of the results.
#
# The region is us-east-1 rather than the ap-southeast-2 the other profiles
# use. s3-tests builds its clients with an empty region_name and botocore
# resolves that to us-east-1, so every request signs for us-east-1 and any
# other region answers AuthorizationHeaderMalformed before a test runs.

version = 1
region = "us-east-1"

[rs]
data = 1
parity = 0

[[host]]
id = 1
addr = "127.0.0.1"
admin_port = 9099

  [[host.node]]
  id = 1
  role = "gate"
  port = 8443

  [[host.node]]
  id = 2
  role = "meta"
  port = 6660

  [[host.node]]
  id = 3
  role = "blob"
  port = 9991

# The main account. Same pair as every other shipped profile, so a session
# that starts this cluster can use the documented quick-start credentials.
[[auth]]
access_key_id = "AKIAIOSFODNN7EXAMPLE"
secret_access_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
account_id = "123456789012"

# The alt account, for the cross-account cases: ACLs, bucket policy, and every
# test that asserts one account is refused another's object.
[[auth]]
access_key_id = "AKIAI44QH8DHBEXAMPLE"
secret_access_key = "je7MtGbClwBF/2Zp9Utk/h3yCo8nvbEXAMPLEKEY"
account_id = "210987654321"

# The tenant account. s3-tests treats a tenant as a third identity in its own
# namespace; predastore has no tenant concept, so the cases that turn on
# namespacing are expected to fail rather than to be skipped.
[[auth]]
access_key_id = "AKIAIOSFODNN7TENANT0"
secret_access_key = "kPxRfiCYEXAMPLEKEY/K7MDENG/bTenantKey0"
account_id = "345678901234"