Re: RCTL and VIMAGE for 11.0-RELEASE

[Bjoern A. Zeeb]

> On 23 Jan 2016, at 06:41 , Ernie Luzar  wrote:
> 
> Bjoern A. Zeeb wrote:
>>> On 24 Aug 2015, at 19:08 , Mark Felder  wrote:
>>> 
>>> What is preventing RCTL from being enabled right now? Any known/serious
>>> blockers?
>> It’s enabled in GENERIC.
>>> And the same for VIMAGE? I know there were issues with some firewalls,
>>> but I'm not sure where that stands today. Does it degrade network
>>> performance in a measurable way?
>> Ignoring performance for a second, there is more than just firewalls that 
>> needs to be done.  I started writing a plan for the next 4 months 
> yesterday.  Most of this was done a few years ago and never made it to HEAD.  
> It needs to be re-validated.  If my plan comes together we’ll have another 4 
> month window before the 11 release cycle will start.
>> /bz
> 
> It's been 5 months since the above was posted. What is the status of VIMAGE 
> as part of base in 11.0-RELEASE?

There is ongoing work; it was slightly delayed to the original plan.  Hope it 
all hits HEAD before early/mid March.  Expect more patches soon.

/bz
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: RCTL and VIMAGE for 11.0-RELEASE

[Ernie Luzar]

Bjoern A. Zeeb wrote:

On 24 Aug 2015, at 19:08 , Mark Felder  wrote:

What is preventing RCTL from being enabled right now? Any known/serious
blockers?


It’s enabled in GENERIC.



And the same for VIMAGE? I know there were issues with some firewalls,
but I'm not sure where that stands today. Does it degrade network
performance in a measurable way?


Ignoring performance for a second, there is more than just firewalls that needs to be done.  I started writing a plan for the next 4 months 
yesterday.  Most of this was done a few years ago and never made it to 
HEAD.  It needs to be re-validated.  If my plan comes together we’ll 
have another 4 month window before the 11 release cycle will start.


/bz



It's been 5 months since the above was posted. What is the status of 
VIMAGE as part of base in 11.0-RELEASE?


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: RCTL and VIMAGE for 11.0-RELEASE

[Miroslav Lachman]

Mark Felder wrote on 08/24/2015 21:29:



On Mon, Aug 24, 2015, at 14:18, Bjoern A. Zeeb wrote:

On 24 Aug 2015, at 19:08 , Mark Felder  wrote:

What is preventing RCTL from being enabled right now? Any known/serious
blockers?


It’s enabled in GENERIC.


If RCTL is in GENERIC, can somebody look on to this problem with swapuse?
https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/082019.html

IMHO it shoul be fixed or better documented in man pages.

Miroslav Lachman

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RCTL and VIMAGE for 11.0-RELEASE

[Mark Felder]

Hi all,

Now that the internet has reached peak container, I would like to see
less barriers of entry for deploying such environments on FreeBSD. This
includes enabling RCTL and VIMAGE in CURRENT so we can hopefully ship
them with 11.0-RELEASE.

I know of a moderately sized deployment of jails+RCTL to keep customer
webhosting in check and it purportedly works well. I don't have a lot of
experience with VIMAGE, but it worked in a few lab environments I played
with a while ago.

What is preventing RCTL from being enabled right now? Any known/serious
blockers?

And the same for VIMAGE? I know there were issues with some firewalls,
but I'm not sure where that stands today. Does it degrade network
performance in a measurable way?


Thanks
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: RCTL and VIMAGE for 11.0-RELEASE

[Bjoern A. Zeeb]

 On 24 Aug 2015, at 19:08 , Mark Felder f...@freebsd.org wrote:
 
 What is preventing RCTL from being enabled right now? Any known/serious
 blockers?

It’s enabled in GENERIC.


 And the same for VIMAGE? I know there were issues with some firewalls,
 but I'm not sure where that stands today. Does it degrade network
 performance in a measurable way?

Ignoring performance for a second, there is more than just firewalls that needs 
to be done.  I started writing a plan for the next 4 months yesterday.  Most of 
this was done a few years ago and never made it to HEAD.  It needs to be 
re-validated.  If my plan comes together we’ll have another 4 month window 
before the 11 release cycle will start.

/bz


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: RCTL and VIMAGE for 11.0-RELEASE

[Mark Felder]

On Mon, Aug 24, 2015, at 14:18, Bjoern A. Zeeb wrote:
  On 24 Aug 2015, at 19:08 , Mark Felder f...@freebsd.org wrote:
  
  What is preventing RCTL from being enabled right now? Any known/serious
  blockers?
 
 It’s enabled in GENERIC.
 
 

This is great news!

https://svnweb.freebsd.org/base/head/sys/amd64/conf/GENERIC?r1=282900r2=282901;

It also appears to be in 10.2-RELEASE -- I missed this. That helps a
lot...

  And the same for VIMAGE? I know there were issues with some firewalls,
  but I'm not sure where that stands today. Does it degrade network
  performance in a measurable way?
 
 Ignoring performance for a second, there is more than just firewalls that
 needs to be done.  I started writing a plan for the next 4 months
 yesterday.  Most of this was done a few years ago and never made it to
 HEAD.  It needs to be re-validated.  If my plan comes together we’ll have
 another 4 month window before the 11 release cycle will start.
 
 /bz
 
 

Thanks for taking time to fill me in on this.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org