On Tue, Jan 29, 2013 at 5:09 PM, Iustin Pop <[email protected]> wrote:
> On Tue, Jan 29, 2013 at 11:49:53AM +0100, Michele Tartara wrote: > > Add information about what class a data collector is part of, > > what is the general status of the report, an optional explicative > message. > > > > Also, the DRBD data collector is changed accordingly. > > Are these detailed in the design doc? I don't see them right now. > They are in the version that we should discuss with Arthur, whose link I sent on the mailing list a couple of weeks ago. Given that whatever format I use is temporary until we have a design document with a final approval, I decided to send this anyway, so at least I can export most of the information I already have and I think should be there in the end. But if you think that it's better to wait for the design document to be finalized, this patch can wait. > The reason I ask is because I'm not sure about: > > > +-- | The possible classes a data collector can belong to. > > +data CollectorClass = Instance | Storage | Daemon | Hypervisor > > + deriving (Show, Eq) > > and > > > +-- | The possible statuses of a data collector. > > +data CollectorStatus = DcOk | DcBad | DcInfo | DcUnknown deriving > (Show, Eq) > > in the sense that are those the correct/only classes, what does it > Daemon, what does DcBad vs DcInfo mean, etc. > Yes, it's all explained in the document, and these are the only possibilities, unless we decide to add more of them afterwards. Thanks, Michele -- You received this message because you are subscribed to the Google Groups "ganeti-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
