This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
copper:copper_work_items [2015/03/24 19:27] Bryan Sullivan |
copper:copper_work_items [2015/09/29 23:23] (current) Bryan Sullivan |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Work Items for Copper | + | Note: this page and the linked pages are being migrated to the issue/task tracking tools ([[https://jira.opnfv.org/browse/COPPER-3?jql=project%20%3D%20COPPER|Jira]], [[https://trello.com/b/vRhIA8sP/opnfv|Trello]]) and the Copper design docs (latest version is [[http://artifacts.opnfv.org/review/1174/index.html|here]]. Content on this page will be removed as it is migrated. |
- | == OpenStack Liberty Blueprints == | + | ===== Work Items for Copper ===== |
+ | |||
+ | To add your name as an active contributor to these work items just edit this page, or send an email to the opnfv-tech-discuss@lists.opnfv.org mail list. | ||
+ | |||
+ | == OpenStack Congress Assessment == | ||
Participating: Bryan | Participating: Bryan | ||
- | 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. Initial proposals have been added for Copper on the [[https://wiki.opnfv.org/community/openstack|Communities]] page. | + | For more info: [[https://wiki.opnfv.org/copper/copper_work_items/congress|Congress]] |
- | == Policy Data Sources == | + | This will develop information related to OpenStack Congress. |
+ | |||
+ | == OpenStack Blueprints == | ||
Participating: Bryan | Participating: Bryan | ||
- | This will document (e.g. summarize / reference) available data sources for policy as a start toward gap identification against Copper use cases. | + | As we develop concrete proposals for new functionality in OpenStack (e.g. for Congress) they will be listed on the [[https://wiki.opnfv.org/community/openstack/|OpenStack community]] page. |
== Policy Architecture == | == Policy Architecture == | ||
Participating: Bryan | Participating: Bryan | ||
+ | |||
+ | For more info: [[https://wiki.opnfv.org/copper/copper_work_items/policy_architecture|Policy Architecture]] | ||
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: | 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: | ||
Line 21: | Line 29: | ||
Participating: Bryan, Iben | Participating: Bryan, Iben | ||
- | This will include [[https://wiki.openstack.org/wiki/Congress|Congress]] in single-node (see "Academy" below) and multi-node OPNFV testbed environments using scripted installers, initially focusing on [[https://wiki.opnfv.org/salt4nfv|SaltStack]], but expanding to other installers asap. | + | For more info: |
- | + | ||
- | == Getting Copper sandbox ("Academy") up and running == | + | |
- | Participating: Bryan | + | |
- | + | ||
- | This will setup a basic functional assessment platform ala [[https://wiki.opnfv.org/wiki/sandbox|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 [[https://wiki.opnfv.org/get_started/get_started_work_items|BGS]], under a single node (e.g. a laptop with lots of memory) or multi-node environment. | + | |
- | + | ||
- | See the [[copper/copper_work_items/academy|Academy]] page for more info. | + | |
+ | This will include [[https://wiki.openstack.org/wiki/Congress|Congress]] in single-node (see "Academy" below) and multi-node OPNFV testbed environments using scripted installers, initially focusing on [[https://wiki.opnfv.org/salt4nfv|SaltStack]], but expanding to other installers asap. | ||