[wildfly-dev] JBoss MSC Plans

[Brian Stansberry]

Thanks, Richard. Comments in-line.

On Thu, Jan 4, 2018 at 7:56 AM, Richard Opalka <ropalka at redhat.com> wrote:

> Hi everyone,
>
>    I would like to outline a brief JBoss MSC Plans for Year 2018.
>
> Goals defined below address both:
>  * Cloud First Effort
>    - Reduce WildFly memory footprint
>

Do you have a sense of how much we're talking about here, e.g. from a
standalone server using the standalone-full.xml config and no deployments?


>    - Speed up WildFly boot time
>

Same question here. A reload takes a couple hundred ms of which my guess is
MSC is a quite small part.


>  * Potential Migration to MSC 2
>
> MSC Library Goals:
>  * SHORT TERM GOALS (MSC 1.2.x, 1.3.x)
>    [1] simplify MSC state machine - deprecate useless MSC internal states
>        (e.g. REMOVED, WONT_START, WAITING, REMOVING, STOPPING maybe others)
>    [2] deprecate API exposing MSC internals
>        (e.g. replace ServiceListener with LifecycleListener)
>    [3] deprecate MSC Values, Injections & Injectors and provide
> alternative API
>        (alternative API should have same minimalistic memory requirements
> like MSC 2)
>  * LONG TERM GOALS (MSC 1.4.x)
>    [4] remove deprecated APIs and all deprecated stuff
>
> WildFly MSC Integration Goals:
>  + SHORT TERM GOALS (WildFly 12)
>    * replace ServiceListeners with LifecycleListeners (LifecycleListeners
> don't expose MSC internals)
>    * eliminate MSC optional dependencies from WildFLy Core
>

Sounds good. The basic issue there is the modeling of optional module
dependencies using MSC services, and IIRC you have an alternate approach in
mind. DomainModelControllerService also has one for some reason but I
figure that can be eliminated easily enough.


>    * eliminate MSC Values, Injections & Injectors and migrate to
> alternative API
>

This sounds like a very large task for WF 12, for which only some weeks of
dev time remain.


>    * WildFly Management Layer should not expose MSC APIs as its public API
>      (complicates potential migration to MSC2 and breaks encapsulation)
>

I can't see this happening in WildFly 12. Let's talk about it when we meet
up at the end of the month.

 + LONG TERM GOALS (WildFly versions targeting next major EAP)
>    * eliminate MSC optional dependencies from WildFly (probably via
> Capabilities)
>      (MSC Optional Dependencies have been fixed recently but there's still
> performance issue
>      - in worst case scenario if service A has N optional dependencies
>      it may happen service A is restarted N times before it is stabilized
> in UP state)
>
> Feedback and comments more than welcome!
>
> --
> Rio
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20180105/3089a8c5/attachment.html