AskApy stands for : Ask for Admin Python Bricks

AskApy is an application server dedicated to system administrators of complexe architectures of servers
(with many filewalls and routers).

It aims to gather all the services needed to transparently launch and supervise a task running on a local or distant server.
This is why AskApy is more likely called a Task Server.

AskApy was born from this specification list.
AskApy aims to be easy to use.

AskApy includes

• An Apb application server : ApbServer.
  
  An ApbServer hosts Apb instances.
  An Apb is an AskApy remote component that can be invoked/instanciated from remote to accomplish a job on the remote server.
  The communication protocol is implemented over HTTP.
  
  An Apb is a python class which :
  • Inherites from class Apb.
    
    
  • Defines the methods that you want to be run as tasks. Their name starts by 'do_'.
    All the 'do_' methods are visible to the clients.
    In these methods you write the code of your adminisrative task.
    This code could as well a shell wrapped commands of any other langages.
    AskApy manages to make these tasks available for any user or from any server of the family.
    
    
  • Apb are statefull re-entrant and share-able over multiple users.
    This allow at any time to enter back on an Apb with an already running task and to handle its actives resources.


• A scheme of hierarchical organisation called the Family.

  
  A manager by family called the Father.

  A deputy by machine/family called Nurse.

  Servers that may act as proxy called Childs.

  Childs clones named Twins.

Features

• Application server services
  

  • Securiry, User registry, identification, authentification, autorisation (upon Server, Apb an Resources).
  • Single signon.
  • Affinity and Session.
  • Management of multiples Servers in an uniformised area called the family.
  • Transparent location of Servers, Apbs an Resources into the family,
    thanks to the Simple Name Service (SNS) and the Uniform Apb Locator (UAL) mechanismes.
  • Clusters (based on Twins)
  • Support of the Deployement of Apbs components also called Cubes.

• Task server services
  

  • Dedicated mechanisms for the writing of heavyloaded Deamon
  • AskApy XQL (AskApy Xml Query Langage) to query and update xml files. (1)
  • AskApy AQL (AskApy Attribute Query Langage) to query and update attributes (properties) files.
  • A scheduler (KRON)
  • A messaging system.

• Protocols and clients

  Protocols are available throught connectors.
  All protocols support SSL (openSSL must be installed).
  Supported protocols

  HTTP connector (nickname web)

  You can connect from any web client like browsers.

  XMLRPC connector (nickname xml)

  You can connect from any client supporting xmlrpc (python, perl, java).

  SOAP connector (nickname soa) (2)

  You can connect from any client supporting soap (python, perl, java).

  FILE TRANSFERT connector (nicknames ftb or ftm)

  Only available from the AskApy client ask.py.

  APB connector (nicknames apb or apm)

  Only available from the AskApy client and the AskApy Graphical client interfaces view.py, ask.py.

• Graphical user interface

  A Graphical framework (based upon view plugins) is provided to design your Views.
  
  Then your Views are transparently displayable
  • from a classic web browser
  • from the AskApy Graphical client interface view.py (wxPython must be installed).
  • or throught any python Application using the AskApy Graphical class ApbView (wxPython must be installed).

Notes

• (1) This not the Offical XQL but a free AskApy implementation of it.
  That's why it is called AskApy XQL.
• (2) Coming soon.