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

I was typing quickly, maybe it was confusing, but nobody said we aim to *replace* fog at all. We were discussing decoupling from Fog API inside Foreman so we could enable writing non-Fog providers, which led to more opened topics like facets, smart-proxy communication or dynflow. This would be

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

On Tue, May 23, 2017 at 10:07 AM, Ivan Necas wrote: > Timo Goebel writes: > >>> 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

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

Timo Goebel writes: >> 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