chore: add .worktrees/ to gitignore
1 file changed
tree: 41ac94401cb44dd096ecc055262a701a8281e98c
  1. .github/
  2. .vscode/
  3. airavata-agent/
  4. airavata-api/
  5. airavata-jupyterhub/
  6. airavata-python-sdk/
  7. airavata-server/
  8. conf/
  9. dev-tools/
  10. examples/
  11. keystores/
  12. scripts/
  13. .asf.yaml
  14. .dockerignore
  15. .gitignore
  16. apache-license-header-java.txt
  17. apache-license-header-xml.txt
  18. apache-license-header.txt
  19. CITATION.cff
  20. compose.yml
  21. DEPLOY
  22. Dockerfile
  23. INSTALL
  24. LICENSE
  25. logo.txt
  26. Makefile
  27. NOTICE
  28. pom.xml
  29. README.md
  30. RELEASE_NOTES
  31. Tiltfile
README.md

Apache Airavata

image

Build Status License Contributors

Apache Airavata is a software framework for executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds. Airavata builds on general concepts of service oriented computing, distributed messaging, and workflow composition and orchestration. Airavata bundles a server package with an API, client software development Kits and a general purpose reference UI implementation.

Key Features

  • πŸ”§ Service-oriented architecture with distributed messaging
  • πŸ”„ Fully-managed task lifecycle (environment setup, data staging, execution, and output retrieval)
  • ☁️ Multi-cloud and hybrid cloud support
  • πŸ–₯️ Comprehensive API and SDK ecosystem
  • 🌐 Reference UI Implementations

Using Airavata

If you’re a researcher, Airavata offers several ways to streamline your workflows:

  1. Submit Batch Jobs via the Airavata Application Portal -- Example
  2. Launch Interactive Experiments through the Airavata Research Portal -- Example
  3. Explore and run published experiments from the Airavata Research Catalog -- Example
  4. Run interactive computational jobs directly from your IDE using Airavata Python SDK -- PyPI

🧱 The Airavata Ecosystem

Apache Airavata is composed of modular components spanning core services, data management, user interfaces, and developer tooling.

πŸ”§ Core Services

πŸ“¦ Data & Metadata Services

πŸ“š Documentation & Branding

πŸ§ͺ Experimental & Research

πŸ”„ How Airavata Works

Airavata runs as a single unified JVM (Spring Boot) that hosts Thrift, REST, and gRPC transports plus background workers.

graph TB
    subgraph "Docker Infrastructure (compose.yml)"
        DB[(MariaDB<br/>:13306)]
        RMQ[RabbitMQ<br/>:5672]
        ZK[ZooKeeper<br/>:2181]
        KFK[Kafka<br/>:9092]
        KC[Keycloak<br/>:18080]
    end

    subgraph "Unified Airavata Server (single JVM)"
        direction TB
        MUX["Thrift :8930<br/>9 multiplexed services"]
        REST["REST :18889<br/>Swagger UI + Actuator"]
        GRPC["gRPC :19900<br/>Agent + Research"]
        SVC["Service Layer<br/>(airavata-api module)"]
        BG["Background Services<br/>12 workers"]
        MON["Monitoring :9097<br/>/metrics /health/services"]
    end

    SDK[Python SDK] -->|TMultiplexedProtocol| MUX
    Portal[Web Portal] -->|REST| REST
    MUX --> SVC
    REST --> SVC
    GRPC --> SVC
    SVC --> DB
    SVC --> RMQ
    BG --> ZK
    BG --> KFK
    BG --> RMQ
    SVC -.->|auth| KC
    MON -.->|tracks| BG

1. Unified Airavata Server (airavata-server)

Entry point: org.apache.airavata.server.AiravataServerMain Started via: tilt up or java -jar airavata-server/target/airavata-server-0.21-SNAPSHOT.jar

The unified server hosts all transports (Thrift, REST, gRPC), Spring Boot services (Research, Agent, File Server), and background workers in a single JVM. On startup it:

  1. Initializes the unified airavata database
  2. Starts the REST server on port 18889 (Swagger UI + Actuator health)
  3. Registers 9 Thrift services on a single TMultiplexedProcessor (port 8930)
  4. Starts gRPC server on port 19900
  5. Starts background IServer workers
  6. Starts monitoring server on port 9097

Architecture: Service Layer + Thrift Transport

All business logic lives in a transport-agnostic service layer (org.apache.airavata.service.*). Thrift handlers are thin adapters that delegate to services via ThriftAdapter, translating between Thrift types and service exceptions. This decoupling enables future REST/gRPC transports without duplicating logic.

ServiceResponsibility
ExperimentServiceExperiment lifecycle (create, launch, clone, terminate, intermediate outputs)
ProjectServiceProject CRUD and search
GatewayServiceGateway management and sharing domain setup
ApplicationCatalogServiceApp modules, deployments, and interfaces
ResourceServiceCompute/storage resources, job submission, data movement, storage info
CredentialServiceSSH/password credential management with sharing
ResourceSharingServiceResource sharing and access control
GroupResourceProfileServiceGroup resource profiles and policies
GatewayResourceProfileServiceGateway resource preferences
UserResourceProfileServiceUser resource preferences
SSHAccountServiceSSH account provisioning and validation
DataProductServiceData products and replicas
NotificationServiceNotification CRUD
ParserServiceParsers and parsing templates

Shared utilities: SharingHelper (sharing operations), EventPublisher (messaging), RequestContext (transport-agnostic identity).

Thrift Services (all on port 8930, multiplexed)

Service nameHandlerResponsibility
AiravataAiravataServerHandlerPublic API β€” delegates to service layer
RegistryServiceRegistryServerHandlerMetadata and definitions for tasks and applications
CredentialStoreCredentialStoreServerHandlerSecure storage and retrieval of compute credentials
SharingRegistrySharingRegistryServerHandlerSharing and permissioning of Airavata resources
UserProfileUserProfileServiceHandlerUser profile management
TenantProfileTenantProfileServiceHandlerTenant/gateway management
IamAdminServicesIamAdminServicesHandlerIAM administration
GroupManagerGroupManagerServiceHandlerGroup and role management
OrchestratorOrchestratorServerHandlerWorkflow DAG construction and task dispatch

Background Services (IServer lifecycle, same JVM)

ServiceResponsibility
DBEventManagerRunnerSyncs task execution events to the DB via pub/sub
MonitoringServerPrometheus metrics endpoint (optional)
ComputationalResourceMonitoringServicePolls compute resource queue status
DataInterpreterServiceMetadata analysis for submitted jobs
ProcessReschedulingServiceRetries and reschedules failed processes
HelixControllerManages Helix cluster state transitions
GlobalParticipantExecutes task steps (EnvSetupTask, InputDataStagingTask, OutputDataStagingTask, JobVerificationTask, CompletingTask, ForkJobSubmissionTask, DefaultJobSubmissionTask, LocalJobSubmissionTask, ArchiveTask, WorkflowCancellationTask, RemoteJobCancellationTask, CancelCompletingTask, DataParsingTask, ParsingTriggeringTask)
PreWorkflowManagerHandles pre-execution phase (env setup, data staging)
PostWorkflowManagerHandles post-execution phase (cleanup, output fetching)
ParserWorkflowManagerHandles parsing/data-interpretation workflow phase
EmailBasedMonitorPolls email inbox for job status updates (optional)
RealtimeMonitorListens on Kafka for real-time job state changes
stateDiagram-v2
    [*] --> CREATED
    CREATED --> VALIDATED : validateExperiment
    VALIDATED --> LAUNCHED : launchExperiment
    LAUNCHED --> EXECUTING : PreWorkflowManager
    EXECUTING --> MONITORING : job submitted
    MONITORING --> COMPLETED : job finished
    MONITORING --> FAILED : job error
    EXECUTING --> CANCELLED : terminateExperiment
    COMPLETED --> [*]
    FAILED --> [*]
    CANCELLED --> [*]
graph LR
    subgraph "Startup Sequence"
        direction TB
        A[1. DB Init] --> B[2. Thrift Handlers]
        B --> C[3. TMultiplexedProcessor :8930]
        C --> D[4. DBEventManager]
        D --> E[5. MonitoringServer :9097]
        E --> F[6. HelixController]
        F --> G{waitForHelixCluster}
        G --> H[7. HelixParticipant]
        H --> I[8. Pre/Post/Parser WF Managers]
        I --> J[9. Email/Realtime Monitors]
    end

Embedded Spring Boot Services

The following services are embedded in the unified server (not run separately):

ServiceModulePurpose
File Serverairavata-api/file-serverSFTP wrapper for secure storage access
Agent Serviceairavata-api/agent-serviceBackend for interactive jobs via bidirectional gRPC
Research Serviceairavata-api/research-serviceResearch catalog API (notebooks, datasets, models)

πŸ—οΈ Getting Started

Prerequisites

RequirementVersionCheck Using
Java SDK17+java --version
Apache Maven3.8+mvn -v
Docker Engine20.10+docker -v
Docker Compose2.0+docker compose version
Tilt0.33+tilt version

Quick Start (Tilt)

Tilt orchestrates the full development stack β€” infrastructure, build, and all services:

git clone https://github.com/apache/airavata.git
cd airavata
tilt up

This starts:

  • Infrastructure: MariaDB, RabbitMQ, ZooKeeper, Kafka, Keycloak (via compose.yml)
  • Unified Airavata Server: Thrift (:8930), REST (:18889), gRPC (:19900), Monitoring (:9097)

Open the Tilt UI at http://localhost:10350 to monitor all resources. Integration tests can be triggered manually from the Tilt UI.

Manual Start

docker compose up -d                          # Infrastructure
mvn clean package -DskipTests -T4             # Build
java -jar airavata-server/target/airavata-server-0.21-SNAPSHOT.jar  # Start server

Or use the helper scripts:

./scripts/setup.sh    # Infrastructure + build
./scripts/start.sh    # Start server

Health Monitoring

The monitoring server on port 9097 exposes:

EndpointMethodDescription
/metricsGETPrometheus metrics
/health/servicesGETJSON status of all background services (UP/DOWN/DISABLED)
/admin/restart/{name}POSTRestart a background service by name

Spring Boot services expose /actuator/health on their respective ports.

Configuration

The main configuration file is airavata-server/src/main/resources/application.yml. Key settings:

  • airavata.servers β€” List of transports to activate: [thrift, rest, grpc]
  • spring.datasource.url β€” JDBC URL (default: jdbc:mariadb://localhost:13306/airavata)
  • airavata.thrift.port β€” Thrift port (default: 8930)
  • server.port β€” REST port (default: 18889)
  • grpc.server.port β€” gRPC port (default: 19900)
  • airavata.security.openid-url β€” Keycloak realm URL

Integration Tests

mvn test -pl airavata-api -Dgroups=runtime

Server Ports

TransportPortPurpose
Thrift89309 multiplexed services (Python SDK, Thrift clients)
REST18889Swagger UI, Actuator health, REST APIs
gRPC19900Agent + Research service gRPC
Monitoring9097Prometheus metrics, /health/services

🀝 Contributing

We welcome contributions from the community! Here's how you can help:

  1. 🍴 Fork the repository
  2. 🌿 Create a feature branch
  3. ✨ Make your changes
  4. πŸ§ͺ Add tests if applicable
  5. πŸ“ Submit a pull request

Learn More:

Setting up your IDE

Use tilt up to start the full stack, then attach your IDE debugger. For remote debugging, add -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 to the serve_cmd in the Tiltfile.

πŸ’¬ Community & Support

Get Help:

πŸ“„ License

Licensed to the Apache Software Foundation (ASF) under one or more contributor
license agreements. See the NOTICE file distributed with this work for
additional information regarding copyright ownership.

The ASF licenses this file to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance with the License.
You may obtain a copy of the License at:

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for the
specific language governing permissions and limitations under the License.

See the LICENSE file for complete license details.