Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by scollier):

 share your ansible hosts file please?

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by misc):

 Flannel is running and I do not remember activating openshift-sdn. I found
 why flannel was failing (wrong cut and paste), but I can reprovision with
 openshift-sdn later. I will likely do the deployment again just to verify
 I didn't do some hotfixes that I forgot, or that it did work by luck after
 enough bruteforce fixes.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by scollier):

 Replying to [comment:16 misc]:

 Finished with openshift-sdn enabked or disabled?

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by misc):

 So good new. The deploy did finished fine. I stumbled on 2 issues, 1 with
 me doing wrong cut and paste (resulting in utf8 fun), and one doing wrong
 cut and paste (ie, taking config that didn't correspond to the VM).

 So now, we just need to figure the last bit, ie having the bastion to do
 proper proxying to the cluster. (and me to push last commit, and basic
 doc)

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #104: Atomic PXE tree does not work for interactive installs

[Fedora Cloud Trac Tickets]

#104: Atomic PXE tree does not work for interactive installs
-+-
 Reporter:  walters  |   Owner:
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #103: bugzilla components for base image and Atomic Host

[Fedora Cloud Trac Tickets]

#103: bugzilla components for base image and Atomic Host
-+-
 Reporter:  walters  |   Owner:
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #89: Add Dockerfile Section to Downloads Page?

[Fedora Cloud Trac Tickets]

#89: Add Dockerfile Section to Downloads Page?
+-
 Reporter:  jzb |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #83: participation in OpenShift Commons

[Fedora Cloud Trac Tickets]

#83: participation in OpenShift Commons
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #78: Draft charter change, new slate (Cloud WG members vote needed!)

[Fedora Cloud Trac Tickets]

#78: Draft charter change, new slate (Cloud WG members vote needed!)
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #76: Explore possibility of shipping preconfigured KVM cloud image on live DVD

[Fedora Cloud Trac Tickets]

#76: Explore possibility of shipping preconfigured KVM cloud image on live DVD
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #60: Enable serial console for bootloader

[Fedora Cloud Trac Tickets]

#60: Enable serial console for bootloader
--+-
 Reporter:  fabiand   |   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #71: libmicrohttpd is back as a systemd dependency

[Fedora Cloud Trac Tickets]

#71: libmicrohttpd is back as a systemd dependency
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #53: anaconda doesn't allow installation of current fedora-cloud-base.ks

[Fedora Cloud Trac Tickets]

#53: anaconda doesn't allow installation of current fedora-cloud-base.ks
-+-
 Reporter:  walters  |   Owner:
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #44: hey we should have a vagrant base box

[Fedora Cloud Trac Tickets]

#44: hey we should have a vagrant base box
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #23: File F22 change: Re-factor cloud-init

[Fedora Cloud Trac Tickets]

#23: File F22 change: Re-factor cloud-init
--+--
 Reporter:  mattdm|   Owner:  hguemar
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+--
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #112: Ultimately reducing the tools installed in the Fedora docker image, but first getting messaging and expectations right

[Fedora Cloud Trac Tickets]

#112: Ultimately reducing the tools installed in the Fedora docker image, but
first getting messaging and expectations right
---+-
 Reporter:  bex|   Owner:
 Type:  enhancement|  Status:  closed
 Priority:  normal |   Milestone:  Future
Component:  Docker Base Container  |  Resolution:  fixed
 Keywords: |
---+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #145: Include bind-utils or similar in base image

[Fedora Cloud Trac Tickets]

#145: Include bind-utils or similar in base image
---+-
 Reporter:  jfindley   |   Owner:
 Type:  enhancement|  Status:  closed
 Priority:  normal |   Milestone:  Future
Component:  Docker Host Image  |  Resolution:  fixed
 Keywords: |
---+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #101: Proposed for Fedora 23 - Support for Windows 10 Client Hyper-V

[Fedora Cloud Trac Tickets]

#101: Proposed for Fedora 23 - Support for Windows 10 Client Hyper-V
+-
 Reporter:  znmeb   |   Owner:
 Type:  enhancement |  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  Docker (Other)  |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #12: send list of packages on cloud images to spot for change from %doc to %license

[Fedora Cloud Trac Tickets]

#12: send list of packages on cloud images to spot for change from %doc to
%license
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  new
 Priority:  normal|   Milestone:  Fedora 21 (Final)
Component:  Cloud Base Image  |  Resolution:
 Keywords:  easyfix   |
--+

Comment (by kushal):

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #42: policies for batched updates

[Fedora Cloud Trac Tickets]

#42: policies for batched updates
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Final)
Component:  Software Updates  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #129: RabbitMQ fails to build

[Fedora Cloud Trac Tickets]

#129: RabbitMQ fails to build
+-
 Reporter:  coolsvap|   Owner:
 Type:  defect  |  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  Docker (Other)  |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size

[Fedora Cloud Trac Tickets]

#120: Fedora 22 Cloud vagrant image does not extend filesystem to disk size
--+-
 Reporter:  pwnall|   Owner:
 Type:  defect|  Status:  closed
 Priority:  normal|   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #34: External need: batched updates

[Fedora Cloud Trac Tickets]

#34: External need: batched updates
--+-
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Flock 2014
Component:  Software Updates  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #110: Make NFS file sync work with Vagrant seamlessly

[Fedora Cloud Trac Tickets]

#110: Make NFS file sync work with Vagrant seamlessly
--+
 Reporter:  rtnpro|   Owner:  rtnpro
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 22
Component:  Software Updates  |  Resolution:  fixed
 Keywords:  vagrant, nfs  |
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #25: File F22 change: OpenShift Out-of-the-Box Image

[Fedora Cloud Trac Tickets]

#25: File F22 change: OpenShift Out-of-the-Box Image
+
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Fedora 22
Component:  OpenShift Origin Image  |  Resolution:  fixed
 Keywords:  |
+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #38: Automatic Smoketests on Image Build

[Fedora Cloud Trac Tickets]

#38: Automatic Smoketests on Image Build
--+
 Reporter:  mattdm|   Owner:  agrimm
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 22
Component:  Testing & QA  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #81: Create cloud training materials for ambassadors

[Fedora Cloud Trac Tickets]

#81: Create cloud training materials for ambassadors
---+
 Reporter:  mattdm |   Owner:
 Type:  task   |  Status:  closed
 Priority:  normal |   Milestone:  Fedora 22
Component:  Collaboration & Communication  |  Resolution:  fixed
 Keywords: |
---+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #73: test cases for cloud-init

[Fedora Cloud Trac Tickets]

#73: test cases for cloud-init
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Final)
Component:  Testing & QA  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #57: get official images uploaded into Rackspace

[Fedora Cloud Trac Tickets]

#57: get official images uploaded into Rackspace
-+-
 Reporter:  mattdm   |   Owner:
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Fedora 21
Component:  Infrastructure & Release |  (Final)
  Engineering|  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #28: discuss modularized SELinux policy packaging

[Fedora Cloud Trac Tickets]

#28: discuss modularized SELinux policy packaging
--+
 Reporter:  mattdm|   Owner:
 Type:  enhancement   |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 22
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #63: list fedora accounts needed for releng to make official cloud images content

[Fedora Cloud Trac Tickets]

#63: list fedora accounts needed for releng to make official cloud images
content
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Fedora 21 (Branch)
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #37: External Need: software collections

[Fedora Cloud Trac Tickets]

#37: External Need: software collections
-+-
 Reporter:  mattdm   |   Owner:  mattdm
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Fedora 21 (Feature
Component:  Collaboration &  |  Deadline)
  Communication  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #39: External Need: Scratch Builds on Change

[Fedora Cloud Trac Tickets]

#39: External Need: Scratch Builds on Change
+-
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Fedora 21 (Branch)
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #59: Process for determining when and why Docker trusted images need to be rebuilt

[Fedora Cloud Trac Tickets]

#59: Process for determining when and why Docker trusted images need to be
rebuilt
+---
 Reporter:  scollier|   Owner:  jzb
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Fedora 21 (Beta)
Component:  Docker (Other)  |  Resolution:  fixed
 Keywords:  |
+---
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #72: go over f21 changes, make sure they're all in good shape

[Fedora Cloud Trac Tickets]

#72: go over f21 changes, make sure they're all in good shape
+
 Reporter:  mattdm  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Fedora 21 (Alpha)
Component:  --- |  Resolution:  fixed
 Keywords:  |
+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #62: notification of pending security updates in motd

[Fedora Cloud Trac Tickets]

#62: notification of pending security updates in motd
--+
 Reporter:  mattdm|   Owner:  rtnpro
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #55: define shell command API available in Fedora Cloud Base Image

[Fedora Cloud Trac Tickets]

#55: define shell command API available in Fedora Cloud Base Image
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #54: define shell command API available in Fedora Atomic

[Fedora Cloud Trac Tickets]

#54: define shell command API available in Fedora Atomic
---+
 Reporter:  mattdm |   Owner:
 Type:  task   |  Status:  closed
 Priority:  normal |   Milestone:  Fedora 21 (Alpha)
Component:  Docker Host Image  |  Resolution:  fixed
 Keywords: |
---+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #48: remove rsyslog from default image, configure journald options appropriately

[Fedora Cloud Trac Tickets]

#48: remove rsyslog from default image, configure journald options appropriately
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #15: migrate to GPT instead of old-style partitions

[Fedora Cloud Trac Tickets]

#15: migrate to GPT instead of old-style partitions
--+
 Reporter:  mattdm|   Owner:  janeznemanic
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #35: External need: Automatic Image Upload

[Fedora Cloud Trac Tickets]

#35: External need: Automatic Image Upload
-+-
 Reporter:  mattdm   |   Owner:  oddshocks
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Fedora 21
Component:  Infrastructure & Release |  (Alpha)
  Engineering|  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #14: Investigate systemd-networkd

[Fedora Cloud Trac Tickets]

#14: Investigate systemd-networkd
--+
 Reporter:  mattdm|   Owner:  kushal
 Type:  task  |  Status:  closed
 Priority:  normal|   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #56: tracking ticket for conversations around shipping ostree... trees.

[Fedora Cloud Trac Tickets]

#56: tracking ticket for conversations around shipping ostree... trees.
---+---
 Reporter:  mattdm |   Owner:
 Type:  task   |  Status:  closed
 Priority:  blocker|   Milestone:  Fedora 21
Component:  Collaboration & Communication  |  (Branch)
 Keywords: |  Resolution:  fixed
---+---
Changes (by kushal):

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


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #157: Review of release blocking deliverables for F24

[Fedora Cloud Trac Tickets]

#157: Review of release blocking deliverables for F24
+-
 Reporter:  jkurik  |   Owner:
 Type:  task|  Status:  closed
 Priority:  major   |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #134: Clarify the status and process of https://github.com/fedora-cloud/docker-brew-fedora

[Fedora Cloud Trac Tickets]

#134: Clarify the status and process of https://github.com/fedora-cloud/docker-
brew-fedora
-+
 Reporter:  adelton  |   Owner:
 Type:  task |  Status:  closed
 Priority:  major|   Milestone:  Fedora 22
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+
Changes (by kushal):

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


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #130: Fedora Atomic Host installable tree needed

[Fedora Cloud Trac Tickets]

#130: Fedora Atomic Host installable tree needed
-+-
 Reporter:  adelton  |   Owner:
 Type:  task |  Status:  closed
 Priority:  major|   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #142: disable deltarpms in cloud images

[Fedora Cloud Trac Tickets]

#142: disable deltarpms in cloud images
--+-
 Reporter:  praiskup  |   Owner:
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #111: Some F22 AMIs marked private

[Fedora Cloud Trac Tickets]

#111: Some F22 AMIs marked private
--+-
 Reporter:  pfrields  |   Owner:
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Future
Component:  Infrastructure & Release Engineering  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #5: tracker for GCE work

[Fedora Cloud Trac Tickets]

#5: tracker for GCE work
--+-
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #134: Clarify the status and process of https://github.com/fedora-cloud/docker-brew-fedora

[Fedora Cloud Trac Tickets]

#134: Clarify the status and process of https://github.com/fedora-cloud/docker-
brew-fedora
-+
 Reporter:  adelton  |   Owner:
 Type:  task |  Status:  new
 Priority:  major|   Milestone:  Fedora 22
Component:  ---  |  Resolution:
 Keywords:   |
-+

Comment (by kushal):

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #13: Port Cloud Image Kickstart to anaconda/imagefactory

[Fedora Cloud Trac Tickets]

#13: Port Cloud Image Kickstart to anaconda/imagefactory
--+-
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Fedora 21 (Branch)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #69: Fedora Cloud image boot: Y U SO SLOW?

[Fedora Cloud Trac Tickets]

#69: Fedora Cloud image boot: Y U SO SLOW?
--+
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #40: rel-eng/image upload changes for f21

[Fedora Cloud Trac Tickets]

#40: rel-eng/image upload changes for f21
-+-
 Reporter:  mattdm   |   Owner:
 Type:  task |  Status:  closed
 Priority:  major|   Milestone:  Fedora 21
Component:  Infrastructure & Release |  (Alpha)
  Engineering|  Resolution:  fixed
 Keywords:   |
-+-
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #4: new release criteria for post-f20 cloud image

[Fedora Cloud Trac Tickets]

#4: new release criteria for post-f20 cloud image
--+
 Reporter:  mattdm|   Owner:  roshi
 Type:  task  |  Status:  closed
 Priority:  major |   Milestone:  Fedora 21 (Alpha)
Component:  Cloud Base Image  |  Resolution:  fixed
 Keywords:|
--+
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #56: tracking ticket for conversations around shipping ostree... trees.

[Fedora Cloud Trac Tickets]

#56: tracking ticket for conversations around shipping ostree... trees.
---+---
 Reporter:  mattdm |   Owner:
 Type:  task   |  Status:  new
 Priority:  blocker|   Milestone:  Fedora 21
Component:  Collaboration & Communication  |  (Branch)
 Keywords: |  Resolution:
---+---

Comment (by kushal):

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #70: cloud-init output not going to the openstack log

[Fedora Cloud Trac Tickets]

#70: cloud-init output not going to the openstack log
-+---
 Reporter:  mattdm   |   Owner:
 Type:  task |  Status:  closed
 Priority:  blocker  |   Milestone:  Fedora 21 (Beta)
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+---
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #43: procedures and process for producing and releasing updated images

[Fedora Cloud Trac Tickets]

#43: procedures and process for producing and releasing updated images
--+---
 Reporter:  mattdm|   Owner:
 Type:  task  |  Status:  closed
 Priority:  blocker   |   Milestone:  Fedora 21 (Beta)
Component:  Software Updates  |  Resolution:  fixed
 Keywords:|
--+---
Changes (by kushal):

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


Comment:

 Closing this ticket as part of trac clean up process. If you want to
 reopen, please reopen it after we move to pagure.io as atomic-wg.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #165: Reimbursement for the Cloud FAD

[Fedora Cloud Trac Tickets]

#165: Reimbursement for the Cloud FAD
+-
 Reporter:  kushal  |   Owner:  jzb@…
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by jberkus):

 The last time I reimbursed someone in India I had to use Western Union.

 Surely Red Hat must have some way of doing this?

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #165: Reimbursement for the Cloud FAD

[Fedora Cloud Trac Tickets]

#165: Reimbursement for the Cloud FAD
+-
 Reporter:  kushal  |   Owner:  jzb@…
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by bex):

 itamarjp, while I appreciate your suggestion, the last time I checked
 bitcoin suffered from three challenges:

 1 - It is difficult to purchase at low fee with a credit card
 2 - It is difficult for most people to convert it back to fiat currency or
 to use it
 3 - It fails several US accounting tests making it almost impossible to
 use for these types of expenses.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #165: Reimbursement for the Cloud FAD

[Fedora Cloud Trac Tickets]

#165: Reimbursement for the Cloud FAD
+-
 Reporter:  kushal  |   Owner:  jzb@…
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by itamarjp):

 just a suggestion, Bitcoin if We are true geeks.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #165: Reimbursement for the Cloud FAD

[Fedora Cloud Trac Tickets]

#165: Reimbursement for the Cloud FAD
+-
 Reporter:  kushal  |   Owner:  jzb@…
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by bex):

 Kushal, it appears that Paypal has shutdown payments for India from non-
 business accounts.  Can you send me some options to consider.  Is there an
 India specific payment gateway we could consider?

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #160: Ship fedora-motd in F24 atomic image

[Fedora Cloud Trac Tickets]

#160: Ship fedora-motd in F24 atomic image
--+---
 Reporter:  rtnpro|   Owner:  kushal
 Type:  task  |  Status:  assigned
 Priority:  normal|   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:
 Keywords:  meeting   |
--+---

Comment (by rtnpro):

 We have added tests to run on tunir for fedora-motd at
 https://github.com/rtnpro/motdgen/tree/master/tunirtests. The tests do the
 following:

 - install fedora-motd rpm on atomic host in hotfix mode
 - reboot atomic host
 - assert if motd message is printed on SSH login

 Here's some instructions on how to run the tests:
 https://github.com/rtnpro/motdgen#tests

 Next steps?

 - include fedora-motd in fedora atomic host builds and enable
 motdgen.service
 - include fedora-motd in fedora cloud images as well

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #155: Decide on post-GA update cadence for various deliverables

[Fedora Cloud Trac Tickets]

#155: Decide on post-GA update cadence for various deliverables
-+--
 Reporter:  maxamillion  |   Owner:  jasonbrooks
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:  meeting  |
-+--
Changes (by sayanchowdhury):

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


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #144: f23 atomic iso configures docker loopback storage

[Fedora Cloud Trac Tickets]

#144: f23 atomic iso configures docker loopback storage
-+-
 Reporter:  jasonbrooks  |   Owner:
 Type:  defect   |  Status:  closed
 Priority:  major|   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:   |
-+-
Changes (by jasonbrooks):

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


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by scollier):

 moved working session out a couple of weeks due to the seboolean issue.
 That gives time for the patch to get rolled in and for misc to test those
 packages.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@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:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:  meeting  |
-+-
Changes (by kushal):

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


Comment:

 It was decided that we will be marking any such bug as non-blocker after
 discussing it over mailing list, or in a ticket. As an example, we have
 marked the journal tests as non-blocking for now. We will bring it back
 into blocking after it is fixed.

 I am also closing this ticket with this. We can reopen it as required.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #136: vagrant boxes fixups

[Fedora Cloud Trac Tickets]

#136: vagrant boxes fixups
---+---
 Reporter:  dustymabe  |   Owner:  imcleod
 Type:  task   |  Status:  assigned
 Priority:  normal |   Milestone:  Future
Component:  ---|  Resolution:
 Keywords:  meeting|
---+---

Comment (by imcleod):

 Folks,

 I originally thought I had code already in Factory to enable this.  I do
 not.  The code I was thinking of is for VMWare OVAs, not the VirtualBox
 OVAs that are used as the basis of the Vagrant box.

 I'll need some more time to sort this out.  Apologies.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #168: Put OpenShift Origin in Container with Fedora Base

[Fedora Cloud Trac Tickets]

#168: Put OpenShift Origin in Container with Fedora Base
+--
 Reporter:  scollier|   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  OpenShift Origin Image  |  Resolution:  invalid
 Keywords:  meeting |
+--
Changes (by scollier):

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


-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #168: Put OpenShift Origin in Container with Fedora Base

[Fedora Cloud Trac Tickets]

#168: Put OpenShift Origin in Container with Fedora Base
+-
 Reporter:  scollier|   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  OpenShift Origin Image  |  Resolution:
 Keywords:  meeting |
+-

Comment (by scollier):

 CLosing this in favor of the work Adam is doing on the FAO project.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by scollier):

 moved works session to Oct 3rd.

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-

Comment (by kushal):

 Worked as a non gating test.

 https://apps.fedoraproject.org/autocloud/jobs/634/output#235

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  closed
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:  fixed
 Keywords:  |
+-
Changes (by kushal):

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


Comment:

 Done in commit
 
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=5e5354b86b7be04094ffcd9dfe5b2c98b03d31ea

-- 
Ticket URL: 
cloud 
Fedora Cloud Working Group Ticketing System
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [cloud] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by trishnag):

 Replying to [comment:12 jberkus]:
 > Yeah, so then the recommendation would be to unblock until this bug is
 fixed, but then make it a gating issue thereafter.
 +1 to this.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by sayanchowdhury):

 Replying to [comment:12 jberkus]:
 > Yeah, so then the recommendation would be to unblock until this bug is
 fixed, but then make it a gating issue thereafter.

 Agree. I wonder if we can have a concrete release criteria as emphasis on
 a issue can change quickly.

 I don't know if my vote counts but I am +1 (Aye) to mark these as non-
 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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by jberkus):

 Yeah, so then the recommendation would be to unblock until this bug is
 fixed, but then make it a gating issue thereafter.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by mattdm):

 Replying to [comment:10 jberkus]:
 > However, surely the Fedora project has some standards around what's
 considered a gating bug?

 We do for the traditional 6-month releases:

 https://fedoraproject.org/wiki/Fedora_Release_Criteria

 For example, functional system logging is considered to block an alpha
 release:

 https://fedoraproject.org/wiki/Fedora_25_Alpha_Release_Criteria#System_logging

 The Atomic release doesn't have to follow the exact same rules, of course,
 but I'd highly suggest keeping in the ballpark and coordinating with QA
 for expertise.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by jberkus):

 My inclination is to say "non-blocking" because I do a lot of testing on
 Atomic Host and never noticed the bug, personally.  I generally figure
 that gating bugs should be ones which either (a) carry significant
 security risk or (b) make the system unusable, or significantly less
 usable, than the prior release.

 However, surely the Fedora project has some standards around what's
 considered a gating bug?

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by mattdm):

 Replying to [comment:7 jberkus]:
 > If we had a version on getfedora which passed the tests, and it was only
 the pending version which was failing, I'd keep them blocking.  But I see
 no point in continuing to block on tests which the "stable" version also
 doesn't pass.  Clearly we've decided it's acceptable to ship a version of
 Fedora Atomic which fails the log tests.

 This implies a second decision to be made: once there ''is'' a working
 version, should the non-blocking test become a blocking one?

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by trishnag):

 Replying to [comment:6 dustymabe]:
 > Replying to [comment:5 trishnag]:
 > > Replying to [comment:3 dustymabe]:
 > > > Replying to [comment:2 trishnag]:
 > > > > What is the point of having the testcase if we want to release
 images even though they have bugs?
 > > > >
 > > >
 > > > So that we can find and fix bugs faster when they do happen. If we
 choose to release with the bug anyway then we know it exists and can guide
 users accordingly until it is fixed.
 > > >
 > > Okay, if we choose to release with the bug anyway does it mean that
 the bug is not going to affect users much?
 >
 > Yeah. The idea is that we put items to a vote and determine the
 severity. This bug is not that severe as it is just a logging issue. While
 important, it shouldn't block release in this case IMHO. My opinion could
 change in the future, but since this has been going out in our images for
 some time now we aren't making the currently released image any worse by
 releasing the next image.
 Got you. Thanks dustymabe.
 >
 >
 > > > > This testcase is also **not a non-gating test** AFAIK.
 https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98
 > > >
 > > > Does that link prove it is a non-gating test? Where is the list of
 gating vs non-gating?
 > > We put non-gating tests here
 https://github.com/kushaldas/tunirtests/blob/master/nongatingtests.py
 > > Rest of the files have gating tests. Journal logging test is a gating
 test. So we have it in a separate file.
 >
 >
 > Thanks

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by jberkus):

 So:

 My reason for unblocking these tests is simple:

 The version we are *currently distributing* also fails these tests.

 If we had a version on getfedora which passed the tests, and it was only
 the pending version which was failing, I'd keep them blocking.  But I see
 no point in continuing to block on tests which the "stable" version also
 doesn't pass.  Clearly we've decided it's acceptable to ship a version of
 Fedora Atomic which fails the log tests.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by dustymabe):

 Replying to [comment:5 trishnag]:
 > Replying to [comment:3 dustymabe]:
 > > Replying to [comment:2 trishnag]:
 > > > What is the point of having the testcase if we want to release
 images even though they have bugs?
 > > >
 > >
 > > So that we can find and fix bugs faster when they do happen. If we
 choose to release with the bug anyway then we know it exists and can guide
 users accordingly until it is fixed.
 > >
 > Okay, if we choose to release with the bug anyway does it mean that the
 bug is not going to affect users much?

 Yeah. The idea is that we put items to a vote and determine the severity.
 This bug is not that severe as it is just a logging issue. While
 important, it shouldn't block release in this case IMHO. My opinion could
 change in the future, but since this has been going out in our images for
 some time now we aren't making the currently released image any worse by
 releasing the next image.


 > > > This testcase is also **not a non-gating test** AFAIK.
 https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98
 > >
 > > Does that link prove it is a non-gating test? Where is the list of
 gating vs non-gating?
 > We put non-gating tests here
 https://github.com/kushaldas/tunirtests/blob/master/nongatingtests.py
 > Rest of the files have gating tests. Journal logging test is a gating
 test. So we have it in a separate file.


 Thanks

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by trishnag):

 Replying to [comment:3 dustymabe]:
 > Replying to [comment:2 trishnag]:
 > > What is the point of having the testcase if we want to release images
 even though they have bugs?
 > >
 >
 > So that we can find and fix bugs faster when they do happen. If we
 choose to release with the bug anyway then we know it exists and can guide
 users accordingly until it is fixed.
 >
 Okay, if we choose to release with the bug anyway does that mean that the
 bug is not going to affect users much?
 > > This testcase is also **not a non-gating test** AFAIK.
 https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98
 >
 > Does that link prove it is a non-gating test? Where is the list of
 gating vs non-gating?
 We put non-gating tests here
 https://github.com/kushaldas/tunirtests/blob/master/nongatingtests.py
 Rest of the files have gating tests. Journal logging test is a gating
 test. So we have it in a separate file.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by dustymabe):

 I vote aye (+1) to release with this known bug.

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by dustymabe):

 Replying to [comment:2 trishnag]:
 > What is the point of having the testcase if we want to release images
 even though they have bugs?
 >

 So that we can find and fix bugs faster when they do happen. If we choose
 to release with the bug anyway then we know it exists and can guide users
 accordingly until it is fixed.

 > This testcase is also **not a non-gating test** AFAIK.
 https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98

 Does that link prove it is a non-gating test? Where is the list of gating
 vs non-gating?

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by trishnag):

 What is the point of having the testcase if we want to release images even
 though they bugs?

 This testcase is also **not a non-gating test** AFAIK.
 https://github.com/kushaldas/tunirtests/blob/master/cloudtests.py#L61-L98

-- 
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] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+-
 Reporter:  kushal  |   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  --- |  Resolution:
 Keywords:  |
+-

Comment (by kushal):

 First I should vote:  Aye (to make them non-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

[cloud] #171: [VOTE] To mark recent failure on Atomic images as non blocking

[Fedora Cloud Trac Tickets]

#171: [VOTE] To mark recent failure on Atomic images as non blocking
+
 Reporter:  kushal  |  Owner:
 Type:  task| Status:  new
 Priority:  normal  |  Milestone:  Future
Component:  --- |   Keywords:
+
 You can view the error at
 https://apps.fedoraproject.org/autocloud/jobs/606/output#227

 Related bugzilla bus

 * https://bugzilla.redhat.com/show_bug.cgi?id=1265295
 * https://bugzilla.redhat.com/show_bug.cgi?id=1353688

 We want to mark these issues as non-blocking.

 Can the WG members please vote in? (Aye, Nay, Abstain).

-- 
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:   |
-+-
Changes (by sayanchowdhury):

 * 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] #153: design, deploy and document Fedora OpenShift Playground (FOSP)

[Fedora Cloud Trac Tickets]

#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
 Reporter:  goern|   Owner:  jberkus
 Type:  task |  Status:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+---

Comment (by jberkus):

 Next work session is Sept. 23

-- 
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:  closed
 Priority:  normal |   Milestone:  Future
Component:  ---|  Resolution:  fixed
 Keywords:  meeting|
---+-
Changes (by sayanchowdhury):

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


-- 
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] #154: make Fedora Atomic download page clearer

[Fedora Cloud Trac Tickets]

#154: make Fedora Atomic download page clearer
---+---
 Reporter:  jberkus|   Owner:  jberkus
 Type:  task   |  Status:  assigned
 Priority:  normal |   Milestone:  Future
Component:  Docker Host Image  |  Resolution:
 Keywords:  Meeting|
---+---

Comment (by jberkus):

 I've started work on this on the wiki:

 https://fedoraproject.org/wiki/Cloud/getfedora_update

-- 
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 jberkus):

 This is being deferred pending completion of
 
https://fedoraproject.org/wiki/Changes/ReleaseEngineeringAutomationWorkflowEngine

 It will be revisited once that's up and running.

-- 
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] #23: File F22 change: Re-factor cloud-init

[Fedora Cloud Trac Tickets]

#23: File F22 change: Re-factor cloud-init
--+---
 Reporter:  mattdm|   Owner:  hguemar
 Type:  task  |  Status:  assigned
 Priority:  normal|   Milestone:  Future
Component:  Cloud Base Image  |  Resolution:
 Keywords:|
--+---
Changes (by mvermaes):

 * cc: mvermaes@… (added)


-- 
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 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

[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

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