Project Atomic integrates the tools and patterns of container-based application and service deployment with trusted operating system platforms to deliver an end-to-end hosting architecture that’s modern, reliable, and secure.
A remote manager for GNU/Linux servers
- Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.
- Cockpit makes it easy for any sysadmin to perform simple tasks, such as administering storage, inspecting journals and starting and stopping services.
- Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface.
- You can monitor and administer several servers at the same time. Just add them with a single click and your machines will look after its buddies.
Cockpit and Docker
Cockpit also makes it easy to monitor and administer Docker containers running on Cockpit-managed servers such as Project Atomic hosts.
- Monitor resources consumed by containers
- Adjust resources available to containers
- Resource limits enforced by the CGroup subsystem in the Linux kernel
- Adjust CPU shares
- Assign memory limits
- More CGroup policy controls to come
- Stop, Start, Delete and Commit container instances
- Run and Delete container images
Starting and Using Cockpit
Cockpit is in beta/preview at this time, but you can still try it out and help test! A preview is included with the image. For more information, see the Cockpit project page.
- After starting your atomic host, you need to enable the cockpit service and socket:
[root@fedora21 ~]# systemctl enable cockpit.socket
[root@fedora21 ~]# systemctl start cockpit.socket
- You can now use the cockpit management interface at http://yourhost:9090
Contain copied from Project Atomic website: http://www.projectatomic.io/docs/cockpit/
Step1 : Login to web GUI with regular root username & password.
Step2 : Hosts Details / Status, we can add multiple hosts.
Step3 : Hosts Machine Resource Status report.
Step4 : System Services Status
Step5 : System Networking Status
Step6 : Managing Resource by setting up resource limit for a container
Step7 : Running a container with /bin/bash shell.
Step8 : Stating a New Container with Set of command & cpu / memory limit.
Step9 : Monitoring the container standard out on /bin/bash prompt via GUI