Your SlideShare is downloading. ×

Fuel's current use cases, architecture and next steps

440

Published on

Fuel is open source initiative which provides great automation and flexibility for: …

Fuel is open source initiative which provides great automation and flexibility for:
* CentOS and Ubuntu provisioning on bare metal servers
* Disk partitioning, including software RAIDs. Support of hardware RAIDs is in the roadmap
* Complex network configurations, including VLANs, GRE and bonding
* Network verification (VLANs, DHCP) before deployment
* Automated deployment of OpenStack components and Ceph
* Health Check - a set of short-running tests to ensure functionality of deployed environment

Published in: Engineering, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
440
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
37
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Fuel & its Architecture Mike Scherbakov Fuel Lead
  • 2. ● What is Fuel? ● How it works (high level) ● User Experience ● Components ● Additional functions ● What Fuel already deploys? ● Roadmap ● Where to get Fuel? ● Resources & Development processes Agenda
  • 3. Fuel targets a position to become a control plane of your Data Center ● Hardware Discovery ● Switches configuration [to be implemented] ● Network Verification ● OS provisioning on bare metal ● Deployment of OpenStack and beyond ● Post-deployment checks of OpenStack What is Fuel?
  • 4. Manual steps to setup an environment: ● Hardware planning ● Network configuration How it works now (high level)
  • 5. Manual steps to setup an environment: ● Hardware planning ● Network configuration ● [Live demo] Installation of Fuel Master node ● [Automated] Hardware discovery process How it works now (high level)
  • 6. How it works: Hardware Discovery Fuel Master (b) PXE (a) Power on (c) discovery image (d) agent REST API call node-1
  • 7. User Experience: UI (Live Demo)
  • 8. User Experience: CLI (Live Demo) ● Covers everything we can do via UI ● Allows even more
  • 9. Components: Nailgun
  • 10. ● Written on Python ● Exposes internal data via REST API ● Concentrates up to 90% of deployment logic ● Transforms user input (UI, CLI) into deployment data (JSON) ● Keeps tasks status and all information in DB ● Uses SQLAlchemy, Alembic for DB access and migrations Components: Nailgun
  • 11. Components: Naily & Astute
  • 12. ● Naily consumes messages sent by Nailgun ● Naily & Astute are both written in Ruby ● Astute uses MCollective RPC ● Has bindings to provisioning ● Tracks progress of deployment, provisioning ● Supports operations (adding/removing nodes) ● Small in comparison with Nailgun Components: Naily & Astute
  • 13. Components: OSTF (Health Check)
  • 14. Architecture: bigger picture
  • 15. ● Health Check ● Network Checker ○ DHCP ○ VLANs ● Diagnostic Snapshot ● Logs collection & calculation of operations progress ● [In development] Master node upgrade capabilities Additional Functions
  • 16. ● Core OpenStack components in HA fashion ○ nova-network & Neutron ○ Ceilometer ● Savanna (Hadoop on top of OpenStack) ● Murano (Windows DCs on top of OpenStack) ● Ceph What Fuel already deploys?
  • 17. ● Fuel Master node upgrades ● Patching & Upgrade of OpenStack ● Replacement of Cobbler by Ironic ● …. suggest us more here: https://blueprints. launchpad.net/fuel In the Roadmap
  • 18. ● Download ISO from Mirantis (need to register) ● Build your own ISO: docs.mirantis.com/fuel-dev ● All other info starts from wiki.opentstack. org/wiki/fuel … Issues? Talk to us at #fuel-dev & https: //launchpad.net/~fuel-dev Where to get
  • 19. ● Code at github.com/stackforge/fuel-* ● OpenStack Gerrit for code reviews ● Launchpad for tracking bugs & blueprints ● #fuel-dev & fuel-dev@lists.launchpad.net ● Development docs at docs.mirantis.com/fuel-dev ● fuel-jenkins.mirantis.com - open CI Development Processes
  • 20. Q&A Mike Scherbakov mscherbakov@mirantis.com

×