Re: [foreman-dev] Dropping Fedora 24 packages
I went ahead an opened a PR to remove this in preparation [1]. We don't have any official policies that I can think of for how long to let this discussion sit before pulling the trigger. As ewoud points out, we should split the "dropping Fedora all together" into its own discussion. I think this one is a bit less controversial with F26 out. [1] https://github.com/theforeman/foreman-packaging/pull/1725 On Wed, Jul 12, 2017 at 8:20 PM, Eric D Helms wrote: > This gets a +1 from me due to the fact that Fedora 24 is now no longer in > support mode and the low percentage of users using Fedora in general. This > would reduce our overall overhead of support. > > > Eric > > On Wed, Jul 12, 2017 at 10:58 AM, Greg Sutcliffe > wrote: > >> Forgot to add a link: >> >> https://theforeman.org/2017/03/2017-foreman-survey-analysis.html#page1 >> >> Page down to the first table (not pie chart) in that section. >> >> Greg >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Eric D. Helms > Red Hat Engineering > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Proposal/Request - Foreman Ansible plugin - Dynamic inventory parameters definition
Hi, first of all, I'd like to thank you for the great work you've done so far. I really admire all of you guys. My programming skills are not so good so I'll only lend my hand in proposing an idea or two that might be useful. Before I run Ansible role directly I can specify certain connection parameters in an Ansible inventory file. As you know the same option is available in the Foreman GUI interface via parameters (Global parameters, Host group parameters etc.). However, there is one limitation and that is the list of parameters administrators can specify is limited. To get an idea which parameters are available one can take a look in the following ruby scripts /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-1.4.5/app/services/foreman_ansible/inventory_creator.rb and /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible-1.4.5/app/models/setting/ansible.rb . The problem arise when somebody needs a parameter that is not listed there. Okay, you can edit both above mentioned scripts and then restart Foreman, but every time the official update is applied, you have to add all necessary code changes again. This sucks and I believe everyone agrees with me. So the idea I'd suggest is that, let administrators define what parameter they need/want without hard-coding into Foreman Ansible plugin ruby scripts, OR make them hard-coded but the list of available parameter must be complete. What do you think? -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Weekly Dev/Design Meeting: Bookmarks and Search
https://docs.google.com/document/d/18RiZASVbRuh9Iuz2OBvzJc4e8H1243IVmhNneBYNsPw/edit Search and Bookmarks Presented by Tomer - Ensure what you can filter by is relevant to the user to reduce items in list that will have no value. - I’ve seen alternate operators… such as in the screen below. Ensure that none are duplicates. I’m not an expert on these operators but if one standard language of operator could be used, that would be better. - - Change error to “Architecturs” not recognized. It is redundant to mention searching since they are already in in a search field. - I have a proposed design for search that would be more consistent with patternfly and add additional functionality here depending on permission. See below, feel free to provide feedback. - Perhaps have Public not be default and also add inline help to define what Public is. - Is there any checking to see if duplicate names or searches are entered? - Gray line bounding box should be removed within modal. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] plugin configuration management
Hello, ansible plugin does not contact any external service to my knowledge except for smart proxy, chef plugin uses REST API to talk to smart proxy which then uses REST API to talk to chef server. Hope this helps -- Marek On středa 12. července 2017 17:21:49 CEST Fairouz el ouazi wrote: > Hi , > > I want to know if foreman plugin (ansible or chef ) communicate > with the configuration management server or platform (chef or ansible ) > using theirs rest Api ? > > Thanks -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
