| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-01-23 | |||
| 11:49:07 | openstackgerrit | Stephen Finucane proposed openstack/nova: Fix and add some notes to the cells v2 first time setup doc https://review.openstack.org/421421 | |
| 11:55:49 | openstackgerrit | Alvaro Lopez Garcia proposed openstack/nova: Ensure that periodic reclaim cleans DB deleted instances https://review.openstack.org/323250 | |
| 12:00:27 | openstackgerrit | Zhenyu Zheng proposed openstack/nova: Fix device taging after API microversion 2.37 https://review.openstack.org/423952 | |
| 12:28:16 | openstackgerrit | Wang Qing wu proposed openstack/nova: WIP(5): Introduce base PowerVM driver (ovs vif) https://review.openstack.org/422512 | |
| 12:39:16 | openstackgerrit | Wang Qing wu proposed openstack/nova: WIP(5): Introduce base PowerVM driver (ovs vif) https://review.openstack.org/422512 | |
| 12:48:38 | openstackgerrit | Alex Szarka proposed openstack/nova: Transform instance-live_migration_abort notification https://review.openstack.org/420453 | |
| 12:55:46 | lyarwood | sfinucan: thanks for the review on the findmnt change, https://review.openstack.org/#/c/418371/ is another straight forward one adding a missing releasenote if you have time today | |
| 13:02:49 | snikitin | johnthetubaguy: Hi John! can you look at instance diagnostics implementation for Xen please? https://review.openstack.org/#/c/399613/ | |
| 13:06:48 | hachi | alex_xu thank you. | |
| 13:06:59 | hachi | but i don't want my users within the same project do accidently delete the VM(s) of each other. | |
| 13:07:18 | hachi | how i can do that without user_id policy ? | |
| 13:09:12 | bhagyashris | cdent: Hi, | |
| 13:11:21 | alex_xu | hachi: you can lock the instance | |
| 13:14:21 | cdent | bhagyashris: hi, what's up? | |
| 13:14:55 | dims | sean-k-mooney : jaypipes : https://review.openstack.org/#/c/423718/ does the trick for getting os-vif's linuxbridge working | |
| 13:15:33 | hachi | alex_xu thank you for the tip. I will try that. | |
| 13:15:43 | amrith | andreykurilin, ping. I'm having a little issue with nova's 7.0.0 client, would you have a couple of minutes to help out? thx | |
| 13:16:59 | amrith | one part of this is a change you submitted, https://review.openstack.org/#/c/412497/ | |
| 13:17:31 | amrith | appears that something changed in 7.0.0 which I'm not quite grok'ing. pl ping me if you have a minute andreykurilin. thx | |
| 13:18:03 | openstackgerrit | Zhenyu Zheng proposed openstack/nova: Add new policy for server list/detail with all_tenants https://review.openstack.org/415330 | |
| 13:19:56 | openstackgerrit | Julian proposed openstack/nova: Create cmd/script that prints JSON Schema of Notification Payload Classes https://review.openstack.org/411836 | |
| 13:21:27 | alex_xu | hachi: np | |
| 13:27:21 | openstackgerrit | Zhenyu Zheng proposed openstack/nova: Add sort_key white list for server list/detail https://review.openstack.org/415142 | |
| 13:31:32 | openstackgerrit | Sylvain Bauza proposed openstack/nova: WIP: Scheduler calling the Placement API https://review.openstack.org/417961 | |
| 13:31:32 | openstackgerrit | Sylvain Bauza proposed openstack/nova: Fix the FakeDriver using same hypervisor names https://review.openstack.org/424110 | |
| 13:32:06 | bauzas | cdent: johnthetubaguy: dansmith: latest versions for the high-prio scheduler placement changes ^ | |
| 13:33:45 | bauzas | cdent: you'll see now the conditional branch for checking the filters before calling the placement service | |
| 13:34:47 | bhagyashris | cdent: I have few questions in my mind regarding Scheduler calling the Placement API [1] https://review.openstack.org/#/c/417961. 1. As it updates allocation information at the placement db so is there a need of compute node table for resource tracking? | |
| 13:37:07 | cdent | bhagyashris: the resource tracker and the nova-scheduler will carry on needing to know about compute nodes, yes. Is that what you're asking? The placement services itself will not need to know about the compute node table, just the uuids of those compute nodes, represented as resource providers in the placement api | |
| 13:37:48 | openstackgerrit | Mikhail Feoktistov proposed openstack/nova: libvirt: ephemeral disk support for virtuozzo containers https://review.openstack.org/312488 | |
| 13:42:29 | openstackgerrit | Claudiu Belu proposed openstack/nova: hyper-v: Do not allow instances with pinned CPUs to spawn https://review.openstack.org/424116 | |
| 13:47:18 | sfinucan | lyarwood: Done and done https://review.openstack.org/#/c/418371/1 | |
| 13:47:45 | sfinucan | johnthetubaguy: ^ that looks like a straightforward +W - could you take a glance if you have a moment? | |
| 13:49:13 | lyarwood | sfinucan: cheers | |
| 13:50:22 | bhagyashris | cdent: I know , i am asking lot of questions :) I just want to know if we are using the placement apis then will compute node table be needed in that case? If it will used then in which case it will be used and for what? | |
| 13:51:29 | diga | jaypipes: Hi | |
| 13:51:31 | cdent | bhagyashris: it will carry on being used for keeping track of the compute nodes because nova still needs to know about them | |
| 13:51:31 | johnthetubaguy | sfinucan: ack, thanks | |
| 13:51:51 | cdent | diga: jaypipes is on PTO, maybe somebody else can help? | |
| 13:52:04 | diga | cdent: Hi, sure | |
| 13:52:20 | diga | cdent: https://review.openstack.org/#/c/423872/ can you review this spec - placement notification | |
| 13:53:09 | cdent | yeah, sure, will stick that on my list for today | |
| 13:54:22 | diga | cdent: :) thank you! | |
| 13:54:31 | diga | cdent: we have meeting now right ? | |
| 13:54:36 | cdent | yeah, in five minutes | |
| 13:55:00 | diga | okay | |
| 13:55:04 | edleafe | diga: in #openstack-meeting-alt | |
| 13:55:21 | diga | edleafe: Sure, will join | |
| 13:56:07 | andreykurilin | amrith: hi | |
| 13:56:23 | amrith | hi andreykurilin | |
| 13:56:33 | amrith | did you see the email I just sent you | |
| 13:56:47 | andreykurilin | yes | |
| 13:56:50 | johnthetubaguy | bauzas: you say only ironic needs the host field, isn't that what we use for the RPC call? | |
| 13:57:05 | amrith | the issue I'm facing is that if I use the v6.0.0 client things work fine | |
| 13:57:15 | amrith | if I switch to the v7.0.0 client, it bombs out | |
| 13:57:21 | bauzas | johnthetubaguy: I meant the problem is that host != node for Ironic | |
| 13:57:23 | johnthetubaguy | bauzas: or is that the node vs host thing | |
| 13:57:29 | bauzas | yup that | |
| 13:57:29 | amrith | am not sure why that would be the case | |
| 13:57:30 | johnthetubaguy | bauzas: ah, gotcha | |
| 13:57:36 | bauzas | maybe my comment is unclear, sorry if so | |
| 13:57:38 | andreykurilin | amrith: I have just several minutes before meeting and will able to help you in ~30 minutes | |
| 13:57:48 | bauzas | but I can't say that I could just use the RP name | |
| 13:58:01 | bauzas | given it's the nodename which can be different for ironic | |
| 13:58:05 | amrith | andreykurilin, I'll be here. | |
| 13:58:13 | andreykurilin | amrith: but now I have one question: What is user.tenant https://github.com/openstack/trove/blob/master/trove/tests/util/__init__.py#L170 here? Is it tenant name or id? | |
| 13:58:23 | bauzas | while the other drivers (except the Fake driver, but that's fixed in a bottom patch) are using host == node | |
| 13:58:29 | bauzas | johnthetubaguy: ^ | |
| 13:58:31 | amrith | looking | |
| 13:59:56 | johnthetubaguy | bauzas: the custom resource class stuff should fix that, I am assuming | |
| 14:00:13 | bauzas | johnthetubaguy: yeah, but it could be merged by Pike | |
| 14:00:23 | bauzas | johnthetubaguy: hence me using the new object method I created | |
| 14:00:44 | bauzas | we could just cut that once the above BP you mentioned is fully merged | |
| 14:01:00 | bauzas | but AFAICS, that's still not done yet hence my big fat comment | |
| 14:01:14 | johnthetubaguy | bauzas: yeah, no biggie, just getting my head straight on that | |
| 14:01:40 | bauzas | np | |
| 14:01:55 | bauzas | johnthetubaguy: I have a bigger concern that I wrote in a ML thread this week-end | |
| 14:02:03 | edleafe | bauzas: scheduler meeting? | |
| 14:02:11 | bauzas | edleafe: I can do, for 20 mins | |
| 14:02:21 | edleafe | cool | |
| 14:02:23 | amrith | andreykurilin, one second, you are looking at the tests. I wasn't running test code | |
| 14:02:32 | bauzas | edleafe: but I'm pretty down given all the work I'm doing atm | |
| 14:02:33 | andreykurilin | ok... | |
| 14:02:34 | amrith | I was running a straight trove command which tried to hit nova | |
| 14:02:42 | amrith | I will find out what that is | |
| 14:02:58 | andreykurilin | I just look at first failure at gates:) | |
| 14:03:01 | andreykurilin | *looked | |
| 14:03:12 | amrith | but for what I've been trying to do, the code is at https://github.com/openstack/trove/blob/master/trove/common/remote.py#L101 | |
| 14:03:17 | amrith | ah, sorry | |
| 14:03:27 | amrith | I am running trove locally to debug | |
| 14:03:38 | amrith | here, we're making a client with version 2.12 | |
| 14:03:58 | amrith | which comes from https://github.com/openstack/trove/blob/master/trove/common/cfg.py#L67 | |
| 14:04:05 | amrith | and we're passing in a bunch of parameters | |
| 14:04:23 | amrith | my specific issue (and like I said in the email, trove may be doing something wrong here) | |
| 14:04:33 | amrith | we're making the call like https://github.com/openstack/trove/blob/master/trove/common/remote.py#L101 | |
| 14:04:49 | amrith | and if I understand compatibility right, this should work unchanged with the v7.0.0 client from nova | |
| 14:04:51 | andreykurilin | amrith: need to go to meeting, sorry. PS: it should help(with depends-on) ttps://review.openstack.org/412497 | |
| 14:04:51 | amrith | but it isn't | |
| 14:05:09 | amrith | nope, doesn't help | |
| 14:05:15 | amrith | tried it | |