Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
scollazo opened this issue May 4, 2018 · 5 comments
Open

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

scollazo opened this issue May 4, 2018 · 5 comments
Labels

Comments

@scollazo
Copy link
Member

scollazo commented May 4, 2018

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?

@scollazo scollazo added the AM17 label May 4, 2018
@sevein
Copy link
Member

sevein commented May 14, 2018

Can't this be done from master?

@sevein
Copy link
Member

sevein commented May 14, 2018

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

@jraddaoui
Copy link
Contributor

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
Copy link
Member

jhsimpson commented May 15, 2018 via email

@scollazo
Copy link
Member Author

scollazo commented May 15, 2018

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants