Download
installation n.
Skip this Video
Loading SlideShow in 5 Seconds..
Installation PowerPoint Presentation
Download Presentation
Installation

Installation

134 Views Download Presentation
Download Presentation

Installation

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Installation • Installation instructions • https://geni-orca.renci.org/trac/wiki/buildInstructions • Full source code access to current trunk • “Real” release still in progress • Software requirements • https://geni-orca.renci.org/trac/wiki/instructions • Orca guides • https://geni-orca.renci.org/orca-doc/current/guides/index.html • Slightly outdated, but very relevant • In the process of being updated

  2. Running Orca • From the command line • https://geni-orca.renci.org/orca-doc/current/guides/command-line/index.html • tools/cmdline • All actors must be in the same container • Only local communication • Very useful for debugging • Inside tomcat • https://geni-orca.renci.org/orca-doc/current/guides/portal/index.html • webapp/ • Local and SOAP-based communication

  3. Configuration • See documentation • https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/index.html • Multiple files, but two are critical: • container.properties • https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/properties.html • config.xml • https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/xml.html • Sample files are checked in the repository • tools/cmdline/config (template copied to tools/cmdline/local) • tools/cmdline/tests • tools/cmdline/renci • weabpp/local/

  4. Actor Setup • Each actor needs: • Name • GUID • Certificate/keystore • Axis2 configuration files • Can be generated automatically at startup • Can be pre-generated on the command line • Needed for distributed setup

  5. Actor Setup Generation • Command line helper tools • https://geni-orca.renci.org/orca-doc/current/tools/config/guides/ • Can be used to pre-generate security/configuration files for an actor • Must be used to generate the security/configuration files for the container admin (the root of an Orca container) • Distributed setup • https://geni-orca.renci.org/trac/wiki/distributed • Must ensure that actors have access to the certificate of remote actors that they are directly connected to • Service manager -> Broker • Broker -> Site

  6. Policies • orca.shirako.apinamespace (core/shirako) • Lists most critical interfaces • Follow implementation and inheritance to get better understanding of relationships • Sample/core policies • orca.policy.corenamespace (core/policy) • orca.cod.controlnamespace (core/cod) • Basic unit-testing framework is in place • Test policies in isolation • Should be documented by the end of May

  7. More on Policies • Broker policy • Extracts what is requested by client • Determine what to allocate • Allocation results in a ticket • Ticket describes allocated resources • Identifies site from which resources must be claimed • Example: • BrokerSimplerUnitsPolicy

  8. More on Policies • Site policy • Extracts ticket allocated by broker • Validate/verify • Determine what units to assign • Assigned units configured via setup handler • Assignment results in a lease update • A collection of Nodes • Each describing an assigned unit • Service manager’s join handler invoked on receipt of update • See • AuthorityCalendarPolicy • VlanControl, VMControl

  9. Packaging Policies and Other Extensions • Orca supports extension packages • Supply new controllers, policies, actors, etc. • Can be added dynamically at runtime • Dynamic update is partly functional • Requires some more classloader and java magic • Undocumented format, but used in several projects in the source tree • Goal: use for delivery to clearinghouse • Documentation by the end of this month