Back to bug 2109224

Who When What Removed Added
RHEL Program Management 2022-07-20 17:17:52 UTC Keywords FutureFeature
Red Hat One Jira (issues.redhat.com) 2022-07-20 17:23:19 UTC Link ID Red Hat Issue Tracker RHCEPH-4862
Matthew Secaur 2022-07-20 17:40:41 UTC Severity unspecified low
Lijo Stephen Thomas 2022-07-20 18:36:17 UTC CC lithomas
Geo Jose 2022-07-22 04:46:51 UTC CC gjose
jeremy 2022-07-28 19:03:03 UTC CC jeremy.coulombe
Redouane Kachach Elhichou 2022-09-02 09:26:02 UTC Assignee adking rkachach
CC rkachach
Redouane Kachach Elhichou 2022-10-10 13:34:42 UTC Status NEW ASSIGNED
Veera Raghava Reddy 2022-12-18 05:37:00 UTC QA Contact mgowri vdas
Red Hat Bugzilla 2022-12-31 23:38:31 UTC Assignee rkachach adking
CC rkachach
Red Hat Bugzilla 2023-01-01 05:37:24 UTC Assignee adking nobody
Red Hat Bugzilla 2023-01-01 08:28:56 UTC Docs Contact asriram
Red Hat Bugzilla 2023-01-01 08:46:19 UTC QA Contact vdas
Alasdair Kergon 2023-01-04 04:51:02 UTC Assignee nobody rkachach
Alasdair Kergon 2023-01-04 04:52:03 UTC QA Contact vdas
Alasdair Kergon 2023-01-04 05:36:47 UTC CC rkachach
Adam King 2023-04-12 21:28:34 UTC CC adking
Status ASSIGNED POST
errata-xmlrpc 2023-04-13 05:30:52 UTC Fixed In Version ceph-17.2.6-17.el9cp
Status POST MODIFIED
CC tserlin
Status MODIFIED ON_QA
Vivek Das 2023-04-24 07:25:20 UTC QA Contact vdas msaini
Manisha Saini 2023-04-27 04:54:07 UTC QA Contact msaini vpapnoi
Vinayak Papnoi 2023-04-27 11:56:56 UTC Status ON_QA VERIFIED
Akash Raj 2023-05-03 06:19:54 UTC Docs Contact akraj
Flags needinfo?(rkachach)
CC akraj
Adam King 2023-05-03 14:55:52 UTC Doc Type If docs needed, set a value Enhancement
Flags needinfo?(rkachach)
Doc Text Feature: Can now have an rgw realm/zone/zonegroup created for you using a spec file using "ceph rgw realm bootstrap -i rgw_spec.yaml". This spec file should be modeled similar tothe one used to dpeloy rgw daemons using hte orchestrator, e.g.

rgw_realm: myrealm
rgw_zonegroup: myzonegroup
rgw_zone: myzone
placement:
hosts:
- rgw-host1
- rgw-host2
spec:
rgw_frontend_port: 5500

The command will then create the realm/zone/zonegroup and pass the spec on to the orchestrator which will then deploy the rgw daemons.

Reason: To try and streamline the process of setting up RGW on an RHCS cluster

Result: There is now an automated process combining RGW realm/zone/zonegroup creation along with deploying the RGW daemons. The inputs for this process (realm/zone/zonegroup names, RGW daemon placement) can be specified using a spec file.
Akash Raj 2023-05-08 02:35:02 UTC Blocks 2192813
Akash Raj 2023-05-18 05:34:46 UTC Doc Text Feature: Can now have an rgw realm/zone/zonegroup created for you using a spec file using "ceph rgw realm bootstrap -i rgw_spec.yaml". This spec file should be modeled similar tothe one used to dpeloy rgw daemons using hte orchestrator, e.g.

rgw_realm: myrealm
rgw_zonegroup: myzonegroup
rgw_zone: myzone
placement:
hosts:
- rgw-host1
- rgw-host2
spec:
rgw_frontend_port: 5500

The command will then create the realm/zone/zonegroup and pass the spec on to the orchestrator which will then deploy the rgw daemons.

Reason: To try and streamline the process of setting up RGW on an RHCS cluster

Result: There is now an automated process combining RGW realm/zone/zonegroup creation along with deploying the RGW daemons. The inputs for this process (realm/zone/zonegroup names, RGW daemon placement) can be specified using a spec file.
.Users can now create Ceph Object Gateway realm,zone, and zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command

With this release, to streamline the process of setting up Ceph Object Gateway on a {storage-product} cluster, users can create a Ceph Object Gateway realm/zone/zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command. The specification file should be modeled similar to the one that is used to deploy Ceph Object Gateway daemons using the orchestrator. The command then creates the realm,zone, and, zonegroup, and passes the specification on to the orchestrator, which then deploys the Ceph Object Gateway daemons.

.Example
----
rgw_realm: myrealm
rgw_zonegroup: myzonegroup
rgw_zone: myzone
placement:
hosts:
- rgw-host1
- rgw-host2
spec:
rgw_frontend_port: 5500
----
Akash Raj 2023-05-18 05:36:15 UTC Doc Text .Users can now create Ceph Object Gateway realm,zone, and zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command

With this release, to streamline the process of setting up Ceph Object Gateway on a {storage-product} cluster, users can create a Ceph Object Gateway realm/zone/zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command. The specification file should be modeled similar to the one that is used to deploy Ceph Object Gateway daemons using the orchestrator. The command then creates the realm,zone, and, zonegroup, and passes the specification on to the orchestrator, which then deploys the Ceph Object Gateway daemons.

.Example
----
rgw_realm: myrealm
rgw_zonegroup: myzonegroup
rgw_zone: myzone
placement:
hosts:
- rgw-host1
- rgw-host2
spec:
rgw_frontend_port: 5500
----
.Users can now create Ceph Object Gateway realm,zone, and zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command

With this release, to streamline the process of setting up Ceph Object Gateway on a {storage-product} cluster, users can create a Ceph Object Gateway realm, zone, and zonegroup using `ceph rgw realm bootstrap -i rgw_spec.yaml` command. The specification file should be modeled similar to the one that is used to deploy Ceph Object Gateway daemons using the orchestrator. The command then creates the realm,zone, and, zonegroup, and passes the specification on to the orchestrator, which then deploys the Ceph Object Gateway daemons.

.Example
----
rgw_realm: myrealm
rgw_zonegroup: myzonegroup
rgw_zone: myzone
placement:
hosts:
- rgw-host1
- rgw-host2
spec:
rgw_frontend_port: 5500
----
errata-xmlrpc 2023-06-15 09:07:51 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-06-15 09:15:33 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2023-06-15 09:15:33 UTC
errata-xmlrpc 2023-06-15 09:16:57 UTC Link ID Red Hat Product Errata RHSA-2023:3623

Back to bug 2109224