New SwitchYard AS7 Management Extensions

[rcernich]

Hey all,

The following describes the new adminstration functionality exposed through the AS7 management API.  These are not yet in upstream/master, but a summary of the changes can be found here: https://github.com/rcernich/core/commit/d248aab9a65600f8e9fbf916d24213f177d82a62

The following operations will be added to the "/subsystem=switchyard" addres:

• get-version - returns the version of the SwitchYard system.
• list-applications - returns a list of all applications deployed on SwitchYard.
• get-application - returns detals about a deployed applications (currently, its name and list of services).
• list-components - returns a list of all installed SwitchYard components.
• get-component - returns details about one or more a component.
• list-services - returns a list of all services deployed on SwitchYard.
• get-service - returns details about one or more coomponent (e.g. interface name, etc.).

In addition to the above operations, a SwitchYard specific model will be added to all SwitchYard deployments.  This can be accessed through the following management address:  /deployment=<archive name>/subsystem=switchyard/application=<application name>.  Invoking "read-resource" from that address will provide all details about the deployment: application name and all services (including all details).

These will all be accessible through the AS7 management CLI (jboss-admin.sh/bat).  They will also be used by the SwitchYard web console.

As always, any and all feedback is welcome.

Rob

[kcbabo]

Hey Rob,

Has the web app been updated to display this new information?  The list of operations you provided sounds reasonable, but I think it would be easiest for folks to provide feedback when looking through the pretty admin pages. :-)  Also, does the CLI just automatically work based on the management model we have exposed or do we have to do additional work there?

One thing we may have overlooked in the initial admin API is the ability to just fetch the deployment descriptor itself as a String.  This goes back to whether we have a deployment-level entity on top of the existing application entity that's there today.  Anyway, something to consider moving forward.

cheers,

keith

[rcernich]

Hey Keith,

Has the web app been updated to display this new information?  The list of operations you provided sounds reasonable, but I think it would be easiest for folks to provide feedback when looking through the pretty admin pages. :-)  Also, does the CLI just automatically work based on the management model we have exposed or do we have to do additional work there?

I'm in the process of updating the web application.  I should have something ready in the next few days.  As for the managment CLI, that will be available as soon as  SWITCHYARD-344 is pulled (which depends on SWITCHYARD-345).  The management operations are exposed through the code in org.switchyard.as7.extension.admin, of which most of the heavy lifting is done by ModelNodeCreationUtil (with a decent amount of code required to document the interface in SwitchYardSubsystemProviders).

The web console currently uses the management API on the backend to process the requests.

One thing we may have overlooked in the initial admin API is the ability to just fetch the deployment descriptor itself as a String.  This goes back to whether we have a deployment-level entity on top of the existing application entity that's there today.  Anyway, something to consider moving forward.

I'll keep that in the back of my head.

Thanks for the feedback,

Rob

[kcbabo]

Sounds good.  I reviewed the pull for 345 and left a comment on it.  I didn't see a pull request for SWITCHYARD-344?