Fedora Cloud Images Home page - oVirt

2017-01-11 Thread Sandro Bonazzola 
Hi,
I'm looking at https://alt.fedoraproject.org/cloud/ and I'd like to ask to
mention oVirt[1] project as well
since oVirt can use Fedora 25 Cloud Base Images as well.
If this mailing list is not the right place to ask, can you please point me
to the correct place?

[1] https://www.ovirt.org/

Thanks,

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Please test new docker version with CVE

2017-01-11 Thread Dusty Mabe 

https://bodhi.fedoraproject.org/updates/FEDORA-2017-dbc2b618eb
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Atomic WG Workflow Proposal

2017-01-11 Thread Dusty Mabe 


On 01/11/2017 05:50 PM, Adam Miller wrote:
> Hello all,
> Recently I attempted to start a mailing list thread that was the
> product of a discussion on IRC about putting together an Atomic WG
> workshop session[0] at DevConf[1].
> 
> This was then discussed during today's Atomic WG Meeting[2] where it
> was decided that we should make this Workshop into a re-occurring
> Virtual Fedora Activity Day(FAD[3]) instead taking place every 2
> months.
> 
> I would like to propose the following:
> Each Virtual FAD occurs on a Thursday, the day after a Fedora
> Atomic WG meeting such that we can use the meeting the day before to
> plan out the work to be done at the Virtual FAD. All work will be
> tracked in a kanban[4] board, I've created one for this purpose in
> Fedora's Taiga instance[5] (Note: I don't know why my FAS name is in
> the URL, Taiga just does that).
> In the kanban board, we would create cards in the NEW column
> through out the two month cycle between Virtual FADs (these should
> correlate to tickets in pagure[6]), then on the meeting before the FAD
> we would "groom" the NEW cards that we want to accomplish on the
> following day of the Virtual FAD, these "groomed" cards would be
> placed into the READY column to signify they are ready to be worked
> on. On the day of the VFAD, participants/contributors would then
> assign a card to themselves that they want to work on, and move the
> card into "IN PROGRESS" so that everyone knows what is being worked on
> and nobody attempts to work on the same thing (unless that's
> intentional, in that case both people's names should be listed in the
> card description for reference). Once a task is done, then it should
> be moved to the DONE column. This will give a good reflection of what
> work was accomplished during the VFAD and we can (optionally) have a
> retrospective meeting after the VFAD about what went well, what didn't
> go well, and what we could do better next time. Also the day before
> the next VFAD at the start of the "grooming" session (the weekly
> Atomic WG meeting), all the previous VFAD's cards in the DONE column
> from the previous VFAD should be moved to ARCHIVED for posterity.

This sounds good but I'm not sure I'm ready to have work items broken
out into another place. Could we get something close by using labels
on issues in pagure? Really what I'm trying to do here is prevent
extra overhead and also prevent duplicated information where there is
a question of what is right and what is wrong? 

> 
> Cards created should be units of work that can feasibly be
> accomplished in a day or less worth of work.
> 
> I would like to ultimately propose we move to a more iterative cycle
> where we use this workflow weekly instead of dedicating a single day
> every 2 months (these periods of time are often known as a "sprint" in
> Agile[7]) but my hope is that this is a good place to start and we can
> improve over time.
> 
> If this is acceptable as a change we would like to adopt as a group, I
> am happy to pre-populate the kanban board with work items we had
> previously discussed that we wanted to accomplish as the original
> agenda to the (now defunct) DevConf Workshop. From there I would
> propose that the first meeting after DevConf  (2017-02-01) be used as
> the first grooming session and the following Thursday be the first
> VFAD (2017-02-02). From there we would set a schedule for every 2
> months to have a VFAD.

Sounds good. As a note we may still want to meet around devconf but
just not work on anything that we need the entire WG for.

> 
> If everyone is in agreement, I'll also get a section of the Wiki page
> (which we need to move out of the Cloud namespace) added to document
> this workflow for newcomers who would like to join the Atomic WG.
> 
> Thank you,
> -AdamM
> 
> 
> [0] - 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/WBTWBLOYWG66EDXJO2I4G3XY3X6EFAIF/
> [1] - https://devconf.cz/index.html
> [2] - 
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/36EBX5WS36OSO57GDWBJVIU6CXRXT237/
> [3] - https://fedoraproject.org/wiki/Fedora_Activity_Day_-_FAD
> [4] - https://en.wikipedia.org/wiki/Kanban
> [5] - 
> https://taiga.fedorainfracloud.org/project/maxamillion-fedora-atomic-wg/kanban
> [6] - https://pagure.io/atomic-wg/issues
> [7] - https://en.wikipedia.org/wiki/Agile_software_development
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
> 
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Fedora Atomic WG Workflow Proposal

2017-01-11 Thread Adam Miller 
Hello all,
Recently I attempted to start a mailing list thread that was the
product of a discussion on IRC about putting together an Atomic WG
workshop session[0] at DevConf[1].

This was then discussed during today's Atomic WG Meeting[2] where it
was decided that we should make this Workshop into a re-occurring
Virtual Fedora Activity Day(FAD[3]) instead taking place every 2
months.

I would like to propose the following:
Each Virtual FAD occurs on a Thursday, the day after a Fedora
Atomic WG meeting such that we can use the meeting the day before to
plan out the work to be done at the Virtual FAD. All work will be
tracked in a kanban[4] board, I've created one for this purpose in
Fedora's Taiga instance[5] (Note: I don't know why my FAS name is in
the URL, Taiga just does that).
In the kanban board, we would create cards in the NEW column
through out the two month cycle between Virtual FADs (these should
correlate to tickets in pagure[6]), then on the meeting before the FAD
we would "groom" the NEW cards that we want to accomplish on the
following day of the Virtual FAD, these "groomed" cards would be
placed into the READY column to signify they are ready to be worked
on. On the day of the VFAD, participants/contributors would then
assign a card to themselves that they want to work on, and move the
card into "IN PROGRESS" so that everyone knows what is being worked on
and nobody attempts to work on the same thing (unless that's
intentional, in that case both people's names should be listed in the
card description for reference). Once a task is done, then it should
be moved to the DONE column. This will give a good reflection of what
work was accomplished during the VFAD and we can (optionally) have a
retrospective meeting after the VFAD about what went well, what didn't
go well, and what we could do better next time. Also the day before
the next VFAD at the start of the "grooming" session (the weekly
Atomic WG meeting), all the previous VFAD's cards in the DONE column
from the previous VFAD should be moved to ARCHIVED for posterity.

Cards created should be units of work that can feasibly be
accomplished in a day or less worth of work.

I would like to ultimately propose we move to a more iterative cycle
where we use this workflow weekly instead of dedicating a single day
every 2 months (these periods of time are often known as a "sprint" in
Agile[7]) but my hope is that this is a good place to start and we can
improve over time.

If this is acceptable as a change we would like to adopt as a group, I
am happy to pre-populate the kanban board with work items we had
previously discussed that we wanted to accomplish as the original
agenda to the (now defunct) DevConf Workshop. From there I would
propose that the first meeting after DevConf  (2017-02-01) be used as
the first grooming session and the following Thursday be the first
VFAD (2017-02-02). From there we would set a schedule for every 2
months to have a VFAD.

If everyone is in agreement, I'll also get a section of the Wiki page
(which we need to move out of the Cloud namespace) added to document
this workflow for newcomers who would like to join the Atomic WG.

Thank you,
-AdamM


[0] - 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/WBTWBLOYWG66EDXJO2I4G3XY3X6EFAIF/
[1] - https://devconf.cz/index.html
[2] - 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/36EBX5WS36OSO57GDWBJVIU6CXRXT237/
[3] - https://fedoraproject.org/wiki/Fedora_Activity_Day_-_FAD
[4] - https://en.wikipedia.org/wiki/Kanban
[5] - 
https://taiga.fedorainfracloud.org/project/maxamillion-fedora-atomic-wg/kanban
[6] - https://pagure.io/atomic-wg/issues
[7] - https://en.wikipedia.org/wiki/Agile_software_development
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Cloud DevConf Workshop

2017-01-11 Thread Adam Miller 
On Tue, Jan 10, 2017 at 12:55 PM, Adam Miller
 wrote:
> On Tue, Jan 10, 2017 at 12:52 PM, Adam Miller
>  wrote:
>> Hello all,
>>During the last Fedora Cloud/Atomic WG meeting jberkus brought up
>> the idea of having a workshop at DevConf to tackle some Layered Image
>> items which we, at the time, seemed in agreement on. Josh and I were
>> talking on irc today and I wanted to make a proposal to the list and
>> find out what others thought.
>>
>> Meeting Time: 14:00 (localtime at DevConf)
>> Meeting Location: TBD
>> Virtual-Meeting Location: #fedora-cloud
>>
>> Work-Tracking (we should make cards for tasks):
>> 
>> https://taiga.fedorainfracloud.org/project/maxamillion-fedora-layered-images/kanban
>>
>> Work to accomplish:
>
> I accidentally hit "send" 
>
> Work to accomplish:
> - Discuss and improve current Dockerfile guidelines[0]
> - Move as many fedora-dockerfiles[1] from github into distgit as possible
> - $Your_Suggestion_Here
>
> I'm open to other suggestions on any of this, but wanted to get the
> discussion started because DevConf is just a couple weeks away.

This was discussed in today's Atomic WG Meeting and it was proposed
that we come up with a more generic re-occurring Virtual Fedora
Activity Day. I will start a new thread with that information as well
as documentation around the proposal.

-AdamM

>
> -AdamM
>
> [0] - https://fedoraproject.org/wiki/Container:Guidelines
> [1] - https://github.com/fedora-cloud/Fedora-Dockerfiles
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Cloud Meeting Minutes 2017-01-11

2017-01-11 Thread Jason Brooks 
summary: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atomic_wg.2017-01-11-17.00.html
full log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atomic_wg.2017-01-11-17.00.log.html

===
#fedora-meeting-1: fedora_atomic_wg
===


Meeting started by jbrooks at 17:00:12 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-01-11/fedora_atomic_wg.2017-01-11-17.00.log.html
.



Meeting summary
---
* roll call  (jbrooks, 17:00:19)

* action items from last meeting  (jbrooks, 17:02:09)
  * ACTION: dustymabe walters jberkus to discuss overlayfs partitioning
issue  (jbrooks, 17:09:17)
  * ACTION: jbrooks to update compose your own doc  (jbrooks, 17:14:49)
  * ACTION: jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches  (jbrooks, 17:15:12)
  * LINK: https://pagure.io/atomic-wg/issue/180   (jbrooks, 17:16:02)
  * ACTION: all comment on PRD draft to discuss next week  (jbrooks,
17:22:48)
  * ACTION: dustymabe to start ticket to discuss virtual fads  (jbrooks,
17:35:59)

* November 21 ISO is not bootable on UEFI  (jbrooks, 17:36:55)
  * LINK: https://pagure.io/atomic-wg/issue/185   (jbrooks, 17:37:03)
  * LINK: https://pagure.io/atomic-wg/issue/192   (dustymabe, 17:38:19)

* Ship fedora-motd in F24 atomic image  (jbrooks, 17:42:31)
  * LINK: https://pagure.io/atomic-wg/issue/160   (jbrooks, 17:42:36)

* Proposed website changes for Cloud Base → Atomic Host switch
  (jbrooks, 17:43:29)
  * LINK: https://pagure.io/atomic-wg/issue/158   (jbrooks, 17:43:34)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  (jbrooks, 17:45:36)
  * LINK: https://pagure.io/atomic-wg/issue/153   (jbrooks, 17:46:26)

* open floor  (jbrooks, 17:47:30)
  * LINK:

https://kojipkgs.fedoraproject.org/atomic/25/refs/heads/fedora-atomic/25/x86_64/testing/
(jbrooks, 17:58:11)

Meeting ended at 18:01:17 UTC.




Action Items

* dustymabe walters jberkus to discuss overlayfs partitioning issue
* jbrooks to update compose your own doc
* jbrooks dustymabe jberkus to collab on testing new
  docker-storage-setup patches
* all comment on PRD draft to discuss next week
* dustymabe to start ticket to discuss virtual fads




Action Items, by person
---
* dustymabe
  * dustymabe walters jberkus to discuss overlayfs partitioning issue
  * jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
  * dustymabe to start ticket to discuss virtual fads
* jberkus
  * dustymabe walters jberkus to discuss overlayfs partitioning issue
  * jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* jbrooks
  * jbrooks to update compose your own doc
  * jbrooks dustymabe jberkus to collab on testing new
docker-storage-setup patches
* **UNASSIGNED**
  * all comment on PRD draft to discuss next week




People Present (lines said)
---
* jbrooks (103)
* dustymabe (58)
* maxamillion (42)
* jberkus (36)
* kushal (26)
* zodbot (18)
* sayan (13)
* misc (7)
* roshi (7)
* trishnag (4)
* scollier (3)
* bowlofeggs (2)
* dgilmore (2)
* puiterwijk (1)
* coremodule (1)




Generated by `MeetBot`_ 0.1.4
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`

2017-01-11 Thread Dusty Mabe 

dustymabe added a new comment to an issue you are following:
``
cloud.fedoraproject.org is now live. There are a few remaining issues but I'm 
going to close this ticket and let the ticket in the fedora-websites repo 
monitor those problems: https://pagure.io/fedora-websites/issue/57 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/158
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #192 `atomic working group - periodic virtual FADs`

2017-01-11 Thread Dusty Mabe 

dustymabe reported a new issue against the project: `atomic-wg` that you are 
following:
``
It would be great if we can have some planned virtual meetings every few months 
to discuss the atomic working group and current issues that extend into 
discussions.

Should we meet every so often (not necessarily for an entire day) to sync up on 
issues and work through the backlog of items to clear out cruft and/or promote 
forgotten priorities?
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/192
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`

2017-01-11 Thread Adam Miller 

maxamillion added a new comment to an issue you are following:
``
Proposal for Workshop to work on this stuff at DevConf sent to the mailing list 
-> 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/WBTWBLOYWG66EDXJO2I4G3XY3X6EFAIF/
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/180
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #191 `Remove-Kube: create end-to-end test for Kubernetes cluster on Atomic`

2017-01-11 Thread Josh Berkus 

jberkus reported a new issue against the project: `atomic-wg` that you are 
following:
``
Once we have containerized kubernetes working, we need an automated or manual 
test which creates a 3+ node cluster, installs kubernetes, and launches one or 
more applications on it.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/191
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Proposal: require DESCRIPTION, USAGE label for images

2017-01-11 Thread Matthew Miller 
On Wed, Jan 11, 2017 at 08:12:53AM -0500, Subhendu Ghosh wrote:
> I disagree that the usage should be limited to "used by another container".

To be clear, I'm only suggesting that when it is meant to be used in
that way, and as more helpful than N/A. This line is meant to be a
brief statement

> Even though that is the intended use, the usage description should be
> uniform and state what capability or function is provided.
> Actual usage pattern for code is always more interesting than intended use.

... and doesn't the "description" cover that detail?

-- 
Matthew Miller

Fedora Project Leader
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Proposal: require DESCRIPTION, USAGE label for images

2017-01-11 Thread Subhendu Ghosh 
On Jan 10, 2017 15:17, "Adam Miller"  wrote:

On Tue, Jan 10, 2017 at 1:47 PM, Josh Berkus  wrote:
> On 01/10/2017 10:52 AM, Matthew Miller wrote:
>> On Tue, Jan 10, 2017 at 10:44:03AM -0800, Josh Berkus wrote:
 On Tue, Jan 10, 2017 at 10:33:05AM -0800, Josh Berkus wrote:
>>   USAGE: single command line giving usage example
>>  for invoking the container; will be "N/A" for
>>  some containers.

 Why N/A? What circumstances would this be?
>>> CNI Networking container for Kubernetes, for example.  A bunch of
>>> "infra" containers only get invoked by other containers and/or the
>>> orchestration system.
>>
>> Could we develop standard wording for that? Like
>>
>>   USAGE: Invoked by $OTHERCONTAINER
>>
>> or
>>
>>   USAGE: Invoked by Kubernetes when $WHATEVERTRIGGERS
>>
>> or are there too many possibilities?
>
> I don't think there are.  I'd suggest:
>
> ---
>
> USAGE: Invoked by $SOMEPROCESS.  Not for direct use.
>
> "$SOMEPROCESS" should be the name of the infrastructure tool, container,
> or other utility which consumes this container.
>
> ---
>

+1 - I like that idea, makes it very clear to the user.

-AdamM


I disagree that the usage should be limited to "used by another container".
Even though that is the intended use, the usage description should be
uniform and state what capability or function is provided.

Actual usage pattern for code is always more interesting than intended use.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org