| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-03-01 | |||
| 10:36:51 | johnthetubaguy | install docs are out of date | |
| 10:36:57 | johnthetubaguy | for placement-api | |
| 10:37:04 | johnthetubaguy | (and cells stuff actually) | |
| 10:37:05 | asettle | bauzas: documentation for the nova portion of the install guide requires updates. ARe there plans to get this updated, or is there someone we can work with to get this updated? | |
| 10:41:49 | bauzas | looks like a huge knowledge transfer to do | |
| 10:42:10 | bauzas | asettle: we have a couple of dev docs that are intended to be user-facing tho | |
| 10:44:24 | asettle | bauzas: if you already have the dev docs, are there any plans to move them and improve on the install guide? | |
| 10:47:29 | bauzas | asettle: well, I did contributed to some docs repo a while ago, but it's a very long story :) | |
| 10:47:40 | prometheanfire | andymccr: still need that mail? | |
| 10:47:45 | prometheanfire | asettle: ^ | |
| 10:47:48 | asettle | Hhahaa bauzas I'd be interested to know how it went - if it was bad, we gotta improve, all that et etc | |
| 10:47:51 | prometheanfire | bad tab complete | |
| 10:47:51 | asettle | prometheanfire: mail?! | |
| 10:47:55 | prometheanfire | to the list | |
| 10:48:03 | bauzas | asettle: well, it was 2013, and it went well :) | |
| 10:48:21 | prometheanfire | thought I was in doc channel, been a long day... | |
| 10:48:31 | asettle | prometheanfire: ummm I don't think so :) thank you hahhaha go to bed dude | |
| 10:48:46 | prometheanfire | :D | |
| 10:48:48 | asettle | bauzas: well that's good! Okay, well. Let's get a bit of an action plan together to get these docs updated. | |
| 10:48:49 | prometheanfire | nn | |
| 10:49:07 | asettle | I am probably going to email out to everyone who is a docs liaison to ensure these docs are being updated continuously each release | |
| 10:49:12 | asettle | Seems to be a bit of a problem | |
| 10:49:33 | johnthetubaguy | asettle: we did talk about getting a new person to take that on | |
| 10:49:56 | johnthetubaguy | asettle: the api stuff is all up to date now, we do that when new APIs land | |
| 10:50:07 | johnthetubaguy | well, apart form the concept guide, I mean api-ref | |
| 10:50:18 | johnthetubaguy | asettle: but totally need someone to own the install docs | |
| 10:51:03 | asettle | johnthetubaguy: I would agree. Who is PTL of nova? (pardon my ignorance) we need to reach out and get this organised :) | |
| 10:51:35 | asettle | johnthetubaguy: do we have any OSIC people who would be good for the job? I know they've done that in keystone and glance. | |
| 10:51:55 | bauzas | asettle: FYI, most of the user/deployer notes for placement can be found in https://docs.openstack.org/developer/nova/placement.html | |
| 10:52:03 | openstackgerrit | Moshe Levi proposed openstack/nova master: [WIP] OVS acceleration https://review.openstack.org/398265 | |
| 10:52:17 | asettle | bauzas: okay cool :) what's good to know is that it's there, and that we're not creating something out of thin air | |
| 10:52:53 | openstackgerrit | Timofey Durakov proposed openstack/python-novaclient master: Deperecate cell_name cli arg for migration-list https://review.openstack.org/439141 | |
| 10:52:57 | bauzas | asettle: for cells v2, deployer instructions are in https://docs.openstack.org/developer/nova/cells.html#setup-of-cells-v2 | |
| 10:54:08 | asettle | bauzas: again, good news. A knowledge transfer should be fairly straight forward from here. | |
| 10:56:48 | johnthetubaguy | asettle: lots of that evolved from the OSA feedback too, its just that last (all important) step thats needed really | |
| 10:57:02 | asettle | johnthetubaguy: even better. | |
| 10:57:19 | asettle | Regardless, I think we need to have a better review process at the end of each release. | |
| 11:02:18 | mdbooth | lyarwood johnthetubaguy: multipath | |
| 11:02:52 | mdbooth | Is nova ever going to model multipath as multiple attachments, or only as a single multipath attachment? | |
| 11:05:56 | johnthetubaguy | mdbooth: I was assuming a single attachment, but its a good question | |
| 11:06:47 | lyarwood | mdbooth: I would also say single, why? | |
| 11:07:02 | sfinucan | tonyb: Couldn't find logs/emails about that issue :/ Anywho, we're stuck with Sphinx 1.3.6 you mean? | |
| 11:07:38 | mdbooth | lyarwood: Just trying to think of problems which would be hard to fix | |
| 11:07:39 | tonyb | sfinucan: for a little longer | |
| 11:08:10 | sfinucan | tonyb: Darn. | |
| 11:08:14 | tonyb | sfinucan: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113085.html | |
| 11:10:17 | sfinucan | tonyb: Just for context, why can't we use pbr (and where can't we use it) if it's been capped in some projects | |
| 11:10:55 | tonyb | sfinucan: that's cool it's a little complex | |
| 11:12:15 | tonyb | sfinucan: upper-constraints.txt os a list of every python library need by some part of OpenStack that we knwo works (at least installs) together | |
| 11:12:35 | tonyb | sfinucan: and all nice projects (such as nova) install *only taht version | |
| 11:13:12 | tonyb | sfinucan: sadly when we try to set the version of pbr === 2.0.0 in u-c.txt there are a small number of libraries that can't be installed | |
| 11:13:36 | tonyb | sfinucan: and therefore no part of OpenStack can use that version until they all agree that 2.0.0 is ok | |
| 11:14:20 | tonyb | sfinucan: upper-constraints.txt does a bunch of other things but it's beyond my ability to expalin on IRC late at night (for me) | |
| 11:14:57 | sfinucan | tonyb: ahhh, gotcha | |
| 11:15:56 | tonyb | sfinucan: there are reviews and PRs out to move the ball forward so we'll see how quickly they land and then we can take the next step | |
| 11:16:23 | sfinucan | tonyb: Perfect. Any topic I can look at? | |
| 11:16:31 | sfinucan | Throw a few reviews in | |
| 11:16:56 | tonyb | sfinucan: https://review.openstack.org/#/q/topic:bug/1668848 | |
| 11:17:38 | sfinucan | tonyb: fwiw, I'm pretty sure this has been said many times but you can't bump Sphinx until everything is using pbr 2.0, because 1.10 is broken with Sphinx 1.5 | |
| 11:17:47 | sfinucan | tonyb: Spot on. Thanks | |
| 11:18:45 | tonyb | sfinucan: right. | |
| 11:19:12 | sfinucan | tonyb: That also would suggest we should be bumping pbr to 2.0, perhaps? | |
| 11:19:17 | sfinucan | or at least blacklisting 1.10 | |
| 11:20:33 | tonyb | sfinucan: Yeah we'll set the minimum to 2.0.0 once if tested it a bit | |
| 11:21:20 | sfinucan | tonyb: Cool. Could we blacklist 1.10 also though? Allows us to start using Sphinx 1.5 | |
| 11:21:24 | sfinucan | (eventually) | |
| 11:21:37 | tonyb | sfinucan: Yeah we could | |
| 11:22:26 | sfinucan | OK. Guess that can be done later though | |
| 11:34:22 | kevinbenton | johnthetubaguy: how is your metadata-fu? | |
| 11:35:04 | johnthetubaguy | kevinbenton: rusty, but whats up? | |
| 11:35:18 | kevinbenton | johnthetubaguy: debugging a failure i observed in the gate | |
| 11:35:25 | kevinbenton | johnthetubaguy: one of the cirros VMs is not getting an SSH key | |
| 11:35:45 | johnthetubaguy | oh, interesting, almost like its fetching metadata before the ssh key is present in the metadata service | |
| 11:36:00 | johnthetubaguy | was it using config drive or not? | |
| 11:36:14 | kevinbenton | johnthetubaguy: no config drive | |
| 11:36:18 | kevinbenton | johnthetubaguy: just metadata | |
| 11:36:27 | kevinbenton | johnthetubaguy: i traced the request all of the way to nova API | |
| 11:36:33 | kevinbenton | johnthetubaguy: but the debug logs there aren't very helpful | |
| 11:36:40 | johnthetubaguy | ah, cool, you got a link to those | |
| 11:36:49 | kevinbenton | johnthetubaguy: http://logs.openstack.org/27/436427/2/gate/gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial/2f3e394/logs/screen-n-api.txt.gz | |
| 11:36:54 | johnthetubaguy | at least the request got there, that was my main question | |
| 11:37:02 | kevinbenton | johnthetubaguy: request-id in question is req-93182a9d-baa9-4cf5-8648-aa9c4a49500 | |
| 11:37:41 | kevinbenton | johnthetubaguy: whatever it is returning there is making cirros think there is nothing further so it doesn't continue on to query the openssh url for the actual keys | |
| 11:39:19 | kevinbenton | johnthetubaguy: a good request ID in the same tenant and behind the same router is req-ff83fad3-86cc-4097-aa6e-538c6889eae2 | |
| 11:39:42 | kevinbenton | johnthetubaguy: would digging up the corresponding instance IDs be helpful? | |
| 11:40:21 | johnthetubaguy | not sure that helps in the logs, I guess it would let you find the create instance requests etc, int he compute logs which would have a hint | |
| 11:40:33 | johnthetubaguy | kevinbenton: this is one of those cases where we just get ssh didn't work errors right? | |
| 11:40:49 | kevinbenton | johnthetubaguy: well in this case it's explicit authentication failures | |
| 11:40:59 | johnthetubaguy | ah, right, that makes sense | |
| 11:41:00 | kevinbenton | johnthetubaguy: 2017-02-28 11:48:29,144 12602 INFO [paramiko.transport] Authentication (publickey) failed. | |
| 11:43:37 | kevinbenton | good instance ID is 747e0481 | |
| 11:43:55 | johnthetubaguy | kevinbenton: maybe finding the server_id here will help, looks like the bad one was 31ca7a58-2a91-4893-bcb0-7c457023f6a1 | |
| 11:44:42 | kevinbenton | aye | |
| 11:44:47 | johnthetubaguy | kevinbenton: oh right, I see GET /2009-04-04/meta-data/public-keys/0/openssh-key | |
| 11:45:21 | kevinbenton | johnthetubaguy: so in the bad case whatever that first one is returning is telling it no keys | |
| 11:45:31 | johnthetubaguy | yeah, it seems it must be | |
| 11:46:16 | kevinbenton | is the preparation of the metadata asynchronous? | |
| 11:47:24 | johnthetubaguy | I think it should be all before the instance boots | |
| 11:47:28 | johnthetubaguy | but I am wondering that now too | |
| 11:51:22 | johnthetubaguy | kevinbenton: so the ssh key is in the compute logs | |