opendevreview | Anvi Joshi proposed openstack/openstacksdk master: Implemented methods for share metadata https://review.opendev.org/c/openstack/openstacksdk/+/886123 | 03:06 |
---|---|---|
opendevreview | Pavlo Shchelokovskyy proposed openstack/openstacksdk master: Fix list of server migrations https://review.opendev.org/c/openstack/openstacksdk/+/887847 | 13:35 |
opendevreview | Mridula Joshi proposed openstack/python-openstackclient master: image: Add support for cache commands https://review.opendev.org/c/openstack/python-openstackclient/+/878631 | 14:04 |
opendevreview | Lajos Katona proposed openstack/openstacksdk master: Add SFC to SDK https://review.opendev.org/c/openstack/openstacksdk/+/887387 | 14:44 |
opendevreview | Douglas Mendizábal proposed openstack/python-openstackclient stable/2023.1: Fix pep issue in the network service provider https://review.opendev.org/c/openstack/python-openstackclient/+/887812 | 15:46 |
opendevreview | Douglas Mendizábal proposed openstack/python-openstackclient stable/2023.1: Fix "access rule" commands to only use ID https://review.opendev.org/c/openstack/python-openstackclient/+/887742 | 15:46 |
opendevreview | Stephen Finucane proposed openstack/python-openstackclient master: Add image metadef resource type command 'list' https://review.opendev.org/c/openstack/python-openstackclient/+/883279 | 16:22 |
opendevreview | Stephen Finucane proposed openstack/python-openstackclient master: Add image metadef resource type command 'list' https://review.opendev.org/c/openstack/python-openstackclient/+/883279 | 17:06 |
opendevreview | Stephen Finucane proposed openstack/python-openstackclient master: doc: Split image command documentation https://review.opendev.org/c/openstack/python-openstackclient/+/887863 | 17:06 |
opendevreview | Merged openstack/openstacksdk master: volume: Add missing attributes to Extension https://review.opendev.org/c/openstack/openstacksdk/+/885132 | 18:02 |
andrewbogott_ | I'm very interested in someone's thoughts about whether or not this is a bug. https://storyboard.openstack.org/#!/story/2010784 | 18:09 |
andrewbogott_ | I changed all my workflows to use clouds.yaml and now a really regret it, thanks to that issue. Maybe clouds.yaml is out of fashion and I should go back to relying on env settings? | 18:10 |
andrewbogott_ | s/now a/now I/g | 18:10 |
frickler | andrewbogott_: to me the story looks incomplete, it ends with " | 18:54 |
frickler | $ source" | 18:54 |
frickler | oops | 18:54 |
andrewbogott_ | I don't understand why storyboard truncates the view, if I click the 'edit' button I can see all the text | 18:54 |
frickler | anyway, I'm not sure what it actually is that is bothering you | 18:54 |
frickler | can you put the whole text into paste.openstack.org and link it in a comment? | 18:55 |
andrewbogott_ | sure | 18:55 |
frickler | also clouds.yaml it the future IMO, env vars should be deprecated | 18:55 |
andrewbogott_ | ok, that's what I thought. In that case I think that we have quite a few commands that need a --project arg added. | 18:57 |
andrewbogott_ | Or the parser could load clouds.yaml first and env second (but that would still be relying on env) | 18:57 |
frickler | oh, I can see the text when I enter edit mode myself. my guess is that the "<script" thing gets parsed as html tag somehow, maybe fungi can have a look? | 18:58 |
andrewbogott_ | oh good idea, let me try messing with quotes | 18:58 |
frickler | what about having one cloud definition per project as workaround? you could easily script setting that up as clouds.yaml | 18:59 |
andrewbogott_ | how's that, better? | 18:59 |
andrewbogott_ | frickler: that would work but seems a bit silly. I have hundreds of tenants in my cloud. | 18:59 |
andrewbogott_ | Also, my understanding is that much of the reason why 'scope' was abandoned as a concept was because it broke the 'global cred' workflows that many clouds use. clouds.yaml also breaks them. | 19:00 |
andrewbogott_ | (the scope discussion just being an example of how as I understand it OpenStack has committed to continuing to support global credentials) | 19:00 |
andrewbogott_ | (another example: --inherited roles set on a domain) | 19:01 |
fungi | frickler: andrewbogott_: storyboard's renderer parses markdown and also (some) html/sgml, so if you want to avoid it trying to interpret literal blocks of text you need to do something to flag it as such, for example by fencing above and below the lines you want not to be interpreted using triple-backticks (```) | 19:02 |
andrewbogott_ | I replaced my <brackets> with [brackets] which seems to work better :) | 19:02 |
fungi | or you can use <pre></pre> tags to wrap content | 19:02 |
andrewbogott_ | Although I don't know why an html parser would throw away all the text following an unknown tag. | 19:03 |
andrewbogott_ | I just figured it was hitting a character limit *shrug* | 19:03 |
andrewbogott_ | fungi: maybe I should log a storyboard bug, is there a place to do that? | 19:04 |
fungi | i'm not sure without digging into the renderer, but likely there's security measures kicking in to try to avoid handing off <script ...> tags to browsers in order to stop xss attacks | 19:04 |
fungi | i doubt we'd treat the inability to render non-preformatted content containing the string "<script" as a bug to be fixed | 19:06 |
frickler | it also drops other things like the <end>, at least in preview | 19:06 |
andrewbogott_ | I don't mind that it doesn't render it but I wish it would do something other than just silently truncate. If 'fail silently' is the behavior you want, though, then ok :) | 19:07 |
fungi | well, "don't allow xss attacks" is a behavior we want, "gracefully display the source of things you can't or intentionally don't parse" is likely something we'd accept a patch for if someone had the time to get it working | 19:08 |
frickler | anyway IMO storyboard is a dead end and hopefully this team will move back to LP soon like most other openstack projects did | 19:08 |
fungi | but also there's the problem that we're already unable to run the latest versions of storyboard due to deployment tooling work that's been perpetually backburnered due to insufficiency of infra volunteers | 19:08 |
* andrewbogott_ really doesn't want to get into a SB vs LP holy war! | 19:09 | |
fungi | most of the openstack projects which were on storyboard haven't moved yet (there are a lot) but a number of more active ones have, and a lot of the ones who haven't are probably ignoring their bug reports regardless of which black hole users send them into | 19:09 |
fungi | as is the case with lots of open source projects | 19:10 |
fungi | bug reports are most useful to project maintainers as a means of organizing work they plan to do or expect someone to have time to do | 19:11 |
opendevreview | Ashley Rodriguez proposed openstack/openstacksdk master: Adds service resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/873328 | 19:11 |
andrewbogott_ | In this case I would certainly write a patch to address my report, but only after I have some reason to think that upstream is interested in the behavior changing. I've found that writing patches at the same time as bug reports often leads to heartbreak :) | 19:12 |
frickler | usually I'd ask gtema for their opinion but they are holidaying right now, maybe give it a couple of days at least | 19:13 |
andrewbogott_ | ok | 19:13 |
fungi | agreed. there's basically nobody handling defect reports about sb automatically, only if someone brings them to our attention and usually then only if they're absolutely crippling. there's basically nobody watching for them and really nobody reviewing/approving changes for the sb repos these days | 19:14 |
andrewbogott_ | I never know how long to wait after a report to start nagging in IRC. Depends on the project I guess. Thanks for looking, frickler | 19:14 |
andrewbogott_ | fungi: now that I have a workaround for my report I'm not super invested, just offering to log if you think it would be useful. (Which it sounds like not, if sb is largely unmaintained) | 19:15 |
fungi | yep, thanks for the heads up about it though, i hadn't considered that particular behavior | 19:15 |
opendevreview | Ashley Rodriguez proposed openstack/openstacksdk master: Add share instance export location resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/873327 | 19:15 |
andrewbogott_ | frickler: can you clarify 'give it a couple of days'? I opened the issue a month ago, should I come back here and ping again next week? | 19:16 |
opendevreview | Ashley Rodriguez proposed openstack/openstacksdk master: Add share replica resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/873324 | 19:16 |
andrewbogott_ | (although i guess it's only just now legible so I probably shouldn't count that month) | 19:16 |
frickler | andrewbogott_: I think noone tracks/watches stories for sdk/osc, so mentioning them here or on the ML is the only get attention to them at all. so indeed time starts counting only now. | 19:34 |
andrewbogott_ | ok | 19:35 |
frickler | come back any time that suits you, I don't think anything bad can happen from that other than you getting frustrated about receiving no response | 19:35 |
opendevreview | Merged openstack/python-openstackclient stable/2023.1: Fix pep issue in the network service provider https://review.opendev.org/c/openstack/python-openstackclient/+/887812 | 19:36 |
opendevreview | James E. Blair proposed openstack/openstacksdk master: Treat server as a dict in add_server_interfaces https://review.opendev.org/c/openstack/openstacksdk/+/887906 | 22:11 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!