From lgriffin at redhat.com  Fri Sep  1 10:28:09 2017
From: lgriffin at redhat.com (Leigh Griffin)
Date: Fri, 1 Sep 2017 15:28:09 +0100
Subject: [aerogear-dev] GSoC 2017: Student presentation, September 1st
In-Reply-To: <CAAg5f2QumChtqjB++_84v=_QbN9f7GZyCTB+X+s6-XrS+9BnUw@mail.gmail.com>
References: <CAAg5f2TbeZnwezUbHKrEGfjva5Jm99rLe7ZtKcj_tgYX5yysfw@mail.gmail.com>
	<CAAg5f2QumChtqjB++_84v=_QbN9f7GZyCTB+X+s6-XrS+9BnUw@mail.gmail.com>
Message-ID: <CAOQ+Wrp9CsUT3UjnGg0vakBTZuH+tJEMU8KKT_MpqEuehuojcA@mail.gmail.com>

Reminder that this is happening in 2 minutes!

On Tue, Aug 29, 2017 at 12:25 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> https://www.youtube.com/watch?v=sBQBGRHDWtU
>
> On Tue, Aug 29, 2017 at 1:14 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> 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
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEIGH GRIFFIN

ENGINEERING MANAGER, MOBILE

Red Hat Ireland <https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

lgriffin at redhat.com    M: +353877545162     IM: lgriffin
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

@redhatway <https://twitter.com/redhatway>   @redhatinc
<https://instagram.com/redhatinc>   @redhatsnaps
<https://snapchat.com/add/redhatsnaps>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170901/e416b2f8/attachment-0001.html 

From matzew at apache.org  Fri Sep  1 11:25:21 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 1 Sep 2017 17:25:21 +0200
Subject: [aerogear-dev] GSoC 17: Kafka/UPS hangout-on-air
Message-ID: <CAAg5f2ShFQvfiM0FQrffYwfUb3d2_GzOzQuMyLgFrwt29Epj_Q@mail.gmail.com>

Hi folks!

we had a great hangout on air, where Polina and Dimitra did a rock solid
presentation of their summer's project. w00t!

The materials from the livestream are now all online. See below:

Recorded Video:
https://www.youtube.com/watch?v=sBQBGRHDWtU

Presentation side deck:
https://docs.google.com/presentation/d/1mWTZKgafKsurh6BrNi92oAZ_8-hC5nW6awSvAixjvrI/edit#slide=id.gc6fa3c898_0_0


WildFly Swarm Demo source:
https://github.com/dimitraz/mp-ups-demo

Demo Recording:
https://www.youtube.com/watch?v=J_4kgsAFhn4


If you have more questions, join us on #aerogear IRC channel, on freenode

Cheers,
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170901/29c23e06/attachment.html 

From aliok at redhat.com  Tue Sep  5 05:00:30 2017
From: aliok at redhat.com (Ali Ok)
Date: Tue, 5 Sep 2017 12:00:30 +0300
Subject: [aerogear-dev] GSoC 17: Kafka/UPS hangout-on-air
In-Reply-To: <CAAg5f2ShFQvfiM0FQrffYwfUb3d2_GzOzQuMyLgFrwt29Epj_Q@mail.gmail.com>
References: <CAAg5f2ShFQvfiM0FQrffYwfUb3d2_GzOzQuMyLgFrwt29Epj_Q@mail.gmail.com>
Message-ID: <CABoO8LcNUb1WaUjDJqAfvv=80CfaBY+eDqwBi75gYg575jAXXQ@mail.gmail.com>

Nice demo and great work Polina and Dimitra! Special thanks for sharing
your experience.

I hope you stay around in the community!

Cheers

On Fri, Sep 1, 2017 at 6:25 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> we had a great hangout on air, where Polina and Dimitra did a rock solid
> presentation of their summer's project. w00t!
>
> The materials from the livestream are now all online. See below:
>
> Recorded Video:
> https://www.youtube.com/watch?v=sBQBGRHDWtU
>
> Presentation side deck:
> https://docs.google.com/presentation/d/1mWTZKgafKsurh6BrNi92oAZ_8-
> hC5nW6awSvAixjvrI/edit#slide=id.gc6fa3c898_0_0
>
>
> WildFly Swarm Demo source:
> https://github.com/dimitraz/mp-ups-demo
>
> Demo Recording:
> https://www.youtube.com/watch?v=J_4kgsAFhn4
>
>
> If you have more questions, join us on #aerogear IRC channel, on freenode
>
> Cheers,
> Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170905/705788ff/attachment.html 

From matzew at apache.org  Tue Sep  5 12:00:21 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 5 Sep 2017 18:00:21 +0200
Subject: [aerogear-dev] UPS 1.2.0-beta.2 release
Message-ID: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>

Hi,

after some month of time, we are running a new release of the master
branch: 1.2.0-beta.2

Main fixes did include:
* WildFly 11 (CR1) support
* Keycloak decoulping
* SimplePush/MPNS removal
* version updates of the non Java EE dependencies

More details can be found here:
https://issues.jboss.org/projects/AGPUSH/versions/12335470

Staging repo is located here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-12282/

Once the release is out, I will update the docker images and compose file
(including a decouple Keycloak)

Have fun!
-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170905/cd93ad6b/attachment.html 

From matzew at apache.org  Wed Sep  6 06:57:37 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 6 Sep 2017 12:57:37 +0200
Subject: [aerogear-dev] UPS 1.2.0-beta.2 release
In-Reply-To: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>
References: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>
Message-ID: <CAAg5f2TD25fyVgVCMC20HrJjPvwpkCyRF2Z=difKWL1qFKDE_g@mail.gmail.com>

Ok, clicked the button.

this will be online tomorrow

In a few days, we might see a CR1 - and shortly after that a .Final :-)

Cheers,
Matthias

On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> after some month of time, we are running a new release of the master
> branch: 1.2.0-beta.2
>
> Main fixes did include:
> * WildFly 11 (CR1) support
> * Keycloak decoulping
> * SimplePush/MPNS removal
> * version updates of the non Java EE dependencies
>
> More details can be found here:
> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>
> Staging repo is located here:
> https://repository.jboss.org/nexus/content/repositories/
> jboss_releases_staging_profile-12282/
>
> Once the release is out, I will update the docker images and compose file
> (including a decouple Keycloak)
>
> Have fun!
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170906/d8547059/attachment.html 

From matzew at apache.org  Wed Sep  6 11:14:48 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 6 Sep 2017 17:14:48 +0200
Subject: [aerogear-dev] UPS 1.2.0-beta.2 release
In-Reply-To: <CAAg5f2TD25fyVgVCMC20HrJjPvwpkCyRF2Z=difKWL1qFKDE_g@mail.gmail.com>
References: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>
	<CAAg5f2TD25fyVgVCMC20HrJjPvwpkCyRF2Z=difKWL1qFKDE_g@mail.gmail.com>
Message-ID: <CAAg5f2RxS4-3GZfbo-CF2jJxyTL6x_Eu8_H5X552DQq_VRyyjA@mail.gmail.com>

release candidate 1 is here:

https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-12288/

-M

On Wed, Sep 6, 2017 at 12:57 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Ok, clicked the button.
>
> this will be online tomorrow
>
> In a few days, we might see a CR1 - and shortly after that a .Final :-)
>
> Cheers,
> Matthias
>
> On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> after some month of time, we are running a new release of the master
>> branch: 1.2.0-beta.2
>>
>> Main fixes did include:
>> * WildFly 11 (CR1) support
>> * Keycloak decoulping
>> * SimplePush/MPNS removal
>> * version updates of the non Java EE dependencies
>>
>> More details can be found here:
>> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>>
>> Staging repo is located here:
>> https://repository.jboss.org/nexus/content/repositories/jbos
>> s_releases_staging_profile-12282/
>>
>> Once the release is out, I will update the docker images and compose file
>> (including a decouple Keycloak)
>>
>> Have fun!
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170906/9b5bf0c3/attachment-0001.html 

From matzew at apache.org  Mon Sep 11 08:40:58 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 11 Sep 2017 14:40:58 +0200
Subject: [aerogear-dev] UPS 1.2.0-beta.2 release
In-Reply-To: <CAAg5f2RxS4-3GZfbo-CF2jJxyTL6x_Eu8_H5X552DQq_VRyyjA@mail.gmail.com>
References: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>
	<CAAg5f2TD25fyVgVCMC20HrJjPvwpkCyRF2Z=difKWL1qFKDE_g@mail.gmail.com>
	<CAAg5f2RxS4-3GZfbo-CF2jJxyTL6x_Eu8_H5X552DQq_VRyyjA@mail.gmail.com>
Message-ID: <CAAg5f2RGR+xEMniKehV2U-_u2tzqLBE3OpCsVz4nVyGQH01fkw@mail.gmail.com>

Tomorrow, I will start the 1.2.0.Final release

afterwards will update the docker images

On Wed, Sep 6, 2017 at 5:14 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> release candidate 1 is here:
>
> https://repository.jboss.org/nexus/content/repositories/
> jboss_releases_staging_profile-12288/
>
> -M
>
> On Wed, Sep 6, 2017 at 12:57 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Ok, clicked the button.
>>
>> this will be online tomorrow
>>
>> In a few days, we might see a CR1 - and shortly after that a .Final :-)
>>
>> Cheers,
>> Matthias
>>
>> On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> after some month of time, we are running a new release of the master
>>> branch: 1.2.0-beta.2
>>>
>>> Main fixes did include:
>>> * WildFly 11 (CR1) support
>>> * Keycloak decoulping
>>> * SimplePush/MPNS removal
>>> * version updates of the non Java EE dependencies
>>>
>>> More details can be found here:
>>> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>>>
>>> Staging repo is located here:
>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>> s_releases_staging_profile-12282/
>>>
>>> Once the release is out, I will update the docker images and compose
>>> file (including a decouple Keycloak)
>>>
>>> Have fun!
>>> -Matthias
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170911/58aa9c2e/attachment.html 

From matzew at apache.org  Wed Sep 13 10:33:07 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 13 Sep 2017 16:33:07 +0200
Subject: [aerogear-dev] UPS 1.2.0-beta.2 release
In-Reply-To: <CAAg5f2RGR+xEMniKehV2U-_u2tzqLBE3OpCsVz4nVyGQH01fkw@mail.gmail.com>
References: <CAAg5f2To51iz7WW0SKU=Pou_bL6razSc51O+f5KWRP-xijNCyA@mail.gmail.com>
	<CAAg5f2TD25fyVgVCMC20HrJjPvwpkCyRF2Z=difKWL1qFKDE_g@mail.gmail.com>
	<CAAg5f2RxS4-3GZfbo-CF2jJxyTL6x_Eu8_H5X552DQq_VRyyjA@mail.gmail.com>
	<CAAg5f2RGR+xEMniKehV2U-_u2tzqLBE3OpCsVz4nVyGQH01fkw@mail.gmail.com>
Message-ID: <CAAg5f2T6ZjSYh93e8YdGOuHm+vR1nFE-4b2uMiuOdpJqCefe2Q@mail.gmail.com>

RC2 is available for evaluation:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-12344/

big difference between rc1 and rc2 is just this one JIRA:
https://issues.jboss.org/browse/AGPUSH-1368

-M

On Mon, Sep 11, 2017 at 2:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Tomorrow, I will start the 1.2.0.Final release
>
> afterwards will update the docker images
>
> On Wed, Sep 6, 2017 at 5:14 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> release candidate 1 is here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jbos
>> s_releases_staging_profile-12288/
>>
>> -M
>>
>> On Wed, Sep 6, 2017 at 12:57 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Ok, clicked the button.
>>>
>>> this will be online tomorrow
>>>
>>> In a few days, we might see a CR1 - and shortly after that a .Final :-)
>>>
>>> Cheers,
>>> Matthias
>>>
>>> On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> after some month of time, we are running a new release of the master
>>>> branch: 1.2.0-beta.2
>>>>
>>>> Main fixes did include:
>>>> * WildFly 11 (CR1) support
>>>> * Keycloak decoulping
>>>> * SimplePush/MPNS removal
>>>> * version updates of the non Java EE dependencies
>>>>
>>>> More details can be found here:
>>>> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>>>>
>>>> Staging repo is located here:
>>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>>> s_releases_staging_profile-12282/
>>>>
>>>> Once the release is out, I will update the docker images and compose
>>>> file (including a decouple Keycloak)
>>>>
>>>> Have fun!
>>>> -Matthias
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170913/cbd460e4/attachment.html 

From matzew at apache.org  Thu Sep 14 06:20:06 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 14 Sep 2017 12:20:06 +0200
Subject: [aerogear-dev] 1.2.0.Final (was: Re: UPS 1.2.0-beta.2 release)
Message-ID: <CAAg5f2Rzyc4jkBWWCn-3gLNU5uL8bJ4Nfsyy+ZBdC=W5neQYsw@mail.gmail.com>

Things are staged here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-12353/

It's basically stable since we did the last beta releases, and requires now
WF10 or later, and Keycloak is required to be separated as well

-M

On Wed, Sep 13, 2017 at 4:33 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> RC2 is available for evaluation:
> https://repository.jboss.org/nexus/content/repositories/
> jboss_releases_staging_profile-12344/
>
> big difference between rc1 and rc2 is just this one JIRA:
> https://issues.jboss.org/browse/AGPUSH-1368
>
> -M
>
> On Mon, Sep 11, 2017 at 2:40 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Tomorrow, I will start the 1.2.0.Final release
>>
>> afterwards will update the docker images
>>
>> On Wed, Sep 6, 2017 at 5:14 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> release candidate 1 is here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>> s_releases_staging_profile-12288/
>>>
>>> -M
>>>
>>> On Wed, Sep 6, 2017 at 12:57 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Ok, clicked the button.
>>>>
>>>> this will be online tomorrow
>>>>
>>>> In a few days, we might see a CR1 - and shortly after that a .Final :-)
>>>>
>>>> Cheers,
>>>> Matthias
>>>>
>>>> On Tue, Sep 5, 2017 at 6:00 PM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> after some month of time, we are running a new release of the master
>>>>> branch: 1.2.0-beta.2
>>>>>
>>>>> Main fixes did include:
>>>>> * WildFly 11 (CR1) support
>>>>> * Keycloak decoulping
>>>>> * SimplePush/MPNS removal
>>>>> * version updates of the non Java EE dependencies
>>>>>
>>>>> More details can be found here:
>>>>> https://issues.jboss.org/projects/AGPUSH/versions/12335470
>>>>>
>>>>> Staging repo is located here:
>>>>> https://repository.jboss.org/nexus/content/repositories/jbos
>>>>> s_releases_staging_profile-12282/
>>>>>
>>>>> Once the release is out, I will update the docker images and compose
>>>>> file (including a decouple Keycloak)
>>>>>
>>>>> Have fun!
>>>>> -Matthias
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170914/fc88db03/attachment-0001.html 

From matzew at apache.org  Wed Sep 20 02:28:01 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 20 Sep 2017 08:28:01 +0200
Subject: [aerogear-dev] Fwd: [pushy] Pushy v0.11 has been released
In-Reply-To: <fa773633-3fb0-42cb-9ba4-e1ae80c96d7c@googlegroups.com>
References: <fa773633-3fb0-42cb-9ba4-e1ae80c96d7c@googlegroups.com>
Message-ID: <CAAg5f2RKk=yp0=UKrWiXV=VCGJ5hgV6dkyn=ROwkU-SvZ21WqQ@mail.gmail.com>

It's quite a change, and needs code to get it working

-M


---------- Forwarded message ----------
From: <jon at turo.com>
Date: Wed, Sep 20, 2017 at 4:26 AM
Subject: [pushy] Pushy v0.11 has been released
To: pushy <pushy-apns at googlegroups.com>


Friends,

I'm pleased to announce that Pushy v0.11 has been released and is on its
way to Maven Central.

This release represents a significant architectural shift. ApnsClient
instances now maintain their own internal connection pools, connect on
demand, and will manage all of the reconnection timing on their own. This
should make life much simpler for most users, and should open the door to
performance gains for industrial-scale users who were previously
constrained by running clients on a single thread. This should also fix a
host of reported bugs around reconnection and resource usage.

Other changes include:

   - Updated to Netty 4.1.14 for the latest bug fixes and performance
   improvements
   - Restored reference-counted SSL providers, which should resolve issues
   around direct memory usage and reclamation
   - Added support for building MDM payloads

For a complete list of changes, please see the v0.11 milestone
<https://github.com/relayrides/pushy/milestone/24?closed=1>.

Cheers!

-Jon

-- 
Pushy is an open-source Java library for sending APNs (iOS and OS X) push
notifications. Pushy is brought to you by the engineers at RelayRides.
---
You received this message because you are subscribed to the Google Groups
"pushy" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to pushy-apns+unsubscribe at googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/ae9a72a0/attachment.html 

From matzew at apache.org  Wed Sep 20 03:44:28 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 20 Sep 2017 09:44:28 +0200
Subject: [aerogear-dev] [pushy] Pushy v0.11 has been released
In-Reply-To: <CAAg5f2RKk=yp0=UKrWiXV=VCGJ5hgV6dkyn=ROwkU-SvZ21WqQ@mail.gmail.com>
References: <fa773633-3fb0-42cb-9ba4-e1ae80c96d7c@googlegroups.com>
	<CAAg5f2RKk=yp0=UKrWiXV=VCGJ5hgV6dkyn=ROwkU-SvZ21WqQ@mail.gmail.com>
Message-ID: <CAAg5f2TfBEkuJkQ=m6N35EyrDjjhadid78dUUyZAqShUfDrorA@mail.gmail.com>

I've created this JIRA:
https://issues.jboss.org/browse/AGPUSH-2209

On Wed, Sep 20, 2017 at 8:28 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> It's quite a change, and needs code to get it working
>
> -M
>
>
> ---------- Forwarded message ----------
> From: <jon at turo.com>
> Date: Wed, Sep 20, 2017 at 4:26 AM
> Subject: [pushy] Pushy v0.11 has been released
> To: pushy <pushy-apns at googlegroups.com>
>
>
> Friends,
>
> I'm pleased to announce that Pushy v0.11 has been released and is on its
> way to Maven Central.
>
> This release represents a significant architectural shift. ApnsClient
> instances now maintain their own internal connection pools, connect on
> demand, and will manage all of the reconnection timing on their own. This
> should make life much simpler for most users, and should open the door to
> performance gains for industrial-scale users who were previously
> constrained by running clients on a single thread. This should also fix a
> host of reported bugs around reconnection and resource usage.
>
> Other changes include:
>
>    - Updated to Netty 4.1.14 for the latest bug fixes and performance
>    improvements
>    - Restored reference-counted SSL providers, which should resolve
>    issues around direct memory usage and reclamation
>    - Added support for building MDM payloads
>
> For a complete list of changes, please see the v0.11 milestone
> <https://github.com/relayrides/pushy/milestone/24?closed=1>.
>
> Cheers!
>
> -Jon
>
> --
> Pushy is an open-source Java library for sending APNs (iOS and OS X) push
> notifications. Pushy is brought to you by the engineers at RelayRides.
> ---
> You received this message because you are subscribed to the Google Groups
> "pushy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pushy-apns+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/96445102/attachment.html 

From aliok at redhat.com  Wed Sep 20 04:27:30 2017
From: aliok at redhat.com (Ali Ok)
Date: Wed, 20 Sep 2017 11:27:30 +0300
Subject: [aerogear-dev] digger-test repo in AG org
Message-ID: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>

Hello,

Could somebody please help me moving
https://github.com/aliok/digger-test/tree/flesh-out to GH AG org?

I don't have the necessary permissions.

For the curious, this is the new testing suite for AeroGear Digger. We pull
templates from https://github.com/feedhenry/fh-template-apps global.json
file and feed them to a build farm to make sure they're built nicely.

The code has some work to do, but it is still a good time to start
migrating it to AG org.

Thanks,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/7c7e4647/attachment.html 

From matzew at apache.org  Wed Sep 20 08:21:28 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 20 Sep 2017 14:21:28 +0200
Subject: [aerogear-dev] digger-test repo in AG org
In-Reply-To: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
References: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
Message-ID: <CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>

like a fork  ?

or more like an import ?

On Wed, Sep 20, 2017 at 10:27 AM, Ali Ok <aliok at redhat.com> wrote:

> Hello,
>
> Could somebody please help me moving https://github.com/
> aliok/digger-test/tree/flesh-out to GH AG org?
>
> I don't have the necessary permissions.
>
> For the curious, this is the new testing suite for AeroGear Digger. We
> pull templates from https://github.com/feedhenry/fh-template-apps
> global.json file and feed them to a build farm to make sure they're built
> nicely.
>
> The code has some work to do, but it is still a good time to start
> migrating it to AG org.
>
> Thanks,
> Ali
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/6bb1983c/attachment.html 

From aliok at redhat.com  Wed Sep 20 09:17:15 2017
From: aliok at redhat.com (Ali Ok)
Date: Wed, 20 Sep 2017 16:17:15 +0300
Subject: [aerogear-dev] digger-test repo in AG org
In-Reply-To: <CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>
References: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
	<CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>
Message-ID: <CABoO8Lcyi=vXvCSbOWe8v6EhkuW3m_4ukS103FqFD=p64fg47A@mail.gmail.com>

More like an import...

I think just create a repo in AG GH and give me access rights. After that,
it is just pushing to a new remote for me :)

We can discard our own repos (@matskiv and I) and fork again from the AG
repo.

We pull templates from https://github.com/feedhenry/fh-template-apps
global.json
> file and feed them to a build farm to make sure they're built nicely.

BTW, after a short talk with @matskiv, we think perhaps we can create a
separate repo for testing FeedHenry templates. Although those templates are
open sourced, it might be better to just test features in the pure
community testing suite, not templates.
This would mean 3 testing suites in separate repositories:

1. BF feature testing suite (%100 pure community version)
2. FeedHenry open source templates testing suite
3. Red Hat productized templates testing suite

These of course will extend from a base (we'll use suite#1 as the base) and
will have very minimal changes to maintain.

Wdyt AeroGear devs?


On Wed, Sep 20, 2017 at 3:21 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> like a fork  ?
>
> or more like an import ?
>
> On Wed, Sep 20, 2017 at 10:27 AM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hello,
>>
>> Could somebody please help me moving https://github.com/alio
>> k/digger-test/tree/flesh-out to GH AG org?
>>
>> I don't have the necessary permissions.
>>
>> For the curious, this is the new testing suite for AeroGear Digger. We
>> pull templates from https://github.com/feedhenry/fh-template-apps
>> global.json file and feed them to a build farm to make sure they're built
>> nicely.
>>
>> The code has some work to do, but it is still a good time to start
>> migrating it to AG org.
>>
>> Thanks,
>> Ali
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/3f7db53a/attachment-0001.html 

From matzew at apache.org  Wed Sep 20 11:08:34 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 20 Sep 2017 15:08:34 +0000
Subject: [aerogear-dev] digger-test repo in AG org
In-Reply-To: <CABoO8Lcyi=vXvCSbOWe8v6EhkuW3m_4ukS103FqFD=p64fg47A@mail.gmail.com>
References: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
	<CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>
	<CABoO8Lcyi=vXvCSbOWe8v6EhkuW3m_4ukS103FqFD=p64fg47A@mail.gmail.com>
Message-ID: <CAAg5f2TbbX4O1N1NXN05+YQEA6YXa01Z28=Phr5M_0hSFqrVJA@mail.gmail.com>

On Wed, 20 Sep 2017 at 15:57, Ali Ok <aliok at redhat.com> wrote:

> More like an import...
>

ok, will do

>
> I think just create a repo in AG GH and give me access rights. After that,
> it is just pushing to a new remote for me :)
>
> We can discard our own repos (@matskiv and I) and fork again from the AG
> repo.
>
> We pull templates from https://github.com/feedhenry/fh-template-apps global.json
>> file and feed them to a build farm to make sure they're built nicely.
>
> BTW, after a short talk with @matskiv, we think perhaps we can create a
> separate repo for testing FeedHenry templates. Although those templates are
> open sourced, it might be better to just test features in the pure
> community testing suite, not templates.
> This would mean 3 testing suites in separate repositories:
>
> 1. BF feature testing suite (%100 pure community version)
> 2. FeedHenry open source templates testing suite
>

sure


3. Red Hat productized templates testing suite
>
> These of course will extend from a base (we'll use suite#1 as the base)
> and will have very minimal changes to maintain.
>
> Wdyt AeroGear devs?
>
>
> On Wed, Sep 20, 2017 at 3:21 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> like a fork  ?
>>
>> or more like an import ?
>>
>> On Wed, Sep 20, 2017 at 10:27 AM, Ali Ok <aliok at redhat.com> wrote:
>>
>>> Hello,
>>>
>>> Could somebody please help me moving
>>> https://github.com/aliok/digger-test/tree/flesh-out to GH AG org?
>>>
>>> I don't have the necessary permissions.
>>>
>>> For the curious, this is the new testing suite for AeroGear Digger. We
>>> pull templates from https://github.com/feedhenry/fh-template-apps
>>> global.json file and feed them to a build farm to make sure they're built
>>> nicely.
>>>
>>> The code has some work to do, but it is still a good time to start
>>> migrating it to AG org.
>>>
>>> Thanks,
>>> Ali
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/d0ab19c3/attachment.html 

From jusanche at redhat.com  Wed Sep 20 12:11:52 2017
From: jusanche at redhat.com (Julio Cesar Sanchez Hernandez)
Date: Wed, 20 Sep 2017 18:11:52 +0200
Subject: [aerogear-dev] aerogear-ios-http 2.0.0 for Swift4 released
Message-ID: <CA+-uZpvjnqzVC-MRLL_tJdO1-DinKqkBxiHmNJ-jSWO6gk-Q1A@mail.gmail.com>

Hi,

We have updated aerogear-ios-http to Swift 4 and it has been released in
CocoaPods as 2.0.0.
It also drops support for iOS 8.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/7bef5088/attachment.html 

From matzew at apache.org  Wed Sep 20 12:23:03 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 20 Sep 2017 18:23:03 +0200
Subject: [aerogear-dev] digger-test repo in AG org
In-Reply-To: <CAAg5f2TbbX4O1N1NXN05+YQEA6YXa01Z28=Phr5M_0hSFqrVJA@mail.gmail.com>
References: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
	<CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>
	<CABoO8Lcyi=vXvCSbOWe8v6EhkuW3m_4ukS103FqFD=p64fg47A@mail.gmail.com>
	<CAAg5f2TbbX4O1N1NXN05+YQEA6YXa01Z28=Phr5M_0hSFqrVJA@mail.gmail.com>
Message-ID: <CAAg5f2Tf77rGmw+YymbYU_bob6PFtVXMC7t4+F=fQF6ORXCm_w@mail.gmail.com>

https://github.com/aerogear/digger-test/



On Wed, Sep 20, 2017 at 5:08 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
> On Wed, 20 Sep 2017 at 15:57, Ali Ok <aliok at redhat.com> wrote:
>
>> More like an import...
>>
>
> ok, will do
>
>>
>> I think just create a repo in AG GH and give me access rights. After
>> that, it is just pushing to a new remote for me :)
>>
>> We can discard our own repos (@matskiv and I) and fork again from the AG
>> repo.
>>
>> We pull templates from https://github.com/feedhenry/fh-template-apps global.json
>>> file and feed them to a build farm to make sure they're built nicely.
>>
>> BTW, after a short talk with @matskiv, we think perhaps we can create a
>> separate repo for testing FeedHenry templates. Although those templates are
>> open sourced, it might be better to just test features in the pure
>> community testing suite, not templates.
>> This would mean 3 testing suites in separate repositories:
>>
>> 1. BF feature testing suite (%100 pure community version)
>> 2. FeedHenry open source templates testing suite
>>
>
> sure
>
>
> 3. Red Hat productized templates testing suite
>>
>> These of course will extend from a base (we'll use suite#1 as the base)
>> and will have very minimal changes to maintain.
>>
>> Wdyt AeroGear devs?
>>
>>
>> On Wed, Sep 20, 2017 at 3:21 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> like a fork  ?
>>>
>>> or more like an import ?
>>>
>>> On Wed, Sep 20, 2017 at 10:27 AM, Ali Ok <aliok at redhat.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> Could somebody please help me moving https://github.com/
>>>> aliok/digger-test/tree/flesh-out to GH AG org?
>>>>
>>>> I don't have the necessary permissions.
>>>>
>>>> For the curious, this is the new testing suite for AeroGear Digger. We
>>>> pull templates from https://github.com/feedhenry/fh-template-apps
>>>> global.json file and feed them to a build farm to make sure they're built
>>>> nicely.
>>>>
>>>> The code has some work to do, but it is still a good time to start
>>>> migrating it to AG org.
>>>>
>>>> Thanks,
>>>> Ali
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
> Sent from Gmail Mobile
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170920/828fb317/attachment.html 

From aliok at redhat.com  Thu Sep 21 08:24:27 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 21 Sep 2017 15:24:27 +0300
Subject: [aerogear-dev] digger-test repo in AG org
In-Reply-To: <CAAg5f2Tf77rGmw+YymbYU_bob6PFtVXMC7t4+F=fQF6ORXCm_w@mail.gmail.com>
References: <CABoO8Ldg5TD73D7UoLuFDj5ZFLx_GCcEzMcYT_SD=-OaggmvyQ@mail.gmail.com>
	<CAAg5f2QSoFbWAdk0hPGHg9PMeR2u66i7gwLMkUzbCN3ri81igw@mail.gmail.com>
	<CABoO8Lcyi=vXvCSbOWe8v6EhkuW3m_4ukS103FqFD=p64fg47A@mail.gmail.com>
	<CAAg5f2TbbX4O1N1NXN05+YQEA6YXa01Z28=Phr5M_0hSFqrVJA@mail.gmail.com>
	<CAAg5f2Tf77rGmw+YymbYU_bob6PFtVXMC7t4+F=fQF6ORXCm_w@mail.gmail.com>
Message-ID: <CABoO8LeTKqAeuowzr0z9HxBnEpsRW6AJJQc_SqzSFuXZJ5FbKg@mail.gmail.com>

Thanks, will migrate soon.

On Wed, Sep 20, 2017 at 7:23 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> https://github.com/aerogear/digger-test/
>
>
>
> On Wed, Sep 20, 2017 at 5:08 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>> On Wed, 20 Sep 2017 at 15:57, Ali Ok <aliok at redhat.com> wrote:
>>
>>> More like an import...
>>>
>>
>> ok, will do
>>
>>>
>>> I think just create a repo in AG GH and give me access rights. After
>>> that, it is just pushing to a new remote for me :)
>>>
>>> We can discard our own repos (@matskiv and I) and fork again from the AG
>>> repo.
>>>
>>> We pull templates from https://github.com/feedhenry/fh-template-apps
>>>>  global.json file and feed them to a build farm to make sure they're
>>>> built nicely.
>>>
>>> BTW, after a short talk with @matskiv, we think perhaps we can create a
>>> separate repo for testing FeedHenry templates. Although those templates are
>>> open sourced, it might be better to just test features in the pure
>>> community testing suite, not templates.
>>> This would mean 3 testing suites in separate repositories:
>>>
>>> 1. BF feature testing suite (%100 pure community version)
>>> 2. FeedHenry open source templates testing suite
>>>
>>
>> sure
>>
>>
>> 3. Red Hat productized templates testing suite
>>>
>>> These of course will extend from a base (we'll use suite#1 as the base)
>>> and will have very minimal changes to maintain.
>>>
>>> Wdyt AeroGear devs?
>>>
>>>
>>> On Wed, Sep 20, 2017 at 3:21 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> like a fork  ?
>>>>
>>>> or more like an import ?
>>>>
>>>> On Wed, Sep 20, 2017 at 10:27 AM, Ali Ok <aliok at redhat.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Could somebody please help me moving https://github.com/alio
>>>>> k/digger-test/tree/flesh-out to GH AG org?
>>>>>
>>>>> I don't have the necessary permissions.
>>>>>
>>>>> For the curious, this is the new testing suite for AeroGear Digger. We
>>>>> pull templates from https://github.com/feedhenry/fh-template-apps
>>>>> global.json file and feed them to a build farm to make sure they're built
>>>>> nicely.
>>>>>
>>>>> The code has some work to do, but it is still a good time to start
>>>>> migrating it to AG org.
>>>>>
>>>>> Thanks,
>>>>> Ali
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at 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 at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> --
>> Sent from Gmail Mobile
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170921/4570ff14/attachment-0001.html 

From dpassos at redhat.com  Thu Sep 21 15:52:51 2017
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 21 Sep 2017 16:52:51 -0300
Subject: [aerogear-dev] Organizing AeroGear iOS Pods
Message-ID: <CADF=h2tWCdjB9SAuw01LfTYxMY3uwuiGKUe8F8VHdoCWZCMf=w@mail.gmail.com>

Hi!

Julio and I are preparing new releases for all our iOS libraries and we
realized the Pods name are a mess

Some projects are using

Repo name: aerogear-ios-[feature]
Project: aerogear-[feature]
Pod: aerogear-[feature]

We wanna move all our libraries to the same page renaming all to the
following pattern:

Repo name: aerogear-ios-[feature]
Project: AeroGear[Feature]
Pod: AeroGear[Feature]

Changing the library name in CocoaPods is not a cool thing to do, but since
the next release will be a major I do not see a problem.

Wdyt?


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170921/0b1e2ffb/attachment.html 

From matzew at apache.org  Thu Sep 21 19:10:08 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 21 Sep 2017 23:10:08 +0000
Subject: [aerogear-dev] Organizing AeroGear iOS Pods
In-Reply-To: <CADF=h2tWCdjB9SAuw01LfTYxMY3uwuiGKUe8F8VHdoCWZCMf=w@mail.gmail.com>
References: <CADF=h2tWCdjB9SAuw01LfTYxMY3uwuiGKUe8F8VHdoCWZCMf=w@mail.gmail.com>
Message-ID: <CAAg5f2T2JQ+v9=hjgPERvGQ-w=-fJvSmT6yzcQ1zC-u-oWRMag@mail.gmail.com>

On Thu, 21 Sep 2017 at 23:13, Daniel Passos <dpassos at redhat.com> wrote:

> Hi!
>
> Julio and I are preparing new releases for all our iOS libraries and we
> realized the Pods name are a mess
>
> Some projects are using
>
> Repo name: aerogear-ios-[feature]
> Project: aerogear-[feature]
> Pod: aerogear-[feature]
>
> We wanna move all our libraries to the same page renaming all to the
> following pattern:
>
> Repo name: aerogear-ios-[feature]
> Project: AeroGear[Feature]
> Pod: AeroGear[Feature]
>
> Changing the library name in CocoaPods is not a cool thing to do, but
> since the next release will be a major I do not see a problem.
>
> Wdyt?
>
>
+1




> --
> -- Passos
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170921/e3c79e43/attachment.html 

From jgallaso at redhat.com  Fri Sep 22 02:31:35 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Fri, 22 Sep 2017 08:31:35 +0200
Subject: [aerogear-dev] Organizing AeroGear iOS Pods
In-Reply-To: <CAAg5f2T2JQ+v9=hjgPERvGQ-w=-fJvSmT6yzcQ1zC-u-oWRMag@mail.gmail.com>
References: <CADF=h2tWCdjB9SAuw01LfTYxMY3uwuiGKUe8F8VHdoCWZCMf=w@mail.gmail.com>
	<CAAg5f2T2JQ+v9=hjgPERvGQ-w=-fJvSmT6yzcQ1zC-u-oWRMag@mail.gmail.com>
Message-ID: <CAGsbZmH_zkpCv+PqY4uhovs4y565=Qxb+8bOe4JPBwOGhhLVjA@mail.gmail.com>

+1, consistent naming is a must

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>

On 22 September 2017 at 01:10, Matthias Wessendorf <matzew at apache.org>
wrote:

>
> On Thu, 21 Sep 2017 at 23:13, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Hi!
>>
>> Julio and I are preparing new releases for all our iOS libraries and we
>> realized the Pods name are a mess
>>
>> Some projects are using
>>
>> Repo name: aerogear-ios-[feature]
>> Project: aerogear-[feature]
>> Pod: aerogear-[feature]
>>
>> We wanna move all our libraries to the same page renaming all to the
>> following pattern:
>>
>> Repo name: aerogear-ios-[feature]
>> Project: AeroGear[Feature]
>> Pod: AeroGear[Feature]
>>
>> Changing the library name in CocoaPods is not a cool thing to do, but
>> since the next release will be a major I do not see a problem.
>>
>> Wdyt?
>>
>>
> +1
>
>
>
>
>> --
>> -- Passos
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170922/32f779cf/attachment.html 

From matzew at apache.org  Tue Sep 26 06:21:08 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 26 Sep 2017 12:21:08 +0200
Subject: [aerogear-dev] Digger-Install and GlusterFS
Message-ID: <CAAg5f2QcnUuietWsagTGKFcW3dr-c1Oyiitkh6WHK2XsmfSgBQ@mail.gmail.com>

Hi,

trying the digger install, and glusterFS,

getting the following error, when running "oc create -f
pv-sample-templates/jenkins/sample-pv-gluster.json":


Error from server (BadRequest): error when creating
"pv-sample-templates/jenkins/sample-pv-gluster.json": PersistentVolume in
version "v1" cannot be handled as a PersistentVolume: [pos 224]: json:
decode bool: got first char "

as well, I am getting the same error for the Android SDK template:

 pv-sample-templates/android-skd-linux/sample-pv-gluster.json


any ideas ?


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170926/486ac573/attachment.html 

From matzew at apache.org  Tue Sep 26 08:53:08 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 26 Sep 2017 14:53:08 +0200
Subject: [aerogear-dev] Digger-Installer problem
Message-ID: <CAAg5f2QxT=Ub5GKUN+X_Bh7NPSc6Nb1VGPdXUQ+RjYHckw3m7Q@mail.gmail.com>

Hi,

I am using this inventory files:
https://gist.githubusercontent.com/matzew/ca6b0481c53db4c6d7df7b521b84529b/raw/6d553ba81157e1fe2036e3e9d7ddf91ad7fffd58/matzew-inventory

and this branch (I had to remove java, for some weird/undocumented reasons,
to move on):
https://github.com/matzew/digger-installer/tree/Problems_running_install


With a bit of help from Leo on IRC I got to a point where I installed the
Android SDK, but the ansible-playbook process exits after some time w/ the
following message:

https://gist.githubusercontent.com/matzew/a06cb779f430ccbde2fa3ba6a97c32d1/raw/65ff9e6b5d5fbfcebeb737cdc5c50ded0f3e75ec/error


any ideas ?  Is this a known issue? Do you want me to create a JIRA ?

Thx,
Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170926/60ca8a46/attachment.html 

From lfitzger at redhat.com  Tue Sep 26 10:35:02 2017
From: lfitzger at redhat.com (Laura Fitzgerald)
Date: Tue, 26 Sep 2017 15:35:02 +0100
Subject: [aerogear-dev] Digger-Install and GlusterFS
In-Reply-To: <CAAg5f2QcnUuietWsagTGKFcW3dr-c1Oyiitkh6WHK2XsmfSgBQ@mail.gmail.com>
References: <CAAg5f2QcnUuietWsagTGKFcW3dr-c1Oyiitkh6WHK2XsmfSgBQ@mail.gmail.com>
Message-ID: <CA+jLkhVjuWiyVyKCmA1-nyFR8762b1TAuN2_w9TdY_HPaPQocQ@mail.gmail.com>

Hi Matthias,

Thanks for the query and the feedback.

I have done some investigation here and I was able to reproduce the issue
that you described above.

In fact this is an older step that we included in the digger-installer
README. So it can be ignored.

We will remove reference to creating pvs as the standard pv creation [1]
described in the 'oc cluster up' documentation provide sufficient pvs
necessary for digger. In this case you do not need to carry out these
additional steps to create pvs.

[1]
https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#persistent-volumes

On Tue, Sep 26, 2017 at 11:21 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> trying the digger install, and glusterFS,
>
> getting the following error, when running "oc create -f
> pv-sample-templates/jenkins/sample-pv-gluster.json":
>
>
> Error from server (BadRequest): error when creating
> "pv-sample-templates/jenkins/sample-pv-gluster.json": PersistentVolume in
> version "v1" cannot be handled as a PersistentVolume: [pos 224]: json:
> decode bool: got first char "
>
> as well, I am getting the same error for the Android SDK template:
>
>  pv-sample-templates/android-skd-linux/sample-pv-gluster.json
>
>
> any ideas ?
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LAURA FITZGERALD

Red Hat Mobile <https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

lfitzger at redhat.com    IM: lfitzgerald
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170926/77a8331f/attachment-0001.html 

From lfitzger at redhat.com  Tue Sep 26 10:36:47 2017
From: lfitzger at redhat.com (Laura Fitzgerald)
Date: Tue, 26 Sep 2017 15:36:47 +0100
Subject: [aerogear-dev] Digger-Installer problem
In-Reply-To: <CAAg5f2QxT=Ub5GKUN+X_Bh7NPSc6Nb1VGPdXUQ+RjYHckw3m7Q@mail.gmail.com>
References: <CAAg5f2QxT=Ub5GKUN+X_Bh7NPSc6Nb1VGPdXUQ+RjYHckw3m7Q@mail.gmail.com>
Message-ID: <CA+jLkhWGcLhw9eU+n9-jEpOQKZ6XeZE_SRQ4mr9hXmKreuULBQ@mail.gmail.com>

Hi Matthias,

Did you add your ssh key to Jenkins as prompted by the Ansible output? As
the output suggests `Playbook run will fail if skipped.`

On Tue, Sep 26, 2017 at 1:53 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I am using this inventory files:
> https://gist.githubusercontent.com/matzew/ca6b0481c53db4c6d7df7b521b8452
> 9b/raw/6d553ba81157e1fe2036e3e9d7ddf91ad7fffd58/matzew-inventory
>
> and this branch (I had to remove java, for some weird/undocumented
> reasons, to move on):
> https://github.com/matzew/digger-installer/tree/Problems_running_install
>
>
> With a bit of help from Leo on IRC I got to a point where I installed the
> Android SDK, but the ansible-playbook process exits after some time w/ the
> following message:
>
> https://gist.githubusercontent.com/matzew/a06cb779f430ccbde2fa3ba6a97c32
> d1/raw/65ff9e6b5d5fbfcebeb737cdc5c50ded0f3e75ec/error
>
>
> any ideas ?  Is this a known issue? Do you want me to create a JIRA ?
>
> Thx,
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LAURA FITZGERALD

Red Hat Mobile <https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

lfitzger at redhat.com    IM: lfitzgerald
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170926/f73955ba/attachment.html 

From matzew at apache.org  Tue Sep 26 11:57:54 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 26 Sep 2017 17:57:54 +0200
Subject: [aerogear-dev] Digger-Install and GlusterFS
In-Reply-To: <CA+jLkhVjuWiyVyKCmA1-nyFR8762b1TAuN2_w9TdY_HPaPQocQ@mail.gmail.com>
References: <CAAg5f2QcnUuietWsagTGKFcW3dr-c1Oyiitkh6WHK2XsmfSgBQ@mail.gmail.com>
	<CA+jLkhVjuWiyVyKCmA1-nyFR8762b1TAuN2_w9TdY_HPaPQocQ@mail.gmail.com>
Message-ID: <CAAg5f2S+gfMBG+XNdY6Ter_+=HDAKZxPuF__xmBE=K99mr5c0Q@mail.gmail.com>

not sure I follow - I generally think that using GlusterFS is a good idea
here (or NFS)

On Tue, Sep 26, 2017 at 4:35 PM, Laura Fitzgerald <lfitzger at redhat.com>
wrote:

> Hi Matthias,
>
> Thanks for the query and the feedback.
>
> I have done some investigation here and I was able to reproduce the issue
> that you described above.
>
> In fact this is an older step that we included in the digger-installer
> README. So it can be ignored.
>
> We will remove reference to creating pvs as the standard pv creation [1]
> described in the 'oc cluster up' documentation provide sufficient pvs
> necessary for digger. In this case you do not need to carry out these
> additional steps to create pvs.
>
> [1] https://github.com/openshift/origin/blob/master/
> docs/cluster_up_down.md#persistent-volumes
>
> On Tue, Sep 26, 2017 at 11:21 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> trying the digger install, and glusterFS,
>>
>> getting the following error, when running "oc create -f
>> pv-sample-templates/jenkins/sample-pv-gluster.json":
>>
>>
>> Error from server (BadRequest): error when creating
>> "pv-sample-templates/jenkins/sample-pv-gluster.json": PersistentVolume
>> in version "v1" cannot be handled as a PersistentVolume: [pos 224]: json:
>> decode bool: got first char "
>>
>> as well, I am getting the same error for the Android SDK template:
>>
>>  pv-sample-templates/android-skd-linux/sample-pv-gluster.json
>>
>>
>> any ideas ?
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> LAURA FITZGERALD
>
> Red Hat Mobile <https://www.redhat.com/>
>
> Communications House, Cork Road
>
> Waterford City, Ireland X91NY33
>
> lfitzger at redhat.com    IM: lfitzgerald
> <https://red.ht/sig>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170926/f8e7247c/attachment.html 

From matzew at apache.org  Wed Sep 27 03:45:18 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 27 Sep 2017 09:45:18 +0200
Subject: [aerogear-dev] Digger-Installer problem
In-Reply-To: <CAAg5f2QxT=Ub5GKUN+X_Bh7NPSc6Nb1VGPdXUQ+RjYHckw3m7Q@mail.gmail.com>
References: <CAAg5f2QxT=Ub5GKUN+X_Bh7NPSc6Nb1VGPdXUQ+RjYHckw3m7Q@mail.gmail.com>
Message-ID: <CAAg5f2T_3ZuajDQqCcRt_rti6FYMp3HU+mjPu_-gBJWvTe=pcg@mail.gmail.com>

I tried with a new ssh key (ssh-keygen) and used that (thanks Leo for the
suggestion), I now get a slightly different error:

TASK [configure-buildfarm : Configure Kubernetes plugin]
**********************************************************************************************************************************************************
fatal: [ansible_connection=local]: FAILED! => {"changed": true, "cmd":
"java -jar /tmp/jenkins-cli.jar -remoting -s
http://jenkins-digger.127.0.0.1.nip.io groovy
/tmp/kubernetes-plugin-config.groovy", "delta": "0:00:02.215772", "end":
"2017-09-27 09:42:31.347839", "failed": true, "failed_when_result": true,
"rc": 6, "start": "2017-09-27 09:42:29.132067", "stderr": "\nERROR:
anonymous is missing the Overall/Read permission", "stderr_lines": ["",
"ERROR: anonymous is missing the Overall/Read permission"], "stdout": "",
"stdout_lines": []}
fatal: [127.0.0.1]: FAILED! => {"changed": true, "cmd": "java -jar
/tmp/jenkins-cli.jar -remoting -s http://jenkins-digger.127.0.0.1.nip.io
groovy /tmp/kubernetes-plugin-config.groovy", "delta": "0:00:02.277280",
"end": "2017-09-27 09:42:31.429172", "failed": true, "failed_when_result":
true, "rc": 6, "start": "2017-09-27 09:42:29.151892", "stderr": "\nERROR:
anonymous is missing the Overall/Read permission", "stderr_lines": ["",
"ERROR: anonymous is missing the Overall/Read permission"], "stdout": "",
"stdout_lines": []}
to retry, use: --limit
@/home/Matthias/Work/Mobile.NEXT/digger-installer/sample-build-playbook.retry





Wondering: anyone ever tried this on Fedora 26 ? :-)







On Tue, Sep 26, 2017 at 2:53 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I am using this inventory files:
> https://gist.githubusercontent.com/matzew/ca6b0481c53db4c6d7df7b521b8452
> 9b/raw/6d553ba81157e1fe2036e3e9d7ddf91ad7fffd58/matzew-inventory
>
> and this branch (I had to remove java, for some weird/undocumented
> reasons, to move on):
> https://github.com/matzew/digger-installer/tree/Problems_running_install
>
>
> With a bit of help from Leo on IRC I got to a point where I installed the
> Android SDK, but the ansible-playbook process exits after some time w/ the
> following message:
>
> https://gist.githubusercontent.com/matzew/a06cb779f430ccbde2fa3ba6a97c32
> d1/raw/65ff9e6b5d5fbfcebeb737cdc5c50ded0f3e75ec/error
>
>
> any ideas ?  Is this a known issue? Do you want me to create a JIRA ?
>
> Thx,
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/f6255916/attachment-0001.html 

From aliok at redhat.com  Wed Sep 27 03:47:28 2017
From: aliok at redhat.com (Ali Ok)
Date: Wed, 27 Sep 2017 10:47:28 +0300
Subject: [aerogear-dev] Renaming digger-java to digger-java-client
Message-ID: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>

Hi,

I am currently working on setting up a proper release procedure for Digger
Java client [1].

While at it, I would like to rename the Git repo from "digger-java"
"digger-java-client".

Any objections?

[1]: https://github.com/aerogear/digger-java

Cheers,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/e0072ea1/attachment.html 

From matzew at apache.org  Wed Sep 27 03:57:16 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 27 Sep 2017 09:57:16 +0200
Subject: [aerogear-dev] Renaming digger-java to digger-java-client
In-Reply-To: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>
References: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>
Message-ID: <CAAg5f2RRfmCgFjvE3hRryriwMJQYMRQv=o4e68+vFsiQSRvcJw@mail.gmail.com>

+1

no issues here

On Wed, Sep 27, 2017 at 9:47 AM, Ali Ok <aliok at redhat.com> wrote:

> Hi,
>
> I am currently working on setting up a proper release procedure for Digger
> Java client [1].
>
> While at it, I would like to rename the Git repo from "digger-java"
> "digger-java-client".
>
> Any objections?
>
> [1]: https://github.com/aerogear/digger-java
>
> Cheers,
> Ali
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/fefe5014/attachment.html 

From matzew at apache.org  Wed Sep 27 05:21:50 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 27 Sep 2017 11:21:50 +0200
Subject: [aerogear-dev] [Digger-Installer] Android SDK download and license
	agreement
Message-ID: <CAAg5f2R334Sh0jFWfqJfnG=AHCKf8=z25fovkJ4BPZu_V3EtiQ@mail.gmail.com>

Hi,

In the digger-installer, we have a component that downloads the Android SDK
and asks afterwards to accept the license:

https://issues.jboss.org/secure/attachment/12425310/Android_text_license_agreement.png

The output is from the sdkmanager itself.

However, on the website, when manually downloading the SDK, you need to
accept the license first.

See:
https://developer.android.com/studio/index.html#linux-bundle

I guess this should be changed on the current execution path.

Any thoughts ?

-Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/02afebd1/attachment.html 

From lrossett at redhat.com  Wed Sep 27 05:28:25 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Wed, 27 Sep 2017 06:28:25 -0300
Subject: [aerogear-dev] [Digger-Installer] Android SDK download and
 license agreement
In-Reply-To: <CAAg5f2R334Sh0jFWfqJfnG=AHCKf8=z25fovkJ4BPZu_V3EtiQ@mail.gmail.com>
References: <CAAg5f2R334Sh0jFWfqJfnG=AHCKf8=z25fovkJ4BPZu_V3EtiQ@mail.gmail.com>
Message-ID: <CAF-nxa9HG9HY4gvsShwEvW4poi3pmMKfFghsjH+CR7dJvWbdEQ@mail.gmail.com>

We can add a task to be executed before this one:
https://github.com/aerogear/digger-installer/blob/master/android-sdk/tasks/main.yml#L159

That task could show a message like this: "By pressing enter you agree with
google android sdk license:
https://developer.android.com/studio/index.html#linux-bundle" as we do with
osx jdk update:
https://github.com/aerogear/digger-installer/blob/master/java/tasks/osx.yml#L28

On Wed, Sep 27, 2017 at 6:21 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> In the digger-installer, we have a component that downloads the Android
> SDK and asks afterwards to accept the license:
>
> https://issues.jboss.org/secure/attachment/12425310/Android_text_license_
> agreement.png
>
> The output is from the sdkmanager itself.
>
> However, on the website, when manually downloading the SDK, you need to
> accept the license first.
>
> See:
> https://developer.android.com/studio/index.html#linux-bundle
>
> I guess this should be changed on the current execution path.
>
> Any thoughts ?
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEONARDO ROSSETTI

SOFTWARE ENGINEER

Red Hat SP <https://www.redhat.com/>

lrossett at redhat.com    M: 11997030621
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/9b36ce55/attachment.html 

From lgriffin at redhat.com  Wed Sep 27 06:05:03 2017
From: lgriffin at redhat.com (Leigh Griffin)
Date: Wed, 27 Sep 2017 11:05:03 +0100
Subject: [aerogear-dev] [Digger-Installer] Android SDK download and
 license agreement
In-Reply-To: <CAF-nxa9HG9HY4gvsShwEvW4poi3pmMKfFghsjH+CR7dJvWbdEQ@mail.gmail.com>
References: <CAAg5f2R334Sh0jFWfqJfnG=AHCKf8=z25fovkJ4BPZu_V3EtiQ@mail.gmail.com>
	<CAF-nxa9HG9HY4gvsShwEvW4poi3pmMKfFghsjH+CR7dJvWbdEQ@mail.gmail.com>
Message-ID: <CAOQ+WrqO7JW97YScC-29r4d1WMD_=5Y3Z-0hMyrgLPSFirOJmg@mail.gmail.com>

Making the text clickable with a url reference would be a nice touch. We
should be careful about licensing implications and try present as much to
the end user so that they acknowledge the fact an external license
agreement is being accepted when you hit return.

Leigh

On 27 Sep 2017 10:29 AM, "Leonardo Rossetti" <lrossett at redhat.com> wrote:

> We can add a task to be executed before this one:
> https://github.com/aerogear/digger-installer/blob/master/
> android-sdk/tasks/main.yml#L159
>
> That task could show a message like this: "By pressing enter you agree
> with google android sdk license: https://developer.
> android.com/studio/index.html#linux-bundle" as we do with osx jdk update:
> https://github.com/aerogear/digger-installer/blob/master/java/tasks/osx.
> yml#L28
>
> On Wed, Sep 27, 2017 at 6:21 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> In the digger-installer, we have a component that downloads the Android
>> SDK and asks afterwards to accept the license:
>>
>> https://issues.jboss.org/secure/attachment/12425310/Android_
>> text_license_agreement.png
>>
>> The output is from the sdkmanager itself.
>>
>> However, on the website, when manually downloading the SDK, you need to
>> accept the license first.
>>
>> See:
>> https://developer.android.com/studio/index.html#linux-bundle
>>
>> I guess this should be changed on the current execution path.
>>
>> Any thoughts ?
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> LEONARDO ROSSETTI
>
> SOFTWARE ENGINEER
>
> Red Hat SP <https://www.redhat.com/>
>
> lrossett at redhat.com    M: 11997030621
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170927/9e77cfe2/attachment-0001.html 

From matzew at apache.org  Thu Sep 28 03:29:36 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 28 Sep 2017 09:29:36 +0200
Subject: [aerogear-dev] Hacktoberfest is back !
Message-ID: <CAAg5f2RB=Qt2BjozXe=77wuFdF2LjEpBtvLpfy5oyJqhGKPRzQ@mail.gmail.com>

Hello AeroGear community,

the Hacktoberfest is back! it's your chance to get a nice t-shirt :-)

I'd be happy to see contributions to our AeroGear repos during this October.

Find details about it:
https://blog.digitalocean.com/hacktoberfest-2017/

PS: Last years t-shirt was super cool!

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/d26bedcc/attachment.html 

From aliok at redhat.com  Thu Sep 28 03:59:00 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 28 Sep 2017 10:59:00 +0300
Subject: [aerogear-dev] Renaming digger-java to digger-java-client
In-Reply-To: <CAAg5f2RRfmCgFjvE3hRryriwMJQYMRQv=o4e68+vFsiQSRvcJw@mail.gmail.com>
References: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>
	<CAAg5f2RRfmCgFjvE3hRryriwMJQYMRQv=o4e68+vFsiQSRvcJw@mail.gmail.com>
Message-ID: <CABoO8LdRNrpKS34MT+xzSdU9Tf77gp4UGncVJL8njbqjEZ1Yfg@mail.gmail.com>

Hello,

In order to make things compatible with https://oss.sonatype.org Nexus, we
need to change the group id from "org.jboss.aerogear" to "org.aerogear" for
various components.

I will only touch AeroGear Digger related things, not everything.

Just a heads up!

Cheers,
Ali

On Wed, Sep 27, 2017 at 10:57 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> +1
>
> no issues here
>
> On Wed, Sep 27, 2017 at 9:47 AM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hi,
>>
>> I am currently working on setting up a proper release procedure for
>> Digger Java client [1].
>>
>> While at it, I would like to rename the Git repo from "digger-java"
>> "digger-java-client".
>>
>> Any objections?
>>
>> [1]: https://github.com/aerogear/digger-java
>>
>> Cheers,
>> Ali
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/a2385483/attachment.html 

From mm at napp.dk  Thu Sep 28 04:04:10 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Thu, 28 Sep 2017 08:04:10 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
Message-ID: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>

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
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/97f6bd7d/attachment.html 

From matzew at apache.org  Thu Sep 28 04:12:42 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 28 Sep 2017 10:12:42 +0200
Subject: [aerogear-dev] Renaming digger-java to digger-java-client
In-Reply-To: <CABoO8LdRNrpKS34MT+xzSdU9Tf77gp4UGncVJL8njbqjEZ1Yfg@mail.gmail.com>
References: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>
	<CAAg5f2RRfmCgFjvE3hRryriwMJQYMRQv=o4e68+vFsiQSRvcJw@mail.gmail.com>
	<CABoO8LdRNrpKS34MT+xzSdU9Tf77gp4UGncVJL8njbqjEZ1Yfg@mail.gmail.com>
Message-ID: <CAAg5f2RwMXV5gcMfYknfKtx5rZafsjaLVzzkbdyyuVdbNT3NKQ@mail.gmail.com>

nope, not correct

both JBoss Nexus and Sonatype do have "org.jboss.aerogear"

However, for recently created projects (e.g. the kafka-cdi xtension) we did
pick "org.aerogear".

If you wanna deploy to OSSRH, than you need to do some overrides (e.g.
distributionManagement) and also not 100% sure the parent works.

That said, there is no need to do any change on the groupIds

On Thu, Sep 28, 2017 at 9:59 AM, Ali Ok <aliok at redhat.com> wrote:

> Hello,
>
> In order to make things compatible with https://oss.sonatype.org Nexus,
> we need to change the group id from "org.jboss.aerogear" to "org.aerogear"
> for various components.
>
> I will only touch AeroGear Digger related things, not everything.
>
> Just a heads up!
>
> Cheers,
> Ali
>
> On Wed, Sep 27, 2017 at 10:57 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> +1
>>
>> no issues here
>>
>> On Wed, Sep 27, 2017 at 9:47 AM, Ali Ok <aliok at redhat.com> wrote:
>>
>>> Hi,
>>>
>>> I am currently working on setting up a proper release procedure for
>>> Digger Java client [1].
>>>
>>> While at it, I would like to rename the Git repo from "digger-java"
>>> "digger-java-client".
>>>
>>> Any objections?
>>>
>>> [1]: https://github.com/aerogear/digger-java
>>>
>>> Cheers,
>>> Ali
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/129ca5ce/attachment-0001.html 

From matzew at apache.org  Thu Sep 28 04:13:31 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 28 Sep 2017 10:13:31 +0200
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
Message-ID: <CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>

I've no idea, honestly - I've never used AWS

On Thu, Sep 28, 2017 at 10:04 AM, Mads M?ller <mm at 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
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/2dd5daaf/attachment.html 

From aliok at redhat.com  Thu Sep 28 04:18:13 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 28 Sep 2017 11:18:13 +0300
Subject: [aerogear-dev] Renaming digger-java to digger-java-client
In-Reply-To: <CAAg5f2RwMXV5gcMfYknfKtx5rZafsjaLVzzkbdyyuVdbNT3NKQ@mail.gmail.com>
References: <CABoO8Ld0mYYnvX1Dwj=U31gpCVofUkwwW0MyC0tNNJyoiicfBg@mail.gmail.com>
	<CAAg5f2RRfmCgFjvE3hRryriwMJQYMRQv=o4e68+vFsiQSRvcJw@mail.gmail.com>
	<CABoO8LdRNrpKS34MT+xzSdU9Tf77gp4UGncVJL8njbqjEZ1Yfg@mail.gmail.com>
	<CAAg5f2RwMXV5gcMfYknfKtx5rZafsjaLVzzkbdyyuVdbNT3NKQ@mail.gmail.com>
Message-ID: <CABoO8LfPcRL1J9ufi6XT6ADZyDv-CeMzoac5_76Sj+QF1pjsfw@mail.gmail.com>

ok, thanks for clarification. I thought it is the otherwise.

On Thu, Sep 28, 2017 at 11:12 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> nope, not correct
>
> both JBoss Nexus and Sonatype do have "org.jboss.aerogear"
>
> However, for recently created projects (e.g. the kafka-cdi xtension) we
> did pick "org.aerogear".
>
> If you wanna deploy to OSSRH, than you need to do some overrides (e.g.
> distributionManagement) and also not 100% sure the parent works.
>
> That said, there is no need to do any change on the groupIds
>
> On Thu, Sep 28, 2017 at 9:59 AM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hello,
>>
>> In order to make things compatible with https://oss.sonatype.org Nexus,
>> we need to change the group id from "org.jboss.aerogear" to "org.aerogear"
>> for various components.
>>
>> I will only touch AeroGear Digger related things, not everything.
>>
>> Just a heads up!
>>
>> Cheers,
>> Ali
>>
>> On Wed, Sep 27, 2017 at 10:57 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> +1
>>>
>>> no issues here
>>>
>>> On Wed, Sep 27, 2017 at 9:47 AM, Ali Ok <aliok at redhat.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am currently working on setting up a proper release procedure for
>>>> Digger Java client [1].
>>>>
>>>> While at it, I would like to rename the Git repo from "digger-java"
>>>> "digger-java-client".
>>>>
>>>> Any objections?
>>>>
>>>> [1]: https://github.com/aerogear/digger-java
>>>>
>>>> Cheers,
>>>> Ali
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/0b1f712a/attachment.html 

From mm at napp.dk  Thu Sep 28 04:24:40 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Thu, 28 Sep 2017 08:24:40 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
Message-ID: <DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>

Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias Wessendorf <matzew at apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/3567945b/attachment-0001.html 

From jusanche at redhat.com  Thu Sep 28 04:30:36 2017
From: jusanche at redhat.com (Julio Cesar Sanchez Hernandez)
Date: Thu, 28 Sep 2017 10:30:36 +0200
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
Message-ID: <CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>

You can try
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk> wrote:

> Any guide on how to get it working on openshift 3?
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.13
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/91c5fe04/attachment.html 

From mm at napp.dk  Thu Sep 28 04:38:23 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Thu, 28 Sep 2017 08:38:23 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
Message-ID: <DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/75f65c6c/attachment-0001.html 

From mm at napp.dk  Thu Sep 28 05:38:14 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Thu, 28 Sep 2017 09:38:14 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
Message-ID: <B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>

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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/4bb6bc90/attachment-0001.html 

From mm at napp.dk  Thu Sep 28 07:14:04 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Thu, 28 Sep 2017 11:14:04 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
Message-ID: <64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>

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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/f52cca54/attachment-0001.html 

From mm at napp.dk  Thu Sep 28 17:30:31 2017
From: mm at napp.dk (=?Windows-1252?Q?Mads_M=F8ller?=)
Date: Thu, 28 Sep 2017 21:30:31 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>,
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
Message-ID: <BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>

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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170928/b89fd13d/attachment-0001.html 

From matzew at apache.org  Fri Sep 29 01:48:18 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 29 Sep 2017 05:48:18 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
Message-ID: <CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>

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 at 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
> T: 42 42 80 60
> M: 20 28 20 26
> E: mm at napp.dk
> W: www.napp.dk
> __________________
>
> On 28 Sep 2017, at 13.21, Mads M?ller <mm at 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.
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 11.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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?
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> Hi,
>
>
>
> I did that and got: http://prntscr.com/gqnxw9
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar
> Sanchez Hernandez <jusanche at redhat.com>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.30
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> You can try
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift
>
>
>
> On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk> wrote:
>
> Any guide on how to get it working on openshift 3?
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.13
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/1d1e41a3/attachment-0001.html 

From mm at napp.dk  Fri Sep 29 02:00:35 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Fri, 29 Sep 2017 06:00:35 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
Message-ID: <CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>

Hi,

I would love to update to 1.2. But the migrator fails. So I cannot upgrade until that is fixed also.
Anyone else I can talk to on your team?

Again, ill gladly pay for some consultancy hours. Its the last day before our production server is shut down by openshift. :(



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias Wessendorf <matzew at apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 07.48
To: AeroGear Developer Mailing List <aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/58b1d2cc/attachment-0001.html 

From matzew at apache.org  Fri Sep 29 02:58:50 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 29 Sep 2017 06:58:50 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
Message-ID: <CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>

On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at 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. :(
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
>
>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
>
> *Date: *Friday, 29 September 2017 at 07.48
>
>
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: 42 42 80 60
>
> M: 20 28 20 26
>
> E: mm at napp.dk
>
> W: www.napp.dk
>
> __________________
>
>
> On 28 Sep 2017, at 13.21, Mads M?ller <mm at 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.
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 11.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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?
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> Hi,
>
>
>
> I did that and got: http://prntscr.com/gqnxw9
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60
>
> M: +45 20 28 20 26
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar
> Sanchez Hernandez <jusanche at redhat.com>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.30
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> You can try
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift
>
>
>
> On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk> wrote:
>
> Any guide on how to get it working on openshift 3?
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.13
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> Sent from Gmail Mobile
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/3dcf1353/attachment-0001.html 

From mm at napp.dk  Fri Sep 29 03:53:06 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Fri, 29 Sep 2017 07:53:06 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
Message-ID: <314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>

Great idea. How do I export to json?
I dont know any export function in unified push.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias Wessendorf <matzew at apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 08.58
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS


On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at napp.dk<mailto:mm at 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. :(



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>

Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 07.48

To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/1b3f7900/attachment-0001.html 

From mm at napp.dk  Fri Sep 29 04:04:58 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Fri, 29 Sep 2017 08:04:58 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
	<314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
Message-ID: <FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>

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 ?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 09.53
To: AeroGear Developer Mailing List <aerogear-dev at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias Wessendorf <matzew at apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 08.58
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS


On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at napp.dk<mailto:mm at 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. :(



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>

Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 07.48

To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/aa9b9159/attachment-0001.html 

From mm at napp.dk  Fri Sep 29 05:25:41 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Fri, 29 Sep 2017 09:25:41 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
	<314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
	<FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>
Message-ID: <8D9839CA-58FF-4887-B622-DC0F33376C31@napp.dk>

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?





BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 10.04
To: AeroGear Developer Mailing List <aerogear-dev at 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 ?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <mm at napp.dk>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 09.53
To: AeroGear Developer Mailing List <aerogear-dev at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias Wessendorf <matzew at apache.org>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 08.58
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS


On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at napp.dk<mailto:mm at 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. :(



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>

Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 07.48

To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60
M: +45 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/d9f96a87/attachment-0001.html 

From lrossett at redhat.com  Fri Sep 29 06:09:07 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Fri, 29 Sep 2017 07:09:07 -0300
Subject: [aerogear-dev] [ag-digger] fastlane as the default build tool for
	digger-jenkins
Message-ID: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>

Hello,

I have created a PR against digger-jenkins with fastlane samples for both
ios and android: https://github.com/aerogear/digger-jenkins/pull/77

You will notice that fastlane can replace both build and codesign logic
from our Jenkinsfiles and this approach has some advantages:

   - easier to test it locally without jenkins (just run fastlane commands).
   - more flexibility since it is just a  couple of ruby scripts.
   - fastlane actions can be distributed as ruby gem packages in the future.
   - fastlane has several community plugins, which is easier to install
   within the jenkinsfile using the gem command if needed.

Currently, we can't sign our binaries with fastlane because of how our
plugins (android signing and xcode) handle jenkins certificates and
developer profile files.

I was thinking if we could create a jenkins plugin to properly handle
credentials using the "withCredentials" pipeline function
<https://jenkins.io/doc/pipeline/steps/credentials-binding/> so we could
keep the main build/sign logic in fastlane actions while we keep specific
jenkins tasks such as handling credentials, archiving the artifact, etc in
the jenkisfile.

WDYT?
-- 

LEONARDO ROSSETTI

SOFTWARE ENGINEER

Red Hat SP <https://www.redhat.com/>

lrossett at redhat.com    M: 11997030621
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/0af6d681/attachment.html 

From wtrocki at redhat.com  Fri Sep 29 06:46:51 2017
From: wtrocki at redhat.com (Wojciech Trocki)
Date: Fri, 29 Sep 2017 11:46:51 +0100
Subject: [aerogear-dev] [ag-digger] fastlane as the default build tool
	for digger-jenkins
In-Reply-To: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>
References: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>
Message-ID: <CAO0+n+oy7mT-qUpUi_70jBjYp1Equ7E9LMtCbf7bc6Hgcax_jw@mail.gmail.com>

I'm huge enthusiast of fastline. Most of the IOS developers will use it on
daily basis. I'm no longer involved in the project but I think it will make
sense to use it as default codesign tool.
There are many ways to introduce it. If you need help with building jenkins
plugin I can help with contribution.

> I was thinking if we could create a jenkins plugin to properly handle
credentials using the "withCredentials" pipeline function
<https://jenkins.io/doc/pipeline/steps/credentials-binding/>
That's great idea! We may also share this on the fastlate github. They have
bigger community and it seems that this will be useful outside digger.

Work checking:
https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Jenkins.md


On Fri, Sep 29, 2017 at 11:09 AM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> Hello,
>
> I have created a PR against digger-jenkins with fastlane samples for both
> ios and android: https://github.com/aerogear/digger-jenkins/pull/77
>
> You will notice that fastlane can replace both build and codesign logic
> from our Jenkinsfiles and this approach has some advantages:
>
>    - easier to test it locally without jenkins (just run fastlane
>    commands).
>    - more flexibility since it is just a  couple of ruby scripts.
>    - fastlane actions can be distributed as ruby gem packages in the
>    future.
>    - fastlane has several community plugins, which is easier to install
>    within the jenkinsfile using the gem command if needed.
>
> Currently, we can't sign our binaries with fastlane because of how our
> plugins (android signing and xcode) handle jenkins certificates and
> developer profile files.
>
> I was thinking if we could create a jenkins plugin to properly handle
> credentials using the "withCredentials" pipeline function
> <https://jenkins.io/doc/pipeline/steps/credentials-binding/> so we could
> keep the main build/sign logic in fastlane actions while we keep specific
> jenkins tasks such as handling credentials, archiving the artifact, etc in
> the jenkisfile.
>
> WDYT?
> --
>
> LEONARDO ROSSETTI
>
> SOFTWARE ENGINEER
>
> Red Hat SP <https://www.redhat.com/>
>
> lrossett at redhat.com    M: 11997030621
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

WOJCIECH TROCKI

Red Hat Mobile <https://www.redhat.com/>

IM: wtrocki
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/608f5689/attachment.html 

From lgriffin at redhat.com  Fri Sep 29 07:50:05 2017
From: lgriffin at redhat.com (Leigh Griffin)
Date: Fri, 29 Sep 2017 12:50:05 +0100
Subject: [aerogear-dev] [ag-digger] fastlane as the default build tool
	for digger-jenkins
In-Reply-To: <CAO0+n+oy7mT-qUpUi_70jBjYp1Equ7E9LMtCbf7bc6Hgcax_jw@mail.gmail.com>
References: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>
	<CAO0+n+oy7mT-qUpUi_70jBjYp1Equ7E9LMtCbf7bc6Hgcax_jw@mail.gmail.com>
Message-ID: <CAOQ+WrqM-6Ogo5v1Xs4ZC0McxnmwgH3EyTg2e-ryjL=MYEM91Q@mail.gmail.com>

Big +1 for cross community contributions. Would be great to gain traction
with fastlane and cross collaborate.

This work is open to all Wojciech so any of our individual team members can
get involved under the OSS banner. In fact it's something I would highly
encourage.

Leigh

On 29 Sep 2017 11:50, "Wojciech Trocki" <wtrocki at redhat.com> wrote:

> I'm huge enthusiast of fastline. Most of the IOS developers will use it on
> daily basis. I'm no longer involved in the project but I think it will make
> sense to use it as default codesign tool.
> There are many ways to introduce it. If you need help with building
> jenkins plugin I can help with contribution.
>
> > I was thinking if we could create a jenkins plugin to properly handle
> credentials using the "withCredentials" pipeline function
> <https://jenkins.io/doc/pipeline/steps/credentials-binding/>
> That's great idea! We may also share this on the fastlate github. They
> have bigger community and it seems that this will be useful outside digger.
>
> Work checking: https://github.com/fastlane/fastlane/blob/master/
> fastlane/docs/Jenkins.md
>
>
> On Fri, Sep 29, 2017 at 11:09 AM, Leonardo Rossetti <lrossett at redhat.com>
> wrote:
>
>> Hello,
>>
>> I have created a PR against digger-jenkins with fastlane samples for both
>> ios and android: https://github.com/aerogear/digger-jenkins/pull/77
>>
>> You will notice that fastlane can replace both build and codesign logic
>> from our Jenkinsfiles and this approach has some advantages:
>>
>>    - easier to test it locally without jenkins (just run fastlane
>>    commands).
>>    - more flexibility since it is just a  couple of ruby scripts.
>>    - fastlane actions can be distributed as ruby gem packages in the
>>    future.
>>    - fastlane has several community plugins, which is easier to install
>>    within the jenkinsfile using the gem command if needed.
>>
>> Currently, we can't sign our binaries with fastlane because of how our
>> plugins (android signing and xcode) handle jenkins certificates and
>> developer profile files.
>>
>> I was thinking if we could create a jenkins plugin to properly handle
>> credentials using the "withCredentials" pipeline function
>> <https://jenkins.io/doc/pipeline/steps/credentials-binding/> so we could
>> keep the main build/sign logic in fastlane actions while we keep specific
>> jenkins tasks such as handling credentials, archiving the artifact, etc in
>> the jenkisfile.
>>
>> WDYT?
>> --
>>
>> LEONARDO ROSSETTI
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat SP <https://www.redhat.com/>
>>
>> lrossett at redhat.com    M: 11997030621
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> WOJCIECH TROCKI
>
> Red Hat Mobile <https://www.redhat.com/>
>
> IM: wtrocki
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/3f42f393/attachment-0001.html 

From aliok at redhat.com  Fri Sep 29 08:20:39 2017
From: aliok at redhat.com (Ali Ok)
Date: Fri, 29 Sep 2017 15:20:39 +0300
Subject: [aerogear-dev] [ag-digger] fastlane as the default build tool
	for digger-jenkins
In-Reply-To: <CAOQ+WrqM-6Ogo5v1Xs4ZC0McxnmwgH3EyTg2e-ryjL=MYEM91Q@mail.gmail.com>
References: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>
	<CAO0+n+oy7mT-qUpUi_70jBjYp1Equ7E9LMtCbf7bc6Hgcax_jw@mail.gmail.com>
	<CAOQ+WrqM-6Ogo5v1Xs4ZC0McxnmwgH3EyTg2e-ryjL=MYEM91Q@mail.gmail.com>
Message-ID: <CABoO8Lfr92ONKAt9WCeh5x3tp+KXg=WrSwGBDrv393ip6CGK8Q@mail.gmail.com>

Hello,

Leonardo, it sounds really good! Using some other open source software for
very complex things would be great.

I have a question though: in my experiments (like ~10 months ago), I was
disappointed with FastLane connecting to Apple Developer console to get
some provision files. I was stuck there...
Is this really the case? Would it block anything?

Cheers,
Ali


On Fri, Sep 29, 2017 at 2:50 PM, Leigh Griffin <lgriffin at redhat.com> wrote:

> Big +1 for cross community contributions. Would be great to gain traction
> with fastlane and cross collaborate.
>
> This work is open to all Wojciech so any of our individual team members
> can get involved under the OSS banner. In fact it's something I would
> highly encourage.
>
> Leigh
>
> On 29 Sep 2017 11:50, "Wojciech Trocki" <wtrocki at redhat.com> wrote:
>
>> I'm huge enthusiast of fastline. Most of the IOS developers will use it
>> on daily basis. I'm no longer involved in the project but I think it will
>> make sense to use it as default codesign tool.
>> There are many ways to introduce it. If you need help with building
>> jenkins plugin I can help with contribution.
>>
>> > I was thinking if we could create a jenkins plugin to properly handle
>> credentials using the "withCredentials" pipeline function
>> <https://jenkins.io/doc/pipeline/steps/credentials-binding/>
>> That's great idea! We may also share this on the fastlate github. They
>> have bigger community and it seems that this will be useful outside digger.
>>
>> Work checking: https://github.com/fastlane/fastlane/blob/master/f
>> astlane/docs/Jenkins.md
>>
>>
>> On Fri, Sep 29, 2017 at 11:09 AM, Leonardo Rossetti <lrossett at redhat.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I have created a PR against digger-jenkins with fastlane samples for
>>> both ios and android: https://github.com/aerogear/digger-jenkins/pull/77
>>>
>>> You will notice that fastlane can replace both build and codesign logic
>>> from our Jenkinsfiles and this approach has some advantages:
>>>
>>>    - easier to test it locally without jenkins (just run fastlane
>>>    commands).
>>>    - more flexibility since it is just a  couple of ruby scripts.
>>>    - fastlane actions can be distributed as ruby gem packages in the
>>>    future.
>>>    - fastlane has several community plugins, which is easier to install
>>>    within the jenkinsfile using the gem command if needed.
>>>
>>> Currently, we can't sign our binaries with fastlane because of how our
>>> plugins (android signing and xcode) handle jenkins certificates and
>>> developer profile files.
>>>
>>> I was thinking if we could create a jenkins plugin to properly handle
>>> credentials using the "withCredentials" pipeline function
>>> <https://jenkins.io/doc/pipeline/steps/credentials-binding/> so we
>>> could keep the main build/sign logic in fastlane actions while we keep
>>> specific jenkins tasks such as handling credentials, archiving the
>>> artifact, etc in the jenkisfile.
>>>
>>> WDYT?
>>> --
>>>
>>> LEONARDO ROSSETTI
>>>
>>> SOFTWARE ENGINEER
>>>
>>> Red Hat SP <https://www.redhat.com/>
>>>
>>> lrossett at redhat.com    M: 11997030621
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>>
>> WOJCIECH TROCKI
>>
>> Red Hat Mobile <https://www.redhat.com/>
>>
>> IM: wtrocki
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/404c311b/attachment.html 

From jusanche at redhat.com  Fri Sep 29 10:36:58 2017
From: jusanche at redhat.com (Julio Cesar Sanchez Hernandez)
Date: Fri, 29 Sep 2017 16:36:58 +0200
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <8D9839CA-58FF-4887-B622-DC0F33376C31@napp.dk>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
	<314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
	<FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>
	<8D9839CA-58FF-4887-B622-DC0F33376C31@napp.dk>
Message-ID: <CA+-uZpvtLEtizY0bgnxZFH75p2QZ5PAthuagPQJj3cKQ8uEBPA@mail.gmail.com>

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 at 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?
>
>
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Friday, 29 September 2017 at 10.04
>
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 ?
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Friday, 29 September 2017 at 09.53
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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.
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Friday, 29 September 2017 at 08.58
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
>
>
> On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at 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. :(
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
>
>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
>
> *Date: *Friday, 29 September 2017 at 07.48
>
>
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: 42 42 80 60
>
> M: 20 28 20 26
>
> E: mm at napp.dk
>
> W: www.napp.dk
>
> __________________
>
>
> On 28 Sep 2017, at 13.21, Mads M?ller <mm at 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.
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 11.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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?
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk" <
> mm at napp.dk>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.38
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> Hi,
>
>
>
> I did that and got: http://prntscr.com/gqnxw9
>
>
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar
> Sanchez Hernandez <jusanche at redhat.com>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.30
> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>
>
>
> You can try https://github.com/aerogear/aerogear-unifiedpush-server/
> tree/master/openshift
>
>
>
> On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk> wrote:
>
> Any guide on how to get it working on openshift 3?
>
>
>
>
>
>
>
> BEST REGARDS
>
> *__________________*
>
> *MADS M?LLER*
>
> CTO, PARTNER
>
>
>
> Napp A/S
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
>
> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
> Wessendorf <matzew at apache.org>
> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> *Date: *Thursday, 28 September 2017 at 10.13
> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>
> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>
> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>
> E: mm at napp.dk
>
> W: https://napp.dk
>
> *__________________*
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> --
>
> Sent from Gmail Mobile
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/fe7e48e0/attachment-0001.html 

From tolisemm at gmail.com  Fri Sep 29 12:52:16 2017
From: tolisemm at gmail.com (Tolis Emmanouilidis)
Date: Fri, 29 Sep 2017 16:52:16 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CA+-uZpvtLEtizY0bgnxZFH75p2QZ5PAthuagPQJj3cKQ8uEBPA@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
	<314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
	<FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>
	<8D9839CA-58FF-4887-B622-DC0F33376C31@napp.dk>
	<CA+-uZpvtLEtizY0bgnxZFH75p2QZ5PAthuagPQJj3cKQ8uEBPA@mail.gmail.com>
Message-ID: <CAN5SbcYAGKibWUJguu_XzYsSEKW406v1t0jLCi9j1afrUS-qMw@mail.gmail.com>

The exception you see "ApnsDeliveryErrorException: Failed to deliver
notification with error code 8"
means that the device token you sent to APN is invalid. It could be that it
is not related to Aerogear UPS installation on EC2.

Afterwards, the invalid token is removed: "Removing invalid (not allowed)
token:c651f284dc52511ed79e8a3e7a318bb6be39c7bc13129508ef4d0dfcd4608d00".

Maybe the application is uninstalled from the specific device or the user
has deactivated push notifications. Otherwise you may ensure you're using
the correct certificates and you're sending production device tokens to the
production APN.


On Fri, 29 Sep 2017 at 18:04, Julio Cesar Sanchez Hernandez <
jusanche at redhat.com> wrote:

> 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 at 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?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk"
>> <mm at napp.dk>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Friday, 29 September 2017 at 10.04
>>
>> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 ?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk"
>> <mm at napp.dk>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Friday, 29 September 2017 at 09.53
>> *To: *AeroGear Developer Mailing List <aerogear-dev at 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.
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
>> Wessendorf <matzew at apache.org>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Friday, 29 September 2017 at 08.58
>> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
>> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>>
>>
>>
>>
>>
>> On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at 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. :(
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
>> Wessendorf <matzew at apache.org>
>>
>>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>>
>> *Date: *Friday, 29 September 2017 at 07.48
>>
>>
>> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>>
>> T: 42 42 80 60
>>
>> M: 20 28 20 26
>>
>> E: mm at napp.dk
>>
>> W: www.napp.dk
>>
>> __________________
>>
>>
>> On 28 Sep 2017, at 13.21, Mads M?ller <mm at 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.
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk"
>> <mm at napp.dk>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Thursday, 28 September 2017 at 11.38
>> *To: *AeroGear Developer Mailing List <aerogear-dev at 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?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of "mm at napp.dk"
>> <mm at napp.dk>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Thursday, 28 September 2017 at 10.38
>> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
>> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>>
>>
>>
>> Hi,
>>
>>
>>
>> I did that and got: http://prntscr.com/gqnxw9
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar
>> Sanchez Hernandez <jusanche at redhat.com>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Thursday, 28 September 2017 at 10.30
>> *To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
>> *Subject: *Re: [aerogear-dev] Migrate Unified Push to AWS
>>
>>
>>
>> You can try
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift
>>
>>
>>
>> On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk> wrote:
>>
>> Any guide on how to get it working on openshift 3?
>>
>>
>>
>>
>>
>>
>>
>> BEST REGARDS
>>
>> *__________________*
>>
>> *MADS M?LLER*
>>
>> CTO, PARTNER
>>
>>
>>
>> Napp A/S
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *<aerogear-dev-bounces at lists.jboss.org> on behalf of Matthias
>> Wessendorf <matzew at apache.org>
>> *Reply-To: *AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org
>> >
>> *Date: *Thursday, 28 September 2017 at 10.13
>> *To: *AeroGear Developer Mailing List <aerogear-dev at 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 at 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
>>
>> T: +45 42 42 80 60 <+45%2042%2042%2080%2060>
>>
>> M: +45 20 28 20 26 <+45%2020%2028%2020%2026>
>>
>> E: mm at napp.dk
>>
>> W: https://napp.dk
>>
>> *__________________*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> --
>>
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> --
>>
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/17abb197/attachment-0001.html 

From lrossett at redhat.com  Fri Sep 29 14:23:40 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Fri, 29 Sep 2017 15:23:40 -0300
Subject: [aerogear-dev] [ag-digger] fastlane as the default build tool
	for digger-jenkins
In-Reply-To: <CABoO8Lfr92ONKAt9WCeh5x3tp+KXg=WrSwGBDrv393ip6CGK8Q@mail.gmail.com>
References: <CAF-nxa-SawFERWxD9XCa5V=G7YPkemhCucFrDvCrf+vSqU7SOQ@mail.gmail.com>
	<CAO0+n+oy7mT-qUpUi_70jBjYp1Equ7E9LMtCbf7bc6Hgcax_jw@mail.gmail.com>
	<CAOQ+WrqM-6Ogo5v1Xs4ZC0McxnmwgH3EyTg2e-ryjL=MYEM91Q@mail.gmail.com>
	<CABoO8Lfr92ONKAt9WCeh5x3tp+KXg=WrSwGBDrv393ip6CGK8Q@mail.gmail.com>
Message-ID: <CAF-nxa_ty2AEwOgr+_mgwzcfLaMQwX+sOTFdQbQUv228F=j2HQ@mail.gmail.com>

Those fastlane actions do not connect to apple services, they expect those
developer files to be in the filesystem.

By credentials I mean a plugin that would enable us to "unwrap" it from a
pipeline function to be used by "sh" commands (fastlane being one example)
which is not possible today, it needs to be done from their java code only
which is a bit limited from a pipeline perspective.

On Fri, Sep 29, 2017 at 9:20 AM, Ali Ok <aliok at redhat.com> wrote:

> Hello,
>
> Leonardo, it sounds really good! Using some other open source software for
> very complex things would be great.
>
> I have a question though: in my experiments (like ~10 months ago), I was
> disappointed with FastLane connecting to Apple Developer console to get
> some provision files. I was stuck there...
> Is this really the case? Would it block anything?
>
> Cheers,
> Ali
>
>
> On Fri, Sep 29, 2017 at 2:50 PM, Leigh Griffin <lgriffin at redhat.com>
> wrote:
>
>> Big +1 for cross community contributions. Would be great to gain traction
>> with fastlane and cross collaborate.
>>
>> This work is open to all Wojciech so any of our individual team members
>> can get involved under the OSS banner. In fact it's something I would
>> highly encourage.
>>
>> Leigh
>>
>> On 29 Sep 2017 11:50, "Wojciech Trocki" <wtrocki at redhat.com> wrote:
>>
>>> I'm huge enthusiast of fastline. Most of the IOS developers will use it
>>> on daily basis. I'm no longer involved in the project but I think it will
>>> make sense to use it as default codesign tool.
>>> There are many ways to introduce it. If you need help with building
>>> jenkins plugin I can help with contribution.
>>>
>>> > I was thinking if we could create a jenkins plugin to properly handle
>>> credentials using the "withCredentials" pipeline function
>>> <https://jenkins.io/doc/pipeline/steps/credentials-binding/>
>>> That's great idea! We may also share this on the fastlate github. They
>>> have bigger community and it seems that this will be useful outside digger.
>>>
>>> Work checking: https://github.com/fastlane/fastlane/blob/master/f
>>> astlane/docs/Jenkins.md
>>>
>>>
>>> On Fri, Sep 29, 2017 at 11:09 AM, Leonardo Rossetti <lrossett at redhat.com
>>> > wrote:
>>>
>>>> Hello,
>>>>
>>>> I have created a PR against digger-jenkins with fastlane samples for
>>>> both ios and android: https://github.com/ae
>>>> rogear/digger-jenkins/pull/77
>>>>
>>>> You will notice that fastlane can replace both build and codesign logic
>>>> from our Jenkinsfiles and this approach has some advantages:
>>>>
>>>>    - easier to test it locally without jenkins (just run fastlane
>>>>    commands).
>>>>    - more flexibility since it is just a  couple of ruby scripts.
>>>>    - fastlane actions can be distributed as ruby gem packages in the
>>>>    future.
>>>>    - fastlane has several community plugins, which is easier to
>>>>    install within the jenkinsfile using the gem command if needed.
>>>>
>>>> Currently, we can't sign our binaries with fastlane because of how our
>>>> plugins (android signing and xcode) handle jenkins certificates and
>>>> developer profile files.
>>>>
>>>> I was thinking if we could create a jenkins plugin to properly handle
>>>> credentials using the "withCredentials" pipeline function
>>>> <https://jenkins.io/doc/pipeline/steps/credentials-binding/> so we
>>>> could keep the main build/sign logic in fastlane actions while we keep
>>>> specific jenkins tasks such as handling credentials, archiving the
>>>> artifact, etc in the jenkisfile.
>>>>
>>>> WDYT?
>>>> --
>>>>
>>>> LEONARDO ROSSETTI
>>>>
>>>> SOFTWARE ENGINEER
>>>>
>>>> Red Hat SP <https://www.redhat.com/>
>>>>
>>>> lrossett at redhat.com    M: 11997030621
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> WOJCIECH TROCKI
>>>
>>> Red Hat Mobile <https://www.redhat.com/>
>>>
>>> IM: wtrocki
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEONARDO ROSSETTI

SOFTWARE ENGINEER

Red Hat SP <https://www.redhat.com/>

lrossett at redhat.com    M: 11997030621
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/efa1bf49/attachment.html 

From mm at napp.dk  Fri Sep 29 14:43:09 2017
From: mm at napp.dk (=?utf-8?B?TWFkcyBNw7hsbGVy?=)
Date: Fri, 29 Sep 2017 18:43:09 +0000
Subject: [aerogear-dev] Migrate Unified Push to AWS
In-Reply-To: <CA+-uZpvtLEtizY0bgnxZFH75p2QZ5PAthuagPQJj3cKQ8uEBPA@mail.gmail.com>
References: <C413ED9E-6AB7-477D-84E4-A011FA255FAC@napp.dk>
	<CAAg5f2QJA3oVdDWtVmViDTx71cyW5=VZE_6EU8M=AmyPOBB8xg@mail.gmail.com>
	<DCF6C04A-C7EB-406F-8E69-F5D5883AFF46@napp.dk>
	<CA+-uZpuovt5Z601L_9fNR7xRQys+ixGFd7vsWAbiiHunsFXBcg@mail.gmail.com>
	<DAFAC9DE-842C-40D2-8318-F132470C6E61@napp.dk>
	<B0698850-36C4-497F-98E0-AD94797A8B92@napp.dk>
	<64A07352-83F8-4FEE-97A7-EE5EF197FC23@napp.dk>
	<BEFD087F-8438-46AA-BD3E-099A75D0CBBB@napp.dk>
	<CAAg5f2SAhOS8gQ35KQbz5Mn9fz0SdYfJbXf6njXFEFczGN3f3A@mail.gmail.com>
	<CD5C135F-9657-47E3-AE05-9386589EA3E7@napp.dk>
	<CAAg5f2TELD23DXcwbapMPk=-ZERwHqqmq60hUVhi94Nzr2uR4w@mail.gmail.com>
	<314CBCCC-A12A-444E-A9D1-1FCCA2AD657D@napp.dk>
	<FFA88F73-204C-4F30-8224-1DDCF04F5008@napp.dk>
	<8D9839CA-58FF-4887-B622-DC0F33376C31@napp.dk>
	<CA+-uZpvtLEtizY0bgnxZFH75p2QZ5PAthuagPQJj3cKQ8uEBPA@mail.gmail.com>
Message-ID: <D5DB8C19-7966-4340-B800-BB0E6D15EB38@napp.dk>

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 at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Date: Friday, 29 September 2017 at 16.36
To: AeroGear Developer Mailing List <aerogear-dev at 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 at napp.dk<mailto:mm at 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?





BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 10.04

To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 ?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 09.53
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 08.58
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS


On Fri, 29 Sep 2017 at 08:00, Mads M?ller <mm at napp.dk<mailto:mm at 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. :(



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>

Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Friday, 29 September 2017 at 07.48

To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: 42 42 80 60
M: 20 28 20 26
E: mm at napp.dk<mailto:mm at napp.dk>
W: www.napp.dk<http://www.napp.dk>
__________________

On 28 Sep 2017, at 13.21, Mads M?ller <mm at napp.dk<mailto:mm at 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.



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 11.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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?




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of "mm at napp.dk<mailto:mm at napp.dk>" <mm at napp.dk<mailto:mm at napp.dk>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.38
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

Hi,

I did that and got: http://prntscr.com/gqnxw9




BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Julio Cesar Sanchez Hernandez <jusanche at redhat.com<mailto:jusanche at redhat.com>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.30
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Subject: Re: [aerogear-dev] Migrate Unified Push to AWS

You can try https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/openshift

On Thu, Sep 28, 2017 at 10:24 AM, Mads M?ller <mm at napp.dk<mailto:mm at napp.dk>> wrote:
Any guide on how to get it working on openshift 3?



BEST REGARDS
__________________
MADS M?LLER
CTO, PARTNER

Napp A/S
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





From: <aerogear-dev-bounces at lists.jboss.org<mailto:aerogear-dev-bounces at lists.jboss.org>> on behalf of Matthias Wessendorf <matzew at apache.org<mailto:matzew at apache.org>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>>
Date: Thursday, 28 September 2017 at 10.13
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at napp.dk<mailto:mm at 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
T: +45 42 42 80 60<tel:+45%2042%2042%2080%2060>
M: +45 20 28 20 26<tel:+45%2020%2028%2020%2026>
E: mm at napp.dk<mailto:mm at napp.dk>
W: https://napp.dk<https://napp.dk/>
__________________





_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at 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 at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile
_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org<mailto:aerogear-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170929/5a4610fd/attachment-0001.html