Bug 20148 - It is impossible to select 20GBits as changed bandwidth for a Mageia mirror
Summary: It is impossible to select 20GBits as changed bandwidth for a Mageia mirror
Status: NEW
Alias: None
Product: Websites
Classification: Unclassified
Component: mirrors.mageia.org (show other bugs)
Version: trunk
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-20 16:48 CET by Marja Van Waes
Modified: 2017-01-20 17:05 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Marja Van Waes 2017-01-20 16:48:16 CET
The Princeton mirror now has 20Gbits bandwidth

From #mageia-sysadm:
2017:01:19:23:39 < brose> oh one other thing I've been going around updating - I set up LACP for mirror.math and campus networking group upgraded our service so I am officially 20 gigabits of bandwidth available now :-) 

But the bandwidth can't be increased to 20Gbits in http://mirrors.mageia.org/

After pressing the "update information" button in  http://mirrors.mageia.org/mirrors/mirror.math.princeton.edu  the drop down list after "Approximated bandwidth" has 10Gbits as highest value.
Comment 1 Rémi Verschelde 2017-01-20 17:05:01 CET
From a quick grep I'd say that it needs to be edited directly in the database, as this is in dump.sql here http://gitweb.mageia.org/software/infrastructure/mgamirrors/tree/

~~~~

--
-- Data for Name: bandwidth; Type: TABLE DATA; Schema: public; Owner: nanardon
--

COPY bandwidth (name, value) FROM stdin;
10Mbits 10485760
100Mbits        104857600
1Gbits  1073741824
10Gbits 10737418240
2Gbits  2147483648
\.

~~~~

Also I suppose this part should be edited to match the DB: http://gitweb.mageia.org/software/infrastructure/mgamirrors/tree/root/html/pages/report/index.tt#n38

The template for the linked page seems to be: http://gitweb.mageia.org/software/infrastructure/mgamirrors/tree/root/html/includes/host_information.tt#n82

Note You need to log in before you can comment on or make changes to this bug.