This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
project_proposals:joid [2015/04/08 23:41] Artur Tyloch [Documentation: ''(optional, Project Categories: Documentation)''] |
project_proposals:joid [2015/12/17 18:08] (current) Iben Rodriguez |
||
---|---|---|---|
Line 10: | Line 10: | ||
==== Project description: ==== | ==== Project description: ==== | ||
- | Introduce MAAS, Juju to support BGS. | + | Introduce MAAS and Juju to support flexible OPNFV platform deployment. |
Line 23: | Line 23: | ||
Note: We are going to utilize MAAS as a part of POD jump-start server so that OS deployment can be handled by MAAS and support Ubuntu, Centos, Windows or customized images (supported by MAAS process). | Note: We are going to utilize MAAS as a part of POD jump-start server so that OS deployment can be handled by MAAS and support Ubuntu, Centos, Windows or customized images (supported by MAAS process). | ||
- | Currently MAAS supports all** NARINDER UPDATE LIST** | + | Currently MAAS supports all Major OEM (HP, Dell, Intel, Cisco, Sea-micro etc.. ) hardware which includes the power management of those hardware through IPMI as well as other power management software. |
**What is Juju?** | **What is Juju?** | ||
Line 58: | Line 58: | ||
==== Scope: ==== | ==== Scope: ==== | ||
- | JOID will provide means to deploy VIM and NFVI services using MAAS and Juju. | + | JOID will provide means to deploy VIM and NFVI using MAAS and Juju. |
Integrate MAAS and Juju with OPNFV continuous integration and continuous deployment infrastructure and processes. | Integrate MAAS and Juju with OPNFV continuous integration and continuous deployment infrastructure and processes. | ||
Line 69: | Line 69: | ||
==== Dependencies: ==== | ==== Dependencies: ==== | ||
- | * Identify similar projects is underway or being proposed in OPNFV or upstream project | ||
- | * Identify any open source upstream projects and release timeline. | ||
- | * Identify any specific development be staged with respect to the upstream project and releases. | ||
- | * Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications. | ||
- | * If project is an integration and test, identify hardware dependency. | ||
- | ==== Committers and Contributors: ==== | + | * The “BGS” project in OPNFV |
+ | * The “OCTOPUS” project in OPNFV | ||
+ | * The “Pharos” project in OPNFV | ||
+ | * The “OSCAR” project in OPNFV | ||
- | * Names and affiliations of the committers | ||
- | * Names and affiliations of any other contributors | ||
- | ==== Planned deliverables ==== | ||
- | * Described the project release package as OPNFV or open source upstream projects. | ||
- | * If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables. | ||
+ | ==== Planned deliverables ==== | ||
+ | |||
+ | * Juju charms for OPNFV workload | ||
+ | * bundles for: | ||
+ | * OPNFV platform, ODL stack i.e. OpenStack and ODL | ||
+ | * OPNFV platform, OpenContrail stack i.e. OpenStack and OpenContrail | ||
+ | * and more stack versions | ||
+ | * Build and deploy scripts for integration with OPNFV CI and CD | ||
==== Proposed Release Schedule: ==== | ==== Proposed Release Schedule: ==== | ||
- | * When is the first release planned? - We are ready to release Juju with rel #1 or immediately after rel #1 | + | * When is the first release planned? - We are ready to release JOID with rel #1 or immediately after rel #1 |
- | * Will this align with the current release cadence | + | * For release #2 we will be able to deploy more SDN options like OpenContrail, etc. |
- | Use the above information to create a key project facts section on your project page | ||
===== Key Project Facts ===== | ===== Key Project Facts ===== | ||
- | ** Project Name: ** Juju \\ | + | ** Project Name: ** JOID \\ |
- | ** Repo name: ** Juju \\ | + | ** Repo name: ** joid \\ |
** Project Category: ** Integration & Testing \\ | ** Project Category: ** Integration & Testing \\ | ||
** Lifecycle State: ** \\ | ** Lifecycle State: ** \\ | ||
Line 101: | Line 101: | ||
** Project Lead: ** \\ | ** Project Lead: ** \\ | ||
** Jira Project Name: ** Same as Project name \\ | ** Jira Project Name: ** Same as Project name \\ | ||
- | ** Jira Project Prefix: ** JUJU \\ | + | ** Jira Project Prefix: ** JOID \\ |
- | ** mailing list tag ** [juju] \\ | + | ** mailing list tag ** [joid] \\ |
** IRC: ** Server:freenode.net Channel:#opnfv-juju \\ | ** IRC: ** Server:freenode.net Channel:#opnfv-juju \\ | ||
+ | |||
** Committers: ** \\ | ** Committers: ** \\ | ||
- | * Narinder Gupta - narinder.gupta@canonical.com | + | * Narinder Gupta - <narinder.gupta@canonical.com> |
* Prakash Ramchandran prakash.ramchandran@huawei.com | * Prakash Ramchandran prakash.ramchandran@huawei.com | ||
* Vagish Shanmukh vagish.shanmukh@huawei.com | * Vagish Shanmukh vagish.shanmukh@huawei.com | ||
- | * Artur Tyloch - artur.tyloch@canonical.com | + | * Artur Tyloch - <artur.tyloch@canonical.com> |
** Contributors: ** \\ | ** Contributors: ** \\ | ||
- | * Ivan Zoratti - ivan.zoratti@canonical.com | + | * David Karr - <dk068x@att.com> |
+ | * Martin Taylor - martin.taylor@metaswitch.com | ||
+ | * Parviz Yegani - pyegani@juniper.net | ||
+ | * Jonas Bjurel - jonas.bjurel@ericsson.com | ||
+ | * Ivan Zoratti - ivan.zoratti@canonical.com | ||
+ | * Samantha Jian-Pielak - <samantha.jian-pielak@canonical.com> | ||
+ | * Iben Rodriguez - <iben@vmsec.com> | ||
+ | ** Link to TSC approval: http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-05-26-13.58.html | ||
- | ** Link to TSC approval: Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html ** \\ | ||
** Link to approval of additional submitters: ** Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html \\ | ** Link to approval of additional submitters: ** Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html \\ |