Ghahahdafse
by Zack Cylinder
On Thu, Sep 10, 2015 at 11:38 AM, Zack Cylinder <zack(a)cloudbakers.net>
wrote:
> Alkjsadflkajdflkasjfalsjfaefjwlak
>
> On Wed, Sep 9, 2015 at 11:29 PM, <cloud-request(a)lists.fedoraproject.org>
> wrote:
>
>> Send cloud mailing list submissions to
>> cloud(a)lists.fedoraproject.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://admin.fedoraproject.org/mailman/listinfo/cloud
>> or, via email, send a message with subject or body 'help' to
>> cloud-request(a)lists.fedoraproject.org
>>
>> You can reach the person managing the list at
>> cloud-owner(a)lists.fedoraproject.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of cloud digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: [cloud] #106: No longer provide 32 bit image
>> (Fedora Cloud Trac Tickets)
>> 2. Re: [cloud] #113: Ship with firewall on by default
>> (Fedora Cloud Trac Tickets)
>> 3. Re: [cloud] #118: Deliverables (Fedora Cloud Trac Tickets)
>> 4. Re: [cloud] #118: Deliverables (Fedora Cloud Trac Tickets)
>> 5. [proposal] Joint meetings between upstream Atomic/Fedora
>> Cloud WG (Haïkel)
>> 6. Re: [cloud] #118: Deliverables (Fedora Cloud Trac Tickets)
>> 7. Re: [cloud] #105: Missing Cockpit RPMs in Fedora Atomic 22
>> (Fedora Cloud Trac Tickets)
>> 8. Re: [proposal] Joint meetings between upstream Atomic/Fedora
>> Cloud WG (Joe Brockmeier)
>> 9. atomic builds still broken (Dusty Mabe)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 09 Sep 2015 17:32:15 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: dennis(a)ausil.us, dustymabe(a)gmail.com, karlthered(a)gmail.com,
>> jzb(a)redhat.com, kushal(a)fedoraproject.org,
>> mattdm(a)fedoraproject.org,
>> oddshocks(a)riseup.net, roshi(a)fedoraproject.org, znmeb(a)znmeb.net
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #106: No longer provide 32 bit image
>> Message-ID: <036.0178a9ccb38b8401c78a3da8cd3404d3(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #106: No longer provide 32 bit image
>> ------------------------------+------------------------
>> Reporter: dustymabe | Owner: oddshocks
>> Type: task | Status: closed
>> Priority: normal | Milestone: Future
>> Component: Cloud Base Image | Resolution: fixed
>> Keywords: meeting |
>> ------------------------------+------------------------
>> Changes (by roshi):
>>
>> * status: assigned => closed
>> * resolution: => fixed
>>
>>
>> Comment:
>>
>> This seems to be pretty much wrapped up. Closing. Thanks all!
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/106#comment:18>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Wed, 09 Sep 2015 17:44:19 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: mattdm(a)fedoraproject.org, roshi(a)fedoraproject.org,
>> ryansb(a)fedoraproject.org
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #113: Ship with firewall on by default
>> Message-ID: <036.557d2b4f970225d3f387e1b532608851(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #113: Ship with firewall on by default
>> -----------------------+----------------------
>> Reporter: dustymabe | Owner:
>> Type: task | Status: closed
>> Priority: normal | Milestone: Future
>> Component: --- | Resolution: invalid
>> Keywords: meeting |
>> -----------------------+----------------------
>> Changes (by roshi):
>>
>> * resolution: => invalid
>> * status: new => closed
>>
>>
>> Comment:
>>
>> Going to close this ticket, as everything seems to be working as expected
>> - no firewall on or configured by default.
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/113#comment:3>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 09 Sep 2015 17:59:48 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: dustymabe(a)gmail.com, karlthered(a)gmail.com, jkurik(a)redhat.com,
>> mattdm(a)fedoraproject.org, roshi(a)fedoraproject.org
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #118: Deliverables
>> Message-ID: <032.985e63ffc211bffb2ff96d7e4b8341cd(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #118: Deliverables
>> ---------------------+---------------------
>> Reporter: roshi | Owner:
>> Type: task | Status: new
>> Priority: normal | Milestone: Future
>> Component: --- | Resolution:
>> Keywords: meeting |
>> ---------------------+---------------------
>>
>> Comment (by dustymabe):
>>
>> +1
>>
>> One thing to note is that right now our AMIs aren't uploading so we need
>> to get that fixed soon so we can test for F23.
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/118#comment:6>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 09 Sep 2015 18:00:51 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: dustymabe(a)gmail.com, karlthered(a)gmail.com, jkurik(a)redhat.com,
>> kushal(a)fedoraproject.org, mattdm(a)fedoraproject.org,
>> roshi(a)fedoraproject.org
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #118: Deliverables
>> Message-ID: <032.53091635f792594ccabc01df1889fb61(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #118: Deliverables
>> ---------------------+---------------------
>> Reporter: roshi | Owner:
>> Type: task | Status: new
>> Priority: normal | Milestone: Future
>> Component: --- | Resolution:
>> Keywords: meeting |
>> ---------------------+---------------------
>>
>> Comment (by kushal):
>>
>> +1 from me.
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/118#comment:7>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Wed, 9 Sep 2015 20:02:35 +0200
>> From: Haïkel <hguemar(a)fedoraproject.org>
>> To: Fedora Cloud SIG <cloud(a)lists.fedoraproject.org>,
>> atomic-devel(a)projectatomic.io
>> Subject: [proposal] Joint meetings between upstream Atomic/Fedora
>> Cloud WG
>> Message-ID:
>> <
>> CAHaCVFBVpYJBQc50SRnT-RyA7YAGvciSUqGDd7L6XGLG-B8zjQ(a)mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> Hi,
>>
>> as you know, Fedora Cloud WG decided that starting F24, Fedora Atomic will
>> be the main Fedora Cloud product.
>>
>> I respect that Project Atomic is not limited to Fedora, but currently,
>> it gives the
>> feeling that Fedora Atomic and Fedora Cloud SIG are separate groups.
>> And this is definitively wrong.
>>
>> So I suggest that every two weeks, we hold joint meetings as in merging
>> our weekly meetings not adding a new one. This will enable us to work
>> together more efficiently.
>>
>> Your thoughts?
>>
>> Regards,
>> H.
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Wed, 09 Sep 2015 18:02:59 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: dustymabe(a)gmail.com, karlthered(a)gmail.com, jkurik(a)redhat.com,
>> kushal(a)fedoraproject.org, mattdm(a)fedoraproject.org,
>> roshi(a)fedoraproject.org
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #118: Deliverables
>> Message-ID: <032.a47514e9415ac8ea4ba1f28e39ecc1c3(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #118: Deliverables
>> ---------------------+---------------------
>> Reporter: roshi | Owner:
>> Type: task | Status: closed
>> Priority: normal | Milestone: Future
>> Component: --- | Resolution: fixed
>> Keywords: meeting |
>> ---------------------+---------------------
>> Changes (by roshi):
>>
>> * status: new => closed
>> * resolution: => fixed
>>
>>
>> Comment:
>>
>> I'll update the signed off bit on the wiki page [0]. Thanks all!
>>
>> [0]
>>
>> https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/118#comment:8>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Wed, 09 Sep 2015 18:06:55 -0000
>> From: "Fedora Cloud Trac Tickets" <cloud-trac(a)fedoraproject.org>
>> To: dennis(a)ausil.us, dustymabe(a)gmail.com, jbrooks(a)redhat.com,
>> jzb(a)redhat.com, kushal(a)fedoraproject.org,
>> mattdm(a)fedoraproject.org,
>> emailscottcollier(a)gmail.com, walters(a)redhat.com
>> Cc: cloud(a)lists.fedoraproject.org
>> Subject: Re: [cloud] #105: Missing Cockpit RPMs in Fedora Atomic 22
>> Message-ID: <030.9785d760d712ea472ee623b2cb495cca(a)fedoraproject.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> #105: Missing Cockpit RPMs in Fedora Atomic 22
>> -------------------------------+--------------------------
>> Reporter: jzb | Owner: jasonbrooks
>> Type: defect | Status: assigned
>> Priority: blocker | Milestone: Fedora 22
>> Component: Docker Host Image | Resolution:
>> Keywords: meeting |
>> -------------------------------+--------------------------
>>
>> Comment (by jasonbrooks):
>>
>> Now on the wiki at
>> https://fedoraproject.org/wiki/Cloud/Tutorials/cockpit-
>> in-a-container
>>
>> --
>> Ticket URL: <https://fedorahosted.org/cloud/ticket/105#comment:24>
>> cloud <https://fedorahosted.org/cloud>
>> Fedora Cloud Working Group Ticketing System
>>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Wed, 9 Sep 2015 14:52:20 -0400
>> From: Joe Brockmeier <jzb(a)redhat.com>
>> To: cloud(a)lists.fedoraproject.org, "atomic-devel(a)projectatomic.io"
>> <atomic-devel(a)projectatomic.io>, "The CentOS developers
>> mailing list."
>> <centos-devel(a)centos.org>
>> Subject: Re: [proposal] Joint meetings between upstream Atomic/Fedora
>> Cloud WG
>> Message-ID: <55F07FE4.6090001(a)redhat.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> On 09/09/2015 02:02 PM, Haïkel wrote:
>> > So I suggest that every two weeks, we hold joint meetings as in merging
>> > our weekly meetings not adding a new one. This will enable us to work
>> > together more efficiently.
>> >
>> > Your thoughts?
>>
>> So - we don't do separate Project Atomic meetings - there's the CentOS
>> SIG meeting and Fedora Cloud. I'm amenable to doing just one joint
>> meeting or finding some way to merge them, though.
>>
>> Also cc'ing the CentOS devel list.
>> --
>> Joe Brockmeier | Community Team, OSAS
>> jzb(a)redhat.com | http://community.redhat.com/
>> Twitter: @jzb | http://dissociatedpress.net/
>>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: signature.asc
>> Type: application/pgp-signature
>> Size: 473 bytes
>> Desc: OpenPGP digital signature
>> URL: <
>> http://lists.fedoraproject.org/pipermail/cloud/attachments/20150909/6b67a...
>> >
>>
>> ------------------------------
>>
>> Message: 9
>> Date: Thu, 10 Sep 2015 00:29:20 -0400
>> From: Dusty Mabe <dusty(a)dustymabe.com>
>> To: cloud(a)lists.fedoraproject.org
>> Subject: atomic builds still broken
>> Message-ID: <20150910042920.GA23101(a)media.redhat.com>
>> Content-Type: text/plain; charset=us-ascii
>>
>>
>> >From what I can tell the the atomic builds are still broken [1]. The
>> cloud base builds are working [2]. I was able to perform a localbuild
>> by changing the "Install Tree" from [3] to match what is set for the cloud
>> base build [4].
>>
>> Is that the problem that is breaking the builds? How do we get the
>> location updated?
>>
>> The good news is that I get an image that is finally built against
>> F23!
>>
>> <<<<<<
>> -bash-4.3# cat /etc/redhat-release
>> Fedora release 23 (Twenty Three)
>> <<<<<<
>>
>> The bad news is that we are still having the same "mounting" problems
>> that we were seeing in the rawhide builds where sysroot isn't mounted
>> properly:
>>
>> <<<<<<
>> -bash-4.3# ls /sysroot/
>> -bash-4.3# rpm-ostree status
>> error: No such file or directory
>> <<<<<<
>>
>> Any tips for getting these issues fixed?
>>
>> Dusty
>>
>> [1] - http://koji.fedoraproject.org/koji/taskinfo?taskID=11016111
>> [2] - http://koji.fedoraproject.org/koji/taskinfo?taskID=10985173
>> [3] - http://kojipkgs.fedoraproject.org/mash/atomic/23/
>> [4] -
>> http://kojipkgs.fedoraproject.org/mash/branched-20150907/23/x86_64/os/
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> cloud mailing list
>> cloud(a)lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/cloud
>>
>>
>> End of cloud Digest, Vol 69, Issue 10
>> *************************************
>>
>
>
8 years, 7 months
[proposal] Joint meetings between upstream Atomic/Fedora Cloud WG
by Haïkel
Hi,
as you know, Fedora Cloud WG decided that starting F24, Fedora Atomic will
be the main Fedora Cloud product.
I respect that Project Atomic is not limited to Fedora, but currently,
it gives the
feeling that Fedora Atomic and Fedora Cloud SIG are separate groups.
And this is definitively wrong.
So I suggest that every two weeks, we hold joint meetings as in merging
our weekly meetings not adding a new one. This will enable us to work
together more efficiently.
Your thoughts?
Regards,
H.
8 years, 7 months
[cloud] #113: Ship with firewall on by default
by Fedora Cloud Trac Tickets
#113: Ship with firewall on by default
-----------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords: meeting
-----------------------+---------------------
We should most likely be including the iptables-services rpm which start
iptables up on system boot and restores rules that represent a "sane
default".
It has been my experience in the past that the firewall has been
configured.. Not sure when the default configuration got moved into a
separate rpm but we should restore it. It is easy to configure and poke
holes in the firewall (via cloud-init) or some other mechanism so this
shouldn't be too big of a deal.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/113>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
8 years, 7 months
[cloud] #106: No longer provide 32 bit image
by Fedora Cloud Trac Tickets
#106: No longer provide 32 bit image
------------------------------+---------------------
Reporter: dustymabe | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Keywords: meeting
------------------------------+---------------------
We have discussed this quite a bit in the past. I believe with proper
communication we can stop delivering 32 bit cloud images for F23.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/106>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
8 years, 7 months
Cloud deliverables for F23
by Jan Kurik
Hi Working Group,
currently we are missing list of release deliverables (blocking as
well as non-blocking) for Fedora releases. Some time ago there has
been an activity started in FESCo to fill this gap [1].
As part of this activity has been put together a Wiki page summarizing
all the deliverables we need, to have a Fedora release complete [2].
I would like to ask you (WG) to go through the section "Cloud" of the
Wiki page and put together the list of deliverables which is produced
by Cloud WG for Fedora 23.
Thanks for your cooperation.
Regards,
Jan
[1] https://fedorahosted.org/fesco/ticket/1427
[2] https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
8 years, 7 months
Image versioning in Fedora-Dockerfiles (and auto-docker-build)
by Pavel Raiskup
Hi all,
I've been told by Scott that we are able to setup auto-build for
Dockerfiles and do automatic push to docker.io registry (triggered by any
merged github pull request).
As a "owner" of particular component in Fedora-Dockerfiles git repo -- am
I able to somehow control docker tags? So far I've seen only 'latest' tag
available in fedora/ namespace, but something like this would be perfect:
$ git clone https://github.com/fedora-cloud/Fedora-Dockerfiles.git
$ cd Fedora-Dockerfiles # master branch
$ cat postgresql/docker-tags
latest
22_latest
22_9.4_0.11
$ git checkout f21
$ cat postgresql/docker-tags
21_latest
21_9.3_0.11
I am unable to find git repository where the script that does
'docker build' and 'docker tag' resides, is it somewhere? I would like to
collaborate possibly.
Pavel
8 years, 7 months
