Madisoft SpA – Page 3 – Innovatori della Scuola Italiana

AWS | Devops

In the previous article we showed you how we created our infrastructure as code. This article describes how to configure services within our EC2 instances. Provision Backend Let’s start with a bash script to run the playbooks:

./provision_nuvola_backend.sh --limit "tag_nuvola_type_${ENV}_backend" 
./provision_nuvola_dbserver.sh --limit "tag_nuvola_type_${ENV}_database"
./provision_nuvola_routine.sh --limit "tag_nuvola_type_${ENV}_routine"

if [ "$ENV" != "prod" ]; then
        ./nuvola-init-not-prod-env.sh --env ${ENV}
        ./deploy_nuvola.sh --limit "tag_nuvola_type_${ENV}_backend" --env ${ENV}
fi

1

2

3

4

5

6

7

8

./provision_nuvola_backend.sh --limit "tag_nuvola_type_${ENV}_backend"

./provision_nuvola_dbserver.sh --limit "tag_nuvola_type_${ENV}_database"

./provision_nuvola_routine.sh --limit "tag_nuvola_type_${ENV}_routine"

if [ "$ENV" != "prod" ]; then

./nuvola-init-not-prod-env.sh --env ${ENV}

./deploy_nuvola.sh --limit "tag_nuvola_type_${ENV}_backend" --env ${ENV}

fi

Here is the playbook used to configure backend services:

- hosts: all

  vars_files:
  - vars/system.yml
  - vars/packages.yml
  - vars/php_prod.yml
  - vars/vars_newrelic.yml
  - vars/vars_backend.yml
  - vars/vars_backend_secure.yml
  - "inventories/group_vars/regions.yml"

  handlers:
    - include: roles/newrelic/handlers/main.yml

  tasks:
    - include: roles/init/tasks/init_upgrade_generic.yml
      tags: init

    - include: roles/init/tasks/init_nuvola_dns_updater.yml
      tags: dns

    - include: roles/init/tasks/init_nuvola_backend.yml
      tags: init

    - include: roles/php7/tasks/php7_prod.yml
      tags: php

    - include: roles/nginx/tasks/nginx_prod.yml
      tags: nginx

    - include: roles/newrelic/tasks/newrelic_php7.yml
      tags: newrelic

    - include: roles/rabbitmq/tasks/rabbitmq_php.yml
      tags: rabbitmq_php

    - include: roles/logstash/tasks/logstash_forwarder_all.yml
      tags: logstash

    - include: roles/cloudwatch-logs-agent/tasks/cloudwatch-logs-agent.yml
      tags: cloudwatch

    - include: roles/webserver/tasks/finalize.yml
      tags: webserver

    - include: roles/deploy-nuvola/tasks/auto-deploy.yml
      tags: auto-deploy

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

- hosts: all

vars_files:

- vars/system.yml

- vars/packages.yml

- vars/php_prod.yml

- vars/vars_newrelic.yml

- vars/vars_backend.yml

- vars/vars_backend_secure.yml

- "inventories/group_vars/regions.yml"

handlers:

- include: roles/newrelic/handlers/main.yml

tasks:

- include: roles/init/tasks/init_upgrade_generic.yml

tags: init

- include: roles/init/tasks/init_nuvola_dns_updater.yml

tags: dns

- include: roles/init/tasks/init_nuvola_backend.yml

tags: init

- include: roles/php7/tasks/php7_prod.yml

tags: php

- include: roles/nginx/tasks/nginx_prod.yml

tags: nginx

- include: roles/newrelic/tasks/newrelic_php7.yml

tags: newrelic

- include: roles/rabbitmq/tasks/rabbitmq_php.yml

tags: rabbitmq_php

- include: roles/logstash/tasks/logstash_forwarder_all.yml

tags: logstash

- include: roles/cloudwatch-logs-agent/tasks/cloudwatch-logs-agent.yml

tags: cloudwatch

- include: roles/webserver/tasks/finalize.yml

tags: webserver

- include: roles/deploy-nuvola/tasks/auto-deploy.yml

tags: auto-deploy

Let’s focus on php…

Infrastructure scripts

AWS | Devops

In the previous article we described the reasons that made us change the provider. In this article we will describe how we built our infrastructure as code. As a first step let’s create a bash script to run the playbook:

:~$ ./infrastructure_nuvola_env_aws.sh --env prod

#!/bin/bash
. libs/extra_option_parser.sh

…

ansible-playbook 
--vault-password-file secrets/infrastructure_nuvola_env.secret \
ansible/infrastucture_nuvola_env.yml \
-e"$EXTRA_OPTIONS"

1

2

3

4

5

6

7

8

9

10

11

:~$ ./infrastructure_nuvola_env_aws.sh --env prod

#!/bin/bash

. libs/extra_option_parser.sh

…

ansible-playbook

--vault-password-file secrets/infrastructure_nuvola_env.secret \

ansible/infrastucture_nuvola_env.yml \

-e"$EXTRA_OPTIONS"

With the flexibility of AWS & Ansible we can easily craft an isolated…

2 Comments Read more

Nuvola: a tale of migration to AWS

AWS | Devops

In this series of articles we will describe our migration experience to AWS. Why a migration? Our old provider had limits. We had to overcome. In particular: No automation No flexibility No autoscaling If we wanted to grow it was necessary to migrate to a provider with these features. Need…

BDD | PHP | PHPSpec

Disclaimer This post title can be misleading. Method order is just an implementation detail that should not be tested as PHPSpec philosophy is to test your public API, not the implementation as it would lead to fragile tests. Fundamentalists might say that following example should not be performed in PHPSpec but with…

Symfony sharding

Symfony

In a previous post we’ve seen how leverage Doctrine sharding functionalities. But how can we tell our app to use a specific shard? A common web app has usually at least two sources: http requests and cli commands. Let’s see one at the time. Http request As you already know HTTP is a…

Doctrine sharding

PHP | Scaling | Symfony

In the previous article we explored why sharding by tenant is a very good solution for us. In this article we dig into how to divide our Symfony app by shard. Doctrine We chose Doctrine as our ORM so let’s see what it offers to us. First of all you have to…

1 Comment Read more

Data migration to AWS

Symfony

In this article, I’ll tell you how we migrated our databases from our previous provider to AWS RDS. Our previous DB infrastructure was already in the cloud and the entire db was sharded, so we had about 350 GB of data split in about 1000 databases. Want to know more about…

Madisoft speaks at AWS Summit

Symfony

We are very proud to have been invited by Amazon at AWS Summit Milan 2017 as speakers. Our speech will focus on how we’re using AWS RDS to leverage our relation data. As you may already know, our software Nuvola is a data-heavy SaaS and we currently manage more than…

AWS | Devops

In this article we are going to describe how we realized our RDS infrastructure using Ansible as automation tool. We’ve completely avoided using AWS GUI, both for implementation and management activities. Our aim was to develop a parametric infrastructure, able to adapt to all of our projects simply by changing few parameters in…

3 Comments Read more

Symfony form pills – form type options

Symfony

Today we are going to tackle a problem that I’ve recently faced with Symfony form types. Scenario: I need a choice type of a certain entity (Foo) with values that follows a certain logic

<?php

class FooChoiceType extends AbstractType
{
    private $fooAdapter;

    public function __construct(FooAdapter $fooAdapter)
    {
        $this->fooAdapter = $fooAdapter;
    }

    function configureOptions(OptionsResolver $resolver)
    {
        $resolver->setDefaults([
            'required' => true,
            'multiple' => false,
            'choices' => $this->fooAdapter->getFoos(),
        ]);
    }

    public function getParent()
    {
        return ChoiceType::class;
    }
}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

<?php

class FooChoiceType extends AbstractType

{

private $fooAdapter;

public function __construct(FooAdapter $fooAdapter)

{

$this->fooAdapter = $fooAdapter;

}

function configureOptions(OptionsResolver $resolver)

{

$resolver->setDefaults([

'required' => true,

'multiple' => false,

'choices' => $this->fooAdapter->getFoos(),

]);

}

public function getParent()

{

return ChoiceType::class;

}

I’ve built up a FooChoiceType because I don’t want to inject fooAdapter in each form where I’m…

2 Comments Read more