*** rmoe has joined #openstack-dns | 00:16 | |
*** betsy has joined #openstack-dns | 00:22 | |
*** eankutse has joined #openstack-dns | 00:27 | |
*** matsuhashi has joined #openstack-dns | 00:27 | |
*** eankutse has quit IRC | 00:27 | |
*** eankutse has joined #openstack-dns | 00:27 | |
*** rektide has joined #openstack-dns | 00:29 | |
*** CaptTofu has joined #openstack-dns | 00:37 | |
*** eankutse has quit IRC | 00:44 | |
*** simonmcc_ has quit IRC | 00:55 | |
*** simonmcc_ has joined #openstack-dns | 00:57 | |
*** CaptTofu has quit IRC | 00:59 | |
*** CaptTofu has joined #openstack-dns | 00:59 | |
*** CaptTofu has quit IRC | 01:03 | |
*** CaptTofu has joined #openstack-dns | 01:07 | |
*** simonmcc_ has quit IRC | 01:11 | |
*** simonmcc_ has joined #openstack-dns | 01:15 | |
*** CaptTofu has quit IRC | 01:18 | |
*** rossk has quit IRC | 01:27 | |
*** CaptTofu has joined #openstack-dns | 01:27 | |
*** nosnos has joined #openstack-dns | 01:31 | |
*** nosnos has quit IRC | 01:38 | |
*** nosnos has joined #openstack-dns | 01:38 | |
*** HenryG has joined #openstack-dns | 01:43 | |
*** vinod1 has joined #openstack-dns | 01:48 | |
*** vinod1 has left #openstack-dns | 02:08 | |
*** CaptTofu has quit IRC | 02:11 | |
*** richm has quit IRC | 02:41 | |
*** jmcbride has joined #openstack-dns | 02:44 | |
*** crc32 has quit IRC | 02:55 | |
*** CaptTofu has joined #openstack-dns | 03:03 | |
*** jmcbride has quit IRC | 03:04 | |
*** matsuhashi has quit IRC | 03:14 | |
*** jmcbride has joined #openstack-dns | 03:19 | |
*** matsuhashi has joined #openstack-dns | 03:20 | |
*** jmcbride has quit IRC | 03:23 | |
*** matsuhashi has quit IRC | 03:30 | |
*** matsuhashi has joined #openstack-dns | 03:33 | |
*** matsuhashi has quit IRC | 03:42 | |
*** nosnos has quit IRC | 03:58 | |
*** mwagner_lap is now known as mwagner_zzz | 04:25 | |
*** jmcbride has joined #openstack-dns | 04:29 | |
*** CaptTofu has quit IRC | 04:45 | |
*** CaptTofu has joined #openstack-dns | 04:46 | |
*** CaptTofu has quit IRC | 04:50 | |
*** matsuhashi has joined #openstack-dns | 04:55 | |
*** nosnos has joined #openstack-dns | 04:59 | |
*** matsuhashi has quit IRC | 06:30 | |
*** CaptTofu has joined #openstack-dns | 06:46 | |
*** matsuhashi has joined #openstack-dns | 06:49 | |
*** CaptTofu has quit IRC | 06:51 | |
*** JensOfSw_ has quit IRC | 07:20 | |
*** CaptTofu has joined #openstack-dns | 08:47 | |
*** CaptTofu has quit IRC | 08:52 | |
*** ytwu has left #openstack-dns | 09:16 | |
*** nosnos_ has joined #openstack-dns | 10:02 | |
*** nosnos has quit IRC | 10:05 | |
*** matsuhashi has quit IRC | 10:25 | |
*** CaptTofu has joined #openstack-dns | 10:48 | |
*** CaptTofu has quit IRC | 10:52 | |
*** gstaicu has joined #openstack-dns | 11:26 | |
gstaicu | hi | 11:26 |
---|---|---|
gstaicu | can someone help me with the integration of designate in openstack havana? | 11:26 |
*** nosnos_ has quit IRC | 11:30 | |
*** nosnos has joined #openstack-dns | 11:31 | |
*** CaptTofu has joined #openstack-dns | 11:33 | |
*** mwagner_zzz has quit IRC | 11:35 | |
ekarlso | gstaicu: sure | 11:41 |
*** CaptTofu has quit IRC | 12:05 | |
*** CaptTofu has joined #openstack-dns | 12:06 | |
*** CaptTofu has quit IRC | 12:10 | |
gstaicu | ekarlso: I have an havana | 12:41 |
ekarlso | gstaicu: what is the issue ? :) | 12:42 |
*** CaptTofu has joined #openstack-dns | 12:42 | |
gstaicu | ekarlso: cluster and I would like to use designate to register name of the instance | 12:42 |
gstaicu | ekarlso: first observation I would like to know what notification handlers are available | 12:43 |
gstaicu | ekarlso: I have installed designate 2013.2-4 | 12:43 |
gstaicu | ekarlso: and from what I am seeing in the /usr/share/pyshared/designate/notification_handler | 12:44 |
gstaicu | ekarlso: I have nova handler and quantum | 12:44 |
gstaicu | ekarlso: isnt't also neutron? | 12:45 |
ekarlso | quantum is the same as neutron but | 12:46 |
ekarlso | I would recommend u running on trunk instead or what Kiall ? | 12:46 |
*** CaptTofu has quit IRC | 12:47 | |
Kiall | 2013.2 is the Designate Havana release.. So it's probably saner to use that with Havana .. | 12:47 |
gstaicu | ekarlso: I am using this repository: http://ppa.launchpad.net/designate-ppa/havana/ubuntu | 12:48 |
Kiall | Anyway gstaicu - the handlers included are really just samples, everyone has a totally different idea of what should happen automatically, so we just made sure it was easy to write plugins for it | 12:48 |
Kiall | https://github.com/stackforge/designate/tree/master/contrib/designate-ext-samplehandler shows a sample handler plugin | 12:48 |
gstaicu | Kiall: this means that if I want to use neutron I should write the corresponding handler? | 12:49 |
Kiall | gstaicu: Neutron was called Quantum before, we didn't rename the handler before the release though.. It should work | 12:50 |
gstaicu | Kiall: ok | 12:50 |
Kiall | But - What it does is pretty basic - It auto generates a name and uses that, that name is likely to be not what you actually want\ | 12:50 |
Kiall | Since everyone has a totally different idea about what should happen automatically, we went for something that was little more than an example of how to write your own plugins. | 12:51 |
gstaicu | Kiall: at this moment my understanding was that the configured sink handler will look in the queue for a certain type of the message | 12:52 |
Kiall | Correct, the sink service will grab events from the neutron/nova event bus, then it will hand those messages to the enabled plugins | 12:53 |
gstaicu | Kiall: and based on that type of the message will call designate to create a record according with configured format | 12:53 |
Kiall | The plugins do the "interesting stuff" of actually creating/deleting records etc | 12:53 |
gstaicu | Kiall: and this means that in my case I can use quantum handler | 12:54 |
Kiall | The stock plugins take the IP, and create a recored named 1-2-3-4.mydomain.com, or something similar. i.e. 99.9% not what you really want\ | 12:54 |
gstaicu | Kiall: and I should change the control_exchange parameter? | 12:54 |
Kiall | Since some people want 1-2-3-4.mydomain.com, others want <name>.cloud.com, others want <name>, others want <name>.<tenant>.cloud.com etc | 12:54 |
Kiall | we decided to do the most basic, and let end users write their own plugin to decide what they want done with the events | 12:55 |
gstaicu | Kiall: with this repository: http://ppa.launchpad.net/designate-ppa/havana/ubuntu which handle is by default supported? | 12:57 |
gstaicu | Kiall: can I use neutron with this repository as it is? | 12:57 |
Kiall | The demo nova and quantum (aka neutron) handlers. But I'll stress again, these are purely samples, intended for you to use an examples of how to write your own plugins. | 12:58 |
gstaicu | Kiall: I will try with quantum | 13:00 |
gstaicu | Kiall: and if it does not work I will try to write a plugin for neutron | 13:01 |
gstaicu | Kiall: I have found that there is already one for neutron in the trunk of the project: https://github.com/stackforge/designate/blob/master/designate/notification_handler/neutron.py | 13:03 |
gstaicu | Kiall: I will try for the beginning to use that one | 13:03 |
Kiall | The quantum one was literally renamed to neutron | 13:03 |
Kiall | it's identical in every other way | 13:03 |
gstaicu | Kiall: I have copied neutron.py from the project to /usr/share/pyshared/designate/notification_handler | 13:13 |
gstaicu | Kiall: in the section [service:sink] | 13:13 |
Kiall | That's not enough, it uses python entry points to load them.. The plugin example repo I gave you has all the pieces needed, with setup.cfg having the missing piece for you | 13:14 |
gstaicu | Kiall: in /etc/desigante/designate.conf | 13:14 |
Kiall | But | 13:14 |
Kiall | The quantum.py one in 2013.2 is literally identical to neutron.py in trunk... There's no need to switch it out | 13:14 |
gstaicu | Kiall: ok | 13:15 |
gstaicu | than I will try with that one | 13:15 |
Kiall | Just give it the right settings, and it should do it's thing | 13:15 |
gstaicu | Kiall: but I will change the exchange, right? | 13:15 |
Kiall | Yea - Point it at your Neutron exchange | 13:15 |
*** eankutse has joined #openstack-dns | 13:15 | |
*** jmcbride has joined #openstack-dns | 13:16 | |
*** eankutse has quit IRC | 13:18 | |
gstaicu | Kiall: I did it | 13:18 |
*** eankutse has joined #openstack-dns | 13:18 | |
*** CaptTofu has joined #openstack-dns | 13:18 | |
gstaicu | Kiall: designate-sink starte without any errors | 13:19 |
gstaicu | Kiall: so far so good....:) thanks | 13:19 |
gstaicu | Kiall: now I will try to start an instance | 13:19 |
gstaicu | Kiall: I have enabled debug in designate.conf | 13:20 |
gstaicu | Kiall: I have started an instance | 13:22 |
gstaicu | Kiall: but I can not see any messages in the log of designate-sink | 13:22 |
gstaicu | Kiall: handler:quantum_floatingip.notification_topics = ['monitor'] | 13:24 |
gstaicu | Kiall: but it seams that in monitor queue are 0 messages | 13:26 |
gstaicu | Kiall: here is the output of the rabbitmqctl list_queues|grep monitor | 13:26 |
gstaicu | Kiall: http://pastebin.com/kqweSBKz | 13:26 |
gstaicu | Kiall: probably nova does not send notifications in monitor queue | 13:27 |
gstaicu | Kiall: I will try to modify the type of notification | 13:27 |
Kiall | gstaicu: the notification_topics setting should match the neutron notification_topics setting | 13:31 |
*** ytwu has joined #openstack-dns | 13:32 | |
gstaicu | Kiall: it is strange | 13:37 |
gstaicu | I have modified in the designate.conf | 13:37 |
gstaicu | Kiall: notification_topics = notifications | 13:38 |
ekarlso | gstaicu: have you setup neutron etc to actually emit the notifications ? | 13:38 |
Kiall | Yes, but it's been a while | 13:39 |
gstaicu | Kiall: but when I restart designate-sink | 13:39 |
gstaicu | Kiall: in log I am seeing: DEBUG [designate.openstack.common.service] service:sink.enabled_notification_handlers = ['quantum_floatingip'] | 13:39 |
gstaicu | Kiall: DEBUG [designate.openstack.common.service] handler:quantum_floatingip.notification_topics = ['monitor'] | 13:39 |
gstaicu | Kiall: should not be notifications in place of monitor? | 13:40 |
gstaicu | ekarlso: I will verify also what notifications neutron is sending | 13:40 |
Kiall | Which "notification_topics" did you change in designate.conf? The one under the [handler:quantum] (or similar named) section, or the one at the top in the [DEFAULT] section? | 13:41 |
Kiall | The [DEFAULT] one is where Designate sends notifications | 13:41 |
Kiall | the [handler:quantum] one is where we listen for Quantum/Neutron notifications | 13:41 |
Kiall | Actually - The section is called [handler:quantum_floatingip], not handler:quantum], my mistake | 13:42 |
gstaicu | Kiall: [handler:qunatum_floating] domain_id = 65783562-064f-4747-9b57-b1788cc9e1b1 notification_topics = notifications control_exchange = 'neutron' format = '%(octet0)s-%(octet1)s-%(octet2)s-%(octet3)s.%(domain)s' | 13:42 |
gstaicu | Kiall: this is what I have in my config | 13:42 |
Kiall | [handler:qunatum_floating] <-- Looks like a typo | 13:43 |
Kiall | vs | 13:43 |
Kiall | [handler:quantum_floatingip] | 13:43 |
*** mwagner_lap has joined #openstack-dns | 13:43 | |
gstaicu | Kiall: sorry, I will modify now | 13:43 |
*** nkinder has quit IRC | 13:52 | |
*** nosnos has quit IRC | 13:56 | |
*** jmcbride has quit IRC | 13:59 | |
gstaicu | Kiall: I repaired the typo | 14:02 |
gstaicu | Kiall: start an instance | 14:03 |
gstaicu | Kiall: before restart the instace restart designate-sink ....:) | 14:03 |
gstaicu | Kiall: the log looks ok | 14:03 |
gstaicu | Kiall: but when I spawn the instance I can not see anything | 14:04 |
gstaicu | in the designate-sink log | 14:04 |
Kiall | gstaicu: if you stop designate-sink, launch the instance, and check the queue has an item.. It's probably something on the neutron side that's not sending the message | 14:04 |
gstaicu | Kiall: from my understanding the queue where the notifications are sent is notification.info | 14:06 |
gstaicu | with rabbitmqctl list_queues|grep notifications | 14:07 |
gstaicu | Kiall: notifications.info 42 | 14:07 |
Kiall | So .. 42 in there, it's sending the right stuff then | 14:08 |
Kiall | (ignore .info, that's normal) | 14:08 |
Kiall | Is designate and neutron on the same RabbitMQ + RabbitMQ VHost? | 14:08 |
gstaicu | Kiall: touche | 14:09 |
gstaicu | Kiall: :) | 14:09 |
gstaicu | Kiall: I have an rabbitmq cluster | 14:09 |
gstaicu | Kiall: but when I configured designate | 14:10 |
Kiall | Well, both on the same cluster should be fine too ;) | 14:10 |
gstaicu | Kiall: on one of the node in the cluster | 14:10 |
gstaicu | Kiall: in the designate.conf I did not specified the cluster | 14:10 |
gstaicu | Kiall: I let it default | 14:10 |
gstaicu | Kiall: localhost | 14:11 |
gstaicu | Kiall: I will configure designate to connect to the cluster | 14:11 |
gstaicu | Kiall: maybe this is the problem | 14:11 |
*** vinod1 has joined #openstack-dns | 14:17 | |
*** CaptTofu has quit IRC | 14:19 | |
gstaicu | Kiall: not getting it | 14:27 |
gstaicu | Kiall: :) | 14:27 |
gstaicu | Kiall: changed the configuration of designate.conf | 14:29 |
Kiall | Are both designate and neutron on the same vhost? | 14:29 |
gstaicu | Kiall: the setup is like this | 14:30 |
gstaicu | Kiall: 2 servers in a rabbitmq cluster | 14:30 |
gstaicu | Kiall: on the same 2 servers plus another one | 14:31 |
gstaicu | Kiall: I have neutron-server running | 14:31 |
Kiall | The cluster piece shouldn't matter.. A RMQ Cluster behaves just like 1 standalone RMQ with multiple IP's from the point of view of a client | 14:31 |
gstaicu | Kiall: neutron-server on the servers connect all to the rabbitmq cluster | 14:32 |
gstaicu | Kiall: so should be ok | 14:32 |
Kiall | Yea, should be. | 14:33 |
Kiall | Are both neutron and designate on the same RMQ vhost? That's the next likely thing. | 14:33 |
*** jmcbride has joined #openstack-dns | 14:33 | |
*** msisk has joined #openstack-dns | 14:33 | |
gstaicu | Kiall: in the neutron.conf I did not change the rabbit_virtual_host parameter | 14:35 |
gstaicu | Kiall: I let it default | 14:35 |
gstaicu | Kiall: which in documetation it says it is "/" | 14:35 |
*** CaptTofu has joined #openstack-dns | 14:36 | |
gstaicu | Kiall: I do not know the default value for designate | 14:37 |
gstaicu | Kiall: is it the same? | 14:38 |
*** nkinder has joined #openstack-dns | 14:39 | |
gstaicu | Kiall: I have verified in the designate-sink log | 14:40 |
gstaicu | Kiall: it is the same | 14:40 |
gstaicu | Kiall: how is designate take message from the queue? | 14:43 |
gstaicu | Kiall: is it realising a binding to what neutron.notifications queue? | 14:44 |
*** betsy has quit IRC | 14:47 | |
*** vinod1 has quit IRC | 14:50 | |
*** rmoe has quit IRC | 14:57 | |
Kiall | gstaicu: bring up the RMQ management UI, and check that designate is bound to the neutron notifictions queue | 15:02 |
Kiall | Maybe something is off there, and it's listening on the wrong queue | 15:03 |
gstaicu | Kiall: I have designate.notifications.handler:quantum_floatingip.neutron.notifications.info | 15:05 |
gstaicu | Kiall: listenting to neutron | 15:05 |
gstaicu | using as a routing key "notifications_info" | 15:06 |
gstaicu | Kiall: but when I do rabbitmqctl list_queues|grep neutron | 15:07 |
gstaicu | Kiall: I see just: designate.notifications.handler:quantum_floatingip.neutron.notifications.info 0 | 15:07 |
gstaicu | Kiall: I do not see something like just "neutron" | 15:08 |
*** vinod1 has joined #openstack-dns | 15:08 | |
Kiall | so the queue name will match the plugin, which is quantum .. But it's bound using notifications_info, which seems wrong to me from memory | 15:09 |
Kiall | are there any other bindings on the neutron exchange for "notifications" or "notifications.info" ? | 15:10 |
gstaicu | Kiall: to the neutron exchange | 15:11 |
gstaicu | Kiall: besides designate.notifications.handler:quantum_floatingip.neutron.notifications.info routed on key notifications.info | 15:12 |
gstaicu | Kiall: there is also notifications.info routed on key notifications.info | 15:13 |
*** vinod1 has quit IRC | 15:14 | |
gstaicu | Kiall: there is another aspect....my instances are receiving just fixed ips | 15:14 |
Kiall | Got a meeting, so have to run.. But something, somewhere still seems wrong .. Not sure exactly what though | 15:14 |
gstaicu | Kiall: thanks a lot | 15:14 |
gstaicu | Kiall: I will continue to fight the problem | 15:15 |
gstaicu | Kiall: and I will tell you how I solved it | 15:15 |
gstaicu | Kiall: and maybe we will write a doc about this | 15:15 |
openstackgerrit | Endre Karlson proposed a change to stackforge/designate: Document the PowerDNS backend https://review.openstack.org/81288 | 15:22 |
*** richm has joined #openstack-dns | 15:25 | |
*** vinod1 has joined #openstack-dns | 15:30 | |
*** jmcbride has quit IRC | 15:35 | |
*** betsy has joined #openstack-dns | 15:47 | |
*** rmoe has joined #openstack-dns | 15:54 | |
*** vinod1 has quit IRC | 15:58 | |
*** jorgem has joined #openstack-dns | 16:00 | |
*** jmcbride has joined #openstack-dns | 16:09 | |
*** jmcbride has quit IRC | 16:10 | |
*** jmcbride has joined #openstack-dns | 16:10 | |
*** jmcbride has quit IRC | 16:25 | |
*** tsimmons has joined #openstack-dns | 16:25 | |
*** jmcbride has joined #openstack-dns | 16:29 | |
*** rossk has joined #openstack-dns | 16:33 | |
gstaicu | Kiall: I think I have an ideea why this is happening | 16:39 |
gstaicu | Kiall: as network topology I am using flatDHCP | 16:40 |
gstaicu | Kiall: and every time I am spawning an instance in the queue there are only events like port.create.start | 16:40 |
gstaicu | Kiall: port.create.end, port.delete.start, port.delete.end | 16:41 |
gstaicu | Kiall: this could mean that I had to write a new handler for these type of events; and to extract for these type of events the ip address | 16:43 |
*** jmcbride has quit IRC | 17:15 | |
*** jmcbride has joined #openstack-dns | 17:16 | |
*** jmcbride has quit IRC | 17:17 | |
*** tsimmons has quit IRC | 17:30 | |
*** vinod1 has joined #openstack-dns | 17:33 | |
*** vinod1 has quit IRC | 17:39 | |
*** vinod1 has joined #openstack-dns | 17:44 | |
*** vinod1 has joined #openstack-dns | 17:44 | |
*** crc32 has joined #openstack-dns | 17:50 | |
*** tsimmons has joined #openstack-dns | 17:55 | |
*** vinod1 has quit IRC | 17:59 | |
*** tsimmons1 has joined #openstack-dns | 18:01 | |
*** vinod1 has joined #openstack-dns | 18:01 | |
*** tsimmons has quit IRC | 18:03 | |
*** shakamunyi has joined #openstack-dns | 18:04 | |
*** msisk_ has joined #openstack-dns | 18:04 | |
*** msisk has quit IRC | 18:04 | |
*** vinod1 has quit IRC | 18:06 | |
*** vinod1 has joined #openstack-dns | 18:09 | |
*** vinod1 has quit IRC | 18:16 | |
*** shakamunyi has quit IRC | 18:18 | |
*** shakamunyi has joined #openstack-dns | 18:27 | |
*** vinod1 has joined #openstack-dns | 18:35 | |
*** vinod1 has quit IRC | 18:46 | |
*** shakamunyi has quit IRC | 18:49 | |
*** betsy has quit IRC | 19:03 | |
*** vinod1 has joined #openstack-dns | 19:17 | |
*** jmcbride has joined #openstack-dns | 19:28 | |
*** vinod1 has quit IRC | 19:28 | |
*** jmcbride has quit IRC | 19:28 | |
*** jmcbride has joined #openstack-dns | 19:28 | |
*** vinod1 has joined #openstack-dns | 19:31 | |
*** vinod1 has quit IRC | 19:32 | |
*** vinod1 has joined #openstack-dns | 19:32 | |
*** jmcbride has quit IRC | 19:35 | |
*** jmcbride has joined #openstack-dns | 19:36 | |
*** gstaicu has quit IRC | 19:41 | |
*** betsy has joined #openstack-dns | 19:53 | |
*** jmcbride has quit IRC | 20:04 | |
*** vinod2 has joined #openstack-dns | 20:09 | |
*** vinod1 has quit IRC | 20:12 | |
*** jmcbride has joined #openstack-dns | 20:13 | |
*** jmcbride1 has joined #openstack-dns | 20:21 | |
*** tsimmons1 has quit IRC | 20:23 | |
*** jmcbride has quit IRC | 20:24 | |
*** tsimmons has joined #openstack-dns | 20:27 | |
*** msisk_ has quit IRC | 20:31 | |
*** tsimmons has left #openstack-dns | 20:47 | |
*** pravka_ has quit IRC | 20:49 | |
*** pravka has joined #openstack-dns | 20:49 | |
*** msisk has joined #openstack-dns | 21:09 | |
*** msisk has quit IRC | 21:09 | |
*** msisk has joined #openstack-dns | 21:14 | |
*** jmcbride1 has quit IRC | 21:21 | |
*** pravka has quit IRC | 21:56 | |
*** CaptTofu has quit IRC | 21:57 | |
*** pravka has joined #openstack-dns | 21:58 | |
*** CaptTofu has joined #openstack-dns | 21:58 | |
*** eankutse has quit IRC | 22:01 | |
*** CaptTofu has quit IRC | 22:02 | |
openstackgerrit | Endre Karlson proposed a change to stackforge/designate: Document the PowerDNS backend https://review.openstack.org/81288 | 22:03 |
*** nkinder has quit IRC | 22:12 | |
openstackgerrit | Betsy Luzader proposed a change to stackforge/designate: Blacklists API Documentation https://review.openstack.org/80453 | 22:20 |
*** mwagner_lap has quit IRC | 22:21 | |
*** nkinder has joined #openstack-dns | 22:22 | |
*** vinod2 has quit IRC | 22:23 | |
*** pravka has quit IRC | 22:43 | |
*** pravka has joined #openstack-dns | 22:46 | |
*** nkinder has quit IRC | 22:57 | |
openstackgerrit | A change was merged to stackforge/designate: Blacklists API Documentation https://review.openstack.org/80453 | 23:01 |
openstackgerrit | A change was merged to stackforge/designate: Document the PowerDNS backend https://review.openstack.org/81288 | 23:01 |
*** crc32 has quit IRC | 23:13 | |
*** vinod1 has joined #openstack-dns | 23:16 | |
*** eankutse has joined #openstack-dns | 23:21 | |
*** eankutse has quit IRC | 23:21 | |
*** eankutse has joined #openstack-dns | 23:22 | |
*** vinod1 has quit IRC | 23:39 | |
*** vinod1 has joined #openstack-dns | 23:46 | |
*** vinod1 has quit IRC | 23:48 | |
*** jmcbride has joined #openstack-dns | 23:56 | |
*** CaptTofu has joined #openstack-dns | 23:58 | |
*** jmcbride has quit IRC | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!