This is just a page to collect brainwaves/ideas/evil-thoughts for Spacewalk.
Inter-satellite-sync
debuginfo sync - enable sync of debuginfo packages via satellite-sync. (Or should this be under Repo and RPM Handling?)
Enable "super-admins" to select the current working organization from a drop down menu, instead of being forced to logout and login as a specific user for that organization.
API-only user, with access to only specific API's. Or a way to login to the API from a client without having to store username/password in cleartext.
User Permissions - Discussion around implementing fine grained user permissions.
PAM authentication to be extended so that local GIDs can be mapped to organisations. --Phil
Use-case deployment - make initial enable & deployment of the following simple
gPXE to compliment Cobbler?
PostgreSQL Support - content sync, rhnpush, registration and yum operations work
make db-control usable with Oracle XE
allow system.scheduleScriptRun to work with scripts that have been saved in the database. This way scripts can be re-used and later maybe even attached to triggers like configchannel actions.
HelpSystem to make help a bit easier to work with.
Asset identification
Integration with JasperReports
Ability to control activation keys with editor and comments -- Antoine
Allow user-defined types for custom info items -- Antoine
DeltaRpmSupport
SRPM Sync to enable sync of source RPM content via satellite-sync.
New page for signing and uploading your own packages. A browse button for selecting the rpm you want to upload, then a multi-select list of channels you want to upload to. The rpm would be automatically signed by your rpm key specified in /root/.rpmmacros . --Josh
Default base channel for non-Redhat supplied channels. --heydrick bugzilla 559370
Provide a UI for folks to edit/create comps files and associated package/group entries for custom content to use with yum client
easier support for importing content from multiple distributions and managing those distributions in parallel
integration with koji -- this is building the packages in koji which will occur when we submit to Fedora.
add support for deb packages/Debian
add support for external repositories so that Spacewalk doesn't have to have a local copy of all RPMs, just retrieves the headers in the same way yum does and can direct subscribed clients to download directly from the 3rd party repo. (Proxy already does this. What is the use case that YUM covers differently?)
Provide a tree structure with a depth greater than 1 for the Software Channel Subscriptions
Provide a way to add arbitrary metadata to any given repository. Like modifyrepo does in createrepo.
download packages using torrent protocol
enable package/package group selection via a GUI which shows available package/package groups for that distribution
enable uploads of (single or max 5)RPMS into the system from the web page, so a user does not have to have a login on the console of the server - Antoine
Allow a channel to be available as a raw yum repo. This would work for building tools like mock. I often have to keep rpms around in 2 spots so I can perform mock biulds. Please, please fix this. --stahnma
Seconded, it would also make migration, manual changes easier? An export as yum repo hierarchy button somewhere? and would help with Koji integration. -- Phil
Spacewalk can serve metalink file with list of Spacewalk Proxies, from which can download package too. --msuchy
Per Channel Vars for Config Channels
Associate a config file with a remote command to allow e.g. dependent service restart after config file deployment. It should be possible to define pre or post deployment scripts.
upgrade configuration management engine? Integrate with puppet or cfengine, let's avoid enhancing our current implementation.
func instead of osad? What are the advantages/disadvantages? Is it possible?
replace ssh probes in monitoring with regular scripts from remote action (will imply usage of osad).
upgrade monitoring engine?
Addition of a GSSAPI/Kerberos authentication method in place of the RHNSD and SSH method for remote client access. Instead of providing the identity file and a user for SSHing (shared keys are banned and impractical in my environment) I'd like to use my existing automaton user and distribute his key tab so that a simple kinit would allow password-less SSH to client machines. AKA Func these days --Phil
add support for Jumpstarting Solaris
Automatic change logging of Kickstart profiles - Starting with kickstart pre/post revisioning. https://fedorahosted.org/spacewalk/wiki/KickstartScriptRevisioning details coec's current thinking on the matter.
Expand macros to have conditional logic and loops in config files using custom system info or other values stored in satellite/spacewalk. {| if rhn.system.custom_info(foo) == 'bar' display 'foo' otherwise display 'not found' |}.
Allow postinstall actions for the server. E.g. force software and configuration updates, set custom variables, send mail.
- can be already done using System details -> Software -> Install -> select some package -> Install -> Run command
I mean, postinstall of a server, not a package. the '%post' part of a kickstart if you will.
+1 for Postinstall of server. Have done this many times by writing large series of scripts which are then deployed by Config Channels via Activation Keys. Then builds up to an init.d type of environment where all scripts in this deployed directory are run. It works, but it's fiddly.
Make it possible to subscribe to Errata and create the errata to subscribe to -- red (Done? -- Phil)
/ Lots of work, but also great benefit -- red
...or maybe create an option to create stupid standard errata (like one for each update/rpm without any text, just to allow the pushing of updates to clients) automatically -- red
/ Fine enough to at least enable the pushing to the clients, but creating errata just for that?! -- red
...or make it possible to push updates/rpm to the clients instead of errata only -- red
Enables pushing of updates to clients without anyone having to write errata - might just suffice for lots of use cases -- red
Replace the current "Custom Build Content Management System" with one that is Open Source (GPL'd) like Alfresco. This could replace the legacy PERL/RPC scheme with a more current Javascript/REST scheme. Alfresco is willing to contribute to this development as there is a need for an Alfresco "Network" and we don't want to reinvent the wheel. If you would like to contact me: lee.faus at alfresco dot com.
finish migrating perl pages to Java, and remove the perl stack entirely.
Ability to save arbitrary script within satellite for reuse (be able to save a script you use a lot) -- Antoine
Manage chkconfig via a kewl webinterface on the satellite -- Antoine
Manage OpenVZ Containers
Seconded. -- Phil
Add NIM on Linux support, based largely around straight TFTP, a Network Installation Manager is used to boot, update and manage AIX servers, IBM have already packaged NIMOL in PRM form for their engineers to use on Linux laptops at client sites, unsure as to feasibility of managing spot sources and LPP in spacewalk? See links...
http://www.ibm.com/developerworks/forums/thread.jspa?messageID=13894772
streamline development process to encourage more contributions, see The Architecture of Participation: ...
decompose Spacewalk into an aggregation of OSS projects, composed of separate subprojects that can be used by other projects
continually ask the question: what use cases are new and not covered by the app because of previous datacenter focus, if any? Where can it and it's subprojects grow?
Integrate Clickheat as a method for determining how the UI is used. Determine some (optional) method to "phone home" data that can be used to aggregate usage data for future UI improvements.
Integration with some sort of FIM such as AIDE, such features as exporting the compiled database back to the spacewalk server and comparison of databases and file hashes between Groups/SSMs. I have clusters of machines that need to be kept consistent, which is harder than it sounds when some are taken out of service for developers or tweaked for special purposes. Plus security obviously. --Phil
See above about NRPE and NPC but integration with Cacti and Nagios perhaps? I know Redhat has "func" but they aren't quite the same and Nagios + Cacti + NPC is becoming an almost de-facto standard in quite a few places I've worked/consulted. --Phil
implement native systemd services.
integration with OpenSCAP.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4