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

 When?  I'd like to join.

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

 Replying to [comment:8 jberkus]:
 > When?  I'd like to join.

 Next Friday.  I added you.

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

 Misc and I are meeting next week to flush out the architecture a bit more
 and maybe even kick off an install to kick the tires on.

-- 
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] #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  |   Keywords:  meeting
+-
 AIUI right now if you deploy OpenShift Origin on a Fedora Atomic host, it
 pulls down Origin running in CentOS based images. Perhaps we should port
 those images to Fedora.

 The images that the CentOS team are created are located here:

 https://wiki.centos.org/ContainerPipeline

 We would want to coordinate the effort with the images on Docker hub:

 https://hub.docker.com/u/openshift/

 And figure how this fits into Fedoras build system.

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

Fedora Cloud SIG Minutes - 8/10/2016

[Scott Collier]

https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-10/fedora_cloud_wg.2016-08-10-17.00.html

#fedora-meeting-1: fedora_cloud_wg
Meeting started by scollier at 17:00:56 UTC (full logs).

Meeting summary

Roll Call (scollier, 17:01:02)
Ticket https://fedorahosted.org/cloud/ticket/125 (scollier, 17:04:41)
Ticket https://fedorahosted.org/cloud/ticket/136 (scollier, 17:05:18)
Ticket https://fedorahosted.org/cloud/ticket/147 (scollier, 17:06:17)
Ticket https://fedorahosted.org/cloud/ticket/151 (scollier, 17:11:22)
Ticket https://fedorahosted.org/cloud/ticket/153 (scollier, 17:13:51)
Ticket https://fedorahosted.org/cloud/ticket/155 (scollier, 17:15:37)
Ticket https://fedorahosted.org/cloud/ticket/160 (scollier, 17:31:33)
Ticket https://fedorahosted.org/cloud/ticket/167 (scollier, 17:38:31)
ACTION: rtnpro will add test workflow (and test cases) for 
testing fedora-motd on F24 atomic image (rtnpro, 17:39:05)
https://bugzilla.redhat.com/show_bug.cgi?id=1353688 (trishnag, 
17:41:42)


Open Floor (scollier, 17:49:45)
ACTION: kushal to write to infra for permission to update 
Autocloud tests while in freeze (kushal, 17:54:38)
http://dustymabe.com/2014/09/08/capture-elusive-cloud-init-debug-output-with-journalctl/ 
(dustymabe, 18:00:28)


Meeting ended at 18:01:02 UTC (full logs).

Action items

rtnpro will add test workflow (and test cases) for testing 
fedora-motd on F24 atomic image
kushal to write to infra for permission to update Autocloud tests 
while in freeze


Action items, by person

kushal
kushal to write to infra for permission to update Autocloud 
tests while in freeze

rtnpro
rtnpro will add test workflow (and test cases) for testing 
fedora-motd on F24 atomic image


People present (lines said)

scollier (79)
dustymabe (79)
maxamillion (46)
kushal (43)
jbrooks_ (35)
zodbot (20)
rtnpro (17)
gholms (15)
trishnag (8)
bowlofeggs (2)
sayan (2)
jbrooks (0)

___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: [cloud] #151: Need owner to define basic container smoke testing requirements

[Fedora Cloud Trac Tickets]

#151: Need owner to define basic container smoke testing requirements
-+--
 Reporter:  acarter  |   Owner:  maxamillion
 Type:  task |  Status:  closed
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:  fixed
 Keywords:  meeting  |
-+--
Changes (by kushal):

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


Comment:

 The QA team is happy with the current state, we are closing this ticket.
 We can reopen it in future if required.

-- 
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] #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:  --- |   Keywords:  meeting
+-
 If we have a test failing the compose (right test, catching a real bug),
 should we stop the release till the time the bug gets resolved?

 My personal opinion is yes, first fix, and then only go ahead.

 For example [https://apps.fedoraproject.org/autocloud/jobs/353/output#283
 this test] fails time to time on the vagrant virtualbox image.

-- 
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] #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   |
--+---
Changes (by rtnpro):

 * owner:  rtnpro => kushal
 * status:  new => assigned
 * component:  --- => Cloud Base Image


-- 
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] #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:  assigned
 Priority:  normal   |   Milestone:  Future
Component:  ---  |  Resolution:
 Keywords:  meeting  |
-+--

Comment (by jasonbrooks):

 We discussed this in a fedora cloud mtg on Jul 20
 (https://meetbot.fedoraproject.org/fedora-
 meeting-1/2016-07-20/fedora_cloud_wg.2016-07-20-17.00.log.html).

 Currently, bodhi updates the testing and stable ostree repos when there
 are new testing or stable pkgs. There's a desire, expressed in the issue
 that Adam referenced above (https://fedorahosted.org/rel-eng/ticket/6313)
 for an ostree commit that coincides with the two week releases.

 The requested changes, as summarized by Colin Walters, who filed the bug:

   Colin's executive summary: Create a new additional ref:

   fedora-atomic/f23/x86_64/batch/docker-host

   Allow users to rebase to this who want it.

   * Change the two-week-atomic.py script to generate this (new rpm-ostree
 run, need to sed the json for the new ref)
   * then sed the kickstarts to pull from it (but still use a *target* ref
 of fedora-atomic/f23/x86_64/docker-host ?)
   * Decide on a version numbering scheme...e.g. also use a datestamp? So
 ostree.version=23.20160106, need to pass this to rpm-ostree

 More detail, from another comment (https://fedorahosted.org/rel-
 eng/ticket/6313#comment:12) some months later:

  * The delivered/highlighted output is a combination ostree compose and
 image build(s) based on that compose, done every two weeks
  * Mirrors should contain the current image, the current compose and 3
 prior composes (1 image and 4 ostree composes in total) - older composes
 may be pruned at will
  * Anything done more frequently should be for dev/test only, need not be
 mirrored and can be pruned at will

 == Next Actions: ==

 * Do we have enough consensus to make the change? On Jul 20, jbrooks and
 dustymabe explicitly +1'd it. Colin requested it originally in
 https://fedorahosted.org/rel-eng/ticket/6313, and Adam seemed to agree as
 well.
 * Settle on the versioning scheme, does datestamp work?
 * Change the two week script
 (https://pagure.io/releng/blob/master/f/scripts/push-two-week-atomic.py)
 * Once the changes are in place and settled, consider process for dealing
 with critical security issues.

-- 
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: Fedora Atomic Host Two Week Release Announcement

[Vasiliy Tolstov]

2016-08-10 16:52 GMT+03:00 Dennis Gilmore :
> change alt to download so https://download.fedoraproject.org/pub/alt/atomic/
> it will redirect you to a globally close mirror


Thanks!

-- 
Vasiliy Tolstov,
e-mail: v.tols...@yoctocloud.net
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Matt Micene]

If I'm reading the autocloud results correctly, that failed on the
VirtualBox provider but not the libvirt provider:

https://apps.fedoraproject.org/autocloud/jobs/355/output#299

Is there a difference between the two box providers that isn't being taken
into account for the existence of the user journal?

Cheers,
Matt M

On Wed, Aug 10, 2016 at 2:26 AM, Trishna Guha 
wrote:

> On Wed, Aug 10, 2016 at 9:27 AM, Adam Miller <
> maxamill...@fedoraproject.org> wrote:
> >
> > Appears to be a bug, I'll get it fixed.
> >
> After reading the job details, this is exact error we can see [1].
> For Vagrant Atomic image user journal is not getting logged to disk ever.
> That's why the error has occurred. I had discussion with dustymabe before
> also regarding this bug.
> It seems the bug is **user journal not getting logged to disk for vagrant
> atomic image**. This is the  BZ issue we have for the bug[2].
>
> [1] https://apps.fedoraproject.org/autocloud/jobs/353/output#290
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1353688
> 
> --
> Regards,
> Trishna Guha
>
> irc nick: trishnag
> Kolkata, India
> trish...@fedoraproject.org
> trishnag.wordpress.com
> https://github.com/trishnaguha
>
> ___
> cloud mailing list
> cloud@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
>
>
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Dennis Gilmore]

On Wednesday, August 10, 2016 2:54:44 PM CDT Vasiliy Tolstov wrote:
> Does https://alt.fedoraproject.org/pub/alt/atomic/ have mirror that
> more close to Russia?

change alt to download so https://download.fedoraproject.org/pub/alt/atomic/
it will redirect you to a globally close mirror

Dennis

> 2016-08-10 9:26 GMT+03:00 Trishna Guha :
> > On Wed, Aug 10, 2016 at 9:27 AM, Adam Miller
> > > 
> > wrote:
> >> Appears to be a bug, I'll get it fixed.
> > 
> > After reading the job details, this is exact error we can see [1].
> > For Vagrant Atomic image user journal is not getting logged to disk ever.
> > That's why the error has occurred. I had discussion with dustymabe before
> > also regarding this bug.
> > It seems the bug is **user journal not getting logged to disk for vagrant
> > atomic image**. This is the  BZ issue we have for the bug[2].
> > 
> > [1] https://apps.fedoraproject.org/autocloud/jobs/353/output#290
> > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1353688
> > 
> > --
> > Regards,
> > Trishna Guha
> > 
> > irc nick: trishnag
> > Kolkata, India
> > trish...@fedoraproject.org
> > trishnag.wordpress.com
> > https://github.com/trishnaguha
> > 
> > ___
> > cloud mailing list
> > cloud@lists.fedoraproject.org
> > https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Trishna Guha]

On Wed, Aug 10, 2016 at 9:27 AM, Adam Miller 
wrote:
>
> Appears to be a bug, I'll get it fixed.
>
After reading the job details, this is exact error we can see [1].
For Vagrant Atomic image user journal is not getting logged to disk ever.
That's why the error has occurred. I had discussion with dustymabe before
also regarding this bug.
It seems the bug is **user journal not getting logged to disk for vagrant
atomic image**. This is the  BZ issue we have for the bug[2].

[1] https://apps.fedoraproject.org/autocloud/jobs/353/output#290
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1353688

-- 
Regards,
Trishna Guha

irc nick: trishnag
Kolkata, India
trish...@fedoraproject.org
trishnag.wordpress.com
https://github.com/trishnaguha
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org