Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-10-20

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

All times shown according to UTC.

Time Nick Message
00:04 zhangjn joined #fuel-dev
00:32 lawrancejing joined #fuel-dev
00:38 dims_ joined #fuel-dev
01:00 tzn joined #fuel-dev
01:02 zhangjn joined #fuel-dev
02:01 tzn joined #fuel-dev
02:41 dims_ joined #fuel-dev
02:54 lawrancejing joined #fuel-dev
03:42 subscope joined #fuel-dev
03:43 dims_ joined #fuel-dev
04:02 tzn joined #fuel-dev
04:02 lawrancejing joined #fuel-dev
04:17 gongysh joined #fuel-dev
04:45 dims_ joined #fuel-dev
05:01 e0ne joined #fuel-dev
05:26 e0ne joined #fuel-dev
05:47 dims_ joined #fuel-dev
06:03 tzn joined #fuel-dev
06:30 e0ne joined #fuel-dev
06:42 mkwiek1 joined #fuel-dev
06:48 dims_ joined #fuel-dev
06:49 pradiprwt joined #fuel-dev
06:54 adanin joined #fuel-dev
07:09 e0ne joined #fuel-dev
07:11 amnk joined #fuel-dev
07:16 e0ne joined #fuel-dev
07:23 pradiprwt joined #fuel-dev
07:25 pradiprwt joined #fuel-dev
07:49 dims_ joined #fuel-dev
07:51 salmon_ joined #fuel-dev
07:54 tzn joined #fuel-dev
08:09 luqas joined #fuel-dev
08:14 karume joined #fuel-dev
08:18 kozhukalov_ joined #fuel-dev
08:20 luqas joined #fuel-dev
08:47 ekosareva joined #fuel-dev
08:49 hyperbaba joined #fuel-dev
08:51 dims_ joined #fuel-dev
08:52 HeOS joined #fuel-dev
08:56 lawranc__ joined #fuel-dev
08:58 amnk joined #fuel-dev
09:05 luqas joined #fuel-dev
09:05 pradiprwt joined #fuel-dev
09:07 tkhno joined #fuel-dev
09:07 e0ne joined #fuel-dev
09:09 sylwesterB joined #fuel-dev
09:15 lawrancejing joined #fuel-dev
09:19 luqas joined #fuel-dev
09:48 tzn joined #fuel-dev
09:49 dims_ joined #fuel-dev
09:57 yottatsa joined #fuel-dev
09:59 ekosareva joined #fuel-dev
10:11 rpodolyaka_ joined #fuel-dev
10:11 tzn joined #fuel-dev
10:11 tlbr joined #fuel-dev
10:12 subscope joined #fuel-dev
10:16 lawrancejing joined #fuel-dev
10:23 yottatsa joined #fuel-dev
10:24 iberezovskiy joined #fuel-dev
10:27 karume Hi there, just a question: is 'fuel graph' command binded to having a 'tasks.yaml' file? I'm currently working on Fuel 7.0 + new file 'deployment_tasks.yaml'. Trying to download the tasks graph I'm getting '500 Server Error: Internal Server Error (internal server error)', so I'm wondering if either I'm missing some prerrequisite setup or maybe graph is not available when setting the tasks from deployment_
10:28 karume tasks.yaml
10:28 idv joined #fuel-dev
10:30 yottatsa joined #fuel-dev
10:36 adanin joined #fuel-dev
10:41 zerda joined #fuel-dev
10:52 tkhno joined #fuel-dev
10:54 pradiprwt joined #fuel-dev
10:56 pradiprwt joined #fuel-dev
10:58 aglarendil @dshulyak ^^
11:01 dshulyak_ joined #fuel-dev
11:03 Chlorum joined #fuel-dev
11:04 weihan joined #fuel-dev
11:08 dshulyak_ karume: hi, this command depends on the tasks state in database
11:08 dshulyak_ what do you mean by - command binded to having a 'tasks.yaml' file?
11:09 dshulyak_ one possibility is that in new deployment_tasks.yaml you made integrity error which is not validated properly
11:11 amnk joined #fuel-dev
11:46 sylwesterB joined #fuel-dev
11:52 yottatsa joined #fuel-dev
12:08 yottatsa joined #fuel-dev
12:20 tzn joined #fuel-dev
12:24 jaypipes joined #fuel-dev
12:24 neophy joined #fuel-dev
12:33 gongysh joined #fuel-dev
12:33 e0ne joined #fuel-dev
12:34 tzn joined #fuel-dev
12:39 tkhno joined #fuel-dev
12:39 ekosareva joined #fuel-dev
12:44 amnk joined #fuel-dev
12:44 karume joined #fuel-dev
12:45 sylwesterB joined #fuel-dev
12:46 sylweste_ joined #fuel-dev
12:47 karume dshulyak_: "what do you mean by - command binded to having a 'tasks.yaml' file?" <-- I wanted to say that I'm not using tasks.yaml file and I though the problem could be related
12:47 karume dshulyak_: indeed I have some dependency cycles within deployment_tasks.yaml, which I'm trying to solve. Thanks for your help
13:11 ddepaoli joined #fuel-dev
13:19 ddepaoli Hi all. Is it possible to manually start the deployment on a single node?
13:20 zhangjn joined #fuel-dev
13:21 zhangjn joined #fuel-dev
13:22 zhangjn joined #fuel-dev
13:23 zhangjn joined #fuel-dev
13:30 dims_ joined #fuel-dev
13:31 bpiotrowski IMHO no
13:31 bpiotrowski if it has been provisioned, you can run particular tasks there
13:32 bpiotrowski you can add nodes one-by-one and then run 'fuel deploy-changes' but it's probably not what you want
13:42 ddepaoli I can run particular task yes, but it's possible to run all task from beginning? My case: last node (new role node) goes wrong, so I modify the script and related order. I need to avoid deploy compute and controller and so re-deploy only last node
13:45 bpiotrowski guessing now, mattymo surely knows better – either deploy_end or particular role you assigned
13:46 yottatsa joined #fuel-dev
13:47 weihan joined #fuel-dev
13:49 mattymo ddepaoli, you want to do an entire puppet run on exactly one node? fuel node --node 10 --deploy
13:49 mattymo where 10 is the ID of your node
13:49 mattymo it will apply all roles for that node, though
13:51 ddepaoli I tried it, but it keeps still at 0%. So I'm looking for a manually way to direct on the node
13:58 zhangjn joined #fuel-dev
13:59 zhangjn joined #fuel-dev
14:00 zhangjn joined #fuel-dev
14:03 julien_ZTE joined #fuel-dev
14:06 artem_panchenko left #fuel-dev
14:06 artem_panchenko joined #fuel-dev
14:19 karume ddepaoli: not sure but maybe you are looking for: fuel --env <env> node --deploy --node <node-id>
14:23 ddepaoli thanks karume mattymo. I retry that way hoping goes better
14:23 karume ddepaoli: check this https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#deployment , it says that you can both provision or deploy single nodes
14:24 karume it's the same for 6.1 and 7.0
14:42 angdraug joined #fuel-dev
14:56 sbog_ joined #fuel-dev
14:58 iberezovskiy joined #fuel-dev
15:02 angdraug aglarendil: are you on #openstack-meeting-4? your exception handling thread is on the agenda...
15:02 e0ne joined #fuel-dev
15:04 xarses joined #fuel-dev
15:09 dshulyak_ joined #fuel-dev
15:22 aglarendil angdraug: yeah, I am there
15:33 dims__ joined #fuel-dev
15:52 angdraug looks like Emilien is happy to keep that discussion on ML
16:14 karume joined #fuel-dev
16:20 dmitryme Hey library team, we have problem with this CR https://review.openstack.org/#/c/132967/21 which was merged into 7.0
16:20 karume hi again, question about tasks declaration and dependencies: I'm using Fuel 7.0 and the new deployment_tasks.yaml, and I'm getting 'Checking prerequisites failed: Tasks can not be processed because it contains cycles in it.'
16:21 dmitryme in short, it creates ‘fantom’ queus which have no consumer, but do receive messages. Once queus get a lot of messages, RabbitMQ starts to feel bad
16:21 dmitryme please see bug https://bugs.launchpad.net/mos/+bug/1497961 for details
16:21 karume since it's a bit hard to determine where the dependency is, I decided to use the former tasks.yaml (which is working for Fuel 6.1 in the same plugin) and I'm getting the same error :(
16:22 dmitryme aglarendil, ashultz, smakar: ^^ . We should consider reimplementing that feature. Can we discuss that?
16:25 dmitryme aschultz: ^^ sorry, misspelled your name above
16:26 karume dmitryme: (you can use tab key to autocomplete nicknames)
16:27 mwhahaha so what's the feature that we'd be reimplementing?
16:27 dmitryme karume: thanks, didn’t know that my client can do that!
16:28 dmitryme mwhahaha: it is that CR https://review.openstack.org/#/c/132967/21
16:28 mwhahaha right so we were relying on the loss of queues to make rabbitmq happy
16:28 mwhahaha sounds like that's not right
16:29 mwhahaha so that change is restoring queues which there are no consumers for which ultimately leads to performance issues right?
16:29 dmitryme sorry, but I didn’t understand your statement “we were relying on the loss of queues”. What did you expected from RabbitMQ?
16:30 mwhahaha https://bugs.launchpad.net/mos/+bug/1497961/comments/4
16:31 mwhahaha https://review.openstack.org/#/c/132967/21 just adds a dump at the end of the deployment and an import on startup
16:31 dmitryme ah, I see. Indeed OpenStack in general expects that auto_delete queues it creates will not be recreated later by some third party app
16:33 weihan joined #fuel-dev
16:33 karume dshulyak: just in case you know about that; shouldn't the tasks.yaml file work the same for 7.0, since it's not giving dependency cycle problems in 6.1? deployment_tasks.yaml file only contains an empty array
16:33 mwhahaha so we could try and add some exclusions to the dump to prevent overlap but we need to dump/import to ensure we don't lose any custom users or queues that are outside of openstack
16:37 dmitryme mwhahaha: hmm, yes, exclusions will help
16:37 dmitryme I will take a look if that works
16:44 sylwesterB joined #fuel-dev
16:47 kozhukalov_ joined #fuel-dev
16:48 dshulyak_ joined #fuel-dev
17:17 dshulyak_ joined #fuel-dev
17:20 dshulyak_ joined #fuel-dev
17:26 kozhukalov_ joined #fuel-dev
17:28 dims_ joined #fuel-dev
17:29 yottatsa joined #fuel-dev
17:55 sbog_ joined #fuel-dev
18:00 jfluhmann joined #fuel-dev
18:17 yottatsa joined #fuel-dev
18:33 sylwesterB joined #fuel-dev
18:44 tzn joined #fuel-dev
19:12 jobewan joined #fuel-dev
19:38 dshulyak_ joined #fuel-dev
20:01 HeOS joined #fuel-dev
20:09 jobewan joined #fuel-dev
20:22 sylwesterB joined #fuel-dev
20:27 kozhukalov_ joined #fuel-dev
20:51 tzn joined #fuel-dev
20:52 tzn joined #fuel-dev
20:58 sbog__ joined #fuel-dev
21:04 yottatsa joined #fuel-dev
21:06 dshulyak_ joined #fuel-dev
21:35 tzn joined #fuel-dev
21:36 adanin joined #fuel-dev
21:50 sbog_ joined #fuel-dev
21:55 yottatsa joined #fuel-dev
22:11 sylwesterB joined #fuel-dev
22:11 yottatsa joined #fuel-dev
22:14 yottatsa joined #fuel-dev
22:16 sbog_ joined #fuel-dev
22:38 tzn joined #fuel-dev
23:20 xarses joined #fuel-dev
23:42 xarses joined #fuel-dev
23:45 bogdando joined #fuel-dev
23:45 dims joined #fuel-dev

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