Add Let's Encrypt to integration playbook #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…from-cypress-install Remove insights from Cypress
Stop reusing ECOMMERCE_DEFAULT_DB_NAME for corresponding user. Use ECOMMERCE_DATABASES.default.USER instead.
edxlocal: Fix "String ... is too long for username" error.
Let's Encrypt role and config settings added to integration playbook, to automatically bring up integration test servers with https.
haikuginger
force-pushed
the
integration
branch
from
29f4248
to
3f77024
Compare
pomegranited
pushed a commit
that referenced
this pull request
Sep 3, 2018
*commit message #1: Optionally use aws/openstack role in edx_sandbox/edx-stateless. This adds two new variables to common_vars: - COMMON_ENABLE_AWS_INTEGRATION - COMMON_ENABLE_OPENSTACK_INTEGRATION They are both set to False by default. When set to True, the corresponding role (aws/openstack) will be automatically included in edx_sandbox.yml and edx-stateless.yml playbooks. (cherry picked from commit ae0a983) *commit message #2:* Make aws and openstack roles create their own directories. The vhost role used to create directories required by the aws and openstack roles based on the value of the VHOST_NAME variable, but that turned out to be problematic (see https://github.com/edx/configuration/pull/3519). Remove the VHOST_NAME variable and make each aws and openstack role responsible for creating its own directories. (cherry picked from commit 494a173) *commit message #3:* Make S3 and SWIFT log syncing independent. While COMMON_OBJECT_STORE_LOG_SYNC and related variables are still supported, this patch offers a finer grained control over tracking log syncing. Sometimes you want to host edX on openstack (and therefore need to run the openstack role), but you still want to sync tracking logs to S3, so it does not make sense to tie the choice of log sync store to the presence of either aws or openstack role in the playbook. (cherry picked from commit 4593743) *commit message #4:* Let edxapp role conditionally install openstack requirements. Based on the value of COMMON_ENABLE_OPENSTACK_INTEGRATION. Installing requirements from the openstack role created role ordering issues where openstack role had to run after the edxapp role so that the required folders and the virtual environment are already created, BUT edxapp migrations can also depend on the default file storage, which will fail when using openstack storage if openstack requirements haven't been installed yet. Letting edxapp role install the requirements solves this problem. (cherry picked from commit 8246496) *commit message #5:* Move aws and openstack roles above edxapp role. If the aws role runs after the edxapp role, it can fail to install the s3cmd binary into /usr/local/bin/, because edxapp role already installs the s3cmd apt package, which creates binaries in /usr/bin. (cherry picked from commit e91ff3e) *commit message #6:* Remove AWS-specific code to set MTU. We run the AWS role on OpenStack to get the logs synced to S3, but we don't need the MTU settings. (cherry picked from commit 01a0d58)
pomegranited
pushed a commit
that referenced
this pull request
Sep 3, 2018
*commit message #1: Optionally use aws/openstack role in edx_sandbox/edx-stateless. This adds two new variables to common_vars: - COMMON_ENABLE_AWS_INTEGRATION - COMMON_ENABLE_OPENSTACK_INTEGRATION They are both set to False by default. When set to True, the corresponding role (aws/openstack) will be automatically included in edx_sandbox.yml and edx-stateless.yml playbooks. (cherry picked from commit ae0a983) *commit message #2:* Make aws and openstack roles create their own directories. The vhost role used to create directories required by the aws and openstack roles based on the value of the VHOST_NAME variable, but that turned out to be problematic (see https://github.com/edx/configuration/pull/3519). Remove the VHOST_NAME variable and make each aws and openstack role responsible for creating its own directories. (cherry picked from commit 494a173) *commit message #3:* Make S3 and SWIFT log syncing independent. While COMMON_OBJECT_STORE_LOG_SYNC and related variables are still supported, this patch offers a finer grained control over tracking log syncing. Sometimes you want to host edX on openstack (and therefore need to run the openstack role), but you still want to sync tracking logs to S3, so it does not make sense to tie the choice of log sync store to the presence of either aws or openstack role in the playbook. (cherry picked from commit 4593743) *commit message #4:* Let edxapp role conditionally install openstack requirements. Based on the value of COMMON_ENABLE_OPENSTACK_INTEGRATION. Installing requirements from the openstack role created role ordering issues where openstack role had to run after the edxapp role so that the required folders and the virtual environment are already created, BUT edxapp migrations can also depend on the default file storage, which will fail when using openstack storage if openstack requirements haven't been installed yet. Letting edxapp role install the requirements solves this problem. (cherry picked from commit 8246496) *commit message #5:* Move aws and openstack roles above edxapp role. If the aws role runs after the edxapp role, it can fail to install the s3cmd binary into /usr/local/bin/, because edxapp role already installs the s3cmd apt package, which creates binaries in /usr/bin. (cherry picked from commit e91ff3e) *commit message #6:* Remove AWS-specific code to set MTU. We run the AWS role on OpenStack to get the logs synced to S3, but we don't need the MTU settings. (cherry picked from commit 01a0d58) *commit message #7:* Fix missing playbooks/roles/vhost/default/main.yml
Agrendalath
pushed a commit
that referenced
this pull request
Sep 19, 2018
*commit message #1: Optionally use aws/openstack role in edx_sandbox/edx-stateless. This adds two new variables to common_vars: - COMMON_ENABLE_AWS_INTEGRATION - COMMON_ENABLE_OPENSTACK_INTEGRATION They are both set to False by default. When set to True, the corresponding role (aws/openstack) will be automatically included in edx_sandbox.yml and edx-stateless.yml playbooks. (cherry picked from commit ae0a983) *commit message #2:* Make aws and openstack roles create their own directories. The vhost role used to create directories required by the aws and openstack roles based on the value of the VHOST_NAME variable, but that turned out to be problematic (see https://github.com/edx/configuration/pull/3519). Remove the VHOST_NAME variable and make each aws and openstack role responsible for creating its own directories. (cherry picked from commit 494a173) *commit message #3:* Make S3 and SWIFT log syncing independent. While COMMON_OBJECT_STORE_LOG_SYNC and related variables are still supported, this patch offers a finer grained control over tracking log syncing. Sometimes you want to host edX on openstack (and therefore need to run the openstack role), but you still want to sync tracking logs to S3, so it does not make sense to tie the choice of log sync store to the presence of either aws or openstack role in the playbook. (cherry picked from commit 4593743) *commit message #4:* Let edxapp role conditionally install openstack requirements. Based on the value of COMMON_ENABLE_OPENSTACK_INTEGRATION. Installing requirements from the openstack role created role ordering issues where openstack role had to run after the edxapp role so that the required folders and the virtual environment are already created, BUT edxapp migrations can also depend on the default file storage, which will fail when using openstack storage if openstack requirements haven't been installed yet. Letting edxapp role install the requirements solves this problem. (cherry picked from commit 8246496) *commit message #5:* Move aws and openstack roles above edxapp role. If the aws role runs after the edxapp role, it can fail to install the s3cmd binary into /usr/local/bin/, because edxapp role already installs the s3cmd apt package, which creates binaries in /usr/bin. (cherry picked from commit e91ff3e) *commit message #6:* Remove AWS-specific code to set MTU. We run the AWS role on OpenStack to get the logs synced to S3, but we don't need the MTU settings. (cherry picked from commit 01a0d58) *commit message #7:* Fix missing playbooks/roles/vhost/default/main.yml
giovannicimolin
pushed a commit
that referenced
this pull request
Jan 21, 2019
* Add the 'analytics_api' nginx site * Fix issue with rubygems 3.0.0 by pinning it to 2.7.8 * Remove demo role from the edx_sandbox.yml playbook
jcdyer
pushed a commit
that referenced
this pull request
Jan 25, 2019
*commit message #1: Optionally use aws/openstack role in edx_sandbox/edx-stateless. This adds two new variables to common_vars: - COMMON_ENABLE_AWS_INTEGRATION - COMMON_ENABLE_OPENSTACK_INTEGRATION They are both set to False by default. When set to True, the corresponding role (aws/openstack) will be automatically included in edx_sandbox.yml and edx-stateless.yml playbooks. (cherry picked from commit ae0a983) *commit message #2:* Make aws and openstack roles create their own directories. The vhost role used to create directories required by the aws and openstack roles based on the value of the VHOST_NAME variable, but that turned out to be problematic (see https://github.com/edx/configuration/pull/3519). Remove the VHOST_NAME variable and make each aws and openstack role responsible for creating its own directories. (cherry picked from commit 494a173) *commit message #3:* Make S3 and SWIFT log syncing independent. While COMMON_OBJECT_STORE_LOG_SYNC and related variables are still supported, this patch offers a finer grained control over tracking log syncing. Sometimes you want to host edX on openstack (and therefore need to run the openstack role), but you still want to sync tracking logs to S3, so it does not make sense to tie the choice of log sync store to the presence of either aws or openstack role in the playbook. (cherry picked from commit 4593743) *commit message #4:* Let edxapp role conditionally install openstack requirements. Based on the value of COMMON_ENABLE_OPENSTACK_INTEGRATION. Installing requirements from the openstack role created role ordering issues where openstack role had to run after the edxapp role so that the required folders and the virtual environment are already created, BUT edxapp migrations can also depend on the default file storage, which will fail when using openstack storage if openstack requirements haven't been installed yet. Letting edxapp role install the requirements solves this problem. (cherry picked from commit 8246496) *commit message #5:* Move aws and openstack roles above edxapp role. If the aws role runs after the edxapp role, it can fail to install the s3cmd binary into /usr/local/bin/, because edxapp role already installs the s3cmd apt package, which creates binaries in /usr/bin. (cherry picked from commit e91ff3e) *commit message #6:* Remove AWS-specific code to set MTU. We run the AWS role on OpenStack to get the logs synced to S3, but we don't need the MTU settings. (cherry picked from commit 01a0d58) *commit message #7:* Fix missing playbooks/roles/vhost/default/main.yml
toxinu
pushed a commit
that referenced
this pull request
Jun 9, 2019
*commit message #1: Optionally use aws/openstack role in edx_sandbox/edx-stateless. This adds two new variables to common_vars: - COMMON_ENABLE_AWS_INTEGRATION - COMMON_ENABLE_OPENSTACK_INTEGRATION They are both set to False by default. When set to True, the corresponding role (aws/openstack) will be automatically included in edx_sandbox.yml and edx-stateless.yml playbooks. (cherry picked from commit ae0a983) *commit message #2:* Make aws and openstack roles create their own directories. The vhost role used to create directories required by the aws and openstack roles based on the value of the VHOST_NAME variable, but that turned out to be problematic (see https://github.com/edx/configuration/pull/3519). Remove the VHOST_NAME variable and make each aws and openstack role responsible for creating its own directories. (cherry picked from commit 494a173) *commit message #3:* Make S3 and SWIFT log syncing independent. While COMMON_OBJECT_STORE_LOG_SYNC and related variables are still supported, this patch offers a finer grained control over tracking log syncing. Sometimes you want to host edX on openstack (and therefore need to run the openstack role), but you still want to sync tracking logs to S3, so it does not make sense to tie the choice of log sync store to the presence of either aws or openstack role in the playbook. (cherry picked from commit 4593743) *commit message #4:* Let edxapp role conditionally install openstack requirements. Based on the value of COMMON_ENABLE_OPENSTACK_INTEGRATION. Installing requirements from the openstack role created role ordering issues where openstack role had to run after the edxapp role so that the required folders and the virtual environment are already created, BUT edxapp migrations can also depend on the default file storage, which will fail when using openstack storage if openstack requirements haven't been installed yet. Letting edxapp role install the requirements solves this problem. (cherry picked from commit 8246496) *commit message #5:* Move aws and openstack roles above edxapp role. If the aws role runs after the edxapp role, it can fail to install the s3cmd binary into /usr/local/bin/, because edxapp role already installs the s3cmd apt package, which creates binaries in /usr/bin. (cherry picked from commit e91ff3e) *commit message #6:* Remove AWS-specific code to set MTU. We run the AWS role on OpenStack to get the logs synced to S3, but we don't need the MTU settings. (cherry picked from commit 01a0d58) *commit message #7:* Fix missing playbooks/roles/vhost/default/main.yml
samuelallan72
pushed a commit
that referenced
this pull request
Jul 12, 2019
[SE-1194] Campus Automate clean-up of obsolete EBS volumes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's Encrypt role and config settings added to integration
playbook, to automatically bring up integration test servers
with https.