https://github.com/alexkross/infracodeaci1

Infrastructure as Code template/example 1 for Cisco ACI and baremetal linux using Ansible and GitLab CI/CD
https://github.com/alexkross/infracodeaci1

ansible cisco-aci infrastructure-as-code

Last synced: about 2 months ago
JSON representation

Infrastructure as Code template/example 1 for Cisco ACI and baremetal linux using Ansible and GitLab CI/CD

• Host: GitHub
• URL: https://github.com/alexkross/infracodeaci1
• Owner: alexkross
• License: gpl-3.0
• Created: 2018-06-20T13:58:18.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2018-07-21T17:02:26.000Z (almost 7 years ago)
• Last Synced: 2025-03-10T20:39:02.333Z (about 2 months ago)
• Topics: ansible, cisco-aci, infrastructure-as-code
• Size: 135 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# InfraCodeACI1

This is an example implementation for Infrastructure as Code for Cisco ACI and baremetal linux using Ansible and GitLab CI/CD.

Consider these Ansible playbooks as a template/skeleton/sample that need customization for your particular environment and requirements.

InfraCodeACI2 project is another example with VMware external computing resources.

## Prerequisites

- Working Cisco ACI fabric.

- Account granted an admin role.

- Baremetal linux host.

- Vault`ed passwords placed in host_vars/.

- Ansible configuraion supposedly in $HOME/.ansible.cfg.

- Ansible inventory supposedly in $HOME/.ansible.hosts with appropriate options and group definitions.

- Working GitLab installation with shell runner configured, tagged for ansible, registered, enabled/started and assinged to the project.

- Reflected ansible environment into gitlab-runner home directory (/var/lib/gitlab-runner/ in my case). Proper permissions must be set.

## Topology

Pretty trivial for the sake of cloning and reusing:

- Single APP of two EPGs.

- Single VRF per tenant.

- BD per EPG.

- Contract allowing communication b/w EPGs is common/default.

## Expected result:

![Sample result](doc/tst1_2018-06-20.png)

for the first simplified version.