On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:
I'd be in favor of pulling NetworkManager. It still seems that network is
the way for server class systems to handle networking
It's not that simple, at least for Atomic, because the *exact same* tree
in Fedora 22 can also be deployed
On Thu, Mar 19, 2015 at 06:27:13PM -0400, Colin Walters wrote:
On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:
I'd be in favor of pulling NetworkManager.? It still seems that network is
the way for server class systems to handle networking
It's not that simple, at least for
On 2015-03-19 15:41, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
I think Matthew Miller said he added the kickstart file, need to see
what else needs to be done there.
Someone needs to test that it works, and make any needed changes.
Send me the
On 2015-03-19 15:41, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
I think Matthew Miller said he added the kickstart file, need to see
what else needs to be done there.
Someone needs to test that it works, and make any needed changes.
Send me the
On Thu, Mar 19, 2015 at 04:19:33PM -0600, Derek Carter wrote:
On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
I think Matthew Miller said he added the kickstart file, need to see
what else needs to be done there.
Someone needs to test that it works, and make any needed changes.
Hi,
I tested the images locally following the cloud tests. They passed
successfully. But I failed to make them to boot on fed-cloud02.
Before uploading the images I converted them by the following command.
$ qemu-img amend -f qcow2 -o compat=0.10
Fedora-Cloud-Base-21-20150309.x86_64.qcow2
In
I vote for different life-time for different purpose, precisely as David
suggests: scratch, test, RC, Final (Beta).
But let's also don't forget about policy for testing the amis: how long to
keep amis that failed testing in particular release stage.
Ideally, we should also keep track of
On 18/03/15, Pete Travis wrote:
Hey cloud team,
I think we need some cloud docs. Fedora has a lot to offer in the cloud
area, and I'm sure that those engaged in the space are excited that
Fedora has what they are looking for. The uninitiated, on the other
hand, are looking for what Fedora
On 19/03/15, Joe Brockmeier wrote:
On 03/19/2015 01:14 AM, Pete Travis wrote:
So, as I'm working on some tooling for a new Fedora Docs site, I'd like
to know what would get *you* into writing about Fedora Cloud. In the
most direct sense, it's a question about markup and delivery, ie a
On 03/19/2015 12:11 AM, M. Edward (Ed) Borasky wrote:
If you have raw data, I'd be happy to explore it for you - email me
off-list if you need an NDA or something like that.
Any data we have should be shared with all or none. We don't have a
Fedora NDA AFAIK.
Best,
jzb
--
Joe Brockmeier |
On 03/18/2015 06:38 PM, David Gay wrote:
Greetings!
We sort of ran out of time in today's Cloud WG meeting, but I did want
to ask:
What are your thoughts on AMI lifetimes? That is to say, how long should
EC2 AMIs exist before they're deleted? A few points to consider:
I feel like I
On 03/19/2015 08:54 AM, Joe Brockmeier wrote:
On 03/18/2015 06:38 PM, David Gay wrote:
Greetings!
We sort of ran out of time in today's Cloud WG meeting, but I did want
to ask:
What are your thoughts on AMI lifetimes? That is to say, how long should
EC2 AMIs exist before they're deleted? A
On 03/18/2015 06:38 PM, David Gay wrote:
Greetings!
We sort of ran out of time in today's Cloud WG meeting, but I did want to ask:
What are your thoughts on AMI lifetimes? That is to say, how long should EC2
AMIs exist before they're deleted? A few points to consider:
- AMIs only cost
On 19/03/15, Joe Brockmeier wrote:
On 03/19/2015 08:20 AM, Kushal Das wrote:
1. Syntax is almost like markdown.
2. It has more features targeted towards devels.
3. If we maintain in a public git repo, we can use a service like
readthedocs.org to build and publish the docs, we can have
On 03/18/2015 06:13 PM, Matthew Miller wrote:
On Wed, Mar 18, 2015 at 06:04:22PM -0400, Jason Brooks wrote:
* jzb help find scollier additional maintainer for dockerfiles
On this item, I believe that the CentOS folks are interested
in working together on Dockerfiles maintenance. Perhaps
On 03/19/2015 06:22 AM, Kushal Das wrote:
I tested the images locally following the cloud tests. They passed
successfully. But I failed to make them to boot on fed-cloud02.
This is converting b/c images are actually qcow3 and OpenStack doesn't
love qcow3? (or v3 qcow2, if you prefer)
Best,
On 03/19/2015 08:20 AM, Kushal Das wrote:
1. Syntax is almost like markdown.
2. It has more features targeted towards devels.
3. If we maintain in a public git repo, we can use a service like
readthedocs.org to build and publish the docs, we can have it in the way
of
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic and this could be causing some issues we are seeing.
We should probably open a BZ for this. If no one objects I will make
one.
Opened this BZ:
I'd be in favor of pulling NetworkManager. It still seems that network is
the way for server class systems to handle networking.
-Matt M
On Thu, Mar 19, 2015 at 12:47 PM, Dusty Mabe du...@dustymabe.com wrote:
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic
Got excited playing with the images linked from this article:
http://fedoramagazine.org/using-fedora-22-atomic-vagrant-boxes/
But I'm not yet up to speed with the atomic way of dealing with things
and was looking for a more standard dev environment to play with F22.
Is there a non-atomic
Have you looked at http://www.projectatomic.io/docs/gettingstarted/ for a
guide to the atomic way with docker and kubernetes?
On Thu, Mar 19, 2015 at 3:36 PM, Derek Carter goozb...@friocorte.com
wrote:
Got excited playing with the images linked from this article:
On 03/19/2015 03:36 PM, Derek Carter wrote:
Got excited playing with the images linked from this article:
http://fedoramagazine.org/using-fedora-22-atomic-vagrant-boxes/
But I'm not yet up to speed with the atomic way of dealing with things
and was looking for a more standard dev
The latest tree update changed the gid for sshkeys (among other things). It
needs a backport of some rpm-ostree fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1203006
Which are waiting on karma here:
https://admin.fedoraproject.org/updates/rpm-ostree-2015.3-1.fc21
On Thursday, March 19, 2015 08:45:36 AM Joe Brockmeier wrote:
On 03/19/2015 12:11 AM, M. Edward (Ed) Borasky wrote:
If you have raw data, I'd be happy to explore it for you - email me
off-list if you need an NDA or something like that.
Any data we have should be shared with all or none. We
On Thursday, March 19, 2015 08:44:19 AM Joe Brockmeier wrote:
On 03/18/2015 06:13 PM, Matthew Miller wrote:
On Wed, Mar 18, 2015 at 06:04:22PM -0400, Jason Brooks wrote:
* jzb help find scollier additional maintainer for dockerfiles
On this item, I believe that the CentOS folks are
On Thu, Mar 19, 2015 at 7:09 AM, Dennis Gilmore den...@ausil.us wrote:
On Thursday, March 19, 2015 08:45:36 AM Joe Brockmeier wrote:
On 03/19/2015 12:11 AM, M. Edward (Ed) Borasky wrote:
If you have raw data, I'd be happy to explore it for you - email me
off-list if you need an NDA or
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just having the Network service enabled. This would also mean
we can pull the NetworkManager packages out of atomic and make the
image smaller.
I'm in favor.
On 2015-03-19 9:11, milanisko k wrote:
I'd like to ask about the status/plan of SriovNet support[1] for Fedora
Amazon images.
I was able to set this up manually for recent F21 ami ami-5cd9ea41, but
it is quite an inconvenient experience --- one has to instantiate, stop,
set attribute value
On Thursday, March 19, 2015 09:20:55 AM Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of
the work so far on
On 03/19/2015 09:25 AM, Daniel J Walsh wrote:
Scott we found an interesting problem with libvirt protections on
/dev/kvm. If you run this container on an atomic machine, the device
has the wrong protections. You need to add chmod 666 /dev/kvm to make
it work, or
chmod 660 /dev/kvm
chown
On Mar 19, 2015 6:21 AM, Kushal Das kushal...@gmail.com wrote:
On 19/03/15, Joe Brockmeier wrote:
On 03/19/2015 01:14 AM, Pete Travis wrote:
So, as I'm working on some tooling for a new Fedora Docs site, I'd
like
to know what would get *you* into writing about Fedora Cloud. In the
On 03/11/2015 09:40 AM, Major Hayden wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of
the work so far on the Dockerfiles - but also, I think he's looking
for assistance there
Scott we found an interesting problem with libvirt protections on
/dev/kvm. If you run this container on an atomic machine, the device
has the wrong protections. You need to add chmod 666 /dev/kvm to make
it work, or
chmod 660 /dev/kvm
chown root:qemu /dev/kvm
I think this would break on other
On 03/19/2015 07:50 PM, Scott Collier wrote:
On 03/11/2015 09:40 AM, Major Hayden wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2015 09:23 AM, Joe Brockmeier wrote:
I'm CC'ing Scott b/c, if I'm not mistaken, he's done quite a lot of
the work so far on the Dockerfiles - but
On Thu, Mar 19, 2015 at 03:54:24PM -0400, Joe Brockmeier wrote:
I think Matthew Miller said he added the kickstart file, need to see
what else needs to be done there.
Someone needs to test that it works, and make any needed changes.
That someone _might_ be me, but if we want it before next
On Thu, Mar 19, 2015, at 11:19 AM, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 11:10:33AM -0400, Colin Walters wrote:
So dgilmore pointed out that f22 docker images will not have yum
installed - which means we need to update the Dockerfiles for f22 to use
dnf and not yum.
Hello list,
I'd like to ask about the status/plan of SriovNet support[1] for Fedora
Amazon images.
I was able to set this up manually for recent F21 ami ami-5cd9ea41, but it
is quite an inconvenient experience --- one has to instantiate, stop, set
attribute value through the CLI tool and start
On Thu, Mar 19, 2015, at 10:25 AM, Daniel J Walsh wrote:
I think this would break on other machines that do not have libvirt
installed on the host.
Right, it's a problem orthogonal to the Atomic Host.
Scott we found an interesting problem with libvirt protections on
On Thu, Mar 19, 2015 at 11:10:33AM -0400, Colin Walters wrote:
So dgilmore pointed out that f22 docker images will not have yum
installed - which means we need to update the Dockerfiles for f22 to use
dnf and not yum.
Personally, this feels like a lot of pain for little gain to me. We
On 19/03/15, Kushal Das wrote:
Hi,
I tested the images locally following the cloud tests. They passed
successfully. But I failed to make them to boot on fed-cloud02.
As a side note, in the atomic image I am getting one service failed to
load in the first boot, can not see the error after a
Both NetworkManager and network systemd services are enabled in F21
and F22 Atomic and this could be causing some issues we are seeing.
We should probably open a BZ for this. If no one objects I will make
one.
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just
41 matches
Mail list logo
