rjrjr | when are mugsie and kiall usually on? | 00:12 |
---|---|---|
*** artom has quit IRC | 00:18 | |
*** openstackgerrit has quit IRC | 00:44 | |
*** openstackgerrit has joined #openstack-dns | 00:44 | |
*** ChanServ sets mode: +v openstackgerrit | 00:44 | |
*** eankutse1 has joined #openstack-dns | 00:49 | |
*** jorgem has quit IRC | 00:52 | |
*** richm has quit IRC | 00:52 | |
*** eankutse has quit IRC | 00:52 | |
*** eankutse1 has quit IRC | 00:53 | |
*** rossk has quit IRC | 01:08 | |
*** CaptTofu has quit IRC | 01:12 | |
*** nosnos has joined #openstack-dns | 01:29 | |
*** CaptTofu has joined #openstack-dns | 01:34 | |
*** jmcbride has joined #openstack-dns | 01:41 | |
*** jmcbride has quit IRC | 01:43 | |
*** jmcbride has joined #openstack-dns | 01:45 | |
*** jmcbride1 has joined #openstack-dns | 01:46 | |
*** jmcbride has quit IRC | 01:50 | |
*** jmcbride1 has quit IRC | 01:51 | |
*** vinod has joined #openstack-dns | 02:03 | |
*** jmcbride has joined #openstack-dns | 03:10 | |
*** vinod has quit IRC | 03:23 | |
*** jmcbride has quit IRC | 03:26 | |
*** jmcbride has joined #openstack-dns | 03:31 | |
*** CaptTofu has quit IRC | 03:32 | |
*** jmcbride has quit IRC | 03:34 | |
*** jmcbride has joined #openstack-dns | 03:36 | |
*** jmcbride has quit IRC | 04:19 | |
*** crc32 has quit IRC | 05:19 | |
*** shakayumi has joined #openstack-dns | 05:30 | |
*** CaptTofu has joined #openstack-dns | 05:33 | |
*** CaptTofu has quit IRC | 05:38 | |
*** baribalbear has joined #openstack-dns | 06:59 | |
*** CaptTofu has joined #openstack-dns | 07:00 | |
*** CaptTofu has quit IRC | 07:06 | |
*** nosnos has quit IRC | 07:31 | |
*** nosnos_ has joined #openstack-dns | 07:31 | |
*** nosnos_ has quit IRC | 08:04 | |
*** nosnos has joined #openstack-dns | 08:04 | |
*** baribalbear has quit IRC | 08:45 | |
*** CaptTofu has joined #openstack-dns | 09:03 | |
*** CaptTofu has quit IRC | 09:07 | |
*** sballe has quit IRC | 09:08 | |
*** sballe has joined #openstack-dns | 09:08 | |
*** sballe has quit IRC | 09:17 | |
*** shakayumi has quit IRC | 10:07 | |
*** CaptTofu has joined #openstack-dns | 11:03 | |
*** CaptTofu has quit IRC | 11:08 | |
*** CaptTofu has joined #openstack-dns | 11:22 | |
openstackgerrit | A change was merged to stackforge/designate: UUID changes to api / utils https://review.openstack.org/75634 | 11:37 |
openstackgerrit | A change was merged to stackforge/designate: Fill in missing Records tests for V2 api https://review.openstack.org/75654 | 11:39 |
openstackgerrit | Kiall Mac Innes proposed a change to stackforge/designate: Ensure Storage Implementions match the Interface https://review.openstack.org/75633 | 11:45 |
*** baribalbear has joined #openstack-dns | 11:48 | |
ekarlso | baribalbear: hi | 11:54 |
ekarlso | i tested the neutron floatibngip handler using devstack yesterday and it worked | 11:54 |
openstackgerrit | A change was merged to stackforge/designate: Ensure that wanted API calls returns exceptions https://review.openstack.org/76599 | 12:05 |
*** ekarlso has quit IRC | 12:09 | |
*** vinod1 has joined #openstack-dns | 12:10 | |
*** cflmarques has joined #openstack-dns | 12:11 | |
*** vinod1 has quit IRC | 12:30 | |
*** vinod1 has joined #openstack-dns | 12:31 | |
*** vinod1 has quit IRC | 12:32 | |
*** mwagner_lap has quit IRC | 12:40 | |
*** ekarlso has joined #openstack-dns | 13:23 | |
*** sballe has joined #openstack-dns | 13:33 | |
*** artom has joined #openstack-dns | 13:40 | |
*** artom has quit IRC | 13:44 | |
*** nosnos has quit IRC | 13:56 | |
*** eankutse has joined #openstack-dns | 13:57 | |
*** CaptTofu has quit IRC | 14:01 | |
*** CaptTofu has joined #openstack-dns | 14:09 | |
*** jmcbride has joined #openstack-dns | 14:22 | |
*** richm has joined #openstack-dns | 14:32 | |
*** nkinder has quit IRC | 14:45 | |
*** msisk has joined #openstack-dns | 15:03 | |
*** msisk has quit IRC | 15:04 | |
*** msisk has joined #openstack-dns | 15:04 | |
*** mnaser has quit IRC | 15:08 | |
*** mnaser has joined #openstack-dns | 15:08 | |
*** eankutse has quit IRC | 15:10 | |
*** eankutse has joined #openstack-dns | 15:10 | |
*** eankutse has quit IRC | 15:11 | |
*** artom has joined #openstack-dns | 15:12 | |
*** vinod has joined #openstack-dns | 15:29 | |
*** nkinder has joined #openstack-dns | 15:32 | |
artom | ekarlso, PTR support is currently implemented only for floating IPs, yes? | 15:59 |
ekarlso | artom: indeed | 16:02 |
ekarlso | artom: what would you like it for ? | 16:02 |
artom | The other stuff. | 16:02 |
ekarlso | private networks ? | 16:02 |
artom | Or even fixed on public networks. | 16:03 |
*** tsimmons has joined #openstack-dns | 16:03 | |
ekarlso | artom: or, really there's nothing keeping you from creating PTR records for those | 16:03 |
ekarlso | it just won't be "automagic" | 16:03 |
ekarlso | as in all the zone creation etc is managed | 16:03 |
rjrjr | the networks are share among tenants. | 16:10 |
kiall | artom: the issue with doing PTR's for private networks is the networks can overlap | 16:10 |
kiall | 2 tenants can both have 10.0.0.0/8 ... so who gets's the 10.in-addr.arpa zone? | 16:10 |
rjrjr | i'm looking at taking this https://wiki.openstack.org/wiki/Designate/Blueprints/Reverse and adding the fixed IP support. | 16:11 |
artom | kiall, yeah, I think client only wants PTR for public-facing stuff. | 16:11 |
artom | But that can include fixed IPs... | 16:11 |
kiall | Right, so if those are auto allocated public IPs, they are technically also floating IPs | 16:11 |
artom | Hrmm, perhaps. Not that knowledgeable about Neutron. | 16:11 |
kiall | (Unless your doing something really weird with networking that I'm not aware of!) | 16:11 |
rjrjr | artom, we have a flat network at E-Bay, so our fixed IPs are our public IPs. | 16:12 |
*** eankutse has joined #openstack-dns | 16:12 | |
*** eankutse has quit IRC | 16:12 | |
*** eankutse has joined #openstack-dns | 16:13 | |
artom | rjrjr, yeah, it might be something similar at Cloudwatt. | 16:13 |
artom | Still in the exploratory phase here :P | 16:13 |
*** ytwu1 has joined #openstack-dns | 16:14 | |
rjrjr | kiall, i've been doing my homework on this. i want to create the blueprint to handle adding fixed IP PTR records. would like to review tomorrow if i get it done. | 16:14 |
kiall | rjrjr: I assume there's no overlapping IPs then? | 16:14 |
rjrjr | no, we also share the network(s). | 16:14 |
kiall | If that's the case, then we can probably do something very similar to FloatingIPs | 16:14 |
kiall | just with an on/off flag that defaults to off | 16:15 |
*** baribalbear has quit IRC | 16:15 | |
rjrjr | i was looking at this. should i key off the IP address and use the Nova fixed-ip-get to get the hostname. | 16:16 |
*** ytwu has quit IRC | 16:16 | |
kiall | It depends, Nova has no (meaningful) "hostname" attribute on instances.. So we've defaulted to to not auto-creating stuff and providing sample sink handlers for creating records | 16:17 |
ekarlso | artom: if it's neutron then it's not fixed ip's no ? | 16:18 |
ekarlso | thought that was a nova thing | 16:18 |
kiall | For FloatingIPs, after a tenant releases and another "creates" it, it get's a new ID.. Hence we do some trickery with both the IDs and IPs to form a unique key | 16:18 |
rjrjr | i was thinking about the /reverse/fixedip API. | 16:18 |
kiall | Ah, so.. FixedIPs don't actually get an ID.. Right | 16:18 |
rjrjr | correct. | 16:19 |
kiall | I wonder if port_id or something is suitable? | 16:19 |
rjrjr | in a VM creation, we get instance_id, IP address, and hostname. | 16:19 |
ekarlso | kiall: port_id get's re-created I think on each new port... | 16:19 |
ekarlso | like each new service that has a port, vm or whatever | 16:19 |
*** ytwu has joined #openstack-dns | 16:19 | |
kiall | rjrjr: Well, I believe we get those same details for auto-created ports | 16:20 |
kiall | and manually created ports can have the name assigned to them | 16:20 |
rjrjr | sorry, not familiar with ports. | 16:20 |
kiall | There is a neutron bug around DNS naming in dnsmasq being tied to ports rather than instances | 16:20 |
kiall | A port is basically just a NIC on your VM | 16:21 |
*** ytwu1 has quit IRC | 16:21 | |
rjrjr | okay. | 16:21 |
kiall | when you boot an instance with nova (and your using neutron), it will auto create a port unless you say "use port 12345" | 16:21 |
kiall | so the network.port.create event should (maybe?) have the right info. | 16:21 |
kiall | I've not looked recently though | 16:21 |
rjrjr | what is the right info we are looking for? are you saying the hostname is wrong in a instance.create.end? | 16:24 |
rjrjr | it looks right to me. | 16:24 |
kiall | It's that Nova asks for an "Instance Name" which you *could* fill in something that looks like a valid hostname | 16:25 |
kiall | But - You don't have to | 16:25 |
kiall | I'm pretty sure !"£$%%^^&**(( is a valid "Instance Name" | 16:25 |
rjrjr | joy! | 16:25 |
artom | Well with Unicode domain names that's now possible ;) | 16:25 |
kiall | artom: lol.. | 16:26 |
rjrjr | so, you are saying the port event would have a valid hostname? | 16:26 |
kiall | Even so, I personally call my instances blabla01.domain.com etc | 16:26 |
kiall | while at HP, we tend to use dns-region-role0001 etc | 16:26 |
kiall | (i.e. FQDN vs Short name) | 16:26 |
rjrjr | hence the notification handlers are customizable. | 16:27 |
rjrjr | at E-Bay, we are using the metadata to pass the hostname. | 16:28 |
rjrjr | (short) | 16:28 |
kiall | There's another option :) | 16:28 |
rjrjr | back to the /reverse/fixedips API. :) | 16:28 |
*** jorgem has joined #openstack-dns | 16:29 | |
rjrjr | on compute.instance.create.end we get the IP address and the hostname (in metadata, as valid hostname, etc.) | 16:29 |
rjrjr | should the API be /reverse/fixedips/<ip-address> and the body contain the hostname to create the PTR record? | 16:30 |
ekarlso | rjrjr: when you mean fixedip's what you mean then ? | 16:31 |
rjrjr | we could use Nova's fixed-ip-get or some other call to lookup the instance_id for record keeping in the records table. | 16:31 |
rjrjr | fixedips = private IPs | 16:32 |
rjrjr | but, for us at EBay, we have a flat network, so fixedips are our public IPs. | 16:32 |
*** shakayumi has joined #openstack-dns | 16:32 | |
rjrjr | we don't use floating IPs. | 16:32 |
ekarlso | don't use neutron ? | 16:33 |
rjrjr | no, we use Neutron. i'll be honest, i don't have all the details. i just know our fixed IPs are publically routable. | 16:34 |
ekarlso | so probably a "provider" network then I guess | 16:35 |
rjrjr | i guess so. | 16:35 |
ekarlso | again then it's a question if you are wanting to implement this for something else then just nova fixed ip's you need to cover both grounds | 16:35 |
rjrjr | sorry, i don't understand this last statement. | 16:37 |
rjrjr | i was going to take this blueprint https://wiki.openstack.org/wiki/Designate/Blueprints/Reverse and finish the work for "... and future Internal IPs." which I'm assuming means fixed IPs. | 16:38 |
ekarlso | it sounds to me you wanted to pull info from nova (though nova) | 16:38 |
ekarlso | through nova. | 16:38 |
rjrjr | i don't need to though. the compute.instance.create.end passed the instance_id, IP address, and hostname (wherever it may be hidden.) | 16:39 |
ekarlso | So, what if the port is something not running in nova ? | 16:39 |
rjrjr | is that possible? i'll be honest, I don't understand all of OpenStack networking yet. | 16:40 |
ekarlso | as in a port residing towards something else like a box full of diff ports that info won't be viable | 16:40 |
ekarlso | because you're tracking 1 vm | 16:40 |
ekarlso | even a VM might have multiple nic's | 16:41 |
ekarlso | or "ports" | 16:41 |
rjrjr | i'm just wanting to handle fixed IPs. those do run in Nova, correct? | 16:41 |
ekarlso | not if it uses neutron underneath :) | 16:42 |
ekarlso | more appropriately it would be best to use neutron since n-net is going to fade away | 16:42 |
rjrjr | the OpenStack fixed IPs concept isn't tied to Nova? | 16:42 |
ekarlso | "fixed" ip's are, but if you are on neutron you're probably using a "provider" network | 16:43 |
*** eankutse has quit IRC | 16:43 | |
rjrjr | we are using Nova for fixed IPs. | 16:43 |
*** eankutse has joined #openstack-dns | 16:43 | |
rjrjr | i'm just trying to solve the fixed IPs problem, similar to the floating IPs problem. | 16:44 |
ekarlso | rjrjr: yes, but even if it seems like fixed ips it might be something diff underneath (nova can use info from neutron)... | 16:44 |
ekarlso | though I don't know you arch so ;p | 16:44 |
rjrjr | does that change the API I'm trying to flesh out though? we have /reverse/floatingips now and I want to finish this work with /reverse/fixedips. | 16:45 |
ekarlso | might not ;P | 16:45 |
rjrjr | i guess i'm wondering if it is required to make a call back to Nova/Neutron/etc. to get more information. or can i rely on the information that comes with the compute.instance.create.end (is this tied to Nova?) message? | 16:47 |
rjrjr | is there any security things I need to consider. someone sending amqp messages that isn't an openstack service? | 16:48 |
ekarlso | good q | 16:48 |
rjrjr | how do i validate the instance_id, IP address, and/or hostname are correct? | 16:49 |
ekarlso | So the way the current floatingip does it is to call neutron using the token from the user towards neutrons either in a predef list or towards the ones in the service catalog | 16:50 |
ekarlso | for this i'm not really sure | 16:50 |
ekarlso | could do the same thing I guess, check towards the nova's if they have a fixed addr that matches the one you have | 16:50 |
rjrjr | so the API has a couple of choices /reverse/fixedips/<instance_id> or /reverse/fixedips/<ip-address> | 16:51 |
ekarlso | So there's two parts | 16:52 |
rjrjr | i suspect i can lookup the instance_id with the IP address or vice versa. | 16:52 |
ekarlso | 1 is the api and verifying that the user is passing a valid thing | 16:52 |
ekarlso | 2 is actually tracking if the resource get's deleted (notifications) | 16:52 |
*** vinod has quit IRC | 16:53 | |
rjrjr | the API should have the ability to add the PTR record and delete the PTR record. | 16:54 |
ekarlso | yeah, but designate won't know if the resource the ptr is for is deleted (hence notifications) | 16:54 |
ekarlso | as we do for FIPs | 16:55 |
rjrjr | ekarlso, i don't understand. we get a compute.instance.create.end in the notification. we add the PTR record. we get a compute.instance.delete.start in the notification. we delete the PTR record. we just need an API for this. | 16:56 |
ekarlso | compute.instance.create.end < so create a PTR that looks like what ? | 16:57 |
rjrjr | I'm thinking rather than PATCH, we are looking at a POST and DELETE maybe for fixed IPs. | 16:58 |
*** vinod has joined #openstack-dns | 16:58 | |
ekarlso | So, notifications should create the PTR or the user via the api ? | 16:58 |
ekarlso | a bit confused | 16:59 |
rjrjr | correct. | 16:59 |
ekarlso | what's the use then for the API if the notifications handle creation / deletion ? | 17:00 |
rjrjr | POST /reverse/fixedips (body contains IP address, hostname, and instance_id. validiation is done with a call to Nova.) DELETE /reverse/fixedips/<instance_id> or /reverse/fixedips/<ip-address> | 17:00 |
rjrjr | because the domains for these IP addresses are shared. | 17:01 |
rjrjr | same as floating IPs. | 17:01 |
ekarlso | yeah, they are "managed" | 17:01 |
ekarlso | but still notifications then don't play a role at this stage as I tried to note earlier | 17:01 |
ekarlso | it would be a API call out to nova or some other random service | 17:01 |
rjrjr | notification has nothing to do with the API, correct. | 17:03 |
ekarlso | notifications in the case for FIPs is just used to keep track of a PTR should be deleted | 17:03 |
ekarlso | nothing more | 17:03 |
rjrjr | was a notification created for FIPs? i didn't come across it while looking at the code. | 17:04 |
ekarlso | we have a handler in the sink I think :p | 17:04 |
rjrjr | hmmm... the only handler i remember see was the default handler to create and remove A records. | 17:05 |
rjrjr | i see what you are referring to. the Neutron handler creates and removes PTR records too. the nova handler only works with A records. that is what I'm trying to fix. :) | 17:07 |
ekarlso | neutron_ptr one | 17:09 |
ekarlso | is the one that handles the PTR part | 17:09 |
*** vinod has quit IRC | 17:09 | |
rjrjr | so, back to the API, how does POST /reverse/fixedips and DELETE /reverse/fixedips/<instance_id> look? i can make calls to Nova API to validate the body of the fixed IPs. | 17:10 |
rjrjr | again, not sure if PATCH makes sense for the fixed IPs API. | 17:10 |
rjrjr | i'll do this. i'll writeup the blueprint and we can discuss tomorrow at our meeting. i put it on the agenda for tomorrow. | 17:11 |
ekarlso | cool :) | 17:12 |
rjrjr | i appreciate your discussing this. it helps me clarify what is needed. | 17:12 |
*** crc32 has joined #openstack-dns | 17:14 | |
*** CaptTofu has quit IRC | 17:28 | |
*** vinod has joined #openstack-dns | 17:29 | |
rjrjr | question, how do i create a new page in the OpenStack wiki? | 17:34 |
rjrjr | i'm signed in, but i don't see any options to create a new page. | 17:34 |
*** vinod has quit IRC | 17:44 | |
*** vinod has joined #openstack-dns | 17:45 | |
*** CaptTofu has joined #openstack-dns | 17:48 | |
*** mwagner_lap has joined #openstack-dns | 17:49 | |
rjrjr | figured it out. | 18:03 |
*** rossk has joined #openstack-dns | 18:10 | |
*** eankutse has quit IRC | 18:21 | |
*** artom has quit IRC | 18:21 | |
*** eankutse has joined #openstack-dns | 18:23 | |
*** cflmarques has quit IRC | 18:34 | |
*** vinod1 has joined #openstack-dns | 19:06 | |
*** sballe has quit IRC | 19:07 | |
*** rossk has quit IRC | 19:08 | |
*** vinod has quit IRC | 19:08 | |
*** rjrjr has quit IRC | 20:01 | |
*** tsimmons has left #openstack-dns | 20:02 | |
*** shakayumi has quit IRC | 20:17 | |
*** shakayumi has joined #openstack-dns | 20:19 | |
richm | in designate, is it correct to say that a "server" is the fqdn of a machine that a dns server is running on? | 20:53 |
*** crc32 has quit IRC | 21:03 | |
*** vinod1 has quit IRC | 21:06 | |
*** crc32 has joined #openstack-dns | 21:11 | |
*** artom has joined #openstack-dns | 21:12 | |
*** rossk has joined #openstack-dns | 21:15 | |
*** artom has quit IRC | 21:16 | |
*** artom has joined #openstack-dns | 21:16 | |
*** vinod has joined #openstack-dns | 21:22 | |
*** crc32 has quit IRC | 21:29 | |
openstackgerrit | Kiall Mac Innes proposed a change to stackforge/designate: Standardize doc requirements https://review.openstack.org/78015 | 21:34 |
*** crc32 has joined #openstack-dns | 21:34 | |
openstackgerrit | Kiall Mac Innes proposed a change to stackforge/python-designateclient: Standardize doc requirements https://review.openstack.org/78018 | 21:35 |
openstackgerrit | Kiall Mac Innes proposed a change to stackforge/python-designateclient: Standardize doc requirements https://review.openstack.org/78018 | 21:36 |
*** rossk has quit IRC | 21:57 | |
*** rossk has joined #openstack-dns | 21:58 | |
ekarlso | yo | 21:58 |
*** vinod has quit IRC | 22:05 | |
*** eankutse has quit IRC | 22:17 | |
*** eankutse has joined #openstack-dns | 22:17 | |
*** jorgem has quit IRC | 22:17 | |
*** jorgem has joined #openstack-dns | 22:20 | |
*** jorgem has quit IRC | 22:32 | |
*** jorgem has joined #openstack-dns | 22:32 | |
*** CaptTofu has quit IRC | 22:45 | |
*** jmcbride has quit IRC | 22:49 | |
openstackgerrit | A change was merged to stackforge/designate: Standardize doc requirements https://review.openstack.org/78015 | 22:52 |
*** jmcbride has joined #openstack-dns | 22:54 | |
openstackgerrit | A change was merged to stackforge/python-designateclient: Standardize doc requirements https://review.openstack.org/78018 | 23:00 |
*** rjrjr has joined #openstack-dns | 23:06 | |
*** jorgem has quit IRC | 23:13 | |
*** shakayumi has quit IRC | 23:14 | |
*** jorgem has joined #openstack-dns | 23:15 | |
*** artom has quit IRC | 23:16 | |
*** jmcbride has quit IRC | 23:24 | |
*** eankutse1 has joined #openstack-dns | 23:28 | |
*** eankutse1 has quit IRC | 23:28 | |
*** eankutse has quit IRC | 23:32 | |
*** mwagner_lap has quit IRC | 23:44 | |
*** jorgem has quit IRC | 23:54 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!