<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><br><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr">Would there be any design goals around allowing this to facilitate developer installations as well as production installs?</div></blockquote><div>That should be one of the side effects of parametrization of the classes and making them more independent. One of the goals is</div><div><span style="font-size: 12pt;"> to set the system accross more machines.</span></div><div><br></div><div>There are more approaches to development environment. Personally, I use katello-configure to set the whole environment in virual machine</div><div>and then reconfigure the apache to use my local Katello/Foreman rails server. In todays world, personally I run a script</div><div>to disable the katello and katello-jobs service, set's elasticsearch and postgres to listen on different interface and reconfigures the apache proxy etc.</div><div><br></div><div>After rework, it should be possible to do that with just tweeking the installation parameters.</div><div><br></div><div>-- Ivan</div><div><br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="gmail_extra"><br><div><br></div><div class="gmail_quote">On Thu, Jul 11, 2013 at 7:49 AM, Ivan Necas <span dir="ltr"><<a href="mailto:inecas@redhat.com" target="_blank">inecas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br><br>
----- Original Message -----<br>
> Will this include looking at pack stack and possibly creating a generic<br>
> puppet installer?<br><br></div>That's the plan, although, we want first solve our issues with possibility<br>
to make it general, instead trying to solve ultimate question of puppet<br>
installer, universe and everything from day one. But yeah, even with<br>
the current goal having one script for katello and foreman seems like<br>
general enough.<br><span class="HOEnZb"><span color="#888888" data-mce-style="color: #888888;" style="color: #888888;"><br>
-- Ivan<br>
</span></span><div class="HOEnZb"><div class="h5"><br>
><br>
> -- bk<br>
> Sent with thumbs<br>
><br>
> On Jul 11, 2013, at 11:57 AM, Ivan Necas <<a href="mailto:inecas@redhat.com" target="_blank">inecas@redhat.com</a>> wrote:<br>
><br>
> > Hi,<br>
> ><br>
> > We had an opportunity to discuss re-design of our puppet classes and<br>
> > installer with<br>
> > the Foreman team, to be able to share as much as possible in the installer<br>
> > area.<br>
> ><br>
> > Couple of stories came out of this discussions, we've created cards on<br>
> > backlogs for<br>
> > both teams. You can see more here [1].<br>
> ><br>
> > The plan basically is to have a installer script independent on the<br>
> > puppet classes, so that is will be possible to use either just for Katello,<br>
> > Foreman, Foreman-proxy or combination: the list of possible parameters will<br>
> > be delivered<br>
> > by the puppet modules presented.<br>
> ><br>
> > With rewriting Katello puppet modules to parametrized classes, this should<br>
> > lead also<br>
> > to be able to use this approach to have katello-configure-like installer<br>
> > script<br>
> > just for pulp/candlepin, that could be used in upstream of this projects.<br>
> ><br>
> > As part of the effort, we also want to share as much puppet modules as<br>
> > possible (apache/passenger/postgres etc.)<br>
> ><br>
> > Questions/opinions?<br>
> ><br>
> > [1] -<br>
> > <a href="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" target="_blank">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</a><br>
> ><br>
> > -- Ivan<br>
> ><br>
> > _______________________________________________<br>
> > katello-devel mailing list<br>
> > <a href="mailto:katello-devel@redhat.com" target="_blank">katello-devel@redhat.com</a><br>
> > <a href="https://www.redhat.com/mailman/listinfo/katello-devel" target="_blank">https://www.redhat.com/mailman/listinfo/katello-devel</a><br>
><br><br>
_______________________________________________<br>
katello-devel mailing list<br><a href="mailto:katello-devel@redhat.com" target="_blank">katello-devel@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/katello-devel" target="_blank">https://www.redhat.com/mailman/listinfo/katello-devel</a><br></div></div></blockquote></div><br></div></blockquote><br></div></body></html>