Cluster page no longer shows whether the cluster is connected or not.

[Andres Rodriguez]

In the latest trunk, the Cluster's page no longer shows whether the Cluster Controller is connected to the cluster or not. There's a new state which shows whether the Cluster is in-sync or out-of-sync but that's for the images.

The Cluster Listing page should show whether the clusters are *connected* or no (so the UI for that needs to be reverted), and it has to show whether the *images* are in-sync or not (Instead of state).

[Blake Rouse (blake-rouse)]

If the cluster is not connected it shows not connected. As its unable to
determine if its in sync or not. If we were to show both then the
information would be duplicated. Because we cannot say the cluster is out
of sync if disconnected because there is no way to tell.
On Sep 27, 2014 12:45 PM, "Andres Rodriguez" <email address hidden>
wrote:

> Public bug reported:
>
> In the latest trunk, the Cluster's page no longer shows whether the
> Cluster Controller is connected to the cluster or not. There's a new
> state which shows whether the Cluster is in-sync or out-of-sync but
> that's for the images.
>
> The Cluster Listing page should show whether the clusters are
> *connected* or no (so the UI for that needs to be reverted), and it has
> to show whether the *images* are in-sync or not (Instead of state).
>
> ** Affects: maas
> Importance: Critical
> Assignee: Blake Rouse (blake-rouse)
> Status: New
>
>
> ** Tags: ui
>
> ** Changed in: maas
> Importance: Undecided => Critical
>
> ** Changed in: maas
> Assignee: (unassigned) => Blake Rouse (blake-rouse)
>
> ** Tags added: ui
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1374793
>
> Title:
> Cluster page no longer shows whether the cluster is connected or not.
>
> Status in MAAS:
> New
>
> Bug description:
> In the latest trunk, the Cluster's page no longer shows whether the
> Cluster Controller is connected to the cluster or not. There's a new
> state which shows whether the Cluster is in-sync or out-of-sync but
> that's for the images.
>
> The Cluster Listing page should show whether the clusters are
> *connected* or no (so the UI for that needs to be reverted), and it
> has to show whether the *images* are in-sync or not (Instead of
> state).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1374793/+subscriptions
>

[Andres Rodriguez (andreserl)]

I understand that and it is a valid point, however, I do strongly believe we need to be able to differentiate two things:

1. Whether the cluster is actually connected or not
2. Whether the images are synced or not.

We might have cluster controllers with Synced images, but for some reason, the cluster might have gotten disconnected, but the images are still there and synced.

In other words, the *current* state of the Cluster can be ./ (Connected) or X (Disconnected), however the last known Image can be *synced* or *out-of-sync* regardless of the Cluster. So a Cluster can be disconnected, but the last known state of the images is *synced*.

Does that make sense?

[Blake Rouse (blake-rouse)]

RPC is required to determine if the cluster is in sync. What your speaking
of is caching this information. This is bad idea because if the cluster is
disconnected then the information can be incorrect, as the images on the
region might have changed when the cluster was disconnected or the files on
the cluster where removed.

If you want to show two different columns on the cluster list page, then if
the cluster is disconnected we could show unknown or "-" meaning unknown,
but not as ugly. Would this work?
On Sep 27, 2014 1:10 PM, "Andres Rodriguez" <email address hidden> wrote:

> I understand that and it is a valid point, however, I do strongly
> believe we need to be able to differentiate two things:
>
> 1. Whether the cluster is actually connected or not
> 2. Whether the images are synced or not.
>
> We might have cluster controllers with Synced images, but for some
> reason, the cluster might have gotten disconnected, but the images are
> still there and synced.
>
> In other words, the *current* state of the Cluster can be ./ (Connected)
> or X (Disconnected), however the last known Image can be *synced* or
> *out-of-sync* regardless of the Cluster. So a Cluster can be
> disconnected, but the last known state of the images is *synced*.
>
> Does that make sense?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1374793
>
> Title:
> Cluster page no longer shows whether the cluster is connected or not.
>
> Status in MAAS:
> New
>
> Bug description:
> In the latest trunk, the Cluster's page no longer shows whether the
> Cluster Controller is connected to the cluster or not. There's a new
> state which shows whether the Cluster is in-sync or out-of-sync but
> that's for the images.
>
> The Cluster Listing page should show whether the clusters are
> *connected* or no (so the UI for that needs to be reverted), and it
> has to show whether the *images* are in-sync or not (Instead of
> state).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1374793/+subscriptions
>

[Andres Rodriguez (andreserl)]

RPC is indeed required to determine whether we have images or not. However, what I'm requesting is not to cache the information. Looking at the new UI changes (sync, out of sync) does not give me any idea of what is in sync and what isn't. I want to be able to see when the node is connected and whether the images have been synced. Looking at it I can't really determine this. Keep in mind that while we know what's going on, the end user isn't.

This is way we need to be clear in the UI as to what we represent. This is why I believe we should show:

1. Whether the cluster controller is connected.
2. Whether we have images or not.

ANd this information needs to be clear enough for an end-user to understand what's going on.

Thanks

[Andres Rodriguez (andreserl)]

This is part of transparency
On Sep 28, 2014 1:55 PM, "Andres Rodriguez" <email address hidden> wrote:

> RPC is indeed required to determine whether we have images or not.
> However, what I'm requesting is not to cache the information. Looking at
> the new UI changes (sync, out of sync) does not give me any idea of what
> is in sync and what isn't. I want to be able to see when the node is
> connected and whether the images have been synced. Looking at it I can't
> really determine this. Keep in mind that while we know what's going on,
> the end user isn't.
>
> This is way we need to be clear in the UI as to what we represent. This
> is why I believe we should show:
>
> 1. Whether the cluster controller is connected.
> 2. Whether we have images or not.
>
> ANd this information needs to be clear enough for an end-user to
> understand what's going on.
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1374793
>
> Title:
> Cluster page no longer shows whether the cluster is connected or not.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1374793/+subscriptions
>

[Raphaël Badin (rvb)]

Like Andres said, this is only a presentation problem: even if displaying that the images are in sync *implies* that the cluster is connected because that's how we fetched the information in the first place: *the end user doesn't know that*.