Earlier  
Posted Nick Remark
#openstack-nova - 2023-04-11
16:42:56 sean-k-mooney so in the past i can see the usecase
16:42:59 bauzas it was obviously pre-traits
16:43:04 sean-k-mooney ya
16:43:23 sean-k-mooney anyway at least we know the semantic of "it shoudl be sortable"
16:43:30 sean-k-mooney have already been depened on
16:43:32 bauzas yeah, but instead of pinning a specific virt version, we should absract this into abstract versions
16:43:38 sean-k-mooney so that makes the weigher simpler
16:43:44 bauzas semantic versioning I mean
16:44:06 sean-k-mooney ya well to do that we woudl need to change this form an int to string
16:44:08 sean-k-mooney to model that
16:44:09 bauzas but yeah, for your weigher, it just makes the paperwork easy
16:44:19 sean-k-mooney but i dont want to touch that now
16:44:26 sean-k-mooney we can in the future if it makes sense too
16:44:36 bauzas sean-k-mooney: yup, and ideally it should obfuscate the hypervisor specific version
16:44:45 sean-k-mooney i will go do the paperwork and let you knwo when its donw
16:44:56 bauzas cool, I'll approve it once you ping me
16:45:16 bauzas and the weigher seems to me an easy peasy given the existing
16:45:30 bauzas the code change itself should be simple to review :)
16:46:39 bauzas anyway, done for today
17:06:20 sean-k-mooney bauzas: when you have time https://blueprints.launchpad.net/nova/+spec/weigh-host-by-hypervisor-version
17:07:47 bauzas sean-k-mooney: done
17:08:06 sean-k-mooney thanks
17:49:29 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (db) https://review.opendev.org/c/openstack/nova/+/831193
17:49:29 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (objects) https://review.opendev.org/c/openstack/nova/+/839401
17:49:30 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194
17:49:30 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part) https://review.opendev.org/c/openstack/nova/+/833090
17:49:31 opendevreview ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (api) https://review.opendev.org/c/openstack/nova/+/836830
17:49:31 opendevreview ribaudr proposed openstack/nova master: Check shares support https://review.opendev.org/c/openstack/nova/+/850499
17:49:32 opendevreview ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500
17:49:33 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501
17:49:33 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028
17:49:35 opendevreview ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029
17:49:35 opendevreview ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/852085
17:49:37 opendevreview ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086
17:49:37 opendevreview ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087
17:49:39 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/854823
17:49:39 opendevreview ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/854824
17:49:41 opendevreview ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282
17:49:41 opendevreview ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283
17:49:43 opendevreview ribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/860284
17:49:43 opendevreview ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860285
17:49:45 opendevreview ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286
17:49:45 opendevreview ribaudr proposed openstack/nova master: Support rescuing an instance with shares (driver part) https://review.opendev.org/c/openstack/nova/+/860287
17:49:47 opendevreview ribaudr proposed openstack/nova master: Support rescuing an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860288
17:49:47 opendevreview ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642
17:49:49 opendevreview ribaudr proposed openstack/nova master: The purpose of this patch is to ensure that, in the event of a compute reboot, shares associated with instances are mounted successfully on the compute host during the service initialization process. https://review.opendev.org/c/openstack/nova/+/880075
18:54:40 dansmith bauzas: I totally missed this, but apparently we should be working to remove hyperv: https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031044.html
19:03:20 sean-k-mooney oh ya
19:03:24 sean-k-mooney i rememebr seeing that
19:04:07 sean-k-mooney so ya we proably should deprecate it this cycle
19:04:12 sean-k-mooney and remove in C
19:04:29 sean-k-mooney ... or D with the new lifecycle
19:04:45 sean-k-mooney that kind of sucks as it proably should have been deprecated in A
19:05:02 gmann if os-win goes away in this cyle then we might need to just remove it ?
19:05:13 sean-k-mooney yep
19:05:27 sean-k-mooney can we retoactivly declare it deprecated for Antelope
19:05:37 sean-k-mooney assuming that happens
19:05:42 gmann humm
19:06:48 sean-k-mooney either way we shoudl declare it deprecated in bobcat
19:06:57 sean-k-mooney and see if we have issues with os-win
19:08:53 bauzas dansmith : we can send a deprecation signal by Bobcat if you want but continue to say it then in C
19:10:11 gmann even TC is reaching out operators if anyone using/have window based customer and can maintain the project/project-deps and will take final call on retirement of os-win in June event or so
19:10:58 dansmith IIRC, we already said that vmware was abandonware right?
19:11:05 gmann but from nova perspective, if we do not/have not seen much interest in hyperV then deprecating ASAP might be good. and if os-win retirement happen in this cycle then removal also in B only
19:11:12 dansmith so I feel like we could do the same for hyperv for the time being and then remove it according to our schedule
19:11:23 bauzas dansmith: yup we deprecated it IIRC
19:11:25 gmann yeah
19:11:53 dansmith yeah, so no need to freak out and yank it early, IMHO, just mark as deprecated, even if it can't run or fails with os-win problems and then we can remove it in D
19:12:13 dansmith the thing that concerns me the most however is the user survey showing 2% of users are using it
19:12:36 dansmith which, deprecation aside, also worries me :)
19:14:00 sean-k-mooney i woudl hope that existing deployment can continue to use the last release of os-win
19:14:14 gmann we can un-deprecate it if anyone come and maintain it. but I am worried that they might see this deprecation way after few cycle when they upgrade it to B and we might hve removed it by then
19:14:17 sean-k-mooney the issue will be with new python releases or its deps
19:14:59 sean-k-mooney well we would not remove it until D
19:15:14 sean-k-mooney unless we are forced to earlier
19:15:17 gmann that is question on how we want to do for supported stable branch, retirement means it goes away from supported releases also and what to tell on hyperV on stable is another challenges
19:15:36 sean-k-mooney we dont test hyperv in the first party ci
19:15:57 gmann yeah
19:15:59 sean-k-mooney so it really only affect stable branches if we fix a bug and want to backport it
19:16:46 gmann yeah, in case of stable broken on any fixes or so
19:17:12 gmann os-win stable is broken and then no way to fix it
19:18:28 gmann but deprecating it now is best we can do
19:22:56 gmann bauzas: dansmith: vmware driver is un-deprecated since victoria https://review.opendev.org/c/openstack/nova/+/742407
19:23:08 sean-k-mooney gmann: we redeprecated it again
19:23:19 dansmith lol
19:23:24 dansmith it has been so many times
19:23:36 gmann oh
19:24:24 gmann where is the latest deprecation ?
19:24:39 sean-k-mooney maybe im mistaken but i tought we did it in yoga?
19:24:58 dansmith that would have been the next release
19:26:21 gmann I cannot see if we re-deprecated after 742407
19:26:45 sean-k-mooney hum well ciwatch.mmedvede.net/project?project=nova&time=7+days seams to nolonger be working
19:26:58 sean-k-mooney has the third party ci been maintianed
19:27:47 sean-k-mooney http://207.189.188.190/logs/
19:28:12 sean-k-mooney im not seeing anything
19:28:47 sean-k-mooney https://review.opendev.org/q/commentby:vmwareminesweeper
19:28:53 sean-k-mooney ok so tehre are comments i gues
19:29:53 sean-k-mooney althouhg im not sure that is recent
19:31:26 gmann yeah, it seems it is not deprecated, I can see a few changes merged also in driver (last merged in Apr 29, 2022) so it is maintained ? :)
19:35:04 sean-k-mooney i think no

Earlier   Later