| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-11-14 | |||
| 15:47:39 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove mox in virt/test_block_device.py https://review.openstack.org/566153 | |
| 15:48:05 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: api-ref: Add descriptions for vol-backed snapshots https://review.openstack.org/615084 | |
| 15:48:25 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Use links to placement docs in nova docs https://review.openstack.org/614056 | |
| 15:48:39 | sean-k-mooney | jaypipes: are you at the summit by the way. you ususally only attend the ptgs as of late | |
| 15:48:48 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Remove Placement API reference https://review.openstack.org/614437 | |
| 15:48:52 | jaypipes | sean-k-mooney: no. I'm not in Berlin | |
| 15:49:08 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Transform compute_task notifications https://review.openstack.org/482629 | |
| 15:49:26 | sean-k-mooney | jaypipes: ah ok same. its weird not being there but also i got to review that spec again | |
| 15:49:28 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Use oslo_db.sqlalchemy.test_fixtures https://review.openstack.org/609352 | |
| 15:50:05 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Fix best_match() deprecation warning https://review.openstack.org/611204 | |
| 15:50:23 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Fix server query examples https://review.openstack.org/616834 | |
| 15:51:08 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 15:56:15 | jaypipes | sean-k-mooney: hell of a reward... | |
| 16:04:26 | mriedem | ha | |
| 16:50:58 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 16:56:34 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 17:35:36 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 19:45:08 | spatel | sean-k-mooney: ^^ | |
| 19:46:08 | spatel | if i have 8 vCPU on instance then its ok to set ethtool -L eth0 combined 8 ? | |
| 19:46:35 | spatel | or i should set 4 (50% of number of cpu) | |
| 20:32:45 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Send RP uuid in the port binding https://review.openstack.org/569459 | |
| 20:32:45 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Pass allocations and traits to neturonv2 api https://review.openstack.org/616240 | |
| 20:32:46 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Test boot with more ports with bandwidth request https://review.openstack.org/573317 | |
| #openstack-nova - 2018-11-15 | |||
| 00:01:18 | sean-k-mooney | spatel you should set it to 8 assuming you have eneabled multi queue | |
| 02:21:37 | lucidguy | lord help me | |
| 02:22:16 | lucidguy | New installment of OpenStack Queens, everything looks good yet my instances just sit there scheduling. I can't figure it out, logs tell me nothing. | |
| 02:22:19 | lucidguy | help | |
| 02:22:21 | lucidguy | :) | |
| 07:09:27 | openstackgerrit | OpenStack Proposal Bot proposed openstack/nova stable/rocky: Imported Translations from Zanata https://review.openstack.org/614757 | |
| 10:06:05 | mriedem | bauzas: gibi: do we have a functional test with vGPU resources that verifies reshaping of flat vGPU resources to nested vGPU resources and successful scheduling to the same compute host after reshaping - maybe not necessarily vgpu, but some kind of resource reshape + scheduling | |
| 10:06:15 | mriedem | i thought that was being worked on during the ptg by tetsuro | |
| 10:15:02 | gibi | mriedem: let me dig a bit | |
| 10:15:57 | gibi | mriedem: at least I did not implemented such scenario | |
| 10:18:49 | melwitt | yeah, looks like it would need to added to this (reshaper for vGPU) patch or stacked on top https://review.openstack.org/599208 | |
| 10:20:25 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 10:21:45 | gibi | mriedem, melwitt: there is nova.tests.functional.test_servers.ProviderTreeTests.test_reshape it almost what you want. it boots, then reshapes but it does not boot again after the reshape | |
| 10:22:10 | mriedem | ok i thought we had a functional test to go from flat to nested and then schedule another workload on that provider | |
| 10:22:49 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 10:23:55 | cdent | gibi: that ^ is the latest. I've needed to do quite a bit to make unit tests not think about placement | |
| 10:25:01 | melwitt | gibi: oh, so that same test will exercise the virt integration code? that's where I'm not clear on | |
| 10:26:14 | gibi | cdent: ack | |
| 10:27:50 | gibi | melwitt: to have rehape in the test we need a virt layer returning a reshaped tree. I don't think the actal vgpu virt integration needs to be covered in the same test | |
| 10:28:56 | melwitt | what I mean is, does test_reshape verify that https://review.openstack.org/599208 works correctly I wonder | |
| 10:32:19 | gibi | melwitt: it does not cover the VGPU resource specifically therefore it does not cover the change in https://review.openstack.org/#/c/599208/8/nova/virt/libvirt/driver.py | |
| 10:33:49 | melwitt | thanks | |
| 10:49:46 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 11:22:08 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 11:23:00 | sean-k-mooney | stephenfin: https://review.openstack.org/#/c/568999 was rebased care to take a look | |
| 12:38:34 | frickler | coreycb: latest nova stable/pike released switched from ostestr to stestr, which draws a bunch of dependencies in, did someone start working on getting these into pike uca yet? I'd like to avoid duplicating the work | |
| 12:53:33 | coreycb | frickler: i haven't gotten to the latest stable release. we are due for an update for pike. | |
| 12:53:59 | coreycb | frickler: so haven't considered it. but if we need to backport packages that are only used for testing that shouldn't be a problem. | |
| 12:55:27 | sean-k-mooney | coreycb: frickler is this not somthing that should have been done prior to the pike release on ubuntu | |
| 12:55:53 | coreycb | sean-k-mooney: if other projects were using stestr then yes | |
| 12:56:59 | sean-k-mooney | well assuming ubuntu shipped nova it should still have used it but yes i belive several project made the swtich and i think all use it at this point | |
| 12:57:10 | sean-k-mooney | at least the python ones | |
| 12:57:12 | coreycb | sean-k-mooney: it's a little odd to switch dependencies for a stable release though | |
| 12:57:45 | sean-k-mooney | coreycb: yes which is why im questioning backportingt stestr if it was not already done | |
| 12:58:30 | coreycb | sean-k-mooney: just checked and we don't have stestr backported for pike | |
| 12:58:35 | sean-k-mooney | anyway i gues that up to ye to decided. its a test package so it should be a much lower risk | |
| 12:59:27 | sean-k-mooney | the change to stestr was made in pike right so its not that its not backprot it was never packaged when the release was made | |
| 13:00:14 | sean-k-mooney | or are you saying pike used ostester and frickler was wondering could you backport stestr to use instead on pike | |
| 13:01:20 | coreycb | sean-k-mooney: it appears that no projects in the cloud archive for pike currently use stestr so we may not have packaged it for pike | |
| 13:03:19 | sean-k-mooney | coreycb: so in that case the unit and functional tests would not have been runable for nova on pike without installing stestr from pip | |
| 13:04:09 | coreycb | sean-k-mooney: right, well s/wouldn't/won't/ in our case because we're not at 16.1.6 yet | |
| 13:05:40 | sean-k-mooney | coreycb: well its listed in the test requirements.txt https://github.com/openstack/nova/blob/stable/pike/test-requirements.txt#L20 so i you have the deb installed and you go to the site pacages directory you should just be able to run tox to run the tests and it will install it in the venv | |
| 13:06:13 | sean-k-mooney | that said i guess that would not be testing with the distro packages | |
| 13:06:35 | sean-k-mooney | i belive you can still run the test with ostester so its not a hard requirement | |
| 13:06:46 | coreycb | sean-k-mooney: yeah but that's not how debian packages work | |
| 13:07:35 | coreycb | sean-k-mooney: i'll raise an issue with you all if we have any problems. | |
| 13:07:50 | coreycb | sean-k-mooney: but i think we can probably figure it out | |
| 13:08:22 | coreycb | sean-k-mooney: still it's probably a change that shouldn't have landed in a stable branch | |
| 13:09:09 | openstackgerrit | Chris Dent proposed openstack/nova master: WIP: Use external placement in functional tests https://review.openstack.org/617941 | |
| 13:09:20 | cdent | gibi: let's see how that one goes (the depends-on has been updated too) | |
| 13:10:35 | frickler | sean-k-mooney: fyi this was introduced in https://review.openstack.org/580492 . result is I cannot build latest release within pike UCA currently | |
| 13:11:06 | sean-k-mooney | coreycb: oh it didnt ship this way https://github.com/openstack/nova/commit/5939ae995fdeb2746346ebd81ce223e4fe891c85 you are right that should not have landed in a stable branch | |
| 13:11:07 | gibi | cdent: testing it locally... | |
| 13:12:04 | cdent | i've been doing spot checks locally, haven't got reasonable cpu for the whole set | |
| 13:12:54 | sean-k-mooney | lyarwood: https://review.openstack.org/#/c/580492/ added a new dependcy to stable pike why was this allowed to be backported? | |
| 13:16:07 | lyarwood | sean-k-mooney: test dependcy that was already widely used by other projects | |
| 13:16:41 | gibi | cdent: I have access to a pretty big machine. `tox -e functional` now all green | |
| 13:16:58 | cdent | woot | |
| 13:17:21 | cdent | let's see what the gate wants to break | |
| 13:17:32 | lyarwood | dependency* | |
| 13:18:02 | cdent | gibi: do you agree with my choice to remove tests but not code (yet)? That made things easier, but I'm not sure it is proper. | |
| 13:20:57 | sean-k-mooney | lyarwood: still we normally dont even allow version bumps and in pike im not sure it was widely used yet. | |
| 13:21:21 | sean-k-mooney | lyarwood: infact on stable/pike keystone,glance,neutron and cinder still use ostestr | |
| 13:21:24 | lyarwood | sean-k-mooney: did this break anything/anyone? | |
| 13:21:55 | sean-k-mooney | yes it broke debian distros as its not packaged in uca in ubuntu or in based debian im guessing | |
| 13:21:59 | sean-k-mooney | stestr that is | |
| 13:22:07 | gibi | cdent: I agree with that compromise. I think the patch is alreasy complex. I think there will be a code removal patch later, after nova switched to use split placement repo | |
| 13:23:27 | gibi | cdent: I think the only problematic situation when we fix bugs in the placement code that is in the nova repo while nova still depends on that copy of the placement code | |
| 13:24:20 | sean-k-mooney | lyarwood: so far of all the project i have looked at nova is now the only project using stestr on pike | |
| 13:25:24 | lyarwood | sean-k-mooney: I was sure mtreinish was doing this across stable/pike tbh | |
| 13:27:06 | sean-k-mooney | nope https://review.openstack.org/#/q/owner:%22Matthew+Treinish%22++stestr+branch:stable/pike | |
| 13:27:21 | sean-k-mooney | look like it was nova only | |
| 13:27:35 | lyarwood | urgh | |
| 13:33:04 | sean-k-mooney | coreycb: frickler are ye going to adress this by packaging stester for pike or do we need a revert of jsut the stestr change? | |
| 13:34:28 | coreycb | sean-k-mooney: i wouldn't be opposed to a revert of stestr usage. if you didn't we could probably figure it out on our end it's just a bit of a pita. :) | |
| 13:36:06 | sean-k-mooney | well thats something that i guess the nova stable team should discuss. proably sooner rather then later | |
| 13:36:15 | sean-k-mooney | am im just going to grab lunch so brb | |