Re: [foreman-dev] Ansible based foreman-installer

[Greg Sutcliffe]

On Tuesday, 14 March 2017 18:16:59 GMT Michael Hofer wrote:
> Hi Ohad
> 
> On Tue, 14 Mar 2017 08:45:19 +0200
> Ohad Levy  wrote:
> [...]
> 
> > Would you be interested in doing a deep dive about the installer? what it
> > currently does, how to use it etc?
> > 
> > I think it would be interesting to our increasing ansible users community.
> 
> [...]
> 
> Sure, why not! :)
> 
> Would that be a topic for a community demo?

We can do it either way (or both!). Community demo items tend to be short 
(5-10 mins tops) and stay at a high level. Deep dives obviously have more time 
to get into the details.

I'd suggest a dedicated deep dive to start with, and then you'll always be 
welcome to join the regular demos to show off latest developments in the 
Ansible installer.

If that works for you, I'll ping you offlist to sort out a date & time for the 
deep dive.

Greg
-- 
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

Re: [foreman-dev] Re: 1.15 branching in approximately 2 weeks

[Dmitri Dolguikh]

On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota  wrote:
> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato  wrote:
>> We're planning to do the branching on all projects on March 28th -
>> please keep it in mind and try to get
>> things that would be important for 1.15 by then.
>>
>> I do not have commit access everywhere, so please check the following
>> list and reply if you
>> could take care of cherry-picking and branching:
>>
>> foreman - Daniel - dlobatog
>> foreman-installer - Stephen - stbenjam
>> smart-proxy - Daniel - dlobatog - (or Dmitri - witlessb if you prefer)

yes can do.
-d

>> foreman-selinux - Lukas - lzap
>> foreman-packaging - Eric - ehelms
>> theforeman.org - Daniel - dlobatog
>> translations - Daniel - dlobatog
>> community-templates - Daniel - dlobatog
>> hammer-cli - Tomas? Martin?
>> hammer-cli-foreman - Tomas? Martin?
>
> I'll take care of hammer branching and release.
>
>> puppet-foreman - ?
>> puppet-foreman_proxy - ?
>>
>>
>> On Fri, Mar 10, 2017 at 7:43 PM, Daniel Lobato Garcia
>>  wrote:
>>> As per 
>>> http://projects.theforeman.org/projects/foreman/wiki/Foreman_115_Schedule,
>>> 1.15 is due to be branched soon, in 2 weeks approximately.
>>>
>>> Please help to make develop more stable during this process, be it through
>>> thorough testing, bugfixing or improving documentation.
>>>
>>> Help with updating the manual would be appreciated, see the list of
>>> tasks in:
>>>   - https://github.com/theforeman/theforeman.org/issues/765
>>>
>>> Some translations are nearing 100% completion, we welcome contributions
>>> that help finishing them for the next release:
>>>   - https://www.transifex.com/foreman/foreman/foreman/
>>>
>>> If you have any critical fixes that you think should be included in 1.15
>>> in any of the core projects, please reply to this read to raise
>>> attention over them. Maintainers feel free to set the 1.15 label to
>>> any PR of that nature.
>>>
>>> Best,
>>>
>>> --
>>> Daniel Lobato Garcia
>>>
>>> @dLobatog
>>> blog.daniellobato.me
>>> daniellobato.me
>>>
>>> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
>>> Keybase: https://keybase.io/elobato
>>
>>
>>
>> --
>> Daniel Lobato
>>
>> @dlobatog
>> daniellobato.me
>>
>> GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30
>>
>> --
>> 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] Dev/Design Weekly Meeting - Subscriptions

[Sean O'Keeffe]

On Wed, 15 Mar 2017 at 11:50, Marek Hulán  wrote:

> Hello Sean,
>
> I'm sorry if we created a feeling that we're doing something behind closed
> doors.
>
> Let me explain the background. When Roxanne started to look at the UI/UX
> improvements we quickly realized that Foreman with all its plugins is a big
> application and it seemed as too much to digest at once. So we decided to
> start introducing smaller, isolated parts of the whole thing to her once a
> week. Each week we sit and talk about specific area. I hope that it helps
> Roxanne to understand how the project is interconnected so she can suggest
> larger changes consistent across the whole app after some time.

That makes sense, a bit of context around the email would have been nice
though.

>
>
> Also as part of these demos, she takes notes of small items that we can fix
> right away, such as "this inline help does not provide a value", "this
> button
> should not be red". So it's not really a discussion or designing of new
> stuff,
> it's rather a demo for a certain area.

Thats good and I would agree if it's just a couple of small changes. Though
as this is a concerted effort that overall will like significantly impact
the UI a simple email like "we're going to making loads of changes to the
UI over the next few months, over many PRs. Here's the tracker in redmine,
watch it if you want to follow all of the changes" or use of the rfc repo
would have been nice.

>
> Roxanne provides the notes from these sessions for what could be improved.
> If
> those are low hanging fruit we try to fix it right away. Since she shares
> notes during these sessions and share them with everyone so people who are
> interested could also add their comments. All changes are going through PRs
> and the discussion, if necessary, happens there.
>
> I think sharing these notes is also useful for people who'd like to
> contribute
> with code and are looking for something small.
>
> I hope it makes better sense now.

Yes, thank you! The main issue was lack of context around these emails.

>
> --
> Marek
>
> On úterý 14. března 2017 22:43:39 CET Sean O'Keeffe wrote:
> > Firstly thanks for all the valuable input Roxanne, I'm just a bit
> concerned
> > about discussions that to me at least appear to be happening behind
> closed
> > doors.
> >
> > When do these "Dev/Design Weekly Meeting" take place?
> > Have they ever been advertised on this mailing list or anywhere
> publicly? I
> > haven't seen anything, maybe I missed it?
> > If not, why not?
> >
> > Having conversations behind closed doors that have such a large impact on
> > the project is not a good thing.
> > To me, sending notes about a meeting that I can only assume happens
> within
> > redhat every week is quite inappropriate. Not only does it make people in
> > the community feel excluded from important discussions, but it also shows
> > the sway and power redhat has within this community, which in my opinion
> > shouldn't be the case.
> >
> > I get that redhat will want to make suggestions that benefit itself and
> us
> > and maybe sometimes just itself but this is not the right way to go about
> > it. We need to have open discussions.
> >
> > Sean
> >
> > On Mon, Mar 13, 2017 at 3:02 PM, Roxanne Hoover 
> wrote:
> > > https://docs.google.com/document/d/1zqK49SNLMA2t8SHen4M2z6-Z
> > > gsVk3oKEQsCwxcK6d6A/edit
> > >
> > >
> > > Subscription Management
> > >
> > > Presented by Thomas McKay
> > >
> > >
> > > Subscription Manifest -- no manifest yet
> > >
> > >-
> > >
> > >Manifest history -- no message/time… it should state as much.
> > >-
> > >
> > >More direct route to Upload… entire page not necessary because it
> has
> > >no data.
> > >-
> > >
> > >Upload success inline messaging lacks icon.
> > >
> > > Subscription Manifest - already manifest
> > >
> > >-
> > >
> > >Delete Manifest is a big deal.
> > >-
> > >
> > >IMport History tab might not be necessary
> > >-
> > >
> > >“Upstream Subscription Management Application” - wraps to 4 lines,
> > >creates awkward empty space and could be confused for independant
> > >labels.
> > >-
> > >
> > >Can the Upload button Delete and then Upload… Tom says no.
> > >-
> > >
> > >Page doesn’t refresh after delete. Delete is nuclear with no
> warning.
> > >-
> > >
> > >Inline messaging is all over the place, grey is at bottom, red is in
> > >the middle (from bad upload), and success delete was at the top.
> > >-
> > >
> > >Also - error on upload was in an inline messaging pattern vs. form
> > >error which is typical in other areas of forum.
> > >
> > > Product Content Tab
> > >
> > >-
> > >
> > >Items are added/removed from another page… integration would be
> nice,
> > >content could at least be formatted for Patternfly as the negative
> > >positive
> > >accordion is not standard.
> > >
> > > --
> > > You received 

[foreman-dev] Fetch continuous output of non-delegated foreman / dynflow tasks

[gerrit . schwerthelm]

Hi,

I was studying the dynflow documentation, but there are some pieces or 
examples missing in order for me to understand how to do this and I cannot 
find examples in the Katello sources either. Therefore, I would appreciate 
some help.

I have written one main task that is a composition of smaller tasks:

class MainAction < Actions::EntryAction
  def plan(args)
sequence do
  plan_action ::Actions::MyPlugin::FirstTask, args
  plan_action ::Actions:: MyPlugin::SecondTask, args
end
plan_self
  end

...

I have wrapped the smaller tasks into runner objects derived from 
ForemanTasksCore::Runner::Base and use publish_data() to emit output for 
the console. In the dynflow console, I can observe that the tasks are 
publishing output when browsing into the smaller tasks. But what is unclear 
for me is how I can fetch this output and show it in the console of the 
main action such that I can observe the progress in the foreman-task task 
page. I believe it needs to work somehow by including 
::Actions::Helpers::WithContinuousOutput? I can see something similar 
working with delegated actions in the foreman_ansible plugin. However, I do 
not need delegated actions as everything happens locally anyway.

Thanks for reading. Looking forward to an answer.

Regards,

--Gerrit

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