Difference between revisions of "Project Proposals/puppet-fdio"

From fd.io
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 13: Line 13:
 
== Description ==
 
== Description ==
 
Deploys FD.IO projects, currently VPP and Honeycomb agent, to to various OSs using puppet.
 
Deploys FD.IO projects, currently VPP and Honeycomb agent, to to various OSs using puppet.
 +
 +
Code currently hosted on github: https://github.com/radez/puppet-fdio
  
 
== Scope ==
 
== Scope ==
Line 35: Line 37:
 
== Administrata ==
 
== Administrata ==
 
* Request for Project proposal consideration
 
* Request for Project proposal consideration
** Email: (place link to email to TSC proposing project, this can be obtained from [https://lists.fd.io/pipermail/tsc/ TSC Archives]
+
** Email: https://lists.fd.io/pipermail/tsc/2016-October/000282.html
** Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)
+
** Date: 10/12/2016

Latest revision as of 13:32, 14 October 2016


Name

puppet-fdio

Project Contact Name and Email

Feng Pan - fpan@redhat.com

Repository Name

puppet-fdio

Description

Deploys FD.IO projects, currently VPP and Honeycomb agent, to to various OSs using puppet.

Code currently hosted on github: https://github.com/radez/puppet-fdio

Scope

  • Installs VPP and Honeycomb agent.
  • Configures VPP and Honeycomb agent, including shutting down host interface and binding to VPP.
  • The main use case is for Openstack installer such as TripleO to use this module to automatically configure VPP and Honeycomb agent during deployment.
  • It is also possible to use the module by itself to configure VPP without Openstack.
  • Currently only tested on CentOS, but the goal is to also support Ubuntu in the future.

Initial Committers

  • Feng Pan - fpan@redhat.com
  • Tim Rozet - trozet@redhat.com


Vendor Neutral

This module will be vendor neutral.

Meets Board Policy (including IPR, being within Board defined Scope etc)

Meets board policy as expressed in Technical Community Charter and IP Policy

Administrata