Problem: Missing easy way to deploy v1.7.0 of Archivematica

[scollazo]

Inspired by @jhsimpson in artefactual-labs/ansible-archivematica-src#191:

Now that there is an official v1.7.0 tag in Archivematica, we need a way to make sure that this repo has an easy way to install that version.

This could be done with a stable/1.7.x branch in this repo, and a v1.7.0 tag?

[sevein]

Can't this be done from master?

[sevein]

We're kind of doing this already I think.
We could even have a single playbooks/archivematica with a bunch of parameters.

[jraddaoui]

I kind of like @sevein's edited idea of having versioned playbooks:

playbooks/archivematica-1.7-xenial
playbooks/archivematica-1.7-trusty
playbooks/archivematica-1.7-centos7
playbooks/archivematica-1.x-xenial
playbooks/archivematica-1.x-trusty
playbooks/archivematica-1.x-centos7

At least I prefer that to have a stable/1.7.x branch in here, where we have playbooks for other applications. The list will grow as time passes but we could drop old versions support as we move on. Having versioned playbooks will also help in the Binder playbooks I'm trying to add in here:

#67

[jhsimpson]

I don't like having versioned playbooks like this. I would prefer to have a single playbook with parameters for os and Archivematica version. I think multiple playbooks is harder to maintain isn't it? Not very DRY. Also a more confusing experience for new users.

…

On Tue, May 15, 2018, 07:26 José Raddaoui Marín ***@***.***> wrote: I kind of like @sevein <https://github.com/sevein>'s edited idea of having versioned playbooks: playbooks/archivematica-1.7-xenial playbooks/archivematica-1.7-trusty playbooks/archivematica-1.7-centos7 playbooks/archivematica-1.x-xenial playbooks/archivematica-1.x-trusty playbooks/archivematica-1.x-centos7 At least I prefer that to have a stable/1.7.x branch in here, where we have playbooks for other applications. The list will grow as time passes but we could drop old versions support as we move on. Having versioned playbooks will also help in the Binder playbooks I'm trying to add in here: #67 <#67> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#69 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC8O3QDQL1DDAts-TgFkDPl3x8447Sy4ks5tyuWlgaJpZM4TyV2F> .

[scollazo]

@mamedin and @hakamine are working on a an upgrade of the percona role, so once it works on CentOS, we should be able to install Archivematica using the same playbook, but different vars.

The scheme should be like this:

├── archivematica-1.7
│   ├── requirements.yml
│   ├── singlenode.yml
│   ├── vars-centos.yml
│   ├── vars-trusty.yml
│   └── vars-xenial.yml
└── archivematica-qa
    ├── requirements.yml
    ├── singlenode.yml
    ├── vars-centos.yml
    ├── vars-trusty.yml
    └── vars-xenial.yml