Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 27 11:39
    obabec synchronize #5216
  • Nov 27 11:01
    obabec synchronize #5216
  • Nov 27 10:59
    obabec synchronize #5216
  • Nov 27 10:31
    obabec synchronize #5216
  • Nov 27 10:06
    obabec synchronize #5216
  • Nov 26 15:58
    obabec synchronize #5216
  • Nov 26 14:27
    obabec synchronize #5216
  • Nov 26 13:24
    obabec synchronize #5216
  • Nov 26 12:42
    obabec synchronize #5216
  • Nov 26 12:34
    obabec synchronize #5216
  • Nov 26 10:46
    obabec synchronize #5216
  • Nov 25 18:39
    lulf closed #5220
  • Nov 25 17:07
    obabec review_requested #5220
  • Nov 25 17:07
    obabec opened #5220
  • Nov 25 10:13
    lulf closed #5217
  • Nov 25 08:56
    obabec review_requested #5217
  • Nov 25 08:56
    obabec review_request_removed #5217
  • Nov 25 08:56
    obabec review_requested #5217
  • Nov 25 08:56
    obabec edited #5217
  • Nov 25 08:56
    obabec edited #5217
Tobias Månsson
@tobias-zeptio
@lulf We would use the interceptor to validate messages and add annotations, before diverting some to other outgoing queues. If you know a different way to do this, we are open to change our architecture.
Ulf Lilleengen
@lulf
@tobias-zeptio for queues, the dispatch router only forwards messages to/from the broker. The dispatch router will only send messages directly to a consumer for address of the 'anycast' or 'multicast' type. 'Queue' and 'topic' always goes to a broker. I think your use case is sane. I think interceptors could be configured in the infrastructure config, or as part of the 'address space', whereas diverts seems like a natural property of an address. I.e. you create address 'a' and 'b', both of type 'queue'. Then on 'a', you can create a divert to 'b' with transformer properties etc.. Instead of supporting the loading of JARs etc dynamically, I wonder if enmasse could run a builtin transformer that supported a common set of transformation operations. You might just want to look into https://github.com/vromero/activemq-artemis-operator or https://github.com/artemiscloud/activemq-artemis-operator as a way of deploying the broker, it should give you more customization than what enmasse offers currently.
Tobias Månsson
@tobias-zeptio
@lulf Thank you. We decided to deploy our own cluster and configuration, so ensure that we have the flexibility going forward.
Ulf Lilleengen
@lulf
@tobias-zeptio that sounds like a good step forward, good luck!
Gary Edwards
@garyedwards
Hi all, are the hono components removed in 0.33.x going to be reinstated in future versions or are they now considered outside of the enmasse scope? I am really enjoying drogue-cloud progress or may look at using the official hono helm release with enmasse. Thanks all for a great project.
Dejan Bosanac
@dejanb
@garyedwards Glad you're interested in all this ... I would use hono helm charts for now and keep an eye (or join the effort) on drogue cloud 🙂
Gary Edwards
@garyedwards
@dejanb thanks a lot for the tips. I am keen to get my head around a few of the drogue bits including the embedded stuff. I hope to make some time early next year 🦀.
Dejan Bosanac
@dejanb
@garyedwards awesome ... looking forward to it
mtmmtm9
@mtmmtm9

Hi, I am trying out enmasse. I run into this problem:

oc create -f standard-address-space.yaml
addressspace.enmasse.io/myspace created

oc get addressspace myspace
NAME READY PHASE AGE
myspace false Pending 6m

Is this supposed to behave like this (nothing happens for 6 minutes ?)

Ulf Lilleengen
@lulf
@mtmmtm9 Hi. Which version are you trying? Also, is there anything in the logs for t he address-space-controller pod?
mtmmtm9
@mtmmtm9
enmasse-0.33.0. Same problem with the one before.
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller DefaultsController
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller AddressFinalizerController
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller MessagingUserFinalizerController
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller ComponentFinalizerController
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller RealmFinalizerController
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller StatusInitializer
2020-11-17T08:19:09.311Z INFO [ControllerChain] Controller CreateController
2020-11-17T08:19:09.320Z INFO [ControllerChain] Controller RouterConfigController
2020-11-17T08:19:09.320Z INFO [ControllerChain] Controller PodDisruptionBudgetController
2020-11-17T08:19:09.320Z INFO [ControllerChain] Controller RealmController
2020-11-17T08:19:09.320Z INFO [ControllerChain] Controller NetworkPolicyController
2020-11-17T08:19:09.325Z INFO [ControllerChain] Controller StatusController
2020-11-17T08:19:09.325Z INFO [ControllerChain] Controller RouterStatusCache
2020-11-17T08:19:09.325Z INFO [ControllerChain] Controller EndpointController
2020-11-17T08:19:09.329Z INFO [ControllerChain] Controller ExportsController
2020-11-17T08:19:09.330Z INFO [ControllerChain] Controller AuthController
2020-11-17T08:19:09.335Z INFO [ControllerChain] Controller MetricsReporterController
2020-11-17T08:19:09.343Z INFO [ControllerChain] Check address spaces: [myapp:myspace]
2020-11-17T08:19:09.343Z INFO [ControllerChain] Checking address space : myapp:myspace creationTimestamp: 2020-11-17T08:07:58Z deletionTimestamp: null
2020-11-17T08:19:09.343Z INFO [ControllerChain] Controller DefaultsController
Ulf Lilleengen
@lulf
@mtmmtm9 Having the log output + maybe kubectl get events -n enmasse-infra could give an indication of whats gone wrong. It shouldn't take that long unless there were issues pulling images or something like that.
@mtmmtm9 Also, kubectl get pods -n enmasse-infra
mtmmtm9
@mtmmtm9
Should i upload it as a file or just type it in here ?
C:\Users\mp\Downloads\enmasse-0.33.0>kubectl get events -n enmasse-infra
LAST SEEN FIRST SEEN COUNT NAME KIND SUBOBJECT TYPE REASON SOURCE MESSAGE
12m 12m 1 enmasse-operator.16483d181bd7494c Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set enmasse-operator-7bdd6cf566 to 1
12m 12m 1 enmasse-operator-7bdd6cf566.16483d181de20920 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: enmasse-operator-7bdd6cf566-pcb9b
12m 12m 1 enmasse-operator-7bdd6cf566-pcb9b.16483d181e6c3a14 Pod Normal Scheduled default-scheduler Successfully assigned enmasse-infra/enmasse-operator-7bdd6cf566-pcb9b to localhost
12m 12m 1 enmasse-operator-7bdd6cf566-pcb9b.16483d184966c0f4 Pod spec.containers{controller} Normal Pulling kubelet, localhost pulling image "quay.io/enmasse/controller-manager:0.33.0"
12m 12m 1 enmasse-operator-7bdd6cf566-pcb9b.16483d1b58e55330 Pod spec.containers{controller} Normal Created kubelet, localhost Created container
12m 12m 1 enmasse-operator-7bdd6cf566-pcb9b.16483d1b3070b890 Pod spec.containers{controller} Normal Pulled kubelet, localhost Successfully pulled image "quay.io/enmasse/controller-manager:0.33.0"
12m 12m 1 enmasse-operator-7bdd6cf566-pcb9b.16483d1b63b6708c Pod spec.containers{controller} Normal Started kubelet, localhost Started container
12m 12m 1 address-space-controller-6fd5c858d8.16483d1c02956a14 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: address-space-controller-6fd5c858d8-ckwf9
12m 12m 1 address-space-controller.16483d1c00127660 Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set address-space-controller-6fd5c858d8 to 1
12m 12m 1 address-space-controller-6fd5c858d8-ckwf9.16483d1c03f958d4 Pod Normal Scheduled default-scheduler Successfully assigned enmasse-infra/address-space-controller-6fd5c858d8-ckwf9 to localhost
12m 12m 1 address-space-controller-6fd5c858d8-ckwf9.16483d1c2feb9434 Pod spec.containers{address-space-controller} Normal Pulling kubelet, localhost pulling image "quay.io/enmasse/address-space-controller:0.33.0"
12m 12m 1 address-space-controller-6fd5c858d8-ckwf9.16483d228289cdb8 Pod spec.containers{address-space-controller} Normal Pulled kubelet, localhost Successfully pulled image "quay.io/enmasse/address-space-controller:0.33.0"
12m 12m 1 address-space-controller-6fd5c858d8-ckwf9.16483d22b8a1dff8 Pod spec.containers{address-space-controller} Normal Started kubelet, localhost Started container
12m 12m 1 address-space-controller-6fd5c858d8-ckwf9.16483d22ae84acd0 Pod spec.containers{address-space-controller} Normal Created kubelet, localhost Created container
11m 11m 1 address-space-controller.1698461153 AddressSpace
There were parts cut off. kubectl get pods -n enmasse-infra
NAME READY STATUS RESTARTS AGE
address-space-controller-6fd5c858d8-ckwf9 1/1 Running 0 14m
console-5f85f965d-rnb8t 2/2 Running 0 13m
enmasse-operator-7bdd6cf566-pcb9b 1/1 Running 0 14m
Ulf Lilleengen
@lulf
@mtmmtm9 Can you run kubectl get addressspace -o wide?
mtmmtm9
@mtmmtm9
myspace standard standard-unlimited false Pending [Missing authentication service and no default authentication service found] 23m
Ulf Lilleengen
@lulf
ah
mtmmtm9
@mtmmtm9
Any ideas ? I am a beginner on kubernetes...
Ulf Lilleengen
@lulf
you need to deploy an authentication service. You can find examples in install/components/example-authservices
mtmmtm9
@mtmmtm9
ok. thanks ;)
Ulf Lilleengen
@lulf
enmasse comes with a 'none' authentication service which basically allows all, and a 'standard' authentication service where you can create users and assign permissions.
mtmmtm9
@mtmmtm9
I followed the guide. It said: "(Optional) Install the standard authentication service"
Ulf Lilleengen
@lulf
you can also roll your own by implementing the auth(z) protocol if you want to integrate with a third party auth service
I can see how that could've been better explained in the docs :)
mtmmtm9
@mtmmtm9
I added the auth-service, but i still get the same error.
Ulf Lilleengen
@lulf
you should be getting another pod up and running, check that its running. Then, it might take a minute for address space controller to pick it up. If its still not working, try to delete and create the address space again
mtmmtm9
@mtmmtm9

I did this: >oc delete -f standard-address-space.yaml
addressspace.enmasse.io "myspace" deleted

C:\Users\mp\Downloads\enmasse-0.33.0>oc create -f standard-address-space.yaml
addressspace.enmasse.io/myspace created

C:\Users\mp\Downloads\enmasse-0.33.0>oc get addressspace myspace
NAME READY PHASE AGE
myspace false Pending 9s

get address space still says it has no auth.
Ulf Lilleengen
@lulf
kubectl get authenticationservice -n enmasse-infra -o wide
mtmmtm9
@mtmmtm9
it gives: No resources found in enmasse-infra namespace.
I did this to create it: oc apply -f install/components/example-authservices/standard-authservice.yaml
authenticationservice.admin.enmasse.io/standard-authservice created
Ulf Lilleengen
@lulf
you might have created it in the wrong namespace
try kubectl apply -f install/components/example-authservices/standard-authservice.yaml -n enmasse-infra
if you follow https://enmasse.io/documentation/master/kubernetes.html#installing-using-bundle-messaging-gs - it recommends setting the namespace context to the namespace where you are installing enmasse
mtmmtm9
@mtmmtm9
thanks, it helped.
mtmmtm9
@mtmmtm9
I went throug the example again (not skipping optional steps). When checking address-space i get "myspace standard standard-unlimited false Configuring [The following deployments are not ready: [admin.30e3f82] The following stateful sets are not ready: [qdrouterd-30e3f82] No router status found.] 6m"
Ulf Lilleengen
@lulf
Yeah, thats expected. Just need to wait for images to be pulled down, started and the processes to be configured
mtmmtm9
@mtmmtm9
It got insufficient memory. I did not set memory when starting. Running on a laptop with 8G total.
Ulf Lilleengen
@lulf
Are you using minikube?
mtmmtm9
@mtmmtm9
yes. but i need more memory. need to get another machine (4 G is to little for it i guess?)
(well, minishift with hyperv).
Ulf Lilleengen
@lulf
6 might be enough
Lari Hotari
@lhotari

Hi, I'm currently evaluating Enmasse for IoT use cases and interested in how it integrates with Eclipse Hono. It seems that the currently website tagline for Enmasse "Multitenant, self-service messaging system for Kubernetes with first-class support for IoT" is misleading since MQTT & other IoT specific support have been removed from Enmasse in PRs EnMasseProject/enmasse#5113 and EnMasseProject/enmasse#5115 . The website also claims that Enmasse has "Support for IoT using HTTP, MQTT, Sigfox or LoRaWAN protocols." This is not the case anymore.

Since PRs #5113 & #5115 didn't contain any rational, could someone explain why IoT support was removed?
Are there plans to move the functionality in another project?
I noticed that a similar question was asked on Github: https://github.com/EnMasseProject/enmasse/pull/5115#issuecomment-724119178
Thank you

Ulf Lilleengen
@lulf
@lhotari Haven't gotten around to update the website yet. The IoT support was going to be first class in enmasse 1.0, but this release have been put on hold, and there are mostly maintenance work being done. You should be better off deploying Hono on your own going forward and point it to EnMasse as the AMQP 1.0 network for instance.
Lari Hotari
@lhotari
Thank you for a quick reply @lulf . Yes it makes sense to drop IoT support so that Enmasse doesn't have many different responsibilities and development can focus on the core functionality of Enmasse. I'll take a look at Hono docs and try to see how to use it with Enmasse.
Ulf Lilleengen
@lulf
@lhotari Website should be updated now :) Thanks for the reminder
Lari Hotari
@lhotari
@lulf that was quick. thanks.