[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lnst-developers
Subject:    Exec on controller revisited
From:       rpazdera () redhat ! com (Radek Pazdera)
Date:       2012-12-07 13:26:26
Message-ID: 20121207132626.GA27621 () laptop ! brq ! redhat ! com
[Download RAW message or body]

On Wed, Dec 05, 2012 at 12:51:25PM +0100, Jan Tluka wrote:
>Hi guys,
>
>we have recently removed possibility to run exec command on the
>controller itself. The argument was that if someone needs to do such
>thing he should start slave instance on the controller. This is ok and
>makes sense. However, there's one problem. It's the cleanup phase. I'm
>using virtual guests as test machines and controller is run from host.
>I need to add netem on the host bridge to simulate packet loss and

I think we could discuss the possibility of enabling that again at the
next meeting. This is a use case that we haven't seen before (so we
disabled it). But if there is a reason for it ...

>reordering. So I started lnst-slave on the controller but oops, the
>bridge went down because bridge module is removed in the cleanup phase.
>
>So, here's the proposal. I'd like to add "module_cleanup" attribute to
>machineconfig info tag. If it's set to "no" the cleanup phase won't be
>executed even if user passes -c option to the controller.
>
>Let me know if this makes sense or if you see different approach to this
>case.
>
>Thanks
>-Jan
>_______________________________________________
>LNST-developers mailing list
>LNST-developers at lists.fedorahosted.org
>https://lists.fedorahosted.org/mailman/listinfo/lnst-developers

[prev in list] [next in list] [prev in thread] [next in thread]