*** ianychoi_ has joined #openstack-dns | 01:03 | |
*** ianychoi has quit IRC | 01:12 | |
*** michchap has quit IRC | 01:12 | |
*** hamalq has quit IRC | 01:23 | |
*** kd has joined #openstack-dns | 03:03 | |
*** k-s-dean has quit IRC | 03:04 | |
*** k-s-dean has joined #openstack-dns | 03:06 | |
*** kd has quit IRC | 03:08 | |
*** k-s-dean has quit IRC | 03:18 | |
openstackgerrit | Merged openstack/designate-tempest-plugin master: Testing "Lists all recordsets owned by a project in Designate" API https://review.opendev.org/c/openstack/designate-tempest-plugin/+/778232 | 05:52 |
---|---|---|
*** icey_ has quit IRC | 07:00 | |
*** icey has joined #openstack-dns | 07:06 | |
frickler | this is an invalid configuration "< k-s-dean> extension_drivers = port_security,dns,dns_domain_ports" | 07:11 |
frickler | dns_domain_ports includes the dns extension, specifying both leads to internal errors | 07:12 |
*** k-s-dean has joined #openstack-dns | 08:28 | |
*** zigo has joined #openstack-dns | 08:29 | |
*** k-s-dean has quit IRC | 09:03 | |
*** k-s-dean has joined #openstack-dns | 09:03 | |
openstackgerrit | Arkady Shtempler proposed openstack/designate-tempest-plugin master: New API test - test_list_service_statuses https://review.opendev.org/c/openstack/designate-tempest-plugin/+/780567 | 11:35 |
*** michchap has joined #openstack-dns | 14:22 | |
*** jobewan has joined #openstack-dns | 14:22 | |
openstackgerrit | Arkady Shtempler proposed openstack/designate-tempest-plugin master: Testing "API test for Get Project Limits" https://review.opendev.org/c/openstack/designate-tempest-plugin/+/780871 | 14:56 |
*** hamalq has joined #openstack-dns | 16:48 | |
hamalq | hi can anyone give +1 on https://review.opendev.org/c/openstack/designate/+/755379/ | 16:49 |
*** lbragstad has quit IRC | 18:07 | |
k-s-dean | johnsom, im about if your available | 18:15 |
k-s-dean | if not no worries | 18:16 |
johnsom | k-s-dean Hi, so still having trouble? | 18:16 |
k-s-dean | Yeah, I asked the neutron guys today and they said create a LP ticket. haha | 18:17 |
k-s-dean | so far I've just disabled fixedIP in the designate conf so that the entries aren't lodged in the external DNS. | 18:17 |
johnsom | Ok, so my plan here is to have a discussion to work through a debug scenario. Is that ok? It may take a bit of time | 18:18 |
k-s-dean | Thats fine with me. | 18:19 |
johnsom | Nice. Did you happen to try the proposed solution from Jens? | 18:19 |
k-s-dean | I may have missed that | 18:20 |
johnsom | His proposal was to not set both dns and dns_domain_ports in the extension_drivers setting for neutron. | 18:21 |
k-s-dean | so dont set either ? | 18:21 |
johnsom | https://www.irccloud.com/pastebin/E2YmgymG/ | 18:21 |
k-s-dean | of them* | 18:21 |
johnsom | I think he was recommending to just set dns_domain_ports and not dns as well | 18:22 |
k-s-dean | right ok. | 18:22 |
johnsom | There is probably a bug in there that we should fix so it doesn't cause internal errors, or at least makes them obvious. But that is a side issue. | 18:23 |
k-s-dean | hold on. I re-deployed last night after reading the neutron docs thoroughly | 18:23 |
johnsom | Ok, no porblem. | 18:23 |
k-s-dean | right my config is like so at the moment | 18:24 |
k-s-dean | [ml2] | 18:24 |
k-s-dean | type_drivers = flat,vlan,vxlan | 18:24 |
k-s-dean | tenant_network_types = vxlan | 18:24 |
k-s-dean | mechanism_drivers = linuxbridge,l2population | 18:24 |
k-s-dean | extension_drivers = port_security,dns_domain_ports | 18:24 |
johnsom | Ok, that looks good. | 18:25 |
k-s-dean | ok, let me unset the modifications I made to the designate config. | 18:25 |
johnsom | Ok | 18:25 |
*** lbragstad has joined #openstack-dns | 18:27 | |
k-s-dean | Quick question I currently have an LDAP backend configured. it shouldn't matter which domain I create the dns domain in should it ? | 18:27 |
k-s-dean | e.g. i can create in either the default or my ldap backend | 18:27 |
johnsom | Is the LDAP for keystone or a Designate backend driver? | 18:29 |
k-s-dean | keystone, its simply just a read only copy of my LDAP directory. | 18:30 |
k-s-dean | all the service endpoints are registered in the default domain | 18:31 |
k-s-dean | anyway it should be fine. I've seen the VMs in my ldap domain being registered in DNS | 18:31 |
k-s-dean | so I'll create the zone in the default domain | 18:32 |
k-s-dean | right kolla reconfiguring, with the zone I've just created | 18:32 |
johnsom | Ok, let's collect some basic information. If any of the data is confidential, change it or PM me. Just be sure to change it consistently. | 18:34 |
johnsom | Otherwise, I will get confused. lol | 18:34 |
johnsom | Do you have the VM booted in nova you are wanting to attach the floating IP to? | 18:35 |
k-s-dean | No problem, time for some regex | 18:36 |
k-s-dean | Not yet, but I can create one | 18:36 |
johnsom | Let's do that. | 18:36 |
k-s-dean | kollas almost done reconfiguring | 18:36 |
k-s-dean | two seconds | 18:36 |
johnsom | No worries, I am going to go fill my water | 18:36 |
johnsom | back | 18:39 |
k-s-dean | Awesome. | 18:39 |
k-s-dean | right. | 18:39 |
johnsom | So, once that instance is booted, the first thing I would like to see is "openstack network show <instance net>" | 18:40 |
k-s-dean | I've set the dns-domain on the public network. | 18:40 |
johnsom | Followed by the instance subnet | 18:40 |
k-s-dean | two seconds let me get paste. | 18:40 |
johnsom | Great. paste.openstack.org is handy for this | 18:41 |
k-s-dean | http://paste.openstack.org/show/803628/ | 18:41 |
k-s-dean | subnet | 18:42 |
k-s-dean | http://paste.openstack.org/show/803629/ | 18:42 |
k-s-dean | ok now I'm going to go and boot an instance. | 18:42 |
johnsom | Ok | 18:42 |
johnsom | Looks good so far | 18:43 |
johnsom | Are you planning to use "public" for the floating IP as well? | 18:43 |
k-s-dean | yes public is the floating IP network | 18:43 |
k-s-dean | would you like to see the private networks | 18:43 |
johnsom | Which network will have the instance port on it? | 18:44 |
johnsom | If private, yes please | 18:44 |
k-s-dean | ok so on instance boot the private network vxlan network will be the initial network | 18:45 |
johnsom | Ok, no problem | 18:45 |
k-s-dean | http://paste.openstack.org/show/803630/ | 18:45 |
k-s-dean | thats is DNS before instance boot | 18:45 |
johnsom | perfect | 18:46 |
k-s-dean | http://paste.openstack.org/show/803631/ | 18:47 |
k-s-dean | private network | 18:47 |
k-s-dean | next I'll boot the instance. | 18:47 |
johnsom | Ok, I see one issue. The private network does not have a dns_domain set | 18:48 |
k-s-dean | ok. didn't think that would be an issue. thought it needed to be set on the public. | 18:49 |
k-s-dean | bugger. I'm being called for my dinner. | 18:50 |
johnsom | Well, I think we may need to create the floating IP differently in that case. | 18:50 |
johnsom | Ok, do we need to stop for your dinner? | 18:51 |
johnsom | My tomorrow morning is busy again, until 10am my time. I could ping you tomorrow if you would like | 18:51 |
k-s-dean | yeah unfortunately, I'll be about 30 minutes. but before I go. | 18:52 |
johnsom | Wednesday is my meeting day. lol | 18:52 |
k-s-dean | the instance has now booted. | 18:52 |
johnsom | Ok, a show on that would be good as well | 18:52 |
johnsom | I can save my place. lol | 18:52 |
k-s-dean | http://paste.openstack.org/show/803632/ | 18:53 |
k-s-dean | there is the paste with the VXLAN IPs in DNS | 18:53 |
k-s-dean | before I've attached a floating IP | 18:53 |
johnsom | Ok | 18:54 |
k-s-dean | I'll ping you again once Ive had dinner my folks are looking at me like what you doing. | 18:54 |
k-s-dean | if you available great if not no worries. | 18:54 |
johnsom | Ok, no problem | 18:54 |
johnsom | I will be around | 18:54 |
k-s-dean | johnsom, Back | 19:23 |
johnsom | k-s-dean Hi | 19:24 |
k-s-dean | you still available :) | 19:25 |
johnsom | Yes | 19:25 |
k-s-dean | awesome. Ok, some from here do you want me to attach the floating IP | 19:25 |
johnsom | So, I am a bit surprised at your last zone show. The network for that instance does not have a dns_domain set, but you have three addresses assigned. | 19:26 |
k-s-dean | Yeah, thats what has been confusing me. | 19:26 |
k-s-dean | I'm not expecting those entries to be added at all. | 19:26 |
johnsom | That is a bit unexpected. Are you running the Designate Sink process? | 19:27 |
k-s-dean | yes. | 19:27 |
johnsom | And you are on which version of Openstack ? | 19:27 |
k-s-dean | victoria. | 19:27 |
k-s-dean | built from source. | 19:27 |
k-s-dean | deployed with kolla. | 19:27 |
johnsom | Hmm, ok. Let's keep going, but I will note that as unexpected. It may be because of the sink, which isn't used for nova/neutron integration anymore. | 19:27 |
k-s-dean | ohhh. ok | 19:28 |
johnsom | Yeah, I have zero experience with Kolla, so I'm not going to be much help there. | 19:28 |
johnsom | Can you provide a "openstack server show"? | 19:28 |
k-s-dean | yeah thats fine. I'm pretty versed with ansible. and i know how kolla works | 19:28 |
k-s-dean | sure | 19:28 |
johnsom | Yeah, kolla is just one of the deployment tools I haven't ever needed to use. | 19:29 |
k-s-dean | http://paste.openstack.org/show/803635/ | 19:29 |
johnsom | Ok, that looks fine. Now the neutron port "openstack port list --device_id cfceceb3-3b84-41e7-a071-093305b364cd" and "openstack port show <port id>" I only need the port show output | 19:32 |
k-s-dean | http://paste.openstack.org/show/803636/ | 19:35 |
johnsom | Thanks | 19:36 |
johnsom | so, this is a total mystery: test-instance.operations.os.example.com. | 19:36 |
k-s-dean | I can show you where thats coming from | 19:36 |
johnsom | Ok, I am interested | 19:36 |
k-s-dean | http://paste.openstack.org/show/803637/ | 19:37 |
k-s-dean | btw the I have modified the notification topics. the default is notifications_designate | 19:38 |
johnsom | Oh, so you do have sink configured. | 19:38 |
k-s-dean | yes kolla is configuring it. | 19:38 |
k-s-dean | which service is now responsible for DNS then ? | 19:39 |
johnsom | So, we may have a conflict situation going on, where sink has already created some records and when the floating comes along it's not able to create | 19:39 |
johnsom | neutron calls directly to the designate API now | 19:39 |
k-s-dean | ahhhh, ok. now that makes more sense. | 19:39 |
johnsom | Let's continue, then we can try a few things and see if we can identify the issue. | 19:40 |
k-s-dean | ok cool. | 19:40 |
k-s-dean | what would you like me to do next ? | 19:40 |
johnsom | My crystal ball says the problem is the network/port doesn't have a domain. But let's see | 19:40 |
johnsom | Ok, please create the floating IP and associate it to the instance port. Then do a show on the floating IP and the zone. All of those can be in the same paste. | 19:41 |
k-s-dean | http://paste.openstack.org/show/803638/ | 19:46 |
johnsom | Yep, ok, so we have reproduced the issue you are seeing. | 19:48 |
k-s-dean | the conflict is deffiently real | 19:48 |
hamalq | sorry for interrupting if the neutron does not create DNS records it could be because of this https://github.com/openstack/neutron/blob/e9a75a379ea423f8ee452015888dc954d0decb08/neutron/plugins/ml2/extensions/dns_integration.py#L374 | 19:48 |
hamalq | specially this line https://github.com/openstack/neutron/blob/e9a75a379ea423f8ee452015888dc954d0decb08/neutron/plugins/ml2/extensions/dns_integration.py#L383 | 19:49 |
johnsom | hamalq Please feel free to add ideas! | 19:49 |
k-s-dean | I'm see a bunch of duplicate entry errors in designate-sink | 19:49 |
hamalq | johnsom: thanks, also no need to use sink when u enable the neutron external dns plugin | 19:52 |
johnsom | There are not any segments on the VM instance network or the subnet. I think this function is passing as the IP address record gets added, it's just the name that doesn't get added. | 19:52 |
johnsom | hamalq Yeah, I mentioned that earlier as well | 19:52 |
johnsom | I think it is either that the network/port doesn't have a domain or the sink being enabled is conflicting | 19:53 |
johnsom | k-s-dean Let's try this. | 19:54 |
k-s-dean | so, from what your saying here is that, one disable designate-sink its no longer required. two assign dns-domain to both private and public network | 19:54 |
k-s-dean | go on. | 19:54 |
johnsom | De-associate the floating IP from the port. Then, on the port for the instance, configure the dns_domain setting. Then re-associate the floating IP | 19:55 |
k-s-dean | sorry, private IP port | 19:58 |
johnsom | Yes | 19:58 |
johnsom | e915ca08-baa5-4879-8ee3-b28888446fb0 | 19:58 |
k-s-dean | ok but the recordsets are still in DNS. might get a duplicate name clash here. setting re-associating now | 20:00 |
k-s-dean | no difference. | 20:01 |
johnsom | Well, you can have multiple A records for a name. (DNS round robin) That would be a different problem, but would show that the floating IP is getting a name | 20:01 |
k-s-dean | http://paste.openstack.org/show/803640/ | 20:03 |
k-s-dean | http://paste.openstack.org/show/803641/ | 20:04 |
k-s-dean | second one is floatin IP | 20:04 |
johnsom | You shared the show zone for example.com, but put os.armourcomms.com in the dns_domain field. Did the os.armourcomms.com zone get the record? | 20:05 |
k-s-dean | shit | 20:05 |
k-s-dean | that is example.com | 20:05 |
johnsom | Ok | 20:06 |
hamalq | neutron will not allow the ip duplication | 20:06 |
johnsom | hamalq The float should have a different IP than the instance port, so that should be fine | 20:07 |
johnsom | I was kind of expecting: test-instance.os.example.com. 192.168.230.237 and a test-instance.os.example.com. 10.30.0.106 in the "example.com" domain | 20:07 |
johnsom | 192.168.230.237 is the instance port IP, 10.30.0.106 is the floating IP | 20:08 |
johnsom | The floating IP didn't "inherit" the instance port DNS names | 20:09 |
johnsom | Ok, I am pretty sure this is part of the problem: | 20:11 |
johnsom | http://paste.openstack.org/show/803637/ | 20:11 |
johnsom | The floating IP config there is limited to the IP | 20:11 |
johnsom | Since it's using the sink, maybe what you need is to add another line there: | 20:12 |
k-s-dean | if i comment out the nova:fixed section the private IPs dont get put in DNS. | 20:12 |
johnsom | formatv4 = %(hostname)s.%(zone)s | 20:12 |
k-s-dean | under neutron:floating IP yes | 20:12 |
k-s-dean | because that produces and error. | 20:13 |
johnsom | Yeah, that is probably a kolla issue where if it is still setting up sink, it's probably not configuring the connection for neutron to call designate | 20:13 |
k-s-dean | I've already tried that | 20:13 |
johnsom | lol, ok | 20:13 |
k-s-dean | hold on let me see if I can find the particular LP that i came across | 20:13 |
johnsom | I am super rusty on the sink setup | 20:13 |
k-s-dean | https://bugs.launchpad.net/designate/+bug/1772925 | 20:14 |
openstack | Launchpad bug 1772925 in Designate "Error in sink formatv4 neutron_floatingip handler" [Undecided,New] | 20:14 |
johnsom | Yeah, ok, I was afraid of that. | 20:15 |
johnsom | Ok, so the path forward is going to be: Undo the kolla sink setup, configure neutron for the direct to designate path. | 20:15 |
k-s-dean | ok | 20:16 |
johnsom | Sadly, you will need to do that outside of the kolla managed config | 20:16 |
k-s-dean | so this should be fairly simple then. Delete the sink container | 20:16 |
johnsom | Probably. That would be a question for the kolla channel | 20:16 |
johnsom | Well, just stop it for now | 20:16 |
k-s-dean | done | 20:17 |
johnsom | You will then need to follow the instructions here: https://docs.openstack.org/neutron/victoria/admin/config-dns-int-ext-serv.html | 20:17 |
k-s-dean | ok thats done as well. | 20:18 |
k-s-dean | I have that particular section in my neutron.conf | 20:18 |
k-s-dean | and external_dns_driver is set to designate | 20:19 |
k-s-dean | I assume from here it would just be a case of setting the dns-domain on the private network | 20:19 |
johnsom | Hmm, well, in theory, but if this was already set I would have expected that last test to work. | 20:20 |
k-s-dean | one thing that I can confirm works. In horizon | 20:21 |
k-s-dean | if i set the dns_domain and dns_name on creation of the floating IP the DNS name does register in DNS | 20:21 |
johnsom | Yeah, you can set the directly in the floating IP on the CLI as well. | 20:22 |
johnsom | I didn't think that would solve your problem though. | 20:22 |
k-s-dean | it doesn't | 20:22 |
k-s-dean | let me try our theory out and see what happens | 20:22 |
k-s-dean | without sink the DNS entries are not being removed, but thats expected. | 20:24 |
k-s-dean | what would be the best service to look at to see the api calls from neurton ? | 20:24 |
k-s-dean | neutron* | 20:24 |
johnsom | Can you provide "openstack extension list --network -c Alias" | 20:25 |
johnsom | The calls from neutron will be in your API log. I'm not sure how kolla deploys it, it could be in the apache logs, or a designate specific api log | 20:25 |
k-s-dean | http://paste.openstack.org/show/803642/ | 20:26 |
hamalq | try delete all the records u have in the zone then create/delete a service | 20:27 |
hamalq | i mean a server | 20:27 |
johnsom | Yeah, I agree or create another instance with a different name | 20:28 |
k-s-dean | yeah nothing being registered. I created a new server test-instance2 | 20:28 |
k-s-dean | which would have a different dns name so should be fine | 20:28 |
hamalq | the ip also matters | 20:28 |
k-s-dean | I created a brand new floating IP also | 20:29 |
k-s-dean | I can also confirm that the fixed IP is different | 20:29 |
hamalq | then it should be https://github.com/openstack/neutron/blob/e9a75a379ea423f8ee452015888dc954d0decb08/neutron/plugins/ml2/extensions/dns_integration.py#L383 is returning false | 20:30 |
k-s-dean | I find that pretty odd that the flat network returns false | 20:31 |
k-s-dean | the docs do refrence a vlan provider network. | 20:31 |
k-s-dean | I can create that if needed. | 20:31 |
hamalq | https://github.com/openstack/neutron/blob/e9a75a379ea423f8ee452015888dc954d0decb08/neutron/plugins/ml2/extensions/dns_integration.py#L370 | 20:31 |
k-s-dean | brb need to take a leak | 20:32 |
k-s-dean | back | 20:33 |
k-s-dean | which component handles DNS registration now then ? | 20:34 |
k-s-dean | if sink is deprecated is it neutron its self | 20:34 |
johnsom | yes | 20:34 |
johnsom | https://docs.openstack.org/neutron/victoria/admin/config-dns-int-ext-serv.html#configuring-openstack-networking-for-integration-with-an-external-dns-service | 20:34 |
johnsom | This gives neutron the credentials to do so. | 20:34 |
johnsom | I would check the designate API logs to make sure neutron is successful at logging in to post the update. | 20:35 |
k-s-dean | I can see it checking for the zone | 20:40 |
k-s-dean | So no post requests only get requests | 20:42 |
k-s-dean | same as before create a new vm with new name, new floating IP | 20:42 |
k-s-dean | I would expect a post request to designate | 20:43 |
johnsom | Yes, me too | 20:43 |
k-s-dean | got an intresting log here. | 20:45 |
k-s-dean | http://paste.openstack.org/show/803643/ | 20:47 |
k-s-dean | .3 | 20:47 |
johnsom | Does the zone show two records? | 20:49 |
johnsom | Or none | 20:50 |
k-s-dean | none | 20:50 |
k-s-dean | did you scroll down on the paste ? | 20:50 |
k-s-dean | I left to much of a gap there. | 20:50 |
johnsom | lol, missed it | 20:50 |
k-s-dean | neutron.db.dns_db neutron_lib.exceptions.dns.DNSDomainNotFound: Domain os.example.com. not found in the external DNS service | 20:50 |
k-s-dean | this | 20:50 |
k-s-dean | now why would that be. | 20:51 |
k-s-dean | it exists. so neutron should see it. | 20:51 |
k-s-dean | I'm wondering do I need to specify the ID of the zone in the neutron conf | 20:51 |
k-s-dean | dns_domain = | 20:52 |
johnsom | That would just be the default. | 20:53 |
k-s-dean | obviously mine is set to dns_domain = example.com. | 20:53 |
johnsom | Could it be that the zone you created for os.example.com is not visible to the account you have in neutron in the [designate] section? | 20:54 |
johnsom | I.e. is the zone owned by a different project? | 20:54 |
k-s-dean | yeah... it is. | 20:54 |
k-s-dean | ok let me trying creating the zone in that domain and in that particular project then | 20:55 |
johnsom | Hmm, but the zone should be owned by the same project as the port. | 20:55 |
johnsom | really | 20:55 |
johnsom | It should impersonate. Let me look in the code. | 20:55 |
johnsom | Can you do an "openstack zone show" for the os.example.com zone? | 20:59 |
k-s-dean | http://paste.openstack.org/show/803644/ | 21:00 |
johnsom | Yeah, ok, that is the problem | 21:01 |
johnsom | The zone is owned by 78293d3b575c43ed81c517fbb751abf4 and the VM is project ID 306d564b6a6e42cc92060361aa87f7fd | 21:01 |
k-s-dean | ok. | 21:02 |
johnsom | You can't insert records into someone else's zone via creating a port. | 21:02 |
k-s-dean | so it has to be in the same project | 21:02 |
k-s-dean | and domain | 21:02 |
k-s-dean | or is it just project. It will impersonate the domain ? | 21:02 |
johnsom | The comparison should be a the project ID level. The concept of a credential domain is in keystone and maps down to the project ID | 21:03 |
k-s-dean | ok. | 21:04 |
johnsom | So, if the user creating the VM, also creates a zone in designate, they should be able to use it. | 21:04 |
k-s-dean | makes sense | 21:05 |
k-s-dean | heyhey.... | 21:08 |
k-s-dean | we have lift off. | 21:08 |
johnsom | Yay | 21:08 |
k-s-dean | thank you so much | 21:08 |
johnsom | Sorry for the long about path to an answer | 21:08 |
k-s-dean | no problem. | 21:08 |
johnsom | But at least you have an answer | 21:08 |
k-s-dean | I do you've made me a very happy man | 21:08 |
k-s-dean | so basically. bye bye desingate-sink | 21:09 |
johnsom | Cool. Happy computing. I am off to do a ton of reviews I have backlogged | 21:09 |
k-s-dean | Thanks so much dude. | 21:09 |
johnsom | Yeah, it had a bunch of limitations, so the decision was made to just go direct and not use the message queues | 21:09 |
* johnsom disappears back into the dungeon where he is locked with launchpad and gerrit | 21:10 | |
k-s-dean | Awesome. well you have no idea how thankfull I am you helped me out. | 21:11 |
k-s-dean | good luck with your code reviews :) | 21:11 |
hamalq | johnsom: can u check this too it was approved before but small changes asked from frickler all done https://review.opendev.org/c/openstack/designate-tempest-plugin/+/755876, https://review.opendev.org/c/openstack/designate/+/755379/ | 21:12 |
johnsom | It's on my list but behind a bunch of high priority stuff (for internal company needs). I thought you had the reviews you need on those, don't you have two +2? | 21:13 |
hamalq | johnsom: frickler asked for some changes so i did them so i need approval again | 21:14 |
hamalq | https://review.opendev.org/c/openstack/designate/+/748285/, https://review.opendev.org/c/openstack/designate/+/754226/ those two dpend on it but they are approved | 21:15 |
johnsom | Ok, hopefully some of the other cores can get to those sooner than I can. | 21:16 |
hamalq | thanks | 21:16 |
*** k-s-dean has quit IRC | 22:17 | |
*** lbragstad_ has joined #openstack-dns | 22:29 | |
*** lbragstad has quit IRC | 22:35 | |
*** k-s-dean has joined #openstack-dns | 23:18 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!