OVH Travaux http://status.ovh.net/ Wed, 22 Feb 2012 18:57:39 +0100 VoIP:: FS#6154 — Telefon plug'n'phone For this purpose we should separate the different voip used technologies on different Ips.

We are going to reconfigure all the plug'n'phone ovh (thomson st2030 and LG sideline).
These phones will connect on a dedicated Ip.

If you use a firewall, please check that the trafic to 91.121.129.0/24 and 91.121.128.0/24 in UDP are authorized. ]]> Task Type: Maintenance

Category: Backend / Core

Status: Finished


Due to the growth that we are facing, we must improve our network architecture.
For this purpose we should separate the different voip used technologies on different Ips.

We are going to reconfigure all the plug'n'phone ovh (thomson st2030 and LG sideline).
These phones will connect on a dedicated Ip.

If you use a firewall, please check that the trafic to 91.121.129.0/24 and 91.121.128.0/24 in UDP are authorized.

Comments:

Date: Wed, 22 Feb 2012 18:57:20 +0100

A bypass solution has been found.

]]> Wed, 22 Feb 2012 18:57:39 +0100 http://status.ovh.net/?do=details&id=2183 http://status.ovh.net/?do=details&id=2183 VoIP:: FS#6383 — SIP restriction by IP
This feature provide better security of SIP accounts.
It will contain a number of attacks that may exist on the Internet.

The restriction by IP will only be active once configured on a line.
The principle is identical to a white list. Only authorized network or ip will be authorized
to connect with a given SIP account.


]]> Task Type: Modernization

Category: Backend / Core

Status: Finished


To improve the security of our infrastructure, we add SIP restriction by IP SIP at the proxy.

This feature provide better security of SIP accounts.
It will contain a number of attacks that may exist on the Internet.

The restriction by IP will only be active once configured on a line.
The principle is identical to a white list. Only authorized network or ip will be authorized
to connect with a given SIP account.


Comments:

Date: Wed, 22 Feb 2012 09:19:58 +0100

We activate the functionality on the instance of port 53.

Date: Wed, 22 Feb 2012 09:20:37 +0100

The tests are OK. There is no change in behavior when the restriction is not configured.

Date: Wed, 22 Feb 2012 09:22:39 +0100

We activate on all ports of the proxy 's listeners.

Date: Wed, 22 Feb 2012 09:24:01 +0100

The none regression tests are OK.

Date: Wed, 22 Feb 2012 18:54:00 +0100

Restrictions by ip were activated.

]]> Wed, 22 Feb 2012 18:54:12 +0100 http://status.ovh.net/?do=details&id=2438 http://status.ovh.net/?do=details&id=2438 VoIP:: FS#6405 — sip.ovh.fr http://status.ovh.net/?do=details&id=2438)
we will create new French sip lines on the field on the domain sip.ovh.fr
Old lines who wish to use this feature may migrate their line
simply from the manager.
]]> Task Type: Modernization

Category: Backend / Core

Status: Finished


To activate the SIP restriction by (http://status.ovh.net/?do=details&id=2438)
we will create new French sip lines on the field on the domain sip.ovh.fr
Old lines who wish to use this feature may migrate their line
simply from the manager.
]]> Wed, 22 Feb 2012 18:52:12 +0100 http://status.ovh.net/?do=details&id=2439 http://status.ovh.net/?do=details&id=2439 Hosting:: FS#6410 — Mysql servers update
mysql5-0.bdb
mysql5-2.bdb
mysql5-3.bdb
mysql5-6.bdb
mysql5-7.bdb
mysql5-8.bdb
mysql5-14.bdb
mysql5-15.bdb
mysql5-18.bdb
mysql5-21.bdb
mysql5-22.bdb
mysql5-24.bdb
mysql5-28.bdb
mysql5-30.bdb
mysql51-32.bdb
mysql51-33.bdb
mysql51-35.bdb
mysql51-47.bdb
mysql51-48.bdb
mysql51-49.bdb
mysql51-50.bdb
mysql51-51.bdb

This operation will take place throughout the night, between 1am and 6am.
]]> Task Type: Maintenance

Category: all (Plan hostings)

Status: Planned


As part of an improvement of BDB database performances. Unavailability of ten minutes on the following servers can be observed:

mysql5-0.bdb
mysql5-2.bdb
mysql5-3.bdb
mysql5-6.bdb
mysql5-7.bdb
mysql5-8.bdb
mysql5-14.bdb
mysql5-15.bdb
mysql5-18.bdb
mysql5-21.bdb
mysql5-22.bdb
mysql5-24.bdb
mysql5-28.bdb
mysql5-30.bdb
mysql51-32.bdb
mysql51-33.bdb
mysql51-35.bdb
mysql51-47.bdb
mysql51-48.bdb
mysql51-49.bdb
mysql51-50.bdb
mysql51-51.bdb

This operation will take place throughout the night, between 1am and 6am.
]]> Wed, 22 Feb 2012 18:51:09 +0100 http://status.ovh.net/?do=details&id=2445 http://status.ovh.net/?do=details&id=2445 VoIP:: FS#6411 — Database Task Type: Incident

Category: Backend / Core

Status: Finished


We encounter problems at the level of the database.

Comments:

Date: Wed, 22 Feb 2012 18:35:39 +0100

Abreviated numbers are impacted.

Date: Wed, 22 Feb 2012 18:39:24 +0100

The communication with the base was interrupted. the problem is repaired. we analyze the origin of the problem with the constructor.

Date: Wed, 22 Feb 2012 18:41:49 +0100

a process has been freeze and lock a table. The patch is under elaboration by the constructor.

]]> Wed, 22 Feb 2012 18:42:02 +0100 http://status.ovh.net/?do=details&id=2444 http://status.ovh.net/?do=details&id=2444 Dedicated servers:: S#6407 — rescue mode update
This rescue system is based on Debian 6 "Lenny" and will bring generic enhancements through newer software versions, as well as some additional tools for system administration (recovery utils, filesystem tools, installation helpers, ...)]]> Task Type: Modernization

Category: all (dedicated servers)

Status: In progress


We will start rolling out a new rescue mode for dedicated servers.

This rescue system is based on Debian 6 "Lenny" and will bring generic enhancements through newer software versions, as well as some additional tools for system administration (recovery utils, filesystem tools, installation helpers, ...)

Comments:

Date: Wed, 22 Feb 2012 16:07:48 +0100

In a first stage, the new rescue system has been enabled for customers. Our internal rescue systems will be updated in a later stage.

]]> Wed, 22 Feb 2012 16:07:48 +0100 http://status.ovh.net/?do=details&id=2440 http://status.ovh.net/?do=details&id=2440 Private Cloud:: FS#6329 — Upgrade Leclerc
Sdd disks will be added in each one of the leclerc where the writing cache will be stored.

The data will still be stocked on the classical disks, dedicated for each customer.

This will allow to increase sensibly the performances (and the latencies) in writing.

This upgrade is expected with no impact for the final customer and without no reconfiguration
from his part.

First of all, we are going to reorganise the used disks on the leclerc in order to insert those
new ssd disks.


After that, we are going to restart the master head and the slave head of each leclerc in order
to update the configuration of the disk controls This configuration change is necessary to
ensure the consistency of the data during a future switch between the 2 heads.


Then, we are going to configure the ssd disks to use them in cache of the existing datastores.]]> Task Type: Modernization

Category: Backend / Core

Status: In progress


We are going to upgrade all the datastores of the pcc customers in order to use the hybrid technology.

Sdd disks will be added in each one of the leclerc where the writing cache will be stored.

The data will still be stocked on the classical disks, dedicated for each customer.

This will allow to increase sensibly the performances (and the latencies) in writing.

This upgrade is expected with no impact for the final customer and without no reconfiguration
from his part.

First of all, we are going to reorganise the used disks on the leclerc in order to insert those
new ssd disks.


After that, we are going to restart the master head and the slave head of each leclerc in order
to update the configuration of the disk controls This configuration change is necessary to
ensure the consistency of the data during a future switch between the 2 heads.


Then, we are going to configure the ssd disks to use them in cache of the existing datastores.

Comments:

Date: Sun, 05 Feb 2012 18:30:06 +0100

The reorganisation of the used disks is done. We freed the necessary spots to allow the insertion of the new ssd disks. The first step of the intervention is done. We are going to spread the seconde step (configuration change) over two nights this week. It's the most sensitive operation. We planned this procedure on the papr but the task force will be also there in order to react in case of problem.

Date: Tue, 07 Feb 2012 09:45:02 +0100

We start the second step this night. Beginning of the operations predicted in the midnight.

Date: Tue, 07 Feb 2012 09:53:05 +0100

1/3 of heads have been restarted with the new configuration. The manual switch procedure is perfectible to avoid some problems at the level of umount/mount/share between ZFS and NFS. We will follow upgrades the next night.

Date: Wed, 08 Feb 2012 09:28:01 +0100

We will begin upgrades in 20 minutes. We improved the procedure of switch to have a faster recovery by service. We have also included probes to get the state of the vm and the datastore before during and after intervention.

Date: Wed, 08 Feb 2012 09:30:47 +0100

The change of the first leclerc was performed properly. The probes of the vm and datastores are green. We continue the change of the following Leclerc.

Date: Wed, 08 Feb 2012 09:31:48 +0100

80% of planned changes were performed. We continue.

Date: Wed, 08 Feb 2012 09:36:57 +0100

During the change of head-42 slave to head-42 master, the master crashed during the import. 3 datastores were above: pcc-001095, pcc-001096 and pcc-001097. We created tickets with concerned customers and we restarted the impacted vms. We will fix the hardware of head-42 Masters before returning it to service. We leave the concerned datastore in service on the slave.

Date: Wed, 08 Feb 2012 09:41:03 +0100

We completed the upgrade of leclerc heads configuration. 2 heads are left on the Slaves (head-42 and head-150). We ill Check the hardware of masters before returning them to service. The most sensible part of upgrades is completed. Next step: inserting the ssd that we will perform tomorrow during the day.

]]> Wed, 22 Feb 2012 11:55:25 +0100 http://status.ovh.net/?do=details&id=2363 http://status.ovh.net/?do=details&id=2363 Hosting:: FS#6409 — Displacements of storage servers Unavailability of 5 to 10 minutes is expected.

Servers concerned with the maintenance:

filerz506.pro.ha.ovh.net
filerz507.media.ha.ovh.net
filerz505.mail.ha.ovh.net
filerz508.mail.ha.ovh.net]]> Task Type: Maintenance

Category: all (Plan hostings)

Status: Planned


We will move many storage servers of the shared infrastructure and email during the night of Wednesday 22/02 to Thursday 23/02.
Unavailability of 5 to 10 minutes is expected.

Servers concerned with the maintenance:

filerz506.pro.ha.ovh.net
filerz507.media.ha.ovh.net
filerz505.mail.ha.ovh.net
filerz508.mail.ha.ovh.net]]> Wed, 22 Feb 2012 11:20:43 +0100 http://status.ovh.net/?do=details&id=2443 http://status.ovh.net/?do=details&id=2443 Dedicated servers:: FS#6406 — ftpback-rbx3-295.ovh.net maintenance
]]> Task Type: Maintenance

Category: Associated service

Status: Finished


We perform a maintenance operation on the server ftpback-rbx3-295.ovh.net. The data will be in read-only the time of the intervention.

]]> Wed, 22 Feb 2012 11:17:05 +0100 http://status.ovh.net/?do=details&id=2437 http://status.ovh.net/?do=details&id=2437 Datacenter:: FS#6375 — Rescue transformer test rescue transformer for the datacenter of Roubaix 2.

There is no interruption expected, the UPS will insure
the continuity of electricity's supply to the servers.
]]> Task Type: Maintenance

Category: Roubaix 2

Status: In progress


We are currently conducting switch tests on the
rescue transformer for the datacenter of Roubaix 2.

There is no interruption expected, the UPS will insure
the continuity of electricity's supply to the servers.

Comments:

Date: Thu, 16 Feb 2012 11:29:43 +0100

We continue the tests of this morning.

]]> Wed, 22 Feb 2012 10:49:35 +0100 http://status.ovh.net/?do=details&id=2408 http://status.ovh.net/?do=details&id=2408