[foreman-dev] Re: Re: Re: Nominating Timo Goebel for theforeman/foreman commit access

days left if you have any objections or comments! Done! Welcome to the core team and may Jenkins help you with your code reviews :) On 06/02, Daniel Lobato Garcia wrote: Hi devs, I'd like to nominate Timo Goebel (timogoebel on Github & IRC) for commit access to theforeman/foreman repo. He's

Re: [foreman-dev] Development of new plugin - assets

> On 04.07.2016, at 09:00, Dominic Cleal wrote: > >> On 04/07/16 03:00, Matthew Ceroni wrote: >> I am attempting to develop a plugin. >> >> The main functionality of the plugin is going to be to automatically set >> the Virtual machine network based off the subnet set on the

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

Hi, > our design of template proxying is not good I don't think, it's that bad. Your suggestion does have it's advantages, though. From a security perspective it would be great if the smart-proxy wouldn't need any calls to Foreman. > The downside is that Smart Proxy would be required in

[foreman-dev] Re: Seeding templates overrides custom changes - should we lock templates we ship?

+1 to locking. This is the only workflow that makes sense imho. Please note, that we need [1] merged first. - Timo [1] https://github.com/theforeman/foreman/pull/4283 Am Freitag, 17. Februar 2017 15:05:13 UTC+1 schrieb Marek Hulán: > > Hello foreman-devs, > > recently I was told about the bug

Re: [foreman-dev] Re: Automate IP allocation over specifying subnets in machine creation

On 31.08.2016, at 12:45, Lukas Zapletal wrote: >> BTW I also tried to work with the API of "Free IP" but couldn't managed to >> authenticate properly, can you give me an example of how to use it? >> that way we could use the workaround I spoke of before... > > The proxy API

Re: [foreman-dev] Diploma projects - need ideas

Am 05.10.16 um 14:55 schrieb Ewoud Kohl van Wijngaarden: On Wed, Oct 05, 2016 at 08:35:49AM -0400, Bryan Kearney wrote: On 09/29/2016 11:57 AM, Lukas Zapletal wrote: Hello, few students of mine are considering doing Diploma Thesis for Red Hat. Can you figure out some good Foreman topics?

[foreman-dev] HoundCI - annoying?

Hi devs, I'm usually not very easily annoyed. What get's me started though eventually is when things don't work properly. HoundCI is one of those things. My main concern is, that I get an e-mail and/or Github notification for every single comment. These can easily be ten or more e-mails.

Re: [foreman-dev] Unify date format in Foreman and plugins

Am 12.04.17 um 18:21 schrieb Ewoud Kohl van Wijngaarden: On Wed, Apr 12, 2017 at 06:02:34PM +0200, Marek Hulán wrote: Thanks guys so far, I'm sending comments below in text that are also relevant for lzap's comments in previous email. On středa 12. dubna 2017 16:56:52 CEST Ewoud Kohl van

Re: [foreman-dev] Hosting katello repos on yum.theforeman.org

Am 09.03.17 um 17:54 schrieb Greg Sutcliffe: I do think bandwidth/traffic may be an issue, as we already (I believe) consume a large proportion of our Rackspace budget on the existing packages. If that's the only reason we're not doing it, I'd consider using cloudflare.com as a

Re: [foreman-dev] Aligning Foreman & Katello git repositories

Sounds very good to me. Let's do this and find solutions for problems as we go. If bandwidth is an issue, Cloudflare CDN might be worth checking out for the packages. Timo > On 2. Aug 2017, at 14:33, Ewoud Kohl van Wijngaarden > wrote: > > Hello all, > > As many

Re: [foreman-dev] Icon Feedback

In my opinion, the infrastructure icon looks unintuitive. How about some kind of treeview? The rest looks good and straightforward to me. Timo > On 14. Aug 2017, at 21:10, Roxanne Hoover wrote: > > Visual Design took a pass at the icons in vertical nav. Anyone have any >

Re: [foreman-dev] Looking for facts from big servers

Hi, Thanks to my co-worker Till: Here you go. https://gist.github.com/timogoebel/11a928f297fbef98f15b643612a9d6e6 Facts from a VM with lots of CPU and memory and a physical host with some harddisks. Hope, that helps. Curious to see some screenshots. Discovery UI refresh is long overdue. :-)

Re: [foreman-dev] Nomination for an additional GitHub org owner

+1 for both Eric and Greg. Keep up the good work. > On 29. Jun 2017, at 13:05, Daniel Lobato Garcia wrote: > >> On 06/29, Tomer Brisker wrote: >> Well, how about our fearless community leader? >> Makes sense to me that managing the community includes the github repos >>

Re: [foreman-dev] Katello pulp_export_destination checks happen inside the application

Am 20.08.17 um 22:39 schrieb Ewoud Kohl van Wijngaarden: I think if Pulp took a parameter to publish to a non-default location, we would not need to do the extra copy step that ties Katello and Pulp closely together. Currently it is needed because we need the export to land in

Re: [foreman-dev] [Infra] Reducing Test Matrix

Am 23.08.17 um 01:44 schrieb Eric D Helms: I would like to propose the following: 1) We drop sqlite3 entirely 2) We test all rubies on postgresql only 3) We pick the most widely used Ruby version and test mysql with that I think, Jenkins pipelines are a good thing and can make the Job

Re: [foreman-dev] vmware html5 console support

Am Montag, 8. Mai 2017 18:27:58 UTC+2 schrieb Michael Eklund: > > I would be happy to help with testing. IMO this is a killer feature. > I created some code to test this. [1] Unfortunately pre-authentication does not work with vsphere > 6 as it always requires SSO. Great idea, but it does not

Re: [foreman-dev] Moments of Coffee Meeting: Fog and Compute Resrouces NG

> On 22. May 2017, at 12:27, Ohad Levy wrote: > > Since we get a lot of lift from fog, especially for popular providers (e.g. > ec2) IMHO its not a good idea to remove fog, which means that we balance > between community contributions to fog (e.g. stuff we won't "enjoy"

Re: [foreman-dev] Requesting discovery test for core PRs

... have you considered using some kind of a CDN for downloads, e.g. cloudflare, if traffic is a concern? Timo > On 27. Sep 2017, at 17:42, Greg Sutcliffe wrote: > >> On Wed, 2017-09-27 at 17:32 +0200, Michael Moll wrote: >> >>> This would be PR-blocking, I assume?

Re: [foreman-dev] Release process & permissions

... isn‘t continuous delivery old these days? Why aren‘t we doing it? I vote in favor of automating this. This ensures predictable results and hopefully makes this process easier. To be honest: The current process scares me. Same for plugin releases. They also are way too manual right now. Timo

Re: [foreman-dev] Changing PR processor introduction text

... do you just want to print some general hints for users for every new PR? Or actively check that and automatically complain on every push? I think prprocessor is already too chatty for my taste. Maybe a Github PR Template could help as an alternative? Timo > On 31. Aug 2017, at 10:22, Lukas

Re: [foreman-dev] [infra] Packaging reorganization

I am wondering if we should name the katello-client repository either foreman-client or just client. I can think of more plugins that need a client package. Timo > On 2. Sep 2017, at 01:48, Eric D Helms wrote: > > Howdy, > > As a lead-in to being working towards

Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes

Hi Lisa, The Foreman dev setup basically needs two webservers running: One to serve the rails app via http and one to server webpacked javascript code. I suspect, that the connection to the latter does not work. The two webservers are started using foreman (not "our forman", but a process

Re: [foreman-dev] Merge permissions to foreman-packaging

+1 > On 24. Oct 2017, at 07:33, Ondrej Prazak wrote: > > +1 > >> On Mon, Oct 23, 2017 at 9:49 PM, Marek Hulan wrote: >> +1, I remember you've helped me many times. >> >> -- >> Marek >> >> >> >> On October 23, 2017 6:16:48 PM Ewoud Kohl van

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

... I think we should take increasing the major version as a chance and remove some old compatibility stuff with it like e.g. APIv1. Or fix some APIv2 inconsistencies. Maybe we could move foreman tasks to core. Just some suggestions. Just increasing the major version is in, but I think just a

Re: [foreman-dev] Possible to allow public access to finish templates?

Hi Martin, Check out the foreman_userdata plugin. That might be what you need. It was made to make vmware image deployments more fun. The README on github has more detail. Timo > On 19. Dec 2017, at 11:48, 'Martin Juhl' via foreman-dev > wrote: > > Hi > > >

Re: [foreman-dev] DHCP filename option no longer honored

: http://projects.theforeman.org/issues/21975 This breaks UEFI provisioning. I git-bisected commit e75df1dd3cc30bff2832d337b5bc20bd822e209a Refs: Author: Timo Goebel <m...@timogoebel.name> AuthorDate: Wed Oct 25 16:26:01 2017 +0200 Commit: Dmitri Dolguikh <witlessb...@

[foreman-dev] Re: New form helpers and reusing definitions from server side

Marek, Thanks for bringing this up. I think you raised some good points and I do agree, these are pain points. But I do prefer an iterative approach here, where we don't get it perfect on the first spot. How can we be sure, what we really need by not experimenting a bit? In my opinion, the

[foreman-dev] Re: [UX] Facets and Host UI - roadmap discussion.

I have been playing with Facets the last few weeks and must say, that they are really great. It's pretty easy to add dedicated functionality to the host model and I want to use that for some of my plugins (Omaha, Monitoring, something new, ...). Everything is great so far except for the missing

Re: [foreman-dev] Abandoned plugins under theforeman github org

... i would not remove it from the github org. There are even more abandoned plugins there. I would not delete the code, maybe somebody wants to start work on them again. I would mark them as unmaintained in the repo description, remove the jenkins jobs and remove them from packaging. Timo

Re: [foreman-dev] RFC: File audit for template rendering

I don't think, this is a good idea. Storing files on the local filesystem is generally consideres an anti-pattern imho. Both for web applications and expecially in a container world. In a clustered setup, you'd have to attach some kind of shared-storage to the foreman hosts to make this work.

Re: [foreman-dev] Nominating additional maintainers in foreman-core

Yes, please. We can use all the help we can get and both Shimon and Michael are doing great work. Thanks Tomer for bringing this up. > On 7. Dec 2017, at 09:23, Ondrej Prazak wrote: > > +1 to both > >> On Wed, Dec 6, 2017 at 5:19 PM, Ivan Necas wrote: