Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-11-10

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

All times shown according to UTC.

Time Nick Message
00:05 zhangjn joined #fuel
00:27 gongysh joined #fuel
00:45 eliqiao1 left #fuel
00:59 zhangjn joined #fuel
01:05 EinstCra_ joined #fuel
01:16 EinstCrazy joined #fuel
01:16 thumpba joined #fuel
01:18 jobewan joined #fuel
01:30 EinstCra_ joined #fuel
01:30 zhangjn_ joined #fuel
02:01 devl_ joined #fuel
02:05 jobewan joined #fuel
02:13 tzn joined #fuel
02:13 youellet joined #fuel
02:14 tzn joined #fuel
02:30 jobewan joined #fuel
02:55 thumpba joined #fuel
03:02 bapalm joined #fuel
03:50 jeh joined #fuel
04:22 thumpba joined #fuel
04:25 fedexo joined #fuel
04:36 jerrygb joined #fuel
04:44 ppetit joined #fuel
05:23 jerrygb joined #fuel
05:28 jobewan joined #fuel
05:57 NelsonPR joined #fuel
06:08 javeriak joined #fuel
06:11 Obi-Wan joined #fuel
06:14 devl joined #fuel
06:24 jerrygb joined #fuel
06:24 thumpba joined #fuel
06:51 fzhadaev joined #fuel
06:57 xarses joined #fuel
06:58 xarses joined #fuel
06:59 xarses joined #fuel
07:00 xarses joined #fuel
07:01 xarses joined #fuel
07:02 xarses joined #fuel
07:16 javeriak joined #fuel
07:25 jerrygb joined #fuel
07:25 thumpba joined #fuel
07:30 javeriak joined #fuel
07:32 magicboiz joined #fuel
07:34 penguinolog joined #fuel
07:42 mkwiek07 joined #fuel
07:47 Wida joined #fuel
07:52 EinstCrazy joined #fuel
08:00 samuelBartel joined #fuel
08:10 javeriak joined #fuel
08:11 saibarspeis joined #fuel
08:14 javeriak_ joined #fuel
08:19 EinstCrazy joined #fuel
08:26 jerrygb joined #fuel
08:26 idvoretskyi joined #fuel
08:33 hyperbaba joined #fuel
08:39 devl_ joined #fuel
08:42 devl_ joined #fuel
08:49 mikemowgli joined #fuel
08:52 mikemowgli Hi there! can anybody help me about fuel network templates? I've seen this new feature in Fuel 7 and it looks interesting. The doc is well writen, however, I'm looking to create several external networks and I'm wondering if network templates could do the trick...
09:02 EinstCra_ joined #fuel
09:03 az joined #fuel
09:09 magicboiz joined #fuel
09:11 tkhno joined #fuel
09:19 magicboiz joined #fuel
09:25 EinstCrazy joined #fuel
09:25 magicboiz joined #fuel
09:27 jerrygb joined #fuel
09:28 youellet joined #fuel
09:29 subscope joined #fuel
09:42 magicboiz joined #fuel
09:44 pal_bth joined #fuel
10:17 devl_ joined #fuel
10:21 fzhadaev joined #fuel
10:28 jerrygb joined #fuel
10:30 EinstCra_ joined #fuel
10:32 EinstCr__ joined #fuel
10:35 mohmultihouse joined #fuel
10:35 mohmultihouse Hey!
10:35 tkhno joined #fuel
10:35 mohmultihouse Just a simple question, is it correct that Mirantis Fuel dont support a L3 spine-leaf network?
10:51 javeriak joined #fuel
10:52 fzhadaev joined #fuel
10:54 Chlorum joined #fuel
10:56 neouf joined #fuel
11:01 EinstCrazy joined #fuel
11:10 pal_bth joined #fuel
11:11 javeriak joined #fuel
11:13 Liuqing joined #fuel
11:16 pasquier-s RageLtMan, assuming that you run the latest version of LMA, the collector is now managed by Pacemaker on the controller nodes so you should use 'crm resource {stop|start|restart} lma_collector'
11:19 tkhno joined #fuel
11:21 Chris___ joined #fuel
11:21 Chris___ Hey
11:22 Chris___ Can some1 help me out with something? got bumped into a weird error with no solution what so ever @ internet
11:24 Chris___ "Error running RPC method granular_deploy"
11:25 bpiotrowski Chris___: hi – what release is this?
11:25 Chris___ 7.0
11:26 bpiotrowski also can you give us a diagnostic snapshot/longer log snippet?
11:26 bpiotrowski because the actual error is usually somewhere around the line you posted
11:26 Chris___ Its in a closed environment, but i've seen something similiar in a posted bug report.
11:27 Chris___ Deploy Changes fails on the computes  [555] Error running RPC method granular_deploy: Deployment failed on nodes 4, 1, trace: ["/usr/lib64/ruby/gems/2.1.0/gems/astute-6.1.0/lib/astute/deployment_engine.rb:64:in `block (3 levels) in deploy'",  "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.1.0/lib/astute/deployment_engine.rb:47:in `each_slice'",  "/usr/lib64/ruby/gems/2.1.0/gems/astute-6.1.0/lib/astute/deployment_engine.rb:47:in `block (2
11:27 Chris___ Almost identical to this error.
11:28 Chris___ https://bugs.launchpad.net/fuel/+bug/1450800
11:28 fzhadaev joined #fuel
11:29 asaprykin joined #fuel
11:31 bpiotrowski I think something else causes it, but please report a new bug and attach a diagnostic snapshot if it's possible
11:31 Chris___ Impossible as I mentioned before, its in a closed environment.. isolated.
11:32 Chris___ let's say, military isolated.
11:32 Chris___ can we talk in private?
11:38 bpiotrowski sure
11:39 youellet joined #fuel
11:41 mikemowgli Hi there. Anyone could help me with the network-template new feature? I'm trying to configured several external networks...
11:41 subscope joined #fuel
11:42 jaypipes joined #fuel
11:46 kgalanov Hi Mike. What's the question?
11:46 javeriak_ joined #fuel
11:50 mikemowgli @kgalanov: I'd like to know how to prepare a network-template to create a second external network. How should I create the bridges? the patches? etc... in order to get 2 external network configured in neutron once I deploy with Fuel
11:53 kgalanov Have you had a chance to take a look at templates?
11:53 kgalanov https://github.com/openstack/fuel-docs/tree/master/examples
11:58 mikemowgli yes of course. very interesting. but no example show how to create a new br-ex, br-floating, how to patch them, is a new br-int needed? a new pr-tun?
12:00 mikemowgli and, in a network-template, if I config br-ex and br-ex-2, will this create uatomatically the two physical networks in ml2 config and l3 config?
12:05 mohmultihouse Just a simple question, is it correct that Mirantis Fuel dont support a L3 spine-leaf network?
12:05 xarses joined #fuel
12:32 jerrygb joined #fuel
12:35 fzhadaev joined #fuel
12:39 ClaudeD joined #fuel
12:47 javeriak_ hey guys, whats the best way to enable the target nodes to be able to ssh into fuel directly?
12:47 javeriak_ as a part of the tasks.yaml i mean
13:01 mkwiek1 joined #fuel
13:02 asaprykin_ joined #fuel
13:07 zhangjn joined #fuel
13:24 jerrygb joined #fuel
13:29 Liuqing_ joined #fuel
13:34 subscope joined #fuel
14:06 gals joined #fuel
14:07 gals joined #fuel
14:09 thumpba joined #fuel
14:13 ppetit joined #fuel
14:17 tkhno joined #fuel
14:23 gals joined #fuel
14:23 gomarivera__ joined #fuel
14:23 ppetit joined #fuel
14:25 Liuqing joined #fuel
14:27 gals joined #fuel
14:36 gals joined #fuel
14:42 rgowrishankar joined #fuel
14:44 pumphouse joined #fuel
14:44 smakar_ joined #fuel
14:47 zhangjn joined #fuel
14:52 neouf joined #fuel
14:56 zhangjn joined #fuel
14:57 angdraug joined #fuel
15:22 javeriak joined #fuel
15:23 javeriak joined #fuel
15:28 javeriak_ joined #fuel
15:33 jerrygb joined #fuel
15:48 fedexo joined #fuel
15:56 ppetit joined #fuel
15:57 DaveJ__ joined #fuel
16:02 ppetit joined #fuel
16:07 jerrygb joined #fuel
16:13 jerrygb joined #fuel
16:15 jerrygb_ joined #fuel
16:15 RageLtMan pasquier-s: thank you for the tip. Its still having the rebinding issue though - "Error making runner for aggregator_tcpinput: Initialization failed for 'aggregator_tcpinput': ListenTCP failed: listen tcp <management ip>:5565: bind: address already in use"
16:16 pasquier-s RageLtMan, you're using the master branch right?
16:16 RageLtMan then says "Error reading config: 1 errors loading plugin" directly after "Loading: [watchdog_output]"
16:16 RageLtMan yes
16:16 RageLtMan from about a week ago though
16:16 pasquier-s so we've just found an issue with this watchdog mechanism
16:16 RageLtMan is there a way to update LMA after Fuel deployed it?
16:17 pasquier-s see https://bugs.launchpad.net/lma-toolchain/+bug/1514893
16:17 RageLtMan thank you
16:17 RageLtMan will just removing the file fix it?
16:18 pszypowicz joined #fuel
16:18 pasquier-s yes, try: rm /tmp/lma_collector.watchdog && killall -9 hekad
16:18 RageLtMan hmm, have to run out to meeting, removed the file, told it to reset
16:19 pasquier-s then pacemaker should respawn the process
16:19 RageLtMan service heka stop; service lma_collector stop; rm /tmp/lma_collector.watchdog; crm resource start lma_collector; sleep 60; crm resource status lma_collector
16:19 RageLtMan question about updating LMA post-install stands :) (lifecycle mgmt)
16:20 RageLtMan thank you very much though
16:20 pasquier-s re lifecycle mgmt, this is a broader Fuel question ;-)
16:21 pasquier-s the short answer is that it has to be done manually for now
16:38 subscope joined #fuel
16:44 HeOS joined #fuel
16:44 subscope joined #fuel
16:52 jeblair joined #fuel
16:55 sergmelikyan joined #fuel
16:56 jeblair i have some questions about the fuel ci system...
16:56 jeblair what does verify-fuel-agent do that gate-fuel-agent-pythonXX does not?
16:57 jeblair it _looks_ like verify-fuel-agent just runs tox, and so does gate-fuel-agent
17:00 mwhahaha probably does the same thing, i'm not sure we've adjusted the fuel ci gates to remove the duplicated checks after we created the openstack-infra jobs
17:01 jeblair cool, that would be a great milestone to drop all of the fuel-ci jobs for a project :)
17:01 mwhahaha oh it might still does python 2.6 checks
17:02 jeblair there's a gate-fuel-agent-python26
17:02 mwhahaha yea but i thought those were going away soon
17:02 jeblair true.... let's see when soon is....
17:02 mwhahaha :D
17:03 mwhahaha but yes, we need to cleanup some of the fuel-ci jobs to remove the duplication.
17:04 claflico joined #fuel
17:04 jeblair sometime shortly after november 19, apparently :)
17:05 jeblair so i could see why you would want to keep that one
17:05 jeblair (could probably do with a rename though)
17:07 mwhahaha indeed
17:07 jeblair for this job: https://ci.fuel-infra.org/job/gate-fuel-astute/100/consoleFull
17:08 jeblair i see that it's using cobbler -- is that accessing external systems, or is there a sort of fake local cobbler setup?
17:08 mwhahaha I'll have to double check but I think that's just rake output. I don't think it's a multi host thing
17:08 jeblair (i notice a lot of ip and mac addresses that look fake)
17:09 jeblair also, it took 31 seconds which doesn't sound like multi host :)
17:09 jeblair so i bet that job could be run upstream
17:10 mwhahaha would be likely
17:11 mwhahaha yea that job just runs ./run_tests.sh from the repo
17:12 mwhahaha so it's just ruby unit tests via bundler & rake
17:12 jeblair do you know of any jobs that are multi-host?
17:12 mwhahaha there are, depends on what repo
17:13 jeblair any repo, i'd just like to see an example of one
17:13 mwhahaha sure, sec
17:13 mwhahaha so for fuel-library
17:13 mwhahaha https://review.openstack.org/#/c/220573/
17:13 mwhahaha fuellib_review_pkgs_master_node and master.fuel-library.pkgs.ubuntu.neutron_vlan_ha
17:20 dklenov joined #fuel
17:35 ppetit joined #fuel
17:41 az joined #fuel
17:48 wayneeseguin joined #fuel
17:49 ppetit joined #fuel
18:02 CheKoLyN joined #fuel
18:06 jerrygb joined #fuel
18:16 pszypowicz joined #fuel
18:33 Wida joined #fuel
18:36 angdraug joined #fuel
19:01 jerrygb_ joined #fuel
19:05 jerrygb joined #fuel
19:06 ppetit joined #fuel
19:17 ppetit joined #fuel
19:35 tzn joined #fuel
19:37 tzn joined #fuel
19:39 subscope joined #fuel
19:39 ppetit joined #fuel
20:19 ppetit joined #fuel
20:51 devl_ joined #fuel
20:58 jerrygb joined #fuel
20:59 jerrygb joined #fuel
21:02 tzn joined #fuel
21:03 sergmelikyan joined #fuel
21:12 jerrygb_ joined #fuel
21:45 tzn joined #fuel
22:47 tzn joined #fuel
22:55 BobBall_AWOL joined #fuel
23:04 RageLtMan pasquier-s: o
23:04 RageLtMan i am still seeing the TCP rebind problem and no data coming into LMA: Error making runner for aggregator_tcpinput: Initialization failed for 'aggregator_tcpinput': ListenTCP failed: listen tcp MGT-IP:5565: bind: address already in use
23:08 jerrygb joined #fuel
23:10 bookwar joined #fuel
23:36 youellet joined #fuel
23:48 tzn joined #fuel
23:49 tzn joined #fuel

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