| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-11-28 | |||
| 23:48:03 | SpamapS | the smaller deployment was Pike with cells v2. | |
| 23:48:27 | SpamapS | RabbitMQ is basically the most hated thing on the OpenStack team at GoDaddy, so, I'm not sure anybody will give you a nuanced answer. ;) | |
| 23:49:27 | sorrison | yeah I am aware of klindgren hate for rabbit, it's been stable for us over the last couple years up until pike upgrade | |
| 23:50:18 | sorrison | we (nectar) have cellsv1, 13 cells ~1000 hypervisors | |
| #openstack-nova - 2018-11-29 | |||
| 00:01:35 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Default zero disk flavor to RULE_ADMIN_API in Stein https://review.openstack.org/603910 | |
| 00:05:06 | SpamapS | IIRC, we had some improvement with newer RabbitMQ versions. | |
| 00:06:04 | sorrison | SpamapS: yeah some of our cells have found upgraded rabbit helps. We tried to upgrade the rabbit that neutron uses and it fell over so we down graded back | |
| 00:36:58 | openstackgerrit | Artom Lifshitz proposed openstack/nova-specs master: Re-propose numa-aware-live-migration spec https://review.openstack.org/599587 | |
| 04:32:01 | openstackgerrit | Ghanshyam Mann proposed openstack/nova stable/queens: Test websocketproxy with TLS in the nova-next job https://review.openstack.org/620776 | |
| 04:44:05 | openstackgerrit | Ghanshyam Mann proposed openstack/nova stable/queens: Move the nova-next job in-tree and update it https://review.openstack.org/620777 | |
| 04:47:09 | openstackgerrit | Ghanshyam Mann proposed openstack/nova stable/queens: Test websocketproxy with TLS in the nova-next job https://review.openstack.org/620776 | |
| 07:24:24 | openstackgerrit | Brin Zhang proposed openstack/nova master: Remove useless sample and add the lack of tests in v266 https://review.openstack.org/614671 | |
| 07:32:24 | openstackgerrit | Brin Zhang proposed openstack/nova master: Remove useless sample tests in v266 https://review.openstack.org/614671 | |
| 09:27:48 | openstackgerrit | Matthew Booth proposed openstack/nova master: Workaround a race initialising version control in db_version() https://review.openstack.org/619622 | |
| 09:33:36 | openstackgerrit | Matthew Booth proposed openstack/nova master: Workaround a race initialising version control in db_version() https://review.openstack.org/619622 | |
| 09:35:42 | openstackgerrit | Jason SUN proposed openstack/nova master: Add task_states when confirm resize https://review.openstack.org/620848 | |
| 09:38:24 | openstackgerrit | Zhenyu Zheng proposed openstack/nova-specs master: Per aggregate scheduling weight (spec) https://review.openstack.org/599308 | |
| 09:40:15 | openstackgerrit | Alvaro Lopez Garcia proposed openstack/nova master: Ensure that periodic reclaim cleans DB deleted instances https://review.openstack.org/323250 | |
| 09:51:24 | ohorecny2_ | Hi #stephenfin, I would like to ask you about your commit https://github.com/openstack/nova/commit/6b3b04d2113915729fd9aced9839338e429e1a01 which implemented PCI NUMA policies, I found that this change is not working properly. So I search about fix and I found this bug: https://bugs.launchpad.net/nova/+bug/1795920 . I would like to ask you if anybody is working on it, or if you have some proposals how to fix it. | |
| 09:51:24 | openstack | Launchpad bug 1795920 in OpenStack Compute (nova) "SR-IOV shared PCI numa not working " [Undecided,Confirmed] | |
| 09:53:26 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Fix misuse of assertTrue https://review.openstack.org/620861 | |
| 10:08:39 | openstackgerrit | Merged openstack/nova master: Remove get_node_uuid https://review.openstack.org/620715 | |
| 10:10:08 | openstackgerrit | Kashyap Chamarthy proposed openstack/nova master: libvirt: Refactor handling of PCIe root ports https://review.openstack.org/620327 | |
| 10:14:45 | openstackgerrit | Alex Xu proposed openstack/nova master: Parse the numa topology from the new flavor when resize instance https://review.openstack.org/620874 | |
| 10:42:47 | mdbooth | bauzas: I need placement to think my compute has more than 2 vcpus in my functional test. Any idea what the best thing to mock would be? | |
| 10:57:44 | mdbooth | bauzas: When you're back, I think I'll be best mocking LibvirtDriver.get_available_resource() | |
| 11:07:28 | bauzas | mdbooth: well, no | |
| 11:07:38 | bauzas | mdbooth: we now have a new method | |
| 11:08:56 | bauzas | mdbooth: but do you need libvirt ? because we have a FakeDriver | |
| 11:10:50 | bauzas | mdbooth: https://github.com/openstack/nova/blob/master/nova/virt/fake.py | |
| 11:11:07 | bauzas | eg. https://github.com/openstack/nova/blob/master/nova/virt/fake.py#L138 | |
| 11:32:59 | openstackgerrit | Ghanshyam Mann proposed openstack/nova stable/queens: Make the nova-next job voting and gating https://review.openstack.org/620888 | |
| 12:10:31 | mdbooth | bauzas: No, I'm specifically testing the LibvirtDriver | |
| 12:10:38 | mdbooth | I *think* I've nearly got it | |
| 12:10:42 | mdbooth | Although.... | |
| 12:11:13 | mdbooth | AAAAAAAAAAAAAAAAAAARGH! methods which secretly modify shared data! | |
| 12:12:23 | sean-k-mooney | mdbooth: dose the method also retrun something? | |
| 12:13:01 | sean-k-mooney | if it just has sideffect its not terrible but if it both retruns things and has sideffect that is a pain | |
| 12:17:58 | mdbooth | bauzas: Sorted now. mocked libvirt methods for fetching disk space, vcpu, and memory, which are used in both places. | |
| 12:24:05 | cdent | mdbooth: tshirt | |
| 12:25:44 | mdbooth | cdent: Hehe | |
| 12:28:06 | mdbooth | cdent: This case wasn't egregious, tbh. LibvirtDriver._get_local_gb_info modified the return from libvirt_utils.get_fs_info() in place, which isn't unreasonable. However, I was mocking get_fs_info(), so it was always returning the same dict. It took me over an hour to work out why my disk space got 1000 times smaller every time it was called. | |
| 12:28:44 | cdent | <- doesn't know haskell | |
| 12:28:47 | mdbooth | FTW! | |
| 12:28:54 | mdbooth | <- neither | |
| 12:29:14 | cdent | of course the number of times I've heard people say that the original authors of nova didn't know python is unfortunately high | |
| 12:29:30 | mdbooth | HAHA | |
| 12:29:31 | cdent | so, you know, maybe it is a goer | |
| 12:30:15 | sean-k-mooney | i didnt know python when i started working on openstck not sure i still dont | |
| 12:31:07 | sean-k-mooney | python is a language that you can pick up as you go along and with the gated trunk/review model we use you learn what you need quickly | |
| 12:31:08 | cdent | yeah, that's the other side of the coin: if you can code, you can usally code anywhere, if you pay attention | |
| 12:31:52 | sean-k-mooney | yep once you lear to corralate different concpets in different languages and how to reason about problems that applies across many languages | |
| 12:32:22 | sean-k-mooney | functional programing people however i have found think differnetly then i do | |
| 12:33:37 | mdbooth | sean-k-mooney: It's a mental switch. It's not as hard to make as you'd think. | |
| 12:34:41 | sean-k-mooney | mdbooth: ya i have tried learning some functional libs in the past and i can use them but its still a style that i reserve for specific uses | |
| 12:34:56 | cdent | there are degrees as well. you can sort of pick and choose what you think matters most. for example: don't be side-effecty | |
| 12:35:21 | mdbooth | That's a general lesson | |
| 12:35:22 | cdent | for collaborative code maintenance I think that one is the most important | |
| 12:35:32 | cdent | a lesson people apparently don't learn often enough :) | |
| 12:36:07 | kashyap | cdent: What makes you think all the current contributors (/looks at self) "know" Python? :D | |
| 12:36:09 | cdent | If you're steeped in a certainly style of OO, it's too normal, even though it doesn't have to be | |
| 12:36:25 | cdent | kashyap: I was trying to be polite, please don't out me :) | |
| 12:36:46 | kashyap | Hehe, before I "out" anyone, /me goes to work on his own limitations | |
| 12:36:57 | sean-k-mooney | cdent: speaking of side effects this will reintoduce the placemetn wsgi isssue the run_once decorator was trying to avoid | |
| 12:36:58 | sean-k-mooney | https://review.openstack.org/#/c/620617/3/placement/db_api.py | |
| 12:37:19 | cdent | that's been abandoned | |
| 12:37:25 | sean-k-mooney | ya i just noticed | |
| 12:37:37 | cdent | in part because of exactly that | |
| 12:38:08 | sean-k-mooney | so is the issue fixed by the way? | |
| 12:40:16 | cdent | it's either fixed, or so out of the timing as to appear to be fixed. I got 77 successful runs last night | |
| 12:41:27 | sean-k-mooney | cool so just diffing the change ye stoped using a global config fixture | |
| 12:42:20 | cdent | sean-k-mooney: that helped, but the crux of the biscuit was probably moving something from init in the Database fixture to setUp | |
| 12:42:37 | cdent | which was probably wrong from the start, but didn't rear its head until mixing with nova | |
| 12:42:45 | cdent | jaypipes++ on the container shinkerage | |
| 12:43:23 | cdent | I think you've nailed it with "lightweight vms in disguise" | |
| 12:43:27 | sean-k-mooney | cdent: ah ok. ya this is proably raising it head due to the use of eventlets in nova | |
| 12:43:56 | kashyap | cdent: Where was that comment from Jay? | |
| 12:44:10 | sean-k-mooney | i just recived it in my email | |
| 12:44:14 | cdent | the removal of global config is still a huge win, sean-k-mooney, so I'm hoping we can keep and merge that soon | |
| 12:44:25 | sean-k-mooney | cdent is a few minuts ahead of us it seams | |
| 12:44:33 | cdent | http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000338.html | |
| 12:44:49 | cdent | I subscribed to openstack-discuss very early so probably my messages a few seconds before others :) | |
| 12:46:28 | kashyap | Also all the mailing lists are being merged, aren't they? | |
| 12:46:59 | cdent | yeah, openstack-discuss is the one true mailing list now | |
| 12:47:27 | cdent | until early next week the others are still around and include the new one in what they send to | |
| 12:47:37 | cdent | but next week the old ones will stop accepting submissions | |
| 12:47:45 | cdent | but the archives will remain | |
| 12:48:37 | kashyap | (Thx) | |
| 12:48:52 | kashyap | cdent: What's the rationale for merging all of them, and making it into a one Jupiter-sized firehose? | |
| 12:49:23 | cdent | yeah probably better to read the related discussion. there are many reasons | |
| 12:49:35 | cdent | some better than others | |
| 12:50:48 | kashyap | Thanks | |
| 12:51:33 | cdent | the overriding reason is to break down some of the artificial boundaries between devs, users, ops, I touch upon that in https://anticdent.org/mailing-list-review.html | |
| 12:52:41 | kashyap | Yeah, but it also requires people to massively "up their game" of managing emails. | |
| 12:53:16 | cdent | Yes, that was one of the arguments that people made, but the conclusions appeared to be: you need to do that anyway for any of the lists | |
| 12:53:25 | cdent | which seemed a bit weak to me, but meh | |
| 12:53:55 | kashyap | cdent: If only more people realized (not just in our community; but inside company lists, too) this: | |
| 12:53:58 | kashyap | [quote] | |
| 12:53:59 | kashyap | [/quote] | |
| 12:54:01 | kashyap | Your main goal as a member of a mailing list is to keep the archive as useful as possible for other members of the community. Do that, and the dynamic activity on the list itself also manages to be useful. | |