Re: [foreman-dev] Re: Deprecate EL6?

[Stefan Lasiewski]

Sure, I understand that EL6 will supported for 6 more months with 1.12; but
it sounds like it could get dropped in 1.13 towards the end of the year,
and this would require migrating from an old host to a new EL7 host. I'm
just saying that some pointers on migrating Foreman from one host to
another could be very helpful.

Thanks for the helpful docs to help with migrating from Puppet 3 to 4 [1].

-= Stefan

[1]
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4

On Fri, Jun 10, 2016 at 12:58 PM, Michael Moll  wrote:

> Hi,
>
> On Fri, Jun 10, 2016 at 12:05:37PM -0700, Stefan Lasiewski wrote:
> > Also, keep in mind that this work would happen at the same time that many
> > Foreman users migrate from Puppet 3.8 to Puppet 4. That's two largish,
> > forced migrations at the same time. We've been holding off on our Puppet
> 4
> > upgrade until there is support in Foreman 1.12, and I suspect other
> admins
> > are in the same boat.
>
> 1.12 is still supported on RHEL6 just fine, so there's no problem to
> update Foreman to 1.12 with Puppet 3.x and then update Puppet to 4.x.
>
> Regards
> --
> Michael Moll
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "foreman-dev" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-dev/xp8_m8nHrNE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Stefan Lasiewski Email: stef...@nersc.gov
Computer System Engineer IIIEmail: slasiew...@lbl.gov
NERSC Data Infrastructure Group

National Energy Research Scientific Computing Center (NERSC
)
Lawrence Berkeley National Laboratory

-- 
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 Sentry plugin

[Brandon Weeks]

As a start I've uploaded it to RubyGems, I'll take a look at 
foreman-packaging to get it built into deps/rpms.

[0] https://rubygems.org/gems/foreman_sentry

On Friday, June 10, 2016 at 1:11:41 AM UTC-7, Ewoud Kohl van Wijngaarden 
wrote:
>
> On Thu, Jun 09, 2016 at 05:07:14PM -0700, Brandon Weeks wrote: 
> > At Square we use Sentry  for exception tracking 
> > across all of our internal applications. To help my team detect and 
> resolve 
> > problems with our Foreman environment I created foreman_sentry 
> > , a small plugin that 
> loads 
> > Raven , the Sentry client for 
> > Ruby. While the hosted version of Sentry is a paid product, the project 
> > itself is open source  and is free 
> to 
> > host yourself. 
>
> As another Sentry user I think this is very interesting. Any plans to 
> package it? 
>

-- 
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] Re: Deprecate EL6?

[Michael Moll]

Hi,

On Fri, Jun 10, 2016 at 12:05:37PM -0700, Stefan Lasiewski wrote:
> Also, keep in mind that this work would happen at the same time that many 
> Foreman users migrate from Puppet 3.8 to Puppet 4. That's two largish, 
> forced migrations at the same time. We've been holding off on our Puppet 4 
> upgrade until there is support in Foreman 1.12, and I suspect other admins 
> are in the same boat.

1.12 is still supported on RHEL6 just fine, so there's no problem to
update Foreman to 1.12 with Puppet 3.x and then update Puppet to 4.x.

Regards
-- 
Michael Moll

-- 
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] Re: Deprecate EL6?

[Stefan Lasiewski]

If Foreman will drop support for EL6, it might worth providing some hints 
on how to migrate Foreman from one node to another, or refreshing existing 
documentation regarding migration if it exists.

Also, keep in mind that this work would happen at the same time that many 
Foreman users migrate from Puppet 3.8 to Puppet 4. That's two largish, 
forced migrations at the same time. We've been holding off on our Puppet 4 
upgrade until there is support in Foreman 1.12, and I suspect other admins 
are in the same boat.

-= Stefan

On Tuesday, May 10, 2016 at 2:26:44 AM UTC-7, Dominic Cleal wrote:
>
> I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have 
> the option of leaving it out of the 1.13 release. This will be 
> documented in the 1.12 release notes. 
>
> This would allow us to start dropping Ruby 1.8.7 support and possibly 
> 1.9.3 across the installer and other subprojects, as this is the last OS 
> using it. Foreman's had EL7 support since version 1.6. 
>
> Any objections? 
>
> -- 
> Dominic Cleal 
> dom...@cleal.org  
>

-- 
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] Re: Re: Re: Nominating Timo Goebel for theforeman/foreman commit access

[Timo Goebel]

Thanks for trusting me with this and for all your support. I'm happy to 
work even closer with you guys and that we all have an aweseome Open 
Source experience.


Cheers from Germany!

Timo

Am 10.06.16 um 11:30 schrieb Daniel Lobato Garcia:

On 06/07, Daniel Lobato Garcia wrote:

Reminder - 2 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 been contributing to the puppet modules, community-templates, bootdisk
and Foreman for some time, particularly on the VMWare/vsphere side of things.
He's been running Foreman on production for years already and gave
local talks about it.(www.meetup.com/AWS-Meetup-Karlsruhe/events/229036956/)

Most importantly and the reason why I thought of him as a person that
could become a committer is his involvement on ipv6 support lately,
where he's been submitting consistently good code.

I think he understands very well the problem domain, and he will be
committed to maintain and improve the code quality of the project, as
well as providing good feedback from a production installations.

Some examples of his contributions:

https://github.com/theforeman/foreman/pull/3420
https://github.com/theforeman/foreman/pull/3424
https://github.com/theforeman/foreman/pull/3498
https://github.com/theforeman/foreman/pull/3499
https://github.com/theforeman/foreman/commit/5131edbfab258c0862c987f238049ee81a1cd13f
https://github.com/theforeman/foreman/commit/8ca6c6bbc5242c29a8039d1e6a1d09d1a454164c
https://github.com/theforeman/foreman/commit/2328beb569d3f0e51043202d3a00a3b30879d244
https://github.com/theforeman/puppet-puppet/pull/389
https://github.com/theforeman/foreman_bootdisk/pull/19

Lastly I'd encourage him to start reviewing already!

Objections or comments in private are welcome, but public replies to this
thread are preferred :)

Best,

--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato



--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato



--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato



--
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] projects.theforeman.org seems to be down...

[Dominic Cleal]

On 10/06/16 11:27, Dominic Cleal wrote:
> On 10/06/16 11:26, Daniel Helgenberger wrote:
>> or is it just me?
> 
> It is down/very slow as it's receiving lots of requests from web
> crawlers. I've blocked a couple and put in some updates to robots.txt,
> hopefully it'll ease off and come back.

It returned to normal between 12:43 and 13:45 UTC but has now worsened,
so I've raised a case with OpenShift support. Hopefully it'll be moved
to somewhere with lower contention.

-- 
Dominic Cleal
domi...@cleal.org

-- 
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] projects.theforeman.org seems to be down...

[Dominic Cleal]

On 10/06/16 11:26, Daniel Helgenberger wrote:
> or is it just me?

It is down/very slow as it's receiving lots of requests from web
crawlers. I've blocked a couple and put in some updates to robots.txt,
hopefully it'll ease off and come back.

-- 
Dominic Cleal
domi...@cleal.org

-- 
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] projects.theforeman.org seems to be down...

[Daniel Helgenberger]

or is it just me?

Cheers,
-- 
Daniel Helgenberger (helge000)
dan...@helgenberger.net

-- 
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] Re: Re: Nominating Timo Goebel for theforeman/foreman commit access

[Greg Sutcliffe]

On 10 June 2016 at 10:30, Daniel Lobato Garcia  wrote:

> On 06/07, Daniel Lobato Garcia wrote:
> > Reminder - 2 days left if you have any objections or comments!
>
> Done! Welcome to the core team and may Jenkins help you with your code
> reviews :)


Welcome Timo!

-- 
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] Re: Re: Nominating Timo Goebel for theforeman/foreman commit access

[Daniel Lobato Garcia]

On 06/07, Daniel Lobato Garcia wrote:
> Reminder - 2 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 been contributing to the puppet modules, community-templates, bootdisk
> > and Foreman for some time, particularly on the VMWare/vsphere side of 
> > things.
> > He's been running Foreman on production for years already and gave
> > local talks about it.(www.meetup.com/AWS-Meetup-Karlsruhe/events/229036956/)
> >
> > Most importantly and the reason why I thought of him as a person that
> > could become a committer is his involvement on ipv6 support lately,
> > where he's been submitting consistently good code.
> >
> > I think he understands very well the problem domain, and he will be
> > committed to maintain and improve the code quality of the project, as
> > well as providing good feedback from a production installations.
> >
> > Some examples of his contributions:
> >
> > https://github.com/theforeman/foreman/pull/3420
> > https://github.com/theforeman/foreman/pull/3424
> > https://github.com/theforeman/foreman/pull/3498
> > https://github.com/theforeman/foreman/pull/3499
> > https://github.com/theforeman/foreman/commit/5131edbfab258c0862c987f238049ee81a1cd13f
> > https://github.com/theforeman/foreman/commit/8ca6c6bbc5242c29a8039d1e6a1d09d1a454164c
> > https://github.com/theforeman/foreman/commit/2328beb569d3f0e51043202d3a00a3b30879d244
> > https://github.com/theforeman/puppet-puppet/pull/389
> > https://github.com/theforeman/foreman_bootdisk/pull/19
> >
> > Lastly I'd encourage him to start reviewing already!
> >
> > Objections or comments in private are welcome, but public replies to this
> > thread are preferred :)
> >
> > Best,
> >
> > --
> > Daniel Lobato Garcia
> >
> > @dLobatog
> > blog.daniellobato.me
> > daniellobato.me
> >
> > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> > Keybase: https://keybase.io/elobato
>
>
>
> --
> Daniel Lobato Garcia
>
> @dLobatog
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> Keybase: https://keybase.io/elobato



--
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

-- 
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: PGP signature

Re: [foreman-dev] Org with host deletion question

[Tomas Strachota]

On 06/09/2016 08:37 PM, David Davis wrote:

Could we perhaps go with option 1 in the CLI/API and then for the UI,
warn users that the org has hosts (but allow them to continue if they
click ok)?



+1 a confirm dialog seems a good option to me. API/CLI could solve the 
issue with a --force parameter. By default it would warn, stop and 
advice using --force if you really want to proceed.


If that's not working for other I'd like to see at least a message about 
what's been disassociated.


T.



David

On Thu, Jun 9, 2016 at 2:33 PM, Stephen Benjamin mailto:step...@redhat.com>> wrote:



- Original Message -
> From: "Marek Hulán" mailto:mhu...@redhat.com>>
> To:foreman-dev@googlegroups.com 
> Cc: "Tom McKay" mailto:thomasmc...@redhat.com>>, 
"ohadlevy"
mailto:ohadl...@redhat.com>>
> Sent: Thursday, June 9, 2016 10:37:23 AM
> Subject: Re: [foreman-dev] Org with host deletion question
>
> Hello
>
> I lean towards the second atm, if taxonomies are enabled we should not add
> more actions leading to hosts being unassociated. I consider host without
> organization in organization enabled instance as a bug. Long term I'd 
like to
> see all hosts that are unassociated today being in fact associated to some
> default org. Once we have that, we could set the host association to this 
new
> default org on organization deletion.

Yea but the default org stuff is just totally broken.  We tried to
set this
by default (there are settings to do this) and stuff explodes
because Puppet
parser generated objects don't get in a taxonomy.  It's not trivial
at all.

> Anyway if there are more votes for option 1, I as a user would like to 
know
> that there were some hosts that were moved to the unasssociated hosts 
bucket.
> At least a warning would be good.

I would vote for disassociating, the "XX is still used by YY" errors
in Foreman
are very frustrating, and in this case I don't think it's especially
unwarranted.
Giving the user a warning saves them a lot of hassle.  If the hosts
aren't useful
anymore, they can then go and delete them, or if they want to keep
using them,
assign them to new orgs/locations.


 > --
 > Marek
 >
 > On Wednesday 08 of June 2016 16:23:48 Tom McKay wrote:
 > > To me, as a user, if I delete an org (or location) I'd simply
want the
 > > foreman resources to be unassociated from it. It may be the
case, for
 > > example, that a resource like a provisioning template is shared
among
 > > multiple orgs. A host is different, I know, in that it can
belong to only
 > > one org but I would still lean towards consistency by throwing
it into the
 > > bucket of unassociated hosts.
 > >
 > > On Wed, Jun 8, 2016 at 3:05 PM, Partha Aji mailto:p...@redhat.com>> wrote:
 > > > While working on one of the org deletion bugs (
 > > > http://projects.theforeman.org/issues/15336) I hit upon this
 > > > inconsistency in Foreman code base and would like
suggestions on the
 > > > agreeable behavior.
 > > >
 > > > So here is the user action
 > > > 1) User creates an org
 > > > 2) Assigns a host to that org
 > > > 3) Deletes that org
 > > >
 > > > There seem to be 2 different approaches taken in the foreman code
 > > > 1)
 > > >
https://github.com/theforeman/foreman/blob/develop/app/models/taxonomies/o
 > > > rganization.rb#L8 seems to indicate the intention to nullify the
 > > > organization-host
 > > > association if organization gets deleted. This tells me that
its ok to
 > > > delete the org with hosts associated to it.
 > > > "has_many_hosts :dependent => :nullify"
 > > >
 > > > 2)
 > > >
https://github.com/theforeman/foreman/blob/develop/test/functional/api/v2/
 > > > locations_controller_test.rb#L74 seems to indicate we do Not
want to
 > > > delete orgs/locations if hosts are attached to it. "should
NOT destroy
 > > > location if hosts use it" .
 > > >
 > > > Looking at the commit dates for both, they were merged a mere
month after
 > > > each other (jan - feb 2013). 2 came before 1 .
 > > >
 > > > I prefer 1 over 2 .. Unassociate the Org from the Host if the
org gets
 > > > deleted instead of blocking the delete.  Whats your preferred
approach.
 > > > Kindly let me know.
 > > >
 > > > Partha
 > > >
 > > > --
 > > > 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 Sentry plugin

[Ewoud Kohl van Wijngaarden]

On Thu, Jun 09, 2016 at 05:07:14PM -0700, Brandon Weeks wrote:
> At Square we use Sentry  for exception tracking 
> across all of our internal applications. To help my team detect and resolve 
> problems with our Foreman environment I created foreman_sentry 
> , a small plugin that loads 
> Raven , the Sentry client for 
> Ruby. While the hosted version of Sentry is a paid product, the project 
> itself is open source  and is free to 
> host yourself.

As another Sentry user I think this is very interesting. Any plans to
package it?

-- 
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] Drop support for Ruby 1.9.2 in smart proxy

[Dominic Cleal]

On 07/06/16 13:20, Dominic Cleal wrote:
> I'd like to drop support for testing Ruby 1.9.2 in the smart proxy,
> primarily because we're getting intermittent segfaults on it during tests.
> 
> We used to have some platforms (such as Debian Squeeze, IIRC) that
> shipped 1.9.2 but we no longer support them. Puppet also didn't support
> it officially as 1.9.3 contained lots of fixes.
> 
> 1.8.7 support would remain, so we'd have 1.8.7, 1.9.3, 2.0.0 and up.

I've removed 1.9.2 from the matrix.

-- 
Dominic Cleal
domi...@cleal.org

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