Earlier  
Posted Nick Remark
#openstack-nova - 2018-07-11
03:19:57 yikun gmann: sure, thanks for your help, and I will change api from nest to flat fist. and if we decided change policy_* I will append the change. :)
04:05:23 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Compute: add support to abort queued live migration https://review.openstack.org/568542
04:18:11 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Fix ServerMigrationSampleJsonTestsV2_24 to use its own sample file https://review.openstack.org/581562
04:22:49 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object https://review.openstack.org/563401
04:22:50 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Change the ServerGroupAntiAffinityFilter to adapt to new policy https://review.openstack.org/571166
04:22:51 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model https://review.openstack.org/571465
04:22:52 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Microversion 2.64 - Use new format policy in server group https://review.openstack.org/567534
04:29:13 gmann yikun: sounds good. we can get the consensus on patch first and then update spec for process.
05:11:35 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Add policy field to ServerGroup notification object https://review.openstack.org/563401
05:11:36 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Change the ServerGroupAntiAffinityFilter to adapt to new policy https://review.openstack.org/571166
05:11:37 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Adapt _validate_instance_group_policy to new policy model https://review.openstack.org/571465
05:11:38 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: Microversion 2.64 - Use new format policy in server group https://review.openstack.org/567534
05:28:03 openstackgerrit Merged openstack/nova master: Update some placement docs to reflect modern times https://review.openstack.org/581151
05:52:22 stelucz Hi, I just found in our cluster one nova aggregate with one host. It was probably created by temptest/benchmark in the past. Is it safe to delete this aggregate? or it will have some impact on running VMs at host?
05:59:58 gmann API office hour time
06:00:01 gmann #startmeeting nova api
06:00:02 openstack Meeting started Wed Jul 11 06:00:01 2018 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
06:00:03 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
06:00:05 openstack The meeting name has been set to 'nova_api'
06:00:11 gmann PING List: gmann, alex_xu
06:00:14 gmann who all here today
06:00:15 alex_xu o/
06:00:19 gmann alex_xu: hi
06:00:29 alex_xu gmann: good afternoon
06:00:38 gmann good afternoon
06:01:00 jichen o/
06:01:03 Kevin_Zheng o/
06:01:41 gmann jichen: Kevin_Zheng : hi
06:01:46 gmann let's start
06:01:59 gmann #link https://wiki.openstack.org/wiki/Meetings/NovaAPI#Agenda_for_next_Office_hours
06:02:11 gmann ^^ generic agenda for this office hour
06:02:15 yikun o/
06:02:22 gmann yikun: hi
06:02:35 gmann #topic Priorities
06:02:45 gmann #link https://etherpad.openstack.org/p/rocky-nova-priorities-tracking
06:02:57 gmann we will go through the API section in above etherpad
06:03:06 jichen ok
06:03:17 gmann line 57
06:03:33 gmann 1. Servers Ips non-unique network names
06:03:54 gmann spec update is merged last week. #link https://review.openstack.org/#/c/558125/
06:05:27 gmann Maciej Kucia started code also but month back
06:06:07 jichen_ Is there code patch ? I only saw a doc patch
06:06:17 gmann i do not irc nick and changes should be straight forwards. if no updated since week, may be i can update the code for this BP
06:06:38 gmann yea, that patch only. in same patch code needs to be updated.
06:06:57 gmann i will check with Maciej about progress.
06:07:04 jichen_ ok, got it
06:07:04 gmann 2.Abort live migration in queued state:
06:07:41 gmann this is from Kevin_Zheng and i think good to review from us. i have added this in my today list.
06:08:23 Kevin_Zheng I got a question about this one
06:08:28 Kevin_Zheng API related
06:08:28 gmann Kevin_Zheng: anything you want to discuss on this then review
06:08:37 gmann yeah go head
06:08:49 Kevin_Zheng in the patch, I have a rpc version check
06:09:18 Kevin_Zheng like if the compute can do 5.1 then it can abort migration in queued status
06:09:23 Kevin_Zheng if cannot do 5.1
06:09:33 Kevin_Zheng then I trough an exception
06:09:50 Kevin_Zheng my question is, should I mention that compute is not new enoguh?
06:09:53 Kevin_Zheng enough
06:10:13 gmann you mean this -
06:10:15 gmann #link https://review.openstack.org/#/c/568542
06:10:18 Kevin_Zheng will that be too much admin details for normal user?
06:10:57 Kevin_Zheng yeah
06:11:10 Kevin_Zheng if it is like what I did in the current patch
06:11:57 Kevin_Zheng it seems a little wierd, as an user I requested 2.64 and then nova replied to me that migration is not in correct status
06:11:58 alex_xu I think we have some example in the before
06:12:23 Kevin_Zheng seems not correct with the mircorversion
06:12:34 gmann yeah i am searching for that
06:12:50 Kevin_Zheng Yeah, we have some, yikun is also working on one with this kind of server version check
06:13:18 Kevin_Zheng just wondering if it is good to let normal user know that some of the node is not new enough
06:13:39 yikun ^ https://review.openstack.org/#/c/567534/30/nova/api/openstack/compute/server_groups.py@190
06:13:40 gmann this one -
06:13:42 gmann #link https://github.com/openstack/nova/blob/d3fa585f5e2d11a91ee62744a0cf0c78921a47e4/nova/compute/api.py#L1033
06:14:24 gmann you can add new exception like this - #link https://github.com/openstack/nova/blob/c8b93fa2493dce82ef4c0b1e7a503ba9b81c2e86/nova/exception.py#L2294
06:14:55 Kevin_Zheng hmm that seems better
06:15:21 Kevin_Zheng Yikun, maybe you should do something similar?
06:15:23 yikun yeah, so we should NOT expose something like "all compute services needs upgrade to Rocky"
06:15:27 gmann Kevin_Zheng: we will tell node is old we will just say this feature not supported so that user will contact admin for details
06:15:28 Kevin_Zheng yeah
06:15:34 alex_xu also this one #link https://github.com/openstack/nova/blob/stable/ocata/nova/compute/rpcapi.py#L1114
06:15:53 Kevin_Zheng maybe the version thing should be appare in the log?
06:15:57 gmann yeah crash dump one alaos
06:16:07 gmann Kevin_Zheng: i think no.
06:17:07 Kevin_Zheng why not, seems better for operators
06:17:52 jichen yes, logs are only viewable to operators...
06:17:55 alex_xu why we didn't check service version instead of rpc version?
06:18:09 Kevin_Zheng they are different cases
06:18:17 gmann for which case
06:18:20 Kevin_Zheng yikun's case we check service version
06:18:27 Kevin_Zheng my case check for rpc version
06:18:40 Kevin_Zheng for log, I mean both version
06:18:44 Kevin_Zheng both case
06:19:35 gmann but operator knows features support from reno and microversions info.
06:19:47 alex_xu Kevin_Zheng: I mean your case can be done by the service version check also?
06:21:39 Kevin_Zheng yeah, but this way is similar, I also did some negotiation in rpc
06:21:43 gmann alex_xu: you mean in compute.api.py only like thrust certificate
06:22:02 alex_xu gmann: yea
06:22:34 gmann ok, that seems better for me too
06:22:41 alex_xu we can stop the API early, and it is more clear in the code
06:22:45 Kevin_Zheng I don't think so
06:23:05 Kevin_Zheng it is not the same with the certificate one

Earlier   Later