Namos openstack-manager
Download as PPTX, PDF0 likes340 views
Kanagaraj Manickam presents Namos, an OpenStack manager that aims to solve problems in the OpenStack ecosystem. Namos provides RESTful APIs and a graphical user interface to manage OpenStack deployments, services, devices, and configurations. It discovers deployment architectures, checks compliance, and provides a single pane of glass for configuration. Namos facilitates adding, updating, deleting, and managing devices and their quotas. This allows operators more control and developers a way to build features based on managed devices.
Namos openstack-manager
- 1. NAMOS OpenStack Manager Kanagaraj Manickam @mrkanag / IRC: KanagarajM OpenStack Summit, Austin, TX April 26th 2016
- 2. About Author Kanagaraj Manickam Sr. System Architect @ Huawei, Bangalore, India. • Core-reviewer @ Heat, OpenStack. • Active participant @ Open-O an Global SDN & NFV-Orchestrator . • Expert in Data-center Server, Storage management and automation. • Founder of namos – OpenStack Manager) 2
- 3. Cloud Data-center OpenStack is an distributed cloud operating system provides an platform for setting up public or private cloud on top of heterogeneous data-center. For operator, It provides set of configurable device- drivers/plug-ins to consume the required hardware-devices and software-defined-devices from cloud data-center regions. And for consumers, it provides required Restful API, CLI to provision and manage their cloud resources such as instances, storage volumes, networks, etc. programmatically. OpenStack
- 4. OpenStack Eco-system Commercial OpenStack Installer Community OpenStack Data-center management Software & Element managers Data-center hardware/sotware- defined devices OpenStack Installer Roles: 1. OpenStack installation & configuration 2. Provides HA, scalable deployment Datacenter management software Roles: 1. Manage life cycle of data-center devices 2. Supports the business operations like performance management, backup, recovery, etc Data-center Roles: 1. Hardware storage, server and network devices 2. Software defined Server, Storage & network devices Community OpenStack Roles: 1. Platform for setting up private & public cloud 2. Device drivers and plug-ins
- 5. Problems in OpenStack Eco-system Commercial OpenStack Installer Community OpenStack Data-center management Software & Element managers Data-center hardware/software- defined devices OpenStack Installer 1. configuration schema maintenance - head-ache. Datacenter management software 1. No coherence on business operation across device- consumption in OpenStack and same device- management datacenter software Data-center 1. Consuming high-end hypervisor across more than one + nova-compute is not possible, leads to single-point-of- failure. Similar problem in cinder-volume as well. Community OpenStack 1. No feature could be developed based on device/service (like tenancy @ device level, quota @ device level, reservation @ device and/or it’s capability level) 2. Zero-configuration vs Fine-tuning of service/device across deployment is night-mare 3. No Device on-boarding with required driver. 4. No cloud deployment architecture viewer/validator (problem of installer)
- 6. How to solve Facilitates: 1. Add, Update, Delete a device with its Endpoint 2. Helps to maintain device capability (useful in quota and reservation) 3. Attach, Detach a device with Service using selected device driver 4. Enable, Disable a Service/Service component (ex: nova-compute) 5. Fine-tune Configuration of Driver 6. Configure Service with messaging, db, logging, auth. across deployment 7. 360 degree view (helps in deployment validation) Region Model complete OpenStack deployment and device consumptions as programmable entities accessible via RESTful API Device Node Device Driver Service Component Service Device Endpoint Device Capability Device Configuration Service Configuration
- 7. Namos Features OpenStack Deployment Architecture Auto-Discoverer (ODaaD) 3600 view & Compliance checker OpenStack Configuration as a Service (OCaaS) Single pane of glace for OpenStack deployment configuration OpenStack Device manager (ODMAN) Shared-wall between Cloud data-center & OpenStack OpenStack Service Manager (OSMAN) Control panel for deployed OpenStack services RestfulAPI,CLI&HorizonUIplug-in Accesspoint SAMPLE USE-CASES As a Operator, I can add, view update, remove the device use. As a Admin, I can manage device quota As user, I could request for device capabilities based reservation. As s developer, I can implement new feature based on device, service
- 8. OpenStack’s Eco-system is happy !! Commercial OpenStack Installer Community OpenStack Data-center management Software & Element managers Data-center hardware/sotware- defined devices Commercial OpenStack Installer 1. Namos maintains the configuration schema, so all commercial and open-source installers are freed from maintenance head-ache. 2. Operator could on-board device using Namos, those devices are not enabled by installer by default. Datacenter management software 1. Namos helps to control the device-consumed in OpenStack via REST API, which helps datacenter software to integrate it’s business operation. Data-center 1. As Namos manages device consumed across OpenStack services, more than one nova-computes could be configured to operate on same hypervisor by enhancing compute drivers. Community OpenStack 1. Feature like tenancy @ device level, quota @ device level, reservation @ device and/or it’s capability level could be developed based on device being consumed/service got deployed 2. Namos provides RESTful api for managing OpenStack Service, it’s Components and their configurations. It also maintains the configuration schema for every device supported in the OpenStack, So Zero-configuration and Fine-tuning of service/device across deployment became easier. 3. Users are not required to study the configuration guide. For device on-boarding with appropriate driver, user could check via RESTful API provided by Namos. So device on-boarding become easier. 4. ODaaD helps to discover the services deployment automatically and gives 360 degree view
- 9. Thank you https://github.com/openstack?utf8=%E2%9C%93&query=namos https://wiki.openstack.org/wiki/Namos -- Kanagaraj Manickam Founder of Namos Namos just binds OpenStack deployment and its eco-system in a programmatic way where operators are facilitated to fine-tune the device/service control and developers finds a way to develop any feature based on the managed devices
Editor's Notes
- #6: As a Operator: No cloud validation tool available to verify the deployed cloud against deployment architecture Not able to do any compliance check such as security policy Configuring services across different deployment nodes is night-mare. Not able to put the devices/services/nodes into maintenance mode without disturbing the running cloud. No way, I could view the list of devices being consumed from data-center region. No way, I could view/manage the data-center device consumed by a given device-driver, If I want to stop or start a service, I end-up logging in to all those deployment nodes where that service’s component installed, which is an cumbersome job. As a Developer: Not able to configure the same devices across multiple service components due-to double counting of device capabilities. It affects the quota management as well. Not able to achieve the ‘tenancy at the device level’
- #11: Assume all the cloud nodes (controller, Storage, compute and network) are up and running , Data center also in place Now Openstack github provides the complete source code Configuration guide helps operator to configure OpenStack Installers There are many Openstack Distros available in the market and it does provide installers for devices It packs the source code from github and covert them as installable packages It read thru the configuration guide and make configuration automation All these 3 together forms the installer During the installation, respective services got installed into appropriate servers Openststack distro installs required devices in the datacenter It configures the intalled devices in respective service nodes Namos is brought up here to take care of configuration automation complete irrespective of the OpenStack installers