What Production Environment Introduces

There is a difference between prod and dev project's source code delivering. Development environment assumes that code is shared by Vagrant. Production environment needs to get code from private git repository. In order to do it user jon_snow must have ssh keys. Here I don't use private repository, but keys are still needed to log in to production server by Fabric.

jon_snow:
  user.present

jon_snow public key:
  ssh_auth:
    - present
    - user: jon_snow
    - source: salt://user/id_rsa.pub
    - require:
      - user: jon_snow

jon_snow secret key:
  file:
    - managed
    - name: /home/jon_snow/.ssh/id_rsa
    - source: salt://user/id_rsa
    - user: jon_snow
    - group: jon_snow
    - mode: 600
    - require:
      - ssh_auth: jon_snow public key

prod/source_code.sls fetches source code from GitHub. I have tried to use built in git.latest Salt state but it requires to configure git name and email on server. I solved this issue by using git hard reset.

git:
  pkg.installed

github.com:
  ssh_known_hosts:
    - present
    - user: jon_snow
    - fingerprint: 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48

messaging repository clone:
  cmd:
    - run
    - unless: test -d /home/jon_snow/messaging_repository
    - user: jon_snow
    - name: >
              git clone https://github.com/marselester/abstract-internal-messaging.git /home/jon_snow/messaging_repository
    - require:
      - pkg: git
      - ssh_known_hosts: github.com

messaging latest source code:
  cmd:
    - run
    - cwd: /home/jon_snow/messaging_repository
    - user: jon_snow
    - name: >
              git fetch origin &&
              git reset --hard origin/master
    - require:
      - cmd: messaging repository clone

  file:
    - symlink
    - name: {{ pillar['website_src_dir'] }}
    - target: /home/jon_snow/messaging_repository
    - force: True
    - user: jon_snow

Fabric as Deployment Runner

Last thing to do is to run deployment of particular Salt environment salt_env in particular host target. Fabric is good at it.

I want Fabric to:

• bootstrap Salt on given target;

• upload minion.conf to given target to /etc/salt/minion;

• upload Salt configs to given target how it is described in minion.conf (to /srv/salt_roots);

• invoke salt-call on given target with particular salt_env (here is prod).

  $ salt-call state.highstate env=prod
  

Let's try to deploy prod environment to VM. I assume that you have messaging directory (see Developing Django project with SaltStack). You need to clone Deploy Abstract Internal Messaging System in it and start VM.

$ cd messaging
$ git clone https://github.com/marselester/abstract-internal-messaging-deploy.git
$ cd abstract-internal-messaging-deploy/vagrant
$ vagrant up

In order to interact with VM you should add 11.22.33.44 messaging-part-2 to /etc/hosts.

Install Fabric and set up Salt masterless minion in VM.

$ cd messaging/abstract-internal-messaging-deploy
$ pip install -r requirements.txt
$ fab target:local setup_masterless_minion

Finally deploy prod environment in VM.

$ fab target:local salt_env:prod deploy

Conclusion

Besides convenient developing, we got ability to deploy arbitrary environments to arbitrary targets. It gives us opportunity to test deployment itself. You can improve this solution by adding ability to specify git branch which will be deployed.

As in previous post project should work:

$ curl -i messaging-part-2