Containers are one of the top trend today. Starting working or playing with them could be really hard also if you’ve well understood the theory at their base.
With this article I’ll try to show you some useful tips and tricks to start into containers world, thanks also to the great web interface provided by the Cockpit project.
Cockpit is an interactive server admin interface. You’ll find below some a of its great features:
- Cockpit comes “out of the box” ready for the admin to interact with the system immediately, without installing stuff, configuring access controls, making choices, etc.
- Cockpit has (as near as makes no difference) zero memory and process footprint on the server when not in use. The job of a server is not to show a pretty UI to admins, but to serve stuff to others. Cockpit starts on demand via socket activation and exits when not in use.
- Cockpit does not take over your server in such a way that you can then only perform further configuration in Cockpit.
- Cockpit itself does not have a predefined template or state for the server that it then imposes on the server. It is imperative configuration rather than declarative configuration.
- Cockpit dynamically updates itself to reflect the current state of the server, within a time frame of a few seconds.
- Cockpit is firewall friendly: it opens one port for browser connections: by default that is 9090.
- Cockpit can look different on different operating systems, because it’s the UI for the OS, and not a external tool.
- Cockpit is pluggable: it allows others to add additional UI pieces.
Continue reading “Cockpit: Your entrypoint to the Containers Management World”
JBoss EAP 7 was recently released, and brings with it a whole host of new features and support, such as support for Java EE 7, Undertow (a highly scalable web server), reduced port usage, graceful shutdown, improved GUI and CLI management, and much more.
Go ahead and download it, unzip, and run
bin/standalone.sh and check out all these great features. What’s that? It didn’t work? Did you check that your JRE is compatible? Are there outstanding incompatibility or security issues that may be resolved in an available patch? Perhaps you’ve already installed it elsewhere on your system and you are trying to install a conflicting version. You’re not running it as root are you?
ZIP files are awesome for getting bits up and running quickly (as a developer I use them myself quite a bit), but its simplicity hides many issues related to production software management, such as those I just mentioned. It’s perfect for cross-platform developers or those non-RHEL CI/CD setups but for production RHEL systems it’s the tl;dr of enterprise software deployment. This is where Red Hat and RPM can help. You can be sure of what you’re installing, that it’ll work securely, that you’ll know it’s there when asked, and that it’ll be manageable using your other investments (think RHEV+RHEL+Satellite+JBoss).
Continue reading “Installing JBoss EAP 7 on RHEL using RPMs”
Have you wanted to use software collections but found packaging has kept you at bay? Tried rebuilding a package only to find it give you weird errors you’ve not seen before? In this blog post we’ll learn how to configure and use mock to build RPM packages for the Python 2.7 Software Collection. Along the way we’ll learn why we can’t use standard mock configurations, and what makes Software Collections (SCL) mock configurations different.
Continue reading “Using Mock to build Python27 Software Collections packages for RHEL6”