All users were logged out of Bugzilla on October 13th, 2018

New public IP-address for relman-vm1.dmz.scl3.mozilla.com

RESOLVED INVALID

Status

RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: sylvestre, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
We, release managers, are now the happy admins of a VM (bug 1149571).

We are planning to publish some json (static) files with the list of all Firefox, Fennec and Thunderbird releases (and probably iOS soon).

The big picture is that we would like to migrate from static files managed some old php code to use the ship-it application which has up to date data (detailed in bug 1083718).

Because we don't want to move ship-it outside of the VPN, as discussed in bug 1146897 (comment #6), we would like to set up a cron job.

The idea is quite simple, from our VM, as it has access to the ship-it web interface, it would just do some wget/curl on the json files and presents them to the public (that is why I said they are static).

We don't have any issues to have if new IP filtered (except ports 80 & 443)
Sounds like webops should get you a VIP on ZLB.

Do you have the service description somewhere?
Group: mozilla-employee-confidential

Updated

4 years ago
Flags: needinfo?(sledru)
(Reporter)

Comment 2

4 years ago
Yes, it is described in the bug 1083718 & 1146897.

Product details is a php library generating json files ( http://viewvc.svn.mozilla.org/vc/libs/product-details/json/ ). More:
https://wiki.mozilla.org/Release_Management/Release_Notes_and_Product_Details#Product_Details

Ship-it, which still won't be available outside of the vpn, is described here:
https://wiki.mozilla.org/ReleaseEngineering/Applications/Ship_It

Hope this helps
Flags: needinfo?(sledru)
We (Sylvestre, Ben Hearsum and I) are going to talk about this in a meeting tomorrow before deciding on how to proceed here.
(In reply to Shyam Mani [:fox2mike] from comment #3)
> We (Sylvestre, Ben Hearsum and I) are going to talk about this in a meeting
> tomorrow before deciding on how to proceed here.

And this isn't needed. Closing.
Assignee: network-operations → server-ops-webops
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Component: NetOps → WebOps: Other
QA Contact: jbarnell → smani
Resolution: --- → INVALID
(Reporter)

Comment 5

4 years ago
Instead, we will be using a cron on ship-it to export the json file on mozilla.org (or something similar)

Removing "Confidential Mozilla Employee Bug" as there is no confidential info in this bug.
Group: mozilla-employee-confidential
You need to log in before you can comment on or make changes to this bug.