OVHcloud Bare Metal Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[Worldwide][Dedicated Servers] - IPXE scripts migration
Scheduled Maintenance
Report for Bare Metal Cloud
Completed
The scheduled maintenance has been completed.
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Update
We will be undergoing scheduled maintenance during this time.
Scheduled
Start time :16/04/2024 08:30 UTC
End time : 16/04/2024 08:45 UTC
Service impact : None
Service improvement : Our iPXE scripts API is evolving, we are simplifying the API call format used to boot a server from a custom iPXE script.
The API calls to make the server boot from the local disk or the rescue are not affected by this change. If you don't know what an iPXE script is, then you are probably not impacted by this change.
The 16th April 2024, we will remove the compatibility with the old method.
Customers can already start using the new method to boot a server from an iPXE script: see the following documentation for more details.
Old method that will stop working
1. The customer adds an iPXE script in their account by using API call POST /me/ipxeScript.
Note that this API call has already been removed the 5th of March 2024: see this status task.
2. For a specific server, the customer calls GET /dedicated/server/{serviceName}/boot?bootType=ipxeCustomerScript to list all compatible iPXE scripts: it returns boot IDs.
3. For any boot ID returned by previous API call, the customer needs to call GET /dedicated/server/{serviceName}/boot/{bootId} to get details untill they find which boot ID corresponds to the previously added iPXE script.
4. Then, the customer needs to call PUT /dedicated/server/{serviceName} with the "bootId" key and the previously obtained boot ID.
New simpler method that is already available
The customer uses the new "bootScript" key within the PUT /dedicated/server/{serviceName} call and directly passes it their iPXE script, see this documentation.
That's it. As you can see it's now less complicated to boot from a custom iPXE script.
End time : 16/04/2024 08:45 UTC
Service impact : None
Service improvement : Our iPXE scripts API is evolving, we are simplifying the API call format used to boot a server from a custom iPXE script.
The API calls to make the server boot from the local disk or the rescue are not affected by this change. If you don't know what an iPXE script is, then you are probably not impacted by this change.
The 16th April 2024, we will remove the compatibility with the old method.
Customers can already start using the new method to boot a server from an iPXE script: see the following documentation for more details.
Old method that will stop working
1. The customer adds an iPXE script in their account by using API call POST /me/ipxeScript.
Note that this API call has already been removed the 5th of March 2024: see this status task.
2. For a specific server, the customer calls GET /dedicated/server/{serviceName}/boot?bootType=ipxeCustomerScript to list all compatible iPXE scripts: it returns boot IDs.
3. For any boot ID returned by previous API call, the customer needs to call GET /dedicated/server/{serviceName}/boot/{bootId} to get details untill they find which boot ID corresponds to the previously added iPXE script.
4. Then, the customer needs to call PUT /dedicated/server/{serviceName} with the "bootId" key and the previously obtained boot ID.
New simpler method that is already available
The customer uses the new "bootScript" key within the PUT /dedicated/server/{serviceName} call and directly passes it their iPXE script, see this documentation.
That's it. As you can see it's now less complicated to boot from a custom iPXE script.
This scheduled maintenance affected: Dedicated Servers || Operating System (Zone Europe, Zone APAC, Zone Canada).