Friday, 2013-10-04

*** CaptTofu has quit IRC00:14
*** CaptTofu has joined #openstack-dns00:15
*** CaptTofu has quit IRC00:20
*** CaptTofu has joined #openstack-dns00:21
*** matsuhashi has joined #openstack-dns00:28
*** nosnos has joined #openstack-dns00:45
*** CaptTofu has quit IRC01:10
*** CaptTofu has joined #openstack-dns01:10
*** CaptTofu has quit IRC01:15
*** zane has quit IRC01:28
*** vipul has quit IRC02:45
*** vipul has joined #openstack-dns02:46
*** CaptTofu has joined #openstack-dns03:15
*** zane has joined #openstack-dns03:33
*** adrian_otto has joined #openstack-dns03:59
*** adrian_otto has quit IRC04:01
*** CaptTofu has quit IRC04:06
*** CaptTofu has joined #openstack-dns04:06
*** zane has quit IRC05:24
*** matsuhashi has quit IRC06:01
*** nosnos has quit IRC06:08
*** krow has joined #openstack-dns06:13
*** matsuhashi has joined #openstack-dns06:24
*** krow has quit IRC06:30
*** krow has joined #openstack-dns06:30
*** nosnos has joined #openstack-dns06:54
*** tvb has joined #openstack-dns07:32
*** tvb has quit IRC09:52
*** tvb has joined #openstack-dns09:53
*** Kiall has quit IRC10:20
*** kiall has joined #openstack-dns10:23
*** matsuhashi has quit IRC10:28
*** krow has quit IRC10:53
*** nosnos has quit IRC11:32
*** CaptTofu has quit IRC11:33
*** CaptTofu has joined #openstack-dns11:34
*** CaptTofu has quit IRC12:24
*** CaptTofu has joined #openstack-dns12:24
*** eankutse has joined #openstack-dns13:16
eankutseHello mugsie:13:41
eankutseServer Pools Phase 2: " Zone serial numbers will move to a incrementing integer (from the current date/time stamp format)".13:41
eankutseI think the current date/time stamp format has an added value of indicating when zone was last updated which an incrementing integer does not. Does keeping the date/timestamp make for a more difficult design/implementation of server pools?13:41
mugsieeankutse: yes, as when we move to async, it is how we are going to track what change is active14:08
mugsieit is much easier to check if thinks are out of sync if it is a incrementing integer14:08
mugsiethe updated time can be pulled frm the API, but it is a loss on the information presented to people querying the dns server directly14:09
eankutsek. THx14:11
eankutseOn server pools scheduler - "allow for multiple pools, and per tenant pools". What is the current initial thoughts on the functionality of this component ? Is this the replacement for v1 Bind9 Agent concept?14:11
mugsieyeah, pool-manager will totoally replace the agent14:15
mugsiefor the functionality, I am not sure yet14:15
mugsiei need to flesh it out14:15
eankutsek. So, pool-manager replaces agent.  But what is the pools scheduler? What is the intent for that piece?14:16
mugsiewhen a domain is created, it will decide what server pool to assign the domain to14:17
kialleankutse: You'll be able to have multiple pools, and the scheduler (like nova-scheduler) will decide which pool (like nova-compute node) the zone will be allocated to14:18
kiall(Heya!)14:18
* kiall might get back to code next week. He hopes.14:18
kiallDevOps ain't as fun ;)14:19
eankutseKiall: you are a scarce resource :-)14:19
kiallHah... Doing some major changes to our deployment, all hands kinda thing ;)14:20
eankutsek :-)14:21
eankutseRegarding asyc-backends...14:21
eankutsewhen that is implemented and the user can call to get the status of the operation. It would be nice to  provide optional context for the pending request when a user calls for the status - context such as the original request with the details of the url and body.14:22
mugsieeankutse: they wont call a decidcated endpoint to get the status, the just run GET against the zone / record14:23
kiallYea - mugsie convinced me that was good idea a few days ago.. I'm not sure if he's had any ideas around how it might work though14:23
mugsieand it will have a status of PENDING / ACTIVE14:23
kiallmugsie: don't tell me you've forgot that conversaion?14:24
kiallconversation*14:24
mugsieyeah, but I havent planned for it yet14:24
mugsieI think it needs more thought before putting it forward14:24
mugsiemore important to get pools / async in14:24
kiallAh - That's what I thought14:24
*** zane has joined #openstack-dns14:25
eankutseGood to know that's in the pipeline. One step at a time :-)14:26
kiallOk.. Need some lunch. Going to go find something.. back in a few14:27
eankutseEnjoy 0-)14:27
eankutse:)14:27
*** CaptTofu has quit IRC14:32
*** CaptTofu has joined #openstack-dns14:33
*** blinky_ghost has joined #openstack-dns14:33
blinky_ghostHi guys, I'm looking for solutions to implement DNS on my openstack cloud. My questions  are if Designate is ready for production and where can I start to deploy it? Thanks14:46
*** CaptTofu has quit IRC14:48
*** CaptTofu has joined #openstack-dns14:49
*** jmcbride has joined #openstack-dns14:50
*** tvb has quit IRC14:55
mugsieblinky_ghost: what sort of DNS are you looking to deploy?15:14
blinky_ghostmugsie: I want to deploy DNS to my instances, to private network15:15
mugsieso when they boot they get a dns entry?15:16
mugsieor as a recursive DNS server for the instances to use?15:17
blinky_ghostmugsie: get a dns entry15:18
*** adrian_otto has joined #openstack-dns15:19
mugsiei *think* there currently is a way using the sink plugin - kiall any ideas?15:20
kiallyea, that's one of the things the sink service is intended for.. But it pretty basic, and is intended for rolling your own rather than an out of the box solution.15:21
kiall(everyone has a different idea about what the DNS name for an instance should be...)15:22
blinky_ghostWell i can create  my own powerdns/bind server and allow dynamic updates, but just wanted to know if openstack supported it as a service15:26
artomTo start another conversation in parallel, since domain-import-export is waiting for review, are there other blueprints I can start on (without stepping on other people's toes)?15:42
artomThe scheduler, for example?15:42
artomThough that will be preceded by a lengthy conversation to establish a common vision.15:43
mugsieartom: i think we need to wait until async lands before the schedualer15:51
mugsiebut..15:51
mugsiehttps://wiki.openstack.org/wiki/Designate/Server_Pools#Phase_Three15:53
mugsieany ideas, stick them in there15:53
artomActually, here's something I don't understand.16:13
artomPools are exposed in the API.16:13
artomSo why the scheduler?16:14
artomIf the pool ID is given in the request, doesn't the eliminate scheduler's reason to exist?16:14
mugsieso when someone posts to /domains/ it needs to be assigned to a pool16:16
mugsiesorry, /zones/16:16
mugsie(pools are not exposed within the /zones/endpoint16:21
artomSo pools are exposed for GET /servers and... anything else?16:27
mugsienope16:30
mugsie(they are embeded within the zone data) - aka in a GET /zones/id there will be pool_id:<blah>16:31
artomOk, so just to make sure, the client only needs to care about pools when GETing /servers?16:32
*** tvb has joined #openstack-dns16:35
mugsieyeap (for the time being, people might want that changed in the future)16:35
artomIs there a technical reason for that? If you can post a server and have the pool decided by the scheduler, isn't that possible with GET as well?16:37
artomServers have GUUIDs anyways...16:37
*** jmcbride has quit IRC16:40
mugsieit is too allow people to have public / private pools16:56
mugsieso you can decide whare the domain is served from them16:57
artomBut then you post a domain and the scheduler decides what pool it goes into...17:03
mugsiethats why it needs to be worked out ;) - we do need a way of forcing a domain on to a patricualar pool17:05
artomPer-tenant maybe?17:06
mugsiealso, if there is per teneant pools, and they choose to have it as a "private" pool, it would be the schedualars job to look it up17:06
artomPeople could create a public and private tenant...17:06
mugsieyeah, that could be one solution.. we do need to fully map out the interctions17:07
artomBut then if a single tenant wants multiple pools for whatever reasons...17:07
mugsienothign is set in stone for this curently17:08
mugsieso, add notes to that page, so when we start to look at it, we know the issues17:08
artomYeah, I can see there's a lot of stuff to figure out before coding can commence...17:09
*** eankutse has quit IRC17:32
*** krow has joined #openstack-dns17:47
*** zane has quit IRC17:55
*** blinky_ghost has quit IRC17:56
*** eankutse has joined #openstack-dns18:04
*** zane has joined #openstack-dns18:07
*** CaptTofu has quit IRC18:26
*** CaptTofu has joined #openstack-dns18:26
*** krow has quit IRC18:27
*** eankutse has quit IRC18:35
*** krow has joined #openstack-dns18:37
*** tsimmons has joined #openstack-dns18:45
*** krow has quit IRC18:45
*** CaptTofu has quit IRC18:45
*** CaptTofu has joined #openstack-dns18:46
*** eankutse has joined #openstack-dns18:50
*** eankutse has quit IRC19:06
*** ctracey is now known as ctracey|away19:20
*** tsimmons has quit IRC19:20
*** tsimmons has joined #openstack-dns19:29
*** eankutse has joined #openstack-dns19:36
*** CaptTofu has quit IRC19:36
*** CaptTofu has joined #openstack-dns19:37
*** zane has quit IRC20:06
*** tvb has quit IRC20:29
*** zane has joined #openstack-dns20:41
*** vipul is now known as vipul-away20:51
*** vipul-away is now known as vipul20:52
*** tvb has joined #openstack-dns21:01
*** krow has joined #openstack-dns21:06
*** krow has quit IRC21:11
*** krow has joined #openstack-dns21:41
*** tsimmons has left #openstack-dns21:42
*** eankutse has quit IRC21:50
*** krow has quit IRC21:54
*** krow has joined #openstack-dns22:25
*** krow has quit IRC22:34
*** krow has joined #openstack-dns23:12
*** zane has quit IRC23:31
*** krow has quit IRC23:32
*** krow has joined #openstack-dns23:43
*** adrian_otto has quit IRC23:47

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