Back to bug 1944769
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Adam King | 2021-04-21 16:11:47 UTC | Status | NEW | ASSIGNED |
| CC | adking | |||
| Assignee | jolmomar | adking | ||
| Red Hat One Jira (issues.redhat.com) | 2021-05-27 10:08:22 UTC | Link ID | Red Hat Issue Tracker RHCEPH-48 | |
| Sebastian Wagner | 2021-05-31 12:47:32 UTC | Priority | unspecified | medium |
| CC | sewagner | |||
| Sebastian Wagner | 2021-08-11 11:37:55 UTC | Status | ASSIGNED | POST |
| Ken Dreyer (Red Hat) | 2021-09-28 20:42:13 UTC | Fixed In Version | ceph-16.2.6-1.el8cp | |
| Status | POST | MODIFIED | ||
| errata-xmlrpc | 2021-09-28 21:21:10 UTC | Status | MODIFIED | ON_QA |
| Ameena Suhani S H | 2021-10-26 07:16:24 UTC | QA Contact | vashastr | sunnagar |
| Rahul Lepakshi | 2021-11-02 05:57:14 UTC | QA Contact | sunnagar | rlepaksh |
| CC | rlepaksh | |||
| Rahul Lepakshi | 2021-11-02 14:41:10 UTC | Flags | needinfo?(adking) | |
| Adam King | 2021-11-02 17:37:37 UTC | Flags | needinfo?(adking) | |
| Rahul Lepakshi | 2021-11-08 11:12:38 UTC | Status | ON_QA | VERIFIED |
| Lijo Stephen Thomas | 2021-12-24 07:34:08 UTC | CC | lithomas | |
| Geo Jose | 2021-12-24 11:00:22 UTC | CC | gjose | |
| Aron Gunn | 2022-01-12 22:33:24 UTC | CC | agunn | |
| Blocks | 2031073 | |||
| Docs Contact | knortema | |||
| Aron Gunn | 2022-01-25 19:49:45 UTC | Docs Contact | agunn | |
| Flags | needinfo?(adking) | |||
| Adam King | 2022-01-25 21:43:04 UTC | Doc Text | Feature: Users may specify custom images for monitoring stack daemons at bootstrap time by passing a config file. This would be done by creating a config file formatted as [mgr] mgr/cephadm/container_image_grafana = <grafana-image-name> mgr/cephadm/container_image_alertmanager = <alertmanager-image-name> mgr/cephadm/container_image_prometheus = <prometheus-image-name> mgr/cephadm/container_image_node_exporter = <node-exporter-image-name> and then passing it to the bootstrap command with "--config <config-file-name>". Keep in mind if you have other config options you'd like to assimilate at bootstrap already you can simply add lines like the ones above to your config file before passing to bootstrap. Reason: So tat users could bootstrap their cluster with the correct monitoring stack images already set Result: Users can now bootstrap their clusters with the correct monitoring stack images set | |
| Flags | needinfo?(adking) | |||
| Red Hat Bugzilla | 2022-01-31 23:32:16 UTC | CC | sewagner | |
| Ranjini M N | 2022-02-16 05:39:07 UTC | Flags | needinfo?(adking) | |
| CC | rmandyam | |||
| Doc Text | Feature: Users may specify custom images for monitoring stack daemons at bootstrap time by passing a config file. This would be done by creating a config file formatted as [mgr] mgr/cephadm/container_image_grafana = <grafana-image-name> mgr/cephadm/container_image_alertmanager = <alertmanager-image-name> mgr/cephadm/container_image_prometheus = <prometheus-image-name> mgr/cephadm/container_image_node_exporter = <node-exporter-image-name> and then passing it to the bootstrap command with "--config <config-file-name>". Keep in mind if you have other config options you'd like to assimilate at bootstrap already you can simply add lines like the ones above to your config file before passing to bootstrap. Reason: So tat users could bootstrap their cluster with the correct monitoring stack images already set Result: Users can now bootstrap their clusters with the correct monitoring stack images set | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users could only use the default images for the monitoring stack in a storage cluster. With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: + .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- + You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. |
||
| Adam King | 2022-02-16 18:28:13 UTC | Flags | needinfo?(adking) | needinfo?(rmandyam) |
| Ranjini M N | 2022-02-17 10:25:16 UTC | Flags | needinfo?(rmandyam) | |
| Doc Text | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users could only use the default images for the monitoring stack in a storage cluster. With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: + .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- + You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users had to adjust the image used for their monitoring stack daemons manually after bootstrapping the cluster With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: + .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- + You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. |
||
| Aron Gunn | 2022-02-21 17:29:51 UTC | Docs Contact | agunn | rmandyam |
| Rahul Lepakshi | 2022-02-25 06:42:23 UTC | Flags | needinfo?(adking) | |
| Adam King | 2022-02-28 13:48:35 UTC | Flags | needinfo?(adking) | |
| Ranjini M N | 2022-03-08 16:25:16 UTC | Doc Text | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users had to adjust the image used for their monitoring stack daemons manually after bootstrapping the cluster With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: + .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- + You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users had to adjust the image used for their monitoring stack daemons manually after bootstrapping the cluster With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. |
| Ranjini M N | 2022-03-09 06:12:23 UTC | Doc Text | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users had to adjust the image used for their monitoring stack daemons manually after bootstrapping the cluster With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_ option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. | .Users can now bootstrap their storage clusters with custom monitoring stack images Previously, users had to adjust the image used for their monitoring stack daemons manually after bootstrapping the cluster With this release, you can specify custom images for monitoring stack daemons during bootstrap by passing a configuration file formatted as follows: .Syntax [source,subs="verbatim,quotes"] ---- [mgr] mgr/cephadm/container_image_grafana = _GRAFANA_IMAGE_NAME_ mgr/cephadm/container_image_alertmanager = _ALERTMANAGER_IMAGE_NAME_ mgr/cephadm/container_image_prometheus = _PROMETHEUS_IMAGE_NAME_ mgr/cephadm/container_image_node_exporter = _NODE_EXPORTER_IMAGE_NAME_ ---- You can run bootstrap with the `--config _CONFIGURATION_FILE_NAME_` option in the command. If you have other configuration options, you can simply add the lines above in your configuration file before bootstrapping the storage cluster. |
| errata-xmlrpc | 2022-04-04 08:00:33 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2022-04-04 10:20:36 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2022-04-04 10:20:36 UTC | |||
| errata-xmlrpc | 2022-04-04 10:21:00 UTC | Link ID | Red Hat Product Errata RHSA-2022:1174 | |
| Manisha Saini | 2023-01-29 13:22:45 UTC | CC | msaini | |
| Vivek Das | 2023-03-30 16:22:23 UTC | CC | vdas |
Back to bug 1944769