Tuesday, 2019-02-26

*** diablo_rojo has joined #storyboard00:02
*** tosky has quit IRC00:23
*** misaac has quit IRC00:35
*** jaosorior has quit IRC01:20
*** jamesmcarthur has joined #storyboard01:23
*** jaosorior has joined #storyboard01:32
*** jamesmcarthur has quit IRC01:49
*** whoami-rajat has joined #storyboard02:02
*** jamesmcarthur has joined #storyboard02:25
*** jamesmcarthur has quit IRC03:25
*** jamesmcarthur has joined #storyboard03:28
*** jamesmcarthur has quit IRC03:36
*** sarwatfatimam has quit IRC03:37
*** jamesmcarthur has joined #storyboard03:40
*** jamesmcarthur has quit IRC03:45
*** udesale has joined #storyboard03:54
*** jamesmcarthur has joined #storyboard04:07
*** jamesmcarthur has quit IRC04:23
*** misaac has joined #storyboard04:47
*** misaac has quit IRC04:51
*** kshitija has joined #storyboard06:18
*** kshitija has quit IRC06:29
*** kshitija has joined #storyboard06:34
*** misaac has joined #storyboard06:58
*** misaac has quit IRC06:58
*** misaac has joined #storyboard07:00
*** jtomasek has joined #storyboard07:25
*** tosky has joined #storyboard08:39
*** dtantsur|afk is now known as dtantsur08:46
*** jpich has joined #storyboard08:53
*** tbarron has quit IRC09:30
*** kshitija has quit IRC09:50
*** shruti10 has joined #storyboard09:58
*** kshitija has joined #storyboard10:04
*** kshitija[m] has joined #storyboard10:05
*** kshitija has quit IRC10:20
*** cmoura has joined #storyboard10:28
cmouraHello everyone, I'm Camila and participate in Outreachy, I discovered a bug that I can solve, so, I want to contribute with the StoryBoard :)11:13
*** udesale has quit IRC11:29
cmouraso, I have questions, Can myself create a Task from a Story? and do the Task?11:35
*** jamesmcarthur has joined #storyboard11:44
*** malani_ has joined #storyboard12:04
*** diablo_rojo_ has joined #storyboard12:30
*** gouthamr has quit IRC12:30
*** diablo_rojo has quit IRC12:30
*** openstackgerrit has quit IRC12:30
*** gouthamr has joined #storyboard12:33
*** jamesmcarthur has quit IRC12:34
*** jamesmcarthur has joined #storyboard12:34
*** aashna has joined #storyboard12:38
aashnahey I'm an outreachy applicant! Can someone help me out with how to get started?12:38
*** jamesmcarthur has quit IRC12:52
*** jamesmcarthur has joined #storyboard12:57
*** ivy has joined #storyboard13:19
*** ivy has quit IRC13:20
*** ivy has joined #storyboard13:21
*** ivy has quit IRC13:33
*** jamesmcarthur has quit IRC13:35
*** dtantsur is now known as dtantsur|afk13:38
*** jamesmcarthur has joined #storyboard13:39
*** jamesmcarthur has quit IRC13:40
*** jamesmcarthur has joined #storyboard13:40
*** hadiajalil has joined #storyboard14:01
hadiajalilHello. This is Hadia.14:02
*** mkarray has joined #storyboard14:12
*** hadiajalil has quit IRC14:33
*** hadiajalil has joined #storyboard14:48
*** hadiajalil has quit IRC15:10
*** jamesmcarthur has quit IRC15:11
*** jamesmcarthur has joined #storyboard15:11
*** jamesmcarthur has quit IRC15:15
*** jamesmcarthur has joined #storyboard15:27
*** malani_ has quit IRC15:28
*** jamesmcarthur has quit IRC15:30
*** ivy has joined #storyboard15:32
ivyIn my last commit, some of the test on zuul return failure. So, I checked the linting job which catches bugs in the syntax of the change on zuul. But everytime I make a correction and commit, some new error comes up.15:33
ivyI decided to set up and do the test locally, so I can correct all errors before pushing the correct code.15:33
ivyI ran pep8, ('tox -e pep8') locally, corrected all errors and it worked. Also ran, 'tox -e py35' and 'tox -ecover' for over 2hrs now but it nothing's happening, no output. It appears to be stuck.15:33
ivyThen I ran 'tox -e py27' which displayed an error. After correcting this error, I ran the command again and just like the the last two commands, there are no results.15:33
ivyAny ideas how I can get these to work?15:34
*** jamesmcarthur has joined #storyboard15:39
clarkbivy: it is possible there is missing database setup15:59
clarkbSotK and diablo_rojo_phon probably know if you need to bootstrap the unittest environment15:59
clarkbI have a meeting now but can check afterwards if you are able to stick around (not sure if that works for your timezone)15:59
clarkbcmoura: yes you should feel free to start interacting with the systems in that way16:00
ivyNo problem. I'll be around16:01
ivy:)16:01
clarkbivy: looks like doc/source/contributing.rst says you do need to set up the database and looks like tools/install_test_backend.sh may do that for you16:04
ivyokay. I'll try that16:05
*** kshitija has joined #storyboard16:50
*** mkarray has quit IRC17:09
*** mkarray has joined #storyboard17:10
*** jpich has quit IRC17:17
*** mkarray has quit IRC17:20
*** ivy has quit IRC17:25
fungidiablo_rojo_phon: 633365 is passing tests now (the verified -1 was for a timeout on a coverage job), and has some other approvals lined up behind it already17:39
*** openstackgerrit has joined #storyboard17:39
openstackgerritMerged openstack-infra/storyboard master: Add an interface specifying the API for storage backends  https://review.openstack.org/63336417:39
*** kshitija has quit IRC17:41
fungi633417 has a similar timeout on the py27 unit test job17:42
*** ivy has joined #storyboard17:43
*** cdent has joined #storyboard17:46
cdentdiablo_rojo_ (or anyone else): Is it okay for a project to start using storyboard prior to migrating anything? Or is migration destructive of stuff that is already there?17:48
fungicdent: all "migration" does is (incrementally) import bugs and their comments and bugtasks from lp into sb and prepopulate users so it can retain references to comment authors17:51
fungithe only tricky part with starting to use it for a project early is that our lp bug updating automation is keyed on the same use-storyboard flag in projects.yaml which also causes our project management orchestration to create the projects and project groups in sb17:53
cdentfungi: I think that's all already kind of broken for placement now that it is it's own official thing, but keeps its (old) bugs under nova17:53
fungigot it17:54
cdentthe emerging plan is that we'll simply start fresh on storyboard17:54
cdentbecause there's a rather small number of placement-tagged bugs under nova17:54
fungiwe do also have an lp bugtag filter we can use to import nova bugs with the placement tag (for example) and create tasks for openstack/placement in storyboard17:54
cdentbut I didn't want us to get into some weird state where if we did need to import we couldn't ...17:55
cdentthis is all somewhat complicated by being in a ptl limbo for a few more days17:56
fungiif you expect those bugs to continue to get comments and state changes though, importing them may be premature. the migration tool will incrementally pull in new bugs and comments which don't exist in sb after the previous run, but it's somewhat lacking in ability to spot and apply changes in bugtask status17:56
*** malani has joined #storyboard17:57
fungibut yeah, if you want to add use-storyboard:true and hold off importing bugs from lp, i think that's fine as long as you're okay with placement bugs in lp not getting comments from gerrit when changes reference them17:58
fungijust make a comment to that effect in the change which switches it over17:58
cdentI think that's the emerging consensus, so yeah, I'll go with that. Thanks for helping come up withe clear strategy17:59
cdentbiab17:59
fungiyou bet18:01
*** kshitija has joined #storyboard18:04
*** mkarray has joined #storyboard18:24
ivyclarkb: I have setup the database with tools/install_test_backend.sh, but the commands still dont work18:49
clarkbivy: they are not returning any response?18:52
ivyThey return a  list of installed packages. Then stop after these 2 lines, *18:55
ivypy35 run-test-pre: PYTHONHASHSEED='3639152057'18:55
ivypy35 runtests: commands[0] | stestr run18:55
ivy*18:55
clarkbdoes `ps -elf | grep stestr` show an stestr process running?18:56
clarkbI believe that stestr is supposed to output test names as they run. fungi diablo_rojo_phon are you able to confirm that?18:56
ivyyes it does shows the stestr process running19:00
clarkbhrm19:12
clarkb(sorry I'm in another meeting now so will be slow for a bit)19:12
ivyNot a problem19:14
ivythanks for helping out. I have to sign off for today. Will continue working on it tomorrow.19:14
*** gouthamr has quit IRC19:20
*** gouthamr_ has joined #storyboard19:20
*** mordred has joined #storyboard19:23
mordredSotK: I'm looking at https://review.openstack.org/#/c/634603 and the python side changes - I have 2 questions19:23
mordredSotK: can you point me to where the auth bit comes for the auth parameter here: https://review.openstack.org/#/c/634603/4/src/app/util/service/upload.js ?19:24
mordredSotK: and what calls get_upload_url here: https://review.openstack.org/#/c/633365/2/storyboard/api/v1/storage/swift_impl.py19:25
mordredSotK: (I'm having trouble stiching together the web user going through the fileupload process, to the webclient requesting an endpoint to upload to, to the file being uploaded19:26
*** talmaqui has joined #storyboard19:32
SotKmordred: the next patch in the webclient series makes a request to /attachments/upload_url (which calls get_upload_url and is added in the next patch in the api series) here: https://review.openstack.org/#/c/633840/7/src/app/stories/controller/story_detail_controller.js@85620:05
mordredSotK: ah. gotcha. thanks!20:10
mordredSotK: so - I'm going to try to make things more complicated here - but I'll leave it all in review ... I think returning the auth_token in the headers is potentially dangerous because it could actually be used by the recipient to take any action on the entire openstack cloud. instead, we can use the tempurl middleware (we've got code that already uses it that can be leveraged) to have get_upload_url20:12
mordredcreate a "tempurl" which is a time-bound url that can be passed back from get_upload_url and the user can post to it and it will only allow posting to the container in question20:12
mordredI'll add both comments as well as either some sample code or links to it20:12
mordred(the structure you have looks great overall and I think will make using tempurl really nice)20:12
mordredfungi: ^^ fyi20:13
fungithanks mordred!20:15
SotKthat makes sense, I was assuming things being configured to have short-lived tokens and an account which can't do much20:15
SotKI hadn't considered the implications if someone decided to use credentials with access to the whole cloud though, using a tempurl sounds like a much more sensible solution20:15
*** jamesmcarthur has quit IRC20:15
mordredSotK: indeed. if it was used with an account that was only used for swift and nothing else it would be fine20:15
fungiyeah, it's a good point though that even if the account permissions are limited, they could still be used to do more than just upload to the supplied url20:16
*** jamesmcarthur has joined #storyboard20:16
mordredSotK: I've been meaning to do something sensibly reusable with the tempurl code for a while - so this will be the motivation to get around to doing that20:16
fungieven if it's merely to upload more things to urls we didn't tell them were okay20:16
mordredfungi: like delete all of the containers and attachments20:16
mordredfungi: or replace their contents with porn20:16
fungiwell, there are swift acls which can be used to limit the scope of commands they're allowed, but yes20:16
fungiso we could probably keep them from deleting things or making container global changes, but we are at least giving them free license to upload to any urls this way20:17
mordredfungi: that only works, aiui, if you're using swift auth and not using keystone20:18
fungiright. is this keystone auth?20:18
mordredas people using swifts via keystoen in openstack clouds, we donm't have that ability20:18
mordredit should be for infra20:18
mordredsupporting swiftauth for people who donmt' have an openstack cloud and are using standalone swift, then those acls will work20:18
mordredbut for us, our clouds are all via keystone20:18
fungigot it20:19
mordredfungi: it's all abundantly complex and clear as mud isn't it?20:19
fungiso if we want to perform local testing of this, we probably want at least keystone in addition to swift20:19
mordredyeah. it would likely be easiest to make a devstack job configured to basically only be running keystone and swift for functional testing20:20
*** jamesmcarthur has quit IRC20:20
SotKI've only tested it with standalone swift, but if the swiftclient docs are trustworthy I *think* it should "just work" when configured for keystone auth instead20:25
SotKmordred: on a related note, I saw some discussion of swiftclient vs openstack sdk, do you have an opinion on that?20:25
mordredI do! I don't believe python-*client should ever be used for any purpose. :) BUT ... I have not tested openstacksdk with standalone swift yet, so I am witholding having a strong opinion on that20:26
mordred(don't let my status as PTL of openstacksdk imply any sort of bias here of course)20:27
mordred;)20:27
SotK:)20:30
malaniHi @SotK @fungi @diablo_rojo!  I am Saurav Malani, 4th-year B.Tech student at IIIT-Hyderabad, India. I am an Outreachy-19 aspirant. I am particularly interested in the cloud-related project. So, I was looking into the project list of OpenStack and out of the listed projects, I found the project idea "StoryBoard Database Query Optimizations" to be interesting & it also aligns with my future goals. I understood the project idea broadly, but20:32
malaniwith the available information, I didn't really understand the how part i.e. how are we going to optimize the database query in the existing database. So, can you please share some more details in this context? I have a little background in kubernetes, cloud technology. Previously, I have submitted a patch in Kubernetes Python-client link: https://github.com/kubernetes/kubernetes/pull/70684.20:32
diablo_rojo_malani, basically you will need to look at how the queries are being done currently and research ways to make them more efficient.20:34
SotKmordred: presumably I should be able to add a "cloud" to the config file which just points at the swift auth url and causes magic to happen when used?20:35
*** diablo_rojo_ has quit IRC20:35
*** kshitija has quit IRC20:36
*** diablo_rojo has joined #storyboard20:36
malanidiablo_rojo_ okay... so can you please guide me on how and where to get started? And, it would be really great if you assign me some beginner bug, to enhance my understanding of the project.20:38
mordredSotK: yes - presumably that should work. but we shoudl try it out20:40
* SotK will do so20:41
mordredSotK: and - in fact, if/when we get it sorted out and show it working, we should maybe set up a functional test job for sdk that runs against a standalone swift20:41
mordredjust to make sure20:41
*** gouthamr_ is now known as gouthamr20:42
*** cdent has quit IRC21:05
*** jamesmcarthur has joined #storyboard21:11
*** zbr|out has quit IRC21:27
*** whoami-rajat has quit IRC21:41
*** jtomasek has quit IRC21:43
*** misaac has quit IRC21:57
*** misaac has joined #storyboard21:57
fungiwe do have all the building blocks already, i think22:02
diablo_rojomalani, the beauty of open source is that you get to choose what you work on :) We have starter tasks tagged with 'low-hanging-fruit'22:11
diablo_rojohttps://storyboard.openstack.org/#!/story/list?status=active&project_group_id=57&tags=low-hanging-fruit22:12
*** misaac has quit IRC22:31
*** jamesmcarthur has quit IRC22:49
*** jamesmcarthur has joined #storyboard23:02
*** jamesmcarthur has quit IRC23:09
*** cmoura has quit IRC23:11
*** cmoura has joined #storyboard23:11

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!