Cisco is providing the community with a packaged version of the Openstack Folsom release with opensource components delivering additional service assurance functionality such as HA, monitoring, and Cisco enabled networking via Quantum.

== Cisco Edition of OpenStack ==

A validated deployment based on [http://puppetlabs.com Puppetlabs] scripted OpenStack services on an [http://ubuntu.com Ubuntu 12.04 LTS] platform.

Developer support email: openstack-support@cisco.com

The Cisco Openstack Edition based on the Openstack Folsom release, is qualified as follows:
Ubuntu 12.04.01 LTS
KVM
UCS and Nexus Hardware

Included in the Cisco release are the following capabilities that have been configured and qualified:
Active/Active HA: Unlike most existing solutions today, which are active/standby, Cisco has utilized off the shelf opensource components to develop an active/active model for the Folsom release of openstack. Included in this architecture are RabbitMQ redundancy, MySQL redundancy, and load balancing (HA Proxy). Cisco is presenting a blueprint of the architecture at the Grizzly summit. The Cisco Edition provides the appropriate configuration files to enable active/active HA.
Monitoring: A basic architecture to monitor the system processes and physical components using collectD, graphite, and Nagios is qualified for the Folsom Openstack release. The Cisco Edition provides the appropriate configuration files to enable this baseline monitoring model.
Quantum for Cisco components: In addition to contributing to Quantum in Folsom, Cisco has qualified Quantum with its Quantum Plugin for Cisco products. The Qualification covers the new V2 interface in Folsom, and enables users to replicate Nova like functionality on UCS and Nexus platforms.

== Installation (Cisco Edition on Folsom)==

[[OpenStack:Folsom | OpenStack Folsom Single controller with multi-compute deployments]]

== Installation (Essex Release) ==

[[OpenStack:Essex_All_In_One | OpenStack Essex All-in-One deployments]]

[[OpenStack:Essex_Multi_Node_HA | OpenStack Essex Control Plane High Availability ]]

== Configuration ==

[[OpenStack:Quantum | Configuring Cisco Quantum Plugin Framework in Folsom]]

== Reference Architecture ==

[[OpenStack:Reference_Architectures:UCS_C2xx_M3 | UCS C2xx-M3 infrastructure reference]]

[[OpenStack:Monitoring_Architecture | Monitoring Architecture for the Cisco Edition]]

[[Category:Systems]][[Category:OpenSource]][[Category:OpenStack]]

OpenStack

2012-10-15T06:59:12Z

Dflorea:

OpenStack:Monitoring Architecture

2012-10-15T06:57:57Z

Dflorea: /* Title */

== Title ==

'''1. Introduction'''

There are multiple layers that need to be monitored in a production Openstack deployment environment to achieve Service Assurance. At a high level, these layers have been captured in the figure below –

[[Image:MonitoringLayers.png]]

 

'''2. Monitoring Tools Info''' a) Collectd

Collectd is an agent based system metrics collection tool. An agent is deployed on every host that needs to be monitored. It provides a configurable plugin architecture that enables collection, storage and processing of metrics based on need. The list of plugins supported by collectd is listed here [1]. b) Graphite

Graphite is real-time graphing system. It is compromised of two components – a webapp frontend and a backend storage application. It allows external application to feed monitoring data into it and then uses it’s “carbon” backend agent to process the data and store it in a specialized graphite database (eg: whisper). The graphite processes need to deployed on the monitoring management box only. Some of the advantages of using Graphite are captured here [2]. c) Nagios

Nagios is a service health check alerting system. It has plugin model that allows service checks to be carried on host groups and generate alerts/notifications in case of any issues detected. The Nagios-Core agent is running on the monitoring management box that provides a webapp frontend and a daemon that reads configurations from it’s resource files and object-definition files. Nagios-NRPE is an addon that allows Nagios to execute plugins on remote hosts.

[[Image:ComputeMonitoringStack.png]]

[[Image:MonitoringStackToolDeployments.png]]

 

'''3. Monitoring Stack'''

Nagios can be used as a stand-alone monitoring tool for graphing and for system metric collection. Also, it can be integrated with an external metrics data collection tool such as collectd using plugins. For graphing purpose, collectd provides a plugin option to provide data to Graphite interface.

a) Graphite Interface integrated with Collectd

[[File:GraphiteInterfaceWithCollectd.png]]

 

b) Nagios Service Health Check Interface

[[Image:NagiosServiceHealthCheck.png]]

OpenStack:Monitoring Architecture

2012-10-15T06:57:25Z

Dflorea: /* Title */

== Title ==

'''1. Introduction'''

There are multiple layers that need to be monitored in a production Openstack deployment environment to achieve Service Assurance. At a high level, these layers have been captured in the figure below –

[[Image:MonitoringLayers.png]]

 

'''2. Monitoring Tools Info''' a) Collectd

Collectd is an agent based system metrics collection tool. An agent is deployed on every host that needs to be monitored. It provides a configurable plugin architecture that enables collection, storage and processing of metrics based on need. The list of plugins supported by collectd is listed here [1]. b) Graphite

Graphite is real-time graphing system. It is compromised of two components – a webapp frontend and a backend storage application. It allows external application to feed monitoring data into it and then uses it’s “carbon” backend agent to process the data and store it in a specialized graphite database (eg: whisper). The graphite processes need to deployed on the monitoring management box only. Some of the advantages of using Graphite are captured here [2]. c) Nagios

Nagios is a service health check alerting system. It has plugin model that allows service checks to be carried on host groups and generate alerts/notifications in case of any issues detected. The Nagios-Core agent is running on the monitoring management box that provides a webapp frontend and a daemon that reads configurations from it’s resource files and object-definition files. Nagios-NRPE is an addon that allows Nagios to execute plugins on remote hosts.

[[Image:ComputeMonitoringStack.png]]

[[Image:MonitoringStackToolDeployments.png]]

 

'''3. Monitoring Stack'''

Nagios can be used as a stand-alone monitoring tool for graphing and for system metric collection. Also, it can be integrated with an external metrics data collection tool such as collectd using plugins. For graphing purpose, collectd provides a plugin option to provide data to Graphite interface.

a) Graphite Interface integrated with Collectd

[[File:GraphiteInterfaceWithCollectd.png]]

b) Nagios Service Health Check Interface

[[Image:NagiosServiceHealthCheck.png]]

OpenStack:Monitoring Architecture

2012-10-15T06:55:35Z

Dflorea: /* Title */

== Title ==

'''1. Introduction'''

There are multiple layers that need to be monitored in a production Openstack deployment environment to achieve Service Assurance. At a high level, these layers have been captured in the figure below –

[[Image:MonitoringLayers.png]]

 

'''2. Monitoring Tools Info''' a) Collectd

Collectd is an agent based system metrics collection tool. An agent is deployed on every host that needs to be monitored. It provides a configurable plugin architecture that enables collection, storage and processing of metrics based on need. The list of plugins supported by collectd is listed here [1]. b) Graphite

Graphite is real-time graphing system. It is compromised of two components – a webapp frontend and a backend storage application. It allows external application to feed monitoring data into it and then uses it’s “carbon” backend agent to process the data and store it in a specialized graphite database (eg: whisper). The graphite processes need to deployed on the monitoring management box only. Some of the advantages of using Graphite are captured here [2]. c) Nagios

Nagios is a service health check alerting system. It has plugin model that allows service checks to be carried on host groups and generate alerts/notifications in case of any issues detected. The Nagios-Core agent is running on the monitoring management box that provides a webapp frontend and a daemon that reads configurations from it’s resource files and object-definition files. Nagios-NRPE is an addon that allows Nagios to execute plugins on remote hosts.

[[Image:ComputeMonitoringStack.png]]

[[Image:MonitoringStackToolDeployments.png]]

 

'''3. Monitoring Stack'''

Nagios can be used as a stand-alone monitoring tool for graphing and for system metric collection. Also, it can be integrated with an external metrics data collection tool such as collectd using plugins. For graphing purpose, collectd provides a plugin option to provide data to Graphite interface.

[[File:GraphiteInterfaceWithCollectd.png]]

[[Image:NagiosServiceHealthCheck.png]]

OpenStack:Monitoring Architecture

2012-10-15T06:55:02Z

Dflorea: /* Title */

== Title ==

'''1. Introduction'''

There are multiple layers that need to be monitored in a production Openstack deployment environment to achieve Service Assurance. At a high level, these layers have been captured in the figure below –

[[Image:MonitoringLayers.png]]

 

'''2. Monitoring Tools Info''' a) Collectd

Collectd is an agent based system metrics collection tool. An agent is deployed on every host that needs to be monitored. It provides a configurable plugin architecture that enables collection, storage and processing of metrics based on need. The list of plugins supported by collectd is listed here [1]. b) Graphite

Graphite is real-time graphing system. It is compromised of two components – a webapp frontend and a backend storage application. It allows external application to feed monitoring data into it and then uses it’s “carbon” backend agent to process the data and store it in a specialized graphite database (eg: whisper). The graphite processes need to deployed on the monitoring management box only. Some of the advantages of using Graphite are captured here [2]. c) Nagios

Nagios is a service health check alerting system. It has plugin model that allows service checks to be carried on host groups and generate alerts/notifications in case of any issues detected. The Nagios-Core agent is running on the monitoring management box that provides a webapp frontend and a daemon that reads configurations from it’s resource files and object-definition files. Nagios-NRPE is an addon that allows Nagios to execute plugins on remote hosts.

[[Image:ComputeMonitoringStack.png]]

[[Image:MonitoringStackToolDeployments.png]]

 

'''3. Monitoring Stack'''

Nagios can be used as a stand-alone monitoring tool for graphing and for system metric collection. Also, it can be integrated with an external metrics data collection tool such as collectd using plugins. For graphing purpose, collectd provides a plugin option to provide data to Graphite interface.

[[Image:NagiosServiceHealthCheck.png]]

[[File:GraphiteInterfaceWithCollectd.png]]

2012-10-15T06:45:46Z

Dflorea:

File:MonitoringStackToolDeployments.png

2012-10-15T06:45:46Z

Dflorea:

File:ComputeMonitoringStack.png

2012-10-15T06:45:46Z

Dflorea:

OpenStack:Monitoring Architecture

2012-10-15T06:41:36Z

Dflorea: /* Title */

== Title ==
[[File:MonitoringLayers.png]]

2012-10-13T00:20:39Z

Dflorea: /* Management */

== Cisco OpenStack Edition ==

Main Information landing page [http://www.cisco.com/go/openstack http://www.cisco.com/go/openstack]

Developer support email: openstack-support@cisco.com

== Installation ==

[[OpenStack:Folsom | OpenStack Folsom Single controller with multi-compute deployments]]

[[OpenStack:Essex_All_In_One | OpenStack Essex All-in-One or single controller multi-compute deployments]]

[[OpenStack:Essex_Multi_Node_HA | OpenStack Essex Multi-node controller Highly Available control plane]]

[[OpenStack:Folsom_All_In_One | Cisco OpenStack Edition All-in-One or single controller multi-compute deployments]]

[[OpenStack:Essex_Swift_HA | Adding Swift to an OpenStack deployment]]

== Management ==
test

== Reference Architecture ==

[[OpenStack:Reference_Architectures:UCS_C2xx_M3 | UCS C2xx-M3 infrastructure reference]]

== Validation Status ==

== OpenStack Blueprints ==

[[OpenStack:Blueprints:High_Availability_Control_Plane | High Availability for the OpenStack Control Plane]]

[[Category:Systems]][[Category:OpenSource]][[Category:OpenStack]]

OpenStack

2012-10-13T00:19:51Z

Dflorea: /* Cisco OpenStack Edition */

== Cisco OpenStack Edition ==

Main Information landing page [http://www.cisco.com/go/openstack http://www.cisco.com/go/openstack]

Developer support email: openstack-support@cisco.com

== Installation ==

[[OpenStack:Folsom | OpenStack Folsom Single controller with multi-compute deployments]]

[[OpenStack:Essex_All_In_One | OpenStack Essex All-in-One or single controller multi-compute deployments]]

[[OpenStack:Essex_Multi_Node_HA | OpenStack Essex Multi-node controller Highly Available control plane]]

[[OpenStack:Folsom_All_In_One | Cisco OpenStack Edition All-in-One or single controller multi-compute deployments]]

[[OpenStack:Essex_Swift_HA | Adding Swift to an OpenStack deployment]]

== Management ==

== Reference Architecture ==

[[OpenStack:Reference_Architectures:UCS_C2xx_M3 | UCS C2xx-M3 infrastructure reference]]

== Validation Status ==

== OpenStack Blueprints ==

[[OpenStack:Blueprints:High_Availability_Control_Plane | High Availability for the OpenStack Control Plane]]

[[Category:Systems]][[Category:OpenSource]][[Category:OpenStack]]