One thing I love about this blog site is the variety of developer-related topics – all created by the experts themselves! So, in case you missed any, here are the top 12 blog posting for 2013:
1. Setting up Django and Python 2.7 on Red Hat Enterprise 6 the easy way – This was the most popular article, by our developer evangelist, Langdon White. Great job, dude!
Continue reading “Our Top 12 Blog Articles of 2013”
This is part 2 of a 2-part article about Advanced Integration with RHEV-M. The first part is available here.
In the last part you learned how to perform different operations on the engine from the outside using the API/SDK. In this part you’ll learn how you can influence the engine from the inside, using extension APIs
In this section we will describe the following APIs:
- UI plugins API (also covered in http://ovedou.blogspot.com and http://www.ovirt.org/Features/UIPlugins) – an API that allows extending the Administrator Portal UI. It allows you to add UI components with a RHEV-M look-and-feel, but with your own functionality. Useful in order to integrate your product with the Administrator Portal
- Scheduling API – an API that allows you to change the way the the engine schedules VMs in your data center, and fit it to your specific needs
- VDSM hooks – A mechanism that allows you to modify the VM in different lifecycle events. Useful for modifying / extending the VM’s functionality
UI plugins API
Looking at the RHEV-M Administrator Portal, there are several main UI components:
Continue reading “Advanced Integration with RHEV-M – Part 2 of 2”
This is part 1 of a 2-part article about Advanced Integration with RHEV-M.
At CloudOpen Europe 2013, in Edinburgh, I presented a talk about advanced integration with the oVirt engine. This technical article is covering the contents of this session.
RHEV-M is a Large scale, centralized management for server and desktop virtualization. It is based on leading performance, scalability and security infrastructure technologies, focusing on KVM for best integration/performance. It provides an alternative to Center/vSphere, providing end-to-end IaaS platform.
In this post I’ll show you how you can integrate with the RHEV-M engine, covering both new and cool features, as well as some “old” useful features. Let’s start with the REST-based APIs. These APIs allow you to perform different operations on the engine externally. You can do anything using the REST APIs, even operations that aren’t exposed through the different UI interfaces.
Continue reading “Advanced integration with Red Hat Enterprise Virtualization Manager (RHEV-M) – Part 1 of 2”
OpenStack is picking up a lot of steam these days, but getting it installed can be a hassle. Lots of puppet-based installers have popped up to automate this arduous task. Using Foreman, however, administrators can not only configure and install OpenStack using puppet, but provision & add new compute nodes at their fancy.
The Foreman is a Ruby on Rails application that does configuration management with puppet and provisioning. We’ll use both of these features to make using & administering OpenStack easier. Our installer leverages PackStack, which includes great puppet modules for setting up OpenStack. Combining these to setup and manage OpenStack Grizzly is a breeze!
- At least three machines running RHEL 6.4 with an active subscription to RHEL OpenStack Platform or Red Hat Cloud Infrastructure.. We recommend your OpenStack Compute & Controller nodes run on bare metal.
- Each machine needs to have a resolvable FQDN
- Each machine needs to be subscribed to a proper RHEL subscription
- The Foreman server should have its firewall configured to allow inbound network traffic on TCP ports 80, 443 and 8140 for Foreman and Puppet to function correctly
- The host running Foreman may be running selinux in Enforcing mode, but you must first install the ruby193-foreman-selinux package. Both the OpenStack controller and compute nodes can also run in enforcing mode if you install the openstack-selinux package. You must also manually set a boolean on the controller node: setsebool -P httpd_can_network_connect on