Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2016-04-07

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

All times shown according to UTC.

Time Nick Message
00:11 dnikishov joined #fuel-dev
00:28 rmoe joined #fuel-dev
02:23 gongysh joined #fuel-dev
02:33 gongysh joined #fuel-dev
03:02 xarses joined #fuel-dev
03:09 gongysh joined #fuel-dev
03:17 dnikishov joined #fuel-dev
03:32 gongysh joined #fuel-dev
04:09 zhsj_ joined #fuel-dev
04:09 zhsj_ left #fuel-dev
04:25 javeriak joined #fuel-dev
04:38 askb joined #fuel-dev
05:19 gongysh joined #fuel-dev
05:39 javeriak joined #fuel-dev
07:14 javeriak joined #fuel-dev
07:51 pbelamge joined #fuel-dev
08:00 HeOS joined #fuel-dev
08:07 yassine__ joined #fuel-dev
08:28 openstackstatus joined #fuel-dev
08:28 skolekonov joined #fuel-dev
08:30 openstackstatus NOTICE: jobs depending on npm are now working again
08:46 salmon_ joined #fuel-dev
08:50 e0ne joined #fuel-dev
09:12 pbelamge joined #fuel-dev
09:15 ekosareva_ joined #fuel-dev
09:22 javeriak joined #fuel-dev
09:36 nadya joined #fuel-dev
10:44 xwizard joined #fuel-dev
10:44 xwizard hi there
10:44 gongysh joined #fuel-dev
10:44 xwizard could you please review the fix https://review.openstack.org/#/c/301769/ ?
10:49 xwizard Thank you :)
11:43 nadya joined #fuel-dev
11:58 javeriak joined #fuel-dev
12:25 skolekonov joined #fuel-dev
13:14 javeriak joined #fuel-dev
13:15 rmoe joined #fuel-dev
13:15 xarses joined #fuel-dev
13:15 xarses joined #fuel-dev
13:47 dnikishov joined #fuel-dev
13:58 ekosareva_ joined #fuel-dev
14:34 javeriak joined #fuel-dev
14:49 javeriak_ joined #fuel-dev
14:57 javeriak joined #fuel-dev
15:11 yottatsa joined #fuel-dev
15:18 javeriak joined #fuel-dev
15:27 krobzaur joined #fuel-dev
15:31 bookwar mattymo: do you have a bug for uca failures? should i file one?
15:48 xwizard and this is the fix for stable branch https://review.openstack.org/#/c/302668
15:49 xwizard please review ^^ and merge :) Thank you!
15:52 grimlock86 joined #fuel-dev
15:53 grimlock86 Does anyone know if there's a way in Fuel 9 to download an ordered list of tasks from the deployment graph rather than producing a graphviz file?  I need to build a dependency graph for a 3rd party integration and there's absolutely no way to make any sense of the graphviz graph that's produced.
15:54 grimlock86 I can get the yaml file of the deployment tasks but it's not in order and it's like 5k lines long.
16:01 mattymo` joined #fuel-dev
16:02 javeriak joined #fuel-dev
16:02 xarses joined #fuel-dev
16:02 amnk joined #fuel-dev
16:03 asvechnikov joined #fuel-dev
16:04 angdraug joined #fuel-dev
16:08 rvyalov_ joined #fuel-dev
16:09 dnikishov joined #fuel-dev
16:09 e0ne joined #fuel-dev
16:16 apopovych joined #fuel-dev
16:29 amnk joined #fuel-dev
16:29 aglarendil grimlock86: there are 3 ways to get graph in different shapes. 1st one is the tasks.yaml not resolved into the nodes, you can do it with fuel2 graph cli utility
16:30 aglarendil 2nd one is via api of serialized_tasks handler
16:30 aglarendil it is more detailed and resolved into the nodes, but it's not yet a graph as the graph is getting built by astute
16:30 asvechnikov joined #fuel-dev
16:30 aglarendil 3rd one is astute dot file
16:30 aglarendil we are working currently to convert the 3rd one into a dot file with cli utility
16:31 aglarendil the final graph is processed by astute by simple traversal with weights for tasks
16:31 aglarendil the more tasks depend on the particular task, the higher the weight is, so that it gets executed earlier to unblock other nodes
16:31 aglarendil each same-node dependencies add 1 to the weight
16:31 aglarendil each cross-node adds 10 to the weight
16:32 aglarendil calculation is recursive
16:32 aglarendil if you want to specify an order of tasks, you need to do it explicitly
16:32 aglarendil btw, this is all about task-based deployment, role-based is the same as earlier
16:44 javeriak_ joined #fuel-dev
17:07 _ody joined #fuel-dev
17:09 amnk_ joined #fuel-dev
17:30 grimlock86 @aglarendil thank you.  Is checking the priority in astute.yaml for which tasks go when going to be fairly accurate then?  Just wanting to make sure the priorities in astute.yaml roughly correspond to the order they'll be run in
17:42 lezbar joined #fuel-dev
17:53 e0ne joined #fuel-dev
17:56 xarses joined #fuel-dev
18:00 mgariepy joined #fuel-dev
18:08 aglarendil grimlock86: it depends on the engine you usr
18:08 aglarendil New tbd traverses graph in astute
18:09 aglarendil It is faster better written and enables lcm
18:10 grimlock86 oh. well i'm basically needing to get an order of puppet manifests to include in a 3rd party lcm integration.
18:11 aglarendil Old one granular deployment or role-based deployment is going to be deprecated. If you use it,  then nodes (more accurately, roles) with different  priorities are processed consequently, with the same - in parallel
18:12 grimlock86 okay. so the priorities in astute.yaml is only valid for the old granular deployment then?
18:12 grimlock86 If that's the case, what would you recommend would be the best way to get a list from the new task based deployment?
18:13 e0ne joined #fuel-dev
18:13 grimlock86 I'm supposed to be done with the code for organizing all the manifests by the end of tomorrow so I just need to find some fast-ish way of being able to at least have a pretty good idea of what happens and in what order for a given deployment.
18:15 aglarendil I described it in the messages above. It is graph traversal. Nodes can have cross dependencies
18:16 aglarendil There is no more than one task per node each time
18:17 aglarendil Task gets run when all its dependencies are resolved  and it is chosen by astute for execution according to its weight
18:17 aglarendil If it has failed deps, it is not executed at all
18:18 aglarendil You can check dot file stored by astute to look at the graph
18:18 aglarendil If you need to add deps, you just add them. Either cross dependencies or old requires/required_for
18:19 aglarendil You can check task based blueprint with its related patch sets in ost gerrit out
18:22 aglarendil You can also ask other guys from fuel enhancement team for help and look into fuel plugins related projects parches for examples of how to support TBD
18:23 aglarendil Note: TBD is turned off if there is at least one task in the task (except for stages/groups) list with < 2.0.0 version
18:23 aglarendil So your plugin seems to use old deployment
18:24 aglarendil I gotta go. I may be online in a couple of hours
18:27 aglarendil grimlock86: ^^ I hope I answered your questions
18:40 grimlock86 yep, thank you
18:44 angdraug joined #fuel-dev
19:00 e0ne joined #fuel-dev
19:57 salmon_ joined #fuel-dev
21:11 e0ne joined #fuel-dev
21:39 cartik joined #fuel-dev

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