Cloud Meeting Minutes 2016-09-07
by Trishna Guha
Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-07/fedora_clou...
Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-07/fedora_clou...
==================================
#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_clou...
.
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/Brochu...
(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
7 years, 7 months
[EMAIL FROM ZACK:] Re: cloud Digest, Vol 81, Issue 1
by Zack Cylinder
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
> ************************************
>
7 years, 7 months
Why do we have an older version number for today's atomic compose?
compose?
by Kushal Das
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
7 years, 7 months
Proposal to test AMIs using Autocloud
by Sayan Chowdhury
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!
7 years, 7 months
