Re: [foreman-dev] Merge permissions for Katello/katello

[Justin Sherrill]

Given its been a number of days with no -1's, I've now granted you access!

Congrats!

Justin

On Tue, Oct 31, 2017 at 9:37 PM, Eric D Helms 
wrote:

> +1
>
> On Oct 31, 2017 9:10 AM, "Andrew Kofink"  wrote:
>
>> +1
>>
>> On Tue, Oct 31, 2017 at 8:17 AM, Brad Buckingham 
>> wrote:
>>
>>> +1 from me as well!
>>>
>>> On Fri, Oct 27, 2017 at 9:19 AM, John Mitsch 
>>> wrote:
>>>
 +1 from me!

 John Mitsch
 Red Hat Engineering
 (860)-967-7285 <(860)%20967-7285>
 irc: jomitsch

 On Thu, Oct 26, 2017 at 4:00 PM, Jonathon Turel 
 wrote:

> Hey folks,
>
> The time has come (through some helpful suggestions) that I should
> make my request to have $subject bestowed upon me. If you'd like to see
> some of my contributions to Katello here are my merged PRs
> 
> and PRs I've otherwise participated in
> .
> Looking forward to contributing more as I continue to come up to speed.
> What do you all think?
>
> Thanks!
>
> Jonathon
>
> --
> 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.
>

 --
 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.

>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> Andrew Kofink
>> akof...@redhat.com
>> IRC: akofink
>> Software Engineer
>> Red Hat Satellite
>>
>> --
>> 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.
>>
> --
> 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.
>

-- 
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] Merge Permissions for Katello/katello

[Eric D Helms]

+1

On Oct 31, 2017 10:17 AM, "Walden Raines"  wrote:

> +1, figured you already had merge permissions.
>
> On Tue, Oct 31, 2017 at 8:16 AM, Brad Buckingham 
> wrote:
>
>> +1 to providing Andrew with merge permissions!!
>>
>> On Fri, Oct 27, 2017 at 10:25 AM, Andrew Kofink 
>> wrote:
>>
>>> Hello,
>>>
>>> I'm not sure why I waited so long to ask, but in light of other
>>> requests, I submit my own. Here are my merged PRs
>>> ,
>>> and here are other PRs I've helped review
>>> .
>>> Do you consent to giving me the mighty power of the Green Button?
>>>
>>> Andrew
>>>
>>> --
>>> Andrew Kofink
>>> akof...@redhat.com
>>> IRC: akofink
>>> Software Engineer
>>> Red Hat Satellite
>>>
>>> --
>>> 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.
>>>
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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] Merge permissions for Katello/katello

[Eric D Helms]

+1

On Oct 31, 2017 9:10 AM, "Andrew Kofink"  wrote:

> +1
>
> On Tue, Oct 31, 2017 at 8:17 AM, Brad Buckingham 
> wrote:
>
>> +1 from me as well!
>>
>> On Fri, Oct 27, 2017 at 9:19 AM, John Mitsch  wrote:
>>
>>> +1 from me!
>>>
>>> John Mitsch
>>> Red Hat Engineering
>>> (860)-967-7285 <(860)%20967-7285>
>>> irc: jomitsch
>>>
>>> On Thu, Oct 26, 2017 at 4:00 PM, Jonathon Turel 
>>> wrote:
>>>
 Hey folks,

 The time has come (through some helpful suggestions) that I should make
 my request to have $subject bestowed upon me. If you'd like to see some of
 my contributions to Katello here are my merged PRs
 
 and PRs I've otherwise participated in
 .
 Looking forward to contributing more as I continue to come up to speed.
 What do you all think?

 Thanks!

 Jonathon

 --
 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.

>>>
>>> --
>>> 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.
>>>
>>
>> --
>> 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.
>>
>
>
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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.
>

-- 
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] Foreman instrumenting analysis

[Eric D Helms]

Before I give a full reply, can you comment, for each given library below,
which are able to run without requiring a separate process? For context, I
am thinking of the container scenario where I am running Foreman as a
single process in a container and want it to be serving up metrics for
collection.

On Tue, Oct 31, 2017 at 3:33 PM, Lukas Zapletal  wrote:

> Hello,
>
> I am seeking for app instrumenting protocol for Foreman Rails
> application that will fulfill the following requirements:
>
> The protocol must work with multi-process server like Passneger.
> The protocol can be easily integrated into Foreman Tasks and Smart Proxy.
> The protocol or agent must support aggregation of time-based data
> (quantiles, average).
> The protocol must integrate with top three open-source monitoring
> frameworks.
>
> Let me summarize my findings so far. I am looking for advice or
> comments on this topic. I already worked on some prototypes, but
> before I commit to some final solution, I want to be sure I will not
> miss something I don't know about.
>
> Before you send comments, please keep in mind I am not searching for
> monitoring solution to integrate with. I want an application
> instrumentation library (or protocol) to be able export measurements
> (or telemetry data if you like) from Rails (like number or requests
> processed, SQL queries, time spent in db or view, time spent rendering
> a template or calling a backend system).
>
>
> Prometheus
>
>
> Flexible text-based protocol (alternatively protobuf) with HTTP
> REST-like communication. It was designed to be pull-based, meaning
> that an agent makes HTTP calls to web application which holds all
> metrics until they are flushed. It was build for Prometheus monitoring
> framework (Apache licenced) created by SoundCloud initially. Server
> and most agents are written in Go, can run without external database
> or export into 3rd party storage backends.
>
>
> It looks great, but it has a major problem - the Ruby client library
> (called client_ruby) does not support multi-process web servers at
> all. There are some hacks but these are using local temp files or
> shared memory with rather bad benchmark results (see the links down
> below).
>
>
> There is a possibility to push metrics into a separate component
> called PushGateway, but this was created for things like cron jobs or
> rake tasks. Doing multiple HTTP requests for each metric per single
> app request will unlikely perform well. In the README authors have
> note that this should be considered as "temporary solution".
>
>
> Although Prometheus seems to have vibrant community, the Ruby library
> development pace slowed down as SoundCloud "does not use many Ruby
> apps anymore". But it is still a good option to have.
>
>
> https://prometheus.io
> https://prometheus.io/docs/instrumenting/pushing/
> https://github.com/prometheus/client_ruby
> https://github.com/prometheus/client_ruby/issues/9
> https://github.com/prometheus/client_ruby/commits/multiprocess
>
>
> OpenTSDB
>
>
> OpenTSDB consists of a Time Series Daemon (TSD) as well as set of
> command line utilities. Interaction with OpenTSDB is primarily
> achieved by running one or more of the TSDs. Each TSD is independent.
> There is no master, no shared state so you can run as many TSDs as
> required to handle any load you throw at it. Each TSD uses the open
> source database Hadoop/HBase or hosted Google Bigtable service to
> store and retrieve time-series data.
>
>
> It uses push mechanism via REST JSON API with alternative
> "telnet-like" text endpoint. Although it does have some agents, it is
> more used as a storage backend than end-to-end monitoring solution.
>
>
> http://opentsdb.net/overview.html
>
>
> Statsd
>
>
> Main idea behind this instrumentation protocol is simple - get the
> measurement out of the application as fast as possible using UDP
> datagram. A collector agent usually runs locally, it does aggregation
> and relays the measurements to target backend system. The vanilla
> version does not support tagging, but there are extensions or mappings
> possible to support that.
>
>
> Almost all monitoring platforms has some kind of
> agent/importer/exporter that talks via statsd. The original statsd
> daemon was written in Perl years ago, then it was re-popularized by
> node.js implementation, but there are many alternative agents from
> which the most promising is statsite with very easy extensibility.
>
>
> This protocol is my favourite because it plays well with multiprocess
> Ruby servers or other Foreman components (all can just send UDP
> packets to localhost) and it also takes all aggregation and storing
> temporary data out of Ruby application. It also brings chances of
> regressions in our codebase to bare minimum - in the worst case the
> aggregating agent can fail but UDP packets will simply get lost
> without interrupting the application. The best Ruby client library
> seems to be statsd-instrument actively 

[foreman-dev] Foreman instrumenting analysis

[Lukas Zapletal]

Hello,

I am seeking for app instrumenting protocol for Foreman Rails
application that will fulfill the following requirements:

The protocol must work with multi-process server like Passneger.
The protocol can be easily integrated into Foreman Tasks and Smart Proxy.
The protocol or agent must support aggregation of time-based data
(quantiles, average).
The protocol must integrate with top three open-source monitoring frameworks.

Let me summarize my findings so far. I am looking for advice or
comments on this topic. I already worked on some prototypes, but
before I commit to some final solution, I want to be sure I will not
miss something I don't know about.

Before you send comments, please keep in mind I am not searching for
monitoring solution to integrate with. I want an application
instrumentation library (or protocol) to be able export measurements
(or telemetry data if you like) from Rails (like number or requests
processed, SQL queries, time spent in db or view, time spent rendering
a template or calling a backend system).


Prometheus


Flexible text-based protocol (alternatively protobuf) with HTTP
REST-like communication. It was designed to be pull-based, meaning
that an agent makes HTTP calls to web application which holds all
metrics until they are flushed. It was build for Prometheus monitoring
framework (Apache licenced) created by SoundCloud initially. Server
and most agents are written in Go, can run without external database
or export into 3rd party storage backends.


It looks great, but it has a major problem - the Ruby client library
(called client_ruby) does not support multi-process web servers at
all. There are some hacks but these are using local temp files or
shared memory with rather bad benchmark results (see the links down
below).


There is a possibility to push metrics into a separate component
called PushGateway, but this was created for things like cron jobs or
rake tasks. Doing multiple HTTP requests for each metric per single
app request will unlikely perform well. In the README authors have
note that this should be considered as "temporary solution".


Although Prometheus seems to have vibrant community, the Ruby library
development pace slowed down as SoundCloud "does not use many Ruby
apps anymore". But it is still a good option to have.


https://prometheus.io
https://prometheus.io/docs/instrumenting/pushing/
https://github.com/prometheus/client_ruby
https://github.com/prometheus/client_ruby/issues/9
https://github.com/prometheus/client_ruby/commits/multiprocess


OpenTSDB


OpenTSDB consists of a Time Series Daemon (TSD) as well as set of
command line utilities. Interaction with OpenTSDB is primarily
achieved by running one or more of the TSDs. Each TSD is independent.
There is no master, no shared state so you can run as many TSDs as
required to handle any load you throw at it. Each TSD uses the open
source database Hadoop/HBase or hosted Google Bigtable service to
store and retrieve time-series data.


It uses push mechanism via REST JSON API with alternative
"telnet-like" text endpoint. Although it does have some agents, it is
more used as a storage backend than end-to-end monitoring solution.


http://opentsdb.net/overview.html


Statsd


Main idea behind this instrumentation protocol is simple - get the
measurement out of the application as fast as possible using UDP
datagram. A collector agent usually runs locally, it does aggregation
and relays the measurements to target backend system. The vanilla
version does not support tagging, but there are extensions or mappings
possible to support that.


Almost all monitoring platforms has some kind of
agent/importer/exporter that talks via statsd. The original statsd
daemon was written in Perl years ago, then it was re-popularized by
node.js implementation, but there are many alternative agents from
which the most promising is statsite with very easy extensibility.


This protocol is my favourite because it plays well with multiprocess
Ruby servers or other Foreman components (all can just send UDP
packets to localhost) and it also takes all aggregation and storing
temporary data out of Ruby application. It also brings chances of
regressions in our codebase to bare minimum - in the worst case the
aggregating agent can fail but UDP packets will simply get lost
without interrupting the application. The best Ruby client library
seems to be statsd-instrument actively maintained by Shopify, it is
very small without any runtime dependency.


https://github.com/etsy/statsd/blob/master/docs/metric_types.md
https://github.com/Shopify/statsd-instrument
https://github.com/prometheus/statsd_exporter
https://github.com/statsite/statsite
https://codeascraft.com/2011/02/15/measure-anything-measure-everything/


New Relic, Instrumental, DataDog, Rollbar


All are paid services, some clients are open-source (Instrumental is
MIT licenced) but usually with not well documented protocol and worse
integration to different monitoring 

Re: [foreman-dev] I am happy to write the headline release notes

[Tomer Brisker]

Hi Bryan,
The list of issues can be found here:
http://projects.theforeman.org/projects/foreman/issues?utf8=%E2%9C%93_filter=1%5B%5D=release_id%5Brelease_id%5D=%3D%5Brelease_id%5D%5B%5D=240


On Tue, Oct 31, 2017 at 4:45 PM, Bryan Kearney  wrote:
> I would like to know the details of the headline features in 1.16 [1]. I
> would be happy to write the text and put int he PR if the authors can
> point me at the issues. I can then run it bye you guys for edits.
>
> -- bk
>
>
> [1] https://theforeman.org/manuals/1.16/index.html#Headlinefeatures
>
> --
> 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.



-- 
Have a nice day,
Tomer Brisker
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.

Re: [foreman-dev] 1.17 schedule

[Greg Sutcliffe]

On Tue, 2017-10-31 at 13:11 +0100, Marek Hulán wrote:
> I think the date is reasonable. Given we have 2-3 RCs per 2 weeks, we
> could expect 1.17 release early next year right? Which I think is
> good since we'll have time to fix potential blockers after we're back
> from Christmas time off.

1.16 has obviously been a blip, but normally we have 1 RC / 2 weeks.
That would put the first RC around Dec 15th, and a second at the end of
the year, if there's anyone around to work on it. Allowing for slippage
/ potential RC3, it'll be out before Devconf, which is nice timing.

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.


signature.asc
Description: This is a digitally signed message part

[foreman-dev] I am happy to write the headline release notes

[Bryan Kearney]

I would like to know the details of the headline features in 1.16 [1]. I
would be happy to write the text and put int he PR if the authors can
point me at the issues. I can then run it bye you guys for edits.

-- bk


[1] https://theforeman.org/manuals/1.16/index.html#Headlinefeatures

-- 
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] Merge Permissions for Katello/katello

[Walden Raines]

+1, figured you already had merge permissions.

On Tue, Oct 31, 2017 at 8:16 AM, Brad Buckingham 
wrote:

> +1 to providing Andrew with merge permissions!!
>
> On Fri, Oct 27, 2017 at 10:25 AM, Andrew Kofink 
> wrote:
>
>> Hello,
>>
>> I'm not sure why I waited so long to ask, but in light of other requests,
>> I submit my own. Here are my merged PRs
>> ,
>> and here are other PRs I've helped review
>> .
>> Do you consent to giving me the mighty power of the Green Button?
>>
>> Andrew
>>
>> --
>> Andrew Kofink
>> akof...@redhat.com
>> IRC: akofink
>> Software Engineer
>> Red Hat Satellite
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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] Merge permissions for Katello/katello

[Andrew Kofink]

+1

On Tue, Oct 31, 2017 at 8:17 AM, Brad Buckingham 
wrote:

> +1 from me as well!
>
> On Fri, Oct 27, 2017 at 9:19 AM, John Mitsch  wrote:
>
>> +1 from me!
>>
>> John Mitsch
>> Red Hat Engineering
>> (860)-967-7285 <(860)%20967-7285>
>> irc: jomitsch
>>
>> On Thu, Oct 26, 2017 at 4:00 PM, Jonathon Turel  wrote:
>>
>>> Hey folks,
>>>
>>> The time has come (through some helpful suggestions) that I should make
>>> my request to have $subject bestowed upon me. If you'd like to see some of
>>> my contributions to Katello here are my merged PRs
>>> 
>>> and PRs I've otherwise participated in
>>> .
>>> Looking forward to contributing more as I continue to come up to speed.
>>> What do you all think?
>>>
>>> Thanks!
>>>
>>> Jonathon
>>>
>>> --
>>> 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.
>>>
>>
>> --
>> 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.
>>
>
> --
> 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.
>



-- 
Andrew Kofink
akof...@redhat.com
IRC: akofink
Software Engineer
Red Hat Satellite

-- 
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] Merge permissions for Katello/katello

[Brad Buckingham]

+1 from me as well!

On Fri, Oct 27, 2017 at 9:19 AM, John Mitsch  wrote:

> +1 from me!
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285 <(860)%20967-7285>
> irc: jomitsch
>
> On Thu, Oct 26, 2017 at 4:00 PM, Jonathon Turel  wrote:
>
>> Hey folks,
>>
>> The time has come (through some helpful suggestions) that I should make
>> my request to have $subject bestowed upon me. If you'd like to see some of
>> my contributions to Katello here are my merged PRs
>> 
>> and PRs I've otherwise participated in
>> .
>> Looking forward to contributing more as I continue to come up to speed.
>> What do you all think?
>>
>> Thanks!
>>
>> Jonathon
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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] Merge Permissions for Katello/katello

[Brad Buckingham]

+1 to providing Andrew with merge permissions!!

On Fri, Oct 27, 2017 at 10:25 AM, Andrew Kofink  wrote:

> Hello,
>
> I'm not sure why I waited so long to ask, but in light of other requests,
> I submit my own. Here are my merged PRs
> ,
> and here are other PRs I've helped review
> .
> Do you consent to giving me the mighty power of the Green Button?
>
> Andrew
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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.
>

-- 
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] 1.17 schedule

[Marek Hulán]

I think the date is reasonable. Given we have 2-3 RCs per 2 weeks, we could 
expect 1.17 release early next year right? Which I think is good since we'll 
have time to fix potential blockers after we're back from Christmas time off.

--
Marek

On úterý 31. října 2017 12:59:12 CET Ohad Levy wrote:
> On Tue, Oct 31, 2017 at 1:48 PM, Ondrej Prazak  wrote:
> > Hi,
> > based on the Redmine release dates [1], 1.17 is supposed to be branched on
> > December 1st. Do we want to stick to this plan or do we want to take into
> > account that 1.16 was delayed?
> > 
> > Let me know what you think,
> 
> Given the fact that we already branched 1.16 in September, I personally
> would like to keep the dates.
> 
> Ondra
> 
> > [1] http://projects.theforeman.org/rb/releases/foreman
> > 
> > --
> > 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.


-- 
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] 1.17 schedule

[Ohad Levy]

On Tue, Oct 31, 2017 at 1:48 PM, Ondrej Prazak  wrote:

> Hi,
> based on the Redmine release dates [1], 1.17 is supposed to be branched on
> December 1st. Do we want to stick to this plan or do we want to take into
> account that 1.16 was delayed?
>
> Let me know what you think,
>

Given the fact that we already branched 1.16 in September, I personally
would like to keep the dates.

Ondra
>
> [1] http://projects.theforeman.org/rb/releases/foreman
>
> --
> 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.
>

-- 
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] 1.17 schedule

[Ondrej Prazak]

Hi,
based on the Redmine release dates [1], 1.17 is supposed to be branched on
December 1st. Do we want to stick to this plan or do we want to take into
account that 1.16 was delayed?

Let me know what you think,
Ondra

[1] http://projects.theforeman.org/rb/releases/foreman

-- 
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] Koji builder crash - days after

[Lukas Zapletal]

Guys,

I configured logwatch on Koji as well, cron output and logwatch is
currently being delivered to my Red Hat address. It looks like Postfix
is able to deliver to redhat.com emails just fine, but when I tested
this with gmail.com it did not work out.

Do we have some infra mailing list for this kind of mails? Anyone else
want to get these emails?

If we decide to puppetize, let's make sure this is under puppet control.

LZ

On Mon, Oct 30, 2017 at 11:33 AM, Greg Sutcliffe
 wrote:
> Hey
>
> On Mon, 2017-10-30 at 10:22 +0100, Lukas Zapletal wrote:
>> After several hours of outage, we were able to bring it up by
>> mounting the volume in a temporary VM, editing /etc/fstab and
>> starting new instance.
>
> Thanks for the effort, especially on a Friday!
>
>> Started new wiki page where we have this information:
>>
>> http://projects.theforeman.org/projects/foreman/wiki/KojiSetup
>
> Good idea.
>
>> There were voices on the IRC to puppetize this server, I am not
>> against and feel free to add this to todo. It does not make much
>> sense IMHO to puppetize koji setup, but things like setting up ssh
>> keys or basic services can be useful.
>
> That was me, and yeah, just setting up the usual base classes will mean
> that the infra team have access (handy if you're away) and all the
> boring stuff is taken care of. One area that it might also help is
> adding Koji into our wider backup system (I don't think we can move the
> Koji files backup, but the Psql backups could be moved offsite, just in
> case)
>
> I can try to find time for this, but I'll need my key[1] adding in that
> case. No promises though - as you say, it's low priority.
>
> 1 http://emeraldreverie.org/about#sshkeys
>
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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.