Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

  • Introduction

       The supported environments are specified in System Dependencies and Target Environments.

The recommended method for installation is through the use of ADE, a Docker-based tool to ensure that all developers in a project have a common, consistent development environment. It comes with a pre-built version of Autoware.Auto, so that you will not need to compile it yourself if you do not want to.

  • License

     Apache License 2.0

  • How to use this document

     Just follow the instruction.

  • Deployment Architecture

  • Pre-Installation Requirements

    • Hardware Requirements

      • Minimum Hardware Requirements

                           Single Machine with Linux or Mac system installed.

      • Recommended Hardware Requirements

    • Software Prerequisites

                           Software environment :jdk1.8+、Python3.6、python virtualenv、mysql5.6+、redis-5.0.2

Using KubeFATE, FATE can be deployed by either docker-compose or Kubernetes:

  • For development or testing purposes, docker-compose is recommended. It only requires Docker enviroment. For more detail, please refer to Deployment by Docker Compose.

  • For a production or a large scale deployment, Kubernetes is recommended as an underlying infrastructure to manage FATE system. For more detail, please refer to Deployment on Kubernetes.

More instructions can be found in KubeFATE.



    • Database Prerequisites

      • Schema scripts

    • Other Installation Requirements

      • Jump Host Requirements

      • Network Requirements

      • Bare Metal Node Requirements

      • Execution Requirements (Bare Metal Only)

  •    Installation High-Level Overview

    • Bare Metal Deployment Guide

      • Install Bare Metal Jump Host

      • Creating a Node Inventory File

      • Creating the Settings Files

      • Running


    • Virtual Deployment Guide

      • Standard Deployment Overview

      • Snapshot Deployment Overview

      • Special Requirements for Virtual Deployments

        • Install Jump Host

        • Verifying the Setup - VMs

    • Upstream Deployment Guide

      • Upstream Deployment Key Features

      • Special Requirements for Upstream Deployments

      • Scenarios and Deploy Settings for Upstream Deployments

      • Including Upstream Patches with Deployment

      • Running

      • Interacting with Containerized Overcloud

  • Verifying the Setup as defined the Akraino validation feature project plus any additional testing specific to the blue print

Running Tests

A script to run all the unittests has been provided in ./federatedml/test folder.

Once FATE is installed, tests can be run using:

sh ./federatedml/test/run_test.sh

All the unittests shall pass if FATE is installed properly.

  • Developer Guide and Troubleshooting

    • Utilization of Images

    • Post-deployment Configuration

    • Debugging Failures

    • Reporting a Bug

  • Uninstall Guide

  • Troubleshooting

    • Error Message Guide

  • Maintenance

    • Blue Print Package Maintenance

      • Software maintenance
      • Hardware maintenance
    • Blue Print Deployment Maintenance

  • Frequently Asked Questions

  • License

  • References

  • Definitions, acronyms and abbreviations

  • No labels