Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
44: Completion 2.3, 46: Completion 2.3. bk maint, 48, 50: Validation/Enforcement, 1: Recovery to productivity
-
10
Description
the customer needs to save backups on their internal storage with S3 compatible API.
In essence, they need to have something like this:
cbbackupmgr config a [s3://couchbase_s3_bucket/archive] -r repo --obj-staging-dir /tmp/asd **obj-endpoint <endpoint address> --obj-access-key-id ** --obj-secret-access-key ** -obj-region ****
inside the backup resource.
the command line parameter -obj-endpoint is an optional parameter with couchbase server. and CAO only supports mandatory parameters. And hence, support for this optional parameter is not implemented within CAO. Based on customer request, we need to add -obj-endpoint parameter for backup to S3 with CAO.
Attachments
Issue Links
- relates to
-
K8S-2579 Object Endpoint & IAM Role Backup Testing
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to CBSE-10599 [ CBSE-10599 ] |
Description |
the customer needs to save backups on their internal storage with S3 compatible API.
In essence, they need to have something like this: |cbbackupmgr config -a s3://couchbase_s3_bucket/archive -r repo --obj-staging-dir /tmp/asd **-*-obj-endpoint* <endpoint address> --obj-access-key-id ** --obj-secret-access-key ** --obj-region CCMCOHCLU2| inside the backup resource. the command line parameter *--obj-endpoint* is an optional parameter with couchbase server. and CAO only supports mandatory parameters. And hence, support for this optional parameter is not implemented within CAO. Based on customer request, we need to add *--obj-endpoint* parameter for backup to S3 with CAO. |
the customer needs to save backups on their internal storage with S3 compatible API.
In essence, they need to have something like this: cbbackupmgr config -a [s3://couchbase_s3_bucket/archive] -r repo --obj-staging-dir /tmp/asd **-*-obj-endpoint* <endpoint address> --obj-access-key-id ** --obj-secret-access-key ** --obj-region **** inside the backup resource. the command line parameter *--obj-endpoint-* is an optional parameter with couchbase server. and CAO only supports mandatory parameters. And hence, support for this optional parameter is not implemented within CAO. Based on customer request, we need to add *-obj-endpoint* parameter for backup to S3 with CAO. |
Description |
the customer needs to save backups on their internal storage with S3 compatible API.
In essence, they need to have something like this: cbbackupmgr config -a [s3://couchbase_s3_bucket/archive] -r repo --obj-staging-dir /tmp/asd **-*-obj-endpoint* <endpoint address> --obj-access-key-id ** --obj-secret-access-key ** --obj-region **** inside the backup resource. the command line parameter *--obj-endpoint-* is an optional parameter with couchbase server. and CAO only supports mandatory parameters. And hence, support for this optional parameter is not implemented within CAO. Based on customer request, we need to add *-obj-endpoint* parameter for backup to S3 with CAO. |
the customer needs to save backups on their internal storage with S3 compatible API.
In essence, they need to have something like this: cbbackupmgr config a [s3://couchbase_s3_bucket/archive] -r repo --obj-staging-dir /tmp/asd ***obj-endpoint* <endpoint address> --obj-access-key-id ** --obj-secret-access-key ** -obj-region **** inside the backup resource. the command line parameter *-obj-endpoint* is an optional parameter with couchbase server. and CAO only supports mandatory parameters. And hence, support for this optional parameter is not implemented within CAO. Based on customer request, we need to add *-obj-endpoint* parameter for backup to S3 with CAO. |
Rank | Ranked lower |
Rank | Ranked higher |
Rank | Ranked higher |
Rank | Ranked higher |
Link | This issue blocks CBSE-10907 [ CBSE-10907 ] |
Assignee | Simon Murray [ simon.murray ] | Alex Emery [ JIRAUSER26037 ] |
Sprint | 44: Completion 2.3 [ 1856 ] |
Rank | Ranked higher |
Status | Open [ 1 ] | In Progress [ 3 ] |
Sprint | 44: Completion 2.3 [ 1856 ] | 44: Completion 2.3, 46: Completion 2.3. bk maint [ 1856, 1877 ] |
Story Points | 1 | 10 |
Sprint | 44: Completion 2.3, 46: Completion 2.3. bk maint [ 1856, 1877 ] | 44: Completion 2.3, 46: Completion 2.3. bk maint, 48 [ 1856, 1877, 1889 ] |
Sprint | 44: Completion 2.3, 46: Completion 2.3. bk maint, 48 [ 1856, 1877, 1889 ] | 44: Completion 2.3, 46: Completion 2.3. bk maint, 48, 50: Validation/Enforcement [ 1856, 1877, 1889, 1890 ] |
Sprint | 44: Completion 2.3, 46: Completion 2.3. bk maint, 48, 50: Validation/Enforcement [ 1856, 1877, 1889, 1890 ] | 44: Completion 2.3, 46: Completion 2.3. bk maint, 48, 50: Validation/Enforcement, 1 [ 1856, 1877, 1889, 1890, 1891 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Simon Murray can it be included in CAO 2.3 without having any major impact on the expected GA timeline(Nov/Dec)?