It is with great pleasure that the Fedora Project Announces the availability of the Fedora Docker Layered Image Build Service to the Fedora Contributor Community! The new service will provide trustworthy, consistent application images for Fedora Atomic and CentOS Atomic as well as other platforms.
In part 1 of this series, we used the OpenShift Ansible Installer to install Openshift Origin on three servers that were running Fedora 25 Atomic Host. The three machines we’ll be using have the following roles and IP address configurations:
| Role | Public IPv4 | Private IPv4 | |-------------|----------------|--------------| | master,etcd | 22.214.171.124 | 10.0.173.101 | | worker | 126.96.36.199 | 10.0.156.20 | | worker | 188.8.131.52 | 10.0.251.101 |
In this blog, we’ll explore the installed Origin cluster and then launch an application to see if everything works.
UPDATE: This issue has been resolved. Please see the update blog post
One of the features of the Fedora Atomic Host 25 release was decoupling Kubernetes from the base ostree for Atomic (this is true of the current CentOS Atomic Host as well). That is, Kubernetes is no longer in the base install, you need to add it in as system containers and/or an overlay. This is a step forwards for Atomic because it means that users can continuously update Atomic, and update Kubernetes on a different schedule which works for their cluster. Since Kubernetes gets released four times a year, this lets developers update to the latest version, and production users stay on their production version.
However, when we released Fedora Atomic 25, the containerized install wasn’t quite ready, and there were issues with installing Kubernetes using package layering which we hadn’t anticipated. At the time, we expected those issues to be resolved within a few days. Instead, some have taken longer than expected and are still unresolved or waiting on PR review.
The Fedora Atomic team is hard at work on getting a solution out for Kubernetes users and expect to have one before the holidays. If you are able to help with building or testing, please speak up on the Atomic Development mailing list; we could use your help. If you can’t help, wait for us to publish documentation of the new containerized Kubernetes before you rebase to 25. Bug fixes are still available for the Fedora 24 tree.
If you use Fedora Atomic, but do not use Kubernetes, this issue does not affect you. If you are using Kubernetes based on a containerized install already (via Kubeadm or Hyperkube), this issue is also not a problem for you. Unaffected users should rebase to Fedora Atomic 25 for updated libraries and platforms, including the latest OpenShift and Docker support.
Thanks for your patience, and we’ll see you on the mailing lists and IRC with any other issues.Add a comment »
Openshift Origin is the upstream project that builds on top of the Kubernetes platform and feeds into the OpenShift Container Platform product that is available from Red Hat today. Origin is a great way to get started with Kubernetes, and what better place to run a container orchestration layer than on top of Fedora Atomic Host?
We recently released Fedora
25, along with the
first biweekly release of Fedora 25 Atomic Host. This blog post
will show you the basics for getting a production installation of Origin
running on Fedora 25 Atomic Host using the OpenShift Ansible
OpenShift Ansible installer will allow you to install a
production-worthy OpenShift cluster. If you’d like to just
try out OpenShift on a single node instead, you can set up OpenShift with
oc cluster up command, which we will detail in a later blog
Cockpit’s build 125 has been released.
Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 123, 124 and 125.
Cockpit is now properly translatable
Cockpit is now properly translatable. It was a big task to extract all the translatable strings and make translations work consistently between the browser and installed tools like the bridge.
We now start also run the login user session with a proper locale and LANG environment variables.
You can help translate cockpit in Zanata, or if you find text in the front end that isn’t translatable, then please do report it.
Display OSTree signatures
Peter implement displaying OSTree tree signatures. You can tell where a certain update tree came from and who signed it.
New expandable views for storage partitions
Marius implemented expandable views in the Storage pages. These let you dive into the details of a particular partition without having to navigate away from the page describing where it lives.
Other storage fixes
Marius did work to fix many other storage related bugs. In particular Cockpit now deals properly with passphrases stored for LUKS encrypted devices, and also no longer offers to format read-only block devices.
Full testing on RHEL 7.3, Ubuntu 16.04 and Debian 8 Jessie
The Cockpit project started testing on Cockpit on RHEL 7.3, Ubuntu 16.04 and Debian 8 Jessie along the operating systems we tested earlier. These will be part of our usual continuous integration, where we boot thousands or tens of thousands of instances per day to test changes and contributions.
Marius fixed many bugs we found, and filed operating system bugs in the issue trackers for those operating systems.
You can see the which operating systems we test Cockpit on:
There’s no Debian Jessie repository yet, but hopefully we can have that ready as time permits.
System shutdown can be scheduled by date
Fridolin did work a long time ago, so that users could select a specific date and time to schedule a shutdown or reboot of the system. Stef finished that work added tests and it’s now in Cockpit.
Properly terminate user sessions on the Accounts page
The Accounts page now properly terminates user sessions when the Terminate Session button is clicked. We use the correct systemd loginctl commands.
You can get Cockpit here.
Cockpit 125 is available in Fedora 25.Add a comment »