New Reports Planned Enhancements

[hagedorn]

• Create new statistics module in server that directly stores data in database rather than intermediary XML files.
• Provide e-mail functionality
• Provide user accounts and customized displays for each user that logs in. This will provide an interface to configure e-mail as well.
• Provide the ability to filter by groups of clients rather than all clients on Summary page. This should savable per user-account
• Modify URLs so the application can be served at a URL other than /; any subdirectory should be fine.

[hagedorn]

• add Packages/config items main menu category, for search by config item name/different perspective to find issues with system

[hagedorn]

Replying to hagedorn:

• add Packages/config items main menu category, for search by config item name/different perspective to find issues with system

This was added quite a while ago, just updating the ticket to note it.

[hagedorn]

• Modify URLs so the application can be served at a URL other than /; any subdirectory should be fine.

This was fixed in r3365 , but remains untested.

[…]

The Urls was not put in a django way, i suggest using the facilities that django uses, so we can use it in a much greater infrastructure. And other's could do webapps that will plug-in somehow with bcfg2.

the django ways is : top urls.py urlpatterns = patterns(,

(r'^{rootofproject$', 'Bcfg2.Server.Reports.reports.urls'),}

)

bcfg2 urls.py urlpatterns = parterns(,

(r'^{*$', 'Bcfg2.Server.Reports.reports.views.index'), [...]}

)

Reference : ​http://www.djangoproject.com/documentation/0.95/url_dispatch/#id1

[…]

A patch that fix Url in a way that is friendly with the django way

[solj]

See also ticket #433

[desai]

This level of development isn't going to happen in the old new reporting system.