 You can get started I suppose if people come in late they come in late So the designate project update. Hi, my name is Graham Hayes. I'm the PTL and I've been the PTL now for quite an extended period of time, so I've seen that I've been with the project as it's grown. I currently work for Verizon I I Help I'm one that leads for the team that runs our internal private cloud so I'm assuming if you're here for the last session, you know what designate is but just a background in it. It's it's designate is about six years old now it was started by a company in Dublin and In 2013 they brought it into the HP public cloud at the time and Started running it as a production service So in Liberty we were added Before the Big Tent we were brought in as a integrator project and The 12% is a longer tree actually we are now up to 19% of production installs use designate and in some of the largest Installs of OpenStack designates a key component so as a recap in Queens we Got all of the goals done. We were actually ahead of the curve for the Queens goals we'd Already split our tempest test out and had the property the beginning of the Python 3 work done For pike there's still a nice standing goal We don't have a whiskey up available yet That's going to become a lot more Urgent as we remove Python 2 because Oslo service plus Python 3 an event that means you can't use SSL So that is the highest one the highest things in our list right now is to get that fixed We removed our legacy API Which also meant that if you had legacy heat objects That used the original v1 Resources You'll have to migrate them to the version 2 Luckily, they're all named different things. So it won't cause conflicts and we were added to the interop guidelines so if you have a Public cloud or if you Sell a product that has a designate in it You can get certification from the foundation to say that you run a certified Interop compatible version of designate and it's an add-on. So you have the Open-stack powered. I think it's called a trademark program. There's a you can have a DNS add-on So you have open-stack compute plus DNS in rocky The loss we got all of the project goals done We we did a lot of Python 3 work Getting it ready as it turns out there was We had there was Compatibility issues for some of our code between Python 3 5 and Python 3 7 So we started getting all that work out of the way so that when The open-stack community as a whole drops Python 2 support. We will run across all the all the major distros on their versions of Python 3 And we merge the open-stack version objects, which is an important step towards debilitating rolling updates without taking down the API or causing interruption to control control plane interactions This cycle and the project-wide goals. We've we're finished the Python one. We've been Cogating on Python for a long time actually For Python 3 and we have The bones of the status upgrade checked on we just need to find something to check because designate being so Compact as a service. There's not a huge amount that can go wrong in an update. So There's not probably not gonna be a huge amount of stuff in there. It's just small gotchas that we've noticed in the past The ability to edit the SOA record data is there's a patch up. We need that it's in review currently Which allows you to override some of the refresh and Other information on the ability to set a serial That's something that a lot of customers have asked for is the ability to say start this at serial, whatever And we had a session earlier this week about doing shared zones So that's the etherpad where we had the discussion It's a fairly simple RBAC solution So the idea the idea is that if you you create cloud calm with cloud company calm And you want other projects be able to update that Zone you should be able to share it with that zone. You also may want to be able to say Okay, nobody can edit this zone, but I want other people to be able to create products cloud company calm as a zone of their own so Allowing other projects create sub-domains of the domain is another level of the shared zone And it's this has been a long outstanding Feature request. I would like to get into Stein, but it's going to be resource dependent So if anyone has free developers When I finished writing the spec based on the etherpad Please shout out It's it should be fairly simple work. It's also a really good way of getting to know how designates put together and How our storage model and everything work works because you'll be touching a lot of the core business logic in designate and For train and beyond we've had one of the large users of designate What has signed themselves up to Start working on split horizon We're not sure what form that's going to take yet. So the spec is going to go up and anyone who has an interest in working on split horizon Please keep an eye out for it and Put in reviews and comments and put in your ideas. It's important to Think about that with the split horizon it will probably it could probably form the basis for GOIP so doing DNS responses based on the requesters geography so I Don't we don't want to re-implement the same thing twice effectively. So GOIP is effectively just a really complex split horizon So we so when we're reviewing the patches, that's what we need to look at and if anyone has a particular interest in Getting something of that in place again, let us know and We can put you in contact the people who are writing the split horizon spec. So you some sort of collaboration can happen There's been asked for a geo redundant control plane So another company has decided has signed up themselves to go come up with a plan But how we can do it? The problem is the problem is that designated is a global service. We're at the same level of flight as keystone having a designate per region doesn't necessarily make sense With different zones so the Obviously you need to have your DNS and the ability to update it Not go down when you lose a If you if you lose a data center, you don't want to be able to not be able to update Records to put traffic to another data center. That will be a bad thing. So It's very welcome work But it is that's probably gonna be quite tricky one and Finally your idea Designate is a fairly simple Project we the aim is to go out is to have an API that's standard to update and create records and zones and Support as many different DNS servers and providers that we as we can so If you have ideas They're great if you have developers to implement them, that's even better but All ideas will be put on to a onto onto a roadmap and as People sign up to say oh, I've free cycles we can help find out at that work Right now there is So this cycle we did in 90 commits the majority of which were bug fixing We have Three three people who working at part-time and a Few others who give time when they can So we're not floundering we're not as bad as we were The two years ago a year ago when I first wrote about it, but we're If we want to address any extra features something like DNS second that's required. We'll require a huge injection of People to make it work and then people to maintain it as it goes forward because We can't just drop a feature in a walk away. We need to do it'll need updates and Maintenance as we go forward so In Mataka There was a plug-in added to Neutron so that when you create a Neutron network you can attach a DNS domain to that network and then when you create a port or floating IP you can attach a DNS name to it and Depending on your setup it'll either push the record out to designate straight away or when you attach a floating IP to that port It'll push the patch. It'll push the name out to designate That is it's in place and it works quite well, but there's as people are using it They're finding more and more use cases where it could be slightly expanded. So we're working getting all that information back I'm working with the Neutron team to make sure All the little bugs or slight modification feature requests people want are in their queue and work done There's also been a request for multiple DNS zones per network So if you have a provider network that is your external network that you share with multiple tenants the ability to have a DNS domain per project for that Network has been asked for That is slightly more work. It's not a small feature But it's something where I'm trying to work through Spec out for the Neutron team and they're fairly receptive to Feature requests for this The integration was written by the current PTL. So I I always use that when they find a bug and need a fixed You wrote this please fix it and We do have a designate sync Every time I come to a summit people ask me about it so Designate sync was written in the early days before we were an open stock official project So what it does is it listens to the rabbit and queue notifications that used to be sent out for salameter So when you create an instance or port or a floating IP It would read that message off the queue and do some automated action. We do highly recommend you move to the Neutron integration. I do know there's a lot of people who have there's a couple of large people large customers who've written very complex Plug-ins for sync, so it's not going to go away, but the documentation isn't going to get any better and We are pushing asking people to move towards the more stable integration that uses the API. So If you have feedback or Suggestions or you're interested in getting involved OpenSync DNS I Live in Ireland, but work Eastern US hours. So there's a high probability. I'll be online at any point in the day I'm designate tag on OpenStack dev or from Monday open stock discuss when they merge the lists I Have an eye filters on the designate keyword in the subject. So it will bypass. It'll go straight into my inbox Or just email me directly directly I will get back to you soon as I can and every two weeks This is complex every every two weeks. We have a meeting and it alternates between a Morning UTC time and an evening UTC time every two weeks so on the eavesdrop Don't open stock to work web page. There's a link to the an ICS file and It will show the right times for the meeting in your calendar if you're interested in joining But you don't feel like you have to wait for a meeting to talk to people in IRC all the contributors are We also were on IRC most of the time and even if we don't answer you straight away We might we'll probably answer you in an hour or two later So don't be Disheartened if you don't get immediate response, but we are there bugs. We have a collection of relatively Good starter bug fixes that are on launchpad with the low hanging fruit tag If you feel like you want to do anything just pick one of those up and start working on it And we'll review the code as you put it up. If you have any questions again The IRC or the meeting or email will help you out. I'm Probably the easiest the best thing is docs. It's always the buyer's rent entry for people So especially if our docs are wrong There we've noticed a couple of places that things have changed and that a doc isn't necessarily correct anymore please either File a bug or even better put up a patch to fix it And but if you can see it also if you see areas that are could be improved to make it easier for people Just let us know And finally that link there is the review dashboard so At the top there's an urgent fix and priority fixes if you feel like doing reviews They are the places to start and Then after that just start working if you want to if you want to review anything just look at the Haseul needs review these are The changes that we're looking for reviews for I'm I've been asked I know for a lot of for a lot of people getting the company to agree to contribute requires a path to core Or the ability to be a project leader We're fairly open to people becoming core. There's no ceremony about it As long as I can see people are doing consistently good reviews and they're doing a sustained reviews they're not Doing say five one day then nothing for a month and then another five if you're doing every week every week an hour say just reviewing what's there. It's a very quick way for us to promote you into core and I Would I would I would rather go with the trust model that I trust you to ask questions if you don't even if you're a core reviewer And you don't know what to if you don't know to approve it or not to ask questions. So We don't have huge gay keeping problems We let people in I'm and that's Pretty much it for me Is there any questions for anyone? That's everyone just want to go get beer seeing we're in Berlin Okay, thank you very much