[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Services, Roles and Xen [was whats next]



On Thu, 2005-06-02 at 12:19 +0200, Kyrre Ness Sjobak wrote: 
> ons, 01.06.2005 kl. 19.59 skrev Elliot Lee:
> > Maybe it's time to start the brainstorming for Fedora Core 5 and Fedora
> > Extras 5 - what major features are you willing to put effort into?
> > 
> > Best,
> > -- Elliot
> 
> system-config-role
> 

See below 

> - LAMP server (setup apache, mysql, and PHP in a sane way)
> - File/login-server (LDAP, NFS, Samba)

Instead of a single role, it's better to have the ability to assign
individual services to individual machines, with each service having a
"meta-role" of Master( primary host for a resource ), Apprentice ( in
sync with Master ), or Backup ( as with Apprentice, but does not
actively serve ). 

You configure the service for the Master server using a front end, which
also stores the details in a single generalized config file, which also
can be copied so it can be accessed at a given URI. When creating an
Apprentice or Backup service all you should need to do is declare the
URI of the Master file. When starting a init.d service, the back end
grabs the generalized config file and generates the appropriate /etc/
files. The front and back ends should also include the ability to use
encryption and digital signatures. 

And if your going to do that, then why not have the option of for each
PC to load a master list of services and required rpm packages from a
single remote URI at boot time, pxeboot style.  


> some setup tool where you could select a machines role using profiles -
> examples:
> 
> - Laptop (ACPI, NetworkManager etc)
> - Workstation (nothing special)



https://www.redhat.com/archives/fedora-devel-list/2005-April/msg00545.html
QUOTE
However, with a little scripted configuration, one OS install and one 
mounted file system tree, should be able to perform all of the
following, one at a time,  depending on boot flags and kernel
selection.  

Native without Xen
     Workstation : Run level 5
         Graphical mode.
         Runs most user applications locally.
         Can host remote services ( httpd etc ).
     X-Terminal  : Run level 4?
         LTSP like thin graphical client.
         Runs most user applications remotely.
*  Important for desktop support: you can fix the 
   normal workstation setup without any user downtime.    
     Server      : Run level 3
         Text mode.
         Runs most user applications locally.
         hosts remote services. 
     Repair      : Run level 2
         Text mode
         Root login only.
         Does not host remote services. 

Xen domain 0
     Xen + Domain 0 Workstation : Run level 5
         Graphical mode ( assuming that AGP is compatible )
         Should operate same as native workstation
     Xen + Domain 0 X-Terminal  : Run level 4?
         Graphical mode ( assuming that AGP is compatible )
         Can also log into local domain U servers.
     Xen + Domain 0 Server      : Run level 3
         Text mode,  
     Xen + Domain 0 Monitor     : Run level 2?
         Text mode.
         Minimal Xen host setup, plus network support.
         Runs user application and services on domain U servers

NOTE : whatever runlevel the Xen domain 0 is running it would still
host/run the "xen" init.d  Xen0 services.
     
Xen domain U
     Note only two.
     Domain U Server : Run level 3
         
     Domain U Repair : Run level 2
UNQUOTE


> Surely you can make a lot of profiles. program runs as stand-alone and
> in firstboot.
> 
> Could probably make it really easy to setup a server etc. - reducing
> deployment time.
> 
> Kyrre
> 
-- 
David Mohring <heretic ihug co nz>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]