Thursday, 2018-07-05

*** yangyapeng has joined #openstack-mistral01:15
*** bobh has joined #openstack-mistral01:26
*** pgaxatte has joined #openstack-mistral01:56
*** nguyenhai has joined #openstack-mistral01:59
*** bobh has quit IRC02:27
*** pgaxatte has quit IRC04:43
*** pgaxatte has joined #openstack-mistral05:01
*** hardikjasani has joined #openstack-mistral05:20
*** quiquell|off is now known as quiquell05:31
*** josecastroleon has joined #openstack-mistral06:10
*** pgaxatte has left #openstack-mistral06:17
*** quiquell is now known as quiquell|bbl06:35
*** pgaxatte has joined #openstack-mistral06:53
rakhmerovapetrich: yeah, this all looks weird a little bit06:53
rakhmerovapetrich: I'd recommend to talk to Andras06:54
rakhmerovhe's not in IRC unfortunately06:54
rakhmerovyou can send him an email06:54
rakhmerovhe knows this part well06:54
pgaxattehello06:58
pgaxatterakhmerov: I think I have something worth merging with https://review.openstack.org/#/c/579477/06:58
pgaxatteI was thinking about refactoring the policy tests and covering all policies06:59
rakhmerovpgaxatte: hey07:00
rakhmerovok07:00
pgaxattebut I should do this in a different change07:01
pgaxatteshould I open a bug for this?07:02
pgaxatterakhmerov: also I'd like to backport my change down to pike and I have no idea how to do this :)07:03
rakhmerovpgaxatte: bug for what? I see that you already put a link to a LP bug07:04
rakhmerovit's enough07:04
pgaxatterakhmerov: I meant to work on a refactor of the policy tests for all the policies07:05
rakhmerovbut I don't think we can backport it, it doesn't look to be compliant with stable branch policy07:05
rakhmerovonly if we treat it as a security bug or something..07:05
rakhmerovso the flow is: 1) we need to review and merge it into master 2) then we discuss if we can backport it (better wait till Dougal is back from vacation) 3) cherry pick the patch to needed branches07:06
pgaxatteoh damn I really need this and I'm in pike :D07:06
rakhmerovpgaxatte: ooh, yes, for tests it's better to file a bug07:06
rakhmerovsure07:06
rakhmerovpgaxatte: no panic :) Let's first make it work and merge it and discuss the further steps with the team07:07
rakhmerovbtw, it still gives -1 on CI07:07
pgaxatterakhmerov: ok no problem I'll be patient :)07:07
rakhmerovpgaxatte: yeah, I think we'll solve it one way or another )07:07
pgaxattemeanwhile I hope I can continue spending time working on upstream code, I really enjoy this :)07:08
rakhmerovpgaxatte: awesome!07:10
rakhmerovgreat to have you with us07:10
*** yangyapeng has quit IRC07:10
pgaxatte:)07:11
*** gkadam has joined #openstack-mistral07:11
*** quiquell|bbl is now known as quiquell07:16
pgaxatterakhmerov: should my change carry a releasenote?07:30
rakhmerov100%07:31
rakhmerovyes07:31
rakhmerovwhen we backport something it's mandatory07:31
rakhmerovpgaxatte: well, you can send a release note separately if you want07:31
rakhmerovbut it should exist07:31
*** yangyapeng has joined #openstack-mistral07:32
pgaxatteI'll add it now07:32
*** yangyapeng has quit IRC07:34
openstackgerritPierre Gaxatte proposed openstack/mistral master: Add a policy to control the right to publish resources  https://review.openstack.org/57947709:47
*** _Adary has joined #openstack-mistral10:08
*** _Adary has quit IRC10:17
*** _Adary has joined #openstack-mistral10:18
*** amorin has joined #openstack-mistral10:32
*** jlejeune has joined #openstack-mistral10:32
openstackgerritAdriano Petrich proposed openstack/python-mistralclient master: WIP Better output when not sourcing auth  https://review.openstack.org/58034010:38
*** thrash|g0ne is now known as thrash12:12
*** quiquell is now known as quiquell|lunch12:27
*** quiquell|lunch is now known as quiquell12:52
jlejeunehi all12:57
jlejeuneI'm start using mistral and I have some questions about custom actions12:57
jlejeunereading the doc, I see that we need to package our customs actions in mistral package and to reinstall it12:58
jlejeuneam I right ?12:58
jlejeuneI wanted to build a new package to deploy my own actions and to manually define them in database using register_action_class() function13:01
jlejeuneactually it works, my new action is correctly inserted in database and mistral client see it13:02
jlejeunebut to be usable, my custom class action need to be in /usr/lib/python2.7/dist-packages/mistral/actions folder13:04
jlejeuneotherwise mistral fails to import my class13:05
jlejeuneis there any way to define the PATH where mistral looks for defined actions ?13:05
jlejeuneis this blueprint still relevant : https://blueprints.launchpad.net/mistral/+spec/mistral-action-providers ?13:09
jlejeunerakhmerov: ^13:09
thrashjlejeune: Not necessary to put in mistal package13:12
thervejlejeune: https://docs.openstack.org/mistral/latest/contributor/creating_custom_action.html have you read this?13:13
therveThe bit about setup.cfg in particular13:13
jlejeuneof course13:13
therveWell that tells you how to package your actions13:13
thrashjlejeune: Not sure you want to get down the path of manual registration... Better to use mistral-db-manage populate13:14
thrashjlejeune: For instance, tripleo-common uses a bunch of custom actions... https://github.com/openstack/tripleo-common/blob/master/setup.cfg#L71-L15413:15
jlejeuneactually we use python-mistral debian package13:15
thrashjlejeune: That shouldn't matter.13:15
jlejeunehm ok13:16
thrashThe keys are using setup.cfg, restarting mistral services, then mistral-db-manage populate13:16
jlejeuneand we can put our custom actions anywhere ?13:21
thrashjlejeune: By anywhere, do you mean in any python path?13:21
jlejeuneyep13:21
thrashYou can have a separate python module, yes.13:21
jlejeune\o/13:21
jlejeuneinteresting13:22
thrashWe do that very thing with tripleo-common13:22
thrashI think you're having an issue by trying to call register_action_class directly13:22
thrashAt the very least, you should call sync_db instead of register_action_class directly.13:22
jlejeuneno actually it works, I' ve just an error when mistral call this new action13:22
thrashBut as long as your python module is installed in the system properly, with a proper setup.cfg, then mistral-db-manage populate should find it.13:23
jlejeunebut maybe it's related13:23
jlejeuneok13:23
jlejeunetesting it13:23
thrashMaybe try with the mistral-db-manage populate first before trying to do it yourself. :)13:23
jlejeuneyou're right13:23
*** hardikjasani has quit IRC13:30
*** quiquell is now known as quiquell|mtg13:53
openstackgerritayyob proposed openstack/mistral master: add docs for states  https://review.openstack.org/58038914:07
jlejeuneso thrash, it just works :)14:11
thrashjlejeune: :)14:11
jlejeunemany thanks !14:11
thrashjlejeune: no worries! Glad it worked for you!14:12
openstackgerritayyob proposed openstack/mistral master: add docs for states  https://review.openstack.org/58038914:13
*** toure|gone is now known as toure14:17
openstackgerritAdriano Petrich proposed openstack/mistral master: Autogenerate configuration documentation  https://review.openstack.org/57715714:50
*** quiquell|mtg is now known as quiquell|off15:26
openstackgerritjacky06 proposed openstack/mistral master: Pin get-pip.py to 3.2  https://review.openstack.org/58042915:49
*** bobh has joined #openstack-mistral16:17
*** bobh has quit IRC16:41
*** bobh has joined #openstack-mistral16:43
*** bobh has quit IRC16:47
*** thrash is now known as thrash|biab16:58
*** thrash|biab is now known as thrash17:35
*** FL1SK has joined #openstack-mistral17:44
*** gkadam has quit IRC19:32
*** toure is now known as toure|gone21:35

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