mNo edit summary |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 12: | Line 12: | ||
== Owner == | == Owner == | ||
* Name: [[User: | * Name: [[User:kushal| Kushal Das]] | ||
* Name: [[User:sundaram| Rahul Sundaram]] | * Name: [[User:sundaram| Rahul Sundaram]] | ||
| Line 18: | Line 18: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/17/Schedule |Fedora 17]] (and its [[Releases/17/FeatureList |Feature List]]) | * Targeted release: [[Releases/17/Schedule |Fedora 17]] (and its [[Releases/17/FeatureList |Feature List]]) | ||
* Last updated: | * Last updated: 2012-03-20 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
[https://darkserver.fedoraproject.org Production URL] | |||
== Detailed Description == | == Detailed Description == | ||
https://fedoraproject.org/wiki/Darkserver | https://fedoraproject.org/wiki/Darkserver | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
To enable developer tools to identify exact package builds from which process images (e.g. core dumps) come. This can enable their analysis, debugging profiling, by finding out where the rpm / elf / dwarf files may be found, so they can download them. (This is even better than abrt-action-install-debuginfo-to-abrt-cache because that apparently cannot query files no longer indexed by repodata.) | |||
== Scope == | == Scope == | ||
== How To Test == | == How To Test == | ||
Devel instance URL: [http://darkserver01.dev.fedoraproject.org/darkserver/ http://darkserver01.dev.fedoraproject.org/darkserver/] | |||
== User Experience == | == User Experience == | ||
| Line 40: | Line 40: | ||
== Dependencies == | == Dependencies == | ||
Infrastructure team needs to host the service. Kevin Fenzi is working with Kushal Das on this already. | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 46: | Line 47: | ||
== Documentation == | == Documentation == | ||
Darkserver, is a Fedora service to help people finding details of build-id(s). People will be able query the service based on build-id(s) or rpm package names. The service will provide output in JSON format as it will be easier for other tools to parse the output. This release includes all the tools to make use of this service. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
| Line 51: | Line 54: | ||
[[Category: | [[Category:FeatureAcceptedF17]] | ||
<!-- 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 --> | ||
Latest revision as of 17:42, 20 March 2012
Darkserver GNU Build ID service
Summary
Darkserver is a service written to help people finding details of build-id(s). People will be able query the service based on build-id(s) or rpm package names. The service will provide output in JSON format as it will be easier for other tools to parse the output. This service will be integrated with the Fedora infrastructure and includes a web interface and koji plugin.
Owner
- Name: Kushal Das
- Name: Rahul Sundaram
Current status
- Targeted release: Fedora 17 (and its Feature List)
- Last updated: 2012-03-20
- Percentage of completion: 100%
Detailed Description
https://fedoraproject.org/wiki/Darkserver
Benefit to Fedora
To enable developer tools to identify exact package builds from which process images (e.g. core dumps) come. This can enable their analysis, debugging profiling, by finding out where the rpm / elf / dwarf files may be found, so they can download them. (This is even better than abrt-action-install-debuginfo-to-abrt-cache because that apparently cannot query files no longer indexed by repodata.)
Scope
How To Test
Devel instance URL: http://darkserver01.dev.fedoraproject.org/darkserver/
User Experience
This is a developer service and won't affect end users except in a indirect way by improving the use of tools.
Dependencies
Infrastructure team needs to host the service. Kevin Fenzi is working with Kushal Das on this already.
Contingency Plan
The service simply won't exist.
Documentation
Darkserver, is a Fedora service to help people finding details of build-id(s). People will be able query the service based on build-id(s) or rpm package names. The service will provide output in JSON format as it will be easier for other tools to parse the output. This release includes all the tools to make use of this service.