In regards to JON
Hello,
I'm working on some proof of concept stuff around Satellite, JON, EAP, and EWS. We have quite a bit up and running at this time, but I feel as though the process could be improved with a little bit of 'best practice' knowledge.
What is the release date for JON 3.3? I think that would be the best version to use as a launch pad because of the large performance enhancements gained by using Casandra and the changes to the UI.
Ideally, I would like to grant our many development groups access to JON - but it just seems like it's too powerful and difficult to lock down. I would only want them to have the ability to deploy bundles to their own resources. Are there any documents out there that outline how JON is being used in large organizations?
Thank you.
Responses
Bryan,
I realize you posted this back in May and some how it has gone unanswered all this time. I am very sorry for that. I can try to answer some of your questions:
What is the release date for JON 3.3?
We are not able to provide product release dates. The best I can estimate is that the plan is for fourth quarter of this year.
Are there any documents out there that outline how JON is being used in large organizations?
Not that I am aware of. I have done some looking around the published content and the only relevant information that I found was JBoss Operations Network – How to manage strategies around multiple environments and JBoss ON - production sizing. Neither of these articles appear to really cover what you are after.
Now, to try to provide some input on the topics you mention:
I think that would be the best version to use as a launch pad because of the large performance enhancements gained by using Casandra and the changes to the UI.
Keep in mind that the existing 3.2 line can be used and easily upgraded to 3.3 later. However, you are correct -- Many of the performance improvements and UI changes will make their way to 3.3. Considering a 3.3 release is insight, it does make sense to launch a new endeavor with plans to use the latest.
Ideally, I would like to grant our many development groups access to JON - but it just seems like it's too powerful and difficult to lock down.
If you are most concerned by resource management and groups, please keep in mind that JBoss ON can have its roles mapped to your organization's LDAP groups and users. This may make managing user permissions a bit easier and providing what you would consider a locked down environment.
If you are referring to all the different monitoring and management capabilities available from the JBoss ON UI, keep in mind you have access to the JBoss ON API. In some cases, it may be necessary to integrate JBoss ON management or monitoring functions into your existing applications. You integrate your application or other reporting processes using the JBoss ON REST API or its remote client API.
I would only want them to have the ability to deploy bundles to their own resources.
Beginning in JBoss ON 3.2, logical bundle groups were introduced. Not only will this allow you to organize your bundles, this will also allow you to map a user role to a bundle group. Because roles can be assigned to one or more users, this provides you the ability to manage these permissions based on the user's job role or function. Finally, because resources can be assigned to user roles, this provides you fine grained control over who can create bundles and to what resources they can deploy available bundles. For more details about bundle groups, see Managing Bundle Groups in the 3.2 product documentation.
I hope this provides you with what you need and may be useful for others that may have had the same questions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
