Re: [Systems] EC2 cost estimates
by Greg DeKoenigsberg
On Sun, 7 Feb 2010, Caroline Meeks wrote:
> Did Amazon say no to donating the service?
Actually, it was Red Hat who was considering donating the service -- but
we're still working out details. :)
--g
> On Thu, Feb 4, 2010 at 7:36 AM, Bernie Innocenti <bernie(a)codewiz.org> wrote:
> Amazon just lowered all prices, do I did some some cost
> estimates for
> the hypothesis of running the bulk of Sugar Labs' public-facing
> and
> development infrastructure on EC2.
>
> In 9 days, the machine running http://activities.sugarlabs.org/
> along
> with a bunch of other low-traffic services received 85.8GB and
> sent
> 103.3GB of data, for a total of 189GB transferred.
>
> In one year, this would become 189/9*365 = 7665GB (7.6TB).
>
> However, these statistics were collected in a period of
> extraordinarily
> low traffic, because schools are closed in Latin America:
>
> http://sunjammer.sugarlabs.org/munin/sugarlabs.org/sunjammer.sugarlabs.org
> -apache_accesses.html
>
> Within two weeks, traffic will return from 150 to 800-1000
> connections
> per minute, a factor 6. Our traffic includes a number of things,
> such as
> backups, which won't grow as much. But we're also expecting the
> popularity of aslo to increase over the next year, so I'd keep
> the 6x
> factor:
>
> 76665GB * 6 = 45990GB (46TB per year)
>
> We're well within the 10TB per month range. So we can expect to
> spend:
>
> 45990 * 0.15 = $6898.50
>
> This is just for bandwidth. Amazon also charges for instance
> hours
> (circa $2000 per year per instance), disk space and IP
> addresses. This
> is the whole story:
>
> http://aws.amazon.com/ec2/#pricing
>
> Depending how fast one instance really is, I'd guesstimate that
> running
> a good chunk of Sugar Labs' development and public-facing
> infrastructure
> on EC2 instances would cost some $10-15K per year. Moving
> everything to
> the cloud would likely cost over $20K per year at current rates.
>
> --
> // Bernie Innocenti - http://codewiz.org/
> \X/ Sugar Labs - http://sugarlabs.org/
>
> _______________________________________________
> Systems mailing list
> Systems(a)lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/systems
>
>
>
>
> --
> Caroline Meeks
> Solution Grove
> Caroline(a)SolutionGrove.com
>
> 617-500-3488 - Office
> 505-213-3268 - Fax
>
>
--
Educational materials should be high-quality, collaborative, and free.
Visit http://opensource.com/education and join the conversation.
14 years, 2 months
Yesterday's kickoff IRC meeting
by Greg DeKoenigsberg
Good stuff. Very productive.
===
First: the Cloud SIG wiki page is now up. It's very rudimentary, but it's
good enough for now.
SIG home: https://fedoraproject.org/wiki/Cloud_SIG
===
Second: the meeting was great, and we have log and minutes for all to
peruse.
Raw Log: http://meetbot.fedoraproject.org/fedora-cloud/2010-02-04/fedora-cloud.201...
Minutes: http://meetbot.fedoraproject.org/fedora-cloud/2010-02-04/fedora-cloud.201...
===
Third: we have the rudiments of a feature page for "Fedora on EC2".
Whether we can get this into the Fedora 13 feature list is up to John
Poelstra, but I think we can make a good case for it:
(a) a lot of the work has been ongoing for quite a while, but has not been
tracked in this particular way;
(b) there's not a great deal of risk to the release itself, since the
handful of meaningful changes to Fedora itself are all in the kernel
anyway, and additional changes are process additions that are largely
independent of current Fedora process (spinning new AMIs and AKIs).
Feature page: https://fedoraproject.org/wiki/Features/FedoraOnEC2
(Note: incomplete draft, patches welcome)
===
Thanks for everyone's participation yesterday. Next meeting will be at
4pm Eastern US time, next Thursday.
--g
--
Educational materials should be high-quality, collaborative, and free.
Visit http://opensource.com/education and join the conversation.
14 years, 2 months
Status of EC2 AMIs for Fedora 12 and beyond?
by John Poelstra
Greetings,
I sat in on a session at FUDCon where there was discussion about getting
the AMIs updated to Fedora 12. Are we tracking those steps and their
status on the wiki anywhere? Can I help with that process?
I'm also curious if we have done any work to map out what needs to
happen and when (a schedule) for Fedora 13 in terms of having Fedora 13
AMIs ready on release day? If there is not a schedule I'd be glad to
help map one out and I'm guessing we need to start on this ASAP?
Who is working on the different pieces right now?
John
14 years, 2 months
Re: Eucalyptus euca2ools RPM -- hey, it's done!
by Garrett Holmstrom
Hi, folks!
I'm waiting on a new release of python-fedora before euca2ools can
make it into cvs, but of course if we need some RPMs for Fedora in the
mean time they are certainly buildable. Making things work on CentOS
will be a bit trickier due to the old Python version, of course, but
if necessary someone could build a repo with the needed Python 2.6 or
2.5 packages.
The euca2ools package that upstream publishes has no chance of working
on Fedora for several reasons:
* It assumes everything with /etc/redhat-release is CentOS and
hardcodes everything for Python 2.5, which breaks both Fedora >= 10
and any CentOS installations that use 2.6 instead.
* It bundles python-boto and m2crypto, which are already in Fedora and EPEL.
* It hardcodes the locations of Python library directories when it
should have Python determine those by itself like the packaging
guidelines desrcibe.
For these reasons I wrote Fedora's euca2ools spec file from scratch.
It ought to be fairly simple to make it work on CentOS by having an
optional "%global python_version" at the top of the spec file and
having that reset the __python variable and any versioned Requires
that are necessary. While I have not looked at the rest of eucalyptus
yet, I suspect much of the same methodology will help clean things up
tremendously and still remain portable.
14 years, 2 months
Eucalyptus
by graziano obertelli
Hello,
I'm part of the Eucalyptus team: we would love to see Eucalyptus in Fedora
Core. What can we do to help? We do already provide RPMs, albeit not for
Fedora Core yet, which I'm sure are not ready to be included in any
distribution, and we know of some of our users already using Eucalyptus in
Fedora Core. Do you think Eucalyptus will fit in your cloud initiative?
cheers,
graziano
--
Graziano Obertelli
Eucalyptus Systems, Inc.
130 Castilian St. Goleta, CA 93117
Phone: 805-570-1647
www.eucalyptus.com
14 years, 2 months
AW: Eucalyptus RPM -- random discussion thread
by Oliver Falk
+1!
----- Ursprüngliche Nachricht -----
Von: Matthew Miller <mattdm(a)mattdm.org>
Gesendet: Dienstag, 2. Februar 2010 18:37
An: Home of the Fedora Cloud SIG <cloud(a)lists.fedoraproject.org>
Betreff: Eucalyptus RPM -- random discussion thread
Question One:
How attached are we to the upstream subpackage names? I'd like of like to
change them to more descriptive names:
eucalyptus-sc -> eucalyptus-storage-controller
eucalyptus-cloud -> eucalyptus-cloud-controller
eucalyptus-cc -> eucalyptus-cluster-controller
eucalyptus-nc -> eucalyptus-node-controller
eucalyptus-gl -> eucalyptus-gatherlog
Does anyone have strong opinions on this?
--
Matthew Miller <mattdm(a)mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Computing & Information Technology
Harvard School of Engineering & Applied Sciences
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
14 years, 2 months