by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 13 18:32
    k-wall synchronize #5125
  • Aug 13 18:05
    k-wall review_requested #5133
  • Aug 13 18:04
    k-wall review_requested #5133
  • Aug 13 18:04
    k-wall review_requested #5133
  • Aug 13 18:04
    k-wall synchronize #5133
  • Aug 13 18:04
    k-wall synchronize #5133
  • Aug 13 17:36
    k-wall synchronize #5133
  • Aug 13 17:35
    k-wall synchronize #5125
  • Aug 13 17:31
    k-wall synchronize #5133
  • Aug 13 17:26
    k-wall synchronize #5133
  • Aug 13 17:16
    k-wall synchronize #5133
  • Aug 13 17:13
    k-wall synchronize #5133
  • Aug 13 17:03
    k-wall synchronize #5133
  • Aug 13 16:45
    k-wall synchronize #5133
  • Aug 13 16:44
    k-wall labeled #5133
  • Aug 13 16:44
    k-wall opened #5133
  • Aug 13 16:44
    k-wall milestoned #5133
  • Aug 13 16:27
    k-wall synchronize #5125
  • Aug 13 14:52
    k-wall edited #5125
  • Aug 13 14:52
    k-wall edited #5125
Ulf Lilleengen
@lulf
@ctron @k-wall could you have a look at EnMasseProject/enmasse#4895 ?
k-wall
@k-wall
@lulf I'm happy with those renames
David Kornel
@kornys
@lulf could you please check this? EnMasseProject/enmasse#4903
Ulf Lilleengen
@lulf
@kornys lgtm, thanks!
Ulf Lilleengen
@lulf
@k-wall Are you ok with the changes to the console 1.0 proposal in EnMasseProject/enmasse#4855 ?
Ulf Lilleengen
@lulf
@k-wall also, there are a few bugfixes in EnMasseProject/enmasse#4920 that @kornys would like to merge :)
David Kornel
@kornys
:D :D
David Kornel
@kornys
@lulf I have fixed framework unit tests without kube cluster EnMasseProject/enmasse#4923
k-wall
@k-wall
@lulf if you would have time to review #4863, that'd be great. Hopefully the test issue I mentioned was a problem enabling SASL ANON from the system test client, it is should be worked around for now
Ulf Lilleengen
@lulf
Having a look now @k-wall (also if you have time to look at #4900 that would be great :) )
David Kornel
@kornys
@lulf do you have any other comments regarding parallel tests V2 PR?
David Kornel
@kornys
@lulf @obabec I have pushed last fixes for parallel PR, could you please re-approve it?
obabec
@obabec
@kornys sure :))
David Kornel
@kornys
I had to add forNode implmenation to fix currupted STDOUT warning from surefire, and I also fixed kubernetes constructor to do not require environment instance since Environment is a singleton
Ulf Lilleengen
@lulf
David Kornel
@kornys
@lulf @obabec pls EnMasseProject/enmasse#4938
David Kornel
@kornys
@lulf @obabec it should work now, I tested it locally with microk8s EnMasseProject/enmasse#4938
David Kornel
@kornys
@k-wall can I merge it? EnMasseProject/enmasse#4942
Mostafa Eltaher
@mostafa-eltaher
Hi All, Do you know if I have a standard queue address with multiple brokers (something like standard-xlarge-queue address plan), will the messages be balanced between the brokers (i.e. active-active setup) or only funneled to one of the brokers (i.e. active-passive setup)?
Ulf Lilleengen
@lulf
@mostafa-eltaher it will be balanced. Note that you will not have any message order this way. Also note that the partitions setting in the address plan will dictate how many brokers an address would be spread across.
@mostafa-eltaher Also note that message order is not guaranteed in this case
Mostafa Eltaher
@mostafa-eltaher
@lulf Thank you, in this case, the message consumers (receivers) will be connected to all brokers (I assume qdr will do that on their behalf), right?
Ulf Lilleengen
@lulf
@mostafa-eltaher Sort of - the consumers are connected to qdr, and qdr will consume messages from broker and forward to consumers. So if 2 consumers are connected to qdr and the same address, they will be round robin receiving messages as well
@mostafa-eltaher Btw, here are some improved overview docs I've been working on for 1.0 http://people.redhat.com/~ulilleen/1.0-guides/overview-guide.html - some of the concepts apply to standard address space today here.
Work in progress :)
Mostafa Eltaher
@mostafa-eltaher
@lulf Brilliant, thank you for that. Another related, I have noticed that currently with 0.32.0, each broker is deployed in a dedicated StatefulSet, do you have any idea why? (i.e. why not having all brokers of an address space in single StatefulSet and scaling out/in by managing the replicas count)?
Ulf Lilleengen
@lulf
@mostafa-eltaher Having a single stateful set causes problem in scaling down, because you can only scale down the last pod. So if you have brokers 0, 1, and 2, and you remove all addresses that are on broker 0, then you can't remove it if they all belong to the same stateful set
@mostafa-eltaher The longer-term vision was that if we are to support HA brokers (active-passive), we would do so by increasing replicas of statefulset, which fits better for that.
Mostafa Eltaher
@mostafa-eltaher
@lulf Thank you
Bob Claerhout
@BobClaerhout
Hi all, in the Artemis documentation I could find a way to configure redeivery back-off and DLQ configuration: https://activemq.apache.org/components/artemis/documentation/1.1.0/undelivered-messages.html. Can somebody tell me how to configure this via enmasse?
k-wall
@k-wall
@BobClaerhout that's something we are currently building for the 1.0 release. It is not present in 0.x
Bob Claerhout
@BobClaerhout
@k-wall thanks for the quick response. Can you give me a (rough) estimate on when the 1.0 will be released?
We are aiming for the Autumn Sep/Oct this year. Some of this work is materialising onto the master branch as the moment
Bob Claerhout
@BobClaerhout
ok, perfect. looking forward to that
Mostafa Eltaher
@mostafa-eltaher
Hi Guys, not sure if you know that already, but the stable release documentation page [https://enmasse.io/documentation/0.32.2/kubernetes.html] is giving 404
Ulf Lilleengen
@lulf
@mostafa-eltaher Should be fixed now, the documentation release process was outdated. Thanks!
Mostafa Eltaher
@mostafa-eltaher
@lulf Thank you
k-wall
@k-wall
@lulf EnMasseProject/enmasse#5107 is ready for final review. I'll left the parts in the code that will enable remote consumer priority. When that Apache Qpid Dispatch feature arrives, all that will need done is to enable the test case and alter the description in the CRD.
Ulf Lilleengen
@lulf
@k-wall The additional changes looks good, thank you! I'm not able to approve it since I created the PR
Bob Claerhout
@BobClaerhout
Hi all, we noticed the broker is logging a lot! I can't seem to find the proper way to configure the level on the broker. Any pointers on where I can find the documentation on that?
Ulf Lilleengen
@lulf
I think @k-wall dug into that at some point, I can’t remember the fix off the top of my head
Bob Claerhout
@BobClaerhout
ok, thanks for the quick reponse @lulf. Any idea of @k-wall is able to respond this week?
k-wall
@k-wall
@BobClaerhout I did some investigation which was documented here EnMasseProject/enmasse#4035
Unfortunately, I did not have capacity at that point to get to root cause. I'll try to find a time to take another look and see if the situation has changed since I wrote those words.
Bob Claerhout
@BobClaerhout
ok, If understand it correctly, it looks like all logging configuration (except for the format aparently) is not loaded properly
k-wall
@k-wall
yes, that's my memory of the issue. I haven't investigated again since I raised that issue.
Bob Claerhout
@BobClaerhout
ok, too bad. Thanks for the information!
Jevgenija Pantiuchina
@jpantiuchina_twitter

Dear developers,

As part of a research team from Università della Svizzera italiana (Switzerland) and University of Sannio (Italy), we have analyzed refactoring pull requests in EnMasseProject/enmasse GitHub repository and are looking for developers for a short 5-10 min survey (https://usi.eu.qualtrics.com/jfe/form/SV_cO6Ayah0D6q4eSF). Would you please spare your time by answering some questions about refactoring-related contributions? We would greatly appreciate your input — it would help us understand how developers can improve the quality of refactoring contributions, and benefit the development process. The responses will be anonymized and handled confidentially! Thank you a lot!

If you consider this message to be spam, I'm very sorry! There will be no follow-up to bother you.

k-wall
@k-wall
@lulf if you have time to review #5125 that would be good.