Description of problem: Openstack-designate package missing in RHOSP16 Version-Release number of selected component (if applicable): RHOSP16 Actual results: package missing in downstream Expected results: To get it merged in downstream Additional info: Few customer wish to test in downstream bits of RHOSP.
Hello, We need to have DNSaaS in the cloud because of multiple OpenShift deployments. We are splitting the OpenShift clusters per tenants so each tenant can have own resources for PaaS. Each tenant can create own DNS zone for cluster deployment and related api.cluster.<zone> and *.app.cluster.<zone> records as described in the documentation: https://docs.openshift.com/container-platform/4.3/installing/installing_openstack/installing-openstack-installer-custom.html#installation-osp-configuring-api-floating-ip_installing-openstack-installer-custom
DNSaas Designate was introduced as Tech Preview in RHOSP7. Designate was deprecated and removed in RHOSP14 onwards. Designate is no included in RHOSP15 or RHOSP16.0 We are evaluating support for Designate for RHOSP 17 planned for Q1 2021, this is on the roadmap but not confirmed. If we decide to add support for RHOSP17 then backport to RHOSP16 may be possible.
Hi Anita Tragler I cannot accept this. Packages were available until RHOSP 14, and now I stuck in the migration process to RHOSP 16. The packages availability does not assume mandatory support from RedHat and removing them from repos because of limitations of the TripleO is not acceptable. Designate is well approved DNSaaS solution for OpenStack and I suggest bringing it back until RedHat has another solution for this critical infrastructure part.
Just to clarify, this was not driven by what TripleO supports. Upstream TripleO does support Designate deployment now. I won't speculate on the reasons behind the deprecation as I wasn't involved in those discussions, but I can tell you it wasn't because of technical limitations in the software.
Hello Igor Tuinov Thank-you for your feedback. Designate packages will be added to OSP 16.1 as Tech Preview, please see Bug 1805883. Is it possible to get some feedback on how Nexign is using Designate today? We are currently evaluating support for Designate for OSP17 and looking to provide a basic DNSaaS solution with single backend and single zone. If necessary we can have a short call as well and appreciate your feedback on this. Thank-you -anita Anita Tragler Product Manager Networking
Hello Anita Tragler Thank you for starting the work, it is very crucial for us. We use Designate for developer's high-dynamic environments. Multiple tenants (the developer's projects in our case) have own DNS zone. Developers have tools to manage DNS records within the project scope, but Mistral workflows cover most of the cases (A/PTR records creation for VMs and dev stands). I have sent the details by email.