*** CaptTofu has quit IRC | 00:14 | |
*** CaptTofu has joined #openstack-dns | 00:15 | |
*** CaptTofu has quit IRC | 00:20 | |
*** CaptTofu has joined #openstack-dns | 00:21 | |
*** matsuhashi has joined #openstack-dns | 00:28 | |
*** nosnos has joined #openstack-dns | 00:45 | |
*** CaptTofu has quit IRC | 01:10 | |
*** CaptTofu has joined #openstack-dns | 01:10 | |
*** CaptTofu has quit IRC | 01:15 | |
*** zane has quit IRC | 01:28 | |
*** vipul has quit IRC | 02:45 | |
*** vipul has joined #openstack-dns | 02:46 | |
*** CaptTofu has joined #openstack-dns | 03:15 | |
*** zane has joined #openstack-dns | 03:33 | |
*** adrian_otto has joined #openstack-dns | 03:59 | |
*** adrian_otto has quit IRC | 04:01 | |
*** CaptTofu has quit IRC | 04:06 | |
*** CaptTofu has joined #openstack-dns | 04:06 | |
*** zane has quit IRC | 05:24 | |
*** matsuhashi has quit IRC | 06:01 | |
*** nosnos has quit IRC | 06:08 | |
*** krow has joined #openstack-dns | 06:13 | |
*** matsuhashi has joined #openstack-dns | 06:24 | |
*** krow has quit IRC | 06:30 | |
*** krow has joined #openstack-dns | 06:30 | |
*** nosnos has joined #openstack-dns | 06:54 | |
*** tvb has joined #openstack-dns | 07:32 | |
*** tvb has quit IRC | 09:52 | |
*** tvb has joined #openstack-dns | 09:53 | |
*** Kiall has quit IRC | 10:20 | |
*** kiall has joined #openstack-dns | 10:23 | |
*** matsuhashi has quit IRC | 10:28 | |
*** krow has quit IRC | 10:53 | |
*** nosnos has quit IRC | 11:32 | |
*** CaptTofu has quit IRC | 11:33 | |
*** CaptTofu has joined #openstack-dns | 11:34 | |
*** CaptTofu has quit IRC | 12:24 | |
*** CaptTofu has joined #openstack-dns | 12:24 | |
*** eankutse has joined #openstack-dns | 13:16 | |
eankutse | Hello mugsie: | 13:41 |
---|---|---|
eankutse | Server Pools Phase 2: " Zone serial numbers will move to a incrementing integer (from the current date/time stamp format)". | 13:41 |
eankutse | I 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 |
mugsie | eankutse: yes, as when we move to async, it is how we are going to track what change is active | 14:08 |
mugsie | it is much easier to check if thinks are out of sync if it is a incrementing integer | 14:08 |
mugsie | the updated time can be pulled frm the API, but it is a loss on the information presented to people querying the dns server directly | 14:09 |
eankutse | k. THx | 14:11 |
eankutse | On 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 |
mugsie | yeah, pool-manager will totoally replace the agent | 14:15 |
mugsie | for the functionality, I am not sure yet | 14:15 |
mugsie | i need to flesh it out | 14:15 |
eankutse | k. So, pool-manager replaces agent. But what is the pools scheduler? What is the intent for that piece? | 14:16 |
mugsie | when a domain is created, it will decide what server pool to assign the domain to | 14:17 |
kiall | eankutse: 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 to | 14:18 |
kiall | (Heya!) | 14:18 |
* kiall might get back to code next week. He hopes. | 14:18 | |
kiall | DevOps ain't as fun ;) | 14:19 |
eankutse | Kiall: you are a scarce resource :-) | 14:19 |
kiall | Hah... Doing some major changes to our deployment, all hands kinda thing ;) | 14:20 |
eankutse | k :-) | 14:21 |
eankutse | Regarding asyc-backends... | 14:21 |
eankutse | when 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 |
mugsie | eankutse: they wont call a decidcated endpoint to get the status, the just run GET against the zone / record | 14:23 |
kiall | Yea - 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 though | 14:23 |
mugsie | and it will have a status of PENDING / ACTIVE | 14:23 |
kiall | mugsie: don't tell me you've forgot that conversaion? | 14:24 |
kiall | conversation* | 14:24 |
mugsie | yeah, but I havent planned for it yet | 14:24 |
mugsie | I think it needs more thought before putting it forward | 14:24 |
mugsie | more important to get pools / async in | 14:24 |
kiall | Ah - That's what I thought | 14:24 |
*** zane has joined #openstack-dns | 14:25 | |
eankutse | Good to know that's in the pipeline. One step at a time :-) | 14:26 |
kiall | Ok.. Need some lunch. Going to go find something.. back in a few | 14:27 |
eankutse | Enjoy 0-) | 14:27 |
eankutse | :) | 14:27 |
*** CaptTofu has quit IRC | 14:32 | |
*** CaptTofu has joined #openstack-dns | 14:33 | |
*** blinky_ghost has joined #openstack-dns | 14:33 | |
blinky_ghost | Hi 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? Thanks | 14:46 |
*** CaptTofu has quit IRC | 14:48 | |
*** CaptTofu has joined #openstack-dns | 14:49 | |
*** jmcbride has joined #openstack-dns | 14:50 | |
*** tvb has quit IRC | 14:55 | |
mugsie | blinky_ghost: what sort of DNS are you looking to deploy? | 15:14 |
blinky_ghost | mugsie: I want to deploy DNS to my instances, to private network | 15:15 |
mugsie | so when they boot they get a dns entry? | 15:16 |
mugsie | or as a recursive DNS server for the instances to use? | 15:17 |
blinky_ghost | mugsie: get a dns entry | 15:18 |
*** adrian_otto has joined #openstack-dns | 15:19 | |
mugsie | i *think* there currently is a way using the sink plugin - kiall any ideas? | 15:20 |
kiall | yea, 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_ghost | Well i can create my own powerdns/bind server and allow dynamic updates, but just wanted to know if openstack supported it as a service | 15:26 |
artom | To 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 |
artom | The scheduler, for example? | 15:42 |
artom | Though that will be preceded by a lengthy conversation to establish a common vision. | 15:43 |
mugsie | artom: i think we need to wait until async lands before the schedualer | 15:51 |
mugsie | but.. | 15:51 |
mugsie | https://wiki.openstack.org/wiki/Designate/Server_Pools#Phase_Three | 15:53 |
mugsie | any ideas, stick them in there | 15:53 |
artom | Actually, here's something I don't understand. | 16:13 |
artom | Pools are exposed in the API. | 16:13 |
artom | So why the scheduler? | 16:14 |
artom | If the pool ID is given in the request, doesn't the eliminate scheduler's reason to exist? | 16:14 |
mugsie | so when someone posts to /domains/ it needs to be assigned to a pool | 16:16 |
mugsie | sorry, /zones/ | 16:16 |
mugsie | (pools are not exposed within the /zones/endpoint | 16:21 |
artom | So pools are exposed for GET /servers and... anything else? | 16:27 |
mugsie | nope | 16:30 |
mugsie | (they are embeded within the zone data) - aka in a GET /zones/id there will be pool_id:<blah> | 16:31 |
artom | Ok, so just to make sure, the client only needs to care about pools when GETing /servers? | 16:32 |
*** tvb has joined #openstack-dns | 16:35 | |
mugsie | yeap (for the time being, people might want that changed in the future) | 16:35 |
artom | Is 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 |
artom | Servers have GUUIDs anyways... | 16:37 |
*** jmcbride has quit IRC | 16:40 | |
mugsie | it is too allow people to have public / private pools | 16:56 |
mugsie | so you can decide whare the domain is served from them | 16:57 |
artom | But then you post a domain and the scheduler decides what pool it goes into... | 17:03 |
mugsie | thats why it needs to be worked out ;) - we do need a way of forcing a domain on to a patricualar pool | 17:05 |
artom | Per-tenant maybe? | 17:06 |
mugsie | also, 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 up | 17:06 |
artom | People could create a public and private tenant... | 17:06 |
mugsie | yeah, that could be one solution.. we do need to fully map out the interctions | 17:07 |
artom | But then if a single tenant wants multiple pools for whatever reasons... | 17:07 |
mugsie | nothign is set in stone for this curently | 17:08 |
mugsie | so, add notes to that page, so when we start to look at it, we know the issues | 17:08 |
artom | Yeah, I can see there's a lot of stuff to figure out before coding can commence... | 17:09 |
*** eankutse has quit IRC | 17:32 | |
*** krow has joined #openstack-dns | 17:47 | |
*** zane has quit IRC | 17:55 | |
*** blinky_ghost has quit IRC | 17:56 | |
*** eankutse has joined #openstack-dns | 18:04 | |
*** zane has joined #openstack-dns | 18:07 | |
*** CaptTofu has quit IRC | 18:26 | |
*** CaptTofu has joined #openstack-dns | 18:26 | |
*** krow has quit IRC | 18:27 | |
*** eankutse has quit IRC | 18:35 | |
*** krow has joined #openstack-dns | 18:37 | |
*** tsimmons has joined #openstack-dns | 18:45 | |
*** krow has quit IRC | 18:45 | |
*** CaptTofu has quit IRC | 18:45 | |
*** CaptTofu has joined #openstack-dns | 18:46 | |
*** eankutse has joined #openstack-dns | 18:50 | |
*** eankutse has quit IRC | 19:06 | |
*** ctracey is now known as ctracey|away | 19:20 | |
*** tsimmons has quit IRC | 19:20 | |
*** tsimmons has joined #openstack-dns | 19:29 | |
*** eankutse has joined #openstack-dns | 19:36 | |
*** CaptTofu has quit IRC | 19:36 | |
*** CaptTofu has joined #openstack-dns | 19:37 | |
*** zane has quit IRC | 20:06 | |
*** tvb has quit IRC | 20:29 | |
*** zane has joined #openstack-dns | 20:41 | |
*** vipul is now known as vipul-away | 20:51 | |
*** vipul-away is now known as vipul | 20:52 | |
*** tvb has joined #openstack-dns | 21:01 | |
*** krow has joined #openstack-dns | 21:06 | |
*** krow has quit IRC | 21:11 | |
*** krow has joined #openstack-dns | 21:41 | |
*** tsimmons has left #openstack-dns | 21:42 | |
*** eankutse has quit IRC | 21:50 | |
*** krow has quit IRC | 21:54 | |
*** krow has joined #openstack-dns | 22:25 | |
*** krow has quit IRC | 22:34 | |
*** krow has joined #openstack-dns | 23:12 | |
*** zane has quit IRC | 23:31 | |
*** krow has quit IRC | 23:32 | |
*** krow has joined #openstack-dns | 23:43 | |
*** adrian_otto has quit IRC | 23:47 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!