Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Vincent Zurczak
    @vincent-zurczak
    FOr my information, did you implement the selector by installer in the templating?
    For
    Vincent Zurczak
    @vincent-zurczak
    OK. I did it.
    Vincent Zurczak
    @vincent-zurczak
    Hi! Any feedback about my Prs?
    PR
    Pierre Bourret
    @bourretp
    Hi
    lot to say, but I'm gonna merge it anyway
    Pierre Bourret
    @bourretp
    Merged! I send a mail to @cdeneux to notify him.
    Pierre Bourret
    @bourretp
    Hi!
    Back from the beach! :sunrise:
    @gibello is continuing the work on the HTTP messaging today. He told me about his idea of merging messaging with the DM... I'll find some other issues to resolve today, and we'll talk about HTTP tomorrow.
    Vincent Zurczak
    @vincent-zurczak
    Hi.
    Merging messaging with the DM?! We'll see tomorrow.
    Vincent Zurczak
    @vincent-zurczak
    Otherwise, welcome back! :)
    Pierre Bourret
    @bourretp
    thx
    Vincent Zurczak
    @vincent-zurczak
    Did you complete the issue related to Javadoc?
    Pierre Bourret
    @bourretp
    no, as it requires to change the mega-parent pom
    Vincent Zurczak
    @vincent-zurczak
    Can you prepare a description of the required changes for tomorrow? We will discuss them and decide what to do next. I'd like to close this issue this week.
    Pierre Bourret
    @bourretp
    ok
    Vincent Zurczak
    @vincent-zurczak
    Thanks.
    Pierre Bourret
    @bourretp
    Hi!
    Pierre Bourret
    @bourretp
    While working on the image upload, I couldn't prevent myself to do a real test on a running DM (using curl to upload the image)...
    Question is: is it normal that, despite the image being uploaded to the correct destination, the web-admin does not display it (still the default coloured Roboconf logo) ?
    even after F5, Ctrl-F5, rebooting the DM, the machine ;)
    Vincent Zurczak
    @vincent-zurczak
    Hi.
    Nope, it's not. F5 should take it.
    Was the image correctly written?
    There might be something too with the serialization...
    Pierre Bourret
    @bourretp
    image is written
    no serialization, just writing a stream to a file
    just to confirm: the application/template icon should be located in {app.or.template.config.dir}/application.X (where X is either gif jpg jpeg png svg) right?
    Pierre Bourret
    @bourretp
    Mmmh, I'm afraid the truth is elsewhere. The IconServlet is never called
    So the default-avatar.png is always the app/tempalte icon
    Once the IconServlet get called, I hope it will serve the uploaded image. But meanwhile... I can only "unit-test" that the file is copied at the right place, not that it will actually be used :(
    Should be in the web-admin, I'll check it later
    Vincent Zurczak
    @vincent-zurczak
    OK.
    Please, report the bug too.
    Pierre Bourret
    @bourretp
    roboconf/roboconf-web-administration#53
    Pierre Bourret
    @bourretp
    Another one for you ;) : roboconf/roboconf-platform#430
    Vincent Zurczak
    @vincent-zurczak
    Congratulations to @diarraa for his first official contribution to Roboconf! :smiling_imp:
    Vincent Zurczak
    @vincent-zurczak
    It's a little dead out there. Anyway, the project keeps on moving on. Exactly 1000 commits today for the platform. :clap:
    roboconf-1000-commits.png
    amchess
    @amchess

    Hello.

    I tried unsuccessfully to execute the following tutorial :
    http://roboconf.net/en/user-guide/tutorial-local-deployment-with-docker.html

    After the correct docker configuration listening at the 4243 port and with the pulled ubuntu-latest
    for the 0.9.1 version of roboconf and lamp-webapp-bash application, I logged the following errors :

    Karaf.log
    2017-11-13 17:18:50,422 | ERROR | pool-22-thread-1 | edTargetHandler$CheckingRunnable | 36 - net.roboconf.target-api - 0.9.1 | An error occurred while configuring machine 'rbcf_4e7d1f37-3ace-4b31-97e6-0582ac72759b'. org.apache.http.conn.HttpHostConnectException: Connect to localhost:4243 [localhost/127.0.0.1] failed: Connexion refusée (Connection refused)

    roboconf.log
    2017-11-14 11:14:39,376 | ERROR | edTargetHandler$CheckingRunnable | An error occurred while configuring machine 'rbcf_8d6bd158-4b52-4a81-a1d9-1124577f53cd'. com.github.dockerjava.api.exception.NotFoundException: {"message":"No such image: demo_roboconf_demo:latest"}
    ...
    2017-11-14 11:17:26,870 | ERROR | ManagedApplication | Agent /MySQL VM has not sent heart beats for quite a long time. Status changed to PROBLEM.
    If, instead I tag manually a demo_robo_demo image from the ubuntu:latest, I have no error, but the created and started containers of lamp application exit immediately with the following warning on the logs:
    A method was found for cap-add but it does not have the right parameter type. Skipping it. You may want to add a feature request.

    for the 0.8 version of roboconf and lamp-webapp-bash application, I have the following error :
    roboconf.log
    com.github.dockerjava.api.exception.DockerClientException: Could not build image: The command '/bin/sh -c apt-get update && apt-get install -y openjdk-7-jre-headless && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
    at com.github.dockerjava.core.command.BuildImageResultCallback.getImageId(BuildImageResultCallback.java:71)
    at com.github.dockerjava.core.command.BuildImageResultCallback.awaitImageId(BuildImageResultCallback.java:48)
    at net.roboconf.target.docker.internal.DockerMachineConfigurator.createImage(DockerMachineConfigurator.java:344)
    at net.roboconf.target.docker.internal.DockerMachineConfigurator.configure(DockerMachineConfigurator.java:153)
    at net.roboconf.target.api.AbstractThreadedTargetHandler$CheckingRunnable.run(AbstractThreadedTargetHandler.java:207)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

    Is there a way to execute successfully this tutorial ?

    Many thanks in advance.

    Vincent Zurczak
    @vincent-zurczak
    Hi.
    Which version of Roboconf are you using? And which version of Docker?
    amchess
    @amchess
    Docker: the latest
    Vincent Zurczak
    @vincent-zurczak
    There is a little error in the last documentation, our images are not based on Ubuntu anymore.
    amchess
    @amchess
    Roboconf: the latest 0.9.1 and the 0.8
    Vincent Zurczak
    @vincent-zurczak
    You cannot mix Roboconf versions...
    amchess
    @amchess
    yes of course