Roadmap meeting Dec 05 2011 » History » Revision 57
Revision 56 (Romain Vrignaud, 12/05/2011 04:27 PM) → Revision 57/63 (Romain Vrignaud, 12/05/2011 04:38 PM)
h1. Roadmap meeting Please add your own wishlist here, we would review these topics during the meeting, Order has no meaning. h2. Dec 05 2011 : 7pm UTC on #theforeman (Freenode) h3. Important Issues to review * Mcollective integration * Pulp Admin integration * Parameterized classes support (#832) * Controlling the BMC through IPMI ** control boot order ** power controls * Remove dependency of virt in foreman ** make a more generic layer that allows for any 3rd party virtualization tools (ovirt, virt, libvirt, aws, fog, ...) * ESX support * Ruby version support * create external service for 3rd party tools ** wrapper service that acts as the middle man to talk to foreman and 3rd party tools ** Can handle compatibility better ** Better security **** Security related issues, that so far have been handled outside Foreman, like restricting who can POST Reports and Facts. Ideally Foreman should handle them. #1169 * [[Password Encryption]] * DB data versioning (Templates, parameters, etc - possibility to revert to a previous state) * Cloud provisioning and unattended access/security related (#969) * Audits to Hostgroups/Classes/Parameters/Provisioning should have be displayed on the Dashboard, perhaps with some Visualization? * host roles that were originally possible with puppet before adding the ENC. Roles can be assigned to host or hostgroups with a (one-to-many) relationship. * Full working unattended installations via proxy * Support NonSql Databases (redis,mongo...) * Add scheduling #1249 * Discuss about new UI in Foreman (from 0.3 -> 0.4) - Fixed size columns ... * Discuss new SHA-512 passwords used (default) IN EL6 (foreman didn't seem to support it as last look) * Bulk uploading client paramaters, rather than editing 1 field at a time for a new host, hostgroup, domain, etc. * Alerting foreman that a host has completed provisioning when behind NAT h3. Organizational topics * Git and Release maintenance * Packaging * Puppet-Foreman deployment recipes - Isolate namespace (as in : http://bit.ly/sFabPs) ? Or not ? * Bug/Feature reviews h2. Dec 05 2011 : Report : h3. Mcollective # functionality exposed in UI : * simple action : puppet kicks, services management * handled by proxy * optional h3. Pulp / Katello * Relation with Foreman should be more precise * Katello doesn't support non RPM disto * Maybe we could try a simple repo management * Functionnality wished : ** Assigning repo to host ** Pull updated * Mainly UI work h3. BMC support * Functionnality wished : ** Power on/off ** Boot order * Should be handled by proxy using IPMI (freeIPMI ?) * Look at otherproject : https://github.com/dellcloudedge/barclamp-ipmi h3. Remove virt dependency * Can not talk to 'a cloud' * Dividing system into : ** Physical ** Virtual * Major code refactoring * Remove dependency on a particular gem and have 3d party integration (libvirt, virt, fog, ec2, ovirt) h3. Password encrytion * Use gpg encryption ? (maybe with hiera support) * Store gpg encrypted sensitive information and decrypt it on the fly when used * See http://rubygems.org/gems/attr_encrypted h3. db versionning * Maybe use GIT as a versionning backend * Use only db versionning system h3. Cloud unattended support * proxy should handle unattended installation not foreman ? * How to solve NAT problem * Client should not talk to foreman during unattended installation * We should track host deployed by foreman with an uuid h3. Audits to Hostgroups/Classes/Parameters/Provisioning should be displayed on the Dashboard * How to track puppet manifest modification * Store puppet manifest in a VCS h3. Redesign role management * Creation of a role server * Allow multiple hostgroup assignment to a signe host => to be discussed