Attaching EBS volumes to FC-14 / 15
by Dima Brodsky
Hey,
Quick question if anybody knows. Is there a special way to attach EBS volumes to the new FC images that have XEN aware kernels? We can only attach devices as /dev/sd* but FC uses /dev/xvd*. I am having an issue where an EBS volume is in the attaching state for the last 12 hours.
Thanks!
ttyl
Dima
--
ddbrodsky(a)gmail.com
"The price of reliability is the pursuit of the utmost simplicity.
It is a price which the very rich find the most hard to pay."
(Sir Antony Hoare, 1980)
12 years, 6 months
Fedora 16 RC2 AMI's
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hey all,
so we have in us-east a pair of amis that are the fedora 16 release
candidate 2 compose.
i386: ami-fddf1194
x86_64: ami-4ddf1124
i have booted them and install man and made sure that documentation and
languages work. the two main issues identified with the beta.
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAk6tllgACgkQkSxm47BaWfdh+QCgj6ITmsdnHv4F3pQFfg+NG+Yu
G+EAoLred6eGl4IIVPvs0u+/p/qlQNUn
=T+vA
-----END PGP SIGNATURE-----
12 years, 6 months
glusterfs and hekafs release number for f16 and rawhide; systemd switch-over
by Kaleb S. KEITHLEY
Up to now the glusterfs and hekafs versions and releases have been the
same for f16 and rawhide, i.e.: glusterfs-3.2.4-1.x86_64.fc16.rpm,
glusterfs-3.2.4-1.x86_64.fc17.rpm, hekafs-0.7-16.x86_64.fc16.rpm, and
hekafs-0.7-16.x86_64.fc17.rpm.
I did that because the source, thus far, is exactly the same for both
f16 and rawhide. In f16 and rawhide both glusterfs and hekafs used sysv
init.d scripts.
Now for rawhide I'm going to switch to systemd. I know I can't switch to
systemd for f16, so the question is, what scheme should I used for the
release numbering?
One thought I had was to 'leapfrog' increment the release numbers. I
already have: glusterfs-3.2.4-1.x86_64.fc16.rpm and
glusterfs-3.2.4-1.x86_64.fc17.rpm. Then for the systemd version then I'd
go to glusterfs-3.2.4-2.x86_64.fc17.rpm. And if I need to respin
glusterfs I'd use glusterfs-3.2.4-3.x86_64.fc16.rpm and
glusterfs-3.2.4-4.x86_64.fc17.rpm.
I.e:
f16 rawhide
current 3.2.4-1.fc16 [i] 3.2.4-1.fc17 [i]
new... 3.2.4-2.fc17 [s]
3.2.4-3.fc16 [i] 3.2.4-4.fc17 [s]
([i] means init.d, [s] means systemd)
Alternatively I could just add a character to the first release using
sytsemd for rawhide, e.g. 's'. Then I'd have the existing
glusterfs-3.2.4-1.x86_64.fc16.rpm and glusterfs-3.2.4-1.x86_64.fc17.rpm,
and glusterfs-3.2.4-1s.x86_64.fc17.rpm for the new systemd version. And
for a respin then I'd just use systemd going forward for rawhide, and
I'd use glusterfs-3.2.4-2.x86_64.fc16.rpm and
glusterfs-3.2.4-2.x86_64.fc17.rpm.
I.e:
f16 rawhide
current 3.2.4-1.fc16 [i] 3.2.4-1.fc17 [i]
new... 3.2.4-1s.fc17 [s]
3.2.4-2.fc16 [i] 3.2.4-2.fc17 [s]
Whichever I go with I'd do the same thing for hekafs.
Thoughts?
12 years, 6 months