Re: [atomic-devel] Proposing moving https://github.com/stefwalter/oci-kvm-hook into projectatomic

tps://github.com/stefwalter/oci-kvm-hook to be very, very >>> useful. Yes, there are other ways one can do it; see the thread in >>> https://github.com/stefwalter/oci-kvm-hook/issues/5 > >> Does Stef *want* it to be moved? It's his repo. > > See the issue l

Re: [atomic-devel] Running VMs in Openshift

On 30.03.2017 21:34, Colin Walters wrote: > On Thu, Mar 30, 2017, at 03:04 PM, Stef Walter wrote: >> After starting a VM in kubevirt, can access the qemu monitor or have >> libvirt access to that VM ... from a container in a kubernetes pod? > > To rephrase what Stef is saying

Re: [atomic-devel] Running VMs in Openshift

On 22.03.2017 14:59, Fabian Deutsch wrote: > On Tue, Mar 21, 2017 at 5:45 PM, Stef Walter wrote: >> One of the cool things you can do when implementing integration testing >> is staging the test dependencies using an OCI image. And scheduling >> integration tests in O

Re: [atomic-devel] Running VMs in Openshift

On 22.03.2017 10:19, Antonio Murdaca wrote: > > > On Mar 22, 2017 10:13, "Stef Walter" <mailto:st...@redhat.com>> wrote: > > That's pretty cool. I imagine there's no Openshift pull request or > branch yet where I can play with this?

Re: [atomic-devel] Running VMs in Openshift

5, Antonio Murdaca wrote: > CRI-O can already do VMs workflows with Clear containers (as opposed to > use Linux containers). Hopefully we'll have it in kubernetes soon and > openshift could use it just for virtual machines workloads. > > On Mar 22, 2017 05:50, "Stef Walter

Re: [atomic-devel] Running VMs in Openshift

On 22.03.2017 04:49, Karanbir Singh wrote: > On 21/03/17 16:45, Stef Walter wrote: >> One of the cool things you can do when implementing integration testing >> is staging the test dependencies using an OCI image. And scheduling >> integration tests in Openshift is also nice.

[atomic-devel] Running VMs in Openshift

One of the cool things you can do when implementing integration testing is staging the test dependencies using an OCI image. And scheduling integration tests in Openshift is also nice. For tests that integrate a full operating system, you need to start up one or more VMs running that operating sys

Re: [atomic-devel] F25: older versions of cockpit in atomic host

On 15.01.2017 22:03, Dusty Mabe wrote: > > I noticed today when comparing two trees, one from Dec25 and the > latest one, that the version of cockpit went backwards. > > !cockpit-bridge-126-1.fc25.x86_64 > =cockpit-bridge-120-1.fc25.x86_64 > !cockpit-docker-126-1.fc25.x86_64 > =cockpit-docker-120

Re: [atomic-devel] Fedora 26: Request for review of Release Blocking Deliverables

On 12.01.2017 11:43, Jan Kurik wrote: > Hi Atomic/Cloud team, > > as we are moving forward with Fedora 26 I would like to make sure we > have all the deliverables, which might or might not be blocking for > the release, identified on time. As such, I would like to ask you to > review the list of d

Re: [atomic-devel] should /etc/os-release mention atomic?

There are many fields in os-release. Indeed most should match RHEL == RHEL Atomic, but there should be a standard simple way to use the /etc/os-release API to get the precise, coherent, well-known, delivered-as-a-unit operating system version that is running on the system. This is what Jonathan is

Re: [atomic-devel] Replacing registry, atomic app on the home page

On 13.07.2016 20:12, Josh Berkus wrote: > On 07/13/2016 10:24 AM, Aaron Weitekamp wrote: >> On Jul 13, 2016 11:53 AM, "Josh Berkus" > > wrote: >>> >>> I'd like to replace Registry on the home page, because (a) it's not new >>> anymore and (b) it's not really ready to inst

Re: [atomic-devel] Python-pyudev instead of storaged

On 16.06.2016 10:37, Marius Vollmer wrote: > Hi, > > if I understand things right, adding storaged as a dependency to > cockpit-docker is not acceptable. Can I add python-pyudev instead? > > Incidentall, what about NetworkManager-team? So long term, the goal for Cockpit should be to run more in

Re: [atomic-devel] One-line project descriptions for Docs and the new website

On 20.04.2016 20:53, Josh Berkus wrote: > On 04/20/2016 11:53 AM, Josh Berkus wrote: >> Folks, >> >> For docs.projectatomic.io, and eventually for the new >> www.projectatomic.io, I'm doing logos and one-line descriptions for each >> atomic-associated project. >> >> Please take a look at it and upd

[atomic-devel] OSTree + Cockpit Next Step

Basic OSTree support is now in Cockpit 0.88. Thanks to everyone who helped make this happen. Will send around a demo in the release notes. Demo: https://youtu.be/Tmj0Nrkasmk Card: https://trello.com/c/5j0gCd3d/26-0-88-basic-ostree-updates The next step is to include cockpit-ostree into Fedora A

Re: [atomic-devel] Need owner of Atomic 2 Week releases

On 13.11.2015 17:47, Matthew Miller wrote: > On Fri, Nov 13, 2015 at 10:41 AM, Amanda Carter wrote: >> Hey folks, creating a separate thread for this longer term discussion. We're >> getting ready to release our first 2 week atomic update on Tuesday and Dusty >> Mabe has raised 2 potential relea

Re: [atomic-devel] Determining if a host is an atomic host

On 09.11.2015 17:45, Charlie Drage wrote: > I'm working on docker-machine integration for atomic host's. The > problem I'm facing is the fact that "atomic" isn't defined under > /etc/os-release, simply "fedora" or "centos". > > At the moment the only viable way to determine if an OS is an atomic >

Re: [atomic-devel] Introducing sen: terminal user interface for docker engine

On 27.10.2015 09:59, Tomas Tomecek wrote: > Quoting Joe Brockmeier (2015-10-27 01:55:17) >> Any chance this is going to be a Cloud feature for Fedora 24? (Probably >> jst a bit late to slip into F23 now.) >> >> Best, >> >> jzb >> -- >> Joe Brockmeier | Community Team, OSAS >> j...@redhat.com

Re: [atomic-devel] Cockpit in Super Privileged Container for older EL6 servers

On 20.10.2015 02:48, Donald DAvanzo wrote: > I am looking for a way to run docker on older Centos 6x installs in > which the image is el7 and super privileged so that Cockpit on el6 > servers can be seen by our main cockpit install. > > We have several hundred vms in our cloud that are el6x and wi

[atomic-devel] Cockpit OSTree Feature and Designs

Peter is implementing an OSTree feature in Cockpit based on the new rpm-ostree daemon mode: https://raw.githubusercontent.com/cockpit-project/cockpit-design/master/software-updates/software-updates-ostree-alt.png https://github.com/cockpit-project/cockpit/wiki/Atomic:-OSTree-Update Here's a tre

Re: [atomic-devel] awesome journald as a fully supported docker log driver got merged.

On 14.09.2015 14:53, Daniel J Walsh wrote: > > > On 09/14/2015 02:02 AM, Nick Coghlan wrote: >> On 13 September 2015 at 21:39, Daniel J Walsh wrote: >>> https://github.com/docker/docker/pull/13707 >>> >>> Nice work Nalin Dahyabhai >>> >>> I think we should switch this to the default. This would

Re: [atomic-devel] AVCs on fedora atomic host 91f0a3478e preventing ssh login

On 15.09.2015 08:51, Tobias Florek wrote: >>> Try `ostree fsck`. If that gives you errors, `ostree fsck --delete; touch >>> /ostree/repo/transaction; atomic host upgrade` should reset things. >> >> Unfortunately that did not work (yet). > > When an atomic host upgrade became available today, it

[atomic-devel] nss-kubernetes for service resolution

Unless you have DNS configured in kubernetes, software running in container pods need to manually check environment variables in order to talk with a kubernetes service. This makes it possible to do that resolution automatically via glibc nsswitch: https://github.com/stefwalter/nss-kubernetes He

Re: [atomic-devel] incorrect permissions

On 14.05.2015 15:33, Scott Collier wrote: > > > On 04/08/2015 10:30 AM, Dusty Mabe wrote: >> On Fri, Apr 03, 2015 at 12:34:38AM -0500, Scott Collier wrote: >>> I was testing cockpit on the F22 Atomic image and ran into this issue. >>> Cockpit would start, but I could not connect to it because SSH

Re: [atomic-devel] API to leverage during the install phase of a container?

On 12.05.2015 08:20, Fabian Deutsch wrote: > - Original Message - >> - Original Message - >>> From: "Fabian Deutsch" >>> To: atomic-devel@projectatomic.io >>> Sent: Monday, May 11, 2015 8:54:13 AM >>> Subject: [atomic-devel] API to leverage during the install phase of a >>> con

[atomic-devel] Fedora Atomic build broken due to DNF

It seems the Fedora 22 Atomic build is broken again. This time due to the switch to DNF: > ... > yum> install kubernetes > yum> install etcd > yum> install flannel > yum> install docker > yum> install python-docker-py > yum> run > Waiting for yum... > Yum command has been deprecated, use dnf inste

Re: [atomic-devel] We are working on Roles Based Access Control for docker.

On 01.04.2015 10:34, Pavel Odvody wrote: > On Tue, 2015-03-31 at 17:02 -0400, Colin Walters wrote: >> On Tue, Mar 31, 2015, at 04:35 AM, Pavel Odvody wrote: >> >>> It's supposed to work in the following way: >>> - docker daemon is started with the --trusted flag, this labels the >>> process as SELi

[atomic-devel] SSH broken after rebase to f22 local build

On 13.03.2015 13:16, Colin Walters wrote: > On Sun, Mar 8, 2015, at 01:59 PM, Stef Walter wrote: >> >> Tried it out, and after the rebase/reboot I could no longer SSH into the >> atomic host. sshd would drop my connection while negotiating host keys. >> I don't h

Re: [atomic-devel] F22 atomic currently broken?

On 26.03.2015 20:37, Colin Walters wrote: > To unblock rel-eng though, I pushed: > https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?h=f22&id=799cf4a7b87e09e0dc0b5d5c53562d3d50c181f2 Thanks! That got me further. Although I get this now: > > > > > > > > > > > > > > > > > > > > > > > > >