 Hi, I'm Heidi Joy Trep away with the OpenStack Foundation and I'm here with Graham Hayes from the Designate project As part of our Metaca design series. Graham, would you tell us a little bit about yourself, please? Hi, I'm the new incoming PTO for the Metaca cycle for Designate. I've been involved in Designate for about two and a half years and I live in Dublin, Ireland and work for Unipackered Enterprise. So, could you please give us a snapshot of what is Designate and what does it do? Designate is a DNS service. So, traditionally in enterprises or in companies, DNS is something that's quite difficult to do. Users have to find a ticket with IT or they have to go edit text files into some server and do it all manually. So, what Designate does is it finds an easy to use API that's multi-tenanted. So, multiple users can all create DNS phones and records while being separated from each other but then use the same server infrastructure to push them out to the internet. So, basically we make what is something that's quite complex, easy to use and something that allows end users to actually directly update instead of having the bottleneck of traditional IT. We're excited to hear more about the hot topics that your team discussed in Tokyo and interested to learn what decisions or outcomes came out of these discussions. Designate has been going through a large amount of re-architecture. We started out in the beginning with one way of talking to different DNS servers that you changed up between Kilo and Liberty. So, the hot topics were the gaps left from that and there was also a sizable chunk of people who were looking for DNS sec and for a technology called IXF or which is incremental zone transfers. So, these were the hot topics for the talk and we spent the majority of the two days talking about these and finally have a roadmap. We had an idea of what we're going to do for this cycle and the priorities, the relative priorities for those. Well, then tell us more about what the user needs or problems that your team wanted to solve are. Yeah, the user needs are for DNS that people wanted to ensure that the DNS results that get back are 100% correct that they haven't been tampered with. This is going to be a longer, it's probably going to be a two cycle feature as it requires us to talk to other open sec projects like Barbican. But that's one of the top things we want to solve for users. We also wanted to allow users to enter with Nerva Neutron. So, when you boot a VM, when you give the VM a name it'll have a record in DNS automatically along with if you have signed a floating IP that will be available for DNS as well. So, these are the two big things that users were asking us to do one of which the integration of Nerva Neutron is very close to being done and DNS like which is starting and it's our next big feature. So, what are the top three or four features that we can look forward to in the Mitaka release? The top features we can look forward to are the incremental zone transfers which will allow for the DNS records to be updated on the DNS servers a lot quicker. So, when you make an API request to create a domain or update a record it'll be active so users can access it a lot quicker. We will be enabling the pool scheduler so if you say you have a large amount of DNS zones there's some people who are looking at designating millions of zones and they want to spread them across a larger group of DNS servers this will allow operators to set up two or three different pools and have users scheduled across the pools. So, what is the key theme or themes that your project aims to achieve in Mitaka? So, one of the themes we're aiming for is modularity. We are increasing the amount of DNS servers that we support and we're also breaking down what used to be a couple of very large services into smaller services that allow for tasks to be distributed across different machines. This also ties in then into resiliency because it allows us to have the repetitive tasks that doesn't it does run across a larger group of machines so if we lose one it doesn't really matter if the rest of the machines will download which also then ties into scalability. We found that if you can scale it horizontally without a huge amount of problems resiliency automatically goes up not automatically goes up but can benefit greatly from the work done for scalability. For manageability we are currently improving our horizon plugin panels so that should be done over the next cycle or so to update them and make them more user friendly It's the current panels we have for the very beginning so it's always good to put something out into the hands of users and get feedback about what they'd like to change so we're taking that feedback now and updating the panels with it. Well, thank you very much for joining us Grim and we look forward to what Designate's going to bring us in the Mitaka release. No problem, thank you very much for having me.