| commit | 71f494996c03b6062bbb940df2d7d1981172a173 | [log] [tgz] |
|---|---|---|
| author | Marc De Leenheer <marc@opennetworking.org> | Tue Oct 31 00:12:06 2017 -0700 |
| committer | Marc De Leenheer <marc@opennetworking.org> | Tue Oct 31 00:12:50 2017 -0700 |
| tree | dea030666e77ca1e0f1e16779d3df4c87469eceb | |
| parent | a14575f0ecb41e4f5525a554226f5caf9ea43484 [diff] |
Realistic bandwidth profiles Change-Id: I5c5d44be2e6593e3f037db41dc609e7d19d03758
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 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.
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.
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.
Used as a part of the OpenCloud deployment. Similar to 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.
E-CORD description goes here.
M-CORD description goes here.
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 dirconfig_cord_profile_dir location on configuration node of cord_profile dirpki_dir, ssh_pki_dir: where SSL and SSH certificates are created on config nodecredentials_dir - location where autogenerated passwords file are createdPaths 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 nodehead_onos_cord_dir - location of the onos-cord directory on the head nodehead_onos_fabric_dir - location of the onos-fabric directory on the head nodePrefix 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.