Popularity Contest

[Sebastian Roth]

@george1421 Good point! Though I would use a more simple name that is easy to remember and type, e.g. stats.fogproject.org?

[Wayne Workman]

Sounds good.

[Sebastian Roth]

@Wayne-Workman said in Popularity Contest:

Right now it’s: https://fog-external-reporting-entries.theworkmans.us:/api/records

This URL does not seem to work in the browser. It’s the backend API URL if I am not on the wrong track. But we want the frontend URL http://fog-external-reporting-results.theworkmans.us/ right? Can you setup HTTPS as well?

[Wayne Workman]

Yeah the back-end only takes entries, nothing else.

The frontend url is less important, as that’s not needed in the fog codebase anywhere. It’s just a place one visits to see results. I can get HTTPS setup for it.

[Wayne Workman]

@Sebastian-Roth So when I try:

curl -X POST -H "Content-Type: application/json"  -d '{"fog_version":"testing","os_name":"testing","os_version":"testing"}' https://stats-api.fogproject.org/api/records

This is the result:

curl: (6) Could not resolve host: stats-api.fogproject.org

[Wayne Workman]

@Sebastian-Roth if you can get an A record created for stats-api.fogproject.org with a value of 3.20.18.241 I can get the ssl cert and such fixed on my side (using lets encrypt). Once that’s all done, we can update the reporting script to use the new URL.

For the results to have a good redirect from stats.fogproject.org, I need the SSL cert to include that subject alternative name. Please create this record, it’ll allow me to create that SSL cert. These values below are not secrets, and they will timeout in 72 hours from now (sometime wednesday). if it’s not made by then I can get new values. This is part of how AWS verifies the cert your making is legit.

Name:
_395058431eb78e5f8f9cc2478adbdfa3.stats.fogproject.org.

Type:
CNAME

Value:
_ee8469a4f9a938de348ef383be83b11f.zbkrxsrfvj.acm-validations.aws.

If this can’t be done for whatever reason, I can use the original results URL and it’ll work fine, just redirects from stats.fogproject.org won’t work.

Here’s the changes on the cloud side if you were interested.

[Sebastian Roth]

@wayne-workman said in Popularity Contest:

For the results to have a good redirect from stats.fogproject.org, I need the SSL cert to include that subject alternative name.

That’s interesting. While I can look it up using the host command I can’t ping it.

$ host stats.fogproject.org
stats.fogproject.org is an alias for fog-external-reporting-results.theworkmans.us.
$ ping stats.fogproject.org
ping: stats.fogproject.org: Name or service not known

[Wayne Workman]

@sebastian-roth Right, the alias is fine, please leave it as-is.

I tried without the subject alternative name and got browser errors related to SSL. The front-end is in AWS CloudFront, which uses AWS ACM for ssl certs. I can’t make a cert with the fogproject SAN in it without the verification. Right now, it’s not set-up as I figured we wanted to get the redirect working right. If that can’t be done, no big deal.

[Wayne Workman]

Tried emailing chuck, he has not replied. For now, I’ve removed all of the fogproject.org references, and HTTPS is working directly (redirect does not work). This is fine until Chuck can help with the DNS records.

[Sebastian Roth]

@Wayne-Workman Do you think adding the kernel version used might be possible? We see many people using non-default kernel versions and it might be interesting to add that information as well.

I have not looked into it yet. So no idea how much work it might be. Just bringing up the idea before it fades away in my head.

[Wayne Workman]

@sebastian-roth I’ll look into it. I assume you mean FOS kernel, not FOG server’s kernel. Hold on the release while I poke at this please.

[Sebastian Roth]

@wayne-workman said in Popularity Contest:

I assume you mean FOS kernel, not FOG server’s kernel.

Exactly, thanks!

[Wayne Workman]

@Sebastian-Roth as well as all the others ( @developers @moderators @testers )

Would we want anything besides kernel information? I had some ideas:

Number of hosts
Number of images
Number of each type of image
Number of systems imaged in the last 7 days
Number of storage nodes
Number of storage groups
Other things?

It’s been said before, but will say it again. This is all anonymous data. There is no way to correlate this data back to any system.

It just provides us insight (and possibly bragging rights). imagine us being able to say “FOG imaged a bazillion systems last week, we’re proud of that” or maybe “FOG assists with managing a quadrillion million computer systems every day”. I’m being funny with the imaginary figures here, but you get the idea. It’d be nice to make statements like that on the home page fogproject.org