[Octa-list] Octa Deployment Documentation and hypervisor support

[Greg_Swift at aotx.uscourts.gov]

So... I would eventually like to get the information for running systems
from the satellite, but I want to rely on separate cobbler instances (we
have several) for the configuration.

The best way I can think to describe it is to take your Architecture
Diagram (
https://fedorahosted.org/octa/attachment/wiki/Architecture/Slide1.png?format=raw)
 scratch out Satellite from each of those little clouds and put it off to
the side.  The only thing it provides is centralized package distribution
and entitlement management.

I've started re-writing some of the code to support this, but would like to
not go completely off the rail with it to a point where ya'll disagree with
the implementation and I end up with a forked project.  That doesn't help
anyone, imo.


Initially I fixed the logic in create.py's profile display to match that of
the existing logic in 'octa --list-profiles' so if satellite isn't
configured at all, then it displays cobbler profiles.  This seems to work
fairly well.

I added logic to create.py to generate a list of existing system names in
cobbler as an option.  But then over the weekend I thoguht about it more
and decided maybe it would be better to have a separate page, build.py
maybe, that would let you pick a system, get a "snapshot" view of its
config (network, cpu, memory, size) and confirm its build (with a existing
status with a confirmation for a rebuild).

I'm still trying to figure out what to do about the whole IP/DHCP bit,
because we are a static IP shop.

I guess my problem is that while we need all the bits for a 'cloud-like'
IaaS, ours is not a dynamic environment like Amazon.

-greg

Aron Parsons <aron at redhat.com> wrote on 04/18/2011 09:06:12 AM:

> Without Satellite you just won't have information about the last
> checkin time and if it's packages are up-to-date.  There's a config
> option to disable the Satellite component.  You don't really lose
> any functionality, just information.
>
> If you don't have control of your DNS zone, just don't configure
> dhcpd to update DNS.  The DDNS portion of octa is all controlled by
> dhcpd, so check out the man pages for dhcpd.conf for whatever you want to
do.
>
> Aron Parsons, RHCA
> Senior Consultant
> Red Hat Consulting
>
> ----- Original Message -----
> From: "Greg Swift" <Greg_Swift at aotx.uscourts.gov>
> To: octa-list at redhat.com
> Sent: Friday, April 15, 2011 11:55:05 AM
> Subject: Re: [Octa-list] Octa Deployment Documentation and hypervisor
support
>
>
> So.. I've downloaded octa and started going through the INSTALL doc.  I
> have a Satellite server, but a stand alone cobbler system, and I wasn't
> planning on integrating with our Satellite.   We also do not have any
> control of DNS.  How does this affect the configuration/functionality?
>
> -greg
>
> ----- Original Message -----
> From: Aron Parsons <aron redhat com>
> To: "James Labocki" <jlabocki redhat com>
> Sent: Friday, February 11, 2011 11:04:19  AM
> Subject: Re: [Octa-list] Octa Deployment Documentation and hypervisor
> support
>
> http://git.fedorahosted.org/git/?p=octa.git;a=blob;f=src/doc/INSTALL
>
> The INSTALL doc should be enough to get everything up.  Basically,
install
> the RPM, setup Cobbler/dhcpd/BIND and configure octa
> in /var/www/octa/clouds.
>
> /aron
>
> ----- Original Message -----
> From: "James Labocki" <jlabocki redhat com>
> To: "octa-list" <octa-list redhat com>
> Sent: Friday, February 11, 2011 9:34:00 AM
> Subject: [Octa-list] Octa Deployment Documentation and hypervisor support
>
> Some folks in the Tysons COE would like to deploy Octa alongside RHEV-M
and
> Satellite. Is there a quick 3 step guide to get started? I'll take the
lead
> to edit the wiki with installation documentation as we go.
>
> Also, what's the best way to approach getting VMware supported as a
> hypervisor? I'm not python guru and I don't want to make your code messy.
>
> -James
> m: 440.503.9996
>
> _______________________________________________
> Octa-list mailing list
> Octa-list at redhat.com
> https://www.redhat.com/mailman/listinfo/octa-list