Re: [foreman-dev] Re: error calling hammer.run() from w/in 'hammer csv subscriptions'

2016-09-06 Thread Tom McKay 
Without the lines add_text_domain the errors happen. Could be that katello
is not initialized at the time I am calling hammer.run() for one of its
commands? I'm just guessing at things at this point.

I am on ruby-2.3.1 w/ fast_gettext-1.2.0

On Mon, Sep 5, 2016 at 4:13 AM, Martin Bačovský 
wrote:

> Recently there were some changes in how the translation domains are
> handled in hammer with new fast_gettext. See the PR [1] for more details.
> There was hammer 0.8.0 gem released last week containing the changes.
> What hammer version anf fast_gettext do you use?
>
> I checked the hammer-cli-csv PR and I'm not sure why are you adding the
> domain manualy for the second time and not only with 
> HammerCLI::I18n.add_domain
> but it was not necessary for hammer-cli-foreman.
>
>
> [1] https://github.com/theforeman/hammer-cli/commit/6e28b70ff1a0
> 5344b0af7abd5a2f660d74ba6df7
>
>
>
> On Fri, Sep 2, 2016 at 9:44 PM, Tom McKay  wrote:
>
>> Opened a PR that works but I'd like to understand the problem and what
>> changed, if anyone has any insights.
>> https://github.com/Katello/hammer-cli-csv/pull/121
>>
>> On Fri, Sep 2, 2016 at 1:14 PM, Tom McKay  wrote:
>>
>>> I get an error "RuntimeError (Current textdomain (nil) was not added,
>>> use FastGettext.add_text_domain !" during a call to hammer.run() from w/in
>>> another hammer command. Effectively 'hammer csv subscriptions' is calling
>>> 'hammer subscription upload' from w/in itself. If I add this code[1] prior
>>> to calling hammer.run() then things work as expected (and as it had
>>> previously).
>>>
>>> What is the proper way to config FastGettext in hammer module?
>>>
>>>
>>> [1] https://github.com/thomasmckay/hammer-cli-csv/blob/fastgette
>>> xt/lib/hammer_cli_csv/subscriptions.rb#L62-L68
>>>
>>
>> --
>> 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] CfP entry for CfgMgmt camp in Berlin

2016-09-06 Thread Lukas Zapletal 
> > Sounds pretty good to me. Just to check we're on the same page, the
> > patch below is meant so that the discovery image accepts blocks, so that
> > the discovery image can accept *another* image and boot from it?
> 
> I was under the impression you could use image to dump to disk and boot it
> (think reusing your vm templates / cloud images for bare metal too).
> 
> this can open the usage case of cloud init for bare metal and ideally speed
> up bare metal provisioning time.

Yes, today if you use the patch, you can dump the image using netcat or
using udpcast (multicast) and reboot and it just works. My idea is to:

- extend FDI API with partitioning endpoint (create volumes/LVM)
- create a image "library" plugin that will serve images
- provide some helper scripts to feed the library with some images (*)
- create new provisioning workflow in discovery plugin

Initial "library" could be very easy smart-proxy plugin with simple
provider (raw files in a directory) but we could integrate with other
technologies later on.

(*) virt-builder is a nice tool that can easily create bunch of images
for you with firstboot scripts, custom root passwords and stuff like
that

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

[foreman-dev] Fwd: [Transifex] The source content of a resource in the project Foreman has been updated

2016-09-06 Thread Dominic Cleal 
If you're receiving regular notifications about
foreman_cockpit/hammer_cli_foreman_admin resources being updated in
Transifex, then please ignore them for now. They're aware of the issue
and are working on a fix soon.

Dominic


 Forwarded Message 
Subject:[Transifex] The source content of a resource in the project
Foreman has been updated
Date:   Tue, 06 Sep 2016 08:55:32 -
From:   Transifex 
To: domi...@cleal.org

Transifex Notification

Hi Dominic Cleal,
The source content of the resource foreman_cockpit
of the project Foreman has been updated.
--
The Transifex Robot

-- 
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] CfP entry for CfgMgmt camp in Berlin

2016-09-06 Thread Ohad Levy 
On Tue, Sep 6, 2016 at 11:35 AM, Daniel Lobato Garcia 
wrote:

> On 09/05, Lukas Zapletal wrote:
> > I just submitted for the record:
> >
> > Abstract:
> >
> > First, it starts with a DVD with an OS installer, then is a recipe to
> > automate it. And then PXE booting from network which sometimes lead to
> > discovering new bare-metal nodes. Some shops fully automate provisioning
> > and the only action is to power on a server. We all have that. But
> > what's next?
> >
> > Make it fast. Blazing fast. Do it virtualization-like or cloud-like
> > experience with Foreman Discovery and the new image-deployment
> > capabilities.
> >
> > Additional info:
> >
> > Bare-metal remains relevant with upcoming farms of ARM servers. We need
> > to be ready to deploy dozens of bare-metal servers at once. I will show
> > story of provisioning in a typical Foreman shop and then make a demo of
> > bare-metal servers deploying OS using multicast image transfer.
> >
> > The image-deployment scenario is a working in progress (prototype that
> > works), I would like to hear feedback on that and also collect ideas.
>
> Sounds pretty good to me. Just to check we're on the same page, the
> patch below is meant so that the discovery image accepts blocks, so that
> the discovery image can accept *another* image and boot from it?
>

I was under the impression you could use image to dump to disk and boot it
(think reusing your vm templates / cloud images for bare metal too).

this can open the usage case of cloud init for bare metal and ideally speed
up bare metal provisioning time.

Ohad

>
> > Links:
> >
> > https://theforeman.org/
> > https://theforeman.org/plugins/foreman_discovery/6.0/index.html
> > https://github.com/theforeman/foreman-discovery-image/pull/44
> >
> > 40 Min talk and discussion
> >
> > --
> > 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.
>
> --
> Daniel Lobato Garcia
>
> @dLobatog
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get=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.
>

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