Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel-dev, 2015-01-13

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

All times shown according to UTC.

Time Nick Message
00:13 angdraug just for pdf/pdf_* files
01:40 rmoe joined #fuel-dev
01:48 LiJiansheng joined #fuel-dev
03:09 xarses joined #fuel-dev
03:25 abhirc joined #fuel-dev
04:21 teran_ joined #fuel-dev
04:23 teran__ joined #fuel-dev
04:26 Longgeek joined #fuel-dev
04:31 Longgeek joined #fuel-dev
05:39 Longgeek joined #fuel-dev
05:49 teran joined #fuel-dev
05:49 teran joined #fuel-dev
06:42 Longgeek joined #fuel-dev
06:42 sambork joined #fuel-dev
06:57 taj_ joined #fuel-dev
07:06 dklepikov joined #fuel-dev
07:30 _gryf joined #fuel-dev
07:34 _gryf hey
07:34 _gryf I have a question
07:34 Miouge joined #fuel-dev
07:36 _gryf is it possible to invoke from fuel master node some command to make the other nodes to force running puppetsync?
07:38 omelchek joined #fuel-dev
07:38 alex_bh joined #fuel-dev
07:40 prmtl joined #fuel-dev
07:42 ikalnits_ joined #fuel-dev
07:42 alex_bh joined #fuel-dev
07:47 corepb_ joined #fuel-dev
07:55 e0ne joined #fuel-dev
08:07 Miouge joined #fuel-dev
08:18 dkusidlo joined #fuel-dev
08:20 e0ne joined #fuel-dev
08:27 mescanef joined #fuel-dev
08:29 ikalnits_ joined #fuel-dev
08:30 stamak joined #fuel-dev
08:30 hyperbaba joined #fuel-dev
08:33 HeOS joined #fuel-dev
08:36 salmon_ joined #fuel-dev
08:43 sambork joined #fuel-dev
08:45 dkusidlo joined #fuel-dev
08:49 avorobiov joined #fuel-dev
08:52 mescanef joined #fuel-dev
08:55 Longgeek joined #fuel-dev
09:01 romcheg joined #fuel-dev
09:04 SS-Yuriy joined #fuel-dev
09:05 SS-Yuriy joined #fuel-dev
09:10 EeeBotu New bug #1410119 in fuel: "[BVT] [rabbitmq v5.0.0 module] failed do detect management plugin" [Critical, Confirmed] https://bugs.launchpad.net/bugs/1410119
09:10 EeeBotu New bug #1410117 in fuel: "    mirror/ubuntu: use debootstrap instead of multistrap" [Undecided, New] https://bugs.launchpad.net/bugs/1410117
09:10 EeeBotu New bug #1410101 in fuel: "HA fencing plugin" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1410101
09:17 ikalnits_ joined #fuel-dev
09:20 azemlyanov joined #fuel-dev
09:32 ikalnits_ joined #fuel-dev
09:33 tzn joined #fuel-dev
09:56 e0ne joined #fuel-dev
09:56 dkusidlo joined #fuel-dev
10:07 dancn joined #fuel-dev
10:18 EeeBotu New bug #1410163 in fuel: "Cluster attrubute use_vcenter value is always true" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1410163
10:24 sovsianikov joined #fuel-dev
10:36 asheplyakov joined #fuel-dev
10:37 tzn joined #fuel-dev
10:37 sovsianikov joined #fuel-dev
10:47 monester_laptop joined #fuel-dev
10:56 subscope joined #fuel-dev
11:13 ddmitriev joined #fuel-dev
11:20 sambork joined #fuel-dev
11:21 prmtl joined #fuel-dev
11:31 salmon_ joined #fuel-dev
11:33 EeeBotu New bug #1410210 in fuel: "[systen tests] Fetch logs in tests failed by timeout" [Medium, New] https://bugs.launchpad.net/bugs/1410210
11:41 ykotko joined #fuel-dev
11:42 Miouge joined #fuel-dev
11:49 dkusidlo joined #fuel-dev
11:59 teran joined #fuel-dev
12:01 teran_ joined #fuel-dev
12:08 sambork joined #fuel-dev
12:11 romcheg teran_: Hi, around?
12:17 teran_ rmoe: Hi
12:17 teran_ romcheg: Hi
12:17 teran_ rmoe: sorry :)
12:18 romcheg teran_: We are moving fuel client into a separate repo now
12:19 romcheg teran_: But it's "unit" tests require nailgun to be running.
12:20 romcheg teran_: So we need a jenkins job that does that for every patch set in python-fuelclient repo. Do you think it's possible to do?
12:24 EeeBotu New bug #1410226 in fuel: "Slow hostname resolution on fuel master" [Undecided, New] https://bugs.launchpad.net/bugs/1410226
12:27 romcheg teran_: I filed a bug for that https://bugs.launchpad.net/fuel/+bug/1410234
12:28 seeg hello, can we merge https://review.openstack.org/#/c/132543/ ?
12:36 EeeBotu New bug #1410239 in fuel: "Unable to automatically remove LVM data" [Undecided, New] https://bugs.launchpad.net/bugs/1410239
12:36 EeeBotu New bug #1410234 in fuel: "New Jenkins job for testing python-fuelclient" [High, New] https://bugs.launchpad.net/bugs/1410234
12:44 e0ne joined #fuel-dev
12:46 IvanBerezovskiy joined #fuel-dev
12:47 Rawan joined #fuel-dev
12:49 omolchanov joined #fuel-dev
13:02 skolekonov joined #fuel-dev
13:07 tdubyk joined #fuel-dev
13:15 Longgeek joined #fuel-dev
13:24 Rawan Hello, I wanna ask if there is a command in fuel CLI to verify networks entered under networks tab ?
13:28 apopovych1 joined #fuel-dev
13:30 omolchanov joined #fuel-dev
13:32 romcheg Rawan: Hi, sure
13:33 romcheg It's fuel netword -verify
13:33 romcheg network even
13:44 SergeyLukjanov joined #fuel-dev
13:45 aignatov joined #fuel-dev
13:53 Rawan so it's fuel fuel network -verify ?
13:53 Rawan and what does network even do ?
13:55 romcheg network even basically means that I mistyped the previous message and corrected it :)
13:56 Rawan ooh okay thank you :)
13:56 romcheg Rawan: my pleasure
14:30 EeeBotu New bug #1410280 in fuel: "PXE doesn't working for HP DL380 with broadcom cards" [Undecided, New] https://bugs.launchpad.net/bugs/1410280
14:30 EeeBotu New bug #1410274 in fuel: "Add network configuration into fuel-stats installation info" [High, Confirmed] https://bugs.launchpad.net/bugs/1410274
14:30 EeeBotu New bug #1410262 in fuel: "Fuel-stats http handler for export statistics to the csv" [High, Confirmed] https://bugs.launchpad.net/bugs/1410262
14:32 jaypipes joined #fuel-dev
14:34 abhirc joined #fuel-dev
14:40 omolchanov joined #fuel-dev
14:40 Miouge joined #fuel-dev
14:55 Doudoux joined #fuel-dev
14:56 Doudoux evg: Hello
14:56 Doudoux are you there ?
14:58 mpetason joined #fuel-dev
15:00 julien_ZTE joined #fuel-dev
15:03 romcheg dpyzhov: Hi, aroud?
15:20 evg Doudoux: hello
15:25 romcheg dpyzhov: ping
15:26 dpyzhov pong
15:26 sovsianikov joined #fuel-dev
15:26 dpyzhov romcheg: pong
15:26 romcheg dpyzhov: I'd like to let you know that python-fuelclient repo was created and you have a +2 right there
15:27 romcheg dpyzhov: So please check you're notifications sometimes because only you and I are in the core group ATM
15:28 IvanKliuk romcheg: what is the URI for fuelclient?
15:28 romcheg IvanKliuk: https://github.com/stackforge/python-fuelclient
15:29 salmon_ romcheg: maybe add other core devs from fuel-web to fuel-client
15:30 romcheg salmon_: Othe core guys will be added according generic process in OpenStack community
15:30 IvanKliuk romcheg: are planning to get rid the client from https://github.com/stackforge/fuel-web/tree/master/fuelclient ?
15:30 romcheg IvanKliuk: yes, we are. However, it's required to adjust a build system for that. That is in progress.
15:30 evg Doudoux: I don't see any useful params in the modinfo output we can try exept enabling debuggin. Mb it'll help.
15:30 salmon_ romcheg: generic process?
15:30 dpyzhov romcheg: why does this repo has separate list of core reviewers?
15:31 dpyzhov it should use fuel-core group for that
15:31 evg Doudoux: you've been asked for upgrading module to moden version. Could you try?
15:31 EeeBotu New bug #1410287 in fuel: "Email notification on errors in the fuel-stats" [High, Triaged] https://bugs.launchpad.net/bugs/1410287
15:32 romcheg dpyzhov: Because python-fuelclient is a separate project. Having a core group members of which do not review the code or are not allowed to +2/-2 certain patches is wrong.
15:32 e0ne joined #fuel-dev
15:33 abhirc joined #fuel-dev
15:33 IvanKliuk romcheg: one more question. Are the new changes going to be applied on both of the repos for a some time?
15:33 dpyzhov romcheg: I know and it will be fixed. We will have separate groups for each projects
15:33 romcheg dpyzhov: Adding new members to the group should be done according to the approved process https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess
15:34 dpyzhov romcheg: Excellent, you have a separate group =)
15:34 romcheg dpyzhov: Yup, we will only keep guys that actually do reviews in there
15:35 romcheg IvanKliuk: No, because there's no way to sync them.
15:36 romcheg I'm going to make an alpha release soon and then we'll be able to adjust a build system so it will be possible to add new patches to the build
15:36 dpyzhov romcheg: it will look like hell to have separate elections for each python project in fuel
15:36 IvanKliuk romcheg: so from now, only python-fuelclient is relevant repo and we shouldn't use the code from fuel-web/fuel-client?
15:37 romcheg IvanKliuk: right
15:37 romcheg IvanKliuk: ATM they contain the same code
15:37 IvanKliuk romcheg: awesome! thanks!
15:37 dpyzhov romcheg: have you updated the build system?
15:38 romcheg dpyzhov: Not yet, as I said I'm working on that.
15:38 romcheg The project has just been created
15:38 dpyzhov so at the moment code from the new repo will not be included into the iso. ok
15:39 romcheg We have a hotter hell in fuel-core now when two thirds of the group cannot review one's patch
15:39 romcheg dpyzhov: No, it will not.
15:39 romcheg dpyzhov: I cannot possibly adjust the build system in 5 minutes :)
15:39 bookwar_ dpyzhov, romcheg: please keep us(devops) informed about build system update as we will need to change our custom build tasks to support new variables
15:40 romcheg bookwar_: I post daily updates to the mailing list
15:42 romcheg bookwar_: http://lists.openstack.org/pipermail/openstack-dev/2015-January/054345.html
15:43 bookwar_ romcheg: yes, and add me to reviewers if possible
15:45 romcheg bookwar_: sure, we already have created two repos for the python-fuelclient. Now I think we need to discuss where to take tarballs from
15:46 romcheg bookwar_: One way is to fetch releases from PyPi, the other way is to fetch tarballs from http://tarballs.openstack.org
15:48 bookwar_ romcheg: you mean we will build from release, not from particular commit?
15:48 romcheg For building ISOs we do not need particular commits
15:49 bookwar_ romcheg: we have custom builds whci are made from particular gerrit requests
15:49 bookwar_ do we plan to support custom fuel-client builds?
15:50 romcheg bookwar_: I think we'll have, but atm it's important to adjust what we really need.
15:51 bookwar_ that's kind of defines the way we implement the build. If we download particular version from external storage or download the code and build it in place
15:51 romcheg bookwar_: In regular build we use RPMs for external deps, don't we?
15:53 dpyzhov romcheg: I’m not sure that we should download fuel-client from pypi
15:54 bookwar_ romcheg: yes, so this is the question, should we treat fuel-client as external dependency or part of the project
15:55 dpyzhov it should be part of the project for us
15:55 dpyzhov and we can provide option for external users to download it from pypi
15:56 dpyzhov it means that we need some process of update of pypi version from our code
15:56 romcheg dpyzhov: the spec actually says that we should take it from PyPi. It's been on review for like 3 months :)
15:56 bookwar_ we can add parameter like PATH_TO_FUEL_CLIENT so people can put certain custom version of fuel client and build iso from it
15:57 romcheg bookwar_: Is the build system capable of fetching this from external repos?
15:58 romcheg bookwar_: Shouldn't the build system just take RPMs and be agnostic to how those RPMs were built?
15:58 bookwar_ romcheg: we have variables to specify custom repositories, for example https://github.com/stackforge/fuel-main/blob/master/config.mk#L154
15:59 romcheg bookwar_: Then what RPMs are used for?
16:00 dpyzhov romcheg: please tell me that client will be built from the source in our iso build
16:00 bookwar_ romcheg: we build them during the iso build
16:00 bookwar_ romcheg: just consider the use case: you are developer of the fuel-client, you created huge patch which is not merged yet. And you want to test it. What do you do?
16:01 romcheg bookwar_: So the answer is the following. We are not going to build master on regular basis
16:02 romcheg Mostly because we want to be able to merge updates which break compatibility with previous revisions
16:03 bookwar_ that's ok for normal builds
16:03 romcheg Exactly
16:03 bookwar_ what about custom builds when you do need to build from latest code
16:03 bookwar_ even not merged code
16:04 romcheg Building isos from a tag is what we are going to do. If someone wants to buld a custom build they should be able to specify a required commit or change id.
16:04 romcheg I think that is the matter of one parameter for the build system isn't it?
16:05 romcheg So it should be a field just like for fuel-astute of fuel-main
16:05 dkusidlo_ joined #fuel-dev
16:05 sovsianikov joined #fuel-dev
16:06 romcheg bookwar_: should that work?
16:20 dkusidlo joined #fuel-dev
16:21 romcheg bookwar_: ping :)
16:23 romcheg bookwar_: I would also like to clarify testing the upstream
16:24 angdraug joined #fuel-dev
16:24 romcheg bookwar_: ATM we are not going to use OpenStack CI because we need to establish testing now but the tests must be re-worked for being able to be launched by python-jobs
16:24 romcheg bookwar_: in particular, they require Nailgun API to be accessible.
16:25 romcheg I was writing about this to teran_ ^
16:26 romcheg bookwar_: So we need a job that will checkout Nailgun, run it and launch tests after that
16:27 e0ne joined #fuel-dev
16:28 romcheg bookwar_: I can make a script for that, but someone still should handle job creation
16:33 EeeBotu New bug #1410346 in fuel: "Need Jenkins slave for testing" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1410346
16:33 EeeBotu New bug #1410333 in fuel: "Master node cannot be correctly installed from USB flash drives" [High, Triaged] https://bugs.launchpad.net/bugs/1410333
16:33 EeeBotu New bug #1410332 in fuel: "[ui] deployed nodes aren't marked as 'pending deletion'" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1410332
16:33 EeeBotu New bug #1410328 in fuel: "fuel-agent logs is not in logs UI" [Undecided, In Progress] https://bugs.launchpad.net/bugs/1410328
16:33 EeeBotu New bug #1410325 in fuel: "[ui] Nodes with empty role" [Medium, Confirmed] https://bugs.launchpad.net/bugs/1410325
16:33 EeeBotu New bug #1410316 in fuel: "[ui] At least one controller is required to redeploy environment" [Medium, New] https://bugs.launchpad.net/bugs/1410316
16:38 mescanef joined #fuel-dev
16:40 jobewan joined #fuel-dev
16:58 dshulyak romcheg: evgeniyl__: ikalnitsky: what do you think if we will merge some code to both repos (web and fuelclient), at the same time?
16:58 romcheg dshulyak: Why do we need that for?
16:59 dshulyak 1. i really want it in master 2. python-fuelclient isnt adopted into build process yet
16:59 romcheg dshulyak: why do you want that in master? :)
16:59 dshulyak ehh
16:59 dshulyak because this is very important stuff for every team in our project :)
17:00 dkusidlo joined #fuel-dev
17:00 romcheg dshulyak: so how having it in master helps?
17:01 romcheg dshulyak: fuelclient in master will be incompatible with nailgun in master
17:01 dshulyak romcheg: 1. we need to be able to upload tasks from library 2. we need an interface in cli for debuging/developing new deployment code
17:02 romcheg dshulyak: for that you may do just pip install python-fuelclient
17:02 dshulyak no
17:02 dshulyak we need recent version installed on master during bootstrap
17:02 salmon_ romcheg: when merging stuff to fuelclient will be possible?
17:02 dshulyak current version
17:02 salmon_ romcheg: in days
17:02 romcheg Again, master of python-fuelclient is incompatible with nailgun in master
17:03 romcheg salmon_:  as soon as build system is updated, I achieve it should be the beginning of the next week.
17:03 dshulyak sorry
17:03 dshulyak i cant wait that long
17:03 dshulyak it blocks me and blocks library modularization
17:04 salmon_ romcheg: yeah, to long. romcheg I agree with dshulyak, we should merge to both places
17:04 romcheg Guys, we cannot posibly have that in two plaes
17:04 romcheg places even
17:04 dshulyak romcheg: so what is your proposal:)?
17:05 salmon_ romcheg: blocking fuelclient for a week is to long
17:05 romcheg Because python-fuelclient in its master is incompatible with nailgun in master
17:05 romcheg To speed up the process you guys may help me updating the stuff
17:06 taj_ joined #fuel-dev
17:06 dshulyak wut :)
17:06 dshulyak what stuff?
17:06 romcheg build system for instance
17:06 romcheg atm I'm working on enabling tests for python-fuelclient master
17:07 bookwar_ romcheg: regarding jenkins, we will create job, but we need you to create the test itself and describe the procedure: what to run, and how to run. It should first work locally, and than we implement it in jenkins
17:07 dshulyak you need a better plan really.. you cant block merge of the code while working at basic stuff
17:07 romcheg bookwar_: I will provide a run_tests.sh which does everything
17:07 julien_ZTE joined #fuel-dev
17:08 romcheg dshulyak: I actually can block the code. All my proposals have been reviewed and accepted.
17:08 romcheg dshulyak: You can merge the code to python-fuelclient
17:08 dshulyak it wont really help
17:08 romcheg fuel-web/fuelclient will be deleted as soon as build system is adjusted
17:09 dshulyak that is why i want it in 2 places
17:09 romcheg You cannot use fuelclient's master
17:09 romcheg Because it will be changed constantly
17:10 romcheg For sure you may sync a tag to fuel-web/fuelclient but that won't really help :)
17:10 salmon_ romcheg: we need a solution here :)
17:11 romcheg salmon_: Use it from pypi
17:11 dshulyak we need fuel-client installed on bootstrap time
17:11 romcheg For making  the process faster there is only one solution which is to help me updating the build system
17:12 romcheg dshulyak: how is it getting installed now?
17:12 dshulyak one more time.. what is the problem with merging code at both places?
17:12 romcheg dshulyak: There will be no two places
17:12 dshulyak lets have a call better
17:12 romcheg No call
17:12 dshulyak omg
17:12 romcheg We have an open process
17:13 dshulyak ok.. right now we have 2 places, one is used for build system, and one is new python-fuelclient
17:13 romcheg I'm not going to make and post the script of the call and post it here
17:13 romcheg dshulyak: Exactly, but the build system will be updated to fetch the code from another repo
17:13 dshulyak if we will merge code into fuel-web/client - we will be able to use it right now
17:14 dshulyak and
17:14 romcheg dshulyak: How is the client getting installed now?
17:14 dshulyak wait a moment
17:14 romcheg at the bootstrap time
17:16 dshulyak we are merging code into python-fuelclient - then you updated build system - and new place will be used, what problems do you see here?
17:16 dshulyak we are packaging it during build of the iso and then installing rpm
17:17 romcheg dshulyak: So nothing is going to change for you then
17:17 romcheg dshulyak: Build system will be taking the sources from a separate repo
17:18 romcheg The only difference will be that it won't take master but a tag
17:18 dshulyak for me - no.. because i am able to build iso with all required patches any time
17:18 romcheg dshulyak: And you will be able to do that
17:18 dshulyak i am talking not about me
17:19 romcheg Everyone will be able to build an iso with any commit or an unmerged patch
17:20 dshulyak there is a couple of devepndencies here
17:20 romcheg dshulyak: bookwar_ posted a configuration file ^ which should be changed to introduce a link to the python-fuelclient's repo, commit or gerrit change-id
17:21 dshulyak 1. to merge certain patches in fuel-library - we need fuel-client to be updated in master build
17:22 dshulyak romcheg: can you tell me what will be the problem with plan i sugested?
17:23 romcheg The problem is that master of python-fuelclient is going to loose backward compatibility any time
17:23 dshulyak 2. testing of granular deployment by 3d parties
17:23 dshulyak why is that?
17:24 romcheg dshulyak: Because that was agreed to.
17:24 dshulyak what kind of compatibility?
17:24 dshulyak you mean you will change interface or what?
17:24 romcheg dshulyak: yup
17:24 romcheg One of the cli params might be removed
17:25 romcheg for instance
17:25 dshulyak romcheg: i dont quite understand how it affects my case right now..
17:25 romcheg We want to be able to enroll there updates w/o carrying too much about the rest of the fuel components
17:26 romcheg + we want to let different compoents to use different version of the client
17:27 romcheg + other projects need to use the client and we are not going to let them use master
17:27 dshulyak i dont think that we understood each other..
17:27 dshulyak i am fine with all that
17:28 romcheg If you need to keep fuelclient in fuel-web, you can do that. But you should not keep master there, only a tag
17:33 dshulyak i am not going to keep anything there.. i need code that upload tasks in master during iso build, for that  - until you will enable building from python-fuelclient repo, at the same time this patches will be merged into python-fuelclient (there is no conflicts even)
17:33 dshulyak salmon_: are you following?)
17:34 romcheg For sure you could copy code to wherever you want during the build
17:34 romcheg However, I basically have no time for that.
17:34 romcheg So someone besides me should do that
17:35 romcheg I'm going to make basic testing work and then adjust the build system to take python-fuelclient from a separate repo
17:36 romcheg After that I will remove fuel-web/fuelclient because it won't be used by the build system anymore
17:36 romcheg That is the pnal
17:36 romcheg plan even
17:36 dshulyak :( yes, i a completely agree with that, but why at this time we cannot merge code into both places?
17:37 dshulyak it does not have any conflicts
17:37 rmoe joined #fuel-dev
17:37 romcheg You can merge whatever you want, but please be sure to merge into python-fuelclient first
17:38 dshulyak oh..
17:38 romcheg because after fuel-web/fuelclient is not used anymore it will be deleted
17:38 dshulyak if you said it 40 min earlier - this discussion wont even happen
17:39 romcheg Well, I supposed you were proposing to keep fuel-web/fuelclient forever :)
17:40 romcheg dshulyak: And I suppose for backporting patches from python-fuelclient to fuel-web they will have to go through two review procedures.
17:40 romcheg And it's important to merge them to fuel-web/fuelclient without any changes
17:41 dshulyak yep.. actually i just cherry-picked them
17:41 e0ne joined #fuel-dev
17:41 romcheg should work
17:42 romcheg But again, please make sure to merge them to the new repo first
17:42 romcheg Otherwise they will be lost
17:45 jaypipes joined #fuel-dev
17:45 romcheg Since the new repo is created I'm not aware what's inside fuel-web/fuelclient and going to remove it once it's not used
17:50 romcheg Well, I can call it a day
17:50 romcheg See y'all tomorrow
18:05 abhirc_ joined #fuel-dev
18:07 taj_ joined #fuel-dev
18:07 julien_ZTE joined #fuel-dev
18:10 xarses joined #fuel-dev
18:22 adanin joined #fuel-dev
18:35 EeeBotu New bug #1410399 in fuel: "[osci]Update our current jenkins autobuild-master job" [Undecided, New] https://bugs.launchpad.net/bugs/1410399
18:48 romcheg bookwar_: Please check out this patch https://review.openstack.org/#/c/146950/1/run_tests.sh
18:49 romcheg bookwar_: I guess it would be sufficient for the job to just invoke that script.
18:51 romcheg bookwar_: It's still a WIP but should give the idea
18:51 romcheg joined #fuel-dev
18:53 romcheg joined #fuel-dev
18:53 e0ne joined #fuel-dev
19:15 adanin joined #fuel-dev
19:36 Longgeek joined #fuel-dev
19:48 teran joined #fuel-dev
19:52 julien_ZTE joined #fuel-dev
19:58 sc68cal_ joined #fuel-dev
19:59 teran joined #fuel-dev
20:22 teran_ joined #fuel-dev
20:23 teran__ joined #fuel-dev
20:38 tzn joined #fuel-dev
20:39 EeeBotu New bug #1410471 in fuel: "[image based provisioning] incorrect "device is busy" handling for non-RAID devices" [High, Triaged] https://bugs.launchpad.net/bugs/1410471
21:00 angdraug joined #fuel-dev
21:04 EeeBotu New bug #1410520 in fuel: "Fuel GUI does not detect/show failed node when customized YAML is used" [Undecided, New] https://bugs.launchpad.net/bugs/1410520
21:04 EeeBotu New bug #1410518 in fuel: "Fuel GUI incorrect when YAML is customized" [Undecided, New] https://bugs.launchpad.net/bugs/1410518
21:04 EeeBotu New bug #1410517 in fuel: "Puppet Scripts to Deploy VMDK Cinder Driver do not run" [Undecided, New] https://bugs.launchpad.net/bugs/1410517
21:10 adanin joined #fuel-dev
21:14 e0ne joined #fuel-dev
21:34 dburmistrov joined #fuel-dev
21:34 evgeniyl__ joined #fuel-dev
21:34 asilenkov joined #fuel-dev
21:34 dteselkin joined #fuel-dev
21:34 ruhe joined #fuel-dev
21:34 higgins joined #fuel-dev
21:34 IvanKliuk joined #fuel-dev
21:34 bogdando joined #fuel-dev
21:34 HeOS_ joined #fuel-dev
21:34 jell joined #fuel-dev
21:34 youellet joined #fuel-dev
21:34 artem_panchenko joined #fuel-dev
21:34 okosse joined #fuel-dev
21:34 asledzinskiy joined #fuel-dev
21:34 aleksandr_null joined #fuel-dev
21:34 HeOS joined #fuel-dev
21:34 salmon_ joined #fuel-dev
21:34 SergeyLukjanov joined #fuel-dev
21:34 aignatov joined #fuel-dev
21:34 mpetason joined #fuel-dev
21:34 abhirc_ joined #fuel-dev
21:34 romcheg joined #fuel-dev
21:34 adanin joined #fuel-dev
21:34 e0ne joined #fuel-dev
21:34 tzn joined #fuel-dev
21:34 subscope joined #fuel-dev
21:34 kaliya joined #fuel-dev
21:34 kudryashova joined #fuel-dev
21:34 kat_pimenova joined #fuel-dev
21:34 jkirnosova joined #fuel-dev
21:35 xarses angdraug: https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/cluster_ha.pp#L277-285
21:37 rmoe joined #fuel-dev
21:42 tdubyk joined #fuel-dev
21:42 IvanBerezovskiy joined #fuel-dev
21:42 agordeev joined #fuel-dev
21:42 IgorYozhikov joined #fuel-dev
21:42 tsufiev joined #fuel-dev
21:42 igorbelikov joined #fuel-dev
21:42 DinaBelova joined #fuel-dev
21:42 mrasskazov joined #fuel-dev
21:43 Longgeek joined #fuel-dev
21:43 enikanorov joined #fuel-dev
21:43 EeeBotu joined #fuel-dev
21:43 sbanka joined #fuel-dev
21:43 aliemieshko_ joined #fuel-dev
21:43 enikanorov__ joined #fuel-dev
21:43 brain461 joined #fuel-dev
21:43 zynzel joined #fuel-dev
21:47 nurla joined #fuel-dev
21:47 tnurlygayanov_ joined #fuel-dev
21:50 Longgeek joined #fuel-dev
21:50 obcecado joined #fuel-dev
21:50 barthalion joined #fuel-dev
21:50 meow-nofer joined #fuel-dev
21:50 apalkina joined #fuel-dev
21:50 igajsin joined #fuel-dev
21:50 evg joined #fuel-dev
21:50 consultron joined #fuel-dev
21:50 Samos123 joined #fuel-dev
21:50 izinovik joined #fuel-dev
21:50 seeg joined #fuel-dev
21:50 rvyalov joined #fuel-dev
21:50 akislitsky joined #fuel-dev
21:50 sbog joined #fuel-dev
21:50 holser joined #fuel-dev
21:50 MorAle joined #fuel-dev
21:50 MiroslavAnashkin joined #fuel-dev
21:50 mihgen joined #fuel-dev
21:50 zigo joined #fuel-dev
21:50 vkramskikh joined #fuel-dev
21:50 t_dmitry joined #fuel-dev
21:50 openstackstatus joined #fuel-dev
21:50 SergK joined #fuel-dev
21:53 sc68cal joined #fuel-dev
21:53 jaypipes joined #fuel-dev
21:53 apopovych1 joined #fuel-dev
21:53 _gryf_afk joined #fuel-dev
21:53 aglarendil joined #fuel-dev
21:53 bdudko joined #fuel-dev
21:53 anteaya joined #fuel-dev
21:53 akscram1 joined #fuel-dev
21:53 dshulyak joined #fuel-dev
21:54 dshulyak joined #fuel-dev
21:54 akscram1 joined #fuel-dev
21:54 anteaya joined #fuel-dev
21:54 bdudko joined #fuel-dev
21:54 aglarendil joined #fuel-dev
21:54 _gryf_afk joined #fuel-dev
21:54 apopovych1 joined #fuel-dev
21:54 jaypipes joined #fuel-dev
21:54 sc68cal joined #fuel-dev
21:54 SergK joined #fuel-dev
21:54 openstackstatus joined #fuel-dev
21:54 t_dmitry joined #fuel-dev
21:54 vkramskikh joined #fuel-dev
21:54 zigo joined #fuel-dev
21:54 mihgen joined #fuel-dev
21:54 MiroslavAnashkin joined #fuel-dev
21:54 MorAle joined #fuel-dev
21:54 holser joined #fuel-dev
21:54 sbog joined #fuel-dev
21:54 akislitsky joined #fuel-dev
21:54 rvyalov joined #fuel-dev
21:54 seeg joined #fuel-dev
21:54 izinovik joined #fuel-dev
21:54 Samos123 joined #fuel-dev
21:54 consultron joined #fuel-dev
21:54 evg joined #fuel-dev
21:54 igajsin joined #fuel-dev
21:54 apalkina joined #fuel-dev
21:54 meow-nofer joined #fuel-dev
21:54 barthalion joined #fuel-dev
21:54 obcecado joined #fuel-dev
21:54 Longgeek joined #fuel-dev
21:54 tnurlygayanov_ joined #fuel-dev
21:54 nurla joined #fuel-dev
21:54 zynzel joined #fuel-dev
21:54 brain461 joined #fuel-dev
21:54 enikanorov__ joined #fuel-dev
21:54 aliemieshko_ joined #fuel-dev
21:54 sbanka joined #fuel-dev
21:54 EeeBotu joined #fuel-dev
21:54 enikanorov joined #fuel-dev
21:54 mrasskazov joined #fuel-dev
21:54 DinaBelova joined #fuel-dev
21:54 igorbelikov joined #fuel-dev
21:54 tsufiev joined #fuel-dev
21:54 IgorYozhikov joined #fuel-dev
21:54 agordeev joined #fuel-dev
21:54 IvanBerezovskiy joined #fuel-dev
21:54 tdubyk joined #fuel-dev
21:54 rmoe joined #fuel-dev
21:54 jkirnosova joined #fuel-dev
21:54 kat_pimenova joined #fuel-dev
21:54 kudryashova joined #fuel-dev
21:54 kaliya joined #fuel-dev
21:54 subscope joined #fuel-dev
21:54 tzn joined #fuel-dev
21:54 e0ne joined #fuel-dev
21:54 adanin joined #fuel-dev
21:54 romcheg joined #fuel-dev
21:54 abhirc_ joined #fuel-dev
21:54 mpetason joined #fuel-dev
21:54 aignatov joined #fuel-dev
21:54 SergeyLukjanov joined #fuel-dev
21:54 salmon_ joined #fuel-dev
21:54 HeOS joined #fuel-dev
21:54 aleksandr_null joined #fuel-dev
21:54 asledzinskiy joined #fuel-dev
21:54 okosse joined #fuel-dev
21:54 artem_panchenko joined #fuel-dev
21:54 youellet joined #fuel-dev
21:54 jell joined #fuel-dev
21:54 HeOS_ joined #fuel-dev
21:54 bogdando joined #fuel-dev
21:54 IvanKliuk joined #fuel-dev
21:54 higgins joined #fuel-dev
21:54 ruhe joined #fuel-dev
21:54 dteselkin joined #fuel-dev
21:54 asilenkov joined #fuel-dev
21:54 evgeniyl__ joined #fuel-dev
21:54 dburmistrov joined #fuel-dev
21:54 angdraug joined #fuel-dev
21:54 teran__ joined #fuel-dev
21:54 skolekonov joined #fuel-dev
21:54 aarefiev joined #fuel-dev
21:54 aviramb joined #fuel-dev
21:54 avlasov joined #fuel-dev
21:54 pasquier-s joined #fuel-dev
21:54 dpyzhov joined #fuel-dev
21:54 ikalnitsky joined #fuel-dev
21:54 ricolin joined #fuel-dev
21:54 a_teem joined #fuel-dev
21:54 mkoderer joined #fuel-dev
21:54 dilyin joined #fuel-dev
21:54 Bomfunk joined #fuel-dev
21:54 saline joined #fuel-dev
21:54 justif joined #fuel-dev
21:54 ChanServ joined #fuel-dev
21:54 sanek joined #fuel-dev
21:54 akasatkin joined #fuel-dev
21:54 bookwar_ joined #fuel-dev
21:54 stefan_berg joined #fuel-dev
21:54 docaedo joined #fuel-dev
21:55 xarses joined #fuel-dev
21:55 omolchanov joined #fuel-dev
21:55 vokhrimenko joined #fuel-dev
21:55 meow-nofer_ joined #fuel-dev
21:55 Tatyanka_Leontov joined #fuel-dev
21:55 ogelbukh joined #fuel-dev
21:55 tlbr joined #fuel-dev
21:55 mattymo joined #fuel-dev
21:57 aviramb joined #fuel-dev
21:57 ricolin joined #fuel-dev
21:59 skolekonov joined #fuel-dev
21:59 avlasov joined #fuel-dev
21:59 pasquier-s joined #fuel-dev
21:59 dpyzhov joined #fuel-dev
21:59 ikalnitsky joined #fuel-dev
21:59 mkoderer joined #fuel-dev
21:59 dilyin joined #fuel-dev
21:59 justif joined #fuel-dev
21:59 sanek joined #fuel-dev
21:59 stefan_berg joined #fuel-dev
21:59 docaedo joined #fuel-dev
22:06 obcecado joined #fuel-dev
22:06 barthalion joined #fuel-dev
22:06 meow-nofer joined #fuel-dev
22:06 apalkina joined #fuel-dev
22:06 igajsin joined #fuel-dev
22:06 evg joined #fuel-dev
22:06 consultron joined #fuel-dev
22:06 Samos123 joined #fuel-dev
22:06 izinovik joined #fuel-dev
22:06 seeg joined #fuel-dev
22:06 rvyalov joined #fuel-dev
22:06 akislitsky joined #fuel-dev
22:06 sbog joined #fuel-dev
22:06 holser joined #fuel-dev
22:06 MorAle joined #fuel-dev
22:06 MiroslavAnashkin joined #fuel-dev
22:06 mihgen joined #fuel-dev
22:06 zigo joined #fuel-dev
22:06 vkramskikh joined #fuel-dev
22:06 t_dmitry joined #fuel-dev
22:06 openstackstatus joined #fuel-dev
22:06 SergK joined #fuel-dev
22:10 julien_ZTE joined #fuel-dev
22:47 apopovych1 left #fuel-dev
23:21 mgariepy joined #fuel-dev
23:50 Longgeek joined #fuel-dev
23:55 xarses joined #fuel-dev

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