Good News, Everybody!
KB let me know today that we've got some images of the rebuild of RHEL Atomic Host ready to test.
You can find images here:
http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
This includes 2 flavors of Vagrant box (libvirt/KVM and VirtualBox), a qcow2 image, and ISO image suitable for installing onto bare metal or other environments.
We've done some preliminary testing but more is needed. We're hoping to announce next week, so I'd invite all interested parties to test these and let us know if you find any anomalies.
Best,
jzb
On 06/18/2015 03:49 PM, Joe Brockmeier wrote:
Good News, Everybody!
KB let me know today that we've got some images of the rebuild of RHEL Atomic Host ready to test.
You can find images here:
http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
This includes 2 flavors of Vagrant box (libvirt/KVM and VirtualBox), a qcow2 image, and ISO image suitable for installing onto bare metal or other environments.
We've done some preliminary testing but more is needed. We're hoping to announce next week, so I'd invite all interested parties to test these and let us know if you find any anomalies.
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
On Thu, Jun 18, 2015, at 09:43 PM, Jim Perrin wrote:
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
I've been working on this. It's triggered a few issues becuase up until now, we haven't tried to ship a remote config in a package (that then gets committed to the tree).
This is the *right* way to do it, and I'd like to switch to doing so in Fedora as well. CentOS is leading a bit here and there's an ostree bug https://bugzilla.gnome.org/show_bug.cgi?id=751188 that makes it not quite work. I hacked around it with a custom Anaconda patch for this rebuild.
In addition there was a bug in rpm-ostree-toolbox, a patch for which I'm just building now: https://cbs.centos.org/koji/taskinfo?taskID=15240 Which is built from: http://pkgs.fedoraproject.org/cgit/rpm-ostree-toolbox.git/commit/?id=1c08587...
KB, want to give it a try? I tested it locally and got an installer with a remote.
On 19/06/15 03:11, Colin Walters wrote:
On Thu, Jun 18, 2015, at 09:43 PM, Jim Perrin wrote:
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
I've been working on this. It's triggered a few issues becuase up until now, we haven't tried to ship a remote config in a package (that then gets committed to the tree).
Build now live at http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
sha256: bfd773fbec8fe15f58e9bb01d91809d2ccc9671079b2dff572d08ab607b12acf
filename: centos-atomic-host-7-build_02.iso
I've verified the issue is now resolved.
On 06/19/2015 02:41 AM, Karanbir Singh wrote:
On 19/06/15 03:11, Colin Walters wrote:
On Thu, Jun 18, 2015, at 09:43 PM, Jim Perrin wrote:
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
I've been working on this. It's triggered a few issues becuase up until now, we haven't tried to ship a remote config in a package (that then gets committed to the tree).
Build now live at http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
sha256: bfd773fbec8fe15f58e9bb01d91809d2ccc9671079b2dff572d08ab607b12acf
filename: centos-atomic-host-7-build_02.iso
I've verified the issue is now resolved.
Using the new iso now. It seems cockpit-bridge isn't included by default. This is causing a bit of an issue for me as it means the cockpit container (shamelessly adapted from fedora) can't function. The logs for cockpit say that the bridge tools must be installed on the host. Would anyone have a way around this? Is it possible to put the cockpit-bridge-* packages in a container and run that way?
Ideally I'd like to have this ready to roll for Dockercon, but I'm stuck on this bit.
On 19/06/15 20:50, Jim Perrin wrote:
On 06/19/2015 02:41 AM, Karanbir Singh wrote:
On 19/06/15 03:11, Colin Walters wrote:
On Thu, Jun 18, 2015, at 09:43 PM, Jim Perrin wrote:
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
I've been working on this. It's triggered a few issues becuase up until now, we haven't tried to ship a remote config in a package (that then gets committed to the tree).
Build now live at http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
sha256: bfd773fbec8fe15f58e9bb01d91809d2ccc9671079b2dff572d08ab607b12acf
filename: centos-atomic-host-7-build_02.iso
I've verified the issue is now resolved.
Using the new iso now. It seems cockpit-bridge isn't included by default. This is causing a bit of an issue for me as it means the cockpit container (shamelessly adapted from fedora) can't function. The logs for cockpit say that the bridge tools must be installed on the host. Would anyone have a way around this? Is it possible to put the cockpit-bridge-* packages in a container and run that way?
Ideally I'd like to have this ready to roll for Dockercon, but I'm stuck on this bit.
can you try the cockpit container from the redhat registry ? see how that is setup ( and will also have the same cockpit version as we do in Extras )
On 19/06/15 02:43, Jim Perrin wrote:
On 06/18/2015 03:49 PM, Joe Brockmeier wrote:
Good News, Everybody!
KB let me know today that we've got some images of the rebuild of RHEL Atomic Host ready to test.
You can find images here:
http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/
This includes 2 flavors of Vagrant box (libvirt/KVM and VirtualBox), a qcow2 image, and ISO image suitable for installing onto bare metal or other environments.
We've done some preliminary testing but more is needed. We're hoping to announce next week, so I'd invite all interested parties to test these and let us know if you find any anomalies.
There's no remote defined in /etc/ostree/remotes.d. Is this intentional for the beta/re-release?
not intentional, and its not an issue in most of the media - only the baremetal installer had this issue. Am going to roll in the patches from Colin and do another build shortly.