similar to: CentOS-7-x86_64-GenericCloud.raw very unusual format

What you mean is not listed ? Click 1) https://www.centos.org/download/ there click 2) More download choices it goes to 3) https://wiki.centos.org/Download there you see 4) Cloud / Containers , http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw raw files are very useful, they are very convenient to tweak by simply mounting using losetup. And there is no good reason to put 1

On 21 March 2016 at 11:51, Karanbir Singh <mail-lists at karan.org> wrote: > On 21/03/16 14:34, Aliaksei Sheshka wrote: > > What is the point to pack single raw file into the tar.gz and to name it > raw ? > > Or it's just a mistake ? > > > > > > Johnny is looking at the cdn side of thigs, but effectively we will not > have a .raw - we will have a

On 10/10/2016 8:28 AM, Aliaksei Sheshka wrote: > $ wgethttp://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw.xz > --2016-10-10 11:21:32-- > http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw.xz > Resolving cloud.centos.org (cloud.centos.org)... 162.252.80.138, > 2607:1680:0:1::2 > Connecting to cloud.centos.org >

On 21/03/16 15:34, Aliaksei Sheshka wrote: > Hello! > > Is anyone aware why CentOS-7-x86_64-GenericCloud.raw has such unusual format ? > > root at test-srv:~# wget > http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw > --2016-03-21 13:16:31-- > http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw > Resolving cloud.centos.org

> > > Why not a compressed qcow2? > > > > Like: CentOS-7-x86_64-GenericCloud.qcow2c > > > > This way, we can add it as-is to OpenStack Glance, that it will be > > downloaded by demand, when required and, OpenStack Nova will > automatically > > uncompress the image for runtime. > > We do publish a qcow2c, the always updated version ( updated

On 22/03/16 01:06, Martinx - ????? wrote: > On 21 March 2016 at 11:51, Karanbir Singh <mail-lists at karan.org> wrote: > >> On 21/03/16 14:34, Aliaksei Sheshka wrote: >>> What is the point to pack single raw file into the tar.gz and to name it >> raw ? >>> Or it's just a mistake ? >>> >>> >> >> Johnny is looking at the

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of John R Pierce > Sent: Monday, October 10, 2016 1:31 PM > To: centos at centos.org > Subject: Re: [CentOS] CentOS-7-x86_64-GenericCloud.raw very unusual > format > > On 10/10/2016 8:28 AM, Aliaksei Sheshka wrote: > > $ > >

Problem re-appeared again. At that time I'm unable to download Cloud Image linked from https://wiki.centos.org/Download http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw.xz $ wget http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw.xz --2016-10-10 11:21:32-- http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.raw.xz Resolving

On 21/03/16 14:34, Aliaksei Sheshka wrote: > What is the point to pack single raw file into the tar.gz and to name it raw ? > Or it's just a mistake ? > > Johnny is looking at the cdn side of thigs, but effectively we will not have a .raw - we will have a .raw.tar.gz file ( which will itself only have a .raw file compressed inside it ) -- Karanbir Singh +44-207-0999389 |

> > did you look in the directory to see what is there? > > http://cloud.centos.org/centos/7/images/ > Kind of, there is a CentOS-7-x86_64-GenericCloud.raw.tar.gz ( compare with CentOS-7-x86_64-GenericCloud.raw.xz ) But again link is not good, and why put raw disk inside the tar? It would me more natural to have compressed image so one can do {z,bz,xc}cat cloud.raw.xz >

On 11/10/16 03:21, TE Dukes wrote: > Just a question, what exactly are these images? > > I see it mentioned on the CentOS website but not a lot of info on exactly > what it is and what it does. > > How does this differ from a CentOS 7 VM installed from an ISO? Are these > just pre-made images? these are images prebuilt to work in cloud infrastructure like openshift / amazon

I'm using the C7.2 GenericCloud image with KVM and am trying to inject my own ssh key by adding it to /etc/cloud/cloud.cfg.d: sudo virt-customize --upload ~/local/cloud/20_centos_sshkey.cfg:/etc/cloud/cloud.cfg.d/20_centos_sshkey.cfg -d c7-template Contents of the file: #cloud-config ssh_authorized_keys: - ssh-rsa [mysshkeyhere] The good news is that it puts something in the

Good day, I initially posted this issue on CentOS-mirror a week ago but did not receive any response. I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image. As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2 The checksum

I believe the bug lies in libguestfs. Taking out the commands being sent to QEMU and using qemu-img info I can recreate the error: # qemu-img info "rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" qemu-img: Could not open 'rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none': invalid

This worked wonderfully!  What are the odds of getting this upstream in the near future?  I'd rather not build from source in production. # ./run guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir "/root/libguestfs/tmp" libguestfs:

I have scoured the web and can't find anything on the topic: Is IPv6 supported for remote image targets? For example: guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 Does not work citing the following: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x5560231bdfb0, program =

Unfortunately I do need to use the address explicitly as opposed to hostnames because the source of the data fed here is Ceph's monmap which returns the addresses explicitly. I've tried all the common ways to escape the : in the v6 address to no avail.  I definitely agree that the problem looks to be it parsing the colons as if the port comes next and then everything after that is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am pleased to announce general availability of the Feb 2016 snapshot for CentOS Linux. This release includes CentOS Linux 7 iso based install media, Generic Cloud images, Atomic Host, Docker containers, Vagrant images, vendor hosted cloud images. This release set is tag'd 1602 CentOS Linux rolling builds are point in time snapshot media

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Yes... we currently use Packer to achieve a repeatable build process, from scratch. We'd like to replicate that and be able to build from scratch without spinning up an EC2 instance, in an automated way. I don't know how to phrase this, so apologies if it comes across wrong, I have immense respect for you personally and for CentOS... but, is it really that difficult to post the kickstarts