Wiki

Participating: Bryan For more info: OpenStack community page

Based upon the need to meet the OpenStack L release timeline (blueprints bring agreed in the May meeting), we need to determine what Copper will bring to the table as detailed (as possible) by then.

Participating: Bryan For more info: Policy Data Sources

This will document (e.g. summarize / reference) available data sources for policy as a start toward gap identification against Copper use cases.

Participating: Bryan For more info: Policy Data Sources

This will develop an architectural view for incorporating the diverse policy functions of OPNFV components (e.g. OpenStack, OpenDaylight) into a layered architecture for policy management, including:

• functions and interfaces of a policy agent/engine that leverages NB policy APIs of components (e.g. Congress, OpenStack GBP, etc.
• how policy functions are driven through components into other SB components

Participating: Bryan, Iben For more info:

This will include Congress in single-node (see "Academy" below) and multi-node OPNFV testbed environments using scripted installers, initially focusing on SaltStack, but expanding to other installers asap.

Participating: Bryan For more info: Academy

This will setup a basic functional assessment platform ala Sandbox prior to getting a BGS environment that we can use. As compared to Sandbox, the goal of this activity is rather to install the actual OPNFV components as listed for BGS, under a single node (e.g. a laptop with lots of memory) or multi-node environment.