034f37c32a
Instead of a shell script looping over ssh calls, use a simple ansible playbook. The benefit this gets is that we can then also script ad-hoc admin tasks either via playbooks or on the command line. We can also then get rid of the almost entirely unused salt infrastructure. Change-Id: I53112bd1f61d94c0521a32016c8a47c8cf9e50f7
28 lines
952 B
Bash
Executable File
28 lines
952 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# Copyright 2014 Hewlett-Packard Development Company, L.P.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
|
|
cd /opt/config/production
|
|
git fetch -a && git reset -q --hard @{u}
|
|
./install_modules.sh
|
|
|
|
# One must touch manifests/site.pp to trick puppet into re-loading modules
|
|
# some times
|
|
touch manifests/site.pp
|
|
|
|
# Run this as an external script so that the above pull will get new changes
|
|
ansible-playbook -v /etc/ansible/remote_puppet.yaml
|