Hi Christian,
We just had the virtual PTG last week and discussed this topic[1].
As you know, we completed the specification document and merged it during Antelope. So the community agrees on the plan to implement. At this point it just needs developers to start work on the patches.
During the PTG session no one attending was able to pick up this specification for development, so we did not highlight it as a feature targeted for Bobcat. I did say that I am willing to help anyone that has developer resources work on it, I just cannot lead that effort during Bobcat.
So if you are willing to work on the patches, we will help out as we can with reviews and answering questions, etc.
Michael
[1] https://etherpad.opendev.org/p/march2023-ptg-designate
On Mon, Apr 3, 2023 at 12:36 AM Christian Rohmann christian.rohmann@inovex.de wrote:
Hey Michael,
On 18/01/2023 23:50, Michael Johnson wrote:
Personally I think the specification is very close to being complete, I think we just need to agree on these last few design items and we can push for reviews.
As I was looking at these agent based drivers, it was very obvious that the catalog zones may eliminate the need for some of the agent based drivers. That is awesome and your proposal to add catalog zone support is perfectly timed.
Michael
On Wed, Jan 18, 2023 at 2:19 PM Christian Rohmann christian.rohmann@inovex.de wrote:
Hey Michael, openstack-discuss,
On 17/01/2023 01:52, Michael Johnson wrote:
- The introduction of catalog zones[6] may eliminate the need for
some of the agent based backend drivers.
I proposed the spec to have catalog zone support added to Designate, see https://review.opendev.org/c/openstack/designate-specs/+/849109.
May I ask what the intended way forward with implementing the newly merged "catalog zones spec" is? Is this targeting the Bobcat release?
Regards
Christian