Comments (4)
Important information extracted from a comment in PR #79.
- Unfortunately only a few subsystems have
update-properties
(e.g./subsystem=logging/periodic-rotating-file-handler=FILE:update-properties(...)
) and a composite operation ofwrite-attribute
is indeed a more generic solution. - My main concern is more related to the case above (you need to disable a resource in order to change it) and deployments dependencies on resources, so if you have, for example, an EAR that depends on a datasource, a queue and a remoting connector, you won't be able to perform some changes in theses resources while the deployment is up (even with write-attribute). [1]
[1] In practice I've seen two ways to realize this: (1) change configuration XML (i.e. offline changes) or (2) disable deployment, change resources and enable it again. Both alternatives imply in a small downtime, and it might be related to JBoss AS 7+ architecture (subsystems are lazily loaded).
- I still can't see how we are going to implement more complex scenarios using just Puppet. Lately I've been thinking that you should use an orchestration tool (MCollective, Capistrano, Fabric, CFEngine) in conjunction with Puppet to perform operations that will put you in the desired state. What do you think? Are we able to put this dependency resolution intelligence in our custom types or is it too application-specific?
from puppet-wildfly.
Ok,
I think some things are not possible or can make the code/procedure pretty complex. So it keep it simple and off course it should be supported by the jboss core ( we don't want to do their work).
but if you want to do manually what are the steps you should do and do you also have some downtime of the resource.
Just brainstorming ( maybe I think to simple ), maybe the administrator should say on the datasource that a particular resource is dependent, check if there is a change on the datasource, we will try to disable the resource, do the datasource change and enable it again.
from puppet-wildfly.
Most of the time this has been handled by building the new resource beside the old resource with a different name. It's dirty, but it's a good way to keep track of your changes.
Another effective strategy is to rollback standalone.xml
to it's initial state and reapply all resources. It could be possible to make Puppet work in conjunction with configuration history[1] to accomplish this seamlessly. (i.e. pass some sort of flag to build your new configuration on top of initial configuration)
Another update: Offline changes is not a constraint anymore since we have Offline CLI [2] in EAP 7+ / Wildfly 9+.
[1] https://docs.jboss.org/author/display/AS71/Configuration+file+history?_sscc=t
[2] https://developer.jboss.org/wiki/OfflineCLIWork
from puppet-wildfly.
operation-headers
with ordering looks promising. Will create a separate issue for OfflineCLI and --server-config
parameter.
from puppet-wildfly.
Related Issues (20)
- Error: Could not set 'file' on ensure: No such file or directory @ dir_s_mkdir HOT 2
- JBOSS-EAP with **systemctl start jboss-eap** don't works from another machine just locally HOT 1
- where the log file is stored on Puppet Agent by this module HOT 1
- on SUSE Linux /etc/init.d/jboss-eap: line 13: /etc/init.d/functions: No such file or directory HOT 1
- wildfly_restart functionality issues
- how to install und build multiple standalone instances in the same machine
- Need a way to install module with multiple jar files as source HOT 1
- Transfer this module to voxpupuli HOT 22
- wildfly::jgroups::stack::tcpping fails with "No resource definition" HOT 1
- Update test environment for Ruby 3, Puppet 7, and related Gems HOT 1
- Add parameters to domain.conf variables PROCESS_CONTROLLER_JAVA_OPTS and HOST_CONTROLLER_JAVA_OPTS
- Replace MaxPermSize with MaxMetaspaceSize in domain.conf template HOT 1
- `wildfly::host::server_config` with `ensure => absent` in already absent server tries to stop it and fails with timeout
- Include support for CLI API for actions currently performed via HTTP API HOT 2
- Multiple calls to defined type wildfly::host::server_config cause "Duplicate resource" error HOT 3
- class wildfly::setup hardcodes subsystem when setting up remote user HOT 2
- Installer download fails because install_cache_dir doesn't exist
- Module configures service only as sysvinit, regardless of actual init system, when $version < 10 HOT 1
- Update Wildfly download URL for version >= 25
- Support for Wildfly 31.0.0
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppet-wildfly.