Repository files navigation

Compilation of Ansible Lightspeed demo content and examples.

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

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

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

The repository folder structure is as follows.

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

• <domain> - Ansible examples are sorted by domain. For example, thecloud folder contains AWS, Azure, and Google Cloud content.
• demo_<playbook_name>.yml - Playbooks that start withdemo_* are the initial Ansible example to use in the demo. For example,demo_provision_ec2_instance.yml located in thecloud/aws folder.
• prepare_<playbook_name>.yml - Playbooks that start withprepare_* 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 withsolution_* 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.

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

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 thesolution_*.yml prefix. For example,solution_provision_azure_vm.yml.
Please use this to compare your generated suggestions before doing the demo.