Unfortunately, no. The only ways to use the old GUI now are:
What features are you looking for in the old GUI that are missing from the new Dashboard? Weâre currently planning our next cycle of work so weâll have an updated roadmap shortly and can take any feedback into consideration.
I want to simply run openstack base with one modification (ceph as directory NOT as /dev/sdb). It states in old config I can do so on old JAAS.ai dashboard. it would be 2 seconds to change in the old one, where I wouldnt have to download a YAML, modify it and get back to doing work.
I am not unwilling mind you, just it increases steps.
SO it is a sweeping change? I am running juju on a testbed, have it gapped and dont want to make it routable.
I think you might be able to build the old GUI from source and then copy it inside your gapped environment and run it there, but @hatch would have to let you know how to do that, as Iâve never done it before.
If you just want to be able to change config on your applications through a GUI you can use Juju Lens, which has both a web application and desktop application which you can use without having to deploy anything or change your controller at all. Itâs super easy to try out.
I love that concept app very much, but it is not successfully loading my controller/models. I will play with it a bit more!
UPDATE:
I am using conjure-up again for a run through to use (same of course as running the model directly). I have successfully modified the field in question. Now I am simply waiting for it to complete. I am in NO way criticizing. These tools are amazing and I am grateful.
Weâre going to be adding config management in an upcoming release of the dashboard. In the meantime you can use one of the other two UIâs or you can modify the config via the CLI juju config
The information on where to obtain the tarball should be available in the docs I think.
Finding the tarballs isnât trivial.
In fact, I canât find the dashboard at all at the moment? Iâm looking for 0.8.1 which I would like to use for upgrading, but I canât find any instruction where to find it.
In the Juju docs I find this: Juju | Access the dashboard and Juju | Use the dashboard . The former says you can access the dashboard by typing juju dashboard
. Iâve tried that but Iâm getting an error. Looking into it now.
Sorry it looks like there was an issue in our release process and the tags werenât being âreleasedâ. Iâve manually added it and you can now find 0.8.1 on github here.
Just so youâre aware, you can always build a release yourself from any commit by cloning the repo and running yarn && yarn generate-release-tarball
. Youâll also need Node 16 and Yarn installed but it doesnât install any global dependencies.
Thanx for this info. I do however miss this very useful information as part of tve official docs.
If the community had this information, it would be awesome!
@hatch - I have some input regarding control to access of juju actions. The interface plays a part her, which I would need to discuss with developers/designers. Better control over who can do what in relations to operating charms/units in models would provide a great interface to operational staff vs admins - significantly improving the use-case for juju and its dashboard.
In short - Iâm seeking to provide ACL:s for users to actions. I know this not yet supported by juju, but I would like to show you exactly the use-case for this and why it would matter to the ROI/TCO for businesses and thus the value-proposition of Juju.
Its going to take forever to write it down in text. So I rather have an online session to do this. Is this possible ?
Hey @erik-lonroth, sure thing. We can organise something this week or at any point later on, before the holiday break. Switching over to emails.
Absolutely⊠The dashboard is promising, but I experience alot of crashes. Especially when trying to use the ârun actionâ feature when I get thisâŠ
After this I get logged out from the interface.
Iâm getting this both on 0.8.1 and 0.9.0 âŠ
Sorry about that, Iâm actively trying to track down that actions bug.
Can I upgrade to something that removes this bug?
I try to follow the instructions in the repo, but Iâm not sure how to install and get yarn + node setup.