Perl 6 - the future is here, just unevenly distributed

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

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

All times shown according to UTC.

Time Nick Message
01:39 LiJiansheng joined #fuel-dev
02:14 abhirc joined #fuel-dev
02:16 ricolin joined #fuel-dev
02:17 ricolin guys I need some reviewer
02:17 ricolin https://review.openstack.org/#/q/topic:bp/fuel-with-existed-ldap,n,z
02:20 ricolin thanks
02:47 ilbot3 joined #fuel-dev
02:47 Topic for #fuel-dev is now #fuel-dev Fuel dev docs http://docs.mirantis.com/fuel-dev/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel-dev/ | gerrit traffic @ #fuel-tracker
03:55 abhirc joined #fuel-dev
04:01 alex_bh joined #fuel-dev
04:15 Longgeek joined #fuel-dev
04:17 LiJiansheng joined #fuel-dev
05:23 LiJiansheng joined #fuel-dev
05:39 lee__ joined #fuel-dev
06:06 LiJiansheng joined #fuel-dev
06:09 LiJiansheng joined #fuel-dev
06:15 _gryf joined #fuel-dev
06:20 _gryf joined #fuel-dev
06:23 prmtl joined #fuel-dev
06:32 dklepikov joined #fuel-dev
06:48 sambork joined #fuel-dev
07:05 Miouge joined #fuel-dev
07:06 monester_laptop joined #fuel-dev
07:27 alex_bh joined #fuel-dev
07:31 omelchek joined #fuel-dev
07:32 dshulyak_ joined #fuel-dev
07:47 Krast joined #fuel-dev
07:50 sambork joined #fuel-dev
07:51 prmtl joined #fuel-dev
07:52 prmtl joined #fuel-dev
08:02 e0ne joined #fuel-dev
08:13 pasquier-s joined #fuel-dev
08:13 IvanBerezovskiy joined #fuel-dev
08:15 asledzinskiy joined #fuel-dev
08:29 dshulyak_ joined #fuel-dev
08:33 sambork joined #fuel-dev
08:34 hyperbaba_ joined #fuel-dev
08:40 corepb_ joined #fuel-dev
08:41 salmon_ joined #fuel-dev
09:05 stamak joined #fuel-dev
09:13 kaliya hi, we're building a custom ISO, we get the following http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom.ubuntu.bvt_2/358/consoleText what could be the problem here?
09:25 monester_laptop joined #fuel-dev
09:25 ikalnitsky bookwar_: nurla: any ideas about kaliya issue? (see above)
09:38 romcheg joined #fuel-dev
09:39 adrianstoica joined #fuel-dev
09:39 adrianstoica left #fuel-dev
09:42 romcheg dpyzhov: Hi, u around?
09:43 romcheg dpyzhov: Could you please clarify the status of https://bugs.launchpad.net/fuel/+bug/1411710 ?
09:43 romcheg dpyzhov: If you cannot do that now it's better to reassign it. We need that badly
09:45 azemlyanov joined #fuel-dev
09:48 kivio joined #fuel-dev
09:52 mescanef joined #fuel-dev
09:54 ddmitriev joined #fuel-dev
09:58 dshulyak aglarendil: please merge this https://review.openstack.org/#/c/142454/ https://review.openstack.org/#/c/144279/
10:15 apalkina Instance has status 'error' and I don't see any errors in logs. Could someone look at my environment?
10:18 romcheg dshulyak: Hi! Do you know who else can help me with the ISO-build script?
10:18 dkusidlo joined #fuel-dev
10:19 igajsin joined #fuel-dev
10:23 e0ne joined #fuel-dev
10:24 dshulyak romcheg: hi, maybe someone from osci will have time to do it, try to ask rvyalov about this
10:24 romcheg rvyalov ^
10:25 romcheg If you're around, could you please take a short look at &&
10:25 romcheg >>
10:25 romcheg Oh sh… ^^
10:25 barthalion ↑ here, take this
10:26 barthalion it's dangerous to go alone
10:27 ChrisNBlum joined #fuel-dev
10:29 rvyalov romcheg: hi
10:30 romcheg rvyalov: Good morning!
10:30 dshulyak sambork: prmtl: ikalnitsky: evgeniyl___: please take a look at this patch https://review.openstack.org/#/c/146874/
10:30 romcheg rvyalov: Did you work with the iso-make srcipts?
10:31 rvyalov yes
10:31 romcheg rvyalov: Do you have time/resources for taking a look at https://bugs.launchpad.net/fuel/+bug/1411710 ?
10:32 rvyalov ok
10:45 ikalnitsky joined #fuel-dev
10:50 bogdando please review https://review.openstack.org/#/c/147897. Critical fix for murano instance of rabbitmq
10:53 e0ne joined #fuel-dev
11:25 salmon_ joined #fuel-dev
11:28 sambork joined #fuel-dev
11:29 prmtl joined #fuel-dev
11:56 corepb_ joined #fuel-dev
11:58 asilenkov ^^holser could you pls take a look at https://bugs.launchpad.net/mos/+bug/1378212 - pacemaker stuff. We have our BVT tests broken badly until we merge it.
12:10 ruhe asilenkov: is this also a reason for failures in http://jenkins-product.srt.mirantis.net:8080/view/6.1/job/6.1.test_staging_mirror/ ?
12:13 dkusidlo joined #fuel-dev
12:27 kaliya bookwar_: nurla ideas? http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom.ubuntu.bvt_2/358/consoleText
12:29 corepb_ joined #fuel-dev
12:40 ChrisNBlum joined #fuel-dev
12:43 ChrisNBlum joined #fuel-dev
12:44 ChrisNBlum joined #fuel-dev
12:47 ChrisNBlum joined #fuel-dev
12:51 ChrisNBlum joined #fuel-dev
12:51 bookwar_ romcheg: i am reading https://review.openstack.org/#/c/146950/5/run_tests.sh,cm In obtain_nailgun it looks like you fetch a commit but then checkout on top of it, overriding the data back to master branch. Shouldn't it be the opposite way - checkout first and fetch on top if needed?
12:51 Rawan joined #fuel-dev
12:51 Rawan when displaying tasks fuel done using cli, i noticed that we have 2 tasks one is called deploy and the other is deployment, what is the difference between them ?
12:52 mattymo deploy contains 2 subtasks: provisioning and deployment (puppet apply and follow-up tasks)
12:53 ChrisNBlum joined #fuel-dev
12:54 bookwar_ prmtl: i've posteds small comment about the jenkins job. But we need to define the strategy - how do we choose version of the nailgun code used to test fuelclient. Do we fix and hardcode it or do we use the latest master every time?
12:56 romcheg bookwar_: it's possible to check out the specific commit with -c option
12:56 ChrisNBlum joined #fuel-dev
12:57 sambork joined #fuel-dev
12:58 romcheg bookwar_: For checking out to the latest fetched commit it's possible to set -c FETCH_HEAD
12:58 romcheg bookwar_: Or ofc one can use appropriate environment vars
13:00 ChrisNBlum joined #fuel-dev
13:01 bookwar_ romcheg: if i set $fetch_repo and $fetch_refspec variables, but don't set $fuel_commit variable, the obtain_nailgun() function will produce 'master' branch, not the refspec i asked for
13:01 dshulyak_ joined #fuel-dev
13:03 ChrisNBlum joined #fuel-dev
13:03 Rawan is there a general form or some examples for Jenkins jobs for fuel ?
13:03 romcheg bookwar_: well, it's possible to set FETCH_HEAD  by default if refspec or even if external repo ($fetch_repo) is specified
13:06 e0ne joined #fuel-dev
13:06 ChrisNBlum joined #fuel-dev
13:08 asilenkov ^^ruhe yeah all 6.1 centos is in brocken state now. It is pacemaker related. We have a patch but it is not merged yet
13:09 ChrisNBlum joined #fuel-dev
13:11 bookwar_ Rawan: we have many jenkins jobs, builds, system tests, unit tests..
13:12 bookwar_ Rawan: you can take a look here https://review.fuel-infra.org/gitweb?p=fuel-infra%2Fjenkins-jobs.git;a=summary for some of jenkins configurations we create vi jenkins-job-builder
13:13 ChrisNBlum joined #fuel-dev
13:14 prmtl joined #fuel-dev
13:14 dshulyak_ joined #fuel-dev
13:14 sambork joined #fuel-dev
13:16 ChrisNBlum joined #fuel-dev
13:19 ChrisNBlum joined #fuel-dev
13:22 ChrisNBlum joined #fuel-dev
13:25 ChrisNBlum joined #fuel-dev
13:25 romcheg bookwar_: There is an easy workaround for this issue (setting -c or $fuel_commit to fetch_head). I'll file a bug for that 'cuz atm and fix this a big later
13:27 abhirc joined #fuel-dev
13:28 ChrisNBlum joined #fuel-dev
13:31 ChrisNBlum joined #fuel-dev
13:34 ChrisNBlum joined #fuel-dev
13:35 sbog Hi guys. Can anyone guess why I cannot forward library puppet modules thru UPLOAD_MANIFESTS and UPLOAD_MANIFESTS_PATH when deploy new env by devops framework?
13:36 sbog first variable is True, second have a right path inside. And it worked couple weeks ago. But now it isn't. Why?
13:37 ChrisNBlum joined #fuel-dev
13:40 ChrisNBlum joined #fuel-dev
13:45 IvanBerezovskiy left #fuel-dev
13:46 ChrisNBlum joined #fuel-dev
13:48 IvanBerezovskiy joined #fuel-dev
13:49 ChrisNBlum joined #fuel-dev
13:50 Rawan bookwar: Thank you :)
13:52 ChrisNBlum joined #fuel-dev
13:55 bogdando I have a question about custom ISO build. How should I include corosync-2.3.3 into custom ISO? I cannot see it at http://fuel-repository.mirantis.com/fwm/6.1/ubuntu/pool/main/, but it was merged according to the related bug  https://bugs.launchpad.net/mos/+bug/1376600
13:55 ChrisNBlum joined #fuel-dev
13:57 bogdando https://bugs.launchpad.net/mos/+bug/1376600/comments/39 says it was placed to the primary repository
13:57 bogdando RPM repository URL: http://osci-obs.vm.mirantis.net:82/centos-fuel-6.1-stable/centos
13:57 bogdando but it is still not clear how to include this repo to my ISO. Should I do the same way as for not merged pacemaker packages https://bugs.launchpad.net/mos/+bug/1378212/comments/28 here?
13:58 ChrisNBlum joined #fuel-dev
13:58 bogdando sorry, wrong link about public repo, I mean centos one http://fuel-repository.mirantis.com/fwm/6.1/centos/os/x86_64/Packages/
13:59 dkusidlo joined #fuel-dev
14:00 barthalion they should be in staging repo, at least they were on friday
14:00 barthalion but if staging.bvt.iso fails, packages are not moved
14:01 ChrisNBlum joined #fuel-dev
14:02 bogdando barthalion, understood. It is ok they are not moved, that would have been a disaster yet ;) But how should I include staging mirrors, should I just add more repos as a param?
14:02 bogdando barthalion, I mean that OSCI bot notes about merged / NOT are a bit confusing
14:02 bookwar_ bogdando: you can use MIRROR_BASE parameter for custom build and set it to latest staging repo
14:03 bogdando bookwar_, ok, so I should just ignore these merged / NOT merged comments and just provide all the repos I want?
14:04 bookwar_ the process look like this: 1) build packages into its own repo 2) merge package into OBS primary repo 3) build staging mirror from OBS primary repo 4) set this mirror as stable and use to build main iso
14:04 ChrisNBlum joined #fuel-dev
14:05 bookwar_ bogdando: OSCI bot posts message about step 2)
14:05 barthalion bogdando: I guess so
14:06 bogdando thanks, now it seems much more clean )
14:07 ChrisNBlum joined #fuel-dev
14:08 bogdando bookwar_, is step 5 is publish them to public mirrors?..
14:10 ChrisNBlum joined #fuel-dev
14:11 bookwar_ bogdando: we have public mirrors at step 3), these are staging mirrors and they are located under http://fuel-repository.mirantis.com/fwm/files/ . At step 4) we just make a symlink from http://fuel-repository.mirantis.com/fwm/6.1/ to one of the http://fuel-repository.mirantis.com/fwm/files/6.1-<timestamp> repos as soon as it passes the 'staging bvt tests'
14:12 omelchek joined #fuel-dev
14:12 omelchek left #fuel-dev
14:13 enikanorov joined #fuel-dev
14:13 ChrisNBlum joined #fuel-dev
14:16 ChrisNBlum joined #fuel-dev
14:19 ChrisNBlum joined #fuel-dev
14:23 bogdando bookwar_, thanks a lot
14:31 e0ne joined #fuel-dev
14:34 amnk joined #fuel-dev
14:39 dkusidlo joined #fuel-dev
14:40 mstrukov joined #fuel-dev
14:44 mstrukov joined #fuel-dev
14:59 miroslav_ joined #fuel-dev
15:01 Guest58673 left #fuel-dev
15:01 Guest58673 joined #fuel-dev
15:03 seeg dshulyak, ping :)
15:04 dshulyak evgeniyl___: ikalnitsky: guys, join the discussion if you are available)
15:04 dshulyak regarding seeg: if i understood correctly your proposal is fetch all tasks in client
15:04 dshulyak https://review.openstack.org/#/c/146874/
15:05 dshulyak seeg: and if there is skip argument provided - we are filtering some tasks right in client
15:05 dshulyak skip flag
15:05 seeg that's right
15:05 seeg we can add fancy stuff like skip or only in cli, API works the same all the time
15:06 dshulyak but then we need to implement complex data structure in client, and basically duplicate everything we have in nailgun right now
15:07 seeg hm, what complex structure? just remove the task that's skipped, that's all
15:07 dshulyak seeg: not really, what if i want to execute only tasks that are related to pre_deployment stage
15:07 dshulyak and this is kindof real requirement
15:07 dshulyak we will need to filter by stage
15:08 seeg so? doesn't API return the stage of task?
15:08 mpetason joined #fuel-dev
15:09 dshulyak seeg: next what we are going to do, is to implement - execute graph up to some point
15:09 dshulyak like end_at
15:10 seeg this is not specified in the review
15:10 seeg in case you want more complicated stuff I guess this could be split into separate handlers then
15:10 evgeniyl___ seeg: agree with dshulyak at some point you'll have to reimplement the graph parsing logic in your client
15:10 seeg I'm not a fan of creating handlers that can do all
15:11 seeg what if you specify both skip, only end_at and whatever? this handler becomes a small monster :)
15:11 seeg or any combination of these
15:11 rmoe joined #fuel-dev
15:12 corepb_ joined #fuel-dev
15:13 dshulyak as example: deployment all tasks from pre_deployment stage but skip restart_rados
15:13 dshulyak and at some point there will be lots of tasks
15:14 dshulyak with plugins, etc..
15:14 seeg what if restart_rados has other dependencies? you'll skip them too i guess, this way the handler is not predictable
15:14 dshulyak no skip_tasks operates as it says, without removing any edges and nodes in graph for that edges
15:15 dshulyak my point is - they are composable
15:16 dshulyak if you want to skip successors of the task, end_at will be used
15:17 dshulyak the other point is that - stage is artificial entity and there will be nothing like stage in future
15:17 seeg so if skip_tasks operates as it says, removing pre_deployment stage doesn't remove predeployment tasks :P
15:18 seeg i mean other than pre_deployment empty task, since i understand there's such a dummy task to run pre_deployment
15:18 dshulyak and put something like stage in client (software that we dont control) is a bad move
15:19 dshulyak seeg: yeah, thats valid)
15:20 dshulyak seeg: can you summarize why it is better to put such logic in client over nailgun?
15:20 seeg well, if you want to skip single tasks like that then no dependency parsing is necessary at all
15:21 seeg as for end_at -- it was not in the code but i guess again, if api can send tasks in order they will be executed, end_at can just trim the list at that place
15:21 seeg this way all graph parsing logic is still on api side
15:21 seeg and if some tasks can be run in parallel -- then what does it even mean to end_at such a 'branch' task?
15:22 dshulyak seeg: it means recursively find all predecessors of this task and execute them
15:23 evgeniyl___ seeg: your suggestion is to send ready graph in PUT request for deployment?
15:23 jobewan joined #fuel-dev
15:23 seeg my suggestion is to send task names that are to be executed, in no particular order
15:23 seeg names or ids or whatever
15:24 seeg but not graph, graph is done in the api
15:24 seeg but the API upon GET should send tasks in order they will be executed
15:24 dshulyak there is no such thing as single order for tasks
15:24 dshulyak it depends on nodes that are going to be deployed
15:25 bookwar_ ikalnitsky: please never edit anything in Jenkins configuration without consulting with devops team
15:25 seeg so end_at does not make much sense too in this case
15:25 ikalnitsky bookwar_: oops, sorry. ok. did i break something?
15:25 dshulyak why?
15:25 bookwar_ ikalnitsky: and if changes are needed for one of the main jobs - you can commit it them here https://review.fuel-infra.org/#/q/project:fuel-infra/jenkins-jobs
15:26 dshulyak it makes sense for me
15:26 bookwar_ ikalnitsky: it is just that changing upgrade tarball structure leads to changes in upgrade tests
15:26 dshulyak you know that you want to deploy three nodes
15:26 dshulyak and stop on neutron checkpoint
15:26 bookwar_ ikalnitsky: and our jenkins configuration is now stored in the repo, so any manual changes will be overriden by next update
15:27 seeg yeah well -- what if you have dependency tree with base A and 2 leaves B and C, you say end_at B, is C also executed?
15:27 ikalnitsky bookwar_: i got it. thank you. i didn't know that we're using job builder.
15:27 dshulyak no, only dependencies for node B
15:27 dshulyak *graph node
15:28 bookwar_ ikalnitsky: even if we don't, changing anything in product jobs is the major change which needs to be discussed and announced
15:30 dshulyak seeg: so in case if skip/only to be applied for stage, client will need to know about data structure, which in future can be easily changed
15:30 seeg well, we can provide API get with such end_at
15:31 dshulyak seeg: and what if skip is composable with end_at ) ?
15:31 seeg skip is simple, just remove element from list
15:31 dshulyak what if you want to skip stage?
15:32 seeg we skip dependencies then or not?
15:32 dshulyak stage is artificial entity, which is here because of legacy orchestration logic
15:32 evgeniyl___ seeg: dshulyak also we shouldn't remove node from the graph, we should replace it with stub, not to break graph
15:33 seeg what does it mean artificial entity? that handler accepts task names, is pre_deployment a task or not?
15:33 ylobankov joined #fuel-dev
15:33 sambork joined #fuel-dev
15:34 dshulyak pre_deployment is stage, it is kindof stub that required to keep graph consistent with our orchestration abilities
15:34 seeg if it's 'kindof stub' then you cannot send such name to task because it's not restful :P
15:34 dshulyak hm
15:34 seeg you need well defined entities not some weird things
15:35 seeg sometimes skip is a task, othertimes something ephemeral
15:35 seeg that's hackish
15:35 dshulyak it has nothing to do with restfull
15:36 seeg i understood that pre_deployment is a task that does nothing, it's only for dependencies
15:36 evgeniyl___ seeg: agree with dshulyak, how does it relate to rest?
15:36 seeg so i you say you want to skip it, i assume you want to skip it's dependencies too
15:36 dshulyak seeg: i dont know what you are calling it weird )
15:36 dshulyak it is not
15:37 dshulyak it is artifact of existent orchestrator
15:37 dshulyak yep, we have different procedures if we want to skip task or stage
15:37 dshulyak if you want we can add skip_stage
15:37 seeg sooo
15:37 dshulyak but it will be required for sure
15:38 seeg that's more complicated now even: skip accepts task OR stage, can also accept only and end_at
15:38 seeg only and end_at also accept stage?
15:38 seeg this seems really complicated
15:38 dshulyak so it is better stop doing anything)?
15:38 dshulyak i dont quite undderstand this argument
15:38 seeg no, i didn't say that
15:39 dshulyak why we should simplify api if this flags is composable?
15:39 dshulyak you can write --only pre_deployment --end_at pre_deployment
15:39 dshulyak and nothing bad will happen
15:40 dshulyak or --skip pre_deployment --end_at pre_deployment -- and nothing will fail
15:40 dshulyak but you will shoot youself in a leg
15:40 dshulyak ofcourse
15:40 dshulyak but this is developer responsibility
15:41 seeg well, now I don't know how skip works at all
15:41 seeg for once
15:41 seeg it skips single task? or whole stages with dependencies?
15:41 seeg what if you skip a task that has dependencies -- they are skipped too or not?
15:42 dshulyak no
15:42 seeg but skipping pre-deployment skips it's dependencies, right?
15:42 dshulyak seeg: yep
15:42 dshulyak )
15:42 seeg that's inconsistent for me
15:42 dshulyak because stage are  special
15:42 dshulyak legacy )
15:42 dshulyak you cant get rid from that
15:43 seeg the API has 'skip_tasks' parameter -- this doesn't tell me anything about stages or legacy or special
15:46 seeg i could also ask the same about only -- only 'foo' will call just foo? or it's dependencies too?
15:46 seeg or it depends on whether 'foo' is task or stage?
15:46 dshulyak yes
15:47 dshulyak consider next example
15:47 seeg ok, how I as the end user can know what is run and what is not run?
15:47 dshulyak fuel node --node 2 --deploy --only pre_deployment hiera
15:47 dshulyak you want to setup repos, rsync puppet
15:47 dshulyak and setup hiera
15:48 dshulyak and api looks to me like pretty good for doing such things
15:48 dshulyak it will described for doc ofcourse, and at this point developer will know that he have 3 stages
15:48 dshulyak pre_deployment, deploy, post_deployment
15:49 seeg which are legacy and will be removed?
15:49 dshulyak yes
15:50 seeg as for me, I'd go another way -- fix the GET and add skip end_at and such so that user has a nice way of filtering and seeing his tasks he wants
15:50 seeg PUT should accepts pure task list with tasks to be done
15:50 seeg this way user will see his tree and if he accepts that, then he sends 'deploy'
15:51 seeg from cli side this would look like 'fuel deploy --dry-run' or something like that
15:51 seeg this way API deployment stage is crystal clear -- deploy these tasks and that's it
15:52 seeg GETs should be for custom views, PUT should be simple and understandable
15:54 e0ne joined #fuel-dev
16:08 jaypipes joined #fuel-dev
16:11 tnurlygayanov_ Hi team
16:11 tnurlygayanov_ we have bug https://bugs.launchpad.net/fuel/+bug/1412457
16:11 tnurlygayanov_ is it issue fro fuel-library?
16:14 dshulyak seeg: i got your point, something like get list of tasks that will be executed will done anyway, but i am no sure why we can not put this arguments right in PUT)
16:14 dshulyak evgeniyl___: what is your opinion?
16:17 prmtl joined #fuel-dev
16:18 evgeniyl___ dshulyak: what seeg is saying makes sense
16:18 evgeniyl___ dshulyak: seeg in this case you have advanced filtration and not much logic on client side
16:20 agordeev joined #fuel-dev
16:25 pasquier-s joined #fuel-dev
16:31 amnk joined #fuel-dev
16:32 bogdando please take a look onto https://bugs.launchpad.net/mos/+bug/1378212 latest comments
16:33 bogdando it looks like some dependency for gems are broken for my custom ISO...
16:33 e0ne joined #fuel-dev
16:34 bogdando Centos BVT is here http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom.centos.bvt_1/422 I guess the errors will be the same
16:38 jaypipes_ joined #fuel-dev
16:42 angdraug joined #fuel-dev
16:54 ChrisNBlum joined #fuel-dev
16:57 ChrisNBlum joined #fuel-dev
16:58 bogdando I create the separate bug for this https://bugs.launchpad.net/mos/+bug/1412499. it looks like the issue is related to https://github.com/stackforge/fuel-web/blob/master/nailgun/requirements.txt#L24 and https://github.com/stackforge/fuel-main/blob/master/packages/rpm/specs/nailgun.spec#L44
17:00 ChrisNBlum joined #fuel-dev
17:02 ikalnitsky bogdando: cool. did you made
17:02 ikalnitsky bogdando: will you make a patch?
17:03 ChrisNBlum joined #fuel-dev
17:03 bogdando ikalnitsky, well I'm not sure should the build system requirement be lowered, or naillgun one raised :)
17:03 bogdando ikalnitsky, and I have no idea what to do with keystone error
17:04 ikalnitsky bogdando: i think we need urllib3 >= 1.7 in nailgun/requirements.txt, just like we have in nailgun.spec
17:05 ikalnitsky bogdando: i don't see any keystone container error. could you please share more information? or maybe you can share your broken env?
17:05 bogdando I try to test it at my lab with simple pip install urllib3==1.7, but docker contrainer should be rebuilt somehow
17:06 ChrisNBlum joined #fuel-dev
17:07 ikalnitsky bogdando: you need to make a patch and build new iso. pip won't help here. also, you can perform some hacks inside docker container )
17:07 bogdando ikalnitsky, ok
17:08 bogdando ikalnitsky, but please take a look onto /var/log/docker-keystone.log
17:09 rmoe joined #fuel-dev
17:09 ChrisNBlum joined #fuel-dev
17:12 ChrisNBlum joined #fuel-dev
17:15 ChrisNBlum joined #fuel-dev
17:17 romcheg joined #fuel-dev
17:18 ChrisNBlum joined #fuel-dev
17:21 ChrisNBlum joined #fuel-dev
17:25 ChrisNBlum joined #fuel-dev
17:25 ikalnitsky bogdando: it looks like you use upstream keystone versions. i mean, there are a lot of new dependencies but they aren't been installed because we don't have them in specs. so, it won't be easy to test it. you need to change keystone-related specs first and build packages with them.
17:28 ChrisNBlum joined #fuel-dev
17:31 ChrisNBlum joined #fuel-dev
17:33 romcheg joined #fuel-dev
17:34 ChrisNBlum joined #fuel-dev
17:35 jaypipes joined #fuel-dev
17:36 ChrisNBlum joined #fuel-dev
17:39 ChrisNBlum joined #fuel-dev
17:42 ChrisNBlum joined #fuel-dev
17:45 ChrisNBlum joined #fuel-dev
17:48 ChrisNBlum joined #fuel-dev
17:51 dshulyak_ joined #fuel-dev
17:51 romcheg joined #fuel-dev
17:51 ChrisNBlum joined #fuel-dev
17:54 ChrisNBlum joined #fuel-dev
17:56 xarses joined #fuel-dev
18:00 ChrisNBlum joined #fuel-dev
18:03 ChrisNBlum joined #fuel-dev
18:06 miroslav_ joined #fuel-dev
18:06 ChrisNBlum joined #fuel-dev
18:09 ChrisNBlum joined #fuel-dev
18:12 ChrisNBlum joined #fuel-dev
18:15 ChrisNBlum joined #fuel-dev
18:18 ChrisNBlum joined #fuel-dev
18:21 ChrisNBlum joined #fuel-dev
18:24 ChrisNBlum joined #fuel-dev
18:25 amnk joined #fuel-dev
18:27 ChrisNBlum joined #fuel-dev
18:30 ChrisNBlum joined #fuel-dev
18:34 ChrisNBlum joined #fuel-dev
18:37 ChrisNBlum joined #fuel-dev
18:40 ChrisNBlum joined #fuel-dev
18:43 ChrisNBlum joined #fuel-dev
18:45 ChrisNBlum joined #fuel-dev
18:46 dshulyak_ joined #fuel-dev
18:48 ChrisNBlum joined #fuel-dev
18:51 ChrisNBlum joined #fuel-dev
18:54 ChrisNBlum joined #fuel-dev
18:58 ChrisNBlum joined #fuel-dev
19:00 ChrisNBlum joined #fuel-dev
19:06 amnk joined #fuel-dev
19:07 ChrisNBlum joined #fuel-dev
19:10 ChrisNBlum joined #fuel-dev
19:13 ChrisNBlum joined #fuel-dev
19:16 ChrisNBlum joined #fuel-dev
19:17 corepb_ joined #fuel-dev
19:19 ChrisNBlum joined #fuel-dev
19:22 ChrisNBlum joined #fuel-dev
19:25 ChrisNBlum joined #fuel-dev
19:28 ChrisNBlum joined #fuel-dev
19:28 monester_laptop joined #fuel-dev
19:30 amnk joined #fuel-dev
19:30 xarses joined #fuel-dev
19:31 ChrisNBlum joined #fuel-dev
19:33 ChrisNBlum joined #fuel-dev
19:34 obcecado joined #fuel-dev
19:36 ChrisNBlum joined #fuel-dev
19:38 pasquier-s joined #fuel-dev
19:39 ChrisNBlum joined #fuel-dev
19:42 ChrisNBlum joined #fuel-dev
19:43 pasquier-s joined #fuel-dev
19:44 amnk joined #fuel-dev
19:45 e0ne joined #fuel-dev
19:45 ChrisNBlum joined #fuel-dev
19:48 ChrisNBlum joined #fuel-dev
19:51 amnk joined #fuel-dev
19:51 ChrisNBlum joined #fuel-dev
19:53 amnk joined #fuel-dev
19:54 ChrisNBlum joined #fuel-dev
19:57 amnk_ joined #fuel-dev
19:57 ChrisNBlum joined #fuel-dev
20:03 prmtl joined #fuel-dev
20:05 monester_laptop joined #fuel-dev
20:50 jaypipes joined #fuel-dev
20:54 pasquier-s joined #fuel-dev
21:00 pasquier-s joined #fuel-dev
21:07 iunruh joined #fuel-dev
21:17 romcheg1 joined #fuel-dev
21:29 pasquier-s joined #fuel-dev
21:43 jaypipes joined #fuel-dev
22:13 dshulyak_ joined #fuel-dev
22:39 pasquier-s joined #fuel-dev
22:46 romcheg joined #fuel-dev
22:58 e0ne joined #fuel-dev
23:07 bookwar docaedo: ping
23:55 pasquier-s joined #fuel-dev

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