Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-12-05
22:42:05 mriedem how many people have already talked about adding basically encoding into traits for the lack of metadata
22:42:31 edleafe mriedem: "disabled" is a nova concept, not a placement one. If you don't want to use a scheduler filter on the nova side, then create a "disabled" agg, and add/remove compute nodes as needed, then use the upcoming negative member_of.
22:42:52 sean-k-mooney mriedem: i was talking to an onap person at one point and when i told them what placement was they ask if the could use traits to tag the compute nodes with there uuids so they could say where to boot...
22:43:20 sean-k-mooney edleafe: there are paralles in other service
22:43:26 mriedem edleafe: even using forbidden aggregates means nova needs to know to filter on that
22:43:43 mriedem which is tpatil's spec
22:43:49 mriedem https://review.openstack.org/#/c/609960/
22:44:01 mriedem which is totally complicated for me btw
22:44:06 mriedem but again, i might just be dumb
22:44:07 sean-k-mooney edleafe: you can mark a neutron dataplane as down i would be surprised if cinder does not have something similar
22:44:15 edleafe mriedem: Sure, just include that in every request, since you never want to schedule to a disabled host
22:44:43 mriedem that's what we'd do with a disabled trait as well
22:45:17 mriedem https://developer.openstack.org/api-ref/block-storage/v3/?expanded=freeze-a-cinder-backend-host-detail#freeze-a-cinder-backend-host
22:45:21 mriedem sean-k-mooney: you mean like that ^
22:45:36 sean-k-mooney yep
22:46:41 sean-k-mooney i think it woudl be common usecase that other servcies woudl use if we figured out a generic way of doing it in nova
22:46:51 sean-k-mooney * in placement
22:47:37 cfriesen how about a "resource unavailable" trait?
22:47:57 sean-k-mooney cfriesen: that is the trait we were suggesting by another name
22:48:03 cfriesen yes
22:49:20 cfriesen just trying to come up with a suitably generic name
22:50:14 sean-k-mooney edleafe: any comment on using a trait?
22:51:43 edleafe sean-k-mooney: You mean besides the design that a trait is not for status?
22:52:15 sean-k-mooney edleafe: yep beside the general object ot using placement as a metdata store / etcd standin
22:52:34 edleafe sean-k-mooney: :)
22:54:38 mriedem here are some sufficiently out of band proxy via nova via placement things you guys will probably all like then https://review.openstack.org/#/c/552190/ https://review.openstack.org/#/c/549067/
22:57:34 sean-k-mooney vmware are aware that openstack in not vspher/vcloud right ...
22:58:57 sean-k-mooney the vmware-vm-groups sound kindof like the tenant aggreate affintiy usecase
22:59:11 sean-k-mooney oh actully
22:59:49 sean-k-mooney ok the usecase is compulte different to what i was expecte form the intro and problem descripteion
23:27:57 sean-k-mooney does blazer not use its specs repos
23:30:49 sean-k-mooney its in tree never mind
23:40:10 tssurya mriedem: we have filed the bug already regarding placement not knowing about disabled computes: https://bugs.launchpad.net/nova/+bug/1805984
23:40:10 openstack Launchpad bug 1805984 in OpenStack Compute (nova) "Placement is not aware of disable compute nodes" [Undecided,New]
23:41:14 sean-k-mooney tssurya: its not really a bug its a new feature that shoudl live in nova
23:41:26 sean-k-mooney well not quite
23:41:44 sean-k-mooney its not currently expected that placement would know
23:41:55 sean-k-mooney so its no a bug in that sence
23:49:44 tssurya sean-k-mooney: right agreed its not a bug since it was decided as a won't fix on the placement side (https://bugs.launchpad.net/nova/+bug/1708958)
23:49:44 openstack Launchpad bug 1708958 in OpenStack Compute (nova) "disabling a compute service does not disable the resource provider" [Wishlist,Won't fix]
23:50:19 tssurya but mriedem wanted a bug (was replying to his ML post)
23:50:25 sean-k-mooney tssurya: i set it to triage and wish list with the suggestion of converting to a spec or specless blueprint
23:50:28 tssurya to just track the issue
23:50:58 sean-k-mooney tssurya: if it was neutron i would have just set the RFE tag on the bug but nova does not use that
23:51:24 sean-k-mooney its definetly an edge case an i can see it causeing issues for larger deployments
23:52:17 sean-k-mooney did you see the conversation we had on this an hour ago
23:56:08 tssurya sean-k-mooney: was just scrolling back up to read it :D
23:56:25 tssurya I can see a couple of plausible solutions being proposed
23:56:42 sean-k-mooney yep there are 2 or 3 options
23:57:11 tssurya probably the one where reserved=total + disabling periodic updates on disabled computes to avoid overwrite is the better option
23:57:23 sean-k-mooney it looks like we should be able to come up with somethign
23:57:27 tssurya considering adding another periodic task just for this might be a overhead
23:57:32 sean-k-mooney tssurya: im not sure about that
23:58:03 sean-k-mooney i guess we will see the traits approch or using a disabled aggreate seam like a clean solution
23:58:43 tssurya oh disabled aggregates! didn't see that part yet, reading now
23:59:53 sean-k-mooney tssurya: well a disable aggreage is just an aggrage that we "nova" adds host that are down too and we jsut use the not member_of proposal to avoid
#openstack-nova - 2018-12-06
00:00:49 sean-k-mooney specifcially use this feature https://review.openstack.org/#/c/603352/
00:03:33 tssurya sean-k-mooney: yea thanks, did read the full spec yet but got the idea
00:04:19 tssurya so it would be something like adding/removing to an aggregate when we disable/enable the service I guess
00:05:44 tssurya and the fourth solution was traits I see
00:05:45 sean-k-mooney yep and we then jsut alway include member_of=!<uuid of disbaled aggreage>
00:05:51 sean-k-mooney in the placement request
00:06:06 tssurya sean-k-mooney: yep makes sense
00:06:21 sean-k-mooney we can use a uuid5 to generate a sable uuid for the aggragte but other services can create there own
00:07:58 tssurya yea, as long as the aggregate doesn't get stale (as in disruption during enable which fails to remove it from the aggregate)/we keep it in sync should work well.
00:08:12 tssurya which is a corner case
00:08:38 sean-k-mooney tssurya: well we could take care of that with a periodic task to fix it
00:09:01 sean-k-mooney e.g we udate it imendiatly form the api but heal it later if the update got lost
00:09:49 tssurya sean-k-mooney: after looking at the RT's periodic task, I am so down with periodic tasks as of now :D because of the overhead when having several computes
00:10:07 tssurya but yea as long as the interval is not so frequent, should be ok
00:10:17 sean-k-mooney haha ya but this would be on i guess the conductor
00:10:29 sean-k-mooney or supper conductor
00:11:17 sean-k-mooney the node status is in i think both the api and cell db so we dont need to run this on every compute node
00:11:42 tssurya node status is only in the cell db's
00:11:57 sean-k-mooney ok so but it could run on the cell conductor then
00:12:14 tssurya yea could be
00:12:40 sean-k-mooney an you could set the interval to a week if you wanted and this time supprot disabling it right out of the box by setting to 0
00:13:06 tssurya but not sure if its an upcall when updating the api aggregate table frm the cell conductor but yea these are implementation details
00:13:11 sean-k-mooney if you trust it to not get out of sync our you will fix it later then no need to run it
00:13:50 sean-k-mooney tssurya: oh im talking about placemetn aggreagtes not nova host aggrats by the way
00:14:45 tssurya sean-k-mooney: oh okay!
00:15:05 tssurya since you saud "nova" adds hosts, got confused
00:15:34 sean-k-mooney ya i should have said nova update the placment aggragte with the compute node RP uuid
00:16:06 tssurya right yea
01:28:47 jaypipes cfriesen: you have awoken the kraken. but unfortunately, the kraken is too tired from playing tennis to fight tonight :) so, will chat tomorrow about it.
02:23:55 openstackgerrit Jack Ding proposed openstack/nova master: Preserve UEFI NVRAM variable store https://review.openstack.org/621646
02:33:19 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
02:44:30 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
02:46:48 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
02:51:53 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
03:11:01 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
03:26:36 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Handle tags in _bury_in_cell0 https://review.openstack.org/621856
03:43:55 openstackgerrit Takashi NATSUME proposed openstack/nova stable/rocky: Add a bug tag for nova doc https://review.openstack.org/623130
04:16:45 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
04:52:18 openstackgerrit Guo Jingyu proposed openstack/nova-specs master: Proposal for a safer noVNC console with password authentication https://review.openstack.org/623120
06:58:42 openstackgerrit Takashi NATSUME proposed openstack/nova master: api-ref: Body verification for the lock action https://review.openstack.org/622835
07:00:32 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Handle tags in _bury_in_cell0 https://review.openstack.org/621856
07:41:25 openstackgerrit Merged openstack/nova master: Update mailinglist from dev to discuss https://review.openstack.org/621827
07:41:36 openstackgerrit Merged openstack/nova master: modify the avaliable link https://review.openstack.org/616905
09:16:53 gibi stephenfin: regarding shorted notification payload, would you like to see the samples stored in nova sorted only or also the json emitted on the message bus?

Earlier   Later