Open Stack

On Tue, May 28, 2019 at 8:31 AM Csatari, Gergely (Nokia - HU/Budapest)
<gergely.csatari at nokia.com> wrote:
>
> Hi,
>
> There was a one hour discussion with Julia from Ironic with the Edge Computing Group [1]. In this mail I try to conclude what was discussed and ask some clarification questions.
>
> Current Ironic uses DHCP for hardware provisioning, therefore it requires DHCP relay enabled on the whole path to the edge cloud instances. There are two alternatives to solve this:
> 1) Virtual media support [2] where the ip configuration is embedded into a virtual image what is booted via the board management interface
> 2) Redfish support, however the state and support of redfish for host management is not clear. Is there already a specification has been added for redfish support?

I don't quite remember discussing redfish in this regard. Is there
something your expecting redfish to be able to provide in this regard?
Redfish virtual media is something we're working on.

>
> Upgrade of edge cloud infrastructures:
>   - Firmware upgrade should be supported by Ironic. Is this something on its way or is this a new need?

The ilo hardware type supports OOB firmware upgrades. iRMC has code up
in review, and Dell has a posted specification. Work is going into the
redfish libraries to help support this so we will likely see something
for redfish at some point, but it may also be that because of vendor
differences, that we may not be able to provide a generic surface
through which to provide firmware update capabilities through the
generic hardware type.

>   - Operating system and infra update can be solved using Fenix [3], however handling several edge cloud instances from a central location needs new features.
>
> Handling of failed servers:
>   - A monitoring system or the operator should provide the input to mark a server as failed
>   - Ironic can power down the failed servers and have the definition of a maintenance state
>   - Discussed in [4]
>
> Additional ideas what we half discussed:
>   - Running Ironic containers in a switch with the images hosted by Swift somewhere else. Are there any concerns about this idea? Any missing features from somewhere?
>
> [1]: https://etherpad.openstack.org/p/edge-wg-ptg-preparation-denver-2019
> [2]: https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/L3-based-deployment.html
> [3]: https://wiki.openstack.org/wiki/Fenix
> [4]: http://lists.openstack.org/pipermail/edge-computing/2019-May/000582.html
>
> Br,
> Gerg0
>