and Operations Fuel: Reliable deploymentfiles.meetup.com/10602292/Fuel for reliable deployment and operations (1).pdfOpenStack upstream codebase, Mirantis is the biggest company in

Copyright © 2015 Mirantis, Inc. All rights reservedwww.mirantis.com

Fuel: Reliable deployment and Operations

Sam Stoelinga （林海洋）

Copyright © 2015 Mirantis, Inc. All rights reserved Page 2

Agenda

• Introduction• Goal of today• Fuel intro

• Deployment• Workflow• Planning• Network & node configuration• Fuel master installation• PXE booting of nodes• Create environment & Deploy

• Operations

• Intro• LMA

• Fuel Roadmap• Q&A


About Mirantis

Community driven:As a Top 3 contributor to the OpenStack upstream codebase, Mirantis is the biggest company in OpenStack with no other product or technology agenda. We drive upstream innovation to customers, and drive customer use cases back into trunk.

1 3 600One agenda:OpenStack OpenStack is all we do at Mirantis, delivering the technology, integration, training and support required for companies to succeed with production-grade open source cloud at scale.

Deep bench: Our 600+ engineers and technologists provide the deepest bench of real-world experience developing and deploying open source cloud infrastructure across a full spectrum of customers, industries and use cases.

We deliver scalable, automated OpenStack for mission-critical production


Goal of today

听完分享每一个人都知道怎么部署和基本维护一个OpenStack的生态环境


Mirantis OpenStack

• The most robust OpenStack distribution on the market

• Fuel takes the guesswork out of deployment

• Broad choice of fully-tested technologies

Simply download, boot, and deploy Mirantis OpenStack


Fuel: Deployment and Management

• Guided configuration & management

• Flexible technology choices

• Production-ready HA deployment

• Health validation• Network verification• Deployment validation• Cloud health checks


Fuel: Network topology

Colour Network name Bridge Comments

Admin/PXE None Untagged. Serves for PXE boot and OS image (bootstrap, Host OS) transfer

Managementbr-mgmt This network should be represented as tagged or untagged isolated L2 network

segment. Serves for:● Communication between OpenStack components and supporting services

(RabbitMQ, MySQL, etc)● Ceph public traffic (datapath from VMs to block devices)

Public+Floating IP

br-ex This network should be represented as tagged or untagged isolated L2 network segment. Serves for external API access and providing VMs with connectivity to/from networking outside the cloud. Floating IPs are implemented with L3 agent + NAT rules on Controller(s)

Storage br-storage

This network should be represented as tagged or untagged isolated L2 network segment. Ceph replication traffic.

Private br-prv Serves for 802.1q (VLAN) tagged traffic of private network segments for tenants. Used only for VLAN segmentation type.


Fuel: Network topology

Computenode

1

Computenode

N

Controllernode (s)

1-3

Ceph-OSDnode

1

Ceph-OSDnode

N

theFuel

Masternode

External networks

OVS OVS OVS


Fuel: Hardware discovery

Fuel Master (b) PXE request

(a) power on

(c) discover image

(d) agent REST API call

node-1


Deployment: General workflow

• Hardware planning (Manual)

• Network & Node configuration (Manual)

• Installation and configuration of Fuel master node (Manual)

• Hardware discovery (Automated)

• Create and deploy OpenStack environments (Automated)


Deployment: 1. Hardware planning

Calculate CPU, memory, storage and network requirements

• CPU: Computational work? Web services? Overcommit?

• Memory: How much memory per compute node? Controller

• Storage: Local storage? Cinder storage? Ceph? LVM?

• Network: Bandwidth per VM? Storage, private and management on 10 GB when possible

Check the Fuel Planning guide for details


Deployment: 2. Network & Node configuration

• Change BIOS (Network boot 1st option, virt enabled)

• Setup RAID• Normally OS on RAID1, ephemeral on RAID-10, Ceph OSD’s on JBOD

• Configure switches

• Network cabling


Deployment: 2. Simple Network config example

Admin needs to be untagged, public should be tagged. When possible separate public & admin


Deployment: 3. Installation of Fuel Master

• Download and burn ISO to CD/USB

• When booting in Grub add kernel param: showmenu=yes

• Change network settings of Fuel master

• IMPORTANT: Make sure Fuel master PXE/admin is on a private totally isolated L2 segment. No other DHCP servers allowed on admin network


Deployment: 4. Hardware discovery

• Start booting up your OpenStack nodes (controller, compute, etc)

• Make sure all nodes show up and that hardware is detected

• Check network speeds

• Check that all disks have been detected


Deployment: 5. Create environment & Deploy

• Create environment in UI

• Assign roles to discovered nodes

• Verify network connectivity

• Deploy OpenStack


Operations: Intro

• Operations is important! Bad ops == SLA not achieved

• LMA toolchain is your buddy

• Logging

• Monitoring with zabbix

• Alerting


Operations: Monitoring with Zabbix

• Enterprise-ready monitoring solution

• Deployed and configured automatically with Fuel 5.1-6.0

• Enable experimental features:/etc/fuel/version.yaml add experimental to product_groups and restart servicescheck documentation for details

• Configure node as Zabbix monitoring role


Operations: Monitoring with Zabbix

• Configured automatically to check all OpenStack related components:• MySQL, RabbitMQ, all openstack-api’s, libvirt, openvswitch,....

• System resources: CPU, memory, network, disk...

• Pro-active monitoring and alerting


Operations: LMA toolchain plugin

• stackforge/fuel-plugin-lma-collector for Fuel 6.1

• Capture all raw operational datanotifications, logs, system resources

• Increase the operational visibility

• Extendible, easy to integrate:Nagios, Zabbix, Netuitive(SaaS)


Operations: LMA toolchain plugin

• collectd: for collecting system related data

• Heka: • collecting logs/notifications

• send data to storage backend

• Storage backends:• InfluxDB: used for time-series data, e.g. cpu usage

• ElasticSearch: used for log and notifications data, e.g. service down, vm created etc.


Mirantis OpenStack 6.0

• Support for OpenStack Juno

• Fuel Plug-ins: reliably add OpenStack functionality

• Deploy Mirantis-certified functionality and create your own

• Examples: GlusterFS back-end storage, LBaaS using HAProxy

• Resiliency and scale• Certification of Fuel-deploy environments to 100

nodes

• Improvements in High Availability

• New kernel for Ubuntu-derived deployments

• Expanded VMWare support• New reference architecture and planning guide

• Support for vSphere Datastore

• Nova-network VLAN manager support for vCenter

• Networking Enhancements• Multiple L3 agents. Improved resiliency, performance in

multi-tenant deployments.

• Multiple L2 networks. Deploy a single environment with multiple L2 segments.

• Experimental – Almost Awesome Features• Fuel upgrade and environment update.

• Zabbix-based monitoring

• Support for vCenter and NSX

• Fuel Plug-ins: VPNaaS and NetApp Cinder


How can we help you succeed with OpenStack?

Q&A

Also we’re hiring!关注我们 http://weibo.com/mirantis

Documents

and Operations Fuel: Reliable deploymentfiles.meetup.com/10602292/Fuel for reliable deployment and operations (1).pdfOpenStack upstream codebase, Mirantis is the biggest company in