Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Tomas Jelinek
    @jelkosz
    sounds legiy
    legit
    Martin Beták
    @matobet
    cool,
    with regards to core MQTT infra, I have made some progress
    I managed to implement low power mqtt ping + we are also capable to reconnect when network fails
    Tomas Jelinek
    @jelkosz
    that is cool
    do we need some special part on any side or it is all existing and just question of config?
    Martin Beták
    @matobet
    we also have topic /doctor/status where we have "Pinned" message whether the doctor is ALIVE or DEAD
    Tomas Jelinek
    @jelkosz
    so are we calling it "doctor"? :D
    Martin Beták
    @matobet
    well, it is already hardcoded :D
    Tomas Jelinek
    @jelkosz
    set in stone / code :D
    Martin Beták
    @matobet
    and in mosquitto.conf where only 'doctor' user can publish anything :D
    regarding mosquitto config we will probably have to ship docker image for it
    for stock fedora from rpm I had to manually edit the systemd unit file to pick up my settings
    Tomas Jelinek
    @jelkosz
    hmmmmm, please don't make our users compile kernel in order to use movirt :)
    if it will continue this way, you will end up that down :)
    Martin Beták
    @matobet
    well yeah, that's why I'm looking at https://github.com/toke/docker-mosquitto
    Tomas Jelinek
    @jelkosz
    you
    Martin Beták
    @matobet
    It's really shame that current jboss doesn't embed MQTT broker
    and that we need to have 2 servers for this push
    Tomas Jelinek
    @jelkosz
    yeah, at least it is more interesting
    Martin Beták
    @matobet
    yeah, recently I though that we can support also setup when we have just MQTT + classical engine
    that gives us freedom in the future to push doctors responsibilities elsewhere (engine itself) or change the source of the push
    and we can do this seamlessly wrt MQTT + doctor + engine, we will have just different "Rest Client" layer
    Tomas Jelinek
    @jelkosz
    yeah - all should be optional
    except engine :)
    Martin Beták
    @matobet
    actually :D
    Tomas Jelinek
    @jelkosz
    mocking engine using doctor?
    :D
    Martin Beták
    @matobet
    if you want just read-only access and don't want to invoke any commands on the engine, MQTT + doctor should satifly you
    in the MQTT + doctor + engine setup we only issue direct calls to engine when doing /start /stop vms and such
    Tomas Jelinek
    @jelkosz
    ...and poll some actual data from engine...
    Martin Beták
    @matobet
    that is the doctors job
    you don't have to specify where the engine is from mobile clien
    t
    Tomas Jelinek
    @jelkosz
    that is right
    anyway, going to sleep
    Martin Beták
    @matobet
    see ya tomorrow
    Tomas Jelinek
    @jelkosz
    see ya
    Martin Beták
    @matobet
    Another update, I managed to build docker image for our configured mosquitto https://github.com/matobet/docker-mosquitto to run just follow the instructions: "docker run -tip 1883:1883 matobet/mosquitto" no need to clone the repo, docker will take care of everything
    Martin Beták
    @matobet
    @jelkosz SwipeToRefresh merged!
    It was like 5 lines of code :D
    Tomas Jelinek
    @jelkosz
    @matobet - cool, until we will get to market it will have a UX we will not be ashamed of :)
    Martin Beták
    @matobet
    Well I wish but I still couldnt after a day get the damned drawer to be not transparent
    Frantisek Kobzik
    @hustodemon
    @matobet that's just uber. go team!
    Martin Beták
    @matobet
    @jelkosz you won't believe it but oVirt REST api supports the following header: "Accept: application/json; detail=statistics+nics+disks" that returns the subcollections embedded in the VM response :) https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/html-single/REST_API_Guide/#sect-REST_API_Guide-Common_Features-Collections-Listing_Resource_Subcollections
    and it seems to have been supported since ovirt 3.0
    I already posted patch to exploit this in moVirt
    Tomas Jelinek
    @jelkosz
    wow, that's an interesting development :D
    Martin Beták
    @matobet
    yeah, doctor rest took a slight hit in terms of its future usefulness ....