September 2016 - cloud - Fedora mailing-lists

[cloud] #171: [VOTE] To mark recent failure on Atomic images as non blocking
by Fedora Cloud Trac Tickets 21 Sep '16

21 Sep '16

#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: <https://fedorahosted.org/cloud/ticket/171> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 16

overlayfs for AFTER Fedora 25
by Dusty Mabe 20 Sep '16

20 Sep '16

In the cloud meeting today I brought up overlayfs and F25. After discussing with the engineers closer to the technology they recommend waiting to move to overlayfs as the default in F26. I think this will work well because it will give us some time to allow people to "try" overlayfs in F25 (we should provide good docs on this) and then give us feedback before we go with it as default in F26. If the feedback is bad then maybe we wouldn't even go with it in F26, but hopefully that won't be the case. Thoughts? Dusty

8 14

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 19 Sep '16

19 Sep '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-09-21 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

F24 Atomic installer image suddenly showing pre-release warning
by Adam Williamson 17 Sep '16

17 Sep '16

This week, the F24 Atomic installer image suddenly started showing the pre-release warning: https://bugzilla.redhat.com/show_bug.cgi?id=1375747 This will cause the openQA test for it to fail until it's fixed (or until I add a softfail workaround, which I can do if it can't be fixed quickly, but...) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

F24 autocloud failure should be fixed by https://bodhi.fedoraproject.org/updates/ostree-2016.10-4.fc24
by Colin Walters 16 Sep '16

16 Sep '16

See https://bodhi.fedoraproject.org/updates/ostree-2016.10-4.fc24

1 0

[cloud] #169: Spec for IRC bot to notify about blockers
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#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: <https://fedorahosted.org/cloud/ticket/169> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

2 5

Cloud Meeting Minutes 2016-09-14
by Sayan Chowdhury 14 Sep '16

14 Sep '16

================================== #fedora-meeting-1: fedora_cloud_wg ================================== Meeting started by sayan at 17:00:24 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-14/fedora_cloud_… . Meeting summary --------------- * Roll Call (sayan, 17:00:33) * Action items from last meeting (sayan, 17:02:51) * vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 (sayan, 17:06:00) * Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 (sayan, 17:16:33) * design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 (sayan, 17:19:47) * make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 (sayan, 17:22:46) * ACTION: Kushal will work on moving to Pagure from Trac (kushal, 17:35:33) * Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 (sayan, 17:36:25) * Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 (sayan, 17:39:29) * Ship fedora-motd in F24 atomic image https://fedorahosted.org/cloud/ticket/160 (sayan, 17:41:40) * Decide a process about failed tests for Autocloud https://fedorahosted.org/cloud/ticket/167 (sayan, 17:43:40) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1265295 and https://bugzilla.redhat.com/show_bug.cgi?id=1353688 (kushal, 17:44:40) * Put OpenShift Origin in Container with Fedora Base https://fedorahosted.org/cloud/ticket/168 (sayan, 17:55:25) * Spec for IRC bot to notify about blockers https://fedorahosted.org/cloud/ticket/169 (sayan, 17:56:38) * Open Floor (sayan, 17:58:11) * ACTION: kushal will create the vote ticket, and update the list :) (kushal, 18:05:35) Meeting ended at 18:05:57 UTC. Action Items ------------ * Kushal will work on moving to Pagure from Trac * kushal will create the vote ticket, and update the list :) Action Items, by person ----------------------- * kushal * kushal will create the vote ticket, and update the list :) * **UNASSIGNED** * Kushal will work on moving to Pagure from Trac People Present (lines said) --------------------------- * kushal (76) * sayan (67) * jberkus (61) * jbrooks (39) * dustymabe (33) * maxamillion (32) * zodbot (20) * walters (11) * imcleod (8) * trishnag (7) * rtnpro (2) * tflink (1) * jdetiber (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

1 0

[cloud] #147: Don't overwrite download location for 2 week atomic images
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#147: Don't overwrite download location for 2 week atomic images -----------------------+--------------------- Reporter: dustymabe | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: --- | Keywords: meeting -----------------------+--------------------- Would be nice if the images don't get overwritten on each release. See discussion in this email thread: https://lists.fedoraproject.org/archives/list/cloud%40lists.fedoraproject.o… -- Ticket URL: <https://fedorahosted.org/cloud/ticket/147> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 16

getfedora/atomic update
by Josh Berkus 14 Sep '16

14 Sep '16

Folks, For the F25 release, we want to update getfedora/cloud to getfedora/atomic. But this means having a bunch of new content, and simplifying the list of available downloads. Here's my stab at it: https://fedoraproject.org/wiki/Cloud/getfedora_update Let's discuss this tommorrow during the meeting. -- -- Josh Berkus Project Atomic Red Hat OSAS

2 1

[cloud] #154: make Fedora Atomic download page clearer
by Fedora Cloud Trac Tickets 14 Sep '16

14 Sep '16

#154: make Fedora Atomic download page clearer -------------------------------+--------------------- Reporter: jberkus | Owner: Type: task | Status: new Priority: normal | Milestone: Future Component: Docker Host Image | Keywords: Meeting -------------------------------+--------------------- The Fedora Atomic Host Download page is confusing to users. I'd like to make some changes making it clearer what to download and why, including: * The ISO images should be a main option, not a link in the sidebar * The qcow2 images, not the raw images, should say "if you're not sure what to use, use this". * Each download option should have a link to the specific docs for installing that kind of download (will wait on new Atomic Host docs, though) Also, it would be great if we could list on the download page somewhere what date the images are from for each 2-week build. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/154> cloud <https://fedorahosted.org/cloud> Fedora Cloud Working Group Ticketing System

1 5

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 12 Sep '16

12 Sep '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-09-14 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

growpart not working in Fedora 25 cloud base
by Dusty Mabe 11 Sep '16

11 Sep '16

From https://kojipkgs.fedoraproject.org//work/tasks/5352/15555352/Fedora-Cloud-B… Sep 10 03:13:17 cloudhost.localdomain cloud-init[645]: 2016-09-10 03:13:17,078 - util.py[WARNING]: Failed: growpart /dev/sda 1 Sep 10 03:13:17 cloudhost.localdomain cloud-init[645]: [CLOUDINIT] util.py[DEBUG]: Failed: growpart /dev/sda 1 Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/cloudinit/config/cc_growpart.py", line 109, in resize util.subp(["growpart", diskdev, partnum]) File "/usr/lib/python3.5/site-packages/cloudinit/util.py", line 1724, in subp cmd=args) cloudinit.util.ProcessExecutionError: Unexpected error while running command. Command: ['growpart', '/dev/sda', '1'] Exit code: 2 Reason: - Stdout: 'FAILED: failed to resize\n' Stderr: "attempt to resize /dev/sda failed. sfdisk output below:\n| Backup files:\n| MBR (offset 0, size 512): /tmp/growpart.PO8wWI/backup-sda-0x00000000.bak\n| \n| Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors\n| Units: sectors of 1 * 512 = 512 bytes\n| Sector size (logical/physical): 512 bytes / 512 bytes\n| I/O size (minimum/optimal): 512 bytes / 512 bytes\n| Disklabel type: dos\n| Disk identifier: 0x1ef30347\n| \n| Old situation:\n| \n| Device Boot Start End Sectors Size Id Type\n| /dev/sda1 * 2048 6291455 6289408 3G 83 Linux\n| \n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Created a new DOS disklabel with disk identifier 0x1ef30347.\n| Created a new partition 1 of type 'Linux' and of size 10 GiB.\n| /dev/sda2: \n| New situation:\n| \n| Device Boot Start End Sectors Size Id Type\n| /dev/sda1 * 2048 20971519 20969472 10G 83 Linux\n| \n| The partition table has been altered.\n| Calling ioctl() to re-read partition table.\n| Re-reading the partition table failed.: Device or resource busy\n| The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).\n***** WARNING: Resize failed, attempting to revert ******\n512+0 records in\n512+0 records out\n512 bytes copied, 0.000400551 s, 1.3 MB/s\n***** Appears to have gone OK ****\n" Sep 10 03:13:17 cloudhost.localdomain cloud-init[645]: [CLOUDINIT] util.py[DEBUG]: resize_devices took 0.127 seconds Sep 10 03:13:17 cloudhost.localdomain cloud-init[645]: [CLOUDINIT] cc_growpart.py[DEBUG]: '/' FAILED: failed to resize: disk=/dev/sda, ptnum=1: Unexpected error while running command. Command: ['growpart', '/dev/sda', '1'] Exit code: 2 Reason: - Stdout: 'FAILED: failed to resize\n' Stderr: "attempt to resize /dev/sda failed. sfdisk output below:\n| Backup files:\n| MBR (offset 0, size 512): /tmp/growpart.PO8wWI/backup-sda-0x00000000.bak\n| \n| Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors\n| Units: sectors of 1 * 512 = 512 bytes\n| Sector size (logical/physical): 512 bytes / 512 bytes\n| I/O size (minimum/optimal): 512 bytes / 512 bytes\n| Disklabel type: dos\n| Disk identifier: 0x1ef30347\n| \n| Old situation:\n| \n| Device Boot Start End Sectors Size Id Type\n| /dev/sda1 * 2048 6291455 6289408 3G 83 Linux\n| \n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Script header accepted.\n| >>> Created a new DOS disklabel with disk identifier 0x1ef30347.\n| Created a new partition 1 of type 'Linux' and of size 10 GiB.\n| /dev/sda2: \n| New situation:\n| \n| Device Boot Start End Sectors Size Id Type\n| /dev/sda1 * 2048 20971519 20969472 10G 83 Linux\n| \n| The partition table has been altered.\n| Calling ioctl() to re-read partition table.\n| Re-reading the partition table failed.: Device or resource busy\n| The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).\n***** WARNING: Resize failed, attempting to revert ******\n512+0 records in\n512+0 records out\n512 bytes copied, 0.000400551 s, 1.3 MB/s\n***** Appears to have gone OK ****\n" Should I open a bug for this? Can we get someone to look at it/work on it? Dusty

3 7

Open 365 and SE linux
by Benson Muite 09 Sep '16

09 Sep '16

Hi, Am looking at using Open 365 with fedora on cloud, but it seems to require disabling SE linux: https://github.com/Open365/Open365/ Should this be needed? What would be the consequences of this? Regards, Benson

2 1

More Atomic troubles on F25
by Adam Williamson 08 Sep '16

08 Sep '16

So since I was told to make more noise...:) F25 composes no longer seem to be hitting the chrony bug (RHBZ #1331864) for some reason - Rawhide composes still do - so install from the Atomic DVD installer image succeeds. However, booting the installed system fails. I *think* this is because its initramfs is broken. See https://bugzilla.redhat.com/show_bug.cgi?id=1374082 for more details. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

No Two Week Atomic Host this cycle
by Adam Miller 08 Sep '16

08 Sep '16

Hello all, There have not been any composes that have passed all AutoCloud Tests this Two-Week cycle and we will therefore be deferring release until the next cycle. The main blocker bug is being worked on[0]. Thank you, -AdamM [0] - https://bugzilla.redhat.com/show_bug.cgi?id=1353688

1 0

Cloud Meeting Minutes 2016-09-07
by Trishna Guha 07 Sep '16

07 Sep '16

Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-07/fedora_cloud_… Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-07/fedora_cloud_… ================================== #fedora-meeting-1: fedora_cloud_wg ================================== Meeting started by trishnag at 17:00:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-07/fedora_cloud_… . Meeting summary --------------- * Roll Call (trishnag, 17:00:22) * Action items from last meeting (trishnag, 17:03:42) * rtnpro will add test workflow (and test cases) for testing fedora-motd on F24 atomic image (trishnag, 17:03:55) * ACTION: rtnpro to write testcases for testing fedora-motd on F24 atomic image and push to git for others to review (trishnag, 17:10:43) * kushal to test new cloud-init on openstack (trishnag, 17:11:10) * ACTION: kushal to test new cloud-init on openstack (trishnag, 17:12:45) * jberkus will draft spec for IRC bot for blocker bugs (trishnag, 17:13:07) * LINK: https://fedorahosted.org/cloud/ticket/169 (jberkus, 17:13:53) * vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136 (trishnag, 17:29:02) * Don't overwrite download location for 2 week atomic images https://fedorahosted.org/cloud/ticket/147 (trishnag, 17:32:09) * design, deploy and document Fedora OpenShift Playground (FOSP) https://fedorahosted.org/cloud/ticket/153 (trishnag, 17:35:55) * make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 (trishnag, 17:38:16) * LINK: https://github.com/fedoradesign/nextweb-assets/blob/master/Mockups/Brochure… (mizmo, 17:43:15) * Decide on post-GA update cadence for various deliverables https://fedorahosted.org/cloud/ticket/155 (trishnag, 17:46:01) * make Fedora Atomic download page clearer https://fedorahosted.org/cloud/ticket/154 (trishnag, 17:46:52) * Need complete Kickstart docs for Atomic Host https://fedorahosted.org/cloud/ticket/156 (trishnag, 17:49:46) * Decide a process about failed tests for Autocloud https://fedorahosted.org/cloud/ticket/167 (trishnag, 17:53:46) * Finish new Fedora Cloud PRD https://fedorahosted.org/cloud/ticket/170 (trishnag, 17:55:51) * Open Floor (trishnag, 17:58:14) Meeting ended at 18:01:29 UTC. Action Items ------------ * rtnpro to write testcases for testing fedora-motd on F24 atomic image and push to git for others to review * kushal to test new cloud-init on openstack Action Items, by person ----------------------- * kushal * kushal to test new cloud-init on openstack * rtnpro * rtnpro to write testcases for testing fedora-motd on F24 atomic image and push to git for others to review * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (69) * trishnag (58) * jberkus (45) * zodbot (20) * dustymabe (18) * rtnpro (15) * maxamillion (13) * mizmo (12) * jbrooks (8) * sayan (3) * bowlofeggs (2) * tflink (1) * ashcrow (1) * vvaldez (1) * jdetiber (1) * lalatenduM (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[EMAIL FROM ZACK:] Re: cloud Digest, Vol 81, Issue 1
by Zack Cylinder 07 Sep '16

07 Sep '16

Hey! Zack Cylinder Cloudbakers Cloud Training Specialist On Tue, Sep 6, 2016 at 8:18 AM, <cloud-request(a)lists.fedoraproject.org> wrote: > Send cloud mailing list submissions to > cloud(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.fedoraproject.org/admin/lists/cloud@lists. > fedoraproject.org > or, via email, send a message with subject or body 'help' to > cloud-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > cloud-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cloud digest..." > > Today's Topics: > > 1. Fedora 25 (Benson Muite) > 2. Re: Fedora 25 (Chris Murphy) > 3. Why do we have an older version number for today's atomic compose? > compose? > (Kushal Das) > 4. [Fedocal] Reminder meeting : Fedora Cloud Workgroup > (dusty(a)dustymabe.com) > 5. Re: Why do we have an older version number for today's atomic > compose? compose? > (Kushal Das) > 6. Re: Why do we have an older version number for today's atomic > compose? compose? > (Dusty Mabe) > 7. Fedora 25 atomic images are stuck while booting (Kushal Das) > 8. Re: Fedora 25 atomic images are stuck while booting > (Colin Walters) > > > ---------------------------------------------------------------------- > > Date: Sun, 4 Sep 2016 15:54:15 +0300 > From: Benson Muite <benson_muite(a)emailplus.org> > Subject: Fedora 25 > To: cloud(a)lists.fedoraproject.org > Cc: Fedora Marketing team <marketing(a)lists.fedoraproject.org> > Message-ID: <195b12e8-187b-6bde-f2ad-8cac34212169(a)emailplus.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > If any of you use Fedora Atomic as a desktop, could you add a brief > overview of why and how (workflow) you do so here: > https://fedoraproject.org/wiki/Fedora_25_talking_points > > For the typical Fedora workstation user, what is needed to migrate to > Fedora Atomic as a desktop? Does this make it easier to use remote cloud > resources? > > Finally please also indicate any hosting providers for which atomic is a > one click install - this seems to be of interest for some users: > https://www.digitalocean.com/community/questions/what- > about-atomic-fedora-centos-or-redhat-in-addition-to-coreos > > > Regards, > Benson > > ------------------------------ > > Date: Sun, 4 Sep 2016 15:47:55 -0600 > From: Chris Murphy <lists(a)colorremedies.com> > Subject: Re: Fedora 25 > To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org> > Cc: Fedora Marketing team <marketing(a)lists.fedoraproject.org> > Message-ID: > <CAJCQCtRwBpbES_x6DJRQvsaZeLn_JSO-=PaLnm=PtsAYW=qEdw@mail. > gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Sun, Sep 4, 2016 at 6:54 AM, Benson Muite <benson_muite(a)emailplus.org> > wrote: > > Hi, > > > > If any of you use Fedora Atomic as a desktop, could you add a brief > overview > > of why and how (workflow) you do so here: > > https://fedoraproject.org/wiki/Fedora_25_talking_points > > > > For the typical Fedora workstation user, what is needed to migrate to > Fedora > > Atomic as a desktop? Does this make it easier to use remote cloud > resources? > > These might be better asked on desktop@ list where the Workstation WG > and users can put in their 2 cents? > > > -- > Chris Murphy > > ------------------------------ > > Date: Mon, 5 Sep 2016 20:42:46 +0530 > From: Kushal Das <mail(a)kushaldas.in> > Subject: Why do we have an older version number for today's atomic > compose? compose? > To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org> > Message-ID: <20160905151246.GA5163@kdas-laptop> > Content-Type: text/plain; charset=utf-8 > > Hi, > > After an *atomic host upgrade* in an atomic host. > > Deployments: > ● fedora-atomic:fedora-atomic/24/x86_64/docker-host > Version: 24.35 (2016-09-05 01:23:02) > Commit: 5832e43bcf2054a46169442557d434 > 8d38e280161955c4bcd83b19db6649a5df > OSName: fedora-atomic > GPGSignature: (unsigned) > > fedora-atomic:fedora-atomic/24/x86_64/docker-host > Version: 24.39 (2016-06-15 09:57:04) > Commit: 2c7d41e8a67931fe21bc92100c59cf > f8a94c2df5a0e6a1b75957bda141601481 > OSName: fedora-atomic > GPGSignature: (unsigned) > > > Any idea anyone? > > Kushal > -- > Fedora Cloud Engineer > CPython Core Developer > https://kushaldas.in > https://dgplug.org > > ------------------------------ > > Date: Mon, 5 Sep 2016 17:00:03 +0000 (UTC) > From: dusty(a)dustymabe.com > Subject: [Fedocal] Reminder meeting : Fedora Cloud Workgroup > To: cloud(a)lists.fedoraproject.org > Message-ID: > <20160905170003.8B75360A4003(a)fedocal02.phx2.fedoraproject.org> > Content-Type: text/plain; charset="utf-8" > > Dear all, > > You are kindly invited to the meeting: > Fedora Cloud Workgroup on 2016-09-07 from 17:00:00 to 18:00:00 UTC > At fedora-meeting-1(a)irc.freenode.net > > The meeting will be about: > Standing meeting for the Fedora Cloud Workgroup > > > Source: https://apps.fedoraproject.org/calendar/meeting/1999/ > > > ------------------------------ > > Date: Mon, 5 Sep 2016 23:36:24 +0530 > From: Kushal Das <mail(a)kushaldas.in> > Subject: Re: Why do we have an older version number for today's atomic > compose? compose? > To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org> > Message-ID: <20160905180624.GA6840@kdas-laptop> > Content-Type: text/plain; charset=utf-8 > > On 05/09/16, Kushal Das wrote: > > Hi, > > > > After an *atomic host upgrade* in an atomic host. > > > > Deployments: > > ● fedora-atomic:fedora-atomic/24/x86_64/docker-host > > Version: 24.35 (2016-09-05 01:23:02) > > Commit: 5832e43bcf2054a46169442557d434 > 8d38e280161955c4bcd83b19db6649a5df > > OSName: fedora-atomic > > GPGSignature: (unsigned) > > > > fedora-atomic:fedora-atomic/24/x86_64/docker-host > > Version: 24.39 (2016-06-15 09:57:04) > > Commit: 2c7d41e8a67931fe21bc92100c59cf > f8a94c2df5a0e6a1b75957bda141601481 > > OSName: fedora-atomic > > GPGSignature: (unsigned) > > > Found more strange information. > > I had installed the box from [1]. But, after booting this was the host > status. > > # atomic host status > TIMESTAMP (UTC) VERSION ID OSNAME > REFSPEC > * 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic > fedora-atomic:fedora-atomic/24/x86_64/docker-host > > I remeber Dusty sending a related mail. But I do not remember if we > found the cause. > > [1] > http://alt.fedoraproject.org/pub/alt/atomic/stable/Atomic/ > x86_64/iso/Fedora-Atomic-dvd-x86_64-24-20160820.0.iso > > Kushal > -- > Fedora Cloud Engineer > CPython Core Developer > https://kushaldas.in > https://dgplug.org > > ------------------------------ > > Date: Mon, 5 Sep 2016 20:40:03 -0400 > From: Dusty Mabe <dusty(a)dustymabe.com> > Subject: Re: Why do we have an older version number for today's atomic > compose? compose? > To: cloud(a)lists.fedoraproject.org > Message-ID: <6fc5ff8f-4f67-5732-0c47-93b717d7ef71(a)dustymabe.com> > Content-Type: text/plain; charset=utf-8 > > > > On 09/05/2016 02:06 PM, Kushal Das wrote: > > On 05/09/16, Kushal Das wrote: > >> Hi, > >> > >> After an *atomic host upgrade* in an atomic host. > >> > >> Deployments: > >> ● fedora-atomic:fedora-atomic/24/x86_64/docker-host > >> Version: 24.35 (2016-09-05 01:23:02) > >> Commit: 5832e43bcf2054a46169442557d434 > 8d38e280161955c4bcd83b19db6649a5df > >> OSName: fedora-atomic > >> GPGSignature: (unsigned) > >> > >> fedora-atomic:fedora-atomic/24/x86_64/docker-host > >> Version: 24.39 (2016-06-15 09:57:04) > >> Commit: 2c7d41e8a67931fe21bc92100c59cf > f8a94c2df5a0e6a1b75957bda141601481 > >> OSName: fedora-atomic > >> GPGSignature: (unsigned) > >> > > Found more strange information. > > > > I had installed the box from [1]. But, after booting this was the host > > status. > > > > # atomic host status > > TIMESTAMP (UTC) VERSION ID OSNAME > REFSPEC > > * 2016-06-15 09:57:04 24.39 2c7d41e8a6 fedora-atomic > fedora-atomic:fedora-atomic/24/x86_64/docker-host > > > > I remeber Dusty sending a related mail. But I do not remember if we > > found the cause. > > We think we fixed it (see thread at [1]). Will you please check the > latest generated isos and see if they are fixed? > > [1] https://lists.fedoraproject.org/archives/list/cloud@lists. > fedoraproject.org/thread/L4EWWWL6HEV3UHOGI2GLERA5BOOD7I43/# > E2P5FE65LOFCNLAORFTVUKK2EVBN4FML > > ------------------------------ > > Date: Tue, 6 Sep 2016 12:29:07 +0530 > From: Kushal Das <mail(a)kushaldas.in> > Subject: Fedora 25 atomic images are stuck while booting > To: cloud(a)lists.fedoraproject.org > Cc: rel-eng(a)lists.fedoraproject.org > Message-ID: <20160906065907.GA8823@kdas-laptop> > Content-Type: text/plain; charset=us-ascii > > Hi, > > We can not ssh into the latest Fedora 25 based atomic images. While > booting one image in Openstack I got [1] as console output. > > [1] https://kushal.fedorapeople.org/f25_notbooting1.png > > Kushal > -- > Fedora Cloud Engineer > CPython Core Developer > https://kushaldas.in > https://dgplug.org > > ------------------------------ > > Date: Tue, 06 Sep 2016 09:18:09 -0400 > From: Colin Walters <walters(a)verbum.org> > Subject: Re: Fedora 25 atomic images are stuck while booting > To: Kushal Das <mail(a)kushaldas.in>, cloud(a)lists.fedoraproject.org > Message-ID: > <1473167889.409531.717130033.75A93EFC(a)webmail.messagingengine.com> > Content-Type: text/plain > > > > On Tue, Sep 6, 2016, at 02:59 AM, Kushal Das wrote: > > Hi, > > > > We can not ssh into the latest Fedora 25 based atomic images. While > > booting one image in Openstack I got [1] as console output. > > There were a few causes of this, but to level set, let's be sure that > https://bodhi.fedoraproject.org/updates/ostree-2016.9-1. > fc25%20rpm-ostree-2016.7-4.fc25 > is used for the treecompose. > > One possible cause is that previous versions of rpm-ostree didn't > set up a container around dracut, and libkmod barfed on the lack > of /proc/modules, which caused no kernel modules to end up > in the initramfs. > > Now rpm-ostree consistently uses bubblewrap which fixes it > for me. > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > cloud mailing list > cloud(a)lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org > > > ------------------------------ > > End of cloud Digest, Vol 81, Issue 1 > ************************************ >

1 0

Why do we have an older version number for today's atomic compose? compose?
by Kushal Das 07 Sep '16

07 Sep '16

Hi, After an *atomic host upgrade* in an atomic host. Deployments: ● fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.35 (2016-09-05 01:23:02) Commit: 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df OSName: fedora-atomic GPGSignature: (unsigned) fedora-atomic:fedora-atomic/24/x86_64/docker-host Version: 24.39 (2016-06-15 09:57:04) Commit: 2c7d41e8a67931fe21bc92100c59cff8a94c2df5a0e6a1b75957bda141601481 OSName: fedora-atomic GPGSignature: (unsigned) Any idea anyone? Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

3 5

Fedora 25 atomic images are stuck while booting
by Kushal Das 06 Sep '16

06 Sep '16

Hi, We can not ssh into the latest Fedora 25 based atomic images. While booting one image in Openstack I got [1] as console output. [1] https://kushal.fedorapeople.org/f25_notbooting1.png Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

2 1

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 05 Sep '16

05 Sep '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-09-07 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

Fedora 25
by Benson Muite 04 Sep '16

04 Sep '16

Hi, If any of you use Fedora Atomic as a desktop, could you add a brief overview of why and how (workflow) you do so here: https://fedoraproject.org/wiki/Fedora_25_talking_points For the typical Fedora workstation user, what is needed to migrate to Fedora Atomic as a desktop? Does this make it easier to use remote cloud resources? Finally please also indicate any hosting providers for which atomic is a one click install - this seems to be of interest for some users: https://www.digitalocean.com/community/questions/what-about-atomic-fedora-c… Regards, Benson

2 1

Proposal to test AMIs using Autocloud
by Sayan Chowdhury 01 Sep '16

01 Sep '16

Hi, I am planning to move the testing functionality to test AMIs from fedimg to Autocloud. Right now, the fedimg just runs the /bin/true command to test if the AMIs is proper or not. Therefore, I am planning to completely remove this functionality from fedimg and move to Autocloud. The plan: 1. Once fedimg creates a new AMI. It will be sending out a fedmsg message with a new topic 'fedimg.ami.create'. 2. Autocloud will be listening to this topic and schedule a testing for the AMI using Tunir. This process will be completely separate and will have no overlap with the current process of testing images. 3. If the test passes, Autocloud emits fedmsg message with topic 'ami.passed'. Fedimg listens to this topic and makes that particular AMI public and copies the AMI to other regions. 4. If the test fails, Autocloud emits fedmsg message with topic 'ami.failed. Fedimg also listens to this topic and deletes all the AMis and related resources. This will give the provision to test the AMIs properly and we can have a separate dashboard for the same. As soon as deployed, we can run tests from the current set of testcases we have. Do share your thoughts or questions on this proposal. -- Sayan Chowdhury <https://sayanchowdhury.dgplug.org/> Senior Software Engineer, Fedora Engineering - Emerging Platform GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B Proud to work at The Open Organization!

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud September 2016