Skip to content

Add setup_maas_tigkstack var default to False#414

Merged
tonytan4ever merged 1 commit intorcbops:masterfrom
andymcc:grafana_conditional
Dec 12, 2017
Merged

Add setup_maas_tigkstack var default to False#414
tonytan4ever merged 1 commit intorcbops:masterfrom
andymcc:grafana_conditional

Conversation

@andymcc
Copy link
Copy Markdown
Contributor

@andymcc andymcc commented Dec 12, 2017

We shouldn't need to install or setup the tigkstack grafana bits unless
we are doing upgrades. As this is causing issues with SNI/SSL on the apt
keys for influxdb we should skip installing this.

A flag is added (defaulting not defined), so that we can easily enable
this for testing downtime on upgrades, setting the
"setup_maas_tigkstack" variable to True.

We shouldn't need to install or setup the tigkstack grafana bits unless
we are doing upgrades. As this is causing issues with SNI/SSL on the apt
keys for influxdb we should skip installing this.

A flag is added (defaulting not defined), so that we can easily enable
this for testing downtime on upgrades, setting the
"setup_maas_tigkstack" variable to True.
Copy link
Copy Markdown
Contributor

@mattt416 mattt416 left a comment

Choose a reason for hiding this comment

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

We still have an underlying Ansible bug w/ SNI, and may need to address later, but I definitely think if this functionality is not being used by customers then we do not need to test it.

@tonytan4ever tonytan4ever merged commit 5d9cd45 into rcbops:master Dec 12, 2017
mattt416 added a commit that referenced this pull request Dec 12, 2017
In #414 we tried making this include conditional, however this playbook
is still being included when run w/ older versions of ansible (1.9.6
as an example).

As tigkstack is not something we deploy for customers, this commit
removes it from testing entirely.
mattt416 added a commit that referenced this pull request Dec 12, 2017
In #414 we tried making this include conditional, however this playbook
is still being included when run w/ older versions of ansible (1.9.6
as an example).

Instead, we switch the two `Add influxdata apt-keys` tasks to using
the shell module.  Using ansible's apt_key fails w/ hosts using SNI
(as https://repos.influxdata.com/ appears to be using) because:

1. ansible/ansible#32053 (not backported to
   2.3.2.0)
2. ansible 1.9.6 doesn't seem to support SNI on Trusty (python < 2.7.9)
mattt416 added a commit that referenced this pull request Dec 12, 2017
In #414 we tried making this include conditional, however this playbook
is still being included when run w/ older versions of ansible (1.9.6
as an example).

Instead, we update maas_influxdata_key to have an id and keyserver key.
This allows apt_key to work since it doesn't need to speak to
https://repos.influxdata.com/ directly.  Using ansible's apt_key with
https://repos.influxdata.com/ fails because of SNI and:

1. ansible/ansible#32053 (not backported to
   2.3.2.0)
2. ansible 1.9.6 doesn't seem to support SNI on Trusty (python < 2.7.9)
cloudnull pushed a commit that referenced this pull request Dec 13, 2017
In #414 we tried making this include conditional, however this playbook
is still being included when run w/ older versions of ansible (1.9.6
as an example).

Instead, we update maas_influxdata_key to have an id and keyserver key.
This allows apt_key to work since it doesn't need to speak to
https://repos.influxdata.com/ directly.  Using ansible's apt_key with
https://repos.influxdata.com/ fails because of SNI and:

1. ansible/ansible#32053 (not backported to
   2.3.2.0)
2. ansible 1.9.6 doesn't seem to support SNI on Trusty (python < 2.7.9)
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.

3 participants