Features/Pcp4

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Detailed Description)
(7 intermediate revisions by 3 users not shown)
Line 12: Line 12:
 
== Current status ==
 
== Current status ==
 
* Targeted release: Fedora 19
 
* Targeted release: Fedora 19
* Last updated: 2013-01-24
+
* Last updated: 2013-01-25
 
* Percentage of completion: 80%
 
* Percentage of completion: 80%
 +
* PCP 3.7 due early March
 +
* PCP 3.8 (or 4.0) due late April
  
 
== Detailed Description ==
 
== Detailed Description ==
  
This PCP update may deliver a group of new features:
+
This PCP update is planned to deliver a group of new features:
* Increased security (SSL transport, authenticated/authorized remote access)
+
* Increased security (SSL transport, authenticated/authorized remote access) (3.7, 4.0)
* RRD format data interoperation
+
* IPv6 support (3.7)
* Improved user interfaces (pmchart, possible web gui)
+
* JSON interface for web monitoring clients (4.0)
* IPv6 support
+
* RRD format data interoperation (4.0)
* Improvements to Python scripting for monitoring clients
+
* Improved user interfaces (pmchart, possible web gui) (3.7, 4.0)
* Prototype instrumentation for systemd and GFS2 clusters
+
* Improvements to Python scripting (3.6.10)
 +
* Instrumentation and monitoring for systemd and GFS2 clusters (3.7)
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
  
The increased security may enable installing/activating the daemon by default.
+
The increased security may enable installing/activating the pmcd daemon by default.
  
 
== Scope ==
 
== Scope ==
  
Only the pcp packages would be modified.
+
Only the PCP packages would be modified.
 +
 
 +
The scope of changes within the PCP code base is relatively large however - addition of SSL/TLS and IPv6 to the core protocol affects all live-mode tools and daemons, for example.  Early upstream point releases and the fairly extensive test suite are used to mitigate risk.
  
 
== How To Test ==
 
== How To Test ==
  
PCP includes a quality assurance suite in the pcp-testsuite package.
+
The PCP sources include a quality assurance suite in the pcp-testsuite package with several hundred tests. Additional tests are being added as the new features are developed.
 +
 
 
Instructions for configuring and running the tests are included in an accompanying README file.
 
Instructions for configuring and running the tests are included in an accompanying README file.
  
 
== User Experience ==
 
== User Experience ==
  
TBA.
+
All changes are backwards compatible, and the user must opt-in to use the new features.  For example, the SSL extensions are negotiated transparently using existing feature bits in the protocol to flag the new capability to either end of the connection.  Secure connections can then be enabled via an environment variable or through explicit user interface selection.
 +
 
 +
As a second example, proposed new GFS2 metrics and monitoring utility would make use of existing GFS2 kernel instrumentation, and existing PCP interfaces for extension (on both the individual cluster nodes, as well as the remote monitoring tool).  The user would explicitly install the GFS2 PCP agent on the cluster nodes, and thus augments their existing PCP installation with these new metrics and capabilities.
  
 
== Dependencies ==
 
== Dependencies ==
Line 53: Line 61:
 
== Documentation ==
 
== Documentation ==
  
All tools, daemons and library interfaces have accompanying man pages.  The pcp-doc package also contains tutorials, howtos and other documentation.
+
All tools, daemons and library interfaces have accompanying man pages.  The pcp-doc package also contains tutorials, howtos and other documentation and coverage of the new major features (like SSL) is being added.
 +
 
 +
Discussion is on-going with the original authors (SGI) as well, about making available the two technical books they have published about PCP in the past, under a community friendly license.
 +
 
 +
Links to each of these documents will be added here as they become available.
 +
 
 +
[http://oss.sgi.com/projects/pcp/ PCP Project Home page]
  
Discussion is on-going with the original authors (SGI) about making available the two technical books they have published about PCP, under a community friendly license.
+
[http://oss.sgi.com/projects/pcp/pcp-gui.git/man/html/index.html Online pcp-doc manual]
  
 
== Release Notes ==
 
== Release Notes ==
  
TBA.
+
It is anticipated that the upstream release notes and documentation will provide coverage of the new features, and the Fedora release notes could link to those.
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 
* See [[Talk:Features/Pcp4]]   
 
* See [[Talk:Features/Pcp4]]   
  
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF19]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 19:55, 5 March 2013

Contents

Feature Name: Performance Co-Pilot Feature Update

Summary

A new feature release of PCP (Performance Co-Pilot).

Owner

Current status

  • Targeted release: Fedora 19
  • Last updated: 2013-01-25
  • Percentage of completion: 80%
  • PCP 3.7 due early March
  • PCP 3.8 (or 4.0) due late April

Detailed Description

This PCP update is planned to deliver a group of new features:

  • Increased security (SSL transport, authenticated/authorized remote access) (3.7, 4.0)
  • IPv6 support (3.7)
  • JSON interface for web monitoring clients (4.0)
  • RRD format data interoperation (4.0)
  • Improved user interfaces (pmchart, possible web gui) (3.7, 4.0)
  • Improvements to Python scripting (3.6.10)
  • Instrumentation and monitoring for systemd and GFS2 clusters (3.7)

Benefit to Fedora

The increased security may enable installing/activating the pmcd daemon by default.

Scope

Only the PCP packages would be modified.

The scope of changes within the PCP code base is relatively large however - addition of SSL/TLS and IPv6 to the core protocol affects all live-mode tools and daemons, for example. Early upstream point releases and the fairly extensive test suite are used to mitigate risk.

How To Test

The PCP sources include a quality assurance suite in the pcp-testsuite package with several hundred tests. Additional tests are being added as the new features are developed.

Instructions for configuring and running the tests are included in an accompanying README file.

User Experience

All changes are backwards compatible, and the user must opt-in to use the new features. For example, the SSL extensions are negotiated transparently using existing feature bits in the protocol to flag the new capability to either end of the connection. Secure connections can then be enabled via an environment variable or through explicit user interface selection.

As a second example, proposed new GFS2 metrics and monitoring utility would make use of existing GFS2 kernel instrumentation, and existing PCP interfaces for extension (on both the individual cluster nodes, as well as the remote monitoring tool). The user would explicitly install the GFS2 PCP agent on the cluster nodes, and thus augments their existing PCP installation with these new metrics and capabilities.

Dependencies

None.

Contingency Plan

In the event some of the improvements don't make it to upstream PCP in time, the then-newest version would be pulled into Fedora.

Documentation

All tools, daemons and library interfaces have accompanying man pages. The pcp-doc package also contains tutorials, howtos and other documentation and coverage of the new major features (like SSL) is being added.

Discussion is on-going with the original authors (SGI) as well, about making available the two technical books they have published about PCP in the past, under a community friendly license.

Links to each of these documents will be added here as they become available.

PCP Project Home page

Online pcp-doc manual

Release Notes

It is anticipated that the upstream release notes and documentation will provide coverage of the new features, and the Fedora release notes could link to those.

Comments and Discussion