9:58 p.m.
Hi everyone,
Based on some feedback from the IRC meeting yesterday, I've scaled back
the changes needed from oVirt for the download page and designed an
alternate that we could use for the immediate future.
http://people.redhat.com/glesage/oVirt/website/mockup-1/download-alt.html
It's based on what is currently on oVirt.org, with some minor changes:
• simplification of the installation steps
• inclusion of system requirements and some summary text at the top
As I wanted to communicate what each section would say, I wrote some
filler text that should be somewhat close to the idea of what we might
want to use. However, the text on this page is very rough in comparison
to the other pages, so please keep this in mind.
Also, I should note that the original download design (for comparison)
is at:
http://people.redhat.com/glesage/oVirt/website/mockup-1/download.html
...and the background thoughts behind the original download page are at:
http://people.redhat.com/glesage/oVirt/website/background-info/design-dow...
Thanks! I'm looking forward to your feedback!
Garrett
10:19 p.m.
Garrett,
This is great: it's clean, it's visually appealing, and it's concise.
Finding non-Fedora distro instructions is easy, and the fact that the page
solicits help for other distributions makes it (hopefully) apparent that
it's not just a Fedora/RHEL party.
Jon
--
Jon Benedict
Technical Marketing Engineer
Red Hat Technologies
Data Center Platforms
Blog http://captainkvm.com | Twitter @CaptainKVM
On 9/6/12 2:58 PM, "Garrett LeSage" <garrett(a)redhat.com> wrote:
Hi everyone,
Based on some feedback from the IRC meeting yesterday, I've scaled back
the changes needed from oVirt for the download page and designed an
alternate that we could use for the immediate future.
http://people.redhat.com/glesage/oVirt/website/mockup-1/download-alt.html
It's based on what is currently on oVirt.org, with some minor changes:
€ simplification of the installation steps
€ inclusion of system requirements and some summary text at the top
As I wanted to communicate what each section would say, I wrote some
filler text that should be somewhat close to the idea of what we might
want to use. However, the text on this page is very rough in comparison
to the other pages, so please keep this in mind.
Also, I should note that the original download design (for comparison)
is at:
http://people.redhat.com/glesage/oVirt/website/mockup-1/download.html
...and the background thoughts behind the original download page are at:
http://people.redhat.com/glesage/oVirt/website/background-info/design-down
load.html
Thanks! I'm looking forward to your feedback!
Garrett
_______________________________________________
Board mailing list
Board(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/board
12:33 a.m.
On 09/06/2012 11:58 AM, Garrett LeSage wrote:
Hi everyone,
Based on some feedback from the IRC meeting yesterday, I've scaled back
the changes needed from oVirt for the download page and designed an
alternate that we could use for the immediate future.
This looks very nice, Garrett.
Some comments/thoughts:
The minimum RAM for ovirt is 4GB. You can get by with less, but the
engine-setup script won't run if it detects less RAM. There is a command
line argument, --no-mem-check, that disables the minimum memory check.
If we're going for simplicity, we may want to go with the
ovirt-engine-setup-plugin-allinone as the suggested package to install.
This way, you come out of these directions ready to create and run VMs.
For a complete setup, it may be that the steps required are too many to
include on this page. We could link to the quick start guide here:
http://wiki.ovirt.org/wiki/Quick_Start_Guide.
Right now, oVirt only works with Fedora and CentOS/RHEL. We shouldn't
give people the wrong idea about multi-distro possibilities. Someone
could get the engine app running on jboss on a different platform, but
vdsm, an essential component for doing anything w/ ovirt, is very much
tied to fedora/el right now.
I really like the "you can help us make ovirt easy to run everywhere"
link -- we need that help!
http://people.redhat.com/glesage/oVirt/website/mockup-1/download-alt.html
It's based on what is currently on oVirt.org, with some minor changes:
• simplification of the installation steps
• inclusion of system requirements and some summary text at the top
As I wanted to communicate what each section would say, I wrote some
filler text that should be somewhat close to the idea of what we might
want to use. However, the text on this page is very rough in comparison
to the other pages, so please keep this in mind.
Also, I should note that the original download design (for comparison)
is at:
http://people.redhat.com/glesage/oVirt/website/mockup-1/download.html
...and the background thoughts behind the original download page are at:
http://people.redhat.com/glesage/oVirt/website/background-info/design-dow...
Thanks! I'm looking forward to your feedback!
Garrett
_______________________________________________
Board mailing list
Board(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/board
--
@jasonbrooks
11:01 a.m.
Hi,
On 09/11/2012 11:33 PM, Jason Brooks wrote:
Right now, oVirt only works with Fedora and CentOS/RHEL. We
shouldn't
give people the wrong idea about multi-distro possibilities. Someone
could get the engine app running on jboss on a different platform, but
vdsm, an essential component for doing anything w/ ovirt, is very much
tied to fedora/el right now.
While I accept that this is the current situation, I think we definitely
want to give people the impression on the website that this is not a Red
Hat only virtualisation manager - yes, there's work to be done to
integrate it on other distros, but we are more than happy to integrate
that work, and we plan on doing it ourselves for Ubuntu in the near
future. The message "we welcome people who want to run other distros as
oVirt nodes" is important.
Cheers,
Dave.
--
Dave Neary
Community Action and Impact
Open Source and Standards, Red Hat
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
5:48 p.m.
On 09/12/2012 01:01 AM, Dave Neary wrote:
Hi,
On 09/11/2012 11:33 PM, Jason Brooks wrote:
> Right now, oVirt only works with Fedora and CentOS/RHEL. We shouldn't
> give people the wrong idea about multi-distro possibilities. Someone
> could get the engine app running on jboss on a different platform, but
> vdsm, an essential component for doing anything w/ ovirt, is very much
> tied to fedora/el right now.
While I accept that this is the current situation, I think we definitely
want to give people the impression on the website that this is not a Red
Hat only virtualisation manager - yes, there's work to be done to
integrate it on other distros, but we are more than happy to integrate
that work, and we plan on doing it ourselves for Ubuntu in the near
future. The message "we welcome people who want to run other distros as
oVirt nodes" is important.
Definitely -- I hope to see us make multi-distro a reality asap, and
it's important to make that goal clear -- and make clear that currently,
a goal is what it is.
Cheers,
Dave.
--
@jasonbrooks
9:04 p.m.
On 09/11/2012 11:33 PM, Jason Brooks wrote:
This looks very nice, Garrett.
Thanks!
Some comments/thoughts:
The minimum RAM for ovirt is 4GB. You can get by with less, but the
engine-setup script won't run if it detects less RAM. There is a
command line argument, --no-mem-check, that disables the minimum
memory check.
Thanks for the correction!
It was a placeholder to express the desire for minimum requirements on
that page — but accuracy even on mockups is a great thing, so I'm
modifying them now.
Do you know the other requirements too? Such as hard disk space, etc. —
or anything I might be leaving out…?
If we're going for simplicity, we may want to go with the
ovirt-engine-setup-plugin-allinone as the suggested package to
install. This way, you come out of these directions ready to create
and run VMs. For a complete setup, it may be that the steps required
are too many to include on this page. We could link to the quick start
guide here: http://wiki.ovirt.org/wiki/Quick_Start_Guide.
That's the intent of the original download mockup:
http://people.redhat.com/glesage/oVirt/website/mockup-1/download.html
&
Info:
http://people.redhat.com/glesage/oVirt/website/background-info/design-dow...
From my understanding, it'll take effort from multiple people to get
the all-in-one install ISO working how we want it to.
The goal of the download-alt mockup was to make sure we can move forward
with the website and still launch in the near future, even if the
all-in-one ISO isn't quite yet ready.
(Hopefully we can move to the fully packaged version soon, as I think
it's conceptually friendlier to those installing oVirt.)
Right now, oVirt only works with Fedora and CentOS/RHEL. We
shouldn't
give people the wrong idea about multi-distro possibilities.
Agreed.
That's why I focused on using Fedora in both download page mockups and
added a plea-for-help.
When other OSes are 100% *fully* supported in an all-in-one install ISO,
we could then (perhaps) add some way to switch the page when we're
comfortable enough that they work. Until that time, I firmly believe
having a recommended install path with links to secondary support is fine.
Someone could get the engine app running on jboss on a different
platform, but vdsm, an essential component for doing anything w/
ovirt, is very much tied to fedora/el right now.
For the time being, "other distros" just means having the management UI
running on various platforms, and that everyone using oVirt is using
Fedora/RHEL/RHEL-derivative doing the heavy lifting on the servers, right?
What's the general plan & timeframe for getting VDSM et al. working
cross-distro, so that all of oVirt can run everywhere?
Garrett
9:17 p.m.
On 09/12/2012 11:04 AM, Garrett LeSage wrote:
> If we're going for simplicity, we may want to go with the
> ovirt-engine-setup-plugin-allinone as the suggested package to
> install. This way, you come out of these directions ready to create
> and run VMs. For a complete setup, it may be that the steps required
> are too many to include on this page. We could link to the quick start
> guide here: http://wiki.ovirt.org/wiki/Quick_Start_Guide.
That's the intent of the original download mockup:
http://people.redhat.com/glesage/oVirt/website/mockup-1/download.html
&
Info:
http://people.redhat.com/glesage/oVirt/website/background-info/design-dow...
From my understanding, it'll take effort from multiple people to get
the all-in-one install ISO working how we want it to.
This is different from ISO -- I'm talking about the all-in-one
engine-setup plugin that's currently available. Right now, you can
install the package "ovirt-engine-setup-plugin-allinone" which pulls in
all the same stuff as ovirt-engine, but adds the option, in the
engine-setup script, to make your engine also be a virtualization host.
With the regular setup, you come out of the script with the engine, a
default data center, and an (optional) iso domain running on the engine
machine. You then have to go create a data domain and add a host before
you can use ovirt.
The AIO plugin adds a local data domain, and configures the engine to
host VMs, so when you first visit the web console, you're ready to roll.
For the time being, "other distros" just means having the management UI
running on various platforms, and that everyone using oVirt is using
Fedora/RHEL/RHEL-derivative doing the heavy lifting on the servers, right?
What's the general plan & timeframe for getting VDSM et al. working
cross-distro, so that all of oVirt can run everywhere?
I don't know the plan -- it'd be good to have a "things needed to enable
multi-distro" page on the wiki. I'll try to start one.
Garrett
--
@jasonbrooks
9:56 p.m.
On 09/12/2012 08:17 PM, Jason Brooks wrote:
This is different from ISO
Aha, okay.
That's also great, and it's probably a requirement for an all-in-one
installer that would allow someone to download just one ISO to install:
A) All of oVirt (this would be the default)
B) The server part ("node")
C) The web-based management UI
(Another approach could be to _always_ install everything on each
machine, and oVirt could run in one of the above modes.)
> What's the general plan & timeframe for getting VDSM et
al. working
> cross-distro, so that all of oVirt can run everywhere?
I don't know the plan -- it'd be good to have a "things needed to
enable multi-distro" page on the wiki. I'll try to start one.
Great idea!
Garrett
4454
days inactive
4460
days old
7 comments
4 participants
participants (4)
-
Benedict, Jon -
Dave Neary -
Garrett LeSage -
Jason Brooks