Re: [cloud] #169: Spec for IRC bot to notify about blockers

[Fedora Cloud Trac Tickets]

#169: Spec for IRC bot to notify about blockers
-+-
 Reporter:  jberkus  |   Owner:
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by mattdm):

 That said, "image does not exist at all because it did not build", or
 "image does not boot" are almost certainly going to be blockers (for any
 image which is itself blocking).

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #169: Spec for IRC bot to notify about blockers

[Fedora Cloud Trac Tickets]

#169: Spec for IRC bot to notify about blockers
-+-
 Reporter:  jberkus  |   Owner:
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by adamwill):

 Well, there's no straightforward way to identify 'cloud release blockers';
 we do not segment them by product in any way.

 Blocker bugs are handled with tracker bugs in Bugzilla. Three trackers are
 filed for each release: one for Alpha, one for Beta, one for Final. They
 are given standard aliases: F(rel)AlphaBlocker , F(rel)BetaBlocker,
 F(rel)FinalBlocker , where (rel) is the release number. So currently we
 have F25AlphaBlocker, F25BetaBlocker, and F25FinalBlocker.

 Any bug blocking one of those trackers is either a proposed or an accepted
 blocker. If it has 'AcceptedBlocker', 'Accepted0Day' or
 'AcceptedPreviousRelease' in its whiteboard field, it's an accepted
 blocker. If it does not, it's a proposed blocker.

 There's a webapp called 'blockerbugs' -
 https://qa.fedoraproject.org/blockerbugs - which we (QA) use for
 convenience in dealing with blockers. It handles a lot of the work of
 identifying blockers for upcoming cycles. Off the top of my head I don't
 know if it has an API, and I also don't know if anything sends out
 fedmsg's for proposed / accepted blockers.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

[cloud] #170: Finish new Fedora Cloud PRD

[Fedora Cloud Trac Tickets]

#170: Finish new Fedora Cloud PRD
-+-
 Reporter:  jberkus  |  Owner:
 Type:  task | Status:  new
 Priority:  normal   |  Milestone:  Future
Component:  ---  |   Keywords:  meeting
-+-
 At Flock, we started but did not finish a revised Cloud PRD.

 This needs to be finished.  Not sure who to assign this to.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

IRC Bot Spec ticket

[Josh Berkus]

Per today's meeting, please refine the spec for this:

https://fedorahosted.org/cloud/ticket/169

-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

[cloud] #169: Spec for IRC bot to notify about blockers

[Fedora Cloud Trac Tickets]

#169: Spec for IRC bot to notify about blockers
-+-
 Reporter:  jberkus  |  Owner:
 Type:  task | Status:  new
 Priority:  normal   |  Milestone:  Future
Component:  ---  |   Keywords:  meeting
-+-
 One of the issues we have with release blockers is slow response by the
 fedora-cloud WG.  As that group is very IRC-centric, we'd like to have
 some form of notification via IRC when a release blocker is encountered.

 Here's a draft spec, please revise:

 1. whenever a release blocker issue is filed or updated, a message will be
 sent via bot to the #fedora-cloud channel;

 2. the /topic of #fedora-cloud will be updated with a list of release-
 blocker issues once a day.

 Questions: how do we identify release-blocker issues?

 This relates to issue https://fedorahosted.org/cloud/ticket/167

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #164: Fedora Atomic Host 24 Not Available

[Fedora Cloud Trac Tickets]

#164: Fedora Atomic Host 24 Not Available
---+-
 Reporter:  jberkus|   Owner:
 Type:  task   |  Status:  closed
 Priority:  blocker|   Milestone:  Future
Component:  ---|  Resolution:  fixed
 Keywords:  downloads  |
---+-
Changes (by jberkus):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 This has been resolved.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Cloud Meeting Minutes 2016-08-31

[Trishna Guha]

summary: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-31/fedora_cloud_wg.2016-08-31-16.59.html
full log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-31/fedora_cloud_wg.2016-08-31-16.59.log.html

==
#fedora-meeting-1: fedora_cloud_wg
==


Meeting started by trishnag at 16:59:36 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-31/fedora_cloud_wg.2016-08-31-16.59.log.html
.



Meeting summary
---
* Roll Call  (trishnag, 16:59:41)

* rtnpro will add test workflow (and test cases) for testing fedora-motd
  on F24 atomic image  (trishnag, 17:01:31)

* Action items from last meeting  (trishnag, 17:02:45)

* rtnpro will add test workflow (and test cases) for testing fedora-motd
  on F24 atomic image  (trishnag, 17:03:01)
  * ACTION: rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image  (trishnag, 17:05:38)

* gholms to test updated cloud-init on f24 for f25  (trishnag, 17:06:25)
  * cloud-init 0.7.7 now in rawhide, needs testing on more clouds than I
have access to  (gholms, 17:06:53)
  * It's also in f25 updates-testing  (gholms, 17:07:18)
  * ACTION: kushal to test new cloud-init on openstack  (gholms,
17:07:58)

* vvaldez to talk with misc, scollier, jberkus about how he can help
  with FOSP (#153)  (trishnag, 17:10:57)
  * LINK: https://fedorahosted.org/cloud/ticket/153   (trishnag,
17:12:49)

* #125 Fedora-Dockerfiles examples for Kubernetes  (trishnag, 17:14:53)
  * LINK: https://fedorahosted.org/cloud/ticket/125   (trishnag,
17:15:03)

* #136 vagrant boxes fixups  (trishnag, 17:17:06)
  * LINK: https://fedorahosted.org/cloud/ticket/136   (trishnag,
17:17:10)

* #147 Don't overwrite download location for 2 week atomic images
  https://fedorahosted.org/cloud/ticket/147  (trishnag, 17:19:28)
  * LINK:

https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/RIVZOYPJSMTMQXHKXIWNTSWQ2CQAPNXC/
(kushal, 17:22:27)

* #154 make Fedora Atomic download page clearer
  https://fedorahosted.org/cloud/ticket/154  (trishnag, 17:23:57)

* #155 Decide on post-GA update cadence for various deliverables
  https://fedorahosted.org/cloud/ticket/155  (trishnag, 17:25:20)

* #156 Need complete Kickstart docs for Atomic Host
  https://fedorahosted.org/cloud/ticket/156  (trishnag, 17:28:30)

* #160 Ship fedora-motd in F24 atomic image
  https://fedorahosted.org/cloud/ticket/160  (trishnag, 17:30:39)

* #167 Decide a process about failed tests for Autocloud
  https://fedorahosted.org/cloud/ticket/167  (trishnag, 17:31:36)

* #168 Put OpenShift Origin in Container with Fedora Base
  https://fedorahosted.org/cloud/ticket/168  (trishnag, 17:36:44)
  * ACTION: jberkus will draft spec for IRC bot for blocker bugs
(kushal, 17:46:22)

* Open Floor  (trishnag, 17:47:53)

Meeting ended at 17:58:07 UTC.




Action Items

* rtnpro will add test workflow (and test cases) for testing fedora-motd
  on F24 atomic image
* kushal to test new cloud-init on openstack
* jberkus will draft spec for IRC bot for blocker bugs




Action Items, by person
---
* jberkus
  * jberkus will draft spec for IRC bot for blocker bugs
* kushal
  * kushal to test new cloud-init on openstack
* rtnpro
  * rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* trishnag (78)
* kushal (43)
* jberkus (29)
* zodbot (21)
* maxamillion (20)
* scollier (11)
* sayan (11)
* walters (11)
* gholms (10)
* rtnpro (8)
* misc (7)
* jbrooks (6)
* vvaldez (4)
* bowlofeggs (1)
* nzwulfin (1)
* nirik (1)
* dustymabe (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #167: Decide a process about failed tests for Autocloud

[Fedora Cloud Trac Tickets]

#167: Decide a process about failed tests for Autocloud
-+-
 Reporter:  kushal   |   Owner:
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by mattdm):

 Replying to [comment:3 jberkus]:
 > So one of the major problems here is that when a blocker is raised,
 nobody responds to it until the weekly meeting.  Adam already has plans to
 send a notification to the fedora-cloud mailing list.  I think it would
 also be very helpful to post a notification on IRC somehow, as the fedora-
 cloud team is very IRC-centric.  How hard is it to pull the list of
 blocker bugs via an API?

 AutoCloud (via Bugyou) puts issues at https://pagure.io/atomic-
 images/issues. And nirik tells me it is possible to have a bot direct
 those to a channel.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #167: Decide a process about failed tests for Autocloud

[Fedora Cloud Trac Tickets]

#167: Decide a process about failed tests for Autocloud
-+-
 Reporter:  kushal   |   Owner:
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by jberkus):

 So one of the major problems here is that when a blocker is raised, nobody
 responds to it until the weekly meeting.  Adam already has plans to send a
 notification to the fedora-cloud mailing list.  I think it would also be
 very helpful to post a notification on IRC somehow, as the fedora-cloud
 team is very IRC-centric.  How hard is it to pull the list of blocker bugs
 via an API?

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #147: Don't overwrite download location for 2 week atomic images

[Fedora Cloud Trac Tickets]

#147: Don't overwrite download location for 2 week atomic images
---+-
 Reporter:  dustymabe  |   Owner:
 Type:  task   |  Status:  new
 Priority:  normal |   Milestone:  Future
Component:  ---|  Resolution:
 Keywords:  meeting|
---+-

Comment (by maxamillion):

 Taking a two-pronged approach, one is a change to the releng script for
 keeping N and N-1, then going to submit a change to the websites code to
 handle the "latest" target. Mailing list threads below.

 Cloud mailing list thread
 
[https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/RIVZOYPJSMTMQXHKXIWNTSWQ2CQAPNXC/
 here].

 Websites mailing list thread
 
[https://lists.fedoraproject.org/archives/list/websi...@lists.fedoraproject.org/thread/7L4QHLHWN4ECRMXCEMKI4JIZBSLSN7QN/
 here].

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #125: Fedora-Dockerfiles examples for Kubernetes

[Fedora Cloud Trac Tickets]

#125: Fedora-Dockerfiles examples for Kubernetes
--+---
 Reporter:  scollier  |   Owner:  jberkus
 Type:  task  |  Status:  assigned
 Priority:  normal|   Milestone:  Future
Component:  ---   |  Resolution:
 Keywords:|
--+---
Changes (by jberkus):

 * keywords:  meeting =>


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #156: Need complete Kickstart docs for Atomic Host

[Fedora Cloud Trac Tickets]

#156: Need complete Kickstart docs for Atomic Host
---+---
 Reporter:  jberkus|   Owner:  jberkus
 Type:  task   |  Status:  assigned
 Priority:  normal |   Milestone:  Future
Component:  Docker Host Image  |  Resolution:
 Keywords:  Meeting|
---+---

Comment (by jberkus):

 Docs are written, currently in review.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #167: Decide a process about failed tests for Autocloud

[Fedora Cloud Trac Tickets]

#167: Decide a process about failed tests for Autocloud
-+-
 Reporter:  kushal   |   Owner:
 Type:  task |  Status:  new
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+-

Comment (by kushal):

 Replying to [comment:1 dustymabe]:
 > I think for this ticket it would be nice to stop the release for a
 failing test but we must make sure we have resources to fix issues when
 they arise otherwise we'll just block release forever.

 +1 to the above. My only concern is to get things fixed in time, say
 within a week of the first reporting the issue (for our 2 week release
 cycle).

 > Right now we don't have enough resources to guarantee an issue will gain
 enough attention to get fixed in a timely manner. Depending on the bug we
 should be able to decide if it is bad enough to block the release or not?

 This also sounds good, should we discuss this over the issue bugyou
 creates for the failed test runs? Or over mailing list etc.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org