Re: [openstack-dev] [cinder][puppet][kolla][helm][ansible] Change in Cinder backup driver naming
Thanks Sean! I did a quick sanity check on the backup part in the puppet-cinder module and there is no opinionated default value there which needs to be changed. Best regards On 09/27/2018 08:37 PM, Sean McGinnis wrote: This probably applies to all deployment tools, so hopefully this reaches the right folks. In Havana, Cinder deprecated the use of specifying the module for configuring backup drivers. Patch https://review.openstack.org/#/c/595372/ finally removed the backwards compatibility handling for configs that still used the old way. Looking through a quick search, it appears there may be some tools that are still defaulting to setting the backup driver name using the patch. If your project does not specify the full driver class path, please update these to do so now. Any questions, please reach out here or in the #openstack-cinder channel. Thanks! Sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder][puppet][kolla][helm][ansible] Change in Cinder backup driver naming
Thanks for the email Sean. https://review.openstack.org/605846 Fix Cinder backup to use full paths I think this should cover us, please let me know if we did things right. FYI: the docs all still seem to point at the old paths.. https://docs.openstack.org/cinder/latest/configuration/block-storage/backup-drivers.html On Thu, Sep 27, 2018 at 2:33 PM Sean McGinnis wrote: > > This probably applies to all deployment tools, so hopefully this reaches the > right folks. > > In Havana, Cinder deprecated the use of specifying the module for configuring > backup drivers. Patch https://review.openstack.org/#/c/595372/ finally removed > the backwards compatibility handling for configs that still used the old way. > > Looking through a quick search, it appears there may be some tools that are > still defaulting to setting the backup driver name using the patch. If your > project does not specify the full driver class path, please update these to do > so now. > > Any questions, please reach out here or in the #openstack-cinder channel. > > Thanks! > Sean > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mohammed Naser — vexxhost - D. 514-316-8872 D. 800-910-1726 ext. 200 E. mna...@vexxhost.com W. http://vexxhost.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder][puppet][kolla][helm][ansible] Change in Cinder backup driver naming
This probably applies to all deployment tools, so hopefully this reaches the right folks. In Havana, Cinder deprecated the use of specifying the module for configuring backup drivers. Patch https://review.openstack.org/#/c/595372/ finally removed the backwards compatibility handling for configs that still used the old way. Looking through a quick search, it appears there may be some tools that are still defaulting to setting the backup driver name using the patch. If your project does not specify the full driver class path, please update these to do so now. Any questions, please reach out here or in the #openstack-cinder channel. Thanks! Sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
