Re: [DISCUSS] Ignite Update Checker

Cos, I’m not sure the redirect will suit us. Remember the update notifier should do 2 things: 1. get the most recent version of Ignite stored in the file on the site [1]. 2. Trigger GA. The redirect does 2. but skips 1. Any technical tricks we can apply here? [1]

Re: [DISCUSS] Ignite Update Checker

Yes, that what I meant. It might not work per website (depends on how the server is configured), but server-wide redirects could be arranged. Also, there's a new discussion on the topic going on legal-discuss@ right now [1] [1] https://is.gd/RPaWQt -- With regards, Konstantin (Cos) Boudnik

Re: [DISCUSS] Ignite Update Checker

Cos, thanks for helping out! By redirect, do you mean changing the .htaccess file to point a certain URL containing Ignite version to a GA URL? In that case, do you know if it will be possible to still send the latest Ignite version back as a response? D. On Tue, Oct 31, 2017 at 11:30 AM,

Re: [DISCUSS] Ignite Update Checker

Looks like we are getting somewhere with this. Please check [1] for the latest comment from the Infra team. I guess we can start with asking for a server-side redirect to GA as the immediate step. And explore it further possibilities as per Greg's recommendations. [1] https://is.gd/CL88O6 --

Re: [DISCUSS] Ignite Update Checker

Hi Cos, Sure, will see you around there. Anyway, a short summary is the following. Starting Ignite 2.3 the nodes will be connecting to a *static* file [1] deployed on Ignite site to obtain the most recent version. If the file has a later version than the nodes will print out a message

Re: [DISCUSS] Ignite Update Checker

Guys, I had a quick chat with Nikita earlier today and it seems that we have came across of a blocker of some kind. With my member's hat on I would love to help to find a resolution that let us (and potentially other communities) to move forward. Let's craft the message and circulate it with

Re: [DISCUSS] Ignite Update Checker

I can’t see it. Could you share a direct link to it? If we can add one more script like that and it will work then the question is closed. Denis On Monday, October 2, 2017, Dmitriy Setrakyan wrote: > Denis, I can see the download.cgi script in SVN. Am I missing

Re: [DISCUSS] Ignite Update Checker

Denis, I can see the download.cgi script in SVN. Am I missing something? On Mon, Oct 2, 2017 at 5:31 PM, Denis Magda wrote: > Dmitriy, > > That’s the rule. See replies in the ticket [1] > > *Background: the TLP server is already pretty darned busy just serving > *static*

Re: [DISCUSS] Ignite Update Checker

Dmitriy, That’s the rule. See replies in the ticket [1] *Background: the TLP server is already pretty darned busy just serving *static* sites. Dynamic operation for near-200 PMCs would bury the machine. Our policy of "static-only websites" has been in place since the Foundation started*

Re: [DISCUSS] Ignite Update Checker

On Mon, Oct 2, 2017 at 12:46 PM, Vladimir Ozerov wrote: > I am not sure it is good idea to send requests to 3rd-party addresses from > Ignite node. Let's do not make the same mistakes again. > Agree with Vladimir. We obviously have CGI support on the website. Can someone

Re: [DISCUSS] Ignite Update Checker

I am not sure it is good idea to send requests to 3rd-party addresses from Ignite node. Let's do not make the same mistakes again. On Mon, Oct 2, 2017 at 12:42 PM, Andrey Novikov wrote: > We may directly send request to GA from Ignite node: >

Re: [DISCUSS] Ignite Update Checker

We may directly send request to GA from Ignite node: https://developers.google.com/analytics/devguides/collection/protocol/v1/ Latest version can be received from maven central:

Re: [DISCUSS] Ignite Update Checker

Denis, I am not sure I understand. We already do have CGI enabled for download.cgi. Is there something else we need? D. On Mon, Oct 2, 2017 at 8:35 AM, Denis Magda wrote: > There is an obstacle. There is no way to execute the script using PHP or > similar sever side

Re: [DISCUSS] Ignite Update Checker

There is an obstacle. There is no way to execute the script using PHP or similar sever side language and trigger GA as discussed earlier: https://issues.apache.org/jira/browse/INFRA-15182 How else can we tackle this? Denis On Thursday, September 7, 2017, Dmitriy Setrakyan

Re: [DISCUSS] Ignite Update Checker

Why would we need googleads for youtube? Any chance to disable it? ⁣D.​ On Sep 30, 2017, 10:25 AM, at 10:25 AM, Prachi Garg wrote: >Yes, I see in dev tools that calls to googleads and doubleclick are >made >from Youtube. > >On Fri, Sep 29, 2017 at 4:33 PM, Denis Magda

Re: [DISCUSS] Ignite Update Checker

Yes, I see in dev tools that calls to googleads and doubleclick are made from Youtube. On Fri, Sep 29, 2017 at 4:33 PM, Denis Magda wrote: > I also did a global search on the Ignite website, but didn't find anything > for googleads or doubleclick. > > > Could you remove and

Re: [DISCUSS] Ignite Update Checker

> I also did a global search on the Ignite website, but didn't find anything > for googleads or doubleclick. Could you remove and add screencasts block temporary on your local deployment to see if the calls to commercial scripts reported by Cos appear in your Chrome dev toolkit? — Denis >

Re: [DISCUSS] Ignite Update Checker

We use the following scripts - https://platform.twitter.com/widgets.js - used on homepage to display tweets https://static.addtoany.com/menu/page.js - used on events page for social media sharing https://www.google-analytics.com/analytics.js I also did a global search on the Ignite website, but

Re: [DISCUSS] Ignite Update Checker

That’s definitely worthwhile checking. Prachi, as the one who embedded the screencast, would you check the theory? — Denis > On Sep 28, 2017, at 11:50 PM, Alexey Kuznetsov wrote: > > Cos, Denis. > > I think it is because we have embedded videos (on YouTube). > Mauricio

Re: [DISCUSS] Ignite Update Checker

Cos, Denis. I think it is because we have embedded videos (on YouTube). Mauricio or Denis, please check my idea. On Fri, Sep 29, 2017 at 8:02 AM, Konstantin Boudnik wrote: > Sorry guys - I neglected the fact that our lists don't permit > attachments. I have put the screenshot

Re: [DISCUSS] Ignite Update Checker

Sorry guys - I neglected the fact that our lists don't permit attachments. I have put the screenshot to an external server [1] [1] https://imgur.com/a/p9FJ9 Thank you! -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed

Re: [DISCUSS] Ignite Update Checker

Cos, The screenshot was not attached. Could you share it some other way (google drive, etc.)? I’ve never seen any commercial on the site. — Denis > On Sep 28, 2017, at 7:23 AM, Konstantin Boudnik wrote: > > I don't see an issue with node version either. > > Just one more,

Re: [DISCUSS] Ignite Update Checker

I don't see an issue with node version either. Just one more, and it might be slightly irrelevant, issue though... I looked at the Ignite's site and found the following ads and trackers (that are indeed getting disabled by my browser). Why are googleads or doubleclick are permitted? ​ Thanks,

Re: [DISCUSS] Ignite Update Checker

On Tue, Sep 26, 2017 at 6:20 AM, Vladimir Ozerov wrote: > Folks, > > Can we add version of current node to web request? This way we will better > understand version distribution, what might help us with certain API > update/deprecate decisions > E.g.

Re: [DISCUSS] Ignite Update Checker

Folks, Can we add version of current node to web request? This way we will better understand version distribution, what might help us with certain API update/deprecate decisions E.g. http://ignite.apache.org/latest.cgi=2.2.0 Vladimir. On Fri, Sep 8, 2017 at 7:06 AM, Dmitriy Setrakyan

Re: [DISCUSS] Ignite Update Checker

I think it is safe to assume at this point that everyone is in general agreement, since there are no active objections. I have filed a ticket for the 2.3 release. Let's try to make it happen: https://issues.apache.org/jira/browse/IGNITE-6305 D. On Sat, Aug 26, 2017 at 3:06 PM, Dmitriy Setrakyan

Re: [DISCUSS] Ignite Update Checker

On Sat, Aug 26, 2017 at 3:22 AM, Raúl Kripalani wrote: > Yeah, I guess that's doable as well and requires less management effort > than my suggestion. We could use events [1] to store payload data (e.g. IP, > version, etc.) Yes, we could use events or some other similar

Re: [DISCUSS] Ignite Update Checker

Yeah, I guess that's doable as well and requires less management effort than my suggestion. We could use events [1] to store payload data (e.g. IP, version, etc.) What the download page CGI developed in? PHP? However, I'm not sure whether storing this data in a 3rd party (Google) is compliant

Re: [DISCUSS] Ignite Update Checker

This will surely works to get the update info to the nodes. And it sounds like a legit approach. I cannot judge on the feasibility of the GA though - don't know squat about it ;) Thanks! -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer:

Re: [DISCUSS] Ignite Update Checker

Hey Dmitriy and all Also, since we have GA enabled for the website, we can track how many times > this page was accessed, which will be equal to the number of starts. This > way, the counter information is tracked and monitored by the Ignite PMC. Unfortunately this won't work because GA is

Re: [DISCUSS] Ignite Update Checker

Cos, Raul, Thanks for the feedback. I completely agree about Maven Central being a 3rd party repo (did not think about that initially). All your suggestions make sense, but I would like to keep it as simple as possible, and so far everything suggested required GIT dependencies and extra work.

Re: [DISCUSS] Ignite Update Checker

I agree with Raul. - providing a ping-back address to a 3rd party might be frown upon by some. And might have a consequences like stats collection about users' infrastructure. - checking an ASF git-repo is easy and won't download any binary data: everything is clear text and could be easily

Re: [DISCUSS] Ignite Update Checker

Raul, any ideas on startup counter? BTW, we have google analytics applied to Ignite site. Can it be used to count node starts? --Yakov

Re: [DISCUSS] Ignite Update Checker

Hey guys In my opinion, maven.org is still owned by a third party (Sonatype). We don't know what kind of data analysis or intelligence extraction they run. If Ignite servers all over the world were hitting maven.org periodically asking for an Ignite Maven artifact, it gives Sonatype a clear

Re: [DISCUSS] Ignite Update Checker

I see nothing wrong with this approach. Cos, Roman, Raul, as Apache veterans, what do you think? Is it good to go? — Denis > On Aug 23, 2017, at 11:17 PM, Dmitriy Setrakyan wrote: > > Is everyone OK with this approach? Should I file a ticket on it? > > On Mon, Aug 21,

Re: [DISCUSS] Ignite Update Checker

Is everyone OK with this approach? Should I file a ticket on it? On Mon, Aug 21, 2017 at 2:07 PM, Dmitriy Setrakyan wrote: > Igniters, > > There has been lots of talk of proposals about various usage metrics for > Ignite and nothing came of it. I would like to resurrect