Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    At the moment we are writing a blog post on the project launch and the next steps we want to go in combination with scaphandre: https://hackmd.io/Fq-CO7VYRH2-UmcZeazTqw
    Tobias Augspurger
    @Ly0n
    It would be nice to get your opinion / thoughts on the draft. Our goal is to show how open "life cycle assessment tools" in combination with continuous reforestation can be used to compensate emissions within the continuous development process.
    bpetit
    @bpetit

    :clap: This is great ! Thanks for sharing. Don't hesitate to ping some of us here to get some help when needed. We can reschedule our workshop too at some point.

    I'll read that and send you my feedback later today.

    Tobias Augspurger
    @Ly0n
    Thanks, that would be nice. A technical workshop with you guys on the next steps would be amazing. First we need to publish the blog post and do some marketing. I think we can finish that this week.
    @bpetit Don't hesitate to edit the blog post by markdown comments. I made a safety backup just now.
    We will also add you as another author if you like to.
    1 reply
    René Ribaud
    @uggla
    @Ly0n :thumbsup:
    bpetit
    @bpetit

    @PierreRust I'm investigating on hubblo-org/scaphandre#85

    Do you have access to a 2-socket server so that we could test ?

    Pierre Rust
    @PierreRust
    Hello, yes, I have a two socket workstation available. I wanted to investigate the issue on it for some time but I did not find the time to do it yet :(
    bpetit
    @bpetit
    Hi, I completely understand. I'll try to extract some precise pointers on how to fix that and I'll let you try on this machine and give feedback or jump on it and add what's needed. is this ok for you ?
    Pierre Rust
    @PierreRust
    That would be great !
    and btw, regarding your proposition of pair programing on that, I really like the idea :)
    bpetit
    @bpetit

    Great ! We can schedule that starting next week if you want.

    I see there is some work here that seems accurate : hubblo-org/scaphandre#87

    It works perfectly on my setup and seems to replace the function I had suspicions about. Could you try that PR on your machine to see if the bug is still there ?

    bpetit
    @bpetit
    did some of you already play with gRPC and protobuf in rust ?
    René Ribaud
    @uggla
    Just a little as rust-riemann-client is using it.
    It could be a good example to look at it as the "stubs" for riemann are "simple".
    bpetit
    @bpetit
    Great, thanks for the pointer, I'll have a look at it
    :)
    René Ribaud
    @uggla
    The protobuf crate looks pretty good.
    But I would say it is interesting if you have "perf" constraints. Otherwise http is easier.
    bpetit
    @bpetit
    This is not really a choice, I need to discuss with containerd. It seems the most clean way is to do it through grpc/protobuf and the admin socket.
    René Ribaud
    @uggla
    ok in this case, yes you don't have the choice.
    bpetit
    @bpetit

    Hi !

    It seems the linting rules in Clippy have changed a bit in the new version: https://github.com/hubblo-org/scaphandre/runs/2199772368

    It asks us to change struct names like JSONExporter to JsonExporter, CPUStat to CpuStat, and so on.

    I'll proceed on the change on the whole codebase, so be aware of that in your PRs to avoid conflict. The full list of struct names to be changed are in the link just before.

    bpetit
    @bpetit
    Actually I wont, as it may break the API/lib for people using scaph as a crate (even if they should'nt be many). Plus it seems the community will revert that lint rule as many other people are not happy about it: rust-lang/rust-clippy#6974
    bpetit
    @bpetit

    Hey there,

    I just moved the documentation static generated files to this repo: https://github.com/hubblo-org/scaphandre-documentation
    I've added a note in the contributing guide to edit and build the doc: https://hubblo-org.github.io/scaphandre-documentation/contributing.html#edit-and-build-the-documentation
    (nothing has really changed)

    The new url for the doc is https://hubblo-org.github.io/scaphandre-documentation (notice the extra -documentation)

    bpetit
    @bpetit

    Hi !

    I've posted an update on hubblo-org/scaphandre#85 @PierreRust if you get some time to check :)
    It seems hubblo-org/scaphandre#87 fixes part of your issue. The other part is not clear yet but I think your answer will make it clearer :smile:

    bpetit
    @bpetit
    @uggla I merged hubblo-org/scaphandre#71 thanks !
    I just added a no-header flag to disable it if needed, and applied it to all exporters by calling the function from lib.rs and not each exporter module
    René Ribaud
    @uggla
    @bpetit , sounds good to me.
    have you had a chance to look at the other PR about exporter factorization ?
    5 replies
    bpetit
    @bpetit
    @uggla Hi ! I've iterated on your initial PR here: hubblo-org/scaphandre#96
    I've also added a test to check that the prometheus exporter can be scrapped.
    René Ribaud
    @uggla
    ok cool. I want me to review it right ?
    If I can i will have a look this afternoon or this evening.
    :)
    René Ribaud
    @uggla
    Hello @bpetit are you available ?
    14 replies
    bpetit
    @bpetit
    Hi ! @barnumbirr have you been able to test scaphandre on AMD since this thread ? hubblo-org/scaphandre#55
    (with a kernel > 5.11)
    bpetit
    @bpetit

    Just release v0.3.0 : https://github.com/hubblo-org/scaphandre/releases/tag/v0.3.0

    :grinning: Thanks to all the contributors !

    René Ribaud
    @uggla
    @bpetit, I will be on vacation next week so I have some "free" time. If you will have a time slot as well, we could discuss the priority of issues and review them.
    If I will be able to help on something.
    bpetit
    @bpetit
    Hi ! Yeah sure, we can schedule a short meeting on monday or tuesday ?
    René Ribaud
    @uggla
    @bpetit , I apologize I could not make it. I thought I would had some "free" time, but my little daughter disagreed that statement.
    bpetit
    @bpetit
    Do not apologize, family first ! :)
    I may have some time late in the afternoon, or we could schedule a call next week. Tell me what if the best for you :)
    René Ribaud
    @uggla
    Hello @bpetit , I have a slot today 16h --> 17h will it be ok 4 u ?
    7 replies
    Arthur Madec-Prévost
    @arthurmadecprevost
    Hello everyone! Good job for your app. I'm currently testing it and it's such a great thing for a better IT. Do you plan to extend it to other Hypervisors ? Such as VMware, Citrix, Hyper-V ?
    bpetit
    @bpetit

    Hi ! Thanks ! I intend to work on VMWare hypervisors support at some point, but there are several things first in the roadmap. Any help on this would be highly appreciated ! :)

    For Hyper-V first thing would be to add windows support : hubblo-org/scaphandre#74
    Then why not.

    Actually, explanation of supporting only qemu/kvm is not rooted in some deep technical explanation. We just only tested in this context. The data coming from the hypervisor is exposed in the virtual machine through a read only volume, which is not that complicated and should be replicable in vmware (maybe) or other linux based hypervisors.
    Arthur Madec-Prévost
    @arthurmadecprevost
    Thank you for the answer! :D