[bind10-dev] Possibly deprecated/solved boss tickets

[Shane Kerr]

Michal,

On Tue, 2011-11-22 at 14:01 +0100, Michal 'vorner' Vaner wrote:
> 
> I remembered I forgot to create a few of the TODO tickets after #213 was
> completed. So I went through it and started creating them. But as I looked for
> tickets that are already created, I discovered a number of tickets related to
> boss which might be already solved, depending on how they are understood. So,
> I'd like your opinions on them. If nobody will protest against closing a ticket
> listed here by the end of the next sprint, I propose we close it.
> 
> The tickets are:
> #230: BoB sequenced startup ‒ we have priorities, so we can order the components
>       the way we want them to start. We don't have a way to tell a component is
>       fully started before going to the next one yet.

I think this one can plausibly still be useful, so maybe we should keep
it open.

> #791: Add command to boss to see component configuration ‒ Does it mean to see
>       which components should start? If so, config show Boss/components will do.

That is part of it. However, we also need a way to see which components
are running, and which are waiting on a restart. Ideally we would also
see things like when each was started, how many times each has
restarted, and so on.

Can we "pause" components now? That is, stop something but not
permanently change the configuration?

> #792: Ability to add components to BIND 10 ‒ it allows adding a process to the
>       list of components which should be started.

Done! I've closed this.

> #793: Ability to remove components from BIND 10 ‒ similar

This too.

> #794: Flag components to run on BIND 10 startup ‒ we can add or remove them from
>       the list. If it is not there, it doesn't run. Or should there be a
>       „enabled“ option for a component to start it?

Well, this is somewhat related to the 'pause' idea above. So, the idea
may be to stop a service while you do something. For example, you may
need to disable a service while doing some maintenance.

But perhaps simply removing it is good enough?

> #1048: Traceback in zonemgr when Ctrl-C in bind10 ‒ I haven't seen a traceback
>        for quite some time and there are some kind of process groups now, so
>        ctrl+c isn't sent to the children directly, the boss handles the
>        shutdown now.

I don't think the main problem - the children not getting the shutdown
command - has been solved. OTOH the software is all different now, and I
suspect the problem is in the msgq itself. So, I've closed this one too,
and we can re-open it if we see the same behavior (or more likely create
a new ticket, since the output will be completely different).

> #514: Allow both the resolver and auth to run at the same time ‒ The can (and
>       could even before) run at the same time. But the ability to share a port
>       is still missing.

I think we need to leave this one open - although it's a Big Issue
rather than a tiny ticket really.

Thanks!

--
Shane