help wanted -- test/karma docker-storage-setup

2014-10-30 Thread Matthew Miller 
As Joe noted the other day, Fedora Atomic is intended to come with this
service, which will create storage space for Docker images. As
mentioned in the IRC meeting, at this point, the plan is to get this to
stable after the beta (before the feature freeze, as soon as possible),
to update the Atomic tree definition, and then to request a test
candidate including it.

But the first step is getting it to stable. So, testers wanted --

https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21

second priority after

http://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test


of course :)



-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-10-30 Thread Dusty Mabe 
On Thu, Oct 30, 2014 at 09:34:32AM -0400, Matthew Miller wrote:
> As Joe noted the other day, Fedora Atomic is intended to come with this
> service, which will create storage space for Docker images. As
> mentioned in the IRC meeting, at this point, the plan is to get this to
> stable after the beta (before the feature freeze, as soon as possible),
> to update the Atomic tree definition, and then to request a test
> candidate including it.
> 
> But the first step is getting it to stable. So, testers wanted --
> 
> https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21
> 

So.. not the easiest thing to test because I couldn't find any atomic
images with this package installed. Here is what I did to test on the atomic
image from http://koji.fedoraproject.org/koji/taskinfo?taskID=7974506 :

cd /tmp/ 
wget 
https://kojipkgs.fedoraproject.org//packages/docker-storage-setup/0.0.3/1.fc21/noarch/docker-storage-setup-0.0.3-1.fc21.noarch.rpm
rpm2cpio docker-storage-setup-0.0.3-1.fc21.noarch.rpm | cpio -idv
cp usr/bin/docker-storage-setup /usr/local/bin/docker-storage-setup
cp usr/lib/systemd/system/docker-storage-setup.service 
/etc/systemd/system/docker-storage-setup.service
sed -i 's|/usr/bin/|/usr/local/bin/|' 
/etc/systemd/system/docker-storage-setup.service
systemctl enable docker-storage-setup.service
systemctl enable docker.service
reboot

After reboot docker was up and running and I was able to pull and run busybox
from the docker registry. Here are the logs:

docker-storage-setup[783]: CHANGED: partition=2 start=1026048 old: size=5265408 
end=6291456 new: size=40916832,end=41942880 
docker-storage-setup[783]: Physical volume "/dev/vda2" changed
docker-storage-setup[783]: 1 physical volume(s) resized / 0 physical volume(s) 
not resized
docker-storage-setup[783]: Rounding up size to full physical extent 20.00 MiB
docker-storage-setup[783]: Logical volume "docker-meta" created
docker-storage-setup[783]: Logical volume "docker-data" created

Hope this helps,

Dusty




___
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: help wanted -- test/karma docker-storage-setup

2014-10-30 Thread Colin Walters 
On Thu, Oct 30, 2014, at 09:12 PM, Dusty Mabe wrote:
> 
> So.. not the easiest thing to test because I couldn't find any atomic
> images with this package installed. 

It is possible to compose trees on your own too, using local packages. A  quick 
HOWTO:

yum install rpm-ostree
cd /srv
git clone https://fedorahosted.org/fedora-atomic/
mkdir /srv/repo
ostree --repo=/srv/repo init --mode=archive-z2
mkdir local-repo
cp /path/to/docker-storage-setup.rpm local-repo
(cd local-repo && createrepo .)
# edit fedora-atomic/fedora-atomic-base.json to add a yum repo pointing to 
/srv/local-repo
rpm-ostree compose tree --repo=/srv/repo 
fedora-atomic/fedora-atomic-docker-host.json

Then set up a static webserver pointing at /srv/repo.  In the client system:

ostree remote add local --set=gpg-verify=false http://192.168.122.1/repo
atomic rebase local:

> rpm2cpio docker-storage-setup-0.0.3-1.fc21.noarch.rpm | cpio -idv
> cp usr/bin/docker-storage-setup /usr/local/bin/docker-storage-setup

That works too though.  Thanks for testing!
___
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: help wanted -- test/karma docker-storage-setup

2014-10-31 Thread Andy Grimm 
On Thu, Oct 30, 2014 at 9:12 PM, Dusty Mabe  wrote:
> On Thu, Oct 30, 2014 at 09:34:32AM -0400, Matthew Miller wrote:
>> As Joe noted the other day, Fedora Atomic is intended to come with this
>> service, which will create storage space for Docker images. As
>> mentioned in the IRC meeting, at this point, the plan is to get this to
>> stable after the beta (before the feature freeze, as soon as possible),
>> to update the Atomic tree definition, and then to request a test
>> candidate including it.
>>
>> But the first step is getting it to stable. So, testers wanted --
>>
>> https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21
>>
>
> So.. not the easiest thing to test because I couldn't find any atomic
> images with this package installed. Here is what I did to test on the atomic
> image from http://koji.fedoraproject.org/koji/taskinfo?taskID=7974506 :
>
> cd /tmp/
> wget 
> https://kojipkgs.fedoraproject.org//packages/docker-storage-setup/0.0.3/1.fc21/noarch/docker-storage-setup-0.0.3-1.fc21.noarch.rpm
> rpm2cpio docker-storage-setup-0.0.3-1.fc21.noarch.rpm | cpio -idv
> cp usr/bin/docker-storage-setup /usr/local/bin/docker-storage-setup
> cp usr/lib/systemd/system/docker-storage-setup.service 
> /etc/systemd/system/docker-storage-setup.service
> sed -i 's|/usr/bin/|/usr/local/bin/|' 
> /etc/systemd/system/docker-storage-setup.service
> systemctl enable docker-storage-setup.service
> systemctl enable docker.service
> reboot
>
> After reboot docker was up and running and I was able to pull and run busybox
> from the docker registry. Here are the logs:
>
> docker-storage-setup[783]: CHANGED: partition=2 start=1026048 old: 
> size=5265408 end=6291456 new: size=40916832,end=41942880
> docker-storage-setup[783]: Physical volume "/dev/vda2" changed
> docker-storage-setup[783]: 1 physical volume(s) resized / 0 physical 
> volume(s) not resized
> docker-storage-setup[783]: Rounding up size to full physical extent 20.00 MiB
> docker-storage-setup[783]: Logical volume "docker-meta" created
> docker-storage-setup[783]: Logical volume "docker-data" created
>
> Hope this helps,
>
> Dusty

Thank you for testing.  You basically tested in the same way that I
developed and demoed it.  :-)  Unfortunately, you gave it karma while
it was still pending, and when the push to testing happened, it reset
the karma to 0.  So please "+1" again.  Thanks!
___
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: help wanted -- test/karma docker-storage-setup

2014-10-31 Thread Dusty Mabe 
On Fri, Oct 31, 2014 at 09:09:41AM -0400, Andy Grimm wrote:
> 
> Thank you for testing.  You basically tested in the same way that I
> developed and demoed it.  :-)  Unfortunately, you gave it karma while
> it was still pending, and when the push to testing happened, it reset
> the karma to 0.  So please "+1" again.  Thanks!

Done
___
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: help wanted -- test/karma docker-storage-setup

2014-11-01 Thread Colin Walters 


On Thu, Oct 30, 2014, at 09:34 AM, Matthew Miller wrote:
> As Joe noted the other day, Fedora Atomic is intended to come with this
> service, which will create storage space for Docker images. As
> mentioned in the IRC meeting, at this point, the plan is to get this to
> stable after the beta (before the feature freeze, as soon as possible),
> to update the Atomic tree definition, and then to request a test
> candidate including it.
> 
> But the first step is getting it to stable. So, testers wanted --
> 
> https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21

Still need one more karma.
___
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: help wanted -- test/karma docker-storage-setup

2014-11-03 Thread Matthew Miller 
On Sat, Nov 01, 2014 at 04:41:35PM -0400, Colin Walters wrote:
> > https://admin.fedoraproject.org/updates/docker-storage-setup-0.0.3-1.fc21
> Still need one more karma.


It's got it now -- should go to stable tonight. Can we get the tree
updated so it includes this and kubernetes (do we also need karma on
https://admin.fedoraproject.org/updates/FEDORA-2014-13940/kubernetes-0.4+-0.9.git8e1d416.fc21
?) and cockpit and whatever else is considered the
state-of-atomic-today?

Once that's ready, we can ask releng for a test candidate.

-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-03 Thread Joe Brockmeier 
On 11/03/2014 11:19 AM, Matthew Miller wrote:
> It's got it now -- should go to stable tonight. Can we get the tree
> updated so it includes this and kubernetes (do we also need karma on
> https://admin.fedoraproject.org/updates/FEDORA-2014-13940/kubernetes-0.4+-0.9.git8e1d416.fc21
> ?) and cockpit and whatever else is considered the
> state-of-atomic-today?
> 
> Once that's ready, we can ask releng for a test candidate.

I thought Colin had made the change required for k8s and Cockpit, but it
didn't seem to get pulled in.

Do we just need to file a ticket with releng for the tc once this is
complete, or...?

Best,

jzb

-- 
Joe Brockmeier | Principal Cloud & Storage Analyst
j...@redhat.com | http://community.redhat.com/
Twitter: @jzb  | http://dissociatedpress.net/



signature.asc
Description: OpenPGP digital signature
___
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: help wanted -- test/karma docker-storage-setup

2014-11-03 Thread Matthew Miller 
On Mon, Nov 03, 2014 at 11:42:22AM -0600, Joe Brockmeier wrote:
> Do we just need to file a ticket with releng for the tc once this is
> complete, or...?

QA normally files the TC tickets, so let's coordinate with them. 


-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-04 Thread Colin Walters 
I backported some changes from fedora-atomic master to f21:
https://git.fedorahosted.org/cgit/fedora-atomic.git/log/?h=f21

Here are 4 patches for spin-kickstarts master for fedora-cloud-atomic.ks.  I 
tried to actually test them against rawhide but hit 
https://bugzilla.redhat.com/show_bug.cgi?id=290

So I backported them to f21 and then I hit a different (presumably anaconda, 
but maybe dracut) bug where it loops forever at shutdown (haven't searched 
for/filed a bug yet).

However if I terminated the VM in imagefactory, the resulting qcow2 works.

To save you all the pain of testing this until we get patches landed, please 
try:
https://alt.fedoraproject.org/pub/alt/fedora-atomic/testing/f21/20141104.0/fedora-atomic-cloud-direct-lvm-walters-20141104.qcow2.gz
From c314ed756cc3579d305867a7da13127fa6ceeb98 Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 08:30:28 -0500
Subject: [PATCH 1/4] cloud-atomic: Use LVM by default in combination with
 docker-storage-setup

This will allow flexible expansion of direct Docker LVM.
---
 fedora-cloud-atomic.ks | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index 2f94492..5b75865 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -24,7 +24,10 @@ services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config
 zerombr
 clearpart --all
 # Atomic differs from cloud - we want LVM
-autopart
+part /boot --size=300 --fstype="xfs"
+part pv.01 --grow
+volgroup atomicos pv.01
+logvol / --size=3000 --fstype="xfs" --name=root --vgname=atomicos
 
 # Equivalent of %include fedora-repo.ks
 ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://kojipkgs.fedoraproject.org/mash/atomic/ --ref=fedora-atomic/rawhide/x86_64/docker-host
-- 
1.8.3.1

From 4fbf117c9819bb618c9a3e0d01a24f53b1ad3241 Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 08:30:58 -0500
Subject: [PATCH 2/4] cloud-atomic: Point to dl.fedoraproject.org

Since this is the repository that's actually getting updates.
---
 fedora-cloud-atomic.ks | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index 5b75865..5ec2dcf 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -30,7 +30,7 @@ volgroup atomicos pv.01
 logvol / --size=3000 --fstype="xfs" --name=root --vgname=atomicos
 
 # Equivalent of %include fedora-repo.ks
-ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://kojipkgs.fedoraproject.org/mash/atomic/ --ref=fedora-atomic/rawhide/x86_64/docker-host
+ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://dl.fedoraproject.org/pub/alt/fedora-atomic/repo --ref=fedora-atomic/rawhide/x86_64/docker-host
 
 reboot
 
-- 
1.8.3.1

From d6b0df5916914921a67b74dcaf0433f8089fb9ec Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 09:07:27 -0500
Subject: [PATCH 3/4] cloud-atomic: We use GRUB2 now instead of extlinux

In order to have one bootloader per architecture for rpmostreepayload.
---
 fedora-cloud-atomic.ks | 15 +--
 1 file changed, 1 insertion(+), 14 deletions(-)

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index 5ec2dcf..b077712 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -16,7 +16,7 @@ user --name=none
 
 firewall --disabled
 
-bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8" --extlinux
+bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8"
 
 network --bootproto=dhcp --device=eth0 --activate --onboot=on
 services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config,cloud-final
@@ -42,10 +42,6 @@ passwd -l root
 # remove the user anaconda forces us to make
 userdel -r none
 
-# Kickstart specifies timeout in seconds; syslinux uses 10ths.
-# 0 means wait forever, so instead we'll go with 1.
-sed -i 's/^timeout 10/timeout 1/' /boot/extlinux/extlinux.conf
-
 # If you want to remove rsyslog and just use journald, remove this!
 echo -n "Disabling persistent journal"
 rmdir /var/log/journal/ 
@@ -125,15 +121,6 @@ echo "---"
 # Note that running rpm recreates the rpm db files which aren't needed/wanted
 rm -f /var/lib/rpm/__db*
 
-
-# This is a temporary workaround for
-# 
-# where sfdisk seems to be messing up the mbr.
-# Long-term fix is to address this in anaconda directly and remove this.
-# 
-dd if=/usr/share/syslinux/mbr.bin of=/dev/vda
-
-
 echo "Zeroing out empty space with fstrim."
 /usr/sbin/fstrim /
 
-- 
1.8.3.1

From cdf0383c05c35d714b6439e2f7a6fa19d856901f Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 09:09:45 -0500
Subject: [PATCH 4/4] cloud-atomic: Drop yum/rpm bi

Re: help wanted -- test/karma docker-storage-setup

2014-11-04 Thread Matthew Miller 
On Tue, Nov 04, 2014 at 08:53:04PM -0500, Colin Walters wrote:
> Here are 4 patches for spin-kickstarts master for fedora-cloud-atomic.ks.  I 
> tried to actually test them against rawhide but hit 
> https://bugzilla.redhat.com/show_bug.cgi?id=290

Applied to master -- I had to update the one about extlinux because an
unrelated change you hadn't pulled. Can you rebase for f21? They don't
apply cleanly -- I think just for minor things but I'll need more focus
than I have right now to do it right. (Will look again tomorrow.)

-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Colin Walters 


On Tue, Nov 4, 2014, at 09:20 PM, Matthew Miller wrote:

> Applied to master -- I had to update the one about extlinux because an
> unrelated change you hadn't pulled. Can you rebase for f21? They don't
> apply cleanly -- I think just for minor things but I'll need more focus
> than I have right now to do it right. (Will look again tomorrow.)

These are the two patches that should go on f21, backported from master.  And 
only the first is really needed.
From 6986a630452bb4ed75dbbdb40c0629d238c1e64b Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 08:30:28 -0500
Subject: [PATCH 1/2] cloud-atomic: Use LVM by default in combination with
 docker-storage-setup

This will allow flexible expansion of direct Docker LVM.
---
 fedora-cloud-atomic.ks | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index 6e10fc0..f881e4d 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -24,7 +24,10 @@ services --enabled=network,sshd,rsyslog,cloud-init,cloud-init-local,cloud-config
 zerombr
 clearpart --all
 # Atomic differs from cloud - we want LVM
-autopart
+part /boot --size=300 --fstype="xfs"
+part pv.01 --grow
+volgroup atomicos pv.01
+logvol / --size=3000 --fstype="xfs" --name=root --vgname=atomicos
 
 ostreesetup --nogpg --osname=fedora-atomic-host --remote=installmedia --url=http://compose-x86-02.phx2.fedoraproject.org/compose/atomic/ --ref=fedora-atomic/f21/x86_64/docker-host
 
-- 
1.8.3.1

From a4eb88794fbcac93c685c282bb54ce3e8080f603 Mon Sep 17 00:00:00 2001
From: Colin Walters 
Date: Tue, 4 Nov 2014 09:09:45 -0500
Subject: [PATCH 2/2] cloud-atomic: Drop yum/rpm bits from %post

While it makes sense to import the GPG key, it has to be done
as part of the treecompose, because it'll drop out of the rpmdb
on the next upgrade.

For yum, it was run as part of the treecompose, not Anaconda, so
there's already no history.
---
 fedora-cloud-atomic.ks | 10 --
 1 file changed, 10 deletions(-)

diff --git a/fedora-cloud-atomic.ks b/fedora-cloud-atomic.ks
index f881e4d..ea28fcf 100644
--- a/fedora-cloud-atomic.ks
+++ b/fedora-cloud-atomic.ks
@@ -152,16 +152,6 @@ echo "RUN_FIRSTBOOT=NO" > /etc/sysconfig/firstboot
 echo "Removing random-seed so it's not the same in every image."
 rm -f /var/lib/random-seed
 
-echo "Cleaning old yum repodata."
-yum history new
-yum clean all
-truncate -c -s 0 /var/log/yum.log
-
-echo "Import RPM GPG key"
-releasever=$(rpm -q --qf '%{version}\n' fedora-release)
-basearch=$(uname -i)
-rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
-
 echo "Packages within this cloud image:"
 echo "---"
 rpm -qa
-- 
1.8.3.1

___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Matthew Miller 
On Wed, Nov 05, 2014 at 10:37:02AM -0500, Colin Walters wrote:
> These are the two patches that should go on f21, backported from master.  And 
> only the first is really needed.

Applied. Don't we also need "Point to dl.fedoraproject.org"?


-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Colin Walters 
On Wed, Nov 5, 2014, at 11:45 AM, Matthew Miller wrote:
> On Wed, Nov 05, 2014 at 10:37:02AM -0500, Colin Walters wrote:
> > These are the two patches that should go on f21, backported from master.  
> > And only the first is really needed.
> 
> Applied. Don't we also need "Point to dl.fedoraproject.org"?

I'd like to get a final confirmation that's what we should do for release 
before we hardcode the URL.  Client systems can at least change that after the 
fact, whereas partitioning is baked 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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Matthew Miller 
On Wed, Nov 05, 2014 at 12:10:40PM -0500, Colin Walters wrote:
> I'd like to get a final confirmation that's what we should do for
> release before we hardcode the URL. Client systems can at least
> change that after the fact, whereas partitioning is baked in.

Who are the stakeholders for that final decision? Cloud WG, releng,
infrastructure, mirrors? Let's get it made quickly.

In the meantime, I'd argue that changing it for the test candidates is
a step forward from the internal URL.

-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Matthew Miller 
On Wed, Nov 05, 2014 at 12:20:38PM -0500, Matthew Miller wrote:
> Who are the stakeholders for that final decision? Cloud WG, releng,
> infrastructure, mirrors? Let's get it made quickly.
> 
> In the meantime, I'd argue that changing it for the test candidates is
> a step forward from the internal URL.

Although obviously we need it to be more than rawhide.


-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Matthew Miller 
On Wed, Nov 05, 2014 at 12:22:33PM -0500, Matthew Miller wrote:
> > In the meantime, I'd argue that changing it for the test candidates is
> > a step forward from the internal URL.
> Although obviously we need it to be more than rawhide.

And also -- we _want_ it to hit the internal URL in koji but be
configured to access the outside URL after, right? So, that should be
changed in %post, I guess?

-- 
Matthew Miller

Fedora Project Leader
___
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: help wanted -- test/karma docker-storage-setup

2014-11-05 Thread Colin Walters 


On Wed, Nov 5, 2014, at 04:11 PM, Matthew Miller wrote:
> On Wed, Nov 05, 2014 at 12:22:33PM -0500, Matthew Miller wrote:
> > > In the meantime, I'd argue that changing it for the test candidates is
> > > a step forward from the internal URL.
> > Although obviously we need it to be more than rawhide.
> 
> And also -- we _want_ it to hit the internal URL in koji but be
> configured to access the outside URL after, right? So, that should be
> changed in %post, I guess?

Right.  This is a complex topic, because when I wrote the original Anaconda 
rpmostreepayload patches, I had been thinking of a boot.iso scenario, whereas 
it's awkward for the ImageFactory-on-server.

The short answer is to change it in %post.

The long term answer is for Anaconda's rpmostreepayload to be aware of the 
distinction between "distribution side" composes and downstream composes.  (And 
for that matter, for Anaconda itself to understand this.  We shouldn't have to 
rm /var/lib/systemd/random-seed in %post)
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct