Back to bug 2005495
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| RHEL Program Management | 2021-09-17 19:10:39 UTC | Target Release | 18.0 | --- |
| Goutham Pacha Ravi | 2021-09-17 19:13:01 UTC | OS | Unspecified | All |
| Assignee | rhos-maint | cardasil | ||
| Hardware | Unspecified | All | ||
| Priority | high | medium | ||
| QA Contact | jhakimra | vhariria | ||
| Carlos da Silva | 2021-09-23 12:35:37 UTC | Target Release | --- | 18.0 |
| Target Milestone | --- | Upstream M1 | ||
| Status | NEW | ASSIGNED | ||
| RHEL Program Management | 2021-09-23 12:35:45 UTC | Target Release | 18.0 | --- |
| Carlos da Silva | 2021-09-24 13:05:57 UTC | Status | ASSIGNED | ON_DEV |
| Giulio Fidente | 2021-09-24 13:32:03 UTC | CC | gfidente | |
| Link ID | OpenStack gerrit 810792 | |||
| Carlos da Silva | 2021-09-24 13:44:08 UTC | Link ID | OpenStack gerrit 810790 OpenStack gerrit 810791 | |
| Carlos da Silva | 2021-10-04 12:32:00 UTC | Keywords | FeatureBackport | |
| Carlos da Silva | 2021-11-08 14:51:05 UTC | CC | vhariria | |
| QA Contact | vhariria | lkuchlan | ||
| Keywords | FeatureBackport | |||
| Carlos da Silva | 2021-11-08 14:57:42 UTC | Blocks | 2021176 | |
| Red Hat One Jira (issues.redhat.com) | 2021-11-18 15:00:06 UTC | Link ID | Red Hat Issue Tracker OSP-9678 | |
| Gregory Charot | 2022-01-06 14:05:17 UTC | Target Milestone | Upstream M1 | Alpha |
| Keywords | FutureFeature | FeatureBackport, Triaged | ||
| CC | gcharot | |||
| Carlos da Silva | 2022-08-04 14:38:44 UTC | CC | spower | |
| Status | ON_DEV | MODIFIED | ||
| Fixed In Version | openstack-tripleo-heat-templates-14.3.1-0.20220123001122.b9a3359 | |||
| Giulio Fidente | 2022-08-04 14:48:35 UTC | Target Milestone | Alpha | ga |
| Target Release | --- | 17.1 | ||
| RHEL Program Management | 2022-08-04 14:48:44 UTC | Target Release | 17.1 | --- |
| Gregory Charot | 2022-08-25 09:50:25 UTC | Target Milestone | ga | beta |
| Gregory Charot | 2022-08-30 09:50:11 UTC | Target Milestone | beta | z2 |
| RHEL Program Management | 2022-09-20 17:50:36 UTC | Target Release | --- | 17.1 |
| errata-xmlrpc | 2022-11-29 14:53:42 UTC | Status | MODIFIED | ON_QA |
| lkuchlan | 2022-12-05 06:08:50 UTC | Status | ON_QA | VERIFIED |
| Mikey Ariel | 2023-01-02 16:28:56 UTC | CC | mariel | |
| Giulio Fidente | 2023-04-19 16:31:21 UTC | Target Milestone | z2 | ga |
| Giulio Fidente | 2023-04-19 17:15:34 UTC | Target Milestone | ga | beta |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(cardasil) | |
| Goutham Pacha Ravi | 2023-08-09 14:52:11 UTC | Flags | needinfo?(cardasil) | |
| Doc Text | Feature: When configuring Shared File Systems service (manila) back end storage, cloud administrators now have the ability to specify an "Availability Zone" per storage back end via Director. Reason: Cloud Administrators might use an "Availability Zone" annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific availability zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different availability zones as opposed to denoting a single availability zone for all the back ends. Result: Director has new options to denote the storage availability zones. Each option corresponds to a supported storage backend driver. Please see the documentation to identify the corresponding option to the storage system in the deployment. |
|||
| Erin Peterson | 2023-08-09 18:33:15 UTC | CC | erpeters | |
| Doc Text | Feature: When configuring Shared File Systems service (manila) back end storage, cloud administrators now have the ability to specify an "Availability Zone" per storage back end via Director. Reason: Cloud Administrators might use an "Availability Zone" annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific availability zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different availability zones as opposed to denoting a single availability zone for all the back ends. Result: Director has new options to denote the storage availability zones. Each option corresponds to a supported storage backend driver. Please see the documentation to identify the corresponding option to the storage system in the deployment. | This enhancement allows cloud administrators to specify an Availability Zone by storage back end through director when configuring the Shared File Systems service (manila) back end storage. With this update, administrators can use an Availability Zone annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific Availability Zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different Availability Zones as opposed to denoting a single Availability Zone for all the back ends. Director has new options to denote the storage Availability Zones. Each option corresponds to a supported storage back end driver. For more information about Availability Zones, see _Configuring persistent storage_. |
||
| errata-xmlrpc | 2023-08-16 00:02:17 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:10:52 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:10:52 UTC | |||
| errata-xmlrpc | 2023-08-16 01:11:06 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 | |
| Jenny-Anne Lynch | 2023-08-16 09:36:03 UTC | CC | jelynch | |
| Doc Text | This enhancement allows cloud administrators to specify an Availability Zone by storage back end through director when configuring the Shared File Systems service (manila) back end storage. With this update, administrators can use an Availability Zone annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific Availability Zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different Availability Zones as opposed to denoting a single Availability Zone for all the back ends. Director has new options to denote the storage Availability Zones. Each option corresponds to a supported storage back end driver. For more information about Availability Zones, see _Configuring persistent storage_. | This enhancement allows cloud administrators to specify an Availability Zone by storage back end through director when configuring the Shared File Systems service (manila) back end storage. + With this update, administrators can use an Availability Zone annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific Availability Zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different Availability Zones as opposed to denoting a single Availability Zone for all the back ends. + Director has new options to denote the storage Availability Zones. Each option corresponds to a supported storage back end driver. For more information about Availability Zones, see _Configuring persistent storage_. |
||
| Jenny-Anne Lynch | 2023-08-17 09:50:59 UTC | Doc Text | This enhancement allows cloud administrators to specify an Availability Zone by storage back end through director when configuring the Shared File Systems service (manila) back end storage. + With this update, administrators can use an Availability Zone annotation to logically separate storage provisioning requests and to denote failure domains. Availability Zones configured by the administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific Availability Zones based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different Availability Zones as opposed to denoting a single Availability Zone for all the back ends. + Director has new options to denote the storage Availability Zones. Each option corresponds to a supported storage back end driver. For more information about Availability Zones, see _Configuring persistent storage_. | This enhancement allows cloud administrators to specify an Availability Zone (AZ) by storage back end through director when configuring the Shared File Systems service (manila) back-end storage. + With this update, administrators can use an AZ annotation to logically separate storage provisioning requests and to denote failure domains. AZs configured by administrators are exposed by the Shared File Systems service to end users. End users can request that their workloads be scheduled to specific AZs based on their needs. When configuring multiple storage back ends, administrators might want to tag each back end to different AZs as opposed to denoting a single AZ for all back ends. + Director has new options to denote the storage AZs. Each option corresponds to a supported storage back-end driver. For more information about AZs, see _Configuring persistent storage_. |
Back to bug 2005495