[katello-devel] Katello-configure re-design plans

[Ivan Necas]

----- Original Message -----

> Would there be any design goals around allowing this to facilitate developer
> installations as well as production installs?

That should be one of the side effects of parametrization of the classes and making them more independent. One of the goals is 
to set the system accross more machines. 

There are more approaches to development environment. Personally, I use katello-configure to set the whole environment in virual machine 
and then reconfigure the apache to use my local Katello/Foreman rails server. In todays world, personally I run a script 
to disable the katello and katello-jobs service, set's elasticsearch and postgres to listen on different interface and reconfigures the apache proxy etc. 

After rework, it should be possible to do that with just tweeking the installation parameters. 

-- Ivan 

> On Thu, Jul 11, 2013 at 7:49 AM, Ivan Necas < inecas at redhat.com > wrote:

> > ----- Original Message -----
> 
> > > Will this include looking at pack stack and possibly creating a generic
> 
> > > puppet installer?
> 

> > That's the plan, although, we want first solve our issues with possibility
> 
> > to make it general, instead trying to solve ultimate question of puppet
> 
> > installer, universe and everything from day one. But yeah, even with
> 
> > the current goal having one script for katello and foreman seems like
> 
> > general enough.
> 

> > -- Ivan
> 

> > >
> 
> > > -- bk
> 
> > > Sent with thumbs
> 
> > >
> 
> > > On Jul 11, 2013, at 11:57 AM, Ivan Necas < inecas at redhat.com > wrote:
> 
> > >
> 
> > > > Hi,
> 
> > > >
> 
> > > > We had an opportunity to discuss re-design of our puppet classes and
> 
> > > > installer with
> 
> > > > the Foreman team, to be able to share as much as possible in the
> > > > installer
> 
> > > > area.
> 
> > > >
> 
> > > > Couple of stories came out of this discussions, we've created cards on
> 
> > > > backlogs for
> 
> > > > both teams. You can see more here [1].
> 
> > > >
> 
> > > > The plan basically is to have a installer script independent on the
> 
> > > > puppet classes, so that is will be possible to use either just for
> > > > Katello,
> 
> > > > Foreman, Foreman-proxy or combination: the list of possible parameters
> > > > will
> 
> > > > be delivered
> 
> > > > by the puppet modules presented.
> 
> > > >
> 
> > > > With rewriting Katello puppet modules to parametrized classes, this
> > > > should
> 
> > > > lead also
> 
> > > > to be able to use this approach to have katello-configure-like
> > > > installer
> 
> > > > script
> 
> > > > just for pulp/candlepin, that could be used in upstream of this
> > > > projects.
> 
> > > >
> 
> > > > As part of the effort, we also want to share as much puppet modules as
> 
> > > > possible (apache/passenger/postgres etc.)
> 
> > > >
> 
> > > > Questions/opinions?
> 
> > > >
> 
> > > > [1] -
> 
> > > > https://trello.com/card/re-design-katello-configure-and-foreman-installer-such-that-the-2-projects-don-t-have-to-maintain-their-own-installers/511bd7357c52d1c61c00510e/116
> 
> > > >
> 
> > > > -- Ivan
> 
> > > >
> 
> > > > _______________________________________________
> 
> > > > katello-devel mailing list
> 
> > > > katello-devel at redhat.com
> 
> > > > https://www.redhat.com/mailman/listinfo/katello-devel
> 
> > >
> 

> > _______________________________________________
> 
> > katello-devel mailing list
> 
> > katello-devel at redhat.com
> 
> > https://www.redhat.com/mailman/listinfo/katello-devel
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20130711/b5966ee2/attachment.htm>