(PRIYA) Rajgurunagar Call Girls Just Call 7001035870 [ Cash on Delivery ] Pun...
ONAP on Vagrant for ONAPers
1. ONAP on Vagrant for ONAPers
Victor Morales
https://about.me/electrocucaracha
2. Agenda
• Problem statement
• ONAP on Vagrant
• Why Vagrant?
• Install prerequisites
• How to generate HTML documentation?
• Key features
• Synced Folders
• Plugins
• Shell Provisioning
• Architecture
• Usage
3. Problem Statement
• Allow new ONAP developers to
ramp up on to active
development quickly
• Reduce the cost to the
community in responding to
simple environment setup
4. ONAP on Vagrant
It is a project that sets up a development environment for building
artifacts required for every ONAP service. Its goal is to unify different
development practices in an automated provisioning mechanism.
Moved from :
https://github.com/electrocucaracha/vagrant-onap
To
https://git.onap.org/integration/tree/bootstrap/vagrant-onap
5. It’s a tool for building and managing
virtual machine environments in a single
workflow. With an easy-to-use workflow
and focus on automation, Vagrant lowers
development environment setup time,
increases production parity, and makes
the "works on my machine" excuse a
relic of the past.
Why Vagrant?
9. Synced Folders
Enables Vagrant to sync a folder on the host machine to the guest
machine, allowing you to continue working on your project's files on
your host machine, but use the resources in the guest machine to
compile or run your project.
10. Shell Provisioning
Provisioners in Vagrant allow you to automatically install software, alter
configurations, and more on the machine as part of the vagrant up process. Shell
provisioning is ideal for users new to Vagrant who want to get up and running
quickly and provides a strong alternative for users who are not comfortable with a
full configuration management system such as Chef or Puppet.
11. Plugins
They are powerful, first-class citizens that extend
Vagrant using a well-documented, stable API that can
withstand major version upgrades.
12. Architecture
Folders:
• doc – Contains documentation about Advanced Features. It’s
goal is to provide information about the usage of the tool
• lib – Contains scripts to clone repositories, configure services,
build images, compile source code, etc. for ONAP services.
• opt – Shared folder that stores ONAP source code
• tests – Contains Unit Tests that ensure the correct functionality of
the scripts located into lib folder.
• tools – Contains scripts to facilitate some daily tasks.