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

AM 1.7 upgrades #123

Merged
merged 27 commits into from
Aug 8, 2017
Merged

AM 1.7 upgrades #123

merged 27 commits into from
Aug 8, 2017

Conversation

sevein
Copy link
Member

@sevein sevein commented Jul 27, 2017

This needs #681 and #682 (AM) and artefactual/archivematica-storage-service#217 (SS).

It includes the changes that Helen did in #120.

I'd also like to address #678 here but can be done in a separate PR.

Reminders (once merged):

  • File issue about problems with upgrade path
  • Update deploy-pub and getting started docs
  • Document environment variables
  • Support automated user creation

This includes details related to mod-wsgi and uwsgi. We want to remove surfaces
and stick with Nginx + Gunicorn.
@sevein sevein added the Status: in progress Issue that is currently being worked on. Waffle label. label Jul 27, 2017
@sevein sevein changed the title AM 1.7 upgrades 🚧 AM 1.7 upgrades Jul 27, 2017
@scollazo
Copy link
Contributor

I think that keeping the .j2 extension for templates is a good idea, so we are aware that they support jinja2 templates inside.

@sevein sevein force-pushed the dev/am-17-upgrades branch 4 times, most recently from dfb77da to 5b45b50 Compare August 1, 2017 00:02
This is not going to be an option anymore. We may still want to offer users
the option to disable this feature but definitely not at operations layer.
This was replaced by a role.
@sevein sevein removed the Status: in progress Issue that is currently being worked on. Waffle label. label Aug 1, 2017
@sevein sevein force-pushed the dev/am-17-upgrades branch 2 times, most recently from b216271 to cb34332 Compare August 1, 2017 00:23
@helenst
Copy link
Contributor

helenst commented Aug 2, 2017

I pushed a small fix to this branch, as the provisioner was failing trying to locate the upstart script for storage service.

@sevein sevein self-assigned this Aug 3, 2017
SS_DB_USER: ""
# Not mandatory:
SS_GUNICORN_BIND: "127.0.0.1:8002"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice AM / SS back end ports are swapped from what they were previously 8001 <-> 8002. Makes sense to me I guess, to have the AM port 'first'. Although caused some confusion as I sometimes kill the gunicorn service and replace it with a runserver for easier debugging! Is there anywhere these ports are documented that will need to be changed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't mea to change them, that was an accident! I'll rever that. Thank you!

@jrwdunham
Copy link
Contributor

In order to get this to work, I had to insert archivematica_src_am_wait_mysql: "yes" into vars-singlenode-qa.yml (using Trusty). Should something like this be in defaults/main.yml?

@sevein
Copy link
Member Author

sevein commented Aug 3, 2017

In order to get this to work, I had to insert archivematica_src_am_wait_mysql: "yes" into vars-singlenode-qa.yml (using Trusty). Should something like this be in defaults/main.yml?

That was a typo, fixed now, thanks @jrwdunham.

@helenst
Copy link
Contributor

helenst commented Aug 4, 2017

I've been using this all day and it seems to be working well now 👍

Copy link
Member

@jhsimpson jhsimpson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this on windows, using @minusdavid's deploy-pub pr artefactual/deploy-pub#39
works good for me
👍

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

Successfully merging this pull request may close these issues.

5 participants