euca2ools
by Jan Pazdziora
On Wed, Nov 03, 2010 at 10:36:19AM -0500, Garrett Holmstrom wrote:
>
> euca2ools aims to be an open source drop-in replacement for most of
> ec2-*-tools. While you folks are working with your images, please try
> installing the euca2ools package and running euca-attach-volume instead
> of ec2-attach-volume, euca-run-instances instead of ec2-run-instances,
> and so forth so we can get things working without needing to install
> proprietary bits from Amazon.
Thank you for pointing this out. I've tried
$ euca-describe-instances
EC2_ACCESS_KEY environment variable must be set.
Connection failed
while having EC2_CERT and EC2_PRIVATE_KEY setup and in shell where
ec2-describe-instances works. The man euca-describe-instances(1) says
that
Euca2ools will use the environment variables EC2_URL, EC2_ACCESS_KEY,
EC2_SECRET_KEY, EC2_CERT, EC2_PRIVATE_KEY, S3_URL, EUCALYPTUS_CERT by
default.
Is there anything else I need to have setup beyond EC2_CERT and
EC2_PRIVATE_KEY?
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
13 years, 5 months
fedora-14-x86_64-S3.ec2: AMIs with instance-store root device not supported for 't1.micro' ???
by sean darcy
Amazon has started offering a year free trial: Ihttp://aws.amazon.com/free.
So I'm trying to get my first instance ever running on ec2. I'm trying
to use the x86-64 ami from
https://fedoraproject.org/wiki/Cloud_SIG/EC2_Images.
But:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances
ami-e291668b -k pstam-keypair
Client.InvalidParameterValue: The requested instance type's
architecture (i386) does not match the architecture in the manifest
for ami-e291668b (x86_64)
Supposedly the Micro instance in the free trial supports both 32 and 64 bit:
Micro Instance
613 MB memory
Up to 2 EC2 Compute Units (for short periodic bursts)
EBS storage only
32-bit or 64-bit platform
I/O Performance: Low
API name: t1.micro
I tried:
/opt/amazon/webservices/ec2-api-tools-1.3-57419/bin/ec2-run-instances
ami-e291668b -t t1.micro -k pstam-keypair
Client.UnsupportedOperation: AMIs with an instance-store root device
are not supported for the instance type 't1.micro'.
The 386 ami works.
Am I doing something wrong, or does F14 64-bit image just not work as
a micro instance?
sean
13 years, 5 months
FC 14 root partition size
by Dima Brodsky
Hi,
First, want to say a big thank you for making FC 14 available on EC2,
very much appreciated.
Second, when I booted the new FC 14 image it came up with a 2GB root
partition. Is there any way to increase this parition to say 10gig,
and if not, what approach should one take with respect to installing
packages, etc, since I don't think that 2GB will be sufficient.
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)
13 years, 5 months
Hey Cloud SIG, let's start talking about F15.
by Robyn Bergeron
We are just a few weeks away from the Fedora 14 release, and actually
having a new version of Fedora on EC2. This has been *the* major goal
over the past, well, 10 months since this list was created, and I'm
delighted that it is finally coming together. (Thank you, Justin, for
doing all of this work, and everyone else who has been working on
supporting his efforts and helping out with behind-the-scenes stuff
like talking to Amazon and writing documentation and asking
questions!)
Of course, this is Fedora, and I know a lot of us are thinking about
*what we can do next*. So I'd like to have a discussion here on our
friendly mailing-list about some of the things we'd like to do in F15
(and beyond!).
First off: We have a lot of stuff in the pipeline that I think we
could submit to the Feature List for Fedora 15. What is this "stuff,"
you might ask?
* OpenStack - We already have the Swift portion of this in, and Nova
is in the pipeline. (Thanks, silassewell.) http://www.openstack.org
* Deltacloud - I'm not sure how far along this is, or if it's possible
that this could be fully in for F15, or if there are clearly definable
portions that could be F15 features. Anyone from Deltacloud - can you
pipe in here? :) http://deltacloud.org/
* BoxGrinder - Marek Goldmann is working on packaging.
http://www.jboss.org/boxgrinder
* Eucalyptus - obino has been looking for some mentorship as far as
packaging goes. If there are folks around to help out with this, I
think it would be awesome to have as a feature. Is anyone willing to
help out here? http://open.eucalyptus.com/
* Sheepdog - Steven Dake is working on this. http://www.osrg.net/sheepdog/
Additionally, we probably have further enhancements we could make on
the EC2 front - namely, having really awesome documentation, which
Sparks has been poking the list on since he'd love to help us out
there. What other EC2-related enhancements are there for us to tackle?
But what I am interested in is - what do YOU guys think about what we
could, or even *should*, be doing? Are there other cloud tools,
implementations, projects, etc. we should be looking at? What are
they? What should Fedora's ongoing cloud-sig focus be?
Yes, I know, I'm full of questions. :)
Cheers,
-Robyn
13 years, 5 months
Cloud SIG Meeting Minutes - 2010/11/04
by Robyn Bergeron
Hey folks,
Just a few highlights here:
* Currently supported F14 EC2 images can be seen here:
https://fedoraproject.org/wiki/Cloud_SIG/EC2_Images
* F15 Feature Submission deadline is 1/25/2011. If you're doing a
feature that is cloud-related, please let the mailing list know so we
can start keeping track of progress and get you help if needed.
* FUDCon is shaping up to have a lot of cloud SIG folks in attendance
- if you're interested in attending, please check out
https://fedoraproject.org/wiki/FUDCon:Tempe_2011.
Meeting minutes follow below. Thanks for coming!
-Robyn
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2010-11-04/fedora-meeting...
Full Log: http://meetbot.fedoraproject.org/fedora-meeting/2010-11-04/fedora-meeting...
==========================
#fedora-meeting: Cloud_SIG
==========================
Meeting started by jforbes at 21:04:49 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2010-11-04/fedora-meeting...
.
Meeting summary
---------------
* roll call (jforbes, 21:05:04)
* EC2 status (jforbes, 21:05:53)
* FUDCon Tempe (rbergeron, 21:30:07)
* If you are planning on doing a session, please add it to the FUDCon
wiki page (rbergeron, 21:31:15)
* LINK: http://fedoraproject.org/wiki/FUDCon:Tempe_2011 (rbergeron,
21:31:25)
* F15 Schedule (rbergeron, 21:31:51)
* LINK: http://fedoraproject.org/wiki/Schedule (rbergeron, 21:32:11)
* Feature submission deadline is 1/25/2011 (rbergeron, 21:32:19)
* LINK: http://fedoraproject.org/wiki/FeatureList (rbergeron,
21:34:34)
* ACTION: jforbes and mgoldmann to get together on some featurelist
guidance for BoxGrinder, silassewell can ping jforbes for help as
well (rbergeron, 21:37:25)
* If anyone else is planning on submitting features, please drop a
note on list so we can start keeping track! (rbergeron, 21:39:25)
* Possible new meeting time (rbergeron, 21:39:33)
* LINK:
http://lists.fedoraproject.org/pipermail/cloud/2010-October/000320.html
(rbergeron, 21:40:27)
* ACTION: rbergeron to mail harish about maybe a once a month meeting
on different time - it's just already impossible to schedule this
meeting (rbergeron, 21:47:10)
* Any other Business? (rbergeron, 21:48:21)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=649495
(rbergeron, 21:52:23)
* please help out with reviewing / giving feedback on openstack-nova
(rbergeron, 21:52:35)
Meeting ended at 21:56:34 UTC.
Action Items
------------
* jforbes and mgoldmann to get together on some featurelist guidance for
BoxGrinder, silassewell can ping jforbes for help as well
* rbergeron to mail harish about maybe a once a month meeting on
different time - it's just already impossible to schedule this meeting
Action Items, by person
-----------------------
* jforbes
* jforbes and mgoldmann to get together on some featurelist guidance
for BoxGrinder, silassewell can ping jforbes for help as well
* mgoldmann
* jforbes and mgoldmann to get together on some featurelist guidance
for BoxGrinder, silassewell can ping jforbes for help as well
* rbergeron
* rbergeron to mail harish about maybe a once a month meeting on
different time - it's just already impossible to schedule this
meeting
* silassewell
* jforbes and mgoldmann to get together on some featurelist guidance
for BoxGrinder, silassewell can ping jforbes for help as well
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* rbergeron (79)
* jforbes (33)
* mgoldmann (31)
* sgordon (15)
* jgreguske (10)
* brianlamere (8)
* silassewell (6)
* zodbot (3)
* eric-smith (3)
* mmcgrath (1)
* eric-smith_ (1)
* smooge (1)
* ke4qqq (1)
* mmorsi (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
13 years, 6 months
Other cloud providers - Fedora on things other than EC2 + marketing
by Robyn Bergeron
Hey folks,
rackerhacker (who, for the record, is a Rackspace employee, as well as
a Fedora fan :D) pinged me on IRC and talked to a few other people as
well about the idea of marketing not just Fedora on EC2, but also
Fedora on $otherproviders as well. I think we all can agree that
while getting things up on EC2 (thanks, Justin!!) was an important
first step, but there are obviously other providers out there as well,
including some that already have F14 available for their customers -
and it's certainly a place where we can benefit from advertising as
well.
I know that this past time around, having Fedora on EC2 was an actual
feature. Going forward, do we want to have that as a feature that is
more general - such as Fedora on Many Providers? Or do we want to take
the opportunity to talk about things in an interim fashion *now* and
maybe do something such as a press piece talking about Fedora on
Rackspace (or any other provider, heck, I'd be happy to keep talking
it up for months)? Or perhaps both is a good idea?
Looking for your thoughts! I'll also add it to this week's meeting agenda.
Cheers,
Robyn
13 years, 6 months
"yum check" error with ami-669f680f
by Eric V. Smith
I'm not sure if this is the correct place to report this. If not, please
let me know a more appropriate place.
If I fire up an instance of ami-669f680f
(fedora-images-us-east-1/fedora-14-i386-S3.ec2.manifest.xml) and the
first command I run is "yum check", I get:
$ yum check
ec2-ami-tools-1.3-57676.noarch has missing requires of rsync
ec2-ami-tools-1.3-57676.noarch has missing requires of ruby
Error: check all
$
I can manually install these and the error goes away, but presumably
there shouldn't be an error with the image.
Eric.
13 years, 6 months
