*** tetsuro has joined #openstack-blazar | 00:35 | |
*** tetsuro has quit IRC | 03:57 | |
*** masahito has joined #openstack-blazar | 04:04 | |
*** tetsuro has joined #openstack-blazar | 05:50 | |
*** asmita has joined #openstack-blazar | 06:16 | |
asmita | masahito: Hi, I want your suggestion on this bug: https://bugs.launchpad.net/blazar/+bug/1797502 | 06:37 |
---|---|---|
openstack | Launchpad bug 1797502 in Blazar "missing 'before_end_date' value in lease response" [Undecided,New] - Assigned to Neha Alhat (nehaalhat) | 06:37 |
*** masahito has quit IRC | 06:40 | |
*** nehaalhat has joined #openstack-blazar | 06:40 | |
*** masahito has joined #openstack-blazar | 06:41 | |
masahito | asmita: sorry, disconnected. What problem are you hitting? | 06:42 |
asmita | masahito: I want your suggestion on this bug: https://bugs.launchpad.net/blazar/+bug/1797502, If we decide to add 'before_end_date' in lease response. then we can go by 1. Updating migration script to add column for 'before_end_date' in lease table | 06:49 |
openstack | Launchpad bug 1797502 in Blazar "missing 'before_end_date' value in lease response" [Undecided,New] - Assigned to Neha Alhat (nehaalhat) | 06:49 |
asmita | 2. fetch value of 'before_end_date' from events table and show it in lease response | 06:50 |
asmita | masahito: or we can go with 'microversioning thing' like other projects(nova, cinder) have implemented. | 06:52 |
masahito | I'm not clear the bug report. I can see the before_end_lease time in the response. | 06:58 |
*** tetsuro has quit IRC | 07:01 | |
*** tetsuro has joined #openstack-blazar | 07:01 | |
*** tetsuro has quit IRC | 07:02 | |
asmita | masahito: Actually like 'start_date' and 'end_date' there is no value for 'before_end_date'. We can see time for all events in response but still 'start_date' and 'end_date' are shown explicitly and same are stored in DB.' | 07:05 |
asmita | In DB value for 'before_end_date' is not getting stored. | 07:05 |
masahito | I got the point. | 07:09 |
masahito | The point is 'before_end_date' key should be a first key in the LEASE object, right? | 07:10 |
asmita | Yes | 07:11 |
masahito | IMO, each date info should be managed in one place, not both of lease table and event table because it causes miss-matching between the lease raw and the event raw. | 07:14 |
masahito | So it's better to either of deleting start/end_date in the lease table or deleting the time in the event column. | 07:16 |
masahito | For the API side, we don't have microversioning now. | 07:17 |
masahito | It's okay to add the new key without microversioning if others agree the change. | 07:18 |
asmita | masahito: ok, so now we need to manage each date info in one place, right? | 07:20 |
asmita | and I haven't understood this: miss-matching between the lease raw and the event raw | 07:24 |
*** masahito has quit IRC | 08:05 | |
*** tetsuro has joined #openstack-blazar | 09:02 | |
*** masahito has joined #openstack-blazar | 09:14 | |
masahito | asmita: yes. It's better to manage the info in one place. | 09:14 |
masahito | In case of the info is managed in two or more places, a developer would create a bug. For example, A developer only modifies either of them to add a new feature even though they need to modify all of the codes. | 09:20 |
asmita | masahito: Okay ,got your point.Will check. | 09:25 |
asmita | Thanks | 09:25 |
*** masahito has quit IRC | 10:16 | |
*** asmita has quit IRC | 10:17 | |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Trivial refactor in instance_plugin.py https://review.openstack.org/610485 | 11:40 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Add create/delete reservation provider https://review.openstack.org/584625 | 12:30 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Add create/delete resource class https://review.openstack.org/578073 | 12:30 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Add update/delete resource inventory https://review.openstack.org/578637 | 12:30 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Create and delete reservation provider https://review.openstack.org/585323 | 12:30 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Use placement inventory for instance reservation https://review.openstack.org/584744 | 12:30 |
openstackgerrit | Tetsuro Nakamura proposed openstack/blazar master: Adds subnormal path for placement client https://review.openstack.org/610497 | 12:30 |
*** tetsuro has quit IRC | 12:32 | |
openstackgerrit | Pierre Riteau proposed openstack/blazar master: Allow terminating a lease in ERROR state https://review.openstack.org/604159 | 14:08 |
*** openstackgerrit has quit IRC | 15:47 | |
*** openstackgerrit has joined #openstack-blazar | 15:48 | |
openstackgerrit | Merged openstack/blazar master: Allow terminating a lease in ERROR state https://review.openstack.org/604159 | 17:21 |
openstackgerrit | Pierre Riteau proposed openstack/blazar master: Allow leases to transition to ERROR status when events fail https://review.openstack.org/589898 | 18:00 |
openstackgerrit | Pierre Riteau proposed openstack/blazar master: Allow terminating leases in ERROR state when start_lease failed https://review.openstack.org/610678 | 18:00 |
*** openstackgerrit has quit IRC | 21:56 | |
*** openstackgerrit has joined #openstack-blazar | 21:57 | |
*** openstackgerrit has quit IRC | 21:58 | |
*** openstackgerrit has joined #openstack-blazar | 22:00 | |
*** openstackgerrit has quit IRC | 22:12 | |
*** openstackgerrit has joined #openstack-blazar | 22:13 | |
*** openstackgerrit has quit IRC | 22:43 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!