On 06/20/2018 10:43 AM, Matthew Miller wrote:
Awesome. Are you, by any chance, going to be at Flock this summer?
Not this year. :( Too many things going on this summer & not enough time.
Joe
--
Joe Doss
j...@solidadmin.com
___
cloud mailing
eases for users to consume. I
definitely want to be apart of that discussion if they plan is to move
Fedora Cloud under Fedora Server's umbrella.
Joe
--
Joe Doss
j...@solidadmin.com
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
On 06/18/2018 02:25 AM, Peter Robinson wrote:
On Fri, Jun 15, 2018 at 10:21 PM, Joe Doss wrote:
Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more
frequent tested releases of Fedora Cloud it's user base. The goal of this
project is to provide more frequent up
Hello!
My name is Joe Doss and I want to help the Fedora Cloud SIG bring more
frequent tested releases of Fedora Cloud it's user base. The goal of
this project is to provide more frequent updates of Fedora Cloud to
users on a set cadence or on a case per case basis for major security
e
OK we are in business.
https://fedoraproject.org/wiki/Test_Results:Fedora_28_Beta_1.3_Cloud#x86_64
I will see if I can get some time to do the same for Atomic AMIs this weekend.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe sen
I was signed in when I tried to fill out the wiki page. I just checked again
and it states You need to have at least CLA+1 (group). I just checked my Fedora
account and I am approved in the cla_done group. Is there another one I need to
apply for?
__
I spun up Fedora 28 Beta 1.3 Cloud AMI in us-west-2, ran through the tests and
it had no issues aside from selinux-policy needed to get updated to
selinux-policy-3.14.1-19.fc28
(https://bodhi.fedoraproject.org/updates/FEDORA-2018-234de0ee13) so you can
start services like Nginx.
I would fill o
jdoss reported a new issue against the project: `cloud-sig` that you are
following:
``
When starting the F28 vagrant image it fails with the error below due to
`/etc/sysconfig/network-scripts/ifcfg-enp0s3` being kept by the build process.
Removing this file fixes the issue.
```
==> f28: Setti
jdoss reported a new issue against the project: `cloud-sig` that you are
following:
``
This BZ https://bugzilla.redhat.com/show_bug.cgi?id=1474593 is an example of
an issue that impacts the Vagrant images that would require us to update the
images once a fix is pushed. Due to how Vagrant start
jdoss added a new comment to an issue you are following:
``
17:00 UTC Mondays works for me.
``
To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/280
___
cloud mailing list -- cloud@lists.fedoraproject.org
To u
jdoss added a new comment to an issue you are following:
``
Awesome! OK so were do we start? Do we have a process documented that we can
follow to update images and get them in the right spot?
``
To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/138
___
.
A periodic update to the base image would be a nice quality of life for
Fedora Cloud end users and help put blocker bugs, like the one I linked
above, in the past.
Thanks!
Joe
--
Joe Doss
j...@solidadmin.com
___
cloud mailing list -- cloud
12 matches
Mail list logo
