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

2016-09-01 Thread Timo Goebel 


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 directly? That's not possible, unless you use HTTP client
> certificate. Sign it with your puppet ca and use it if you want.

... you can also get a free ip via Forman's API, without calling the proxy 
directly. Do you need any help doing that? I'm just not sure if support was 
added in 1.12 or 1.13. :-)

-- 
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: Automate IP allocation over specifying subnets in machine creation

2016-09-01 Thread Greg Sutcliffe 
On 31 August 2016 at 11: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 directly? That's not possible, unless you use HTTP client
> certificate. Sign it with your puppet ca and use it if you want.
>

Well, it is possible - but you have to make some changes to the proxy :)

The proxy, by default, sets:

:trusted_hosts:
  - foreman.domain.org

This means 2 things - one, API calls need to be wrapped with a certificate
signed by the proxy's CA, and 2, the cert's name has to be in the
trusted_hosts.

So, you have three options, from most to least-secure:

1) If only a few machines will need to call the free_ip endpoint, you can
generate new certs from the same CA, give them to the clients, and add them
to trusted_hosts (i.e what Lukas said)
2) disable trusted_hosts entirely, at which point any valid SSL request can
access the API
3) Allow non-ssl requests to that proxy module

Hope that helps!
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.

[foreman-dev] Adjusting Katello test jobs

2016-09-01 Thread Eric D Helms 
I will be adjusting Katello test jobs to try to get better throughput
through our CI system and in preparation to move to the Jenkins PIpeline
plugin once Dominic is able to install it. For a while, please be mindful
of any strangeness or breakages and report them to me for investigation.


Thanks,
Eric

-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
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] hammer requires ruby >= 2.1.0

2016-09-01 Thread Tomas Strachota 

On 08/31/2016 01:13 PM, David Davis wrote:

We probably need to pin the version to 1.1.0. It looks like 1.2.0 which
came out this month requires ruby >= 2.1.0.



Yes, the requirement is quite new, but we actually need 1.2.0 to get the 
performance improvements it received recently. As Tomer wrote, git 
installation should be fine. More details about how we (plan to) 
approach the problem for various distributions is here:


https://groups.google.com/forum/#!msg/foreman-dev/kDPl1hgP9lQ/uvfEToYCCAAJ;context-place=forum/foreman-dev



David

On Tue, Aug 30, 2016 at 8:27 PM, Tom McKay mailto:thomasmc...@redhat.com>> wrote:

Am I doing something wrong? Trying to install hammer (from github)
on RHEL-7Server fails because fast_gettext requires ruby >= 2.1.0.

--
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] Jenkins slaves not responding

2016-09-01 Thread Dominic Cleal 
On 01/09/16 09:00, Timo Goebel wrote:
> Dominic,
> 
>> On 31.08.2016, at 09:43, Dominic Cleal  wrote:
>>
>> The slave that I attempted this on crashed within a day, so they'll
>> remain on two slots each.
> 
> Do you know why these crashes happen? Are there any monitoring graphs, that 
> show cpu/memory usage over time? The issue sounds like a oom problem judging 
> from what i read here. Do you see anything related in the system's logs?

No, I don't know precisely and the slave that crashed yesterday doesn't
have the Rackspace monitoring agent installed to collect memory data.

slave09, one of those that crashed on the morning of 16/08, was showing
high memory and swap usage on 15/08
(http://paste.fedoraproject.org/418780/47271889/), so memory exhaustion
is quite likely. I don't have any data about what processes were using
the memory in this instance.

slave10, that crashed yesterday only logged hanging tasks
(https://paste.fedoraproject.org/418772/72718379/), which I've seen on
consoles and logs from other crashed systems. There's no ability to send
a sysrq through the provided console, and nothing like kdump/watchdogs
are configured on those systems.

-- 
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] Jenkins slaves not responding

2016-09-01 Thread Timo Goebel 
Dominic,

> On 31.08.2016, at 09:43, Dominic Cleal  wrote:
> 
> The slave that I attempted this on crashed within a day, so they'll
> remain on two slots each.

Do you know why these crashes happen? Are there any monitoring graphs, that 
show cpu/memory usage over time? The issue sounds like a oom problem judging 
from what i read here. Do you see anything related in the system's logs?

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.

Re: [foreman-dev] Expanding Slave Capacity

2016-09-01 Thread Dominic Cleal 
On 31/08/16 16:55, Bryan Kearney wrote:
> On 08/31/2016 09:30 AM, Dominic Cleal wrote:
>> On 31/08/16 14:30, Bryan Kearney wrote:
>>> On 08/31/2016 09:07 AM, Dominic Cleal wrote:
 On 31/08/16 14:04, Bryan Kearney wrote:
> Would an m3.medium from ec2 be helpful?

 If additional storage is available, yes, as the requirements (link
 above) are for a minimum of 60GB space, not the 4GB it appears that the
 m3.medium spec has.

>>> I mis read that. Are any of the slaves ec2 now? If so, do you know the size?
>>
>> No, not to my knowledge.
>>
> Lets try one:
> 
> ec2-184-72-89-17.compute-1.amazonaws.com
> 
> your ssh key should work

Thanks, the slave is now online with three slots.

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