Draft/RFC: What Aeolus is not
by Matt Wagner
Hi all,
After discussing the "What Is Aeolus?" document / mission statement, and
after reading an article about Aeolus that got a few technical details
wrong, it occurred to me that, in addition to "What Is Aeolus?", we
might want a "What Aeolus Is NOT" page.
Here's a quick stab at that. Obviously, I didn't set out to make a
complete list of things Aeolus is not (a trombone, pecan pie, etc.), but
I tried to focus on possible/common misconceptions. Could you let me
know if (a) the below is accurate and reasonably complete, and (b) if
you think it makes sense to have such a list or not?
* Aeolus is not a part of Linux. Although our packaging efforts
currently focus on Linux, Aeolus is not explicitly tied into Linux. It
is a suite of applications that run on Linux and related operated
systems.
(I struggled with how to word this one. I read an article that seemed to
imply Aeolus was a kernel module for the cloud or something of the sort,
which is the idea I'm trying to dispel.)
* Aeolus is not owned by Red Hat. Although the majority of Aeolus
developers are currently sponsored by Red Hat, the project is an
independent community effort.
* Aeolus is not a cloud. Aeolus is a project for managing existing
clouds (public and private), not an attempt at creating yet another
one.
-- Matt
12 years, 7 months
- 3
- 2