Node status enum starts with a false statement

[Christian Reis]

Does the below make sense?

class NODE_STATUS:
    """The vocabulary of a `Node`'s possible statuses."""
    # A node starts out as READY.
    DEFAULT = 0

[Christian Reis (kiko)]

Oh, even wierder if I look deeper:

class NODE_STATUS:
    """The vocabulary of a `Node`'s possible statuses."""
    # A node starts out as READY.
    DEFAULT = 0

    #: The node has been created and has a system ID assigned to it.
    NEW = 0

[Raphaël Badin (rvb)]

DEFAULT is an "alias" for NEW (which makes sense). What doesn't make sense is the "# A node starts out as READY." sentence.

[Christian Reis (kiko)]

Right, that's what I meant to imply with my comment. Could you fix this in a drive-by?

[Christian Reis (kiko)]

BTW, the node statuses aren't documented anywhere in the API docs, but the end-user of the API kind of needs to know them and the state machine, don't they?

[Raphaël Badin (rvb)]

> BTW, the node statuses aren't documented anywhere in the API docs, but the end-user of the API kind of needs to know them
> and the state machine, don't they?

True, this is the related to bug 1376144.

[Raphaël Badin (rvb)]

Actually, the statuses are documented: https://maas.ubuntu.com/docs/enum.html.

Maybe we could make this information more visible but that should probably be part of a general refactoring of the documentation.