Ansible Lightspeed technical preview demo content

Compilation of Ansible Lightspeed demo content and examples.

Ansible Lightspeed demo list

Please refer to the README.md for each demo in the corresponding demo root folder for detailed demo instructions.

Infrastructure

• Install and configure Cockpit
• Install and configure postgresql and pgadmin4 podman container

Cloud

• Provision an AWS EC2 instance
• Provision Azure resources and VM

Demo content folder structure

The repository folder structure is as follows.

.
└── playbooks/
    └── <domain>/
        └── <demo_name>/
            ├── demo_<playbook_name>.yml <-- Initial Ansible content for demo.
            ├── solution_<playbook_name>.yml <-- Tested Ansible content for comparison.
            └── prepare_<playbook_name>.yml <-- Initial Playbook to configure the demo environment.

• <domain> - Ansible examples are sorted by domain. For example, the cloud folder contains AWS, Azure, and Google Cloud content.
• demo_<playbook_name>.yml - Playbooks that start with demo_* are the initial Ansible example to use in the demo. For example, demo_provision_ec2_instance.yml located in the cloud/aws folder.
• prepare_<playbook_name>.yml - Playbooks that start with prepare_* prepares the environment for the demo.
• README.md - Contains a video and step-by-step instructions to prepare and perform the demo.
• solution_<playbook_name>.yml - Playbooks that start with solution_* have been tested with the latest version of the Ansible Lightspeed model. Use the tested Ansible content to compare your Ansible Lightspeed-generated outputs before the demo.

How do I get started with Ansible Lightspeed?

Please follow the instructions provided by the resources available in the getting started guide.

❗️Test before doing a demo if you're using this content locally

The IBM Watson Code Assistant model continues to improve and evolve with each release. This can result in generated suggestions that differ from the examples provided.

Tested Ansible Playbooks are available for each corresponding demo Playbook and start with the solution_*.yml prefix. For example, solution_provision_azure_vm.yml.
Please use this to compare your generated suggestions before doing the demo.

---