incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Trivial Update of "BennuProposal/BennuFaq" by DanielSHaischt
Date Wed, 26 Dec 2007 15:43:02 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by DanielSHaischt:
http://wiki.apache.org/incubator/BennuProposal/BennuFaq

The comment on the change is:
fixed typos

------------------------------------------------------------------------------
  
  '''''Q:''' Why have you chosen to initially focus on FreeBSD?''
  
- '''A:''' Bennu will be re using the m0n0wall code base as a initial starting point. m0n0wall
is FreeBSD based and thus the Bennu management layer will be initially FreeBSD compliant as
well.
+ '''A:''' Bennu will be re using the m0n0wall code base as an initial starting point. m0n0wall
is FreeBSD based and thus the Bennu management layer will be initially FreeBSD compliant as
well.
  
  '''''Q:''' Isn't it a real overhead to try to accomplish an OS agnostic management layer?''
  
- '''A:''' To a certain degree Yes. On the other hand with the help of appropriate software
design (like service abstraction and a polymorphic service behavior), POSIX complaint coding
guidelines and the appropriate tooling (autotools or cmake etc.) we do believe that such a
OS agnostic software service management layer can be accomplished or at least porting the
layer to a different OS will be easier.
+ '''A:''' To a certain degree Yes. On the other hand with the help of appropriate software
design (like service abstraction and a polymorphic service behavior), POSIX complaint coding
guidelines and the appropriate tooling (autotools or cmake etc.) we do believe that such an
OS agnostic software service management layer can be accomplished or at least porting the
layer to a different OS will be easier.
  
- '''''Q:''' So is it correct that Bennu will be composed of a operating system (e.g FreeBSD)
plus a management layer to manage software services of an operating system?''
+ '''''Q:''' So is it correct that Bennu will be composed of an operating system (e.g FreeBSD)
plus a management layer to manage software services of an operating system?''
  
  '''A:''' No. The Bennu system (as it will be maintained in a SCM system) will only consist
of the aforementioned management layer plus an appropriate build system that is assembling
a custom operating system, suitable to be run either on an embedded device or a server appliance.
The outcome will be a Bennu image that contains anything that is required to run the Bennu
system on an embedded device or a server appliance.
  
@@ -52, +52 @@

  
  '''''Q:''' Which interfaces will be exposed by the management layer to enable other software
systems to interact with the Bennu system?''
  
- '''A:''' Some particular implementation of a web service (either SOAP based or REST or even
both).
+ '''A:''' Some particular implementation of a web service protocol (either SOAP based or
REST or even both).
  
- '''''Q:''' In the hardware section above you've mentioned that there will be some kind of
build system that is coming along with the Bennu (source code) distribution. What's the particular
purpose of such a build system?''
+ '''''Q:''' In the hardware section above you've mentioned that there will be some kind of
a build system that is coming along with the Bennu (source code) distribution. What's the
particular purpose of such a build system?''
  
  '''A:''' Basically it's more than impractical to require the end user to assemble a ready
to run Bennu operating system image on his own. Thus a Bennu build system will be put into
place that is responsible for ''a)'' compiling the Bennu software service management layer
''b)'' creating a directory tree structure that will compose the actual Bennu runtime system
''c)'' configuring the Bennu boot loader etc. and ''d)'' creating an installable software
image that contains the Bennu binaries plus an accompanying operating system. The installable
software image will be geared towards a specific hardware platform (e.g. embedded or server).
  
@@ -64, +64 @@

  
  '''''Q:''' Hummm ... Sounds like Bennu is trying to accomplish what others like Webmin are
already providing.''
  
- '''A:''' No, not exactly. Bennu is providing an abstraction layer that allows to administer
concrete software services. The abstraction will be fine grained to allow to replace a software
service that implements for example a HTTP proxy by another software service implementation
having the same purpose. Such a software interchange scenario may be required if a customer
increases the QoS criteria for a HTTP proxy software service implementation where software
service A does not fulfill these kind of criteria any more and thus must be exchanged by software
service implementation B. Furthermore we are envision to provide software services which are
proxying the actuall service implementation. That way it may be possible to off-load the actual
service implementation to another hardware device. Finally Bennu does not provide a mandatory
web based GUI as it is implied by Webmin. The web based GUI may be deployed as an add-on to
the Bennu runtime environment. Although it would be 
 also possible to administer several Bennu runtime environments using a centralized management
facility and thus the web based management GUI on each Bennu runtime environment becomes obsolete.
+ '''A:''' No, not exactly. Bennu is providing an abstraction layer that allows to administer
concrete software services. The abstraction will be fine grained to allow to replace a software
service that implements for example a HTTP proxy by another software service implementation
having the same purpose. Such a software interchange scenario may be required if a customer
increases the QoS criteria for a HTTP proxy software service implementation where software
service ''A'' does not fulfill these kind of criteria any more and thus must be exchanged
by software service implementation ''B''. Furthermore we are envision to provide software
services which are proxying the actual service implementation. That way it may be possible
to off-load the actual service implementation to another hardware device. Finally Bennu does
not provide a mandatory web based GUI as it is implied by Webmin. The web based GUI may be
deployed as an add-on to the Bennu runtime environment. Although it wo
 uld be also possible to administer several Bennu runtime environments using a centralized
management facility and thus the web based management GUI on each Bennu runtime environment
becomes obsolete.
  
  '''''Q:''' How will the software service management layer persist configuration settings
of particular software services?''
  
@@ -78, +78 @@

  
  '''A:''' Yes. Basically migrating from m0n0wall or pfSense to Bennu will be supported. If
Bennu doesn't support a certain function which was available on m0n0wall or pfSense it wouldn't
be possible to migrate the corresponding configuration settings for obvious reasons.
  
- 
  '''''Q:''' It sounds like the software service management layer is just providing the building
blocks for managing software services which may be found on an operating systems (e.g. UNIX
daemons etc.). Does this mean this management layer may be used to assemble a custom NAS or
PBX system based on Bennu?''
  
- '''A:''' Yes. This has been already done using m0n0wall as a foundation (e.g. FreeNAS and
Askozia are both m0n0wall based) and thus, because Bennu shares the same idea of providing
re usable components, it would be as well possible to create a PBX or NAS system by using
the Bennu software artifacts. Tho we currently put our focus on firewalling/routing, Wi-FI
and unified threat management.
+ '''A:''' Yes. This has been already done using m0n0wall as a foundation (e.g. FreeNAS and
Askozia are both m0n0wall based) and thus, because Bennu shares the same idea of providing
re usable components, it would be as well possible to create a PBX or NAS system by using
the Bennu software artifacts. Tho we currently put our focus on firewalling/routing, Wi-Fi
and unified threat management.
  
  '''''Q:''' I am used to managing my router devices using a command line shell or a character
based GUI (e.g. curses). Will Bennu provide such a shell or even a character based GUI?''
  
@@ -89, +88 @@

  
  '''''Q:''' IDS and IPS systems do require a certain amount of computing power. How are you
plans to support this particular kind of software on embedded devices?''
  
- '''A:''' Each installable software service that mau be installed on a Bennu runtime environment
will provide a certain degree of meta information which includes data about for which system
the service was originally designed (e.g. may NOT be run on embedded devices). Thus the user
will get a certain degree of decision guidiance about whether a particular service is suitable
for an embedded device or not. At the end of the day it upon the user to make a decission
to install an IDS/IPS on an embedded device or not.
+ '''A:''' Each installable software service that may be installed on a Bennu runtime environment
will provide a certain degree of meta information which includes data about for which system
the service was originally designed (e.g. may ''NOT'' be run on embedded devices). Thus the
user will get a certain degree of decision guidiance about whether a particular service is
suitable for an embedded device or not. At the end of the day it's upon the user to make a
decision to install an IDS/IPS on an embedded device or not.
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message