True, but its just a bit sad that we are two people that have tried for 2 entire days to get a simple version working.
Openshift 3 template does not work, so we are ending up with a hack version to patch stuff together in the very last hours before deadline.
It would be great that next time EOL happens, then there is a very clear migration path. :)
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E:
mm@napp.dk
__________________
From:
<aerogear-dev-bounces@lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche@redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Friday, 29 September 2017 at 16.36
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
If you are silver customer, the deadline has been extended until December 31st, 2017.
https://blog.openshift.com/migrate-to-v3-v2-eol/
If you are not silver, maybe you can become silver until you have the replacement in place. (not really sure if it's possible to switch the plan at this moment, according to the comments, some users were able to do it a few days ago)
On Fri, Sep 29, 2017 at 11:25 AM, Mads Møller <mm@napp.dk> wrote:
Im also trying to use your docker version of UPS 1.2.
I've deployed it on my server, published to external port. But when I try to access the web ui, it tries to redirect me to internal docker ip
What is going on here?
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of "mm@napp.dk" <mm@napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Friday, 29 September 2017 at 10.04
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
It seems the documentation is incorrect on installling 1.2:
it says: $ ./path/to/SERVER_HOME/bin/jboss-cli.sh --file=/path/to/jms-setup-wildfly.cli
but no jms-setup-wildfly.cli in release package ?
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of "mm@napp.dk" <mm@napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Friday, 29 September 2017 at 09.53
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
Great idea. How do I export to json?
I dont know any export function in unified push.
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of Matthias Wessendorf <matzew@apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Friday, 29 September 2017 at 08.58
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
On Fri, 29 Sep 2017 at 08:00, Mads Møller <mm@napp.dk> wrote:
Hi,
I would love to update to 1.2. But the migrator fails. So I cannot upgrade until that is fixed also.
hrm...
try:
* export all installations from old
in new:
* create new variants. go to db and change variantID/secrets to old values.
* import devices from exported json file
Anyone else I can talk to on your team?
this list, or IRC ;-)
Again, ill gladly pay for some consultancy hours. Its the last day before our production server is shut down by openshift. :(
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of Matthias Wessendorf <matzew@apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>Date: Friday, 29 September 2017 at 07.48
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
Not sure - will look, but traveling most of the day
PS: I'd highly recommend using 1.2.0 we fixed performance issues, and memory leaks, especially in our APNS code path
On Fri, 29 Sep 2017 at 00:34, Mads Møller <mm@napp.dk> wrote:
We finally got a server running using ec2 and wildfly. Everything works, but when we send push messages out, then the server throws the below exception.
This does not happen on the openshift server.
Anyone knows why the two servers does not act the same?
14:46:38,491 SEVERE [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Error sending payload to APNs server: com.notnoop.exceptions.ApnsDeliveryErrorException: Failed to deliver notification with error code 8
at com.notnoop.apns.internal.ApnsConnectionImpl$2.run(ApnsConnectionImpl.java:199) [apns-1.0.0.Beta6.jar:]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
14:46:39,381 INFO [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (Thread-0 (HornetQ-client-global-threads-2020047067)) Sent push notification to the Apple APNs Server for 443 tokens
14:46:39,473 INFO [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-3) Removing invalid (not allowed) token: c651f284dc52511ed79e8a3e7a318bb6be39c7bc13129508ef4d0dfcd4608d00
MED VENLIG HILSEN / BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
On 28 Sep 2017, at 13.21, Mads Møller <mm@napp.dk> wrote:I will gladly pay one to help me out here.. We are two developers who cannot deploy AeroGear to: openshift, aws, or just regular ec2 server.
Please, if anyone have time – contact me.
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of "mm@napp.dk" <mm@napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
I got more resources connected to my account, but the aerogear server cannot deploy.
This two other apps works just fine: http://prntscr.com/gqomv3
But unifiedpush-server will not deploy: http://prntscr.com/gqolyk
I get:
Readiness probe failed: rpc error: code = 13 desc = invalid header field value "oci runtime error: exec failed: container \"f15bbd0887b42057604afa2de6a6243b8c3a51b1f97dbb21a809f62a6dc99c54\" does not exist\n"
Readiness probe failed: sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell --2017-09-28 09:33:01-- http://localhost:8080/ag-push Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:8080... failed: Connection refused. Connecting to localhost (localhost)|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying.
Anyone got Unified push server working in Openshift 3?
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of "mm@napp.dk" <mm@napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
Hi,
I did that and got: http://prntscr.com/gqnxw9
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche@redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
On Thu, Sep 28, 2017 at 10:24 AM, Mads Møller <mm@napp.dk> wrote:
Any guide on how to get it working on openshift 3?
From: <aerogear-dev-bounces@lists.jboss.org> on behalf of Matthias Wessendorf <matzew@apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev@lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS
I've no idea, honestly - I've never used AWS
On Thu, Sep 28, 2017 at 10:04 AM, Mads Møller <mm@napp.dk> wrote:
Hi list,
I truly need your help.
We have been trying for days to migrate our Unified Push server from the Openshift 2 that is sunset at sep 30th.
We have tried to migrate to AWS ECS, but the docker file does not work for us. it's because of the volumes I think, it wanted some files outside of docker image.
Does anyone know how to get Unified Push og the Keyclock to work with AWS container service?
If not, then please point me in a direction where I quickly can migrate too.
I would be very grateful if someone can help out.
BEST REGARDS
__________________
MADS MØLLER
CTO, PARTNER
Napp A/S
E: mm@napp.dk
__________________
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev