Re: [MirageOS-devel] Lifecycle

[Richard Mortier <richard.mortier@xxxxxxxxxxxx>]

On 14 July 2016 at 16:22, Nick Betteridge
<lists.nick.betteridge@xxxxxxxxx> wrote:
>
>>>>
>>>>> The basic calls would be Start, Stop, Pause, Resume. Restart?
>>>
>>>> I suspect restart may be difficult to distinguish in certain
>>>> contexts, this would make it an unreliable event. Do you have any
>>>> particular use cas for something you'd like to do knowing that you
>>>> are going to restart ?
>>>>
>>>
>>> ...in particular I wonder what Restart and Pause/Resume look like in a
>>> unikernel / microservice world, and how are they different from
>>> Stop...Start. (Assuming immutability, compile-time configuration,
>>> state persistence into Irmin, and so on.)
>>
>> Micromanagement interface? :)
>>
>
> I guess the use-case I had in mind was the radio modem connected to the
> unikernel:
>
> Stop -> inform participating unikernels that we're stopping, housekeep,
> turn off the radio.
> Pause -> housekeep, turn off the radio
> Restart -> housekeep
>
> Certainly 'Stop' is a must-have.

Ah-- I guess I don't understand who's invoking which operation :)

I had assumed that Start/Stop were operations that could be invoked on
a unikernel to boot it and then cleanly shut it down. But from what
you say above it sounds like Stop is a message that a unikernel may
broadcast to other unikernels to say "I'm stopping"? (I may just be
completely misunderstanding though!)

-- 
Richard Mortier
richard.mortier@xxxxxxxxxxxx

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel