Tuesday, 2014-03-18

*** rmoe has joined #openstack-dns00:16
*** betsy has joined #openstack-dns00:22
*** eankutse has joined #openstack-dns00:27
*** matsuhashi has joined #openstack-dns00:27
*** eankutse has quit IRC00:27
*** eankutse has joined #openstack-dns00:27
*** rektide has joined #openstack-dns00:29
*** CaptTofu has joined #openstack-dns00:37
*** eankutse has quit IRC00:44
*** simonmcc_ has quit IRC00:55
*** simonmcc_ has joined #openstack-dns00:57
*** CaptTofu has quit IRC00:59
*** CaptTofu has joined #openstack-dns00:59
*** CaptTofu has quit IRC01:03
*** CaptTofu has joined #openstack-dns01:07
*** simonmcc_ has quit IRC01:11
*** simonmcc_ has joined #openstack-dns01:15
*** CaptTofu has quit IRC01:18
*** rossk has quit IRC01:27
*** CaptTofu has joined #openstack-dns01:27
*** nosnos has joined #openstack-dns01:31
*** nosnos has quit IRC01:38
*** nosnos has joined #openstack-dns01:38
*** HenryG has joined #openstack-dns01:43
*** vinod1 has joined #openstack-dns01:48
*** vinod1 has left #openstack-dns02:08
*** CaptTofu has quit IRC02:11
*** richm has quit IRC02:41
*** jmcbride has joined #openstack-dns02:44
*** crc32 has quit IRC02:55
*** CaptTofu has joined #openstack-dns03:03
*** jmcbride has quit IRC03:04
*** matsuhashi has quit IRC03:14
*** jmcbride has joined #openstack-dns03:19
*** matsuhashi has joined #openstack-dns03:20
*** jmcbride has quit IRC03:23
*** matsuhashi has quit IRC03:30
*** matsuhashi has joined #openstack-dns03:33
*** matsuhashi has quit IRC03:42
*** nosnos has quit IRC03:58
*** mwagner_lap is now known as mwagner_zzz04:25
*** jmcbride has joined #openstack-dns04:29
*** CaptTofu has quit IRC04:45
*** CaptTofu has joined #openstack-dns04:46
*** CaptTofu has quit IRC04:50
*** matsuhashi has joined #openstack-dns04:55
*** nosnos has joined #openstack-dns04:59
*** matsuhashi has quit IRC06:30
*** CaptTofu has joined #openstack-dns06:46
*** matsuhashi has joined #openstack-dns06:49
*** CaptTofu has quit IRC06:51
*** JensOfSw_ has quit IRC07:20
*** CaptTofu has joined #openstack-dns08:47
*** CaptTofu has quit IRC08:52
*** ytwu has left #openstack-dns09:16
*** nosnos_ has joined #openstack-dns10:02
*** nosnos has quit IRC10:05
*** matsuhashi has quit IRC10:25
*** CaptTofu has joined #openstack-dns10:48
*** CaptTofu has quit IRC10:52
*** gstaicu has joined #openstack-dns11:26
gstaicuhi11:26
gstaicucan someone help me with the integration of designate in openstack havana?11:26
*** nosnos_ has quit IRC11:30
*** nosnos has joined #openstack-dns11:31
*** CaptTofu has joined #openstack-dns11:33
*** mwagner_zzz has quit IRC11:35
ekarlsogstaicu: sure11:41
*** CaptTofu has quit IRC12:05
*** CaptTofu has joined #openstack-dns12:06
*** CaptTofu has quit IRC12:10
gstaicuekarlso: I have an havana12:41
ekarlsogstaicu: what is the issue ? :)12:42
*** CaptTofu has joined #openstack-dns12:42
gstaicuekarlso: cluster and I would like to use designate to register name of the instance12:42
gstaicuekarlso: first observation I would like to know what notification handlers are available12:43
gstaicuekarlso: I have installed designate 2013.2-412:43
gstaicuekarlso: and from what I am seeing in the /usr/share/pyshared/designate/notification_handler12:44
gstaicuekarlso: I have nova handler and quantum12:44
gstaicuekarlso: isnt't also neutron?12:45
ekarlsoquantum is the same as neutron but12:46
ekarlsoI would recommend u running on trunk instead or what Kiall ?12:46
*** CaptTofu has quit IRC12:47
Kiall2013.2 is the Designate Havana release.. So it's probably saner to use that with Havana ..12:47
gstaicuekarlso: I am using this repository:  http://ppa.launchpad.net/designate-ppa/havana/ubuntu12:48
KiallAnyway 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 it12:48
Kiallhttps://github.com/stackforge/designate/tree/master/contrib/designate-ext-samplehandler shows a sample handler plugin12:48
gstaicuKiall: this means that if I want to use neutron I should write the corresponding handler?12:49
Kiallgstaicu: Neutron was called Quantum before, we didn't rename the handler before the release though.. It should work12:50
gstaicuKiall: ok12:50
KiallBut - 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
KiallSince 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
gstaicuKiall: at this moment my understanding was that the configured sink handler will look in the queue for a certain type of the message12:52
KiallCorrect, the sink service will grab events from the neutron/nova event bus, then it will hand those messages to the enabled plugins12:53
gstaicuKiall: and based on that type of the message will call designate to create a record according with configured format12:53
KiallThe plugins do the "interesting stuff" of actually creating/deleting records etc12:53
gstaicuKiall: and this means that in my case I can use quantum handler12:54
KiallThe 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
gstaicuKiall: and I should change the control_exchange parameter?12:54
KiallSince some people want 1-2-3-4.mydomain.com, others want <name>.cloud.com, others want <name>, others want <name>.<tenant>.cloud.com etc12:54
Kiallwe decided to do the most basic, and let end users write their own plugin to decide what they want done with the events12:55
gstaicuKiall: with this repository:  http://ppa.launchpad.net/designate-ppa/havana/ubuntu which handle is by default supported?12:57
gstaicuKiall: can I use neutron with this repository as it is?12:57
KiallThe 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
gstaicuKiall: I will try with quantum13:00
gstaicuKiall: and if it does not work I will try to write a plugin for neutron13:01
gstaicuKiall: 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.py13:03
gstaicuKiall: I will try for the beginning to use that one13:03
KiallThe quantum one was literally renamed to neutron13:03
Kiallit's identical in every other way13:03
gstaicuKiall: I have copied neutron.py from the project to /usr/share/pyshared/designate/notification_handler13:13
gstaicuKiall: in the section [service:sink]13:13
KiallThat'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 you13:14
gstaicuKiall: in /etc/desigante/designate.conf13:14
KiallBut13:14
KiallThe quantum.py one in 2013.2 is literally identical to neutron.py in trunk... There's no need to switch it out13:14
gstaicuKiall: ok13:15
gstaicuthan I will try with that one13:15
KiallJust give it the right settings, and it should do it's thing13:15
gstaicuKiall: but I will change the exchange, right?13:15
KiallYea - Point it at your Neutron exchange13:15
*** eankutse has joined #openstack-dns13:15
*** jmcbride has joined #openstack-dns13:16
*** eankutse has quit IRC13:18
gstaicuKiall: I did it13:18
*** eankutse has joined #openstack-dns13:18
*** CaptTofu has joined #openstack-dns13:18
gstaicuKiall: designate-sink starte without any errors13:19
gstaicuKiall: so far so good....:) thanks13:19
gstaicuKiall: now I will try to start an instance13:19
gstaicuKiall: I have enabled debug in designate.conf13:20
gstaicuKiall: I have started an instance13:22
gstaicuKiall: but I can not see any messages in the log of designate-sink13:22
gstaicuKiall: handler:quantum_floatingip.notification_topics = ['monitor']13:24
gstaicuKiall: but it seams that in monitor queue are 0 messages13:26
gstaicuKiall: here is the output of the rabbitmqctl list_queues|grep monitor13:26
gstaicuKiall: http://pastebin.com/kqweSBKz13:26
gstaicuKiall: probably nova does not send notifications in monitor queue13:27
gstaicuKiall: I will try to modify the type of notification13:27
Kiallgstaicu: the notification_topics setting should match the neutron notification_topics setting13:31
*** ytwu has joined #openstack-dns13:32
gstaicuKiall: it is strange13:37
gstaicuI have modified in the designate.conf13:37
gstaicuKiall: notification_topics = notifications13:38
ekarlsogstaicu: have you setup neutron etc to actually emit the notifications ?13:38
KiallYes, but it's been a while13:39
gstaicuKiall: but when I restart designate-sink13:39
gstaicuKiall: in log I am seeing:   DEBUG [designate.openstack.common.service] service:sink.enabled_notification_handlers = ['quantum_floatingip']13:39
gstaicuKiall:  DEBUG [designate.openstack.common.service] handler:quantum_floatingip.notification_topics = ['monitor']13:39
gstaicuKiall: should not be notifications in place of monitor?13:40
gstaicuekarlso: I will verify also what notifications neutron is sending13:40
KiallWhich "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
KiallThe [DEFAULT] one is where Designate sends notifications13:41
Kiallthe [handler:quantum] one is where we listen for Quantum/Neutron notifications13:41
KiallActually - The section is called [handler:quantum_floatingip], not handler:quantum], my mistake13:42
gstaicuKiall: [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
gstaicuKiall: this is what I have in my config13:42
Kiall[handler:qunatum_floating] <-- Looks like a typo13:43
Kiallvs13:43
Kiall[handler:quantum_floatingip]13:43
*** mwagner_lap has joined #openstack-dns13:43
gstaicuKiall: sorry, I will modify now13:43
*** nkinder has quit IRC13:52
*** nosnos has quit IRC13:56
*** jmcbride has quit IRC13:59
gstaicuKiall: I repaired the typo14:02
gstaicuKiall: start an instance14:03
gstaicuKiall: before restart the instace restart designate-sink ....:)14:03
gstaicuKiall: the log looks ok14:03
gstaicuKiall: but when I spawn the instance I can not see anything14:04
gstaicuin the designate-sink log14:04
Kiallgstaicu: 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 message14:04
gstaicuKiall: from my understanding the queue where the notifications are sent is notification.info14:06
gstaicuwith rabbitmqctl list_queues|grep notifications14:07
gstaicuKiall: notifications.info      4214:07
KiallSo .. 42 in there, it's sending the right stuff then14:08
Kiall(ignore .info, that's normal)14:08
KiallIs designate and neutron on the same RabbitMQ + RabbitMQ VHost?14:08
gstaicuKiall: touche14:09
gstaicuKiall: :)14:09
gstaicuKiall: I have an rabbitmq cluster14:09
gstaicuKiall: but when I configured designate14:10
KiallWell, both on the same cluster should be fine too ;)14:10
gstaicuKiall: on one of the node in the cluster14:10
gstaicuKiall: in the designate.conf I did not specified the cluster14:10
gstaicuKiall: I let it default14:10
gstaicuKiall: localhost14:11
gstaicuKiall: I will configure designate to connect  to the cluster14:11
gstaicuKiall: maybe this is the problem14:11
*** vinod1 has joined #openstack-dns14:17
*** CaptTofu has quit IRC14:19
gstaicuKiall: not getting it14:27
gstaicuKiall: :)14:27
gstaicuKiall: changed the configuration of designate.conf14:29
KiallAre both designate and neutron on the same vhost?14:29
gstaicuKiall: the setup is like this14:30
gstaicuKiall: 2 servers in a rabbitmq cluster14:30
gstaicuKiall: on the same 2 servers plus another one14:31
gstaicuKiall: I have neutron-server running14:31
KiallThe 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 client14:31
gstaicuKiall: neutron-server on the servers connect all to the rabbitmq cluster14:32
gstaicuKiall: so should be ok14:32
KiallYea, should be.14:33
KiallAre both neutron and designate on the same RMQ vhost? That's the next likely thing.14:33
*** jmcbride has joined #openstack-dns14:33
*** msisk has joined #openstack-dns14:33
gstaicuKiall: in the neutron.conf I did not change the rabbit_virtual_host parameter14:35
gstaicuKiall: I let it default14:35
gstaicuKiall: which in documetation it says it is "/"14:35
*** CaptTofu has joined #openstack-dns14:36
gstaicuKiall: I do not know the default value for designate14:37
gstaicuKiall: is it the same?14:38
*** nkinder has joined #openstack-dns14:39
gstaicuKiall: I have verified in the designate-sink log14:40
gstaicuKiall: it is the same14:40
gstaicuKiall: how is designate take message from the queue?14:43
gstaicuKiall: is it realising a binding to what neutron.notifications queue?14:44
*** betsy has quit IRC14:47
*** vinod1 has quit IRC14:50
*** rmoe has quit IRC14:57
Kiallgstaicu: bring up the RMQ management UI, and check that designate is bound to the neutron notifictions queue15:02
KiallMaybe something is off there, and it's listening on the wrong queue15:03
gstaicuKiall: I have designate.notifications.handler:quantum_floatingip.neutron.notifications.info15:05
gstaicuKiall: listenting to neutron15:05
gstaicuusing as a routing key "notifications_info"15:06
gstaicuKiall: but when I do rabbitmqctl list_queues|grep neutron15:07
gstaicuKiall: I see just: designate.notifications.handler:quantum_floatingip.neutron.notifications.info   015:07
gstaicuKiall: I do not see something like just "neutron"15:08
*** vinod1 has joined #openstack-dns15:08
Kiallso the queue name will match the plugin, which is quantum .. But it's bound using notifications_info, which seems wrong to me from memory15:09
Kiallare there any other bindings on the neutron exchange for "notifications" or "notifications.info" ?15:10
gstaicuKiall: to the neutron exchange15:11
gstaicuKiall: besides designate.notifications.handler:quantum_floatingip.neutron.notifications.info routed on key notifications.info15:12
gstaicuKiall: there is also notifications.info routed on key notifications.info15:13
*** vinod1 has quit IRC15:14
gstaicuKiall: there is another aspect....my instances are receiving just fixed ips15:14
KiallGot a meeting, so have to run.. But something, somewhere still seems wrong .. Not sure exactly what though15:14
gstaicuKiall: thanks a lot15:14
gstaicuKiall: I will continue to fight the problem15:15
gstaicuKiall: and I will tell you how I solved it15:15
gstaicuKiall: and maybe we will write a doc about this15:15
openstackgerritEndre Karlson proposed a change to stackforge/designate: Document the PowerDNS backend  https://review.openstack.org/8128815:22
*** richm has joined #openstack-dns15:25
*** vinod1 has joined #openstack-dns15:30
*** jmcbride has quit IRC15:35
*** betsy has joined #openstack-dns15:47
*** rmoe has joined #openstack-dns15:54
*** vinod1 has quit IRC15:58
*** jorgem has joined #openstack-dns16:00
*** jmcbride has joined #openstack-dns16:09
*** jmcbride has quit IRC16:10
*** jmcbride has joined #openstack-dns16:10
*** jmcbride has quit IRC16:25
*** tsimmons has joined #openstack-dns16:25
*** jmcbride has joined #openstack-dns16:29
*** rossk has joined #openstack-dns16:33
gstaicuKiall: I think I have an ideea why this is happening16:39
gstaicuKiall: as network topology I am using flatDHCP16:40
gstaicuKiall: and every time I am spawning an instance in the queue there are only events like port.create.start16:40
gstaicuKiall: port.create.end, port.delete.start, port.delete.end16:41
gstaicuKiall: 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 address16:43
*** jmcbride has quit IRC17:15
*** jmcbride has joined #openstack-dns17:16
*** jmcbride has quit IRC17:17
*** tsimmons has quit IRC17:30
*** vinod1 has joined #openstack-dns17:33
*** vinod1 has quit IRC17:39
*** vinod1 has joined #openstack-dns17:44
*** vinod1 has joined #openstack-dns17:44
*** crc32 has joined #openstack-dns17:50
*** tsimmons has joined #openstack-dns17:55
*** vinod1 has quit IRC17:59
*** tsimmons1 has joined #openstack-dns18:01
*** vinod1 has joined #openstack-dns18:01
*** tsimmons has quit IRC18:03
*** shakamunyi has joined #openstack-dns18:04
*** msisk_ has joined #openstack-dns18:04
*** msisk has quit IRC18:04
*** vinod1 has quit IRC18:06
*** vinod1 has joined #openstack-dns18:09
*** vinod1 has quit IRC18:16
*** shakamunyi has quit IRC18:18
*** shakamunyi has joined #openstack-dns18:27
*** vinod1 has joined #openstack-dns18:35
*** vinod1 has quit IRC18:46
*** shakamunyi has quit IRC18:49
*** betsy has quit IRC19:03
*** vinod1 has joined #openstack-dns19:17
*** jmcbride has joined #openstack-dns19:28
*** vinod1 has quit IRC19:28
*** jmcbride has quit IRC19:28
*** jmcbride has joined #openstack-dns19:28
*** vinod1 has joined #openstack-dns19:31
*** vinod1 has quit IRC19:32
*** vinod1 has joined #openstack-dns19:32
*** jmcbride has quit IRC19:35
*** jmcbride has joined #openstack-dns19:36
*** gstaicu has quit IRC19:41
*** betsy has joined #openstack-dns19:53
*** jmcbride has quit IRC20:04
*** vinod2 has joined #openstack-dns20:09
*** vinod1 has quit IRC20:12
*** jmcbride has joined #openstack-dns20:13
*** jmcbride1 has joined #openstack-dns20:21
*** tsimmons1 has quit IRC20:23
*** jmcbride has quit IRC20:24
*** tsimmons has joined #openstack-dns20:27
*** msisk_ has quit IRC20:31
*** tsimmons has left #openstack-dns20:47
*** pravka_ has quit IRC20:49
*** pravka has joined #openstack-dns20:49
*** msisk has joined #openstack-dns21:09
*** msisk has quit IRC21:09
*** msisk has joined #openstack-dns21:14
*** jmcbride1 has quit IRC21:21
*** pravka has quit IRC21:56
*** CaptTofu has quit IRC21:57
*** pravka has joined #openstack-dns21:58
*** CaptTofu has joined #openstack-dns21:58
*** eankutse has quit IRC22:01
*** CaptTofu has quit IRC22:02
openstackgerritEndre Karlson proposed a change to stackforge/designate: Document the PowerDNS backend  https://review.openstack.org/8128822:03
*** nkinder has quit IRC22:12
openstackgerritBetsy Luzader proposed a change to stackforge/designate: Blacklists API Documentation  https://review.openstack.org/8045322:20
*** mwagner_lap has quit IRC22:21
*** nkinder has joined #openstack-dns22:22
*** vinod2 has quit IRC22:23
*** pravka has quit IRC22:43
*** pravka has joined #openstack-dns22:46
*** nkinder has quit IRC22:57
openstackgerritA change was merged to stackforge/designate: Blacklists API Documentation  https://review.openstack.org/8045323:01
openstackgerritA change was merged to stackforge/designate: Document the PowerDNS backend  https://review.openstack.org/8128823:01
*** crc32 has quit IRC23:13
*** vinod1 has joined #openstack-dns23:16
*** eankutse has joined #openstack-dns23:21
*** eankutse has quit IRC23:21
*** eankutse has joined #openstack-dns23:22
*** vinod1 has quit IRC23:39
*** vinod1 has joined #openstack-dns23:46
*** vinod1 has quit IRC23:48
*** jmcbride has joined #openstack-dns23:56
*** CaptTofu has joined #openstack-dns23:58
*** jmcbride has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!