hello - probably i'm on the wrong 'list' but will give this one a try
- are there any job ongoing for to have the webmail program
'Squirrelmail' available on 'yum'?
-- -
rgds,
glenn.
hi,
I've created a new project at http://bugs.centos.org/ to handle and work
with all the cloud instance specific issues.
so far, its got 2 components: cloud-init, cloud-utils. If needed we can
add components for each environment we target, or hope to target.
regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi
I've just pushed a GenericCloud image, that will become the gold
standard to build all varients and environ specific images from.
Requesting people to help test this image :
http://cloud.centos.org/centos/7/devel/CentOS-7-x86_64-GenericCloud-2014082…
( ~ 922 MB)
or
http://cloud.centos.org/centos/7/devel/CentOS-7-x86_64-GenericCloud-2014082…
( 261 MB)
Sha256's;
3c049c21c19fb194cefdddbac2e4eb6a82664c043c7f2c7261bbeb32ec64023f
CentOS-7-x86_64-GenericCloud-20140826_02.qcow2
4a16ca316d075b30e8fdc36946ebfd76c44b6882747a6e0c0e2a47a8885323b1
CentOS-7-x86_64-GenericCloud-20140826_02.qcow2.xz
please note: these images contain unsigned content ( cloud-init and
cloud-utils-* ), and are therefore unsuiteable for use beyond validation
on your environment.
Also note, that the desktop Generic image will eventually have
cloud-init removed ( but not cloud-utils ). If thats hard to achieve,
then we might want to ship a pre-setup config drive or a built in
datasource in the image itself.
regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Now that we have a working CentOS 7 tree and process for putting Red Hat
Sources onto git.centos.org, we are going to start a process to figure
out how to import CentOS-6 Sources onto git.centos.org as well.
We will be starting with sources from 6.0 ISOs all the way through
current CentOS-6+updates.
We do not have a specific time line for this to happen, but we will be
generating the SRPM lists (in order) that we will likely use to populate
original RHEL SRPMs (for non modified packages) and the CentOS SRPMs
(for modified packages), and the correct order to make it happen.
We will be posting those lists for review/correction to both the CentOS
QA IRC channel and this mailing list.
We will also be upgrading to a new version of gitblit for git.centos.org
before we actually roll in the CentOS-6 sources, though I will begin the
list generation before we actually start the gitblit upgrade process.
Thanks,
Johnny Hughes
Given that work on a docker image for CentOS 7 in AWS is being worked on,
where does this leave the status of the standard CentOS 7 AMI? It's been
almost 2 months since release, and almost every other major cloud provider,
except the most popular one, has the image available to deploy in their
environments.
Can we get a status update on this, or is there anything we as the
community can do to help, including collaborating with AWS for those of us
that utilize their business level support to help get any testing or
technical roadblocks removed?
--
*Cheers,*
*___________________________*________
*TheaterMania.com <http://www.theatermania.com> | OvationTix.com
<http://www.ovationtix.com>*
*Sena Heydari, Dev Ops and Infrastructure Manager*
*1156 Avenue of the Americas New York, NY 10036*
*Phone:* +1-646-500-8309
Hi,
please note : this is an Alpha1 grade build. Its only suiteable for
developing the ostree tools, and bootstrapping the atomic SIG content
for CentOS Atomic.
http://cloud.centos.org/centos/7/devel/CentOS-7-Atomic-DockerHost-20140826_…
sha256:
0fad83f41c511cfe939459a83985a6c12367e76790031258635b9394136988dc
CentOS-7-Atomic-DockerHost-20140826_02.qcow2.xz
signed sums: http://cloud.centos.org/centos/7/devel/sha256sum.txt.asc
sha256 for the signed sha's:
16c8b9d6befb126f07f54c3c970374648bccc04a8ca12ac776bc60b5f7d52687
sha256sum.txt.asc
Notes:
1 these images contain unsigned content
2 these images contain content not hosted or built at centos.org
3 you need to boot the image, with a configdrive attached; the images
contain cloud-init that will then setup auth and metadata
4 the primary function target for this image is docker
5 please test extensive and report issues here to this mailing list,
including depoying to various environments and also functional test the
ostree mechanics, and how it impacts local yum and typical deployment
process / lifecycle management
6 the only testing that is being done for these images from buildsys to
release is that they boot and ssh service comes up. please contribute
tests !
7 there is no upstream ostree repo as yet, I will get something setup on
cloud.centos.org under devel/ or testing/ with the next build
8 Aim to rerun builds every 2 days as we stabalise content and import
into centos.org
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Hi,
has anyone looked at the cloud-utils stack for Atomic ? at the moment
were stuck with a 8gb disk image, I've got a patch that lets me change
that on the build time side of things. But before i upstream it, I was
going to try cloud-utils and that fails quite badly in a dynamic backing
store setup like AWS.
Has anyone had a look at what the issues might be and if its worth poking ?
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Hi,
One of the corner case challenges that I have on the builders that do
the chained instance, images, media builds is that they consume an
internal mirror - but a generic mirror. i.e updates during the day can
result in the images that are built later to end up with different
content ( for the ones that consume the updates/ repo etc )
To work around this, I'm proposing running a mirror closer to the
image-buildsys machine, that only updates at midnight UTC, and will
represent the state of play on the calendar date before the timestamped
images. eg. the CentOS-7-x86_64-Generic-2014_08_26.qcow2 image will
contain updates upto and including all content released till the 25th
midnight.
Its likely easier to make this private. But is there value in having
this be public ? its only going to be a single node ?
Also, longer term we might need / want to chain this from
ci.dev.centos.org runs, so we only include content thats been through
the ci process.
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
hi,
CentOS 7 Atomic Cloud Docker Host AMI's are up, and I'm looking for
people to help test these before we do a wider released.
These images are marked Alpha1 grade. Only built for us-east-1 at this
point.
Please email me at directly ( kbsingh at centos.org ) with an amazon aws
account id ( 12 digit number ) and I'll add you to the testers-list with
access to the ami's.
Major issues outstanding:
* need to redo the image build process to not use partitions, but to
consume the entire block device
* resolve issues for pv booting ( create a fudged grub setup that works
for pv-grub expecting grub < 2 )
Other things:
* we need to get a centos-release-atomic built and pushed
* consolidate the srpms into git.centos.org
* get cockpit working and included in this stack
Regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc