| 2024-04-10 10:43:43 |
Alex Lutay |
bug |
|
|
added bug |
| 2024-04-10 10:44:10 |
Alex Lutay |
description |
Hi,
This is UX improvement report. |
Updating... pressed enter tooooo early... soryy... WIP
Hi,
This is UX improvement report. |
|
| 2024-04-10 10:44:50 |
Alex Lutay |
summary |
juju status' highlight outdated model on new controller |
Visualize outdated model version on the new controller in 'juju status' |
|
| 2024-04-10 10:49:18 |
Alex Lutay |
description |
Updating... pressed enter tooooo early... soryy... WIP
Hi,
This is UX improvement report. |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available. TL;DR:
Controller Model User Access Cloud/Region Models Nodes HA Version
lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
ubuntu@juju340:~$ juju status
Model Controller Cloud/Region Version ...
maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue if controller ls already new 3.4.2
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:49:50 |
Alex Lutay |
description |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available. TL;DR:
Controller Model User Access Cloud/Region Models Nodes HA Version
lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
ubuntu@juju340:~$ juju status
Model Controller Cloud/Region Version ...
maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue if controller ls already new 3.4.2
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
Controller Model User Access Cloud/Region Models Nodes HA Version
lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
ubuntu@juju340:~$ juju status
Model Controller Cloud/Region Version ...
maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue if controller ls already new 3.4.2
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:50:47 |
Alex Lutay |
description |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
Controller Model User Access Cloud/Region Models Nodes HA Version
lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
ubuntu@juju340:~$ juju status
Model Controller Cloud/Region Version ...
maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue if controller ls already new 3.4.2
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:51:18 |
Alex Lutay |
description |
Hi,
This is UX improvement report based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:52:00 |
Alex Lutay |
description |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
<pre>
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
<pre/>
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:52:09 |
Alex Lutay |
description |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
<pre>
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
<pre/>
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-10 10:53:34 |
Alex Lutay |
description |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot! This is request to improve it a bit further if controller is already upgraded and each model owner should upgrade their models (when owners they are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
Hi,
This is UX improvement based on the real experience with Maksim Beliaev today.
The latest `juju status` indicates the outdated controller/model version using the yellow color if the new juju is available (juju 3.4+ AFAIK, at least 3.2+). TL;DR:
> > juju controllers
> Controller Model User Access Cloud/Region Models Nodes HA Version
> lxd* maksim admin superuser localhost/localhost 2 1 none 3.4.1 # 3.4.1 is yellow here
> microk8s lisbon admin superuser microk8s/localhost 2 - - 3.4.2 # 3.4.2 is white here
This is a very nice UX which help a lot!
This is request to improve it a bit further IF controller has been upgraded already AND the model is still old.
The each model owner should upgrade their models independently on ProdStack6 (when owners are ready).
Otherwise Maksim has requested IS team controller upgrade not seeing controller is already new.
Proposal:
> > juju status
> Model Controller Cloud/Region Version ...
> maksim lxd localhost/localhost 3.4.1 ... # print 3.4.1 in blue IF controller ls already new/3.4.2+
It will show model owners they can execute 'juju upgrade-model' anytime they are ready.
Tnx! |
|
| 2024-04-11 08:49:30 |
Joseph Phillips |
juju: status |
New |
Triaged |
|
| 2024-04-11 08:49:33 |
Joseph Phillips |
juju: importance |
Undecided |
Wishlist |
|
| 2024-04-11 08:50:00 |
Joseph Phillips |
tags |
|
bitesize status usability |
|
