add support to deploy from local charms

Bug #1893800 reported by Felipe Reyes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
stsstack-bundles
Invalid
Wishlist
Unassigned

Bug Description

Add scripts to deploy using charms 2 years old (e.g. 18.05), these scripts should do something like this:

1) ./clone-all.sh --branch stable/18.05 --target /home/ubuntu/charms/

   Internally the script would do something like:

     cd $TARGET_DIR
     for CHARM in $LIST_OF_CHARMS; do
         git clone https://opendev.org/openstack/${CHARM}.git
         pushd $CHARM
         git checkout $BRANCH
         popd
     done

2) ./generate-bundle --charms-dir /home/ubuntu/charms/

    When --charms-dir is passed a new overlay is generated that contains lines like these:

    keystone:
      charm: /home/ubuntu/charms/keystone

Revision history for this message
Edward Hope-Morley (hopem) wrote :

Currently this can be achieved by doing generate-bundle without --run, modifying the bundles and overlays to use local copies and then re-running generate-bundle with --replay. A better solution would be to have something like a --charms-path option which if set will override all charms deployed. It would mean that you would have to always have all charms locally but if so then that should be easy enough. if the requirement is really to be able to deploy from a specific release then i think we should try to find a way to support that natively e.g. --charm-release 20.08 and then the generator goes and finds all the right versions (if they still exist).

Changed in stsstack-bundles:
importance: Undecided → Wishlist
Revision history for this message
Edward Hope-Morley (hopem) wrote :
Changed in stsstack-bundles:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.