#151: Need owner to define basic container smoke testing requirements
Reporter: acarter | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
The release tooling team will begin shipping layered images officially in
F25. As part of that, we'll be creating an automated release workflow that
includes testing via Taskotron. In order to scope Taskotron requirements,
we need to know the core testing requirements are for basic smoke testing
that will be shared across containers. We need an owner to define those
tests initially. I'd also like to know whether that person would continue
to own them going forward or if ownership would fall to the group or
another individual at that time. This should be done soon so that we can
scope Taskotron work.
Note: Kushal has noted that the owner should be sure to discuss with the
internal Container Certification team
Ticket URL: <https://fedorahosted.org/cloud/ticket/151>
Fedora Cloud Working Group Ticketing System
So when we pointed the thing that makes new ostrees to the "correct"
location we started a new ostree repo that knows nothing about the old
I just did an upgrade and here is what I'm looking at:
[vagrant@vanilla-f24atomic ~]$ sudo rpm-ostree status
TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
2016-07-24 20:14:21 24.4 c4b2c5e08d fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
* 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic fedora-atomic:fedora-atomic/24/x86_64/docker-host
so what I was on was 24.39 and the upgrade went to 24.4.
are we ok with this?
I think the solution would be to delete the ostree at the new (correct)
location and cp the contents of the old ostree into place and go from there.
The alternative is to just leave it and eventually the version # will
be greater than 39 again.
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2016-07-27 from 17:00:00 to 18:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
On Jul 20, 2016 5:30 PM, "Adam Miller" <maxamillion(a)fedoraproject.org>
> On Wed, Jul 20, 2016 at 1:02 PM, Devan Goodwin <dgoodwin(a)rm-rf.ca> wrote:
> > A few comments regarding openshift-ansible. I think the master branch
in the repo can probably cover Fedora quite easily at least at this point
in time, I don't think there's a whole lot in there that would be an issue.
> > We're also quite well set up to deploy, manage, and upgrade
containerized OpenShift deployments. (however this all uses docker today)
This is only tested on RHEL and RHEL Atomic today (AFAIK) but the mechanism
for doing it should already cover CentOS and Fedora Atomic variants and I
suspect this would be extremely easy to get working, if it didn't just work
out of the box today.
> > We have not started down the system containers path in
openshift-ansible but we very much are looking forward to that, so the work
would be relevant and if the Fedora community began some of that work, I
think I can safely say we'd jump at the chance to work and get it merged
> > Please feel free to loop me in if there are questions, I genuinely
think you could be doing a lot of this very quickly with current master of
> +1 - Thanks
> This is something we're hoping to have at least a proof of concept in
> working order by Flock, so the time tables are definitely near-term.
Now that is a tight deadline, but I don't see why Devan and myself couldn't
help facilitate changes needed.
> > _______________________________________________
> > cloud mailing list
> > cloud(a)lists.fedoraproject.org
> cloud mailing list
Hot off the heels of Fedora Cloud WG (well kind of ... little lag
time in there) I took an action item during the Cloud WG Weekly
Meeting to write up a proposal for the Fedora Council on what was
being called "Project Foosion" during the Cloud FAD. In an attempt to
both not get into legal trouble with Foosion Software (yes, I know
the website isn't working yet but it does appear to be a software
company) and in hopes the name would not actually stick because it's
silly, I've simply renamed it "Project FAO" where the FAO stands for
Fedora + Atomic + OpenShift. We can properly paint the bike shed when
there is actually one standing and in need of a coat of paint (i.e. -
we at least have a working PoC).
In the mean time, please everyone go to the current Draft Objective
page and offer comments, feedback, and snide remarks.
 - http://foosion.net/