Why some charms are not maintained to use current series?

Hi dear,

I was seeing the same charms present on store, that are very useful, are not anymore upgraded like Zappix.
I want to know if there is a way to make that available also for the last version of ubuntu, it is easy or hard to make that? Thanks

I think that it is often not too big a deal to upgrade a charm for the latest Ubuntu. It mostly has to do with updating the package versions for the new version of Ubuntu and then testing it to make sure it works.

If it is an Open Source charm then it should be simple enough to modify and build the charm locally to test the changes, at which point you could submit a pull request for the update, if the maintainer is still active.

I think Canonical could also help facilitate the publication of a replacement charm into the same namespace if the original author is truly inactive etc. If you’ve updated a fork of the charm and want it published, ask here and we can help.

1 Like

do you know if there is an guide that explain how to make that?
I mean, to take an old charm and try to upgrade it of making it available on the last release of ubuntu, because I see that only some charm or bundle can be used on u18.04 LTS.

Juju charms encapsulate and package knowledge about how to set up specific workloads. The charm declares in metadata.yaml what series it supports, but the exact enablement work (setup, config, packages to install etc etc) to have something able to run on a newer Ubuntu series would be dependent on the workload.

There’s some generic charm writing doc here. The simplest thing that can be done is to add a new series to the charm’s list of supported series in metadata.yaml, eg

series:
    - xenial
    - trusty
    - bionic
    - focal

Sometimes that’s all that’s needed. But it depends on the workload.

To expand on that slightly, you can download the .zip file of the charm and edit its source code. Once you’re happy, you’re welcome to re-publish it with your own user account.

I’ll try that, but I think that is not very easy to rebuild a charm or a bundle just to modify a file :slight_smile: … I try and in case I ask you a help!

1 Like

I was trying to deploy wordpress on my lab to make some test, the charm is gone well

ubuntu@openstack-aio:~$ juju status
Model    Controller  Cloud/Region           Version  SLA          Timestamp
default  msk         microstack/microstack  2.7.4    unsupported  17:59:14Z

App        Version  Status  Scale  Charm      Store       Rev  OS      Notes
wordpress           active      1  wordpress  jujucharms    0  ubuntu  exposed

Unit          Workload  Agent  Machine  Public address  Ports   Message
wordpress/0*  active    idle   0        10.20.20.133    80/tcp  

Machine  State    DNS           Inst id                               Series  AZ    Message
0        started  10.20.20.133  520c6941-423f-4d09-8f3d-290125c11754  bionic  nova  ACTIVE

but I’ve not understand if I’ve to deploy also mysql and apache/nginx .to use wordpress correctly…
I tried to find that and nginx works until trusty, apache2 is fine and mysql ??
My opinion if I’ve to use Juju in this way in a production environment is very hard to create a project :slight_smile:

Yes, that’s true today.

Thankfully if we can create a community around the charm, the process will be simplified. @maaudet has proven that Juju can be very helpful with web technologies: