currently, there are some docker container in dockerhub. Here is the url:
https://registry.hub.docker.com/search?q=shinken
++++++
Ning Xie
2015-04-07 21:59 GMT+08:00 nap <napar...@gmail.com>:
>
>
> On Thu, Apr 2, 2015 at 10:51 PM, Thibault Cohen <titilamb...@gmail.com>
> wrote:
>
>> Hello everyone !
>>
>> I'm guilty, this is my fault... :( sorry.
>>
>> I just created a new pull request that should fix this bug :)
>>
> Hi,
>
> still issue on debian (I didn't test centos). But the Travis part is ok.
>
>> But I have two comments about all of this:
>>
>> - BETA tags seem to be useless, otherwise someone would have reported
>> this bug earlier...
>>
>> Sad but true. don't expect people to test a beta (unless they are core
> dev). Even the test level is quite low on RC. It's mainly on few days after
> the release that we have the most bug ticket.
>
>>
>> - Also, I think we don't use setuptools as we should. If you look at
>> what ansible/salt do, they don't ship any files outside /usr/local/ folder
>> (using ie: sudo pip install salt). I didn't find any python software which
>> copy configuration files in /etc/ or makes some chown during the
>> installation (pip install ...).
>> I feel like pip is made to install libs more than full software
>>
>> Yes, the whole python ecosystem was done for libs, not tools :(
>
>
>> - Maybe we need to rethink about what setup.py should do and should
>> not do...
>>
>> For linux installation, I think we should get inspiration from BSD folder
>> architecture generated by pip installation.
>>
> We already finish this talk on the pre-2.0 version and we did choose the
> LSB. We won't change again as it's a valid way to find files after all.
>
> In the next years, I think docker-like ship will be the default (think
> about docker-like plugins! no more system/python/perl lib issue ^^), and
> users won't even have to mix local system and applications. And they won't
> even care where it's installed in the container (as it's a black box and it
> won't break their system).
>
> All we need for this are (easier) orchestration tools and more powerful
> container monitoring (currently it's not so natural to monitor containers
> as they can spawn quickly).
>
> It can be docker or another container solution, but as it can save a lot
> of time to admins to install/link new tools, I think it will be really
> asked in production, and not just a dev playground tool ^^
>
> [...]
>>
>> --
>> Thibault Cohen
>>
>>
>
> Jean
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Shinken-devel mailing list
> Shinken-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/shinken-devel
>
>
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
