Tuesday, 2014-03-04

rjrjrwhen are mugsie and kiall usually on?00:12
*** artom has quit IRC00:18
*** openstackgerrit has quit IRC00:44
*** openstackgerrit has joined #openstack-dns00:44
*** ChanServ sets mode: +v openstackgerrit00:44
*** eankutse1 has joined #openstack-dns00:49
*** jorgem has quit IRC00:52
*** richm has quit IRC00:52
*** eankutse has quit IRC00:52
*** eankutse1 has quit IRC00:53
*** rossk has quit IRC01:08
*** CaptTofu has quit IRC01:12
*** nosnos has joined #openstack-dns01:29
*** CaptTofu has joined #openstack-dns01:34
*** jmcbride has joined #openstack-dns01:41
*** jmcbride has quit IRC01:43
*** jmcbride has joined #openstack-dns01:45
*** jmcbride1 has joined #openstack-dns01:46
*** jmcbride has quit IRC01:50
*** jmcbride1 has quit IRC01:51
*** vinod has joined #openstack-dns02:03
*** jmcbride has joined #openstack-dns03:10
*** vinod has quit IRC03:23
*** jmcbride has quit IRC03:26
*** jmcbride has joined #openstack-dns03:31
*** CaptTofu has quit IRC03:32
*** jmcbride has quit IRC03:34
*** jmcbride has joined #openstack-dns03:36
*** jmcbride has quit IRC04:19
*** crc32 has quit IRC05:19
*** shakayumi has joined #openstack-dns05:30
*** CaptTofu has joined #openstack-dns05:33
*** CaptTofu has quit IRC05:38
*** baribalbear has joined #openstack-dns06:59
*** CaptTofu has joined #openstack-dns07:00
*** CaptTofu has quit IRC07:06
*** nosnos has quit IRC07:31
*** nosnos_ has joined #openstack-dns07:31
*** nosnos_ has quit IRC08:04
*** nosnos has joined #openstack-dns08:04
*** baribalbear has quit IRC08:45
*** CaptTofu has joined #openstack-dns09:03
*** CaptTofu has quit IRC09:07
*** sballe has quit IRC09:08
*** sballe has joined #openstack-dns09:08
*** sballe has quit IRC09:17
*** shakayumi has quit IRC10:07
*** CaptTofu has joined #openstack-dns11:03
*** CaptTofu has quit IRC11:08
*** CaptTofu has joined #openstack-dns11:22
openstackgerritA change was merged to stackforge/designate: UUID changes to api / utils  https://review.openstack.org/7563411:37
openstackgerritA change was merged to stackforge/designate: Fill in missing Records tests for V2 api  https://review.openstack.org/7565411:39
openstackgerritKiall Mac Innes proposed a change to stackforge/designate: Ensure Storage Implementions match the Interface  https://review.openstack.org/7563311:45
*** baribalbear has joined #openstack-dns11:48
ekarlsobaribalbear: hi11:54
ekarlsoi tested the neutron floatibngip handler using devstack yesterday and it worked11:54
openstackgerritA change was merged to stackforge/designate: Ensure that wanted API calls returns exceptions  https://review.openstack.org/7659912:05
*** ekarlso has quit IRC12:09
*** vinod1 has joined #openstack-dns12:10
*** cflmarques has joined #openstack-dns12:11
*** vinod1 has quit IRC12:30
*** vinod1 has joined #openstack-dns12:31
*** vinod1 has quit IRC12:32
*** mwagner_lap has quit IRC12:40
*** ekarlso has joined #openstack-dns13:23
*** sballe has joined #openstack-dns13:33
*** artom has joined #openstack-dns13:40
*** artom has quit IRC13:44
*** nosnos has quit IRC13:56
*** eankutse has joined #openstack-dns13:57
*** CaptTofu has quit IRC14:01
*** CaptTofu has joined #openstack-dns14:09
*** jmcbride has joined #openstack-dns14:22
*** richm has joined #openstack-dns14:32
*** nkinder has quit IRC14:45
*** msisk has joined #openstack-dns15:03
*** msisk has quit IRC15:04
*** msisk has joined #openstack-dns15:04
*** mnaser has quit IRC15:08
*** mnaser has joined #openstack-dns15:08
*** eankutse has quit IRC15:10
*** eankutse has joined #openstack-dns15:10
*** eankutse has quit IRC15:11
*** artom has joined #openstack-dns15:12
*** vinod has joined #openstack-dns15:29
*** nkinder has joined #openstack-dns15:32
artomekarlso, PTR support is currently implemented only for floating IPs, yes?15:59
ekarlsoartom: indeed16:02
ekarlsoartom: what would you like it for ?16:02
artomThe other stuff.16:02
ekarlsoprivate networks ?16:02
artomOr even fixed on public networks.16:03
*** tsimmons has joined #openstack-dns16:03
ekarlsoartom: or, really there's nothing keeping you from creating PTR records for those16:03
ekarlsoit just won't be "automagic"16:03
ekarlsoas in all the zone creation etc is managed16:03
rjrjrthe networks are share among tenants.16:10
kiallartom: the issue with doing PTR's for private networks is the networks can overlap16:10
kiall2 tenants can both have 10.0.0.0/8 ... so who gets's the 10.in-addr.arpa zone?16:10
rjrjri'm looking at taking this https://wiki.openstack.org/wiki/Designate/Blueprints/Reverse and adding the fixed IP support.16:11
artomkiall, yeah, I think client only wants PTR for public-facing stuff.16:11
artomBut that can include fixed IPs...16:11
kiallRight, so if those are auto allocated public IPs, they are technically also floating IPs16:11
artomHrmm, 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
rjrjrartom, we have a flat network at E-Bay, so our fixed IPs are our public IPs.16:12
*** eankutse has joined #openstack-dns16:12
*** eankutse has quit IRC16:12
*** eankutse has joined #openstack-dns16:13
artomrjrjr, yeah, it might be something similar at Cloudwatt.16:13
artomStill in the exploratory phase here :P16:13
*** ytwu1 has joined #openstack-dns16:14
rjrjrkiall, 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
kiallrjrjr: I assume there's no overlapping IPs then?16:14
rjrjrno, we also share the network(s).16:14
kiallIf that's the case, then we can probably do something very similar to FloatingIPs16:14
kialljust with an on/off flag that defaults to off16:15
*** baribalbear has quit IRC16:15
rjrjri 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 IRC16:16
kiallIt 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 records16:17
ekarlsoartom: if it's neutron then it's not fixed ip's no ?16:18
ekarlsothought that was a nova thing16:18
kiallFor 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 key16:18
rjrjri was thinking about the /reverse/fixedip API.16:18
kiallAh, so.. FixedIPs don't actually get an ID.. Right16:18
rjrjrcorrect.16:19
kiallI wonder if port_id or something is suitable?16:19
rjrjrin a VM creation, we get instance_id, IP address, and hostname.16:19
ekarlsokiall: port_id get's re-created I think on each new port...16:19
ekarlsolike each new service that has a port, vm or whatever16:19
*** ytwu has joined #openstack-dns16:19
kiallrjrjr: Well, I believe we get those same details for auto-created ports16:20
kialland manually created ports can have the name assigned to them16:20
rjrjrsorry, not familiar with ports.16:20
kiallThere is a neutron bug around DNS naming in dnsmasq being tied to ports rather than instances16:20
kiallA port is basically just a NIC on your VM16:21
*** ytwu1 has quit IRC16:21
rjrjrokay.16:21
kiallwhen you boot an instance with nova (and your using neutron), it will auto create a port unless you say "use port 12345"16:21
kiallso the network.port.create event should (maybe?) have the right info.16:21
kiallI've not looked recently though16:21
rjrjrwhat is the right info we are looking for?  are you saying the hostname is wrong in a instance.create.end?16:24
rjrjrit looks right to me.16:24
kiallIt's that Nova asks for an "Instance Name" which you *could* fill in something that looks like a valid hostname16:25
kiallBut - You don't have to16:25
kiallI'm pretty sure !"£$%%^^&**(( is a valid "Instance Name"16:25
rjrjrjoy!16:25
artomWell with Unicode domain names that's now possible ;)16:25
kiallartom: lol..16:26
rjrjrso, you are saying the port event would have a valid hostname?16:26
kiallEven so, I personally call my instances blabla01.domain.com etc16:26
kiallwhile at HP, we tend to use dns-region-role0001 etc16:26
kiall(i.e. FQDN vs Short name)16:26
rjrjrhence the notification handlers are customizable.16:27
rjrjrat E-Bay, we are using the metadata to pass the hostname.16:28
rjrjr(short)16:28
kiallThere's another option :)16:28
rjrjrback to the /reverse/fixedips API. :)16:28
*** jorgem has joined #openstack-dns16:29
rjrjron compute.instance.create.end we get the IP address and the hostname (in metadata, as valid hostname, etc.)16:29
rjrjrshould the API be /reverse/fixedips/<ip-address> and the body contain the hostname to create the PTR record?16:30
ekarlsorjrjr: when you mean fixedip's what you mean then ?16:31
rjrjrwe 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
rjrjrfixedips = private IPs16:32
rjrjrbut, for us at EBay, we have a flat network, so fixedips are our public IPs.16:32
*** shakayumi has joined #openstack-dns16:32
rjrjrwe don't use floating IPs.16:32
ekarlsodon't use neutron ?16:33
rjrjrno, 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
ekarlsoso probably a "provider" network then I guess16:35
rjrjri guess so.16:35
ekarlsoagain 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 grounds16:35
rjrjrsorry, i don't understand this last statement.16:37
rjrjri 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
ekarlsoit sounds to me you wanted to pull info from nova (though nova)16:38
ekarlsothrough nova.16:38
rjrjri 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
ekarlsoSo, what if the port is something not running in nova ?16:39
rjrjris that possible?  i'll be honest, I don't understand all of OpenStack networking yet.16:40
ekarlsoas in a port residing towards something else like a box full of diff ports that info won't be viable16:40
ekarlsobecause you're tracking 1 vm16:40
ekarlsoeven a VM might have multiple nic's16:41
ekarlsoor "ports"16:41
rjrjri'm just wanting to handle fixed IPs.  those do run in Nova, correct?16:41
ekarlsonot if it uses neutron underneath :)16:42
ekarlsomore appropriately it would be best to use neutron since n-net is going to fade away16:42
rjrjrthe 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" network16:43
*** eankutse has quit IRC16:43
rjrjrwe are using Nova for fixed IPs.16:43
*** eankutse has joined #openstack-dns16:43
rjrjri'm just trying to solve the fixed IPs problem, similar to the floating IPs problem.16:44
ekarlsorjrjr: yes, but even if it seems like fixed ips it might be something diff underneath (nova can use info from neutron)...16:44
ekarlsothough I don't know you arch so ;p16:44
rjrjrdoes 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
ekarlsomight not ;P16:45
rjrjri 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
rjrjris there any security things I need to consider.  someone sending amqp messages that isn't an openstack service?16:48
ekarlsogood q16:48
rjrjrhow do i validate the instance_id, IP address, and/or hostname are correct?16:49
ekarlsoSo 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 catalog16:50
ekarlsofor this i'm not really sure16:50
ekarlsocould do the same thing I guess, check towards the nova's if they have a fixed addr that matches the one you have16:50
rjrjrso the API has a couple of choices /reverse/fixedips/<instance_id> or /reverse/fixedips/<ip-address>16:51
ekarlsoSo there's two parts16:52
rjrjri suspect i can lookup the instance_id with the IP address or vice versa.16:52
ekarlso1 is the api and verifying that the user is passing a valid thing16:52
ekarlso2 is actually tracking if the resource get's deleted (notifications)16:52
*** vinod has quit IRC16:53
rjrjrthe API should have the ability to add the PTR record and delete the PTR record.16:54
ekarlsoyeah, but designate won't know if the resource the ptr is for is deleted (hence notifications)16:54
ekarlsoas we do for FIPs16:55
rjrjrekarlso, 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
ekarlsocompute.instance.create.end < so create a PTR that looks like what ?16:57
rjrjrI'm thinking rather than PATCH, we are looking at a POST and DELETE maybe for fixed IPs.16:58
*** vinod has joined #openstack-dns16:58
ekarlsoSo, notifications should create the PTR or the user via the api ?16:58
ekarlsoa bit confused16:59
rjrjrcorrect.16:59
ekarlsowhat's the use then for the API if the notifications handle creation / deletion ?17:00
rjrjrPOST /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
rjrjrbecause the domains for these IP addresses are shared.17:01
rjrjrsame as floating IPs.17:01
ekarlsoyeah, they are "managed"17:01
ekarlsobut still notifications then don't play a role at this stage as I tried to note earlier17:01
ekarlsoit would be a API call out to nova or some other random service17:01
rjrjrnotification has nothing to do with the API, correct.17:03
ekarlsonotifications in the case for FIPs is just used to keep track of a PTR should be deleted17:03
ekarlsonothing more17:03
rjrjrwas a notification created for FIPs?  i didn't come across it while looking at the code.17:04
ekarlsowe have a handler in the sink I think :p17:04
rjrjrhmmm... the only handler i remember see was the default handler to create and remove A records.17:05
rjrjri 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
ekarlsoneutron_ptr one17:09
ekarlsois the one that handles the PTR part17:09
*** vinod has quit IRC17:09
rjrjrso, 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
rjrjragain, not sure if PATCH makes sense for the fixed IPs API.17:10
rjrjri'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
ekarlsocool :)17:12
rjrjri appreciate your discussing this.  it helps me clarify what is needed.17:12
*** crc32 has joined #openstack-dns17:14
*** CaptTofu has quit IRC17:28
*** vinod has joined #openstack-dns17:29
rjrjrquestion, how do i create a new page in the OpenStack wiki?17:34
rjrjri'm signed in, but i don't see any options to create a new page.17:34
*** vinod has quit IRC17:44
*** vinod has joined #openstack-dns17:45
*** CaptTofu has joined #openstack-dns17:48
*** mwagner_lap has joined #openstack-dns17:49
rjrjrfigured it out.18:03
*** rossk has joined #openstack-dns18:10
*** eankutse has quit IRC18:21
*** artom has quit IRC18:21
*** eankutse has joined #openstack-dns18:23
*** cflmarques has quit IRC18:34
*** vinod1 has joined #openstack-dns19:06
*** sballe has quit IRC19:07
*** rossk has quit IRC19:08
*** vinod has quit IRC19:08
*** rjrjr has quit IRC20:01
*** tsimmons has left #openstack-dns20:02
*** shakayumi has quit IRC20:17
*** shakayumi has joined #openstack-dns20:19
richmin 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 IRC21:03
*** vinod1 has quit IRC21:06
*** crc32 has joined #openstack-dns21:11
*** artom has joined #openstack-dns21:12
*** rossk has joined #openstack-dns21:15
*** artom has quit IRC21:16
*** artom has joined #openstack-dns21:16
*** vinod has joined #openstack-dns21:22
*** crc32 has quit IRC21:29
openstackgerritKiall Mac Innes proposed a change to stackforge/designate: Standardize doc requirements  https://review.openstack.org/7801521:34
*** crc32 has joined #openstack-dns21:34
openstackgerritKiall Mac Innes proposed a change to stackforge/python-designateclient: Standardize doc requirements  https://review.openstack.org/7801821:35
openstackgerritKiall Mac Innes proposed a change to stackforge/python-designateclient: Standardize doc requirements  https://review.openstack.org/7801821:36
*** rossk has quit IRC21:57
*** rossk has joined #openstack-dns21:58
ekarlsoyo21:58
*** vinod has quit IRC22:05
*** eankutse has quit IRC22:17
*** eankutse has joined #openstack-dns22:17
*** jorgem has quit IRC22:17
*** jorgem has joined #openstack-dns22:20
*** jorgem has quit IRC22:32
*** jorgem has joined #openstack-dns22:32
*** CaptTofu has quit IRC22:45
*** jmcbride has quit IRC22:49
openstackgerritA change was merged to stackforge/designate: Standardize doc requirements  https://review.openstack.org/7801522:52
*** jmcbride has joined #openstack-dns22:54
openstackgerritA change was merged to stackforge/python-designateclient: Standardize doc requirements  https://review.openstack.org/7801823:00
*** rjrjr has joined #openstack-dns23:06
*** jorgem has quit IRC23:13
*** shakayumi has quit IRC23:14
*** jorgem has joined #openstack-dns23:15
*** artom has quit IRC23:16
*** jmcbride has quit IRC23:24
*** eankutse1 has joined #openstack-dns23:28
*** eankutse1 has quit IRC23:28
*** eankutse has quit IRC23:32
*** mwagner_lap has quit IRC23:44
*** jorgem has quit IRC23:54

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