Comment 3 for bug 1470017
Revision history for this message
| sharan (saran110) wrote Re: Initial commit for WebSphere Extreme Scale | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Hi Matt,
The issues related to icon.svg and variable cfg_im_pkg_name is resolved.The config-change hook is not going into error state.
I tested the charm by giving multiple "juju-set” command and config-changed hook got invoked every time.I was not able to reproduce any failure.Can you please elaborate more on the scenario where you were not able to initiate more than one config-changed event with the “juju set” command.
Regarding the scenario where WXS can have relation with other charms like WAS , I checked with product team.According to them , WebSphere eXtreme Scale can be integrated with other products, such as WebSphere Application Server and WebSphere Application Server Community Edition. As of now we have charm available for WebSphere application Server only.WAS can be integrated with WXS server or client type only , not WXS standalone which is the one we have charmed.
To test this relation with other charms we don't have any charm as of now in store which we can integrate with WXS standalone.In-case in future it is available ,we can test this scenario
We can have multiple WXS standalone deployments on different containers and establish a peer relation among them.To establish the peer relation we need to do some manual steps.I have updated the README with the link providing this information.
Thanks,