Update HRO Cloud configuration according to latest network changes

The following nodes had their network configuration manually changed :

• storage001 had to migrated in a new subnet following a migration from 100TB (see LeastAuthority/it-ops#219)
• storage002 had the wrong gateway and netmask, likely since the provisioning (see LeastAuthority/it-ops#218)

We need to make sure morph will be handling these changes for the next deployment.