# Playbook: INFRA > Historical documentation restored from the Pigsty v1.5.1 tag. --- > Install pigsty & Add new optional to meta node with `INFRA` series [playbooks](/docs/p-playbook/). | Playbook | Function | Link | |---------------------------------------------|--------------------------------------|------------------------------------------------------------------------| | [`infra`](/docs/p-infra/#infra) | Install pigsty on meta nodes | [`src`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra.yml) | | [`infra-demo`](/docs/p-infra/#infra-demo) | Special version of `infra`, pull up the 4-node sandbox in one-pass | [`src`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-demo.yml) | | [`infra-remove`](/docs/p-infra/#infra-remove) | Uninstall pigsty from the meta node. | [`src`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-remove.yml) | | [`infra-jupyter`](/docs/p-infra/#infra-jupyter) | Install optional JupyterLab on meta node | [`src`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-jupyter.yml) | --------------- ## `infra` The [`infra.yml`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra.yml) playbook will install **Pigsty** on the **meta nodes**. When using Pigsty as a battery-included Postgres, `infra.yml` is sufficient for the installation. ![](/img/history/v1.5/playbook/infra.svg) ### What The following tasks will be executed: * Configure dir and environment variables of meta nodes. * Download and create a LocalYum repo. (If [offline](/docs/t-offline/) packages `/tmp/pkg.tgz` exists, skip the download phase) * Init the current meta node as a [common node](/docs/p-nodes/) in Pigsty management. * Deploy **infra**, including Prometheus, Grafana, Loki, Alertmanager, Consul Server, etc... * Init a common [PostgreSQL](/docs/p-pgsql/) singleton on the current node as CMDB. ### Where This playbook works on **meta nodes**. * Pigsty will use **the node currently executing this playbook** as Pigsty's meta node by default. * Pigsty will mark the current node as the meta node by default during [`configure`](/docs/v-config/#configure) and replace the placeholder IP `10.10.10.10` in the config template with the **current node's primary IP**. * **Meta node** can initiate management and deploy infra. It is not different from a regularly managed pgsql node. * Pigsty uses meta nodes by default to deploy DCS Servers for PostgreSQL HA. But you can use external DCS Servers, too. * Using multiple meta nodes is possible. Refer to the [`pigsty-dcs3`](https://github.com/pgsty/pigsty/blob/v1.5.1/files/conf/pigsty-dcs3.yml#L33) template: 3 meta x 3 nodes, allowing one failure. ### How Some special notes: * This playbook is **idempotent**. Play again will erase Consul Server and CMDB (when protection is disabled) * The complete execution of this playbook takes about 5-8 minutes with [offline](/docs/t-offline/) pkgs, depending on your machine spec. * Depending on your network conditions, downloading packages directly from the Internet may take 10-20 minutes. * This playbook treats the meta node as a common node to manage and deploy the PGSQL database. If it can be executed successfully, you could be confident that [`nodes.yml`](/docs/p-nodes/) and [`pgsql.yml`](/docs/p-pgsql/) will work on nodes with the same state. * The default [`pg-meta`](https://github.com/pgsty/pigsty/blob/v1.5.1/pigsty.yml#L43) on the meta node will be used as the Pigsty CMDB and supporting advanced features. ### Tasks The playbook. ```bash ./infra.yml --tags=environ # Reconfigure envs on the meta node ./infra.yml --tags=repo -e repo_rebuild=true # Forced re-creation of local repo ./infra.yml --tags=repo_upstream # Add upstream yum repos ./infra.yml --tags=prometheus # Recreate Prometheus ./infra.yml --tags=nginx_config,nginx_restart # Regenerate Nginx conf and restart …… ``` Nodes within the `meta` group will be marked with the [`meta_node`](/docs/v-nodes/#meta_node) flag in Pigsty [inventory](/docs/v-config/). --------------- ## `infra-demo` The [`infra-demo.yml`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-demo.yml) is a special playbook for the demo env, which can be used to initialize a 4-node sandbox in one go by interweaving meta node & other nodes initialization. It's useful when trying to deploy multiple meta nodes. It's equivalent to following commands in the standard 4-node demo. ```bash ./infra.yml # Install Pigsty on meta node ./nodes.yml -l pg-test # Init 3 nodes of cluster pg-test ./pgsql.yml -l pg-test # Init pgsql database cluster pg-test ``` > [!WARNING] > USE THIS WITH CAUTION! You could just destroy the entire env with a fat finger & wrong config. ![](/img/history/v1.5/playbook/infra-demo.svg) --------------- ## `infra-remove` The [`infra-remove.yml`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-remove.yml) playbook will uninstall pigsty from the meta node. ![](/img/history/v1.5/playbook/infra-remove.svg) Following services will be stopped & removed from meta nodes. - grafana-server - prometheus - alertmanager - node_exporter - consul - loki - promtail --------------- ## `infra-jupyter` Playbook [`infra-jupyter.yml`](https://github.com/pgsty/pigsty/blob/v1.5.1/infra-jupyter.yml) will install JupyterLab on the meta node. Check [Tutorial: Jupyter Lab](/docs/t-jupyter/) for more details. ![](/img/history/v1.5/playbook/infra-jupyter.svg)