| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-10 | |||
| 20:18:13 | mriedem | but ok | |
| 20:18:20 | bauzas | call me dumb, but I can't find where in the RT code instance.claim() is defined as a contextmanager?! The Claim object itself is not having __enter__ and __exit__ | |
| 20:18:31 | mriedem | we could expand list_cells to show hosts in a given cell | |
| 20:18:34 | dansmith | kfox1111: you can only have one cell with hosts right now, so .. either they're mapped there or they're not | |
| 20:18:45 | mriedem | bauzas: the parent noopclaim class | |
| 20:18:52 | bauzas | oh shit, nvm | |
| 20:18:59 | bauzas | mriedem: yup, just missed that | |
| 20:19:04 | kfox1111 | dansmith: yeah. but I'm just trying to overify if thats the case or not. | |
| 20:19:15 | kfox1111 | there are two states there. :) | |
| 20:19:20 | dansmith | kfox1111: have you created other cell databases? | |
| 20:19:20 | bauzas | grmblbl, it's late | |
| 20:19:36 | dansmith | kfox1111: if so, then you messed up anyway and if not, then no hosts are registered in a nonexistent database | |
| 20:19:47 | kfox1111 | dansmith: yeah. I have all the code for creation in. it works most of the time. but if a race condition happans and the cell is created before the compute, | |
| 20:19:47 | mriedem | kfox1111: dansmith: to be clear, we can expand list_cells for more info, we talked about that in ocata i think, i think it'd be useful | |
| 20:19:57 | kfox1111 | I wana ensure that all the nodes madie it into the cell. | |
| 20:20:08 | kfox1111 | just running discover_hosts again should fix it. | |
| 20:20:19 | kfox1111 | but was looking for more info to look for the condition. | |
| 20:20:25 | mriedem | reporting clis will be nice for people rolling into this that are new to it | |
| 20:20:25 | kfox1111 | but that doesn't seem like its there yet. thats fine. | |
| 20:20:38 | mriedem | "it" == cells v2 | |
| 20:20:46 | kfox1111 | just rerunning discover_hosts will be an ok workournd for now. | |
| 20:21:10 | kfox1111 | yeah. I'm comming from many years of nova deployments. the cell v2 stuff is all very new to me. | |
| 20:21:21 | dansmith | discovering and listing hosts per cell is nearly the same operation | |
| 20:21:34 | dansmith | there's not much point in listing alone | |
| 20:21:37 | kfox1111 | yeah. but one makes changes, the other does not. | |
| 20:21:45 | kfox1111 | yes, there is. | |
| 20:21:59 | mriedem | the point is i'm afraid of unexpected changes | |
| 20:22:01 | kfox1111 | one tells you why something migh have failed in the past. | |
| 20:22:06 | mriedem | so just read-only type commands i'm happy with | |
| 20:22:07 | kfox1111 | the other fixes an issue. | |
| 20:22:33 | dansmith | kfox1111: discover_hosts differentiates between hosts that are existing and added, | |
| 20:22:34 | dansmith | but that's fine | |
| 20:22:38 | kfox1111 | those are potentially different operations to an operator trying to understand and fix their system. | |
| 20:22:49 | dansmith | for people with thousands of hosts, the list is not super pointful, IMHO | |
| 20:23:05 | kfox1111 | I'm only in the hundereds. | |
| 20:23:07 | kfox1111 | ;) | |
| 20:25:47 | kfox1111 | anyway. as an op, its not very intuitive to go looking for "how do I find out what hosts are bound to what cell" and expect "bind hosts to cell" to be the right answer. just fyi. might be a good faq item at least. | |
| 20:26:51 | dansmith | if you want to list hosts in a cell, | |
| 20:27:01 | dansmith | you would use the regular host list thing pointing at a cell config file | |
| 20:27:11 | dansmith | which we can automate from the top level for sure, | |
| 20:27:43 | dansmith | but it just seems not that useful to me to get 10k hosts in a list to find if host N is in cell M | |
| 20:27:46 | dansmith | but clearly it is | |
| 20:27:59 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Document and provide useful error message for volume-backed backup https://review.openstack.org/452970 | |
| 20:27:59 | openstackgerrit | Matt Riedemann proposed openstack/nova master: api-ref: move createBackup to server-actions https://review.openstack.org/452971 | |
| 20:28:00 | openstackgerrit | Matt Riedemann proposed openstack/nova master: 2.43: Remove Location header from createImage and createBackup responses https://review.openstack.org/455443 | |
| 20:28:50 | mriedem | dansmith: you mean nova-manage host list right? | |
| 20:28:53 | mriedem | pointing at the cell config? | |
| 20:28:58 | dansmith | yar | |
| 20:29:00 | mriedem | ok | |
| 20:29:08 | mriedem | maybe i'll start a FAQs section to the cells page | |
| 20:29:11 | mriedem | i thought about that at one point | |
| 20:29:15 | mriedem | same for placement | |
| 20:29:32 | mriedem | because there was a couple of weeks around ocata rc when i felt like we were answering the same questions over and over | |
| 20:30:26 | mriedem | oh snap today is supposed to be mitaka eol | |
| 20:36:17 | bauzas | mriedem: dansmith: cdent: edleafe: possibly a misunderstanding of me, but I thought we finally ended up saying that we would use the RequestSpec object as the conveyor for the RPC bus ? | |
| 20:36:46 | cdent | bauzas: mriedem wants it over rpc but not in the requestspec object | |
| 20:36:48 | bauzas | mriedem: dansmith: cdent: edleafe: but etherpad tells me we agreed it would be a separate RPC arg | |
| 20:37:13 | bauzas | okay, tbh, I'm not opiniated at all | |
| 20:37:38 | bauzas | cdent: anyway, seems an implementation detail to me (well, to a certain point since it requires RPC version bumps) | |
| 20:38:48 | dansmith | bauzas: the etherpad is right | |
| 20:39:33 | bauzas | roger. | |
| 20:41:32 | mriedem | -2 to stuffing the allocation list into the requestspec | |
| 20:41:40 | mriedem | the request spec is ALREADY an arg on the rpc call | |
| 20:41:48 | mriedem | remember, the unused floppy dildo? | |
| 20:42:25 | bauzas | mriedem: hold your -2 :p | |
| 20:42:43 | mriedem | -4 | |
| 20:45:37 | bauzas | 42 | |
| 20:47:38 | mriedem | bauzas: remember when you said the hangout time was too late for you? | |
| 20:47:50 | mriedem | and that was 5 hours ago | |
| 20:49:33 | bauzas | mriedem: don't ask me to explain the space/time relationship we have in France | |
| 20:49:56 | bauzas | it would require Einstein to come back and explain French theory of relativity | |
| 20:51:44 | openstackgerrit | Sylvain Bauza proposed openstack/nova-specs master: Placement doing claims https://review.openstack.org/437424 | |
| 20:52:08 | bauzas | dansmith: mriedem: cdent: edleafe: (and jaypipes FWIW) ^ | |
| 20:52:31 | bauzas | also, please note I'll be quite offline tomorrow afternoon my time | |
| 20:53:46 | edleafe | bauzas: cool, will review soon | |
| 20:55:32 | bauzas | because of this https://scontent-cdg2-1.xx.fbcdn.net/v/t31.0-8/17390425_1896048050684288_3792623604748129338_o.jpg?oh=fe50d8c043cb3958a87e71b91dcb44bb&oe=598BED45 | |
| 20:55:47 | bauzas | new co-worker arriving tomorrow ^ | |
| 21:03:28 | mriedem | oh man | |
| 21:15:04 | cdent | sdague, mtreinish: I didn't get as much done this evening as I wanted on uwsgi and other explorations, but will continue tomorrow. Most of today's work was simply getting my bearings, but I've started some notes on https://etherpad.openstack.org/p/devstack-uwsgi | |
| 21:15:09 | mriedem | dansmith: want to take a gander at https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata+topic:bug/1665698 and then once those are in i'll release ocata | |
| 21:15:17 | mriedem | sdague: mtreinish: ^ you too | |
| 21:20:49 | jroll | mriedem: so ironic wants to do a thing where we can tag ironic hosts with neutron networks, and make sure nova schedules instances to the hosts with matching networks. seems like nova's routed networks thing does that, but I don't understand what I would need to change to make that work for ironic. can you help with that or should I wait to bug johnthetubaguy ? | |
| 21:22:21 | mriedem | jroll: have you read through carl_baldwin's nova spec about working routed networks support into nova? | |
| 21:23:03 | mriedem | https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/neutron-routed-networks.html | |
| 21:23:07 | jroll | mriedem: yeah, is it all just host aggregate based? | |
| 21:23:19 | mriedem | yeah basically | |
| 21:23:34 | jroll | hrm | |
| 21:23:40 | mriedem | neutron creates a resource provider for the network allocation pool | |
| 21:23:48 | mriedem | that's tied to a host aggregate | |
| 21:24:05 | mriedem | honestly i'd have to go back and read the spec too, it's been since newton | |
| 21:24:11 | jroll | I can only aggregate hosts, right, not nodes? | |
| 21:24:30 | mriedem | yeah | |
| 21:24:34 | mriedem | well, i think so | |
| 21:24:44 | jroll | ya, sounds right | |
| 21:24:58 | mriedem | we don't distinguish between hosts and nodes in the api | |
| 21:25:02 | jroll | yeah | |
| 21:26:02 | jroll | mriedem: I was just going through our priorities and making sure we had BPs and such approved for everything, this was the only one that did not. might have something coming this week, I guess, if they had ideas | |
| 21:26:18 | mriedem | you have 3 days | |
| 21:26:33 | jroll | exactly :P | |
| 21:26:35 | mriedem | and then the boy dies | |