Earlier  
Posted Nick Remark
#openstack-nova - 2018-07-25
07:03:10 gmann alex_xu: i found some context of doing it intentionally or say as per old behaviour
07:03:14 gmann alex_xu: #link https://review.openstack.org/#/c/446239/3/nova/tests/unit/test_quota.py@1031
07:05:38 alex_xu gmann: interesting
07:07:44 gmann may be we can fix that per user but sot sure we can fix it easily as melwitt metnioned on that reivew
07:07:59 alex_xu gmann: it sounds make sense to show keypair for specific user, but for the server_group_member we really have no way to express that
07:08:26 gmann yeah that per server group
07:09:18 alex_xu gmann: then do we need microversion :)
07:09:28 gmann humm
07:10:32 gmann it change the behaviour but not sure we need microversion as it would not cause any backward incompatibility in iterface usage
07:11:20 alex_xu gmann: but there is no way for the user to know whether the usage is valid in the deployment
07:12:02 sean-k-mooney mriedem: melwitt regarding the noop plugin im just looking into it now. it looks related to how we dynamicaly load plugins here https://github.com/openstack/os-vif/blob/master/os_vif/__init__.py#L41-L49
07:12:16 sean-k-mooney mriedem: melwitt ill take a look at it now
07:12:22 gmann yeah, that's true.
07:13:43 gmann microversion bump can be done but then it cannot be backported if we want to.
07:14:17 alex_xu gmann: we have user quota since long time ago, not sure whether is it always 0
07:14:42 alex_xu gmann: this bug is newton
07:15:19 alex_xu gmann: or just send this question to maillist to get wider agreement
07:15:32 alex_xu I'm really not good at answering the microversion question
07:16:13 gmann alex_xu: you mean to ask for microversion bump or to fix the bug for showing the key_pair usage per suer ?
07:17:02 alex_xu gmann: both I guess since we already ask question, at least it make sense to show user qutoa for keypair for me
07:17:44 gmann alex_xu: ok.
07:18:18 gmann i can send the ML, tough i do not have full context of quota calculation background
07:18:29 gmann s/tough/though
07:18:54 alex_xu I can help that
07:20:13 gmann alex_xu: thanks,
07:20:29 gmann alex_xu: you mean you can send mail or reply on the query i sent?
07:21:13 alex_xu gmann: ethier works for me :)
07:22:04 alex_xu s/ethier/either/
07:22:20 gmann alex_xu: cool, I will bring the query on ML and then you can respond. thanks
07:22:27 alex_xu gmann: got it, thanks
07:22:30 gmann anything else on bug or we move next
07:22:45 gmann #topic Open Discussion
07:23:00 vishakha gmann, should I look for another?
07:23:20 gmann vishakha: sorry did not conclude that. we are bringing your question on ML and their you can see the discussion or respond
07:23:43 vishakha gmann, alex_xu : ok thanks
07:23:56 gmann vishakha: yeah, if you can help on other bug also it will be great. if you are looking for more then you can choose from API one
07:24:11 gmann binator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search&orderby=-importance&start=0
07:24:11 gmann https://bugs.launchpad.net/nova/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=api%20api-ref&field.tags_com
07:24:11 gmann vishakha: #link
07:24:16 gmann opps
07:24:22 vishakha gmann, yes sure
07:24:32 gmann anything else to discuss or we close the office hour
07:25:01 gmann let's close then.
07:25:04 vishakha gmann, just wanted you to review https://review.openstack.org/#/c/580271/
07:25:05 Kevin_Zheng me
07:25:12 gmann Kevin_Zheng: go ahead
07:25:30 Kevin_Zheng Our product team found out a strange API behaviour
07:25:31 Kevin_Zheng https://developer.openstack.org/api-ref/compute/#get-availability-zone-information
07:25:36 gmann vishakha: sure, ll add in my list
07:25:41 Kevin_Zheng there is a hosts field
07:25:55 Kevin_Zheng and it will always be "null"
07:26:02 Kevin_Zheng it was just added here:
07:26:14 Kevin_Zheng https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/availability_zone.py#L42
07:26:26 Kevin_Zheng so any particular reason why it is added?
07:26:34 Kevin_Zheng Or should we just remove it
07:27:53 gmann Kevin_Zheng: may be for consistency for GET and GET detail API
07:28:05 gmann Kevin_Zheng: Detail give the host information
07:28:09 vishakha gmann, Thanks :)
07:28:19 Kevin_Zheng but do we need this kind of consistency?
07:28:23 Kevin_Zheng looks strange
07:28:33 gmann #link https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/availability_zone.py#L91
07:28:42 Kevin_Zheng we do not have this kind of consistency in list server and list server details
07:29:17 Kevin_Zheng yeah, I know that, just think this is not necessary
07:29:22 gmann ohk it is not get particular AZ
07:29:49 gmann we can remove but need microversion. what harm in keeping it ?
07:30:15 Kevin_Zheng no harm, just found it strange
07:30:21 Kevin_Zheng and the customer asks
07:30:37 Kevin_Zheng so we have to tell them why it is like that all the time
07:30:48 gmann i remember we kept it for v2.1 for compatibility
07:31:12 Kevin_Zheng So might be good to remove it in S?
07:31:18 Kevin_Zheng with microversion
07:32:01 gmann Kevin_Zheng: ok. i can note down this on API improvement etherpad (which i need to create yet)and then we can decide if we can fix this with other consistent changes
07:32:15 Kevin_Zheng yeah cool
07:32:26 gmann microversion alone for this seems little overhead for me
07:32:39 Kevin_Zheng yeah
07:33:04 gmann Kevin_Zheng: thanks for finding and reporting this.
07:33:29 Kevin_Zheng NP, just solving our problems
07:33:44 gmann anything else to discuss
07:34:29 gmann ok let's close then
07:34:35 gmann thanks everyone for joining
07:34:39 gmann #endmeeting
07:34:40 openstackgerrit Lucian Petrut proposed openstack/nova master: Hyper-V + OVS: plug vifs before starting VMs https://review.openstack.org/585661
07:34:42 openstack Meeting ended Wed Jul 25 07:34:39 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
07:34:43 openstack Minutes: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-07-25-06.02.html
07:34:44 openstack Minutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-07-25-06.02.txt
07:34:45 openstack Log: http://eavesdrop.openstack.org/meetings/nova_api/2018/nova_api.2018-07-25-06.02.log.html
07:34:50 Kevin_Zheng gmann a test related question
07:34:59 gmann Kevin_Zheng: yup
07:35:12 Kevin_Zheng https://review.openstack.org/#/c/583927/ I'm working on this
07:35:39 Kevin_Zheng and Matt asked me to use a real mc backend instead of mock
07:36:01 Kevin_Zheng Seems like it need to have some set_up besides just override the configs
07:36:20 gmann checking
07:36:22 Kevin_Zheng I have no clue how do it, do you have this kind of experience/
07:36:24 Kevin_Zheng ?
07:36:34 Kevin_Zheng Thanks
07:39:17 gmann i have not done yet but trying to look
07:41:20 gmann Kevin_Zheng: it did not work with dogpile.cache.memory also ?
07:41:50 gibi mriedem: No worries, I didn't planned to have a meeting this week (either) http://lists.openstack.org/pipermail/openstack-dev/2018-July/132410.html
07:42:13 Kevin_Zheng yeah, seems the backend is not working, the client can be correctly initialized, but no data was saved
07:42:25 Kevin_Zheng so cannot retrive any data

Earlier   Later