"Deployed" and "Deploying" are too similar

Alternatively it would be nice to see the OS, to perhaps we'd list the image there instead of "Deployed". So Ubuntu, CentOS6 etc.

Hi Mark,

We have a concern about changing 'Deployed' to 'OS/Release' because in custom images, that wouldn't be that nice, as it allows users to define the name of the image, which can be pretty much anything they want and that may just break the UI as a whole.

However, we have added two things:

1. Spinner for "-ing" actions, which allows you to differentiate when a machine is "Deploying" vs "Deployed"
2. Added a filter for OS/Release.

In the meantime we can try if this works. Otherwise we can explore some other name changes.

Thanks.

"custom-image" would be a fixed-length and useful version.
"ubuntu/trusty" and "centos/v7" would be what I'd expect elsewhere.

I like the spinner, thank you, but please push on with the image details.

Mark

On 07/10/16 06:23, Andres Rodriguez wrote:
> Hi Mark,
>
> We have a concern about changing 'Deployed' to 'OS/Release' because in
> custom images, that wouldn't be that nice, as it allows users to define
> the name of the image, which can be pretty much anything they want and
> that may just break the UI as a whole.
>
> However, we have added two things:
>
> 1. Spinner for "-ing" actions, which allows you to differentiate when a machine is "Deploying" vs "Deployed"
> 2. Added a filter for OS/Release.
>
> In the meantime we can try if this works. Otherwise we can explore some
> other name changes.

Mark,

Can you take a look at the screenshots to see if you like how it looks?

http://imgur.com/a/f92DG

Thanks.

That's pretty cool, I thought it would just say "Deploying" then
"ubuntu/trusty", but I like what you have. Only issue is width of the
column, what do you think?

Mark

The remaining columns to the right of status can collapse a lot, so I do not worry about space for Ubuntu or CentOS images, but for custom images it could become a problem. I think we can try it out and see how it performs across different screen sizes and if its a problem either revert it or try some other ways to collapse the other columns on smaller screens.

Perhaps for custom images, require a one-word name, and then put
"custom/name" in the column. So ubuntu/trusty and custom/foo.

Mark

@sabdfl, are you saying you want the "Status" column to just say "ubuntu/trusty", or is "Deployed ubuntu/trusty" okay?

We discussed this as a team the other day after trying both ways, and decided that since "ubuntu" isn't really a "Status", it looked better with the "Deployed" label first. Do you think that thinking is too rigid?

Personally I like having the numeric version there too; not everyone may be familiar enough with Ubuntu to know that Xenial > Trusty, etc. (post-Z that will be more confusing than today, assuming the user at least knows it's alphabetic.)

We present the OS when your going to start a deployment as "Ubuntu 16.04 LTS" so I would not want the listing to show something different then the selection. The OS filter also shows "Ubuntu 16.04 LTS" as the name, and we have plenty of room in those areas to show the full name. Custom names even in the simple case could be long but again rare "custom/my-custom-image-with-name-too-long".

I will land the branch and we can adjust from there to see how it looks with some user testing.

Mike I think the version number is a good idea. Perhaps we could update
streams to reflect a version after the release (technically it's yakkety
until its out then it is 16.10).

Also, I prefer tight statuses so I would prefer ubuntu/xenial or
ubuntu/16.04 to "Deployed Ubuntu 16.04 LTS" in that column. Take a look
with a designer and tell me what you think. Our audience are not fluffy
types :)

Mark

Hello Mark, or anyone else affected,

Accepted maas into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/maas/2.1.0+bzr5480-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hi Mark,

We will take a look and fix this for the next iteration.

The verification of the Stable Release Update for maas has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.