tree: 11dc662d1d57236d811360e0ef814462d73b69d5 [path history] [tgz]
  1. .gitignore
  2. LICENSE.txt
  3. README.md
  4. ansible.cfg
  5. bootstrap-dev-env.yml
  6. build-core-image-playbook.yml
  7. build-platform-install-playbook.yml
  8. collect-diag-playbook.yml
  9. compute-node-enable-playbook.yml
  10. compute-node-refresh-playbook.yml
  11. copy-cord-playbook.yml
  12. copy-profile-playbook.yml
  13. cord-automation-playbook.yml
  14. cord-config-playbook.yml
  15. cord-fabric-pingtest.yml
  16. cord-refresh-fabric.yml
  17. credentials/
  18. deploy-computenode-playbook.yml
  19. deploy-elasticstack-playbook.yml
  20. deploy-mavenrepo-playbook.yml
  21. deploy-onos-playbook.yml
  22. deploy-openstack-playbook.yml
  23. devel-tools-playbook.yml
  24. docs/
  25. filter_plugins/
  26. glance-images-playbook.yml
  27. install-kubernetes-tools-playbook.yml
  28. inventory/
  29. library/
  30. onboard-exampleservice-playbook.yml
  31. onboard-openstack-playbook.yml
  32. onboard-profile-playbook.yml
  33. onos-debug-playbook.yml
  34. pod-test-playbook.yml
  35. prep-buildnode-playbook.yml
  36. prep-computenode-playbook.yml
  37. prep-headnode-playbook.yml
  38. prereqs-check-playbook.yml
  39. publish-images-playbook.yml
  40. publish-platform-install-playbook.yml
  41. roles/
  42. scripts/
  43. ssh_pki/
  44. start-xos-helm-playbook.yml
  45. start-xos-playbook.yml
  46. teardown-onos-playbook.yml
  47. teardown-openstack-playbook.yml
  48. teardown-xos-playbook.yml
  49. vtn-refresh-playbook.yml
  50. xos-service-config.yml
  51. xos-services-up.yml
README.md

CORD platform-install

This repository contains Ansible playbooks for installing and configuring software components that build a CORD POD: OpenStack, ONOS, and XOS.

It is used as a sub-module of the main CORD repository.

Credentials

Credentials will be autogenerated and placed in the credentials/ directory when the playbooks are run, where the credential name is the filename, and the contents of the file is the password.

For most profiles the XOS admin user is named xosadmin@opencord.org.

Creating a new CORD profile

To create a new CORD profile, you should create a .yaml variables file in profile_manifests/ with the name of your profile (ex: my-profile.yaml), and populate it with your configuration.

Making changes and lint checking your changes

Before commit, please run ./scripts/lintcheck.sh . in the repo root, which will perform the same ansible-lint check that Jenkins performs when in review in gerrit.

Specific profiles notes

opencloud

Used as a part of the OpenCloud deployment. Similar to rcord.

rcord

This is a part of the R-CORD deployment - start using the steps specified in that repo.

This profile is designed to integrate XOS with physical infrastructure pieces like MaaS, OpenStack, and ONOS. See the CORD-in-a-Box Quick Start Guide for how to set up a virtual multi-node R-CORD pod on a single host.

ecord

E-CORD description goes here.

mcord

M-CORD description goes here.

Design Notes for Developers

Variables used in platform-install

cord_profile: name of the profile_manifest to use.

Paths on configuration node (where playbooks are run, may also be build node)

  • config_cord_dir location on configuration node of cord dir
  • config_cord_profile_dir location on configuration node of cord_profile dir
  • pki_dir, ssh_pki_dir: where SSL and SSH certificates are created on config node
  • credentials_dir - location where autogenerated passwords file are created

Paths on head node (target system operated on by playbooks)

  • head_cord_dir - where the cord directory is copied to on the head node (deprecated when we reach container-only deploys)
  • head_cord_profile_dir - location of the cord_profile directory on the head node
  • head_onos_cord_dir - location of the onos-cord directory on the head node
  • head_onos_fabric_dir - location of the onos-fabric directory on the head node

Style notes

Prefix every role file with the yaml start block and comment with name of file relative to role base.

---
# rolename/tasks/main.yml

When using templates, put the template filename and path within the role as a comment in the template so that it's easy to determine which template was used to create a file after it's been created.

If you use a variable that isn't created by the ansible setup task, define it in the role defaults file. The default value for anay variable must be the same across all role defaults.

Use the YAML style syntax for tasks, not the older = syntax, as the former is more likely to indent and syntax highlight properly in most editors.

Roles should always have the same outcome, so avoid using conditionals or tags to change the behavior of a role. These features should only be used for avoiding time-consuming tasks in an idempotent manner.