Earlier  
Posted Nick Remark
#openstack-nova - 2019-06-24
21:55:33 sean-k-mooney os-vif say mock < X some other poject requires mock > x
21:55:48 sean-k-mooney os-vif and that service can nolonger be installed together
21:56:10 tonyb sean-k-mooney: ahhh okay .... that's handled in the generate-constraints job so it *shouldn't* be possible
21:56:34 tonyb sean-k-mooney: for *upper* constraints for lower all bets are off
21:56:37 sean-k-mooney can you explain breifly how upper-constratis is generated
21:56:59 sean-k-mooney i.e. how is gr used for uc
21:57:14 tonyb sean-k-mooney: basically we pip install -r global-requirements.txt and "freeze" the output
21:57:18 sean-k-mooney i was not aware uc was generated for gr
21:57:34 sean-k-mooney i though uc was manually updated as needed
21:57:57 sean-k-mooney rathar then auto updating as upstream releases?
21:58:03 sean-k-mooney i guess that is not the case?
21:58:16 tonyb for master it's a daily update and then "fixed" if needed, for stable it's all manual
21:58:39 sean-k-mooney ah ok so master allows latest unless we know somthing is broken
21:58:53 sean-k-mooney is gr used to pin things that are broken in that case ?
21:58:59 tonyb https://review.opendev.org/#/c/666981/ was last night's auto generate
21:59:33 tonyb sean-k-mooney: Yes, if lib $foo has a broken version we add a != in g-r to avoid it
21:59:47 openstackgerrit Eric Fried proposed openstack/nova-specs master: Libvirt: add vPMU spec for train https://review.opendev.org/651269
22:00:22 sean-k-mooney and we are now using sphinx < 2.0 as a shorthad to cover all the non py27 versions
22:01:45 sean-k-mooney ok i can approve https://review.opendev.org/#/c/666387/ but its kind of regretable that we will have to modify requirement every time gr is modifed to reflect a new cap.
22:02:08 sean-k-mooney if the cap was only done via upper-constratits then it would just automaticlly work
22:02:19 tonyb sean-k-mooney: Yes, we've always needed to do that but it's just more obvious now
22:02:35 tonyb sean-k-mooney: I agre it's ugly but we can't think of a better way with the tools we have
22:02:45 sean-k-mooney nova os-vif and other project that generate docs form code need to use uc to pin to compatible verions anyway otherwise they can fail
22:03:13 tonyb sean-k-mooney: correct
22:03:45 tonyb sean-k-mooney: gotta disappear I'll be back in a bit
22:04:27 sean-k-mooney hehe im going to drop too. i was playing games on my desktop but its late enough now that i should praobbly call it a day o/
22:04:40 sean-k-mooney tonyb: thanks for explainin
22:05:33 sean-k-mooney i had taken the view that capping in requiremetn in repo was nolonger allowed but ill adjust to allowing it if it is capped that way in gr going forward
22:27:09 tonyb sean-k-mooney: we (the requirements team) clearly need better reference docs or a FAQ or something
22:47:14 openstackgerrit Merged openstack/nova master: bdm: store empty object as connection_info by default https://review.opendev.org/645352
#openstack-nova - 2019-06-25
00:04:29 openstackgerrit Takashi NATSUME proposed openstack/python-novaclient master: Add a guide to add a new microversion support https://review.opendev.org/667002
00:07:45 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Support for changing deleted_on_termination after boot https://review.opendev.org/580336
00:08:08 openstackgerrit Brin Zhang proposed openstack/nova-specs master: Support delete_on_termination in volume attach api https://review.opendev.org/612949
01:12:52 openstackgerrit Alex Xu proposed openstack/nova master: Correct the comment of RequestSpec's network_metadata https://review.opendev.org/667061
03:40:46 openstackgerrit huichen proposed openstack/nova master: Support pagination for sever groups by sql https://review.opendev.org/667259
05:50:52 cf__ Hi! I asked in cinder channel yesterday regarding delete_on_termination and they pointed me towards nova, which make sense, however, when I do nova show <uuid>, I do not receive any information about delete_on_termination, even that I did set it when creating the instance.. What am I doing wrong, to check if the volume is going to be deleted on instance termnination?
05:56:29 cf__ $ nova show 83fcdb58-045a-4475-b4eb-5b9287daebcc |grep volume
05:56:30 cf__ | os-extended-volumes:volumes_attached | [{"id": "f3e192b6-f8b0-4a9b-8512-4e7ffa37756d"}]
06:05:31 brinzhang__ cf__: What about your volume? root disk? or data disk ?
06:06:05 cf__ brinzhang__: it's my root disk
06:06:22 brinzhang__ cf__: If it's a root disk, you can see the delete_on_termination from 'nova show server_id'
06:06:39 brinzhang__ [root@localhost ~]# nova show ec939a46-9e1e-4126-8214-6ceb3b95676a |grep volume
06:06:39 brinzhang__ | image | Attempt to boot from volume - no image supplied |
06:06:39 brinzhang__ | os-extended-volumes:volumes_attached | [{"id": "df191675-0ac1-4101-a590-7ad2f7607e89", "delete_on_termination": true}] |
06:07:27 cf__ The thing is, the person that started a bunch of instances did it with config_drive enabled which is kinda destroying the idea of a flexible environment, by making it extremely hard to live migrate running instances
06:08:48 cf__ Yeah, that's what i'm trying to find, however as pasted above, it dosnt show.. This is a test instance I made with delete_on_termination true, but I wanted to check if I was able to see it anywhere because for my production instances, i cannot risk to lose my volumes when i'm forced to delete the running instances and create new ones with the existing volumes in order to get rid of config_drive
06:10:04 cf__ for a random production instance i get:
06:10:04 cf__ stack@j3499-cp1-c1-m1-mgmt:~$ nova show f0c664e6-f161-41ac-93bd-cc2500644583 |grep volume
06:10:05 cf__ | image | Attempt to boot from volume - no image supplied |
06:10:05 cf__ | os-extended-volumes:volumes_attached | [{"id": "d86ea1ef-1b31-435d-8d3c-f106b61501ec"}, {"id": "d6fc7a5b-2cc0-4764-9a47-8cc89a609e0f"}, {"id": "9ff316b7-ff6d-4f63-a3fe-97dde0ba8803"}] |
06:11:08 cf__ ofcause this one, I do not know if delete_on_termination was set uppon creation - however it is on the first one I pasted, which was made only to check if I was able to find the info about delete_on_termination
06:12:01 brinzhang__ cf__: I think you can check it in block_device_mapping table, is that the delete_on_termination was set?
06:12:35 cf__ brinzhang__: so check the database? or is there a way to check it from cli?
06:13:14 brinzhang__ Because there is no scene for you, you can’t be sure that the problem exists.
06:13:45 cf__ Yeah, i just want to make sure not to lose data when I delete the running instances :)
06:15:40 brinzhang__ Currently, the delete_on_termination can only set when the server boot, there are two specs want to support config and reconfig that change, but not start working ...
06:16:39 cf__ It make sense.. maybe I should just create some backup before testing this :P
06:17:46 brinzhang__ Thanks, you can try test this, and report a but on launchpad https://bugs.launchpad.net/nova
06:18:16 brinzhang__ If ensure that issue exist :P
06:19:01 cf__ Will do, thanks :)
06:19:44 cf__ Oh btw, it's worth mentioning that this is a rather old instance of openstack since we're currently running Newton, but I guess that shouldnt do much of a difference
06:24:49 brinzhang__ Oh.. good luck.
06:33:14 openstackgerrit Yongli He proposed openstack/nova master: Clean up orphan instances virt driver https://review.opendev.org/648912
06:33:15 openstackgerrit Yongli He proposed openstack/nova master: clean up orphan instances https://review.opendev.org/627765
06:54:27 cf__ brinzhang__: I found it! Turns out that the easiest way was to check it in the nova database...
06:54:40 cf__ mysql> select delete_on_termination from block_device_mapping where instance_uuid = '83fcdb58-045a-4475-b4eb-5b9287daebcc';
06:54:40 cf__ | delete_on_termination |
06:54:40 cf__ +-----------------------+
06:54:40 cf__ | 1 |
06:54:41 cf__ +-----------------------+
07:01:20 brinzhang__ cf__:So, next, you should to check that 'nova show' why not return this attribute, is there some error? Or some useful log?
07:02:51 brinzhang__ I am sorry, I am not have the newton environment to support more help :P
07:59:32 openstackgerrit zhaixiaojun proposed openstack/python-novaclient master: Modify the url of upper_constraints_file https://review.opendev.org/665934
09:02:15 openstackgerrit Rui Zang proposed openstack/nova-specs master: support virtual persistent memory https://review.opendev.org/601596
09:06:13 openstackgerrit Arnaud Morin proposed openstack/nova master: Do not refresh deleted instance info cache https://review.opendev.org/667294
09:53:13 openstackgerrit huichen proposed openstack/nova master: Support pagination for sever groups by sql https://review.opendev.org/667259
10:00:39 openstackgerrit huichen proposed openstack/nova master: Support pagination for sever groups by sql https://review.opendev.org/667259
10:06:57 openstackgerrit Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520
10:34:26 openstackgerrit Stephen Finucane proposed openstack/nova master: nova-status: Remove consoleauth workaround check https://review.opendev.org/652968
10:34:26 openstackgerrit Stephen Finucane proposed openstack/nova master: Remove nova-consoleauth https://review.opendev.org/652969
10:34:27 openstackgerrit Stephen Finucane proposed openstack/nova master: objects: Remove ConsoleAuthToken.to_dict https://review.opendev.org/652970
10:34:27 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Rework nova console diagram https://review.opendev.org/660147
10:34:28 openstackgerrit Stephen Finucane proposed openstack/nova master: docs: Integrate 'sphinx.ext.imgconverter' https://review.opendev.org/665693
11:24:52 openstackgerrit Balazs Gibizer proposed openstack/nova stable/stein: Remove redundant group host setup https://review.opendev.org/667334
11:50:43 openstackgerrit Arnaud Morin proposed openstack/nova stable/stein: Always Set dhcp_server in network_info https://review.opendev.org/667340
12:04:41 openstackgerrit Lee Yarwood proposed openstack/nova master: libvirt: flatten rbd images when unshelving an instance https://review.opendev.org/457886
12:05:10 lyarwood mdbooth / dansmith ; ^ rebased and touched up slightly, should be ready for review again.
12:07:58 mdbooth lyarwood: Hehe, I managed to avoid the external_events conflict with my patch by out-waiting it :)
12:08:50 mdbooth Ah, you didn't conflict with it. Lucky.
12:16:21 mdbooth artom|gmtplus3 sean-k-mooney: Do you expect your fixed hybrid vif plugged patch to land soon?
12:17:16 sean-k-mooney am i hope so but that depend on stealing review time from peole to land it
12:19:25 sean-k-mooney it looks like artom has some concerns
12:20:05 sean-k-mooney so maybe not right away
12:20:17 sean-k-mooney mdbooth: are you asking for you patch that is in merge conflict
12:20:56 mdbooth sean-k-mooney: Well it was in merge conflict while the patch was landed, but is now no longer conflicting but I need to rebase anyway because it seems gerrit can't tell that.
12:21:26 sean-k-mooney ah well you might as well rebase
12:21:58 mdbooth sean-k-mooney: https://youtu.be/N0BkjvUOtX4?t=29
12:22:06 sean-k-mooney have you got any review on it lately
12:22:29 mdbooth sean-k-mooney: Yeah, a bit.
12:23:44 sean-k-mooney hum i havent seen fifth element in a while

Earlier   Later