Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-11-27

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:04 dpyzhov joined #fuel-dev
00:04 pbrzozowski_ joined #fuel-dev
00:04 nurla joined #fuel-dev
00:04 mihgen joined #fuel-dev
00:04 bogdando joined #fuel-dev
00:04 apalkina joined #fuel-dev
00:04 dpyzhov joined #fuel-dev
00:07 avgoor_ joined #fuel-dev
00:12 zhangjn joined #fuel-dev
00:14 zhangjn joined #fuel-dev
00:59 zhangjn joined #fuel-dev
01:05 iwi joined #fuel-dev
01:45 [HeOS] joined #fuel-dev
02:19 zhangjn joined #fuel-dev
04:04 gongysh_ joined #fuel-dev
04:26 dims joined #fuel-dev
04:33 zhangjn joined #fuel-dev
04:53 kozhukalov__ joined #fuel-dev
05:31 zhangjn joined #fuel-dev
05:32 subscope joined #fuel-dev
05:47 Liuqing joined #fuel-dev
06:25 HeOS joined #fuel-dev
06:34 zhangjn_ joined #fuel-dev
06:35 pasquier-s joined #fuel-dev
06:46 mattymo joined #fuel-dev
06:53 dklenov joined #fuel-dev
07:04 e0ne joined #fuel-dev
07:05 iwi joined #fuel-dev
07:08 bgaifullin joined #fuel-dev
07:35 iwi left #fuel-dev
07:45 xarses joined #fuel-dev
07:58 xarses joined #fuel-dev
07:59 sylweste_ joined #fuel-dev
07:59 xarses joined #fuel-dev
08:06 karume joined #fuel-dev
08:22 salmon_ joined #fuel-dev
08:24 sylwesterB joined #fuel-dev
08:26 pasquier-s joined #fuel-dev
08:26 rlu joined #fuel-dev
08:32 jaranovich joined #fuel-dev
08:32 asilenkov joined #fuel-dev
08:32 ukinau joined #fuel-dev
08:32 pasquier-s joined #fuel-dev
08:32 zhangjn joined #fuel-dev
08:34 ashtokolov joined #fuel-dev
08:35 DinaBelova joined #fuel-dev
08:39 aignatov joined #fuel-dev
08:40 pasquier-s_ joined #fuel-dev
08:47 holser joined #fuel-dev
08:48 salmon_ joined #fuel-dev
09:01 maximov guys, please review this one liner https://review.openstack.org/#/c/249095/ this is for ironic integration, should be merged before FF
09:12 hyperbaba joined #fuel-dev
09:12 ukinau joined #fuel-dev
09:12 tzn joined #fuel-dev
09:12 salmon_ joined #fuel-dev
09:12 pasquier-s_ joined #fuel-dev
09:12 ashtokolov joined #fuel-dev
09:12 jaranovich joined #fuel-dev
09:12 sylwesterB joined #fuel-dev
09:12 dklenov joined #fuel-dev
09:12 dpyzhov joined #fuel-dev
09:12 pbrzozowski_ joined #fuel-dev
09:12 nurla joined #fuel-dev
09:12 mihgen joined #fuel-dev
09:12 bogdando joined #fuel-dev
09:12 apalkina joined #fuel-dev
09:12 ekosareva joined #fuel-dev
09:13 avgoor joined #fuel-dev
09:14 bgaifullin joined #fuel-dev
09:14 xarses joined #fuel-dev
09:16 DinaBelova joined #fuel-dev
09:17 karume joined #fuel-dev
09:19 subscope joined #fuel-dev
09:20 aignatov joined #fuel-dev
09:21 subscope joined #fuel-dev
09:21 asilenkov joined #fuel-dev
09:22 kozhukalov_ joined #fuel-dev
09:23 xarses_ joined #fuel-dev
09:24 avgoor_ joined #fuel-dev
09:24 bgaifullin_ joined #fuel-dev
09:24 zhangjn joined #fuel-dev
09:24 ekosareva_ joined #fuel-dev
09:28 karume_ joined #fuel-dev
09:34 hyperbaba joined #fuel-dev
09:34 ukinau joined #fuel-dev
09:34 tzn joined #fuel-dev
09:34 salmon_ joined #fuel-dev
09:34 pasquier-s_ joined #fuel-dev
09:34 ashtokolov joined #fuel-dev
09:34 jaranovich joined #fuel-dev
09:34 sylwesterB joined #fuel-dev
09:34 dklenov joined #fuel-dev
09:34 dpyzhov joined #fuel-dev
09:34 pbrzozowski_ joined #fuel-dev
09:34 nurla joined #fuel-dev
09:34 mihgen joined #fuel-dev
09:34 bogdando joined #fuel-dev
09:34 apalkina joined #fuel-dev
09:35 artem_panchenko joined #fuel-dev
09:35 e0ne joined #fuel-dev
09:35 ekosareva joined #fuel-dev
09:39 bpiotrowski does anyone have any idea why https://review.openstack.org/#/c/248057/ fails to deploy? deployment graph says that tasks added in the patch are to be executed before fuel_pkgs https://paste.xinu.at/oCOEq/
09:39 IvanKliuk joined #fuel-dev
09:39 bpiotrowski what did I miss there?
09:40 zynzel joined #fuel-dev
09:41 bpiotrowski I checked logs and it looks that these tasks are not executed at all
09:43 bpiotrowski so fuel graph is a little liar apparently
09:44 aignatov joined #fuel-dev
09:45 kozhukalov_ joined #fuel-dev
09:45 e0ne joined #fuel-dev
09:46 DinaBelova joined #fuel-dev
09:47 asilenkov joined #fuel-dev
09:48 bpiotrowski moreover both manifests work just fine when executed manually, and deployment proceeds then…
09:49 xarses joined #fuel-dev
09:53 subscope joined #fuel-dev
09:56 aglarendil bpiotrowski: you might want to talk to @evgenyl_ or @ikalnitsky aboutit
09:57 bpiotrowski I think I know, astute.yaml doesn't have info about "local" repository, so obviously fuel-ha-utils is not found
09:57 bpiotrowski or maybe not… sigh
09:58 bpiotrowski will go to them after I check some things
10:00 javeriak joined #fuel-dev
10:00 skath joined #fuel-dev
10:07 DinaBelova joined #fuel-dev
10:08 karume joined #fuel-dev
10:09 tkhno joined #fuel-dev
10:13 amnk joined #fuel-dev
10:20 zigo joined #fuel-dev
10:20 xarses joined #fuel-dev
10:20 IvanBerezovskiy joined #fuel-dev
10:21 rvyalov_ joined #fuel-dev
10:24 xarses_ joined #fuel-dev
10:24 rvyalov__ joined #fuel-dev
10:32 asaprykin joined #fuel-dev
10:33 DinaBelova2 joined #fuel-dev
10:33 _tzn joined #fuel-dev
10:34 ukinau- joined #fuel-dev
10:34 pbrzozowski joined #fuel-dev
10:35 bpiotrowski nah, it's not executed anyway
10:41 skath joined #fuel-dev
10:42 subscope joined #fuel-dev
10:42 e0ne joined #fuel-dev
10:42 ekosareva joined #fuel-dev
10:42 hyperbaba joined #fuel-dev
10:42 pasquier-s_ joined #fuel-dev
10:42 ashtokolov joined #fuel-dev
10:42 jaranovich joined #fuel-dev
10:42 sylwesterB joined #fuel-dev
10:42 dklenov joined #fuel-dev
10:42 dpyzhov joined #fuel-dev
10:42 nurla joined #fuel-dev
10:42 mihgen joined #fuel-dev
10:42 bogdando joined #fuel-dev
10:42 apalkina joined #fuel-dev
10:45 gongysh joined #fuel-dev
10:46 gongysh joined #fuel-dev
10:46 subscope joined #fuel-dev
10:46 e0ne joined #fuel-dev
10:46 ekosareva joined #fuel-dev
10:46 hyperbaba joined #fuel-dev
10:46 pasquier-s_ joined #fuel-dev
10:46 ashtokolov joined #fuel-dev
10:46 jaranovich joined #fuel-dev
10:46 sylwesterB joined #fuel-dev
10:46 dklenov joined #fuel-dev
10:46 dpyzhov joined #fuel-dev
10:46 nurla joined #fuel-dev
10:46 mihgen joined #fuel-dev
10:46 bogdando joined #fuel-dev
10:46 apalkina joined #fuel-dev
11:03 yottatsa joined #fuel-dev
11:05 romcheg joined #fuel-dev
11:15 javeriak joined #fuel-dev
11:20 maximov joined #fuel-dev
11:29 romcheg joined #fuel-dev
11:30 smakar joined #fuel-dev
11:30 grs joined #fuel-dev
11:31 aglarendil_ joined #fuel-dev
11:32 maximov joined #fuel-dev
11:35 mkwiek joined #fuel-dev
11:35 smakar joined #fuel-dev
11:36 e0ne joined #fuel-dev
11:36 hyperbaba joined #fuel-dev
11:36 pasquier-s_ joined #fuel-dev
11:36 ashtokolov joined #fuel-dev
11:36 jaranovich joined #fuel-dev
11:36 sylwesterB joined #fuel-dev
11:36 dklenov joined #fuel-dev
11:36 dpyzhov joined #fuel-dev
11:36 nurla joined #fuel-dev
11:36 mihgen joined #fuel-dev
11:36 bogdando joined #fuel-dev
11:36 apalkina joined #fuel-dev
11:42 agordeev joined #fuel-dev
11:43 ogelbukh_ joined #fuel-dev
11:43 mkwiek joined #fuel-dev
11:43 romcheg joined #fuel-dev
11:43 evgenyl_ joined #fuel-dev
11:48 aglarendil joined #fuel-dev
11:48 MorAle_ joined #fuel-dev
11:48 bpiotrowski joined #fuel-dev
11:48 kgalanov joined #fuel-dev
11:48 vitaly1 joined #fuel-dev
11:48 fuel-slackbot joined #fuel-dev
11:48 akasatkin joined #fuel-dev
11:48 7F1AA1WWZ joined #fuel-dev
11:48 akislitsky_ joined #fuel-dev
11:48 kozhukalov joined #fuel-dev
11:48 IvanKliuk_ joined #fuel-dev
11:49 yantarou joined #fuel-dev
11:50 smakar joined #fuel-dev
11:52 evgenyl_ joined #fuel-dev
11:57 yantarou joined #fuel-dev
12:01 aglarendil ikalnitsky: could you please help Bartek with this?
12:02 mkwiek joined #fuel-dev
12:02 holser joined #fuel-dev
12:07 kate_ joined #fuel-dev
12:10 agordeev joined #fuel-dev
12:10 mwhahaha joined #fuel-dev
12:11 skath joined #fuel-dev
12:11 aderyugin joined #fuel-dev
12:11 francois_eleouet joined #fuel-dev
12:11 javeriak joined #fuel-dev
12:11 rvyalov_ joined #fuel-dev
12:11 intr1nsic joined #fuel-dev
12:12 ekosareva joined #fuel-dev
12:12 ukinau joined #fuel-dev
12:12 amnk joined #fuel-dev
12:12 DinaBelova joined #fuel-dev
12:12 subscope joined #fuel-dev
12:12 xarses joined #fuel-dev
12:14 xarses joined #fuel-dev
12:19 bpiotrowski evgenyl_, ikalnitsky: to spare you reading the backlog, https://review.openstack.org/#/c/248057/ introduces two new tasks that replace upload_core_repos – they are present in deployment graph (https://paste.xinu.at/oCOEq/) but doesn't seem to be run
12:20 karume joined #fuel-dev
12:21 asaprykin joined #fuel-dev
12:26 subscope joined #fuel-dev
12:26 tatyana joined #fuel-dev
12:36 amnk joined #fuel-dev
12:36 yantarou joined #fuel-dev
12:37 ekosareva_ joined #fuel-dev
12:37 rvyalov__ joined #fuel-dev
12:37 javeriak_ joined #fuel-dev
12:39 feleouet joined #fuel-dev
12:40 mescanef joined #fuel-dev
12:40 agordeev joined #fuel-dev
12:41 tzn joined #fuel-dev
12:41 yottatsa joined #fuel-dev
12:42 romcheg joined #fuel-dev
12:43 tkhno joined #fuel-dev
12:43 ukinau joined #fuel-dev
12:43 francois joined #fuel-dev
12:43 ogelbukh_ joined #fuel-dev
12:43 obcecado joined #fuel-dev
12:44 zhangjn joined #fuel-dev
12:44 skath joined #fuel-dev
12:45 DinaBelova joined #fuel-dev
12:48 maximov joined #fuel-dev
12:49 ddmitriev joined #fuel-dev
12:49 ekosareva joined #fuel-dev
12:50 skath joined #fuel-dev
12:51 javeriak joined #fuel-dev
12:52 aliemieshko_ joined #fuel-dev
12:52 aderyugin joined #fuel-dev
12:59 romcheg joined #fuel-dev
13:04 xarses joined #fuel-dev
13:04 intr1nsic joined #fuel-dev
13:05 maximov joined #fuel-dev
13:05 yantarou joined #fuel-dev
13:07 consultron joined #fuel-dev
13:09 holser joined #fuel-dev
13:09 evgenyl_ joined #fuel-dev
13:09 ogelbukh_ joined #fuel-dev
13:11 ikalnitsky bpiotrowski: you put them into deployment graph
13:11 ikalnitsky therefore, you need to use "groups" instead of "role" in task declaration
13:11 ikalnitsky see other tasks
13:13 smakar joined #fuel-dev
13:14 asaprykin joined #fuel-dev
13:14 skath joined #fuel-dev
13:17 kate_ joined #fuel-dev
13:17 agordeev joined #fuel-dev
13:17 maximov joined #fuel-dev
13:17 bpiotrowski ikalnitsky: thx
13:19 ikalnitsky bpiotrowski: no problem. ping me if there will be more questions
13:22 bpiotrowski ikalnitsky: I don't think a group allows me to achieve what I need? I have to run these two tasks before fuel_pkgs
13:23 ikalnitsky bpiotrowski: em sorry? do you know difference between roles in groups? on deployment level we operate by groups, not roles
13:23 aglarendil ikalnitsky: I guess this comes back to the issue when we cannot use wildcards to catch all the existing groups. this will break existing plugins as you will need to specify things like that for each plugin
13:23 ikalnitsky and it has nothing to do with ordering of tasks.. it's about ordering of node deployment
13:24 kate__ joined #fuel-dev
13:24 smakar joined #fuel-dev
13:24 agordeev_ joined #fuel-dev
13:24 maximov_ joined #fuel-dev
13:24 ikalnitsky aglarendil: then keep these plugins as pre_deployment
13:24 bpiotrowski well, I can't
13:24 bpiotrowski I need access to astute.yaml
13:24 aglarendil ikalnitsky: can we just fix wildcard issue?
13:25 bpiotrowski I got what you meant by groups now, though
13:25 aglarendil It seems to be not so difficult to introduce the simplest wildcards/regexps
13:25 bpiotrowski update_core_repos is hardcoded in nailgun, so it obviously consumes information about repositories directly
13:26 bpiotrowski we don't have that convenience on puppet side
13:27 aglarendil and this is what we need to get rid of - otherwise we are mixing responsibilities between components
13:27 yottatsa joined #fuel-dev
13:27 aglarendil ikalnitsky: what do you think? are you ok with regexps for group names in tasks format?
13:29 asaprykin joined #fuel-dev
13:30 obcecado joined #fuel-dev
13:32 romcheg_ joined #fuel-dev
13:33 ikalnitsky bpiotrowski: wait.. i'm totally confused. you can get access to astute.yaml from both pre-deployment and deployment task. it shouldn't block you at all. but if you want to use deployment tasks, you need to use "groups", not "role".
13:33 aglarendil ikalnitsky: let's just support wildcards/regexps for group names, shan't we ?
13:34 bpiotrowski astute.yaml is not there before deploy_start
13:34 ikalnitsky aglarendil: why do you need "*"? it's awful. but that's might be a holywar.
13:34 ikalnitsky aglarendil: plugin developer may explicitly sspecify these tasks to reuse
13:34 ikalnitsky no need to have awful "*" pattern
13:35 ikalnitsky bpiotrowski: why? i think it's bug then, astute bug. i thought we upload this file before any tasks
13:35 bpiotrowski if we did, that patch would be done week ago :(
13:46 warpc joined #fuel-dev
13:49 ikalnitsky bpiotrowski: i have no idea why you have waited so long. let me check astute
13:50 bpiotrowski https://github.com/openstack/fuel-astute/blob/ed8248db45a20d2e582e0660dc36234dc977e3a2/lib/astute/pre_deployment_actions/upload_facts.rb there, I suppose
13:54 ikalnitsky yep, and it looks like we upload it on pre-deployment stage. so astute.yaml is available before pre-deployment tasks
13:56 bpiotrowski file is certainly unavailable on managed nodes, at least under 'astute.yaml' name
13:58 ikalnitsky according to code, it should be available.
13:58 ikalnitsky warpc: could you please confirm ?
13:58 ikalnitsky evgenyl_: maybe you know?
13:59 evgenyl_ ikalnitsky: I see a huge discussion, could you summarise a question?
13:59 ikalnitsky yep
14:00 ikalnitsky when astute.yaml arrives to nodes?
14:00 ikalnitsky before pre-deployment tasks or after?
14:00 ikalnitsky or somewhere in the middle?
14:00 evgenyl_ ikalnitsky: before task for each role gets executed
14:00 evgenyl_ ikalnitsky: oh
14:01 evgenyl_ ikalnitsky: I'm wrong, before pre-deployment, we did it specifically for plugins
14:01 evgenyl_ ikalnitsky: but symlink /etc/role-name.yaml to /etc/astute.yaml gets linked before each role execution
14:01 evgenyl_ ikalnitsky: so in pre-deployment /etc/role-name.yaml files can be used
14:03 bpiotrowski okay, that clears things up a bit
14:03 ikalnitsky hm.. i thought this line https://github.com/openstack/fuel-astute/blob/master/lib/astute/deployment_engine/granular_deployment.rb#L202 add link /etc/role-name.yaml -> /etc/astute.yaml before pre-deployment stage
14:04 ikalnitsky evgenyl_: could you please comment my lmessage above ^^^ ? and any chance to have astute.yaml before pre-deployment stage?
14:06 warpc ikalnitsky: yes. astute.yaml is avaliable in pre_deployment stage
14:06 evgenyl_ ikalnitsky: basically plugin can create symlink by itself, if we are going to do it automatically, the question is, yaml for which role to symlink?
14:07 evgenyl_ ok, warpc has a new information
14:07 ikalnitsky warpc: if it's available, why bpiotrowski has some problems to access it?
14:07 dims joined #fuel-dev
14:07 evgenyl_ ikalnitsky: it gets created, for random role
14:07 warpc ikalnitsky, evgenyl_ https://github.com/openstack/fuel-astute/blob/master/lib/astute/pre_deployment_actions/initial_connect_facts.rb
14:07 evgenyl_ bpiotrowski: what version of fuel do you use?
14:07 bpiotrowski random newest iso
14:07 bpiotrowski that passed BVT
14:09 warpc bpiotrowski: can you give some more info about it: logs, env?
14:09 bpiotrowski I should have kept an env (but I didn't), but 'find /etc -name *.yaml' gave me nothing, and these manifests failed due to lack of said file
14:09 bpiotrowski I'll try to reproduce it again
14:21 amnk joined #fuel-dev
14:25 dpyzhov joined #fuel-dev
14:32 e0ne joined #fuel-dev
14:37 w_verdugo joined #fuel-dev
14:42 bgaifullin joined #fuel-dev
14:46 amnk joined #fuel-dev
14:48 obcecado joined #fuel-dev
14:48 pasquier-s_ joined #fuel-dev
14:48 ashtokolov joined #fuel-dev
14:48 jaranovich joined #fuel-dev
14:48 sylwesterB joined #fuel-dev
14:48 dklenov joined #fuel-dev
14:48 nurla joined #fuel-dev
14:48 mihgen joined #fuel-dev
14:48 bogdando joined #fuel-dev
14:48 apalkina joined #fuel-dev
14:51 sylweste_ joined #fuel-dev
14:53 pasquier-s joined #fuel-dev
14:54 yottatsa joined #fuel-dev
15:06 bogdando joined #fuel-dev
15:17 IvanBerezovskiy left #fuel-dev
15:27 salmon_ joined #fuel-dev
15:30 jerrygb joined #fuel-dev
15:42 alrick joined #fuel-dev
15:42 romcheg joined #fuel-dev
15:42 maximov_ joined #fuel-dev
15:44 alrick joined #fuel-dev
15:47 sylwesterB joined #fuel-dev
15:52 asaprykin_ joined #fuel-dev
16:05 yottatsa joined #fuel-dev
16:07 pasquier-s joined #fuel-dev
16:09 bogdando joined #fuel-dev
16:11 aglarendil ikalnitsky: this task is a basic task. plugin developers will need to require these tasks explicitly. thus the change proposed by bpiotrowski will break things, although it is trivial
16:14 aglarendil it is not a holy war, it is about filling the gaps
16:18 javeriak joined #fuel-dev
16:32 ekosareva joined #fuel-dev
16:41 jerrygb joined #fuel-dev
16:47 ikalnitsky aglarendil: it's not a gap, it's by design. personally, i believe this is a horrible idea to have patterns. you may affect plugin developers, who wants to have their role as clear as possible. having pattern feature, fuel-library devs may start putting it there and there, without thinking how it will affect plugin developers.
16:49 javeriak joined #fuel-dev
16:50 e0ne joined #fuel-dev
16:51 aglarendil ikalnitsky: well, otherwise we are going to break things completely here. or introduce additional pre-pre-deployment stage. we need to think about it
16:52 ikalnitsky aglarendil: omg. why? why you're trying to make a problem where we don't have one? put it to pre-deployment stage and that's it
16:52 aglarendil we have a problem
16:52 ikalnitsky see conversation above, everything should work
16:52 aglarendil we have tasks in Nailgun which should be in Fuel Library
16:52 ikalnitsky if it doesn't
16:53 ikalnitsky please ping me or warpc
16:53 aglarendil there should be 0 tasks in Nailgun code
16:53 ikalnitsky yeah, i know. and how *patterns* will solve this?
16:53 ikalnitsky it's a completely another issue
16:53 aglarendil I can easily tell a task to run on ALL nodes
16:53 aglarendil ALL deployment groups
16:53 ikalnitsky and?
16:53 ikalnitsky and?
16:54 yottatsa joined #fuel-dev
16:54 ikalnitsky and what? how it solve the problem?
16:54 aglarendil and thus the issue is solved - I do not need to contact plugin developers to change tasks in their plugins
16:54 ikalnitsky have you ever seen why we have a lot of tasks in nailgun?
16:54 ikalnitsky it's not about plugins
16:54 aglarendil because you guys wrote them
16:54 aglarendil task library should be one place
16:54 aglarendil and it is called Fuel Library for now
16:54 ikalnitsky ok
16:54 ikalnitsky come one
16:54 ikalnitsky just make a patch
16:55 ikalnitsky and that's it
16:55 aglarendil and you are python guys and you wrote it in our python repo
16:55 ikalnitsky you completely do not understand things
16:55 aglarendil I do not blame you
16:55 aglarendil may be :-)
16:56 bogdando joined #fuel-dev
16:56 pasquier-s joined #fuel-dev
16:56 asaprykin joined #fuel-dev
16:56 maximov_ joined #fuel-dev
16:56 obcecado joined #fuel-dev
16:56 ashtokolov joined #fuel-dev
16:56 jaranovich joined #fuel-dev
16:56 dklenov joined #fuel-dev
16:56 nurla joined #fuel-dev
16:56 mihgen joined #fuel-dev
16:56 apalkina joined #fuel-dev
16:56 ikalnitsky look at this https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/orchestrator/tasks_serializer.py#L164-L205
16:56 aglarendil so, ikalnitsky can you tell me which things I do not understand?
16:56 aglarendil because I mentioned several things here
16:56 ikalnitsky we spawn different tasks based on os
16:56 ikalnitsky we also spawn apt preferences when needed
16:56 ikalnitsky if you guys will implement it
16:56 ikalnitsky on your side
16:56 ikalnitsky i'll gladly remove this shit from nailgun
16:56 aglarendil ikalnitsky: then we should have this logic data-driven
16:57 aglarendil oh, awesome, that's what we are talking about
16:57 aglarendil and that is what bpiotrowski os working on
16:57 aglarendil we are more than glad to take that s**t from you
16:58 bgaifullin joined #fuel-dev
16:58 aglarendil but some of these tasks need to be run explicitly on ALL the nodes and ALL the roles and we should be able to specify this through tasks metadata, I think
16:58 aglarendil you already have this https://github.com/openstack/fuel-web/blob/54b0a436281c9331f8629990ca7efa7b111631ab/nailgun/nailgun/test/unit/test_stages_task_serialization.py#L419
16:58 aglarendil there is a wildcard
17:00 ikalnitsky aglarendil: you MUST NOT decide for plugin developers which task do you want to run for them. let them decide on their own.
17:01 ikalnitsky you already have a mechanism to run tasks on all nodes - use pre-deployment stuff
17:01 aglarendil you ARE already DOING this IN PRE-POST DEPLOYMENT stage
17:01 aglarendil sorry for CAPS
17:01 aglarendil why it should be different for deployment part of the graph?
17:01 ikalnitsky and that's a fucking problem
17:01 ikalnitsky we shouldn't do it
17:02 ikalnitsky in ideal world, the should be a one deployment graph.. no pre/post stages
17:02 aglarendil we are working on it, btw
17:02 ikalnitsky but everything was done not because of a good life
17:03 aglarendil and what is your suggestion   remove wildcards/regexes forever ?
17:03 aglarendil in new shiny unique graph?
17:04 ikalnitsky in my opinion - yep. it's crazy idea to have wildcares - you will affect others. explicit is better than implicit.
17:05 mattymo it just makes it hard to coexist with other plugins when they rely on some common overridable resources
17:07 ikalnitsky mattymo: you shouldn't override resources. otherwise, it's ok that plugin a do not work with plugin b. it's much better then plugin a needs to remove something that was done by core functionality just because core functionality wants to
17:07 aglarendil well, I think, the only option here is to allow a plugin to extend metadata of other tasks
17:08 mattymo to ikalnitsky's credit, we now can make task references to plugins that may or may not be installed... and plugin A can make certain rules if plugin B is installed
17:08 aglarendil e.g. I should be able to add some dependencies into a graph even for tasks I do not introduce in a plugin
17:08 mattymo at least in UI conditions
17:08 mattymo not sure if the graph permits it
17:08 mattymo my plugin B depends on plugin A, for example, and B needs to run its hiera-override after plugin A's
17:08 ikalnitsky aglarendil: no-no, you shouldn't! what case you want to cover? just introduce a new task, that must be executed before some other task?
17:09 aglarendil it is like puppet resource collectors for dependencies
17:09 aglarendil I should be able to reorder tasks dependencies based on the combination of the plugins
17:10 mattymo ^ that last statement I'm not sure how it would even look in yaml representation
17:10 aglarendil ikalnitsky: we want to cover a case of plugins coexistance
17:10 aglarendil like: plugin A:
17:10 aglarendil task: <id-of-task-from-plugin-B>
17:10 aglarendil requires: <id-of-task-from-plugin-A>
17:11 ikalnitsky what if there's no plugin a?
17:11 aglarendil then this yaml does not exist
17:11 aglarendil it is not being parsed and executed
17:12 omolchanov joined #fuel-dev
17:12 ikalnitsky that's not good to make plugin b know about plugin a .. in general use case.. it might be the case for some rare thing, such as using different backends or something like that.. but..
17:12 ikalnitsky hm, actually, it could be solved by extending "condition" field in tasks
17:13 ikalnitsky so you can check whether plugin exists or not
17:13 ikalnitsky and execute or skip some task
17:14 lezbar joined #fuel-dev
17:15 aglarendil well, actually it is ok to let some plugin explicitly define its requirements for particular plugin
17:15 aglarendil it is explicit (satisfies your requirement) and allows to reorder dependencies (my and mattymo case)
17:16 aglarendil okay, screw you guys, I am going home (c)
17:16 aglarendil have a good weekend everyone
17:24 kozhukalov_ joined #fuel-dev
17:26 omolchanov1 joined #fuel-dev
17:30 alrick joined #fuel-dev
17:34 yottatsa joined #fuel-dev
17:40 javeriak joined #fuel-dev
17:57 kozhukalov_ joined #fuel-dev
18:08 e0ne joined #fuel-dev
18:15 javeriak joined #fuel-dev
18:21 gerst joined #fuel-dev
18:28 aglarendil_ joined #fuel-dev
18:51 dims_ joined #fuel-dev
18:57 tzn joined #fuel-dev
19:16 kozhukalov_ joined #fuel-dev
19:25 sylwesterB joined #fuel-dev
19:25 kozhukalov_ joined #fuel-dev
19:42 e0ne joined #fuel-dev
20:06 ogelbukh_ generally speaking, plugins shouldn't know about each other
20:06 ogelbukh_ but the framework must know if plugins are going to touch the same area
20:07 ogelbukh_ which means that all plugins must end up in some common namespace(s) eventually
20:09 obcecado joined #fuel-dev
20:09 ogelbukh_ both in terms of tasks orchestration/ordering and configuration data precedence
20:12 kozhukalov_ joined #fuel-dev
20:13 dims joined #fuel-dev
20:16 nihilifer1 joined #fuel-dev
21:14 sylwesterB joined #fuel-dev
21:37 krobzaur joined #fuel-dev
21:47 kozhukalov_ joined #fuel-dev
22:06 krobzaur joined #fuel-dev
22:07 HeOS joined #fuel-dev
22:16 krobzaur joined #fuel-dev
23:02 sylwesterB joined #fuel-dev

| Channels | #fuel-dev index | Today | | Search | Google Search | Plain-Text | summary