| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2020-02-18 | |||
| 19:51:31 | sean-k-mooney | kind of like i did for the pcpu testing | |
| 19:51:36 | dansmith | sean-k-mooney: ah okay, that's my next step is digging into how the test gets setup because booting with a profile name gives me NVH, which I assume is because it hasn't found a compute with my device profile | |
| 19:51:38 | dansmith | but I didn't dig in | |
| 19:53:45 | sean-k-mooney | i had this automated in a bash script however the physical server i run my openstack on at home has been raising hardawer machine check errors for the last month or so on and off and now it wont detect my pci ssd with the host os | |
| 19:54:40 | sean-k-mooney | so had to set eveything up again that said i have a simpler version that i can also share. it might make more sense to email the list with the 3/4 files as an attament | |
| 19:55:08 | sean-k-mooney | but ya if i sit down tomorow i shoudl be able to hack a job together to do at least some testing | |
| 20:04:56 | umbSublime | Hi, this isn't a question about nova specificaly, but I'm asking here becasue i know many of you have attended openstack events. I'm re-starting the openstack-meetup group in my area and wanted to know if we can use the Openstack logo. It sayd here https://www.openstack.org/legal/openstack-restricted-use-logo-guidelines/ that we nee written permission. Is this enforced ? | |
| 20:06:12 | umbSublime | The company I am working for is hosting the event and want to know if it's OK to come up with a "<Insert company name> loves <openstacklogo>" flyers/stickers/wtv | |
| 20:19:37 | efried | umbSublime: If I were trying to find an official answer, I would start with fungi or diablo_rojo | |
| 20:20:01 | efried | If they don't know off the top, they're one degree from the people who do. | |
| 20:30:31 | fungi | indeed, as efried surmises, i am not authorized to provide an official answer, but https://www.openstack.org/brand/ is the page you want and mentions the e-mail address to contact | |
| 20:30:36 | fungi | umbSublime: ^ | |
| 20:30:59 | fungi | under "OpenStack Community Organizers & Non-Commercial Use" | |
| 20:31:54 | fungi | though also directs you to https://www.meetup.com/pro/osf | |
| 20:32:33 | fungi | which suggests a different contact e-mail... i'm pretty sure both of those end up in the same queue with the same folks looking at them either way | |
| 20:33:44 | fungi | the communitymgr@ address is intended more for topics related to user groups, while the events@ address is more for folks wanting to put on an openinfra days or openstack days or similar conference | |
| 20:50:56 | umbSublime | efried, fungi thanks! | |
| 20:58:49 | fungi | you're welcome | |
| 21:41:01 | umbSublime | fungi, Just to confirm that I understand correctly https://www.openstack.org/brand/, If my group is already listed in https://www.meetup.com/pro/osf , I should be good to use the web-badge logos? Should I validate with one of the MLs or is this sufficient | |
| 21:44:54 | fungi | umbSublime: that's how i interpret it, but i'm not well-versed in this so if you're in doubt you might e-mail for clarification just to be sure | |
| 21:51:21 | umbSublime | fungi, will do, thanks again! | |
| 21:52:00 | fungi | any time | |
| 21:59:36 | abaindur | Not really a nova question, but the #openstack-dib channel seems to have disappeared... | |
| 21:59:44 | abaindur | anyone know the purpose of this script? | |
| 21:59:46 | abaindur | https://github.com/openstack/diskimage-builder/commit/00d853e5fde8fe5549177bad7957be5f9699f63c | |
| 21:59:51 | abaindur | https://github.com/openstack/diskimage-builder/commit/5bed4a6d5e0e037a41931a840c4399e844631cfb | |
| 22:00:15 | abaindur | The generic dhcp-interface@.service template, and the dhcp-all-interfaces.sh script? | |
| #openstack-nova - 2020-02-19 | |||
| 01:37:10 | openstackgerrit | Luyao Zhong proposed openstack/nova master: address specific resources cleanup issue https://review.opendev.org/699148 | |
| 01:37:10 | openstackgerrit | Luyao Zhong proposed openstack/nova master: support live migration with vpmems https://review.opendev.org/687856 | |
| 02:35:52 | openstackgerrit | Ghanshyam Mann proposed openstack/nova master: Use tempest-full-py3 as base job https://review.opendev.org/708548 | |
| 04:15:21 | openstackgerrit | Merged openstack/nova master: Reject boot request for unsupported images https://review.opendev.org/707738 | |
| 08:16:27 | gibi | sean-k-mooney: thanks. I will try to set up something with a fake cyborg driver. So if you have patches to the driver then I could use it as well | |
| 08:37:18 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/train: Reject boot request for unsupported images https://review.opendev.org/708577 | |
| 08:37:48 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/stein: Reject boot request for unsupported images https://review.opendev.org/708578 | |
| 08:39:09 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Use recognized extra specs in tests https://review.opendev.org/708435 | |
| 08:39:10 | openstackgerrit | Stephen Finucane proposed openstack/nova master: api: Add framework for extra spec validation https://review.opendev.org/704643 | |
| 08:39:10 | openstackgerrit | Stephen Finucane proposed openstack/nova master: api: Add microversion 2.82, extra spec validation https://review.opendev.org/708436 | |
| 09:37:09 | lyarwood | Morning all, https://review.opendev.org/#/c/708126/ - any non-RH cores able to review this? Looking to close it out and backport if possible. | |
| 09:37:49 | lyarwood | stephenfin: ah so you're also trying to land on 2.82, is there any etiquette around multiple changes trying to land on the same microversion between M2 and M3? | |
| 09:38:02 | lyarwood | stephenfin: for context https://review.opendev.org/#/c/701430/ | |
| 09:38:44 | stephenfin | lyarwood: whoever gets there first? :) | |
| 09:38:54 | lyarwood | stephenfin: ack, may the best change win | |
| 09:39:13 | stephenfin | -2 -2 -2 -2 -2 | |
| 09:39:22 | stephenfin | sorted. | |
| 09:39:22 | lyarwood | lol | |
| 09:39:29 | lyarwood | MINE MINE MINE | |
| 09:49:27 | gibi | lyarwood: put https://review.opendev.org/#/c/708126/ into my review queue | |
| 09:49:47 | lyarwood | gibi: awesome thank you | |
| 09:58:35 | stephenfin | bauzas: Want to help me close out my oldest review today? :) https://review.opendev.org/#/c/399653/ | |
| 09:59:10 | gibi | lyarwood, stephenfin, rosmaita: I have one question regarding the release notes https://review.opendev.org/#/c/708126/3/releasenotes/notes/absolutely-non-inheritable-image-properties-85f7f304fdc20b61.yaml@19 | |
| 09:59:12 | kashyap | stephenfin: Wonder if I can borrow your rST eyes for a quick once-over for a QEMU upstream doc: https://kashyapc.fedorapeople.org/qemu_v4.2.0-1300-g5da20ed7e3_docs/system/qemu-cpu-models.html | |
| 09:59:58 | kashyap | stephenfin: Reading from the bottom, do you find the QEMU / libvirt examples with bullet / sub-bullet combo ugly? | |
| 10:00:32 | kashyap | Or "unclean", or "inelegant", or "un-rST" or ... | |
| 10:00:57 | stephenfin | gibi: Replied. It was done in change https://review.opendev.org/#/c/707738/ | |
| 10:01:37 | stephenfin | kashyap: you mean the "Syntax for configuring CPU models" section? | |
| 10:01:46 | kashyap | stephenfin: Exactly | |
| 10:02:19 | stephenfin | Yeah, I tend to refrain from bullet points in favour of definition lists or simply sub-titles | |
| 10:02:27 | stephenfin | though the former wouldn't work here | |
| 10:03:21 | stephenfin | For things like the "Important CPU features for AMD x86 hosts" section though, definitely definition lists for the flags, IMO | |
| 10:03:30 | kashyap | stephenfin: I'll turn them into sub-titles, then. | |
| 10:03:41 | gibi | stephenfin: thanks. I see now. I'm +A | |
| 10:03:50 | stephenfin | kashyap: | |
| 10:03:53 | stephenfin | definition term | |
| 10:04:00 | stephenfin | definition definition | |
| 10:04:09 | stephenfin | no newlines between the two | |
| 10:06:00 | kashyap | stephenfin: I see, okay, you suggest that for the CPU features for AMD|Intel hosts. (I'll ACK your review in the QEMU commit message, of course.) | |
| 10:09:25 | bauzas | stephenfin: oh sorry, missed your ping | |
| 10:17:51 | bauzas | stephenfin: call it a deal | |
| 10:22:00 | brinzhang | A follow up patch of bp/support-delete-on-termination-in-server-attach-volume | |
| 10:22:02 | brinzhang | https://review.opendev.org/#/c/680655/ | |
| 10:22:38 | brinzhang | Anyone can review this? It has been pushed for a long time | |
| 10:35:50 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/rocky: Reject boot request for unsupported images https://review.opendev.org/708608 | |
| 10:38:13 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/queens: Reject boot request for unsupported images https://review.opendev.org/708609 | |
| 10:50:52 | gibi | brinzhang: it would be nice to get gmann and or takashi vote on that followup as that fixes their comments | |
| 10:51:40 | brinzhang | gibi: yes, thanks | |
| 10:53:25 | brinzhang | gibi: and that update gmann and takashi's comments, so I think it would be ok now, and in PS4, they are all +1 for that :) | |
| 10:55:39 | gibi | brinzhang: I see takashi's +1 but I only see -1 from gmann. anyhow I queued that path for review on my side | |
| 10:56:22 | stephenfin | bauzas: Reviewed https://review.opendev.org/#/c/670112/ - just two changes requested and I'm happy | |
| 10:56:33 | brinzhang | gibi: yeah, thanks, I was already fixed gmann's comments, and wait for gmann check for that | |
| 10:56:59 | brinzhang | gmann: please check again https://review.opendev.org/#/c/680655/9 | |
| 11:03:06 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Avoid PlacementFixture silently swallowing kwargs https://review.opendev.org/701754 | |
| 11:05:05 | stephenfin | bauzas: Got another suppppper easy one here for you https://review.opendev.org/#/c/706466/ | |
| 11:19:13 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/stein: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708615 | |
| 11:19:41 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/rocky: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708616 | |
| 11:19:59 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/queens: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708617 | |
| 11:20:30 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/stein: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708615 | |
| 11:24:56 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/stein: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708615 | |
| 11:25:02 | lyarwood | gah, I need to repost some of these, sorry! | |
| 11:25:31 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/rocky: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708616 | |
| 11:25:47 | openstackgerrit | Lee Yarwood proposed openstack/nova stable/queens: Make RBD imagebackend flatten method idempotent https://review.opendev.org/708617 | |
| 11:25:51 | lyarwood | okay done, lyarwood-- | |
| 13:06:29 | stephenfin | lyarwood: Question for you at https://review.opendev.org/#/c/706897/2/nova/virt/images.py@53 | |
| 13:32:10 | mnaser | dansmith: the backfilling issue is confirmed to be resolved, just did it against a cloud with ~450kish records in instances table | |
| 13:32:20 | mnaser | so it didnt try to backfill the hidden value | |
| 13:58:30 | openstackgerrit | Merged openstack/nova master: Absolutely-non-inheritable image properties https://review.opendev.org/708126 | |
| 13:58:40 | openstackgerrit | Merged openstack/nova master: tests: Validate huge pages https://review.opendev.org/399653 | |
| 14:34:13 | bauzas | stephenfin: ack for the placement audit review and thanks, will look | |
| 14:36:29 | bauzas | stephenfin: and I added a better explanation in https://review.opendev.org/#/c/706466/ | |
| 14:36:38 | bauzas | that won't be in the commit msg but okay | |
| 14:44:12 | dansmith | mnaser: sweet, that's been backported and released now so hopefully nobody else will hit it | |