Earlier  
Posted Nick Remark
#openstack-nova - 2018-07-26
20:11:27 openstackgerrit melanie witt proposed openstack/os-vif stable/rocky: Add vif_plug_noop to setup.cfg packages https://review.openstack.org/586340
20:13:12 mriedem well i shall start the stack while writing my monthly report...
20:14:12 melwitt how can I tell who is stable/core for $project? I haven't noticed a way to figure that out for libs like os-vif
20:14:19 melwitt figure out via gerrit
20:16:07 mriedem people
20:16:19 mriedem oh well,
20:17:26 mriedem i thought it was in project-config but can't find it
20:17:57 melwitt ok, just curious. since I keep asking, was wondering if there was a way to avoid bugging people
20:18:24 melwitt I assume for os-vif it's the same stable team as for nova
20:18:55 melwitt I need stable review for a FFE release of os-vif https://review.openstack.org/586340
20:19:44 mriedem oh i found it
20:20:07 mriedem https://github.com/openstack-infra/project-config/blob/master/gerrit/acls/openstack/os-vif.config
20:20:39 melwitt cool! thanks
20:20:53 mriedem +2
20:21:21 melwitt thanks 2x
20:23:12 melwitt dansmith: plz https://review.openstack.org/586340
20:24:57 mriedem commence to stacking
20:36:31 melwitt thx dansmith
20:36:54 dansmith aye
20:37:49 melwitt mriedem: fyi https://review.openstack.org/586307 sorry I didn't get your ack before osc-placement got released
20:38:08 melwitt I meant to
20:40:37 mriedem doesn't that need to branch?
20:41:21 melwitt are we supposed to branch manually in the release? I thought that would happen automatically
20:41:33 mriedem no it's a designated thing in the deliverable yaml
20:41:46 mriedem i.e. what was removed on the left side https://review.openstack.org/#/c/586307/1/deliverables/rocky/osc-placement.yaml
20:41:55 mriedem you'd need that for 1.3.0 to be where they branch stable/rocky
20:42:07 melwitt gdi
20:42:31 mriedem i don't know what "And it removes the stable/rocky branch that had to be manually deleted because of the mis-categorization of the library as a non-client." all means but that's what i've done in the past
20:43:13 melwitt what happened was that osc-placement has been categorized as a 'non-client library' up to now,
20:43:25 mriedem oh i see https://github.com/openstack/releases/commit/8dadc73479e3c303c4f5ee3975628c3e333d61cc#diff-64bede2e011f3f457420a6313880e97b
20:43:27 mriedem so smcginnis did it for you
20:44:11 mriedem i did it in queens https://github.com/openstack/releases/commit/a5a77d24664a2502c68cc5b0cba17db8373499c2#diff-b9ac789921c8d258691218b7fcbeaefb
20:44:13 melwitt and I had asked around in -releases about whether it should be considered a client library since it's a osc plugin, we agreed it should be a client lib and smcginnis had meant to omit it in the branch cutting that happened last week for non client libs, and that I would propose a change to the library 'type' when I released it this week
20:44:41 melwitt so, they ended up deleting the stable/rocky branch for us to go ahead and do the release today as a client library
20:45:11 mriedem yup so i guess push a patch to branch stable/rocky at 1.3.0
20:45:24 mriedem have you done a python-novaclient release?
20:45:37 mriedem b/c same thing there
20:45:47 melwitt sounds like it, I'll ask in -releases. it looks like this branch thing might be part of their (release team) process
20:45:55 melwitt not yet, putting that together now
20:45:59 mriedem i've always done it myself
20:46:34 mriedem i never trusted smcginnis touching my sweet sweet deliverables
20:47:13 melwitt heh :)
20:48:37 melwitt yeah, that was his 'clean up after people' script that did it. I'm a terrible release proposer
20:49:54 smcginnis :)
20:50:24 smcginnis I've thought of so many responses to that. None of which I feel I should write here.
20:50:48 smcginnis Not to your comment melwitt, to mriedem's. :)
20:50:56 melwitt I figured :)
20:53:13 mriedem dansmith: yup thar she blar http://paste.openstack.org/show/726714/
20:53:44 dansmith nice
21:01:49 melwitt mriedem: novaclient release proposed https://review.openstack.org/586350
21:08:05 mriedem my awk skills are not going to be good enough to parse out that df output
21:08:11 mriedem i can parse out: ceph status | grep usage
21:08:45 dansmith is that a challenge?
21:08:49 mriedem it is
21:09:25 melwitt mriedem: you can pass --format=json to make it return json if that helps
21:09:42 mriedem $ sudo ceph df | awk 'NR==3{print $1}END{$1}'
21:09:42 mriedem ooo
21:09:43 mriedem 24564M
21:10:20 mriedem melwitt: doesn't really help me in bash
21:10:43 mriedem although,
21:10:50 mriedem pipe that into python -m json.tool
21:10:56 mriedem }
21:10:56 mriedem "total_used_bytes": 275038208
21:10:56 mriedem "total_bytes": 25757220864,
21:10:56 mriedem "total_avail_bytes": 25482182656,
21:10:56 mriedem "stats": {
21:11:16 dansmith 22
21:11:16 dansmith echo $((`cat ceph | grep vms | awk '{print $5}' | egrep -o '[0-9]+'` / 1024))
21:11:45 dansmith oh json format is nice
21:11:51 dansmith is jq on the worker nodes? I bet it is
21:12:03 mriedem 25482182656,
21:12:03 mriedem $ sudo ceph df --format=json | python -m json.tool | grep total_avail_bytes | awk 'END{print $2}'
21:12:03 mriedem except the comma
21:12:22 dansmith hold up
21:13:03 mriedem 25481973760
21:13:03 mriedem $ sudo ceph df --format=json | python -m json.tool | grep total_avail_bytes | awk 'END{print $2}' | egrep -o '[0-9]+'
21:13:03 mriedem haha
21:13:35 dansmith ceph df --format=json |
21:13:43 dansmith ceph df --format=json | jq .total_bytes
21:13:49 dansmith er
21:13:57 dansmith ceph df --format=json | jq stats.total_bytes
21:13:59 dansmith I think
21:14:14 mriedem don't have jq
21:14:28 dansmith ceph df --format=json | jq .stats.total_bytes
21:14:30 dansmith ^ works
21:14:37 dansmith on the worker nodes?
21:14:40 dansmith that sucks
21:14:43 mriedem 25757220864
21:14:43 mriedem $ sudo ceph df --format=json | jq .stats.total_bytes
21:14:47 mriedem i mean, we can install it...
21:14:58 mriedem $ sudo ceph df --format=json | python -m json.tool | grep total_avail_bytes | egrep -o '[0-9]+'
21:14:58 mriedem but this also works
21:14:59 mriedem 25481973760
21:15:12 dansmith yup
21:15:22 dansmith convert to GB of course
21:16:41 mriedem $ sudo ceph df --format=json-pretty | grep total_avail_bytes | egrep -o '[0-9]+'
21:16:41 mriedem yup; even shorter with json-pretty
21:16:42 mriedem 25481887744
21:27:01 mriedem oh do we have to pull from the vms pool specifically?
21:27:02 mriedem i suppose huh

Earlier   Later