August 2017 - aerogear-dev - Jboss List Archives

by Bruno Oliveira

Good morning, just to let you know we released today the bits for digital signatures and some bug fixes. Have a happy new year sweet hearts. -- abstractj

4 years, 3 months

2
1
0 / 0

Re: [aerogear-dev] AeroGear Digger Logo

by Ali Ok

Hello, According to the voting, logo #6 is the most favorite one. Here is the summary: [image: Inline image 1] I am delighted to present you AeroGear Digger's logo: [image: Inline image 2] Cheers, Ali On Mon, Jun 19, 2017 at 10:40 AM, Ali Ok <aliok(a)redhat.com> wrote: > Hello, > > We would like to pick a logo for the new AeroGear module, Digger [1]. > > James Cobb has already prepared some great designs and now we vote to pick > the best one [2]. > > We have prepared a Google poll (no login required) here: > https://goo.gl/forms/WdUoHecQtrshMkBg1 > > The poll will be open for 10 days (until June 29th 10:00 AM UTC). > > > [1] : https://github.com/aerogear/digger-jenkins > [2] : https://issues.jboss.org/browse/DESIGN-943 > > Cheers, > Ali >

8 years, 10 months

4
3
0 / 0

GSoC 2017: Student presentation, September 1st

by Matthias Wessendorf

Hi, as you all know, Polina Koleva and Dimitra Zuccarelli were our students this year, working on a POC that brings the UPS towards Apache Kafka as its internal message bus. On September 1st, 14:30 UTC, we will do a hangout-on-air, where the students give a little presentation about their work. Cheers, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

8 years, 12 months

2
2
0 / 0

WildFly loggers for Kafka

by Matthias Wessendorf

Hi, by default the Kafka client APIs log a lot on INFO. On IRC Polina and Dimitra were mentioning that. Here is a snippet for the "standalone.xml", to be inserted in the logging subsystem: <logger category="org.apache.kafka.streams.processor"> <level name="WARN"/> </logger> <logger category="org.apache.kafka.clients.producer.ProducerConfig"> <level name="WARN"/> </logger> <logger category="org.apache.kafka.clients.consumer.ConsumerConfig"> <level name="WARN"/> </logger> <logger category="org.apache.kafka.streams.StreamsConfig"> <level name="WARN"/> </logger> Greetings, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

8 years, 12 months

2
1
0 / 0

Removing old and deprecated Push Networks ?

by Matthias Wessendorf

Hi, we have server-side support for ADM (Amazon's Kindle Device push) as well as support for Microsofts' deprecated MPNS (Microsoft Push Notification Service) and SimplePush (from Firefox). I was wondering if we should remove those, on the master branch, going forward ? Would mean that UPS would be just supporting: * APNs (HTTP/2 only) * FCM (via HTTP only) * WNS (Windows Push Notification Services) How do folks feel about that ? Anyone actively using ADM, SimplePush or MPNS? Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

9 years

3
4
0 / 0

GSoC Update - a week before the end

by Polina Koleva

Hey, everyone :) It is almost the end of GSoC 2017, we have one more week left. Here is a quick summary what we have achieved since the previous update: * Dimitra has finished the implementation of custom object serialisers and deserialisers which gives us the ability to produce whatever we want to our topics. * We completely removed JMS. We are using Kafka producers, consumers and streams instead of it. So we can say that our push message epic <https://issues.jboss.org/browse/AGPUSH-2110> is completely implemented. * We have our first Kafka Stream ready to be merged. See PR <https://github.com/aerogear/aerogear-unifiedpush-server/pull/900> * We set up our test environment which gives us the ability to test consumers and producers used in UPS. See PR <https://github.com/aerogear/aerogear-unifiedpush-server/pull/895> * The next check on our list is collecting stats for push messages using Apache Kafka.The basic idea is summarized in this epic AGPUSH-2111 <https://issues.jboss.org/browse/AGPUSH-2111>. We have already come up with some proposals - AGPUSH-2187 <https://issues.jboss.org/browse/AGPUSH-2187> AGPUSH-2186 <https://issues.jboss.org/browse/AGPUSH-2186> AGPUSH-2188 <https://issues.jboss.org/browse/AGPUSH-2188>. But we are open for new ideas. What information will be good to have in terms of stats for push messages? For example, how many push messages are sent per application? per OS? in some interval of time? Glad to hear what you think. * Also stress testing of current Kafka implementation is good to be done if enough time available. For more information, you can take a look at our dashboard here. <https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=4022&view=planning> Thanks for the support and the help. Feedback is always appreciated. Polina & Dimitra

9 years

5
8
0 / 0

GSoC: no longer requiring the full profile

by Matthias Wessendorf

Hi, on the GSOC branch I just verified that we can use the normal config, no need for the -full profile. See for details: https://issues.jboss.org/browse/AGPUSH-2197 -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

9 years

1
1
0 / 0

Roadmap: UPS 1.2.0.Final and UPS.next

by Matthias Wessendorf

Folks! GSoC is wrapping up, and Polina and Dimitra have done great work on our "GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be merged to master, and stays for a little bit longer on that branch.... == 1.2.0.Final == Our last release for the 1.2.0 series was a BETA1, in May: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.2.... In order to move forward and release a 1.2.0 release to the community, I will be re-starting the looooooooooooong outstanding work to decouple UPS from our legacy Keycloak: https://issues.jboss.org/browse/AGPUSH-1047 this also helps us to be able to work on latest of WildFly, our legacy Keycloak currently is a blocker for moving towards WF11: https://issues.jboss.org/browse/AGPUSH-2117 Once that decoupling is done and complete, there will be a UPS 1.2.0.Final release, and Docker images will be updated to relay on WF11.Final (once out). == What's next ? == After that I'd like to merge the GSOC_2017_kafka branch to master, and also bump the version to 2.0.0-SNAPSHOT, since than we have Kafka integrated for the centralized messaging. Also, Docker images (and Openshift templates) will be updated - but all of that starts really _after_ the 1.2.0.Final is out. Any thoughts or comments? Thanks, Matthias! -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf

9 years

4
3
0 / 0

jboss server missing/unsatisified dependencies

by Rachael O'Regan

Hi all, I’m having issues with the jboss server on my vm. It’s failing to start and the server log reports this error: JBAS014775: New missing/unsatisfied dependencies: service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry] I’m using the latest fhcap and jboss-eap-6.4.15. My jboss config can be found here => https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b <https://gist.github.com/rachael-oregan/01e59e609a59a3b32fe436ada1e45c9b> The server log can be found here => https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22 <https://gist.github.com/rachael-oregan/ab5f268529e48c0f9fb253f82841db22> I’ve tried changing the config so remoting doesn’t use the management endpoint too - <remoting-connector use-management-endpoint=“false” /> I’ve created a new vm and still getting the same error. Any help is appreciated. Thanks, RACHAEL O'REGAN Red Hat Mobile Communications House, Cork Road Waterford City, Ireland X91NY33 roregan(a)redhat.com IM: roregan

9 years

3
6
0 / 0

AGDIGGER JIRA components

by Ali Ok

Hi, I think we need to update our JIRA components in AGDIGGER project. Perhaps these: - Android support - IOS support - Ansible Installer - Sample (I mean sample Jenkinsfiles) - Node client - Java client Anything missing or strange? @Matthias, can you do that? Cheers, Ali

9 years

4
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

aerogear-dev August 2017