Efforts are beginning in earnest to bring katello into foreman as a plugin
(rails engine).
Near term goal: Get katello engine integrated enough to work (users and
other basic integration).
Longer term goal: Strip foreman functionality into engines as well, leaving
a flexible "core" base app to build on.
The first step is to just get katello up and running as an engine. Although
there was a branch made a couple months ago, some brief discussions make it
seem sensible to use that branch only as a reference and create a new
branch off master.
The first cut will be no db table integration, just get the UI and API
working. This should be accomplished by end of day Oct 15th. Seem
reasonable?
> The first cut will be no db table integration, just get the UI and API
> working. This should be accomplished by end of day Oct 15th. Seem
> reasonable?
We are targeting 1.3 release for Monday, so from this perspective it is
fine.
Running foreman w/ katello as an engine is very nearly in a
development-worthy state. At our first scrum on Monday the definition of
success for first milestone goal was, "Display a single katello UI page by
Wednesday morning." I'd say that goal was met!
There are a few minor changes to a pull-request forthcoming before it will
be usable by other devs. Stay tuned!
A big, big thanks to Eric, Brad, and Joseph for their efforts.
···
On Wednesday, October 9, 2013 2:08:08 PM UTC-4, Thomas McKay wrote:
>
>
> Efforts are beginning in earnest to bring katello into foreman as a plugin
> (rails engine).
>
> Near term goal: Get katello engine integrated enough to work (users and
> other basic integration).
>
> Longer term goal: Strip foreman functionality into engines as well,
> leaving a flexible "core" base app to build on.
>
> The first step is to just get katello up and running as an engine.
> Although there was a branch made a couple months ago, some brief
> discussions make it seem sensible to use that branch only as a reference
> and create a new branch off master.
>
> The first cut will be no db table integration, just get the UI and API
> working. This should be accomplished by end of day Oct 15th. Seem
> reasonable?
>
I am targeting some initial work that is required to get the Katello code
base turned into an engine that I previously did. This is mostly just
sifting through what I did previously and applying it to a new branch of
Katello based on this morning's master. The particular activities I am
targetting to more quickly get other developers able to make use of it are:
Build out gemspec with any new dependencies
Ensure proper requires in lib/katello.rb
Add Foreman plugins Rakefile task to pull down Foreman into the test
directory
Ensure that, at a minimum, a server started from test/foreman_app can be
run and logged in to (not necessarily that Katello UI is visible anywhere
yet)
You might also want to look at Greg's work this week which flips this
round and makes it easier to run engine tests from within a normal
Foreman checkout. (Subject "Improvements to the test framework for
Plugins".)
I think this might be a better way to run it, as it's easier to get a
working Foreman checkout and add plugins to it than to have plugin
checkouts and a fiddly rake prepare mechanism and separate Foreman repo
clone.
···
On 10/10/13 18:08, Eric D Helms wrote:
> - Add Foreman plugins Rakefile task to pull down Foreman into the test
> directory
> - Ensure that, at a minimum, a server started from test/foreman_app can
> be run and logged in to (not necessarily that Katello UI is visible
> anywhere yet)
> > - Add Foreman plugins Rakefile task to pull down Foreman into the test
> > directory
> > - Ensure that, at a minimum, a server started from test/foreman_app can
> > be run and logged in to (not necessarily that Katello UI is visible
> > anywhere yet)
>
> You might also want to look at Greg's work this week which flips this
> round and makes it easier to run engine tests from within a normal
> Foreman checkout. (Subject "Improvements to the test framework for
> Plugins".)
>
> I think this might be a better way to run it, as it's easier to get a
> working Foreman checkout and add plugins to it than to have plugin
> checkouts and a fiddly rake prepare mechanism and separate Foreman repo
> clone.
>
I'll look it over. I can say from the perspective of "I am a pure plugin
developer", having a little script that sets up a Foreman for you is rather
nice in that I just grab my plugin's git repo, run a command and start
working on the plugin. Keeping in mind that I haven't attempted to tackle
testing in our case whatsoever.
Eric
···
On Thu, Oct 10, 2013 at 1:19 PM, Dominic Cleal wrote:
> On 10/10/13 18:08, Eric D Helms wrote:
There is also an initial plugin i18n support. I will work on that to
improve that tho. Greg made some changes recently and I need to catch
up.
LZ
···
On Thu, Oct 10, 2013 at 01:31:41PM -0400, Eric D Helms wrote:
> On Thu, Oct 10, 2013 at 1:19 PM, Dominic Cleal wrote:
>
> > On 10/10/13 18:08, Eric D Helms wrote:
> > > - Add Foreman plugins Rakefile task to pull down Foreman into the test
> > > directory
> > > - Ensure that, at a minimum, a server started from test/foreman_app can
> > > be run and logged in to (not necessarily that Katello UI is visible
> > > anywhere yet)
> >
> > You might also want to look at Greg's work this week which flips this
> > round and makes it easier to run engine tests from within a normal
> > Foreman checkout. (Subject "Improvements to the test framework for
> > Plugins".)
> >
> > I think this might be a better way to run it, as it's easier to get a
> > working Foreman checkout and add plugins to it than to have plugin
> > checkouts and a fiddly rake prepare mechanism and separate Foreman repo
> > clone.
> >
>
> I'll look it over. I can say from the perspective of "I am a pure plugin
> developer", having a little script that sets up a Foreman for you is rather
> nice in that I just grab my plugin's git repo, run a command and start
> working on the plugin. Keeping in mind that I haven't attempted to tackle
> testing in our case whatsoever.
>
> Eric
>
> >
> > --
> > Dominic Cleal
> > 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+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
To get more eyeballs on this work, and since most people tend to monitor
pull requests and not commit logs, we are starting with pull requests from
the outset. The initial one taking advantage of previous work done to mount
Katello as an engine can be found here: https://github.com/Katello/katello/pull/3165
-Eric
···
On Fri, Oct 11, 2013 at 10:49 AM, Lukas Zapletal wrote:
There is also an initial plugin i18n support. I will work on that to
improve that tho. Greg made some changes recently and I need to catch
up.
LZ
On Thu, Oct 10, 2013 at 01:31:41PM -0400, Eric D Helms wrote:
On Thu, Oct 10, 2013 at 1:19 PM, Dominic Cleal dcleal@redhat.com > wrote:
On 10/10/13 18:08, Eric D Helms wrote:
Add Foreman plugins Rakefile task to pull down Foreman into the
test
directory
Ensure that, at a minimum, a server started from test/foreman_app
can
be run and logged in to (not necessarily that Katello UI is visible
anywhere yet)
You might also want to look at Greg’s work this week which flips this
round and makes it easier to run engine tests from within a normal
Foreman checkout. (Subject “Improvements to the test framework for
Plugins”.)
I think this might be a better way to run it, as it’s easier to get a
working Foreman checkout and add plugins to it than to have plugin
checkouts and a fiddly rake prepare mechanism and separate Foreman repo
clone.
I’ll look it over. I can say from the perspective of “I am a pure plugin
developer”, having a little script that sets up a Foreman for you is
rather
nice in that I just grab my plugin’s git repo, run a command and start
working on the plugin. Keeping in mind that I haven’t attempted to tackle
testing in our case whatsoever.
