Hi,
I'm writing to inform, that the current Windows infrastructure hosting
sponsor doesn't plan to support the project anymore. Furthermore, a
notification was given, that the servers will be taken down within a couple
of next weeks. Alex Schoenmaker found another sponsor, so all the HW will
have to be moved to a new place. As a consequence, some shortages are to
expect. The particular date for the move is 3pm-4pm CET on Friday 20th
January. The downtime might concern windows.php.net downloads, snapshot
build uploads, as well as the PECL build and upload service. Especially as
the boxes have to be physically disconnected, a downtime of at least one
hour is possible. Please plan your possible work with accordance to this
info.
This action requires some one of the devops to set the new A record and to
reload the DNS server configuration. I'm going to mail the new IP address
for the A record to systems@php.net close to the moment things are about to
move. A temporary redirect is planned for the transition time, so then at
least the basic service should be back after the boxes are back online.
However, this redirect will likely to be only active only until the end of
January. Could please someone from the systems team give a confirmation, the
record could be changed close to the move action?
Thanks
Anatol
Hi,
I'm writing to inform, that the current Windows infrastructure hosting
sponsor doesn't plan to support the project anymore. Furthermore, a
notification was given, that the servers will be taken down within a couple
of next weeks. Alex Schoenmaker found another sponsor, so all the HW will
have to be moved to a new place. As a consequence, some shortages are to
expect. The particular date for the move is 3pm-4pm CET on Friday 20th
January. The downtime might concern windows.php.net downloads, snapshot
build uploads, as well as the PECL build and upload service. Especially as
the boxes have to be physically disconnected, a downtime of at least one
hour is possible. Please plan your possible work with accordance to this
info.This action requires some one of the devops to set the new A record and to
reload the DNS server configuration. I'm going to mail the new IP address
for the A record to systems@php.net close to the moment things are about
to
move. A temporary redirect is planned for the transition time, so then at
least the basic service should be back after the boxes are back online.
However, this redirect will likely to be only active only until the end of
January. Could please someone from the systems team give a confirmation,
the
record could be changed close to the move action?Thanks
Anatol
Hi Anatol,
if such a change is planned, the TTL for the DNS record should probably be
adjusted to have a shorter caching of the old records.
Regards, Niklas
"Anatol Belski" in php.internals (Tue, 17 Jan 2017 20:14:55 +0100):
I'm writing to inform, that the current Windows infrastructure hosting
sponsor doesn't plan to support the project anymore. Furthermore, a
notification was given, that the servers will be taken down within a couple
of next weeks.
Just curious: what kind of boxes are we talking about? Can we get some
insight in CPU's, RAM, OS and storage space and speed?
BTW: kudos for the new sponsor.
Jan
W dniu 18.01.2017 o 07:47, Jan Ehrhardt pisze:
"Anatol Belski" in php.internals (Tue, 17 Jan 2017 20:14:55 +0100):
I'm writing to inform, that the current Windows infrastructure hosting
sponsor doesn't plan to support the project anymore. Furthermore, a
notification was given, that the servers will be taken down within a couple
of next weeks.Just curious: what kind of boxes are we talking about? Can we get some
insight in CPU's, RAM, OS and storage space and speed?BTW: kudos for the new sponsor.
I will ask differently: will wiki.php.net/systems be updated afterwards?
I will ask differently: will wiki.php.net/systems be updated afterwards?
I saw a few outdated links there, maybe someone can correct/remove them?
Within "Machine Status"
- "public network status" http://monitoring.php.net/status/ => 404
- "available here" http://monitoring.php.net/munin/ => 404
- "protected area" http://monitoring.php.net/nagios/ => 404
- And it isn't "Nagios" anymore but "Icinga".
Seems only http://monitoring.php.net/ itself is relevant anymore.
:-)
- Markus
I will ask differently: will wiki.php.net/systems be updated afterwards?
I saw a few outdated links there, maybe someone can correct/remove them?
Within "Machine Status"
- "public network status" http://monitoring.php.net/status/ => 404
- "available here" http://monitoring.php.net/munin/ => 404
- "protected area" http://monitoring.php.net/nagios/ => 404
- And it isn't "Nagios" anymore but "Icinga".
Seems only http://monitoring.php.net/ itself is relevant anymore.
Apparently, that is. However, I can't login with my PHP account
credentials. :-/
--
Christoph M. Becker
W dniu 18.01.2017 o 15:28, Christoph M. Becker pisze:
I will ask differently: will wiki.php.net/systems be updated afterwards?
I saw a few outdated links there, maybe someone can correct/remove them?
Within "Machine Status"
- "public network status" http://monitoring.php.net/status/ => 404
- "available here" http://monitoring.php.net/munin/ => 404
- "protected area" http://monitoring.php.net/nagios/ => 404
- And it isn't "Nagios" anymore but "Icinga".
Seems only http://monitoring.php.net/ itself is relevant anymore.
Apparently, that is. However, I can't login with my PHP account
credentials. :-/
I can confirm, can't login as well. We really should keep those
/systems entries up-to-date, it's PITA to plan any changes regarding
infrastructure now. I did update informations about the box I was able
to (euk2.php.net) but the rest is out of my possibilities.
"Anatol Belski" in php.windows (Tue, 17 Jan 2017 20:14:55 +0100):
I'm writing to inform, that the current Windows infrastructure hosting
sponsor doesn't plan to support the project anymore. Furthermore, a
notification was given, that the servers will be taken down within a couple
of next weeks. Alex Schoenmaker found another sponsor, so all the HW will
have to be moved to a new place. As a consequence, some shortages are to
expect. The particular date for the move is 3pm-4pm CET on Friday 20th
January.
windows.php.net is down at the moment. What is happening?
Jan
windows.php.net is down at the moment. What is happening?
Seems it's back again. :)
--
Christoph M. Becker