Earlier  
Posted Nick Remark
#openstack-nova - 2022-04-04
16:26:08 sean-k-mooney sure
16:29:34 bauzas sean-k-mooney: I don't disagree, this is tribal knowledge
16:29:47 bauzas hence why I'd have appreciated some automatic zuul reply with link
16:29:59 sean-k-mooney yes that is why i suggested doing that
16:30:19 bauzas sean-k-mooney: I think I expressed this beforehand :p
16:30:39 bauzas anyway, if there is a consensus, we should see how to do this
16:30:47 sean-k-mooney i know how to do this
16:30:49 sean-k-mooney its trivial
16:31:00 bauzas not for me :)
16:31:13 bauzas but I'll review you :p
16:31:15 sean-k-mooney update this https://github.com/openstack/project-config/blob/master/zuul.d/pipelines.yaml#L10-L12=
16:31:36 sean-k-mooney it currently links to the section that contians the guidence on when to recheck
16:32:07 sean-k-mooney this is part of the pipeline config so it affect all jobs in the pipeline
16:32:22 sean-k-mooney so it woudl be for all projects
16:32:49 sean-k-mooney we likely and update that to be more explcit and say do not recheck without first reading ....
#openstack-nova - 2022-04-05
05:36:37 opendevreview melanie witt proposed openstack/nova master: block_device: Add DriverImageBlockDevice to block_device_info https://review.opendev.org/c/openstack/nova/+/826527
05:36:37 opendevreview melanie witt proposed openstack/nova master: scheduler: Add an ephemeral encryption pre filter https://review.opendev.org/c/openstack/nova/+/760456
05:36:38 opendevreview melanie witt proposed openstack/nova master: virt: Add block_device_info helper to find encrypted disks https://review.opendev.org/c/openstack/nova/+/826529
05:36:38 opendevreview melanie witt proposed openstack/nova master: block_device: Add encryption attributes to image and ephemeral disks https://review.opendev.org/c/openstack/nova/+/826528
05:36:39 opendevreview melanie witt proposed openstack/nova master: imagebackend: Add disk_info_mapping as an optional attribute of Image https://review.opendev.org/c/openstack/nova/+/826530
05:36:39 opendevreview melanie witt proposed openstack/nova master: blockinfo: Add encryption details to the disk_info mappings when provided https://review.opendev.org/c/openstack/nova/+/772272
05:36:40 opendevreview melanie witt proposed openstack/nova master: privsep: Move qemu-img create calls under nova.privsep.qemu https://review.opendev.org/c/openstack/nova/+/826750
05:36:41 opendevreview melanie witt proposed openstack/nova master: privsep: Add encryption support to qemu-img create command https://review.opendev.org/c/openstack/nova/+/826752
05:36:41 opendevreview melanie witt proposed openstack/nova master: privsep: Return QemuImgInfo objects from qemu-img info calls https://review.opendev.org/c/openstack/nova/+/826751
06:45:01 gibi good morning nova
09:27:41 Uggla Hello guys, dumb question. Is there a preferred style syntax for string. I mean any preference for 'string' or "string" ?
09:31:04 opendevreview Wenping Song proposed openstack/nova-specs master: Usage of new trait of OWNER_NOVA https://review.opendev.org/c/openstack/nova-specs/+/836583
09:34:09 opendevreview Wenping Song proposed openstack/nova-specs master: Usage of new trait of OWNER_NOVA https://review.opendev.org/c/openstack/nova-specs/+/836583
09:38:36 gibi Uggla: no hard rule exists. I try to follow the style from the code around my edit (if that is consistent :D)
09:41:20 sean-k-mooney gibi: or we can have pre-comit do it
09:41:31 gibi yeah
09:41:31 sean-k-mooney there is a rule that will make them all ''
09:41:54 gibi but black would change everything so we would loose git blame and easy backport
09:41:54 sean-k-mooney i used it on one of my other repos personaly i prefer ""
09:42:14 gibi I use black for personal projects too
09:42:15 sean-k-mooney but i prefer machine enforced style more
09:42:21 sean-k-mooney oh i dont use black
09:42:31 sean-k-mooney i just use pre-commit + autopep8
09:42:36 gibi ahh autopep8
09:42:49 gibi can it only format the current diff?
09:42:57 sean-k-mooney i was suggesting we could use pre-commit to normalise the strings and have that run in the pep8 target
09:43:01 sean-k-mooney if we wanted too
09:43:16 sean-k-mooney yes
09:43:29 gibi then I'm supportive
09:43:35 gibi I use https://github.com/gibizer/blacken_selection in my IDE
09:43:48 sean-k-mooney but we already did the gloabl update for autopep8 but pre-commit only runs on the current diff by default
09:46:32 Uggla sean-k-mooney, is autopep8 will be "smart" enough to not broke strings like: "Share '0000:1222:1144:7777'" ? (strings where you want to display quotes).
09:47:53 sean-k-mooney autopep8 wont change this we would have to use a pre-commit hook. autopep8 is conservitive and tries to only enforce pep8 rules and sting format is not one of them
09:48:05 sean-k-mooney so we shoudl just test the hook.
09:48:17 sean-k-mooney https://pre-commit.com/hooks.html
09:48:24 sean-k-mooney double-quote-string-fixer
09:48:34 sean-k-mooney is the one i use in other repo
09:54:22 Uggla I have question regarding https://specs.openstack.org/openstack/nova-specs/specs/yoga/approved/libvirt-virtiofs-attach-manila-shares.html
09:55:18 Uggla Is there a reason to have an "attachmentId" ? Not saying that because I forget it... :)
09:58:33 Uggla this field is not used by the api.
10:02:29 sean-k-mooney yes
10:02:42 sean-k-mooney so a volume can have multiple attachments when its moving
10:03:19 sean-k-mooney althoguh this is a manilla share
10:03:28 sean-k-mooney so not entirly sure
10:03:35 sean-k-mooney i woudl ahve to read the spec again
10:05:49 sean-k-mooney Uggla so attachment id is the interanl id filed in the share_mappings table https://specs.openstack.org/openstack/nova-specs/specs/yoga/approved/libvirt-virtiofs-attach-manila-shares.html#data-model-impact
10:07:37 sean-k-mooney i think the intent is to allow the share to be assoated with teh vim but with differe exprot locations during move operations
10:08:03 sean-k-mooney but im not certin
10:08:23 Uggla sean-k-mooney, each line of the table is unique by the couple instance_uuid, share_id
10:08:50 sean-k-mooney i think attachment id was ment to be in the unique constraint
10:09:03 sean-k-mooney lyarwood: ^ if you are around
10:09:18 sean-k-mooney lyarwood: do you remember why we have attachment id
10:11:26 sean-k-mooney if the id filed is just intended as a primary key it should be an integer not a uuid so the fact its listed as a uuid is what is making me belive it for move operations
10:11:52 Uggla sean-k-mooney, I think I can add it easily, it is just to understand the purpose of it.
10:11:53 sean-k-mooney so that we can create a new attachmet with a different export location for the destination.
10:12:02 sean-k-mooney yep
10:13:11 Uggla let's see id lyarwood can answer. If not I'll try to ping him.
10:13:59 sean-k-mooney have you already implemented move operations
10:14:37 sean-k-mooney i dont think you will need it before then
10:14:52 sean-k-mooney the other suecases is allowign the share to be mounted to the vm multiple times
10:15:46 lyarwood yeah I was just typing that
10:15:54 lyarwood I think this was more to do with the multi attach case of a share
10:16:07 Uggla sean-k-mooney, with this first version --> Support for move operations once a share is attached will also not be covered by this spec
10:16:44 Uggla sean-k-mooney, ny requests to shelve, evacuate, resize, cold migrate or live migrate an instance with a share attached will be rejected for the time being
10:16:47 lyarwood that and debugging issues, I've always found it easier to use the underlying bdm id when tracing volume attachment issues
10:18:21 Uggla lyarwood, ok make sens.
10:18:58 Uggla lyarwood, thx
10:25:51 opendevreview Stephen Finucane proposed openstack/nova master: hacking: Prevent use of six https://review.opendev.org/c/openstack/nova/+/836588
10:25:59 stephenfin sean-k-mooney: bauzas: ^
10:33:06 sean-k-mooney stephenfin: care to add a pre-commit check? i guess that should be picked up by the flake8 check
10:33:17 sean-k-mooney so i guess it already is there
10:33:38 sean-k-mooney have you tested that locally to confirm one way or another?
10:33:51 sean-k-mooney otherwise ya that looks like a good idea to me
10:50:10 gibi Uggla: left a bunch of comments / questions on https://review.opendev.org/c/openstack/nova-specs/+/833669 (manila shares spec). Let me know if something of them are unclear
11:14:46 opendevreview Stephen Finucane proposed openstack/nova master: Sync rootwrap.conf from oslo.rootwrap https://review.opendev.org/c/openstack/nova/+/823229
11:19:23 sean-k-mooney stephenfin: actully i need to add that to the cinder ptg
11:19:37 sean-k-mooney stephenfin:we only have rootwrap because of os-brick
11:19:41 sean-k-mooney nova does not use it directly
11:19:48 sean-k-mooney so i would like to move ti to os-brick
11:20:13 sean-k-mooney that or we could finsih porting os-brick to privsep so that it does not need it either
11:22:09 stephenfin makes sense
11:25:02 sean-k-mooney i pinged the cinder folks to see if i can get a slot to chat to them about it in there ptg adgenda
11:25:18 sean-k-mooney it looks pretty full so maybe we can do it in ours if they can have people join
11:57:37 sean-k-mooney stephenfin: ping me when you have time to review my comments on the hacking change https://review.opendev.org/c/openstack/nova/+/836588
11:57:53 sean-k-mooney ill be afk for the next 30 mins or so but happy to look at that again when im back

Earlier   Later