Hi Brian, The new websphere_application_server module builds upon the great start provided by Josh Beard and adds some important bug fixes and polish to the defines, types, and providers while maintaining feature parity with the old module. This is an introductory release in the puppetlabs namespace on the Forge that provides a foundation for us to iterate and build towards an eventual supported module.
The ibm_installation_manager issue you pointed out was fixed in a recent refactor I believe. The ibm_pkg provider no longer requires the 'ps' fact. The PR for this can be found here: https://github.com/puppetlabs/puppetlabs-ibm_installation_manager/pull/11/files#diff-da882ddff62c30975d57d19358066749L104. With much gratitude to Corey Osman (@logicminds) for the contribution. This fix has since been released to the Forge(https://forge.puppet.com/puppetlabs/ibm_installation_manager) and is in version 0.2.0 and newer. Thanks, Bryan Jen On Monday, June 13, 2016 at 7:33:12 AM UTC-7, Brian Fekete wrote: > > Whats the difference between the old module and the new one? I see nothing > different except that you changed the module name. > > Old one: https://forge.puppet.com/joshbeard/websphere > New one: https://forge.puppet.com/puppetlabs/websphere_application_server > > Also the IBM installation manager which is a prerequisite to Websphere is > broken because Puppet removed the ps fact it relied on. > > On Thursday, June 2, 2016 at 4:23:15 PM UTC-4, Michael Olson wrote: >> >> Hi everyone - Today, we announced the latest in Puppet Enterprise 2016.2 >> (available beginning later this month), a new set of Puppet modules and >> integrations, and more from Project Blueshift. These updates continue to >> make it easier to manage today’s technology while evolving your modern >> cloud and container practices, in a standard way. >> >> *Check out What’s New in Puppet Enterprise 2016.2* >> >> - *New change success reporting *- The Puppet Enterprise 2016.2 >> release provides a new level of granularity to show which changes that >> ran >> with a cached catalog were successful, which failed, and which failed but >> were able to revert to the last known, good state. This means that you >> can >> get a clearer sense of how failures affect the environments you are >> managing. >> - *Classify nodes in Puppet Enterprise web UI based on structured and >> trusted facts *- Without granular access to metadata about >> infrastructure, it can be challenging to classify and manage servers >> efficiently and make rapid changes. The Puppet Enterprise node classifier >> web UI now consumes richer metadata about infrastructure so nodes can be >> segmented with more granularity to drive change more quickly, efficiently >> and with greater consistency. >> >> *You can register for our upcoming webinar to learn more about what's >> new: *http://info.puppet.com/2150-Whats-New-in-PE-2016.1-Register.html >> >> *A Common Language and Data Center Standard* >> >> We've also added to the broad range of technology you can manage with >> Puppet through new integrations and modules for: >> >> - *IBM z Systems and LinuxONE* - In partnership with IBM, we'll have >> a new agent to manage Linux VMs on IBM z Systems and LinuxONE. >> - *WebSphere -* We help simplify the management of WebSphere with a >> new module that provides a repeatable and consistent process for >> deploying >> WebSphere, including deployment managers, application servers, and IBM >> HTTP >> Servers (IHS) for WebSphere Application Server. >> - *Cisco* - With the latest release of the Puppet Supported Cisco >> module, we’ve added support for the 5k, 6k, and 7k line of Cisco Nexus >> switches, in addition to existing support for the 3k and 9k series of >> switches. >> >> *New Ways of Using Docker and Puppet* >> >> In April, we launched Project Blueshift, our dedicated way of engaging >> with leading-edge technologies and their communities. So far, we’ve focused >> on providing modules, examples and guidance to help you deliver and operate >> modern software like CoreOS, Docker (Compose, Swarm, Network, UCP), >> Kubernetes, Mesos and Mesosphere, and more. Today, we’re adding a new set >> of Docker images for running Puppet in Docker, released to Docker Hub. >> >> A set of Docker images for Puppet Server, PuppetDB and Puppet agent are >> now available on Docker Hub. Now, Puppet itself can be deployed and run >> within Docker, making it more portable and easier to maintain, test and >> scale. In addition to the images on the Docker Hub, we’ve created examples >> and guidance to help shed light on ways to use Docker with Puppet. >> >> *You can read all about what’s new and find links to learn more via our >> blog:* >> https://puppet.com/blog/use-puppet-in-docker-manage-ibm-websphere-z-systems-with-puppet-enterprise >> >> >> Thanks, >> Michael >> >> -- >> >> Michael Olson *| *Senior Product Marketing Manager >> 308 SW 2nd Ave., 5th Floor >> Portland, OR 97204 >> Puppet <http://puppet.com/>*. The shortest path to better software.* >> >> PuppetConf 2016 <http://2016.puppetconf.com/>, October 17-21, San Diego, >> California >> *Early Birds save $350* >> <https://www.eventbrite.com/e/puppetconf-2016-october-17-21-tickets-18750712887?discount=EarlyBird> >> - >> Register by June 30th >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c10e29d2-ed8e-4ba0-8602-6650a3987628%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
