[fedora-atomic] Issue #72: Flock 2017 list of events from Atomic WG

[Kushal Das]

kushal reported a new issue against the project: `fedora-atomic` that you are 
following:
``
Please comment in this ticket for any talk, workshop, or discussion related to 
Atomic WG during Flock 2017. This will help us to make sure that we don't miss 
any important meeting.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-atomic/issue/72
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: doctl package for Fedora

[Kushal Das]

On 23/04/17, Dusty Mabe wrote:
> 
> 
> On 04/22/2017 10:31 AM, Dharmit Shah wrote:
> > Hi,
> 
> Hey Dharmit,
> 
> Thanks for working on this!
> 
> > 
> > After setting up gofed on my system, I did:
> > 
> > $ gofed repo2spec --detect https://github.com/digitalocean/doctl
> > --commit bb6a9630426adc1fed74f93df6f749deae6530aa
> > 
> > since that's the commit ID for latest version - 1.6.0.
> > 
> > After that I did:
> > 
> > $ gofed fetch --spec
> > 
> > to download the tarball.
> > 
> > Doing a local build or mockbuild is failing. In case of local build,
> > it's throwing [1] while for mockbuild I'm seeing this [2].
> 
> So there are two ways to build go packages in Fedora. One is to build
> from the source of a bunch of devel packages that have already been
> packaged up for Fedora. The other is to "bundle" all of that stuff and
> essentially provide the source for all of those deps within this
> package itself.
> 
> I believe it is preferable to build from the source of all the devel
> packages that are already a part of Fedora, but that is the long/hard
> approach because we have to package up the source files into devel
> rpms for all of them. It's not really hard to do this, and would be
> great if you did, but not required. An example of bundling the source
> code is here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1418368
> 
> If you want to bundle instead, an example is the kompose rpm here:
> 
> https://src.fedoraproject.org/cgit/rpms/kompose.git/tree/
> 

Also have a look at the gotun review [1], where I also started with the
gofed generated spec, and then changed for the dependencies as Jan
helped to do package the deps.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1386625

Kushal

> You can do a diff between kompose.spec and kompose.spec.orig to see
> what changes were made. Also, check out the notes.txt file.
> 
> > 
> > For both cases, it seems to me like missing Go dependencies are the
> > issue. How am I supposed to make these dependencies available?
> > 
> > Also, just want to know if I'm following the right steps. The specfile
> > generated by repo2spec command is intimidating!
> 
> It can be :). We'll help you through it!
> 
> > 
> > [1] 
> > https://paste.fedoraproject.org/paste/P-t~p-RmBzpVb8nl0avICF5M1UNdIGYhyRLivL9gydE=
> > [2] 
> > https://paste.fedoraproject.org/paste/WkcqyLNWkfuysR0OUpsrdl5M1UNdIGYhyRLivL9gydE=
> > 
> > Regards,
> > Dharmit.
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #264: 2WK Atomic Release Criteria

[Kushal Das]

kushal added a new comment to an issue you are following:
``
LGTM +1.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/264
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Updated Container Guidelines

[Kushal Das]

On 09/03/17, Honza Horak wrote:
> On 03/09/2017 05:40 PM, Adam Miller wrote:
> > On Thu, Feb 23, 2017 at 12:07 PM, Honza Horak  wrote:
> > > Hi Adam & co.,
> > > 
> > > I think the container guidelines should include a section about the 
> > > Layered
> > > Images used as a base for other Layered Builds. I've created an updated
> > > draft that also fixes label names to use the lower-case convention:
> > > 
> > > https://fedoraproject.org/wiki/User:Hhorak/Draft/Container:Review_Process
> > > 
> > > Is it possible to merge the changes? Or is there any process for it?
> > 
> > Sorry for the delayed response.
> > 
> > Absolutely 100% of those guidelines are open for continued
> > improvement. Please file an issue ticket in the atomic-wg[0] space and
> > mark it with the meeting tag so we can get some review from the
> > Working Group and then get changes merged.
> 
> I've just opened https://pagure.io/atomic-wg/issue/248 but it looks like I
> don't have permissions to set a tag, the only operation I'm allowed to do is
> changing status. So, please, set the meeting tag for me..

Done, thanks for the help :)


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

I am on leave today

[Kushal Das]

$SUBJECT

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[X-POST] Example of running gotun inside Taskotron

[Kushal Das]

Hi,

I have posted a blog[1] showing how can we run the gotun[2] tool inside of
Taskotron. Please let me know what do you think. Previously I have
posted[3] about how to run it inside Jenkins.

[1] https://kushaldas.in/posts/running-gotun-inside-taskotron.html
[2] https://gotun.readthedocs.io/
[3] https://kushaldas.in/posts/running-gotun-inside-jenkins.html

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[X-POST] Example of testing MariaDB layered image using gotun tool

[Kushal Das]

I just posted a blog [1] showcasing how we can use the gotun[2] tool to
test the MariaDB Fedora Layered image. Using a static binary like in
this example can help us not to worry about dependencies in the Atomic
host for tests.


[1] 
https://kushaldas.in/posts/testing-fedora-mariadb-layered-image-using-gotun.html
[2] https://gotun.readthedocs.io/en/latest/

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #232 `ssh issue on libvirt based images`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
> Kushal,  were you able to get the system logs from a failed image?
Nope, but I managed to get the tests working on the same boxes if we wait much 
longer time for the ssh to come back. 

So I pushed tunir-0.17.1 in production after testing on my servers, it has POLL 
directive, and we are polling for 300 seconds for the ssh service to come back.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
> I'd vote for images having a simple serial number - in the case where we have 
> to respin the cloud image because we changed the kickstart but not the tree, 
> we'd go from -1 to -2 or so.
> i.e.:
> Fedora-Atomic-25.20170130.0-1.x86_64.qcow2
> 
I like this one.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/229
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [atomic-devel] 2wk atomic release candidate: 20170228

[Kushal Das]

On 28/02/17, Dusty Mabe wrote:
> 
> We are going to attempt to release the 20170228 images
> that contain the fix for CVE-2017-6074. We'll try to
> release today (2/28) unless we get any negative feedback.
> Here is the new candidate:
> 
> The atomic images are here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/CloudImages/x86_64/images/
> 
> The ISO image is here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170228.0.iso
Alls tests passed on Fedora Infra Cloud.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Ownership of the Cloud Base Image

[Kushal Das]

On 08/02/17, Dusty Mabe wrote:
> 
> After some discussions with mattdm and sgallagh about the cloud base
> image and the server WG we have decided for now to leave the cloud
> base image out of the server WG. Obviously it doesn't make sense to
> have it stay as owned by the Atomic WG so here is what I would like to
> propose:
> 
> - Have the cloud base image owned by a CLOUD SIG
> - Mainly members of the old CLOUD WG that care about the cloud
>   base image, including me.
> - Create a new pagure issue tracker for the cloud sig.
This sounds good.

> 
> I had also toyed around with splitting out the atomic working group
> into a new mailing list atomic@fp.o and a new IRC channel #fedora-atomic 
> but I'm not sure if that is necessary. I think as long as we have a
> separation of ownership (mainly different issue trackers) then that
> should take care of some of the issues.
+1 to this idea too. We don't enough noise anyway to have separate
mailing lists and IRC channels.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #200 `Planning for interim container releases: To rebuild or not rebuild?`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
> 
> We should do what's needed to ensure that our images pick up the most recent 
> rpms -- when you say rebuild all content, do you mean rebuild the rpms 
> themselves, or rebuild all the images?
> 
> Sorry for lack of clarification, I meant "Rebuild all images" which would 
> pull in the latest stable rpms without requiring maintainer intervention.
I am +1 to this idea.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/200
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
+1 to stay with the current namespace.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/202
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Atomic Host: important updates in testing

[Kushal Das]

On 07/02/17, Dusty Mabe wrote:
> Hey team,
> 
> Right now some very critical pieces of Atomic Host have packages
> that are in testing. It would be great if we can get some people
> to take the updates-testing tree for a spin and report any issues.
> 
> 
> Here is a summary of what is in updates-testing vs what is in updates:
> 
> 
> Changed:
>   atomic 1.15.1-1.fc25 -> 1.15.2-1.fc25
>   docker 2:1.12.6-5.git037a2f5.fc25 -> 2:1.12.6-6.gitae7d637.fc25
>   docker-common 2:1.12.6-5.git037a2f5.fc25 -> 2:1.12.6-6.gitae7d637.fc25
>   etcd 3.0.15-1.fc25 -> 3.0.17-1.fc25
>   flannel 0.5.5-8.fc25 -> 0.7.0-2.fc25
>   gnutls 3.5.8-1.fc25 -> 3.5.8-2.fc25
>   gpgme 1.8.0-8.fc25 -> 1.8.0-10.fc25
>   kernel 4.9.6-200.fc25 -> 4.9.7-201.fc25
>   kernel-core 4.9.6-200.fc25 -> 4.9.7-201.fc25
>   kernel-modules 4.9.6-200.fc25 -> 4.9.7-201.fc25
>   openssh 7.4p1-1.fc25 -> 7.4p1-2.fc25
>   openssh-clients 7.4p1-1.fc25 -> 7.4p1-2.fc25
>   openssh-server 7.4p1-1.fc25 -> 7.4p1-2.fc25
>   openssl 1:1.0.2j-3.fc25 -> 1:1.0.2k-1.fc25
>   openssl-libs 1:1.0.2j-3.fc25 -> 1:1.0.2k-1.fc25
>   python3 3.5.2-4.fc25 -> 3.5.3-1.fc25
>   python3-libs 3.5.2-4.fc25 -> 3.5.3-1.fc25
>   runc 1:1.0.0-3.rc2.gitc91b5be.fc25 -> 1:1.0.0-5.rc2.gitc91b5be.fc25
>   screen 4.4.0-4.fc25 -> 4.5.0-1.fc25
>   socat 1.7.3.1-1.fc25 -> 1.7.3.2-1.fc25
>   system-python 3.5.2-4.fc25 -> 3.5.3-1.fc25
>   system-python-libs 3.5.2-4.fc25 -> 3.5.3-1.fc25
> Added:
>   criu-2.10-1.fc25.x86_64
>   libnet-1.1.6-11.fc24.x86_64
>   protobuf-c-1.2.1-1.fc25.x86_64
> 
> 
> To rebase to the updates-testing tree just run:
> 
> rpm-ostree rebase fedora-atomic/25/x86_64/testing/docker-host
> 
Ran our Fedora Atomic tests on the new tree. atomic command is failing
with the following error:

'NoneType' object is not subscriptable

# rpm-ostree rollback
and then tried the command again.

# atomic run kushaldas/busybox

This time it worked well (with atomic 1.14.1-1.fc25).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Testing Kubernetes on top of Fedora Atomic images

[Kushal Das]

Hi,

I have written a blog post [1] explaining how can we test Kubernetes on top
of Fedora Atomic images. Please have a look.

[1] 
https://kushaldas.in/posts/testing-kubernetes-on-fedora-atomic-using-gotun.html

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: tunir tests: what's this useradd-not-found failure?

[Kushal Das]

On 01/02/17, Matthew Miller wrote:
> I'm looking at https://apps.fedoraproject.org/autocloud/jobs/740, where
> there is a failure in the Fedora Cloud Base vagrant-libvirt image (yet
> vagrant-virtualbox and others are fine).
It was a non-gating test about auditd, which got automatically fixed. We
did not make any changes on the tests.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

I am on leave today

[Kushal Das]

Hi all,

I am on leave today. I will check emails in my afternoon time, and later
at night.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

No meeting today

[Kushal Das]

Hi all,

Most of the Working Group members are travelling for DevConf, so we are
cancelling our meeting today.

A few of us still chatting on the #fedora-cloud channel.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Atomic 2wk: Release Candidate

[Kushal Das]

On 24/01/17, Dusty Mabe wrote:
> 
> New build just finished with new kernel and new kubernetes versions that
> prevented us from releasing our 2wk release last week.
> 
> The vm images are here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/
> 
> The iso is here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170124.1.iso
> 
> 
> Please give these a sping and report any issues!
The qcow2 image passed through all of our Fedora Atomic tests on Fedora
Infra Openstack.

$ ./gotun --job fedora
Starts a new Tunir Job.

Server ID: f15923aa-a523-4f7e-a538-fdcc58924952
Let us wait for the server to be in running state.
Time to assign a floating pointip.
Polling for a successful ssh connection.

Polling for a successful ssh connection.

Polling for a successful ssh connection.

Polling for a successful ssh connection.

Polling for a successful ssh connection.

Polling for a successful ssh connection.

Executing:  curl -O 
http://infrastructure.fedoraproject.org/infra/autocloud/tunirtests.tar.gz
Executing:  tar -xzvf tunirtests.tar.gz
Executing:  ## sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtests -v
Executing:  ## sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtestBzip2 -v
Executing:  ## sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtestsCpio -v
Executing:  ## sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtestDiffutills -v
Executing:  ## sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtestaudit -v
Executing:  ## sudo python3 -m unittest tunirtests.selinux.TestSELinux -v
Executing:  ## sudo python3 -m unittest tunirtests.sshkeygentest.sshkeygenTest 
-v
Executing:  ## sudo python3 -m unittest 
tunirtests.testumountroot.TestUmountRoot -v
Executing:  sudo python3 -m unittest tunirtests.cloudtests.TestBase -v
Executing:  sudo python3 -m unittest tunirtests.cloudtests.TestCloudtmp -v
Executing:  sudo python3 -m unittest tunirtests.cloudtests.Testtmpmount -v
Executing:  sudo python3 -m unittest tunirtests.cloudtests.Testnetname -v
Executing:  ## python3 -m unittest tunirtests.cloudtests.TestJournalWritten -v
Executing:  sudo python3 -m unittest tunirtests.cloudservice.TestServiceStop -v
Executing:  sudo python3 -m unittest tunirtests.cloudservice.TestServiceDisable 
-v
Executing:  @@ sudo reboot
Sleeping for  30
Executing:  ## sudo python3 -m unittest tunirtests.testreboot.TestReboot -v
Executing:  sudo python3 -m unittest 
tunirtests.cloudservice.TestServiceManipulation -v
Executing:  ## python3 -m unittest 
tunirtests.cloudtests.TestJournalWrittenAfterReboot -v
Executing:  @@ sudo reboot
Sleeping for  30
Executing:  sudo python3 -m unittest tunirtests.cloudservice.TestServiceAfter -v
Executing:  sudo python3 -m unittest tunirtests.atomictests.TestDockerInstalled 
-v
Executing:  sudo python3 -m unittest 
tunirtests.atomictests.TestDockerStorageSetup -v
Executing:  sudo python3 -m unittest 
tunirtests.atomictests.TestAtomicFirstBootRun -v
Executing:  sudo python3 -m unittest tunirtests.atomictests.TestAtomicCommand -v
Executing:  sudo python3 -m unittest 
tunirtests.atomictests.TestAtomicDockerImage -v
Executing:  sudo python3 -m unittest tunirtests.atomictests.TestRootMount -v
Executing:  sudo python3 -m unittest tunirtests.atomictests.Testreadonlymount -v
Executing:  sudo python3 -m unittest tunirtests.atomictests.TestDockerDaemon -v

Result file at: /tmp/tunirresult_062736880


Job status: true


command: curl -O 
http://infrastructure.fedoraproject.org/infra/autocloud/tunirtests.tar.gz
status:true

  %!T(MISSING)otal%!R(MISSING)eceived %!X(MISSING)ferd  Average Speed   
TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100 12540  100 125400 0  23983  0 --:--:-- --:--:-- --:--:-- 23977


command: tar -xzvf tunirtests.tar.gz
status:true

tunirtests/
tunirtests/atomictests.py
tunirtests/cloudservice.py
tunirtests/cloudtests.py
tunirtests/__init__.py
tunirtests/loopbacktest.py
tunirtests/nongatingtests.py
tunirtests/selinux.py
tunirtests/sshkeygentest.py
tunirtests/testreboot.py
tunirtests/testumountroot.py
tunirtests/testutils.py
tunirtests/LICENSE


command: sudo python3 -m unittest tunirtests.nongatingtests.TunirNonGatingtests 
-v
status:true

test_bash (tunirtests.nongatingtests.TunirNonGatingtests)
Tests the bash version as the same of upstream ... ok

--
Ran 1 test in 0.002s

OK


command: sudo python3 -m unittest 
tunirtests.nongatingtests.TunirNonGatingtestBzip2 -v
status:true

test_bzip2 (tunirtests.nongatingtests.TunirNonGatingtestBzip2)
Test to run a file through bzip2,bzcat,bunzip2 ... ok

--
Ran 1 test in 0.011s

OK


command: sudo python3 

Re: Fedora Atomic 2wk: Release Candidate

[Kushal Das]

On 24/01/17, Dusty Mabe wrote:
> 
> New build just finished with new kernel and new kubernetes versions that
> prevented us from releasing our 2wk release last week.
> 
> The vm images are here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/
> 
> The iso is here:
> 
> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170124.1.iso
> 
> 
> Please give these a sping and report any issues!
Autocloud found the old ssh not available issue. Rest of the tests seems to be
working properly.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: About the recent failures of Atomic images on Autocloud

[Kushal Das]

On 19/01/17, Mike Ruckman wrote:
> On Thu, Jan 19, 2017 at 08:48:20AM -0800, Adam Williamson wrote:
> > 
> > Someone was actually asking me yesterday about a bug where they
> > couldn't ssh into a freshly-booted system for several minutes. Wonder
> > if it might possibly be the same thing...
> > -- 
> > Adam Williamson
> > Fedora QA Community Monkey
> > IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> > http://www.happyassassin.net
> 
> It was Kushal, iirc and it is the same issue.
It seems I created a cyclic graph through my question in different
mediums :)

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: About the recent failures of Atomic images on Autocloud

[Kushal Das]

On 09/01/17, Matthew Miller wrote:
> On Mon, Jan 09, 2017 at 10:16:51AM -0500, Dusty Mabe wrote:
> > > I finally managed to reproduce the error on a local box. After doing the
> > > reboot like in [1], the tool can not ssh back into the vm. When I tried
> > > the same on debug mode on, it still fails for some time, and then
> > > randomly allows to ssh again.
> > > I could not reproduce this using the same images over our OpenStack
> > > cloud. Any tips will be helpful to find the cause.
> > > 
> > Can we get together and debug this?
> 
> Is this a key-generation entropy problem?
Finally managed to isolate the issue. If we boot the image with only one
CPU, the error comes up. If we boot with 2 or more CPU(s), no issues at
all. Now the question is if we should  make local testing on Autocloud
with 2 CPU(s) or get this issue fixed somehow?

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: About the recent failures of Atomic images on Autocloud

[Kushal Das]

On 09/01/17, Matthew Miller wrote:
> On Mon, Jan 09, 2017 at 10:16:51AM -0500, Dusty Mabe wrote:
> > > I finally managed to reproduce the error on a local box. After doing the
> > > reboot like in [1], the tool can not ssh back into the vm. When I tried
> > > the same on debug mode on, it still fails for some time, and then
> > > randomly allows to ssh again.
> > > I could not reproduce this using the same images over our OpenStack
> > > cloud. Any tips will be helpful to find the cause.
> > > 
> > Can we get together and debug this?
> 
> Is this a key-generation entropy problem?
It can be an entropy problem, tried many things for the last few hours.
Nothing helped till now. Still looking.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

About the recent failures of Atomic images on Autocloud

[Kushal Das]

Hi,

I finally managed to reproduce the error on a local box. After doing the
reboot like in [1], the tool can not ssh back into the vm. When I tried
the same on debug mode on, it still fails for some time, and then
randomly allows to ssh again.

I could not reproduce this using the same images over our OpenStack
cloud. Any tips will be helpful to find the cause.

[1] https://apps.fedoraproject.org/autocloud/jobs/1845/output#264

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #185 `November 21 ISO is not bootable`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
It also passed the Automated tests in OpenQA 
https://openqa.fedoraproject.org/tests/overview?distri=fedora=Atomic=Fedora-Atomic-25-20161121.0=1
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
> can someone ( @kushal,  @sayanchowdhury , ?) be responsible for tracking down 
> the root cause of this and getting it fixed? This is becoming a pain and is 
> giving us bad information for releasing the next 2W release.

Yesterday I fixed both the new boxes and got fedmsg-hub enabled on them. We are 
going to remove the old production hardware and move these new boxes into 
production. So this test was done knowingly for yesterday (still today in your 
timezone). We will take the box out of fedmsg till we put them back as the 
production servers.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/182
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
@sayanchowdhury thanks for confirming. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/182
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
The VirtualBox backend failed to start the vms. It seems a version issue of 
VirtualBox, we upgraded the VirtualBox to latest, and manually tested that it 
is working. From tomorrow's compose we should not be having any issue. I am 
keeping the issue until we see everything work fine.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/182
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
Due to the restart of the fedmsg-hub the same builds were enqueued again. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/182
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: List of F26 features from Atomic Working Group

[Kushal Das]

On 28/11/16, Kushal Das wrote:
> Hi all.
> 
> It is time again to create the list of features we (Atomic Working
> Group) will be working on for Fedora 26. We want to discuss the
> features in this week's IRC meeting. But first everyone should put up
> the ideas to this thread. This will help us to create a proper agenda
> for Wednesday's meeting.
The wiki page to put up all the ideas is at [1].

[1] https://fedoraproject.org/wiki/Fedora_26_Change_Proposals_Atomic_WG


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Please to put any future Atomic/Cloud docs for the users

[Kushal Das]

Hi all,

As mentioned before we have [1] up and running as our user docs. If
anyone of you wish to write any new document, or think of any old one,
please submit a pull request to the repository [2]. As we are using
sphinx, and readthedocs, after the pull request is merged, it will
automatically show up in the website [1].

I just started writing a wiki page [3] so that we can point people where
to look for existing documentation (as discussed in the meeting
yesterday). Please update the wiki page as required.


[1] http://fedoracloud.readthedocs.io/en/latest/
[2] https://github.com/fedora-cloud/fedoracloud
[3] https://fedoraproject.org/wiki/Atomic_WG_docs


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

List of F26 features from Atomic Working Group

[Kushal Das]

Hi all.

It is time again to create the list of features we (Atomic Working
Group) will be working on for Fedora 26. We want to discuss the
features in this week's IRC meeting. But first everyone should put up
the ideas to this thread. This will help us to create a proper agenda
for Wednesday's meeting.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
Somehow I want to shout "networkd" "networkd" :)
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/174
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #177 `Disable interactive "cp" in fedora base image`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
+1 from me.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/177
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Meeting minutes from 2016-11-09

[Kushal Das]

==
#fedora-meeting-1: Fedora Atomic Working Group
==


Meeting started by kushal at 17:01:59 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-09/fedora_atomic_working_group.2016-11-09-17.01.log.html
.



Meeting summary
---
* Roll call  (kushal, 17:02:11)

* https://pagure.io/atomic-wg/issue/158 website change for atomic
  (kushal, 17:08:30)
  * LINK: https://stg.getfedora.org/en/cloud/   (kushal, 17:10:59)

* Open Floor  (kushal, 17:16:11)
  * ACTION: jbrooks to file issue on kube situation w/ f25 atomic
(jbrooks, 17:27:41)
  * LINK:

https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/2VY5QFBU5KXXBEGCNIYQDSZXEHDILPEG/
(dustymabe, 17:36:55)

Meeting ended at 17:40:45 UTC.




Action Items

* jbrooks to file issue on kube situation w/ f25 atomic




Action Items, by person
---
* jbrooks
  * jbrooks to file issue on kube situation w/ f25 atomic
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (58)
* dustymabe (34)
* jbrooks (34)
* zodbot (15)
* bowlofeggs (5)
* maxamillion (5)
* walters (4)
* sayan (3)
* trishnag (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Python is missing in Fedora AWS AMIs

[Kushal Das]

On 08/11/16, Danishka Navin wrote:
> Hi team,
> 
> Is there any specific reason to drop python from Fedora AMIs in AWS?
> 
Standard Fedora Cloud images are Python3 only as we moved to Python3 as
default. Only the Atomic images have Python2 as we can not install new
packages on it (and Python2 is required for ansible).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Where is Kushal Das for the rest of the week?

[Kushal Das]

Hi all,

Today, and tomorrow are holidays in India. On Wednesday I will be
travelling to Cambodia for FUDCon APAC. I will be back home on Monday
evening. I am hoping to have a working internet connection during the
conference.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
The following bug seems to be the problem.

https://bugzilla.redhat.com/show_bug.cgi?id=1212082#c21
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/175
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

[Kushal Das]

kushal added a new comment to an issue you are following:
``
Note: strangely the vagrant libvirt is also failing for me with ssh issues.

http://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20161025.0/compose/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-24-20161025.0.x86_64.vagrant-libvirt.box
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/175
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`

[Kushal Das]

kushal reported a new issue against the project: `atomic-wg` that you are 
following:
``
Even though autocloud managed to ssh, when I tried to ssh into an instance on 
our OpenStack, it never allowed a connection. Opening this ticket to dig more 
into this.

* https://apps.fedoraproject.org/autocloud/jobs/1016/output
* 
http://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20161025.0/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20161025.0.x86_64.qcow2


``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/175
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Join Us for a Fedora 25 Test Day Next Week (October 24, 2016)

[Kushal Das]

On 19/10/16, Jason Brooks wrote:
> Want to help make Fedora Atomic Host even better? Join us next week
> for the Fedora Cloud Test Day, where we’ll be banging on the Atomic
> Host image for Fedora. As always, we’re looking for many hands to help
> put the release through its paces.
> 
> To participate, you’ll need a system with Vagrant, libvirt/KVM, or
> access to OpenStack or another IaaS that can consume the qcow or raw
> images for Atomic. Alternately, if you have an Amazon Web Services
> account, there will be AMIs you can test; check the wiki page for
> links on the test day.
> 
> Grab the image from the wiki [0], and then check out the test results
> page [1] to see the tests you should run and report the results.
> 
> [0] https://fedoraproject.org/w/index.php?title=Test_Day:2016_10_24_Cloud
> [1] http://testdays.fedorainfracloud.org/events/11
> 
I have updated the testdays event page along with the test details. Only
missing information for now is the list of AMI(s) for Atomic, which
sayan will fill up soon.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Enabling the atomic-wg pagure instance

[Kushal Das]

Hi,

It is 2AM here in India, and I finally managed to import our cloud trac
into pagure at [1] :) Feel free to update the tickets as you want.

I will enable fedmsg, and email notification to the list in the morning.
We will also have redirects from any old issue URL from the trac.
Patrick will help us for the same.

[1] https://pagure.io/atomic-wg/issues

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

A stage Pagure instance of our trac issues

[Kushal Das]

Hi all,

As discussed over the list, I have a stage setup for our trac tickets
moved into Pagure [1]. Please have a look.

When we will move into the production pagure, all of us (who ever
commented on a trac ticket ever) will get a flood of fedmsg(s) :)
I will require a permission to do that amount of flooding :)

[1] https://stg.pagure.io/atomic-wg/issues

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Cloud and Server Q

[Kushal Das]

On 30/09/16, Josh Berkus wrote:
> On 09/30/2016 02:01 PM, Josh Boyer wrote:
> 
> > 16:44:56  Cloud base image is the only blocking deliverable.
> > 16:44:59  Atomic is not.
> > 
> > I realize this WG is in the middle of rebooting itself, but to have
> > clearly conflicting information from the WG members is a bit
> > concerning.
> 
Atomic host image is the deliverable for the Atomic WG, which is under 2
week release cycle. We sync up with the official release version at the
time of GA, but we continue to be in our 2 week atomic release cycle
then on the 6month old GA. This is my understanding about all the work
done for 2 Week Atomic.

Now I may be completely wrong to understand our 2 week release cycle
process, but this is what I followed for the release-infra work till
now.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Request for review of blocking deliverables for Fedora 25

[Kushal Das]

On 16/09/16, Jan Kurik wrote:
> On Fri, Sep 16, 2016 at 2:27 PM, Colin Walters  wrote:
> >
> >
> > On Fri, Sep 16, 2016, at 04:14 AM, Jan Kurik wrote:
> >> Hi,
> >>
> >> may I request any feedback on this topic, and/or adding this topic to
> >> the next Cloud WG meeting agenda ?
> >
> > It'd be nice to make Atomic Host a blocking deliverable - I think
> > we have sufficient experience now and manpower to do that.
> 
> How this should work ? I am asking because Atomic is delivered
> bi-weekly and Fedora releases are delivered two times a year. Perhaps
> delivering the last released Atomic build before Fedora release GA
> date might work. Any other/better ideas how this should be
> synchronized ?
This is my understanding too. We sync up Atomic host with the latest
released Fedora GA, and then follow on our normal 2-week release cycle.
This does not make the 2 week atomic into the official 6month old
release cycle story.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora 25 atomic images?

[Kushal Das]

On 03/10/16, Kushal Das wrote:
> On 01/10/16, Matthew Miller wrote:
> > I see Fedora Rawhide, just Fedora (cloud base, I assume) 25, and Fedora
> > Atomic 24 in https://apps.fedoraproject.org/autocloud/compose?limit=20.
> > Shouldn't there also be an Atomic 25 branch by now? (Shouldn't there be
> > one starting with branching, for that matter?) Or am I just missing it?
> > 
> Last we heard that rpm-ostree based composes were broken (as informed in
> the rel-eng list).
> 
I can see latest builds in autocloud today. Only the F25 base qcow2
passed the tests, rest never booted. I manually verified the same by
trying to boot the base vagrant-libvirt image on my system.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora 25 atomic images?

[Kushal Das]

On 01/10/16, Matthew Miller wrote:
> I see Fedora Rawhide, just Fedora (cloud base, I assume) 25, and Fedora
> Atomic 24 in https://apps.fedoraproject.org/autocloud/compose?limit=20.
> Shouldn't there also be an Atomic 25 branch by now? (Shouldn't there be
> one starting with branching, for that matter?) Or am I just missing it?
> 
Last we heard that rpm-ostree based composes were broken (as informed in
the rel-eng list).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Request for review of blocking deliverables for Fedora 25

[Kushal Das]

On 07/09/16, Jan Kurik wrote:
> Hi Cloud/Atomic WG,
> 
> I would like to request review of the WG deliverables for Fedora 25
> release. The list of deliverables is available on wiki:
> https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fedora25#Cloud
> Please let me know, or edit the wiki page, in case there are missing
> deliverables or the current ones have wrong blocking status.
> 
> There is going to be overall review done by FESCo, probably on
> 2016-Sep-30 for all the blocking deliverables.
> 
I thought I already replied to this mail but seems like I am wrong :( As
I mentioned in the meeting last night, for F25 the current release
blocking list looks good for Cloud. Only the base image is blocking for
now.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Current Fedora 25 Atomic images are failing to boot

[Kushal Das]

Hi all,

The current F25 Atomic images are failing to boot[1], I never managed to reach
dracut emergency shell in my local box.

Can anyone else also please have a look?

[1] https://apps.fedoraproject.org/autocloud/jobs/704/output

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: overlayfs for AFTER Fedora 25

[Kushal Das]

On 14/09/16, Adam Miller wrote:
> On Wed, Sep 14, 2016 at 2:14 PM, Dusty Mabe  wrote:
> >
> > 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?
> 
> Seems a little conservative, but I'm not opposed.
> 
> I've been under the impression that part of the point of the Two Week
> Release cycle was to be able to deliver new stuff faster and fix
> issues faster but playing it safe isn't inherently a bad approach
> either.
For two week atomic we are not tied with the Fedora 25 release cycle. We
can enable it in our release when we think it is ready for the
consumers. It does not have to wait F26 release. For example we see it
is in good condition after one week of F25 release, we can then enable
it default in the next 2WA release.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Why do we have an older version number for today's atomic compose? compose?

[Kushal Das]

On 06/09/16, Micah Abbott wrote:
 
> It looks like the ostree composes had the version numbering reset on July
> 20.
> 
> # ostree pull --commit-metadata-only --depth=-1
> fedora-atomic:fedora-atomic/24/x86_64/docker-host
> 
> 68 metadata, 0 content objects fetched; 7 KiB transferred in 32 seconds
> 
> # ostree log fedora-atomic/24/x86_64/docker-host
> commit 5832e43bcf2054a46169442557d4348d38e280161955c4bcd83b19db6649a5df
> Date:  2016-09-05 01:23:02 +
> Version: 24.35
> (no subject)
> 
> ...
> 
> commit 076c89f879b14c24b5912c0daa389e1e8e227bc2456d4a59fe1619f5bd2c9202
> Date:  2016-07-20 17:21:21 +
> Version: 24
> (no subject)
> 
> 
> maxamillion was looking at this around mid-August and noticed something
> similar:
> 
> Aug 15 15:14:00   maxamillion: it looks like the version string
> got reset on 2016-07-20 to just '24'
> ...
> Aug 15 15:15:38   the unfortunate side effect of whatever happened
> on that day is that all the previous commit history is gone
> Aug 15 15:16:20yeah, Fedora RelEng changed a bunch of the
> compose stuff on that day ... it's had some side effects
> Aug 15 15:17:06   well, that's better than not knowing why it
> happened
> Aug 15 15:17:27yeah, it wasn't just Atomic Host impacted
> ... number of things were
Thanks for the detailed information.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Fedora 25 atomic images are stuck while booting

[Kushal Das]

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
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Discussion on changing the name of Working Group

[Kushal Das]

On 25/08/16, Dusty Mabe wrote:
> 
> 
> On 08/25/2016 02:51 PM, Jason Brooks wrote:
> > On Thu, Aug 25, 2016 at 11:43 AM, Dusty Mabe  wrote:
> >>
> >> Others have made some good comments in this thread. I'm really not as
> >> concerned with these specific questions.
> >>
> >> I think the deeper problem is that there needs to be (I think) a person
> >> who is clearly identified to lead this effort (and ultimately this group).
> >> I think a lot of times it is hard for contributors to make meaningful
> >> contributions because the group is scattered and there is not really any
> >> one person to ask for a definitive answer on things. Sometimes a user will
> >> get a response back to a question/request/contribution, and sometimes not.
> >> I'm not saying we need one person to do all of the work, or to even be
> >> the expert in every area, but one person to at least know who is 
> >> responsible
> >> for each part and to track down when things don't get done.
> >>
> >> As a group we haven't been very thorough and that has led to some
> >> serious issues with some of our shipped bits at times. To be honest I
> >> think we just need some dedicated leadership. Someone who crosses the
> >> Ts and dots the Is and greases the skids so that it is easy to on-board
> >> and make contributions. Hopefully this would lead to increased contribution
> >> activity and a more vibrant community.
> > 
> > This is sort of what I've been doing w/ CentOS Atomic, and I can do
> > the same w/ Fedora Atomic -- there's a lot of overlap.
> > 
> 
> You've done an amazing job with CentOS Atomic. I think the best approach 
> would actually be to have an additional "leader" person that worked hand in
> hand with you as the CentOS lead. If we can't get an additional person 
> then I would certainly support you in that role for Fedora, but I
> would hope to not overload you too much.
I am also willing to volunteer for this. As the base image is moving to
server wg, and my work related to rel-eng testing side is stable, I can
refocus myself to the Fedora Atomic host in the same way I was doing
base image. Last few months were about jumping into too many things. I
hope that I will be helpful in this case.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Discussion on changing the name of Working Group

[Kushal Das]

Hi all,

During Flock PRD discussion, a proposal was put up about changing the
name of the WG to Atomic. We have few open questions from last week's meeting. I
will try to put those down here, if anyone wants to add to that list, or
explain things better, please go ahead and reply to the thread :)

* If we rename how to make sure that the users know that we are not
  abandoning the cloud?

* If we create a new group, then who else are still interested about
  helping out the Cloud WG?

* We will require new user stories related to Atomic. This also brings
 in the question about old user stories in current PRD. They are still
 mostly valid. PRD updation is surely one major point towards Atomic WG.

* Who will maintain Atomic workstation? If it is workstation wg, then
  how to reduce duplication of efforts?

* What will happen to the Cloud Base image?

* Who will maintain the Vagrant images?

* What will happen to our effort to push Fedora to different public
  cloud services? We have AMI(s) right now, we also push to Digital
  Ocean.



Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Will be missing tonight's meeting

[Kushal Das]

Hi,

I will be missing tonight's meeting. Sorry for informing late.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

About finding the source of binaries in any image

[Kushal Das]

Hi,

I was thinking about a test to find the source of all of binaries in an
image (cloud/atomic). One person was working on a patch, but I need more
eyes on the PR[1], and provide him more ideas. May be verifying all the
rpms are signed or not can be another test in the same front.


[1] https://github.com/kushaldas/tunirtests/pull/43

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Update about Autocloud deployment

[Kushal Das]

Hi all,

Below are the notes about Autocloud update happened last week. There
were few things which went bad, few points worked well. I am trying to
list them here, and how do we plan to make sure that the bad things
never happen again. I am ccing patrick in this mail as he was the
contact point from fedora infrastructure (read: he did all the work).

## deployment using ansible to the newly installed systems

We only had to change yum to dnf, and also had to remove the old hotfix
part from the roles. The current playbooks, roles seems to be stable,
and can help us in the future too.

## fedmsg-hub on the backends double enqueue

We had to restart fedmsg-hubs few times in the backends servers. In
between we also found that fedmsg-hub service was happily enqueueing the
jobs twice (for each compose), and then it got fixed automagically,
nothing was changed in our configuration or in code.

We are still not sure why this happened, but we are trying to dig more
on this.

## fedmsg-hub broke due to a faulty dependency

Even though we kept our code up and running for weeks, after the
production deployment we found one of the dependency (fedfind, adamw is
the upstream author) was broken with the fedora atomic image names, and
causing our fedmsg-hub instances go crazy. We have informed upstream,
and got a quick hotfix deployment in few hours after finding the issue.

For the next release we will make sure if keep it running for longer on
our internal hardware with messages from production fedmsg. This
dependency failure was something we should have caught, but could not.

## missing fedmsg(s) from autocloud on completing the testing of a compose

Now this was a known part of the whole development+release cycle. Sayan had
submitted the patch [1], but there was some slight miscommunication. In my part
i missed to track the state of this dependency. 

For the next release, i will make a release/deployment checklist for
autocloud, and get it validated from everyone involved. Most probably we
will add too many minor details to this checklist, but that will help us
to keep things in track about any future deployment. sayan is currently
working to get that particular change in production so that we can send
out fedmsg(s) as required by adam.

## missing package dependency causing missing bridge on libvirt backend

We also found that a missing link in the dependency chain caused a
missing virtual bridge in the libvirt backend. Patrick helped to find
that adding libvirt as dependency for that particular box will fix the
issue in future.

We should test on clean installations while developing next time to make
sure this is not repeated. Plus we should think about getting better on
the stage environment.

## the new webfrontend is better

Sayan did a good job in making the new webfrontend. We can now point out
to the exact failures [2].

In future we should try to get more input about the features of the
webfrontend. Even though the whole service is made for automation, but
this frontend helps us to find, and point to the right issues found in
the tests.

## autocloud+tunir did what they are supposed to do

After fixing the hiccups, the autocloud service is doing what it
supposed to do, testing the images. We will push our effort in having
better test coverage in the coming months to take the advantage from
this new deployment.


Please comment/suggest whatever you think about the work. This will help
us to improve in the future releases.

[1]
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/386
[2] https://apps.fedoraproject.org/autocloud/jobs/66/output#290

kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Canceling today's Cloud WG meeting

[Kushal Das]

Hi all,

Many of our regular attendees are in RH Summit this week. I think it
will be wise to cancel today's Cloud WG meeting, we will meet again next
week. Mean while if you want to discuss something, feel free to start a
new thread in the list.


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: No Fedora 24 container?

[Kushal Das]

On 14/06/16, Josh Berkus wrote:
> https://hub.docker.com/_/fedora/
>
> This seems like a big loss, especially for getting folks to test Fedora 24.
> 
We push there only after GA. You can see the latest nightly build at
[1].

[1]
https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-/compose/Docker/x86_64/images/

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Fedora-Atomic-24-20160614.n.0.x86_64.qcow2 passed all tests

[Kushal Das]

Hi all,

Manually fired up Fedora Cloud/Atomic tests against the
Fedora-Atomic-24-20160614.n.0.x86_64.qcow2  image from [1]. It passed
all the tests successfully.

Note: I will run the same tests against the RC builds later at night.

[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=14484560

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Strange behavior of rpm command in nightly Atommic F23 image

[Kushal Das]

Hi,

rpm command is showing no packages are installed in the latest nightly
build of F23 Atomic image [1]. It is same for the Vagrant box images
[2]. I am not being able to find out the exact cause of this. If anyone
has time to look into this matter, please do so, or let me know I missed
any discussion on the same.

# ostree admin status
* fedora-atomic 
3d28675ce8980f0e0df86ea2c7969388bfaca0858ac9b8e5f08e6559242b6979.0
Version: 23.135
origin refspec: fedora-atomic:fedora-atomic/f23/x86_64/docker-host

[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=14468600
[2] http://koji.fedoraproject.org/koji/taskinfo?taskID=14468602


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Will not be attending the meeting tomorrow

[Kushal Das]

Hi,

I will be travelling to PyCon tomorrow, so I will be missing the cloud
wg meeting.


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Fedora-Atomic-24-20160523.n.0.x86_64.qcow2 passes all tests

[Kushal Das]

Hi all,

Tested Fedora-Atomic-24-20160523.n.0.x86_64.qcow2 [1] today on
Openstack, it passed all the defined tests in tunirtests repo. Good work
everyone on getting the bugs fixed.

[1]
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-24-20160523.n.0/compose/CloudImages/x86_64/images/Fedora-Atomic-24-20160523.n.0.x86_64.qcow2

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Resigning from Cloud WG

[Kushal Das]

On 17/05/16, Haïkel wrote:
> Hello,
> 
> It pains me to admit it but I had no time for the WG for a while and
> it's unlikely to change in the near-future.
> So according our charter, I'm resigning from my seat.
> 
> Thank you for all the time spent together and I wish you all the best.
> 
Thanks for all the help, please do come back when you find time :)

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

[X-POST] Fedora 24 Cloud/Atomic test day tomorrow

[Kushal Das]

Hi all,

As we discussed in the weekly meeting, we are organizing a test day for
Fedora Cloud/Atomic images tomorrow. [1] is the event page, more details
about individual tests can be found at [2].

Please find some time in the to test one or more features, and submit
back the results to the testdays application.

Happy testing :)

[1]
https://fedoraproject.org/w/index.php?title=Test_Day:2016_05_10_Cloud
[2] http://testdays.fedorainfracloud.org/events/7

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Our FAD has been approved

[Kushal Das]

On 05/05/16, Josh Berkus wrote:
> ... so get your travel now, if you haven't already.
> 
Great news, thank you once again :)

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora-Cloud-Base 24 docker isn't included?

[Kushal Das]

On 25/04/16, Chris Murphy wrote:
> Fedora-Cloud-Base-24-20160424.n.0.x86_64.qcow2
> 
> - Docker isn't installed.  I can install it, but docker-storage-setup
> won't setup a volume group with a thin pool if it's on a non-boot
> drive apparently? Are both of these expected? (I normally use cloud
> atomic which pretty much works out of the box, so this could be a user
> misunderstanding of cloud base behavior).
> 
Docker is not part of the cloud base image.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: ATTN: Beta Blocker - docker is broken running F-24 on F-24

[Kushal Das]

On 22/04/16, Peter Robinson wrote:
> >> > So heads up because I'm not sure we want docker broken again at GA for 
> >> > F-24.
> >> >
> >> > https://bugzilla.redhat.com/show_bug.cgi?id=1322909
> >> >
> >> > The bug has been open since end of March and is on x86 and it appears
> >> > F-24 docker binaries are broken so F-24 (and likely other) images
> >> > don't work on F-24.
> >> >
> >> > I'm not sure how the cloud SIG tests docker deliverables but now might
> >> > be a good time to move to F-24 on the host.
> >> We have docker related tests enabled but only on Atomic images. As we do
> >> not have F24 based atomic images, this error never showed up to us.
> > My mistake, autocloud is picking the only base images from F24/rawhide,
> > but not the atomic images, that is why we never saw this error. In the
> > coming days we are moving to compose based testing, I hope that will fix
> > this issue.
> 
> Please make sure it's been tested by the time we hit Beta RCs so the
> blocker can be properly tested and verified.
Yes, working on a hotfix. In the coming days autocloud will also move to
compose based testing than koji build based (the current model).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: ATTN: Beta Blocker - docker is broken running F-24 on F-24

[Kushal Das]

On 22/04/16, Kushal Das wrote:
> On 21/04/16, Peter Robinson wrote:
> > So heads up because I'm not sure we want docker broken again at GA for F-24.
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1322909
> > 
> > The bug has been open since end of March and is on x86 and it appears
> > F-24 docker binaries are broken so F-24 (and likely other) images
> > don't work on F-24.
> > 
> > I'm not sure how the cloud SIG tests docker deliverables but now might
> > be a good time to move to F-24 on the host.
> We have docker related tests enabled but only on Atomic images. As we do
> not have F24 based atomic images, this error never showed up to us.
My mistake, autocloud is picking the only base images from F24/rawhide,
but not the atomic images, that is why we never saw this error. In the
coming days we are moving to compose based testing, I hope that will fix
this issue.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: 2-week build broken again?

[Kushal Das]

On 20/04/16, Josh Berkus wrote:
> According to the downloads page:
> 
> "The latest two week build did not meet our testing criteria. The images
> available are from over 14 days ago. Check the Project Atomic blog for
> updates and information about Atomic blocker bugs."
> 
> Can someone let me know what's going on?
> 
The release announcement happened after you sent out this email :)

https://getfedora.org/en/cloud/download/atomic.html says last release
was 0 days ago :D

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: New meeting time

[Kushal Das]

On 28/03/16, Joe Brockmeier wrote:
> On 03/28/2016 02:19 PM, Kushal Das wrote:
> > This is still the best time for me.
> 
> It's OK for me, but not optimal. Kushal, are you sure the time is the
> best? It seems to be kinda late for you.
Still better than any other time. Other days are totally full in my
calendar :(

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Will be absent for the meeting tonight

[Kushal Das]

Hi,

I am still packing for super early morning trip. Will miss the meeting
tonight. See you all next week.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Retiring 32-bit images

[Kushal Das]

On 23/03/16, Dusty Mabe wrote:
> 
> 
 
> I don't know if it was every properly communicated to the public, but
> I definitely don't want to see 32 bit images any longer.

Yes, we are supposed to drop the 32 bit images as decided during Flock,
how can we go ahead and do this?

> Did we ever put a post up on fedmag about this? Can we do one now?
No iirc. We may want to do one.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: New meeting time

[Kushal Das]

On 24/03/16, Dusty Mabe wrote:
> It seems as if people are overbooked at the current meeting time (17:00 UTC). 
> Shall we 
> try to find an alternative? 
> 
This is still the best time for me.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Please help test Fedora 24 Alpha candidate 7 (RC)

[Kushal Das]

On 22/03/16, Dusty Mabe wrote:
> 
> 
> On 03/22/2016 09:14 PM, Adam Williamson wrote:
> > Hi folks! We have a new Fedora 24 Alpha candidate compose (like an 'RC'
> > in earlier cycles) and go/no-go is tomorrow, so if you could please
> > help test it, that would be great!
> > 
> > The Cloud validation test page is here:
> > 
> > https://fedoraproject.org/wiki/Test_Results:Fedora_24_Alpha_1.7_Cloud
> > 
> > and has download links. You can enter your results by editing the
> > results tables directly (please follow the instructions on the page for
> > that) or using the 'relval' tool - 'dnf --enablerepo=updates-testing
> > install relval', 'relval report-results'.
> > 
> > One question I'm afraid I can't answer is "how do we do EC2 testing?" -
> > I don't know when/if/how the candidate composes get published on EC2.
> > dgilmore may be able to enlighten us there. If not, it'd be great if at
> > least local and Openstack tests could be done.
> > 
> > The only tests we absolutely *need* doing for Alpha are the two marked
> > 'Alpha' in the Milestone column, but it's great to do the Final tests
> > as well if possible. The i386 tests I don't think anyone cares about
> > any more (I have an action item to ditch i386 stuff from the test pages
> > but didn't do it yet), and we don't have Atomic images for this
> > compose.
> 
> Thanks Adam, A few of us tested all criteria and things look pretty
> good I would say so far. Please more people join in! 
> 
> I no longer have a local openstack setup so I wasn't able to test on
> that front.
> 
I have tested both locally and on Openstack. All tests passed nicely :)
I have updated the wiki page.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora MOTD status

[Kushal Das]

On 10/03/16, Dusty Mabe wrote:
> 
> 
> On 03/10/2016 07:01 AM, Ratnadeep Debnath wrote:
> > Hi all,
> > 
> > fedora-motd-0.1.1-1 package has been pushed to "updates-testing" repo
> > today, with some fixes, on top of fedora-motd-0.1-1.
> > 
> > I built a f23 cloud base vagrant image after patching fedora-motd
> > related changes[1] on top of fedora-cloud-base kickstart file, with
> > "updates-testing" repo enabled (for now), and things seemed to work
> > properly.
> > 
> > I also created patches for:
> > - configuring fedora-motd on fedora-cloud-atomic image [2]
> > - adding fedora-motd in fedora-atomic's ostree[3]
> > 
> > I need help with updating the ostree for fedora-cloud-atomic and
> > building an image for fedora-cloud-atomic with fedora-motd enabled.
> 
> Kushal, can you see this through? I know Ian and I are travelling/meetings
> all next week.
> 
I will try to do this next week. I am also travelling to Singapore and
attending/organizing a conference there :(

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

State of tests

[Kushal Das]

Hi all,

I also posted a blog post with the same text. I was supposed to update
the list with the state of tests last week, but wanted to write that up
only after making all changes live.

Till Fedora 22 release we have tested our Cloud images only with manual help.
The amazing Fedora QA team organized test days, and also published [detailed
documentation](https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test)
on the wiki about how to test the images. People tried to help as when
possible, as not having access to a Cloud was a problem for many. The images
are also big in size (than any random RPM), so that also meant only people with
enough bandwidth can help.

During Fedora 23 release cycle, we worked on a change for [Automated Two Week
Atomic release](https://fedoraproject.org/wiki/Changes/Two_Week_Atomic). A part
of it was about having automated testing, which we enabled using
[Autocloud](https://apps.fedoraproject.org/autocloud/jobs/) project. This
automatically tests every Cloud Base and Atomic qcow2 images, and libvirt, and
Virtualbox based Vagrant images.

This post will explain the state of [currently activated
tests](https://github.com/kushaldas/tunirtests/wiki#currently-activated-tests)
for the same. These tests are written as Python3 unittest cases.

At first we run 5 non-gating tests, failing any of these will not do a release
blocking, but at the end of each run we get the summary for all of these
non-gating tests. These include bzip2, cpio, diffutils, Audit.

Then we go ahead in testing the basics test cases, things like journald
logging, package install (only on base image), SELinux should be enforcing, and
no service should fail during startup of the image.

The next test is about checking that /tmp should be world writable. We then
move into testing the mount status of the /tmp filesystem. If it is a link,
then also it should behave properly. Our next test checks that for Vagrant
images we are using predictable naming convention of network devices, basically
checking the existing of *eth0*.

We then disable *crond* service, after a reboot we make sure that the service
is still in disabled state, and do the rest of service manipulations. We also
check that the user journald log file exists on that reboot, this comes from a
regression test. Then we reboot the instance again.

After this second reboot, we test the status of the *crond* service once again,
and then we move to our special tests cases related to Atomic host. Means these
tests will run only on Atomic hosts (both cloud, and Vagrant ones).

In the first test we check if the package *docker* is at all installed or not.
Yes, if you guessed that this is a regression test, then you are correct. We
once had an image without the docker package inside :) Next, we test the docker
storage setup, that should be up, and in running state. We then run the busybox
image, and see that it should be able to run properly. The *atomic* command is
used next to start the same container. Pulling in the latest *Fedora* image,
and running it is the next test. As our next test, we try to mount */* as
*/host* in the container. The next test is about having */bin*, */sbin*, and
*/usr* mounted as read only in the Atomic host. In our final test, we check
that a privileged container should be able to talk to the host docker daemon.

We also have a [github wiki
page](https://github.com/kushaldas/tunirtests/wiki/How-to-write-a-new-test-case)
explaining how to write any new test case. Feel free to ping if you want to
contribute, and make Fedora flying high in the Cloud.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

[urgent] Review container packager guidelines

[Kushal Das]

Hi all,

Around 6 weeks back Adam created a new trac ticket [1] about the
container "Packager" guidelines. It is related to the work for layered
image build process [2].

We need more eyes to review the proposals, and please update the trac
ticket with your input.

[1] https://fedorahosted.org/cloud/ticket/148
[2]
https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Kushal Das]

On 23/02/16, Dusty Mabe wrote:
> 
> 
 
> 
> I'm having issues downloading this from the mirrors (404). Considering it has 
> been 
> many hours since you have sent the announcement should I assume it is an issue
> that needs to be fixed?
> 
The images got synced to mirrors automatically. I guess they just took
more time. Works now very well.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

[Kushal Das]

On 23/02/16, Dusty Mabe wrote:
> 
> 
 
> 
> I'm having issues downloading this from the mirrors (404). Considering it has 
> been 
> many hours since you have sent the announcement should I assume it is an issue
> that needs to be fixed?
> 
Yes, the final image name is wrong. It is
"Fedora-Cloud-Atomic-23-20160127.2.x86_64.qcow2" where as the URL points
to "Fedora-Cloud-Atomic-23-20160223.x86_64.qcow2".

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Meeting log from 2016-01-13

[Kushal Das]

==
#fedora-meeting-1: Fedora Cloud WG
==


Meeting started by kushal at 17:01:46 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2016-01-13/fedora_cloud_wg.2016-01-13-17.01.log.html
.



Meeting summary
---
* Roll Call  (kushal, 17:01:55)

* Action items from last meeting  (kushal, 17:03:44)

* Fedora Cloud FAD (late 2015/early 2016)
  https://fedorahosted.org/cloud/ticket/115  (kushal, 17:05:44)
  * ACTION: dustymabe to update #115 after talking to mhayden  (kushal,
17:08:08)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (kushal, 17:08:50)
  * ACTION: kushal to work on https://fedorahosted.org/cloud/ticket/136
(kushal, 17:10:06)

* Produce updated cloud base images
  https://fedorahosted.org/cloud/ticket/138  (kushal, 17:12:37)

* Producing 2 week atomic images
  https://fedorahosted.org/cloud/ticket/139  (kushal, 17:14:10)

* Proposals for F24 features https://fedorahosted.org/cloud/ticket/143
  (kushal, 17:16:50)
  * LINK: https://fedoraproject.org/wiki/Releases/24/Schedule   (kushal,
17:22:16)

* AMI lifetimes (Cloud WG members vote needed)
  https://fedorahosted.org/cloud/ticket/99  (kushal, 17:23:08)

* Create and host a Fedora 23 Cloud image supporting all languages
  https://fedorahosted.org/cloud/ticket/146  (kushal, 17:26:58)
  * LINK: http://tinyurl.com/live-respins (redirects to
alt.fp.o./live-respins  (linuxmodder, 17:33:38)
  * ACTION: kushal will build an unofficial image with all lang packs
for #146  (kushal, 17:39:13)

* Don't overwrite download location for 2 week atomic images
  https://fedorahosted.org/cloud/ticket/147  (kushal, 17:39:20)

* Container "Packager" Guildelines and Naming Conventions
  https://fedorahosted.org/cloud/ticket/148  (kushal, 17:45:22)

* Open Floor  (kushal, 17:53:08)

Meeting ended at 18:02:24 UTC.




Action Items

* dustymabe to update #115 after talking to mhayden
* kushal to work on https://fedorahosted.org/cloud/ticket/136
* kushal will build an unofficial image with all lang packs for #146




Action Items, by person
---
* dustymabe
  * dustymabe to update #115 after talking to mhayden
* kushal
  * kushal to work on https://fedorahosted.org/cloud/ticket/136
  * kushal will build an unofficial image with all lang packs for #146
* mhayden
  * dustymabe to update #115 after talking to mhayden
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (122)
* dustymabe (45)
* striker (29)
* maxamillion (28)
* zodbot (22)
* rtnpro (17)
* linuxmodder (12)
* tflink (11)
* number80 (10)
* jsmith (9)
* adimania (3)
* fhackdroid (3)
* imcleod (2)
* mhayden (1)
* sayan (1)
* trishnag (1)
* gholms (1)
* praveenkumar (1)
* jbrooks (1)
* adamw (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Meeting log from 2015-01-06

[Kushal Das]

==
#fedora-meeting-1: Fedora Cloud WG
==


Meeting started by kushal at 17:00:18 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2016-01-06/fedora_cloud_wg.2016-01-06-17.00.log.html
.



Meeting summary
---
* Roll Call  (kushal, 17:00:25)

* Action items from last meeting  (kushal, 17:03:00)
  * ACTION: jzb will update #135 on Fedora 23 retrospective  (dustymabe,
17:08:45)

* Proposals for F24 features https://fedorahosted.org/cloud/ticket/143
  (kushal, 17:09:26)
  * OpenShift Origin F24 Feature has been approved and origin is in
Rawhide currently
https://fedoraproject.org/wiki/Changes/OpenShiftOrigin
(maxamillion, 17:17:56)
  * rtnpro will work on cloud motd change  (kushal, 17:18:00)
  * cloud atomic dev mode info at

https://lists.fedoraproject.org/archives/list/cloud%40lists.fedoraproject.org/message/M75UQFVNUPNC6ES3RZMT5PXRHIH3FMP5/
(jbrooks, 17:19:31)
  * nzwulfin to add glusterfs and ceph client rpms  (nzwulfin, 17:20:44)

* Fedora Cloud FAD (late 2015/early 2016)
  https://fedorahosted.org/cloud/ticket/115  (kushal, 17:21:58)
  * LINK: https://fedoraproject.org/wiki/How_to_organize_a_FAD#Budget
(jzb, 17:27:12)

* Migrate all Dockerfiles / Images to systemd where possible
  https://fedorahosted.org/cloud/ticket/121  (kushal, 17:29:22)
  * ACTION: kushal will update #121 with a alarm in Feb  (kushal,
17:37:00)

* fedora-dockerfiles: Clean up READMEs
  https://fedorahosted.org/cloud/ticket/122  (kushal, 17:37:24)

* Document process for using Fedora-Dockerfile branches
  https://fedorahosted.org/cloud/ticket/123  (kushal, 17:39:51)

* Fedora-Dockerfiles examples for Kubernetes
  https://fedorahosted.org/cloud/ticket/125  (kushal, 17:45:06)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (kushal, 17:52:39)

* Produce updated cloud base images monthly  (kushal, 17:53:24)
  * LINK: https://fedorahosted.org/cloud/ticket/138   (kushal, 17:53:37)
  * ACTION: Kushal will update #136 and drop a mail to the list
(kushal, 17:55:01)

* Producing 2 week atomic images
  https://fedorahosted.org/cloud/ticket/139  (kushal, 17:55:17)
  * LINK: https://apps.fedoraproject.org/calendar/cloud/#m3212
(kushal, 17:57:11)
  * LINK:

https://lists.fedoraproject.org/archives/list/cloud%40lists.fedoraproject.org/thread/T6PVY62LR43LJE7JM2SHHNTKATQZZD76/
(dustymabe, 17:57:52)

* Networkd on Cloud/Atomic images  (kushal, 18:01:50)
  * ACTION: Kushal to update networkd ticket  (kushal, 18:08:58)

Meeting ended at 18:09:51 UTC.




Action Items

* jzb will update #135 on Fedora 23 retrospective
* kushal will update #121 with a alarm in Feb
* Kushal will update #136 and drop a mail to the list
* Kushal to update networkd ticket




Action Items, by person
---
* jzb
  * jzb will update #135 on Fedora 23 retrospective
* kushal
  * kushal will update #121 with a alarm in Feb
* **UNASSIGNED**
  * Kushal will update #136 and drop a mail to the list
  * Kushal to update networkd ticket




People Present (lines said)
---
* kushal (150)
* jzb (82)
* dustymabe (63)
* maxamillion (42)
* zodbot (28)
* scollier (20)
* nzwulfin (10)
* number80 (9)
* mmcgrath (8)
* jberkus (7)
* jbrooks (6)
* lalatenduM (5)
* trishnag (3)
* rtnpro (3)
* sayan (2)
* mhayden (1)
* imcleod (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Putting Networkd on cloud Atomic and base image for F24

[Kushal Das]

On 17/12/15, Sudhir D wrote:
> 
>

> >>But it is not used as the default networking configuration stack by any
> >>existing Fedora deliverable of which I'm aware.
> >>
> >Correct in that point.
> >
> >>>  We are
> >>>talking about enabling it as default networking stack.
> 
> This comes at a cost. It sounds more like 'gut feeling' to have networkd as
> default because we (fedora) have to be 'first' ?
> Just sighting the foundation statement,
> 
> *First* represents our commitment to innovation. We are not content to let
> others do all the heavy lifting on our behalf; we provide the latest in
> stable and robust, useful, and powerful free software in our Fedora
> distribution.
> 
> 
> I haven't worked on networkd myself, so you can beat me on that.. but from
> other responses to this thread I see that networkd still has to cover some
> ground before we label it as latest in stable and robust. I don't want to
> sound conservative, but remember, once we make it default it won't look good
> on us to retract if there are lot of issues.
If you read the other replies in the thread from the people who are
already using networkd, you will find it is actually the opposite. It is
very much stable, and robust, and latest in network stack (CoreOS is
using it as default from 2014).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Weekly meeting log from 2015-12-16

[Kushal Das]

===
#fedora-meeting-1: cloud_wg
===


Meeting started by kushal at 17:01:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-12-16/cloud_wg.2015-12-16-17.01.log.html
.



Meeting summary
---
* Roll Call  (kushal, 17:01:20)

* Action items from last meeting  (kushal, 17:03:39)
  * LINK: https://fedoraproject.org/wiki/Changes/Cloud_MOTD   (kushal,
17:08:50)

* Fedora Cloud FAD (late 2015/early 2016)
  https://fedorahosted.org/cloud/ticket/115  (kushal, 17:18:57)

* Migrate all Dockerfiles / Images to systemd where possible
  https://fedorahosted.org/cloud/ticket/121  (kushal, 17:23:42)
  * AGREED: Cloud group agrees to continue to maintain dockerfils on
GitHub for now until a more concrete proposal and timeline is
proposed to move them elsewhere. Work will re-commence on updating
Dockerfiles for dnf, systemd, etc.  (jzb, 17:35:52)

* make docker archived image get imported with lowercase tag
  https://fedorahosted.org/cloud/ticket/131  (kushal, 17:37:29)

* Fedora 23 Retrospective https://fedorahosted.org/cloud/ticket/135
  (kushal, 17:39:49)
  * ACTION: jzb will update #135 on Fedora 23 retrospective  (kushal,
17:42:00)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (kushal, 17:42:23)
  * LINK: https://fedoramagazine.org/fedora-cloud-vagrant-boxes-atlas/
(dustymabe, 17:56:10)

* Producing 2 week atomic images
  https://fedorahosted.org/cloud/ticket/139  (kushal, 17:56:28)

* Open Floor  (kushal, 17:57:40)
  * LINK: https://fedoraproject.org/wiki/Cloud/Network-Requirements
(jzb, 18:08:51)
  * LINK: https://fedoraproject.org/wiki/Changes/Cloud_Systemd_Networkd
(jzb, 18:13:08)

Meeting ended at 18:18:42 UTC.




Action Items

* jzb will update #135 on Fedora 23 retrospective




Action Items, by person
---
* jzb
  * jzb will update #135 on Fedora 23 retrospective
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (141)
* jzb (83)
* dustymabe (75)
* linuxmodder (48)
* tflink (27)
* jbrooks (22)
* mhayden (19)
* nzwulfin (18)
* zodbot (15)
* siXy (14)
* gholms (11)
* scollier (6)
* rtnpro (4)
* jsmith (3)
* number80 (3)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Putting Networkd on cloud Atomic and base image for F24

[Kushal Das]

On 14/12/15, Matthew Miller wrote:
> On Mon, Dec 14, 2015 at 12:31:45PM -0800, Adam Williamson wrote:
> > The situation is not at all the same; there is no clear expectation
> > that networkd will replace NetworkManager, indeed AFAIK it's been
> > explicitly stated that it won't, because it's not desirable for it to
> > cover all the complex configurations NM supports.
> 
> One development (mostly) since we started talking about this is that NM
> is now much more modular, and has a "configure and go away" mode (the
> lack of which was the main reason for not using it in the cloud image
> in the first place). It also can use the same lightweight DHCP library
> that systemd does, which in either case is an advantage over ye olde
> memory-hungry reference implementation as used by the initscripts
> networking.
> 
> I'm not saying it's the automatic winner over systemd-networkd, but all
> that should be taken into consideration.
Correct, still configuring networkd seems to be easier in my eyes. I
also forget to mention that CoreOS is using networkd from 2014. Major
also mentioned in the meeting that systemd-networkd's resource
requirements are a little lower than NM last time he checked. He is also
using networkd on bare metal servers.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Putting Networkd on cloud Atomic and base image for F24

[Kushal Das]

On 14/12/15, Adam Williamson wrote:
> On Tue, 2015-12-15 at 01:53 +0530, Kushal Das wrote:
> > 
> > > The thing is that it's almost impossible to say "if we just run all X
> > > tests, we can guarantee everything is fine!" in real life, especially
> > > at the level of something as complex as an entire OS networking stack.
> > > It's simply an unavoidable fact of life that the more network
> > > configuration stacks we have in mass usage, the more likely it is that
> > > there will be problems. We already have the legacy network.service and
> > > NetworkManager, adding a third choice is kind of egregious.
> > > 
> > The third choice is already in the images along with systemd.
> 
> But it is not used as the default networking configuration stack by any
> existing Fedora deliverable of which I'm aware.
> 
Correct in that point.

> >  We are
> > talking about enabling it as default networking stack. Ubuntu already
> > has a beta implementation in place with network instead of networking
> > scripts.
> > 
> > If we have to stay ahead in innovation, we have to do things for the
> > "First" of our four foundation. We were ahead in adopting systemd, we
> > should do the same for Networkd.
> 
> The situation is not at all the same; there is no clear expectation
> that networkd will replace NetworkManager, indeed AFAIK it's been
> explicitly stated that it won't, because it's not desirable for it to
> cover all the complex configurations NM supports.

Networkd will not replace NetworkManager. As Major wrote in his
findings, Networkd works really great (with very less configuration)
when used for head less systems.  NetworkManager in the other hand can
do many different magics for desktop/laptop users. In our cloud
scenario, we are looking into the head less use case. We also have clear
examples written by Major for various complex cases with Networkd.

As I mentioned in my previous mail, the other *major* distributions on
cloud are also moving to Networkd. If we provide the same, it will be
somewhat helpful to migrate for the users.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Time to put in Fedora 24 changes

[Kushal Das]

Hi all,

It is again time to start working towards next Fedora release. Proposal
submission deadline for Fedora 24 is 12th January, 2016 [1].

During the last week's Cloud SIG meeting, we discussed about few
possible features we want to work on. Please file the formal changes in
the wiki, and then update [2] where we are keeping the notes related to
the ideas for Fedora 24 from Cloud SIG.

If you want to learn more about how to file a change request, please go
through [3]. To discuss on any particular idea, feel free to start a new
thread in this list, or reply to this mail in the same thread.


[1] https://fedoraproject.org/wiki/Releases/24/Schedule
[2]
https://fedoraproject.org/wiki/Changes/Features_for_Fedora_24_from_Cloud_SIG
[3] https://fedoraproject.org/wiki/Changes/Policy

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Putting Networkd on cloud Atomic and base image for F24

[Kushal Das]

On 14/12/15, Adam Williamson wrote:
> On Mon, 2015-12-14 at 23:30 +0530, Kushal Das wrote:
> > Hi,
> > 
> > This email is to resume the discussion on putting Networkd as network
> > stack in Fedora Cloud Atomic and base images. During Fedora 23 release
> > we had some discussion on the same. I made couple of images [1], and
> > also AMI on AWS [2], so that people can play around.
> > 
> > Major Hayden did some excellent write up [3] [4] [5] about Networkd in
> > Fedora [6].
> > 
> > Last time when we discussed this issue, one of the major concern was QA
> > cycle. We all know how much overloaded the QA team is. Now we have some
> > level of automated testing (increasing regularly), and also a new
> > volunteer group from the Cloud SIG to help by doing manual QA on the
> > images. If we can make a list of things to be tested (or what all tests
> > are currently being done) on the network stack for current Fedora
> > releases, we all can help in, and make sure that the images with this
> > new feature get proper testing.
> 
> The thing is that it's almost impossible to say "if we just run all X
> tests, we can guarantee everything is fine!" in real life, especially
> at the level of something as complex as an entire OS networking stack.
> It's simply an unavoidable fact of life that the more network
> configuration stacks we have in mass usage, the more likely it is that
> there will be problems. We already have the legacy network.service and
> NetworkManager, adding a third choice is kind of egregious.
> 
The third choice is already in the images along with systemd. We are
talking about enabling it as default networking stack. Ubuntu already
has a beta implementation in place with network instead of networking
scripts.

If we have to stay ahead in innovation, we have to do things for the
"First" of our four foundation. We were ahead in adopting systemd, we
should do the same for Networkd.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Putting Networkd on cloud Atomic and base image for F24

[Kushal Das]

Hi,

This email is to resume the discussion on putting Networkd as network
stack in Fedora Cloud Atomic and base images. During Fedora 23 release
we had some discussion on the same. I made couple of images [1], and
also AMI on AWS [2], so that people can play around.

Major Hayden did some excellent write up [3] [4] [5] about Networkd in
Fedora [6].

Last time when we discussed this issue, one of the major concern was QA
cycle. We all know how much overloaded the QA team is. Now we have some
level of automated testing (increasing regularly), and also a new
volunteer group from the Cloud SIG to help by doing manual QA on the
images. If we can make a list of things to be tested (or what all tests
are currently being done) on the network stack for current Fedora
releases, we all can help in, and make sure that the images with this
new feature get proper testing.

"Features", and "First" are part of our four foundations. I personally
think putting Networkd on our cloud images will certainly help us to
grow the features where latest technology is involved.

[1]
https://kushaldas.in/posts/testing-fedora-cloud-image-with-systemd-networkd.html
[2]
https://kushaldas.in/posts/testing-systemd-networkd-based-fedora-22-ami-s.html
[3] https://major.io/2015/10/26/systemd-networkd-and-macvlan-interfaces/
[4] https://major.io/2015/10/16/gre-tunnels-with-systemd-networkd/
[5]
https://major.io/2015/09/28/customizing-systemds-network-device-names/
[6] https://fedoraproject.org/wiki/Cloud/Network-Requirements

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Add net.ifnames=0 to Atomic host

[Kushal Das]

On 09/12/15, Colin Walters wrote:
> On Wed, Dec 9, 2015, at 11:40 AM, Dusty Mabe wrote:
> >
> >
> >
> On 12/04/2015 02:16 PM, Colin Walters wrote:
> > > On Mon, Nov 23, 2015, at 10:35 AM, Dusty Mabe wrote:
> >>
> >>
> >> Right, this would affect them all. As you mention below we were
> >> intending for this ("eth0") to be the case for a long time so I
> >> figured we should fix it. You are right that this would be a change
> >> over how we released F23 atomic and it does have implications for
> >> other environments.
> >
> > Based on that, my instinct here is to only do this change for the
> > Vagrant box.  WDYT?
> >
> >
> Ok can you merge the attached patch then?
> 
> Done, thank you!
> 
> https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=80eeba2146f8165b274348113b54b81070116ba7

Same failure [1] in today's tests.

[1] https://apps.fedoraproject.org/autocloud/jobs/828/output

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Add net.ifnames=0 to Atomic host

[Kushal Das]

On 09/12/15, Colin Walters wrote:
> On Wed, Dec 9, 2015, at 11:40 AM, Dusty Mabe wrote:
> >
> >
> >
> On 12/04/2015 02:16 PM, Colin Walters wrote:
> > > On Mon, Nov 23, 2015, at 10:35 AM, Dusty Mabe wrote:
> >>
> >>
> >> Right, this would affect them all. As you mention below we were
> >> intending for this ("eth0") to be the case for a long time so I
> >> figured we should fix it. You are right that this would be a change
> >> over how we released F23 atomic and it does have implications for
> >> other environments.
> >
> > Based on that, my instinct here is to only do this change for the
> > Vagrant box.  WDYT?
> >
> >
> Ok can you merge the attached patch then?
> 
> Done, thank you!
> 
> https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=80eeba2146f8165b274348113b54b81070116ba7
Means we have to wait for the next nightly build to see if it passes or
not. Thanks a lot for the work :)

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Meeting minutes from 2015-11-18

[Kushal Das]

===
#fedora-meeting-1: Cloud WG
===


Meeting started by kushal at 17:00:44 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-18/fedora-meeting-1.2015-11-18-17.00.log.html
.



Meeting summary
---
* Roll Call  (kushal, 17:00:50)

* Action items from last meeting  (kushal, 17:03:25)
  * LINK:
https://kushaldas.in/posts/need-help-to-test-fedora-cloud-images.html
(kushal, 17:03:45)
  * ACTION: rtnpro to open a trac ticket to create nulecule examples in
fedora-dockerfiles  (kushal, 17:07:42)

* Fedora Cloud FAD (late 2015/early 2016)
  https://fedorahosted.org/cloud/ticket/115  (kushal, 17:10:16)

* Migrate all Dockerfiles / Images to systemd where possible
  https://fedorahosted.org/cloud/ticket/121  (kushal, 17:11:35)

* fedora-dockerfiles: Clean up READMEs.
  https://fedorahosted.org/cloud/ticket/122  (kushal, 17:14:04)
  * ACTION: kushal will ask coolsvap for an update on
https://fedorahosted.org/cloud/ticket/122  (kushal, 17:15:37)

* Document process for using Fedora-Dockerfile branches
  https://fedorahosted.org/cloud/ticket/123  (kushal, 17:16:00)
  * ACTION: maxamillion will review

https://github.com/fedora-cloud/Fedora-Dockerfiles/wiki/Guidelines-for-Creating-Dockerfiles#branches-in-fedora-dockerfiles-repo
(kushal, 17:17:50)

* Fedora-Dockerfiles examples for Kubernetes
  https://fedorahosted.org/cloud/ticket/125  (kushal, 17:18:35)
  * ACTION: rtnpro will push a PR with Nulecule file for
https://fedorahosted.org/cloud/ticket/125  (kushal, 17:23:17)

* make docker archived image get imported with lowercase tag
  https://fedorahosted.org/cloud/ticket/131  (kushal, 17:23:31)
  * LINK: https://github.com/redhat-imaging/imagefactory/issues/359
(kushal, 17:24:41)

* Fedora 23 Retrospective https://fedorahosted.org/cloud/ticket/135
  (kushal, 17:26:33)
  * LINK: https://fedorahosted.org/cloud/ticket/121   (kushal, 17:35:07)

* Produce updated cloud base images monthly
  https://fedorahosted.org/cloud/ticket/138  (kushal, 17:36:36)

* Producing 2 week atomic images
  https://fedorahosted.org/cloud/ticket/139  (kushal, 17:45:41)

* Open Floor  (kushal, 17:48:40)
  * LINK: https://github.com/fedora-infra/fedimg   (kushal, 17:51:08)

Meeting ended at 17:53:31 UTC.




Action Items

* rtnpro to open a trac ticket to create nulecule examples in
  fedora-dockerfiles
* kushal will ask coolsvap for an update on
  https://fedorahosted.org/cloud/ticket/122
* maxamillion will review
  
https://github.com/fedora-cloud/Fedora-Dockerfiles/wiki/Guidelines-for-Creating-Dockerfiles#branches-in-fedora-dockerfiles-repo
* rtnpro will push a PR with Nulecule file for
  https://fedorahosted.org/cloud/ticket/125




Action Items, by person
---
* kushal
  * kushal will ask coolsvap for an update on
https://fedorahosted.org/cloud/ticket/122
* maxamillion
  * maxamillion will review

https://github.com/fedora-cloud/Fedora-Dockerfiles/wiki/Guidelines-for-Creating-Dockerfiles#branches-in-fedora-dockerfiles-repo
* rtnpro
  * rtnpro to open a trac ticket to create nulecule examples in
fedora-dockerfiles
  * rtnpro will push a PR with Nulecule file for
https://fedorahosted.org/cloud/ticket/125
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (111)
* dustymabe (31)
* imcleod (13)
* adimania (11)
* zodbot (11)
* maxamillion (10)
* rtnpro (6)
* fhackdroid (5)
* prkumar (3)
* trishnag (3)
* gholms (3)
* jbrooks (3)
* number80 (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Meeting minutes from 2015-11-11

[Kushal Das]

===
#fedora-meeting-1: Cloud WG
===


Meeting started by kushal at 17:00:57 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-11-11/fedora-meeting-1.2015-11-11-17.00.log.html
.



Meeting summary
---
* Roll Call  (kushal, 17:01:03)

* Action items from last meeting  (kushal, 17:04:19)
  * ACTION: kushal will blog post about getting more volunteers for
manual qa + test coverage.  (kushal, 17:11:39)
  * LINK: https://www.piratepad.ca/p/fedoracloud   (kushal, 17:15:50)
  * LINK: https://fedoraproject.org/easyfix/   (kushal, 17:16:52)

* python3 only means ansible won't work
  https://fedorahosted.org/cloud/ticket/126  (kushal, 17:17:48)
  * LINK: https://fedoramagazine.org/getting-ansible-working-fedora-23/
(jbrooks, 17:18:36)
  * ACTION: dustymabe will do a PR to add ansible steps in
https://github.com/fedora-cloud/fedoracloud  (kushal, 17:21:10)

* Producing Updated Cloud/Atomic Images
  https://fedorahosted.org/cloud/ticket/94  (kushal, 17:22:53)
  * LINK: https://fedoraproject.org/wiki/Changes/ProductDefinitionCenter
(dustymabe, 17:27:51)

* Fedora Cloud FAD (late 2015/early 2016)
  https://fedorahosted.org/cloud/ticket/115  (kushal, 17:29:15)

* Migrate all Dockerfiles / Images to systemd where possible
  https://fedorahosted.org/cloud/ticket/121  (kushal, 17:37:03)
  * LINK:
https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
(adimania, 17:38:59)

* fedora-dockerfiles: Clean up READMEs.
  https://fedorahosted.org/cloud/ticket/122  (kushal, 17:42:39)

* Document process for using Fedora-Dockerfile branches
  https://fedorahosted.org/cloud/ticket/123  (kushal, 17:45:25)
  * LINK:

https://github.com/fedora-cloud/Fedora-Dockerfiles/wiki/Guidelines-for-Creating-Dockerfiles
(adimania, 17:47:30)

* Fedora-Dockerfiles examples for Kubernetes
  https://fedorahosted.org/cloud/ticket/125  (kushal, 17:48:11)
  * ACTION: rtnpro will help to create nulecule examples in
fedora-dockerfiles  (kushal, 17:50:16)

* Working with the Server WG https://fedorahosted.org/cloud/ticket/127
  (kushal, 17:51:18)

* make docker archived image get imported with lowercase tag
  https://fedorahosted.org/cloud/ticket/131  (kushal, 17:52:53)

* Fedora 23 Retrospective https://fedorahosted.org/cloud/ticket/135
  (kushal, 17:54:09)
  * F23 testing left something to be desired  (gholms, 17:55:58)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (kushal, 17:56:25)

* Open floor  (kushal, 17:56:45)
  * HELP: If anyone is interested in pitching in to help maintain
cloud-init please let me know.  (gholms, 18:01:48)

Meeting ended at 18:04:24 UTC.




Action Items

* kushal will blog post about getting more volunteers for manual qa +
  test coverage.
* dustymabe will do a PR to add ansible steps in
  https://github.com/fedora-cloud/fedoracloud
* rtnpro will help to create nulecule examples in fedora-dockerfiles




Action Items, by person
---
* dustymabe
  * dustymabe will do a PR to add ansible steps in
https://github.com/fedora-cloud/fedoracloud
* kushal
  * kushal will blog post about getting more volunteers for manual qa +
test coverage.
* rtnpro
  * rtnpro will help to create nulecule examples in fedora-dockerfiles
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (118)
* dustymabe (80)
* adimania (28)
* maxamillion (24)
* zodbot (13)
* number80 (11)
* gholms (11)
* nirik (8)
* scollier (5)
* fhackdroid (3)
* jbrooks (3)
* spstarr (2)
* rtnpro (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [DISCUSS] Cloud and Server Workgroup relationship

[Kushal Das]

On 03/11/15, Matt Micene wrote:
> I think this highlights the problem we're currently seeing with the Fedora
> Cloud Base adoption
> 
> On 10/28/2015 07:42 PM, Matthew Miller wrote:
> > > Actually, I don't think that's true. Take a look at "fr1st p0st":
> > >
> > > https://lists.fedoraproject.org/pipermail/cloud/2010-January/01.html
> 
> 
> There is no singular Fedora release anymore, so what are people getting
> when they install Cloud Base?  The `cloudtoserver` script essentially
> disables cloud-init and installs Fedora Server.  So what's in the Cloud
> Base box when we say it's the "base building block of the Fedora flavors"?
> What was the point of creating use case editions and not using them in the
> cloud?
Because we can not even guess what all use cases people have while using a
cloud instance? People generally take the base image, and have their own
tooling (say ansible, or shell scripts) which deploys the required
applications in the cloud. This is where the minimal cloud base image
comes handy.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[X-POST] New guide focusing cloud users

[Kushal Das]

Hi all,

i started a new guide [1] focusing Cloud users. Currently we have
different guides spread over different wiki pages, and blog posts. But
we don't have any single place which at least points to the current
and updated docs. I first suggested about this during Flock cloud
working group meeting.

The docs are written using reStructured Text format, using sphinx
project. When Fedora docs team comes up with the new tooling, they can
just pull in the files from here. The source can be found at [2].

Right now it contains a very few things I just put in today. Because i
am using readthedocs.org here, any commit will be reflected on the
docs very fast. I am yet to add the download chapter.  Feel free to
add anything you think is important for our users, PR(s) are always
welcome.


[1]  http://fedoracloud.rtfd.org
[2] https://github.com/fedora-cloud/fedoracloud


Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora 22 Cloud image with systemd-networkd

[Kushal Das]

Hi all,

I have made one Fedora 22 image with systemd-networkd for network
configuration. The image is at [1], and the corresponding blog post can
be found at [2]. Please have a look, and test the image. Reply back in
this email, or make a comment in the blog post if you have any trouble
in using the image.

[1] http://kushaldas.in/networkd.qcow2
[2]
http://kushaldas.in/posts/testing-fedora-cloud-image-with-systemd-networkd.html

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Testing Docker images (and possibly other cloud images) in CentOS CI

[Kushal Das]

On Thu, Jul 2, 2015 at 8:12 PM, Matthew Miller mat...@fedoraproject.org wrote:
 At Summit, I talked briefly to Karanbir Singh from CentOS. CentOS has a
 Jenkins system with a lot of hardware behind it (https://ci.centos.org/),
 and they run all of their layered image builds* through that. KB
 offered to run their tests on any images Fedora produces. That seems
 cool, but I'm not sure how we could best take advantage of this. How
 could we integrate such tests into our processes?

 As a first step, does anyone have a problem with saying to CentOS,
 Cool! Start running those tests! Thanks! — even if we don't know what
 exactly what we're going to do with any results? I'm imagining that
 once we get to $futurephase of the build service plan, layered images
 will go through Bodhi just like RPMs, and at that point, this feedback
 could be hooked in there. In the meantime, packagers of layered images
 could simply be told to look manually.
This sounds great. I am already doing similar kind of work for Python upstream
in ci.centos.org.


 The tests themselves, as I understand it, are documented at
 http://wiki.centos.org/QaWiki/AutomatedTests/WritingTests/t_functional,
 by the way, including contribution information.


We can use most of these t_fuctional tests, just that instead of yum,
we have dnf.

 * See change proposal for a layered image build service for Fedora —
 actually testing images which are produced is a next step specifically
 listed as out of scope for the change itself.
 https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service

+1

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Fedora 22 is out, Fedora 23 is coming :)

[Kushal Das]

On 16/06/15, Matthew Miller wrote:
 On Tue, Jun 16, 2015 at 09:31:27AM -0400, Dusty Mabe wrote:
It's unfortunate that the dependencies can't be expressed in a richer
way here. It's not that the kernel requires that package... the
hardware does. Even if we remove it in the cloud kickstarts, it gets
pulled back in on update, because it's a Requires(pre).
   Create a dnf plugin to ignore it.
  Will this handle the rpm db correctly? Meaning after the install will
  rpm still think there is a missing dependency? If this happens I think
  you get a warning anytime you use yum/dnf. 
 
 In this case, since it's only a Requires(pre), RPM doesn't mind.
 
I was talking with the dnf developers today. They said there is no
direct way to achieve this. But we can create a plugin which will remove
it (if it exits) after any transaction.

Another option is to try to put the package in the exclude list for the
transaction. I will try for this method first.

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [Cloud WG] meeting time change request

[Kushal Das]

On Thu, Jun 11, 2015 at 12:24 AM, Haïkel hgue...@fedoraproject.org wrote:
 Hi,

 I request that we change the meeting time to 5PM UTC.
 It should be fine for most of us, and we can't keep that current
 schedule.
 Please vote in that thread (-1/+0/+1)

 ---

 +1

+1 :D

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Fedora 22 is out, Fedora 23 is coming :)

[Kushal Das]

Hi,

Thank you everyone for a great Fedora 22 release. Things are stable now,
before we can understand we will be in the alpha freeze for Fedora 23.
So this is a good time to start working on the new features list for Fedora
23. 23rd June is the last date to submit a new system wide change
for Fedora 23, 11th August is the alpha release for Fedora 23.

Below I have written few points which came up in different discussions.
Please feel free to comment/add/delete in this thread.

* Better user documentation for cloud. We need something better than
  wiki.
* Notification of pending updates in the base image. After login the
  user should get a motd message saying which all updates are pending (I
  have worked on this part time before).
* Reduce the base cloud image size (we also have
  https://fedorahosted.org/fedora-badges/ticket/378 )
* testCloud (pushed back from Fedora 22 change list).
* https://github.com/vmware/tdnf this might help us to go another step
  closer to remove Python stack from the cloud image.* Having a better
* workstation to cloud story (came up in the last week's meeting).

Kushal
-- 
Fedora Cloud Engineer
CPython Core Developer
Director @ Python Software Foundation
http://kushaldas.in
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct