<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 8, 2016 at 11:57 AM, David Caro <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/08 18:53, Barak Korren wrote:<br>
> On 8 March 2016 at 18:25, Eric Helms <<a href="mailto:ehelms@redhat.com">ehelms@redhat.com</a>> wrote:<br>
> > I am thinking about how to make this more useful to the masses on the team.<br>
> > The question I am asking myself is "can it replace vagrant for some<br>
> > scenarios". For example, being able to spin up a Satellite + Capsule(s) with<br>
> > DHCP, DNS etc. but allow outside access to the server via a web browser.<br>
> > Since often the setup requires a beefy box that is running on a beaker<br>
> > machine or server under a desk and developers use their laptops to access.<br>
> ><br>
> Faced with the same dilemma when running oVirt on Lago on my MiniDell,<br>
> I've simply setup Apache on it to proxy HTTP traffic into the VM<br>
> network.<br>
> With a browser proxy plugin such as foxy proxy configured to make the<br>
> browser also resolve DNS for domains with certain suffixes over the<br>
> proxy, I've got a pretty seamless user experience without giving up on<br>
> the environment isolation.<br>
><br>
> If you want this to be self-contained in a script you give developers,<br>
> you can perhaps use the Ruby or Python built-in HTTP servers to do the<br>
> proxying.<br>
<br>
<br>
</span>I think that a better solution might be exposing ports or similar, though I<br>
agree that having the possibility to setup external nets is a nice to have.<br>
<br>
btw. you can use ssh's -D option to setup a socks proxy server too, simpler<br>
imo.<br></blockquote><div><br></div><div>Can you help me visualize what this would look like from a code or user perspective? Right now I have it reduced to "run this script" and environment gets setup and installation steps occur. Ideally, that same script would setup or configure whatever is needed so a developer just hits the IP in their browser and is off and running.</div><div><br></div><div>Eric</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
<br>
><br>
><br>
><br>
> --<br>
> Barak Korren<br>
> <a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
> RHEV-CI Team<br>
</span>> _______________________________________________<br>
> lago-devel mailing list<br>
> <a href="mailto:lago-devel@ovirt.org">lago-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/lago-devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/lago-devel</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com">dcaro@redhat.com</a><br>
IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</font></span></blockquote></div><br></div></div>