Deltacloud aggregator on F14
by Steve Gordon
Hi all,
Has anyone had any success installing the Deltacloud aggregator on F14?
I am trying to do it using the repo at
http://repos.fedorapeople.org/repos/deltacloud/appliance/fedora-14/ but
the RPMs there appear to just be the f13 ones copied into a new folder.
In particular attempting to install the aggregator (or more
specifically, deltacloud-configure as per the instructions at
http://deltacloud.org/download.html) results in dependency issues:
Error: Package:
deltacloud-aggregator-0.0.2-0.fc13.20101029150259gitfe3ae28.x86_64
(fedora-appliance)
Requires: libclassad.so.0()(64bit)
Error: Package: iwhd-1.0-1.fc13.x86_64 (fedora-appliance)
Requires: libboost_thread-mt.so.1.41.0()(64bit)
Error: Package: python-imgcreate-031-1.fc12.1.x86_64 (fedora-appliance)
Requires: python(abi) = 2.6
Installed: python-2.7-8.fc14.1.x86_64 (@fedora)
python(abi) = 2.7
Available: python3-3.1.2-14.fc14.i686 (fedora)
python(abi) = 3.1
Error: Package: iwhd-1.0-1.fc13.x86_64 (fedora-appliance)
Requires: libboost_system-mt.so.1.41.0()(64bit)
Any suggestions,
Steve
--
------------------------------------------------------
Red Hat Asia Pacific Pty Ltd
Level 1, 193 North Quay, Brisbane, QLD 4000, Australia
www.apac.redhat.com
------------------------------------------------------
13 years, 7 months
stopping an instance on ec2: redirect? wrong instance states reported?
by André Dietisheim
Hi
I stumbled upon behavior in the deltacloud API that I did not expect:
I started an instance in the AWS console, and went to the deltacloud
tools. I then stopped the instance and the following behaviour differs
from what I'd have expected:
- after stopping the instance, the response from the deltacloud server
states that the instance is STOPPED. Chatting to bbrowing in the IRC
showed me that stopping ec2 instances results in destroying them. If
this is the way things have to be, I would have expected state DESTROYED
in the response. Any objections, ideas, hints?
- when I tried to start it again, I recieved a 302. I'd expect a 404
here since this is a client error (4xx) and more specifically, the
resource I address does not exist. Agree?
Thanks!
Cheers
André
13 years, 7 months