Review and merge the old capomastro-deploy branch code with the new charm

Bug #1385221 reported by Caio Begotti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Capomastro
Fix Released
Low
Caio Begotti

Bug Description

If it still makes sense... need to check it first anyway because that's all legacy stuff.

Caio Begotti (caio1982)
Changed in capomastro:
assignee: nobody → Caio Begotti (caio1982)
Caio Begotti (caio1982)
Changed in capomastro:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Caio Begotti (caio1982) wrote :

The old branch is lp:~ce-infrastructure/bygmester/capomastro-deploy/ and I think most if not all of it is already explained in the README file of the new Capomastro charm. What it basically does as I can see is to automate the actual deployment commands present in the new README anyway.

I think working on #1389669 makes more sense as the rest of this capomastro-deploy branch would be made obsolete by it. I mean, we can still work on this bug and rewrite the deploy helpers, but IMHO it would have little use in the long term. The only reason to work on this is to acquire knowledge on how David and Kevin did do things to hook it up with haproxy etc.

Revision history for this message
Caio Begotti (caio1982) wrote :

Also, our understanding of what needs to be run by a potential deploy script can change after an initial review of our charms by IS, which I'd rather request as soon as we can.

Revision history for this message
Caio Begotti (caio1982) wrote :

I've got a branch that I am using to clean up some bits from the old deployment scripts and keep the charm configs but I am still not sure how useful it's going to be for us. Perhaps it will be to IS? Anyway, it's in at lp:~ce-infrastructure/capomastro/deploy-cleanup and I'm currently testing it in a new environment so other teammates can use the branch to come up with a whole Capomastro environment if they ever need it too.

Caio Begotti (caio1982)
Changed in capomastro:
status: Confirmed → Fix Released
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.