Alexander Finger
2013-01-12 12:52:28 UTC
http://goo.gl/0B5Wr
We have received some further proposals for talks on OUCE2013!
While the initially proposed talks were focused on know-how and technology,
we have now submissions featuring user stories and integration with COTS
software like HP's Remedy or IBM's Netcool.
*NMS config management - like a boss*
"I'm using Redmine and SVN for my OpenNMS documentation and change
management. All changes are depicted as Redmine tickets. So i have a good
view for each process, diff-views for my changes and i'm able to switch
back to my old configuration if something went wrong.
Certainly my environment and all records are in german language. And i have
no experiences in doing english presentations. At the moment i'm not sure
in which language i will do this presentation. But i'm trying to push my
english skills until there. Is there a deadline for this this decision?"
*OpenNMS meets VMware Infrastructure*
Virtualization changed the way of day-to-day operations of IT
administrators. The deployment of virtual machines is an easier and simpler
process than installing new physical hardware and the possibilities of
moving virtual machines between host systems reduces maintenance windows
and downtimes. The virtualization of hardware also introduced new ways of
monitoring and measuring performance of virtualized IT services. The
integration of these features in network management and monitoring systems
is needed for a secure and proactive operation of virtualized
infrastructures. This talk presents the idea and development process of
integrating VMware vSphere virtual infrastructures in OpenNMS.
*OpenNMS Remedy Integration*
"Describe a recent OpenNMS integration with Remedy Incident Management
System.
The objective are to display the general behavior of Trouble Ticket
Integration in opennms and to show how to integrate and configure remedy
system into."
*Element Management System for an HP based enterprise solution and SNMPv3
alarm forwarding and syncronization with Netcool*
"Nokia Siemens Networks provided a Customer Experience Management solution
to Vodafone Global, able to load, aggregate and transform the data from the
OpCos in a central repository where OpCos can schedule ad-hoc reports. The
solution included an Element Management System offering fault and
performance management functions based on OpenNMS, which was configured and
customized (thanks to Antonio Russo's contribute) in order to:
- monitor with the adequate depth Oracle processes, HP Brocade SAN
switches, Cisco switches, HP Blade servers, HP EVA 4400 storage, OS
resources (disks, memory...). Particular attention has been dedicated to
the HP agent integration (trap based) which has lead to strong changes on
the HP event XML files provided by OpenNMS out of box
- act as single point of integration for the northbound Umbrella Management
System (Netcool)
- forward to Netcool only the alarms that are evaluated as relevant for VF
according to configurable filter criteria
- forward traps via SNMPv3 or SNMPv2 and according to a MIB wrapping the
alarm format managed by OpenNMS.
- feature a trap based heartbeat functionality just to periodically notify
Netcool that OpenNMS is alive
- implement a trap based synchronization functionality that allows Netcool
to synchronize its alarms on demand
- be installed and deployed in high availability exploiting the clustering
functionality offered by the operating system (Rhel Cluster)."
*How to FAIL with OpenNMS*
"All aboard the failboat!
We all prefer to succeed, but we must sometimes fail. Lucky for you, many
people have gone before you into the facepalm wasteland. This talk will
recount a handful of real-world stories which illustrate what *not* to do
in a project involving OpenNMS.
We have received some further proposals for talks on OUCE2013!
While the initially proposed talks were focused on know-how and technology,
we have now submissions featuring user stories and integration with COTS
software like HP's Remedy or IBM's Netcool.
*NMS config management - like a boss*
"I'm using Redmine and SVN for my OpenNMS documentation and change
management. All changes are depicted as Redmine tickets. So i have a good
view for each process, diff-views for my changes and i'm able to switch
back to my old configuration if something went wrong.
Certainly my environment and all records are in german language. And i have
no experiences in doing english presentations. At the moment i'm not sure
in which language i will do this presentation. But i'm trying to push my
english skills until there. Is there a deadline for this this decision?"
*OpenNMS meets VMware Infrastructure*
Virtualization changed the way of day-to-day operations of IT
administrators. The deployment of virtual machines is an easier and simpler
process than installing new physical hardware and the possibilities of
moving virtual machines between host systems reduces maintenance windows
and downtimes. The virtualization of hardware also introduced new ways of
monitoring and measuring performance of virtualized IT services. The
integration of these features in network management and monitoring systems
is needed for a secure and proactive operation of virtualized
infrastructures. This talk presents the idea and development process of
integrating VMware vSphere virtual infrastructures in OpenNMS.
*OpenNMS Remedy Integration*
"Describe a recent OpenNMS integration with Remedy Incident Management
System.
The objective are to display the general behavior of Trouble Ticket
Integration in opennms and to show how to integrate and configure remedy
system into."
*Element Management System for an HP based enterprise solution and SNMPv3
alarm forwarding and syncronization with Netcool*
"Nokia Siemens Networks provided a Customer Experience Management solution
to Vodafone Global, able to load, aggregate and transform the data from the
OpCos in a central repository where OpCos can schedule ad-hoc reports. The
solution included an Element Management System offering fault and
performance management functions based on OpenNMS, which was configured and
customized (thanks to Antonio Russo's contribute) in order to:
- monitor with the adequate depth Oracle processes, HP Brocade SAN
switches, Cisco switches, HP Blade servers, HP EVA 4400 storage, OS
resources (disks, memory...). Particular attention has been dedicated to
the HP agent integration (trap based) which has lead to strong changes on
the HP event XML files provided by OpenNMS out of box
- act as single point of integration for the northbound Umbrella Management
System (Netcool)
- forward to Netcool only the alarms that are evaluated as relevant for VF
according to configurable filter criteria
- forward traps via SNMPv3 or SNMPv2 and according to a MIB wrapping the
alarm format managed by OpenNMS.
- feature a trap based heartbeat functionality just to periodically notify
Netcool that OpenNMS is alive
- implement a trap based synchronization functionality that allows Netcool
to synchronize its alarms on demand
- be installed and deployed in high availability exploiting the clustering
functionality offered by the operating system (Rhel Cluster)."
*How to FAIL with OpenNMS*
"All aboard the failboat!
We all prefer to succeed, but we must sometimes fail. Lucky for you, many
people have gone before you into the facepalm wasteland. This talk will
recount a handful of real-world stories which illustrate what *not* to do
in a project involving OpenNMS.