Hi cloud group,
based on , the working groups are expected to gather feedback from
users that should help defining next steps in Fedora.next development.
Since there are no direct users of Env & Stacks group and it makes sense
to be able to segment the answers by audience, Env & Stacks group
decided to let other groups to ask their users some particular questions
, that are connected to Env & Stacks work, if it would be possible.
Thus, I'd like to find out whether there are some ideas already how to
gather feedback from your users or whether you plan to do something
where we can participate.
Thank you everyone for a great Fedora 22 release. Things are stable now,
before we can understand we will be in the alpha freeze for Fedora 23.
So this is a good time to start working on the new features list for Fedora
23. 23rd June is the last date to submit a new system wide change
for Fedora 23, 11th August is the alpha release for Fedora 23.
Below I have written few points which came up in different discussions.
Please feel free to comment/add/delete in this thread.
* Better user documentation for cloud. We need something better than
* Notification of pending updates in the base image. After login the
user should get a motd message saying which all updates are pending (I
have worked on this part time before).
* Reduce the base cloud image size (we also have
* testCloud (pushed back from Fedora 22 change list).
* https://github.com/vmware/tdnf this might help us to go another step
closer to remove Python stack from the cloud image.* Having a better
* workstation to cloud story (came up in the last week's meeting).
Fedora Cloud Engineer
CPython Core Developer
Director @ Python Software Foundation
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2015-07-08 from 17:00:00 to 18:00:00 UTC
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
At Summit, I talked briefly to Karanbir Singh from CentOS. CentOS has a
Jenkins system with a lot of hardware behind it (https://ci.centos.org/),
and they run all of their layered image builds* through that. KB
offered to run their tests on any images Fedora produces. That seems
cool, but I'm not sure how we could best take advantage of this. How
could we integrate such tests into our processes?
As a first step, does anyone have a problem with saying to CentOS,
"Cool! Start running those tests! Thanks!" — even if we don't know what
exactly what we're going to do with any results? I'm imagining that
once we get to $futurephase of the build service plan, layered images
will go through Bodhi just like RPMs, and at that point, this feedback
could be hooked in there. In the meantime, packagers of layered images
could simply be told to look manually.
The tests themselves, as I understand it, are documented at
by the way, including contribution information.
* See change proposal for a layered image build service for Fedora —
actually testing images which are produced is a next step specifically
listed as out of scope for the change itself.
Fedora Project Leader