summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/cockpit/cockpit-0.103.md42
-rw-r--r--content/cockpit/cockpit-0.104.md56
2 files changed, 98 insertions, 0 deletions
diff --git a/content/cockpit/cockpit-0.103.md b/content/cockpit/cockpit-0.103.md
new file mode 100644
index 0000000..9d207bd
--- /dev/null
+++ b/content/cockpit/cockpit-0.103.md
@@ -0,0 +1,42 @@
+Title: Cockpit Ubuntu PPA
+Date: 2016-04-20 15:45
+Tags: cockpit, linux, technical, kubernetes
+Slug: cockpit-0.103
+Category: release
+Summary: Cockpit releases every week. Here's highlights from 0.103
+
+Cockpit is the [modern Linux admin interface](http://cockpit-project.org/). There's a new release every week. Here are the highlights from this weeks 0.103 release.
+
+
+### Upload each Release to an Ubuntu PPA
+
+Each weekly release of Cockpit is now uploaded to an Ubuntu PPA. Here's how to make use of it:
+
+ sudo add-apt-repository ppa:cockpit-project/cockpit
+ sudo apt-get update
+ sudo apt-get install cockpit
+
+
+### Kubernetes Connection Configuration
+
+When a Kubernetes client wants to access the API of the cluster, it looks for a "kubeconfig" file to tell it how to find the cluster and how to authenticate when accessing the API. The usual location for this file is in the current user's home directory at the ```~/.kube/config``` file path. If that doesn't exist, then usually the cluster isn't available. This applies to both clients like the ```kubectl``` command as well as Cockpit's cluster dashboard.
+
+Cockpit can now prompt for this information, and build this file for you. If it doesn't exist, then there's a helpful "Troubleshoot" button to help get this configuration in place.
+
+<iframe width="853" height="480" src="https://www.youtube.com/embed/WSh7wYhAXrA" frameborder="0" allowfullscreen></iframe>
+
+
+### Remove jQuery Usage from cockpit.js API
+
+As part of stabilizing the internals of Cockpit, we removed jQuery usage from the cockpit.js file. [The javascript API itself](http://cockpit-project.org/guide/latest/api-base1.html) hasn't changed, but this change helps to help keep a stable API in the future.
+
+
+### Try it out
+
+Cockpit 0.103 is available now:
+
+ * [For your Linux system](http://cockpit-project.org/running.html)
+ * [Source Tarball](https://github.com/cockpit-project/cockpit/releases/tag/0.103)
+ * [Fedora 24](https://bodhi.fedoraproject.org/updates/cockpit-0.103-1.fc24)
+ * [COPR for Fedora 23, CentOS and RHEL](https://copr.fedoraproject.org/coprs/g/cockpit/cockpit-preview/)
+
diff --git a/content/cockpit/cockpit-0.104.md b/content/cockpit/cockpit-0.104.md
new file mode 100644
index 0000000..26b3530
--- /dev/null
+++ b/content/cockpit/cockpit-0.104.md
@@ -0,0 +1,56 @@
+Title: Cockpit 0.104
+Date: 2016-04-28 15:21
+Tags: cockpit, linux, technical, kubernetes
+Slug: cockpit-0.104
+Category: release
+Summary: Cockpit releases every week. Here's highlights from 0.104
+
+Cockpit is the [modern Linux admin interface](http://cockpit-project.org/). There's a new release every week. Here are the highlights from this weeks 0.104 release.
+
+
+### Kubernetes iSCSI Volumes
+
+Peter added support for iSCSI Kubernetes Volumes in the Cockpit Cluster dashboard. When you
+have container pods that need to store data somewhere, it's now real easy to configure use
+an iSCSI initiator. Take a look:
+
+<iframe width="853" height="480" src="https://www.youtube.com/embed/ytNGsIDYNSQ" frameborder="0" allowfullscreen></iframe>
+
+
+### Listing View Expansion
+
+Andreas, Dominik, and I worked on a better listing view pattern. In Cockpit we like to give
+admins the option to expand data inline, and compare it between multiple entries on the same
+page. But after feedback from the [Patternfly folks](https://www.patternfly.org/) we added an
+explicit expander to do this.
+
+<iframe width="853" height="480" src="https://www.youtube.com/embed/myXr_hnr5Jg" frameborder="0" allowfullscreen></iframe>
+
+
+### Tagging Docker Images in the Registry
+
+The Atomic Registry and Openshift Registry support mirroring images from another image registry
+such as the Docker Hub. When the images are mirrored, they are copied and available in your
+own registry. Cockpit now has support for telling the registry which specific tags you'd like
+to mirror. And Aaron is adding support for various mirroring options as well.
+
+<iframe width="853" height="480" src="https://www.youtube.com/embed/MJzqob5AYI8" frameborder="0" allowfullscreen></iframe>
+
+
+### From the Future
+
+Marius has a working proof of concept that lets you configure where Docker stores container and image
+data on its host. Take a look at the demo below. Marius adds disks to the container storage pool:
+
+<iframe width="960" height="720" src="https://www.youtube.com/embed/9YiG4AY6HeY?rel=0" frameborder="0" allowfullscreen></iframe>
+
+
+### Try it out
+
+Cockpit 0.104 is available now:
+
+ * [For your Linux system](http://cockpit-project.org/running.html)
+ * [Source Tarball](https://github.com/cockpit-project/cockpit/releases/tag/0.104)
+ * [Fedora 24](https://bodhi.fedoraproject.org/updates/cockpit-0.104-1.fc24)
+ * [COPR for Fedora 23, CentOS and RHEL](https://copr.fedoraproject.org/coprs/g/cockpit/cockpit-preview/)
+