Clustering and provisioning in the Amazon cloud
OpenSVC now has ip address and volume drivers for amazon ec2. These drivers allow clustering between ec2 instances. Also check out http://docs.opensvc.com/agent.service.provisioning.html to see how to provision a full clustered service in a single OpenSVC command.
Event in Paris
We will be presenting OpenSVC at the 22th April 2015 IT Innovation Forum. We look forward to the opportunity to describe the benefits of our solutions to the CRiP members and to collect their feedback. The event details are hosted at www.itiforums.com
Service definition templates
A comment we often get from OpenSVC users is that usr/share/doc/template.env is not really helping when you need to add a new resource to a service : too unstructured and outdated at places. Fine, issue tackled. usr/share/doc/ now contains per-resource configlets automatically generated from the agent keyword dictionnary classes. As these classes are used by the service and resource provisioning features, they are guaranteed up-to-date and the configlets structure is strict. The result can be seen in the online documentation at http://docs.opensvc.com/agent.template.env.html
Ceph rados drivers merged
The OpenSVC agent now embeds drivers to handle rados block devices as services resources. A disk group driver handles mapping, unmapping, locking, unlocking and provisioning. A snapshot and a clone resource drivers are also available. The provisioning capability is of special interest here, as it allows end-to-end service provisioning in a single command : from storage allocation to the application deployment.
Live collector update
The internet-hosted OpenSVC collector is now upgraded to the lastest codebase and uses OpenSVC and docker for the software stack integration. The DRP replication is handled by the OpenSVC btrfs send/receive driver. We consider btrfs and docker have matured enough to trust them some of our serious production services at OVH. If you are interested in how to setup similar services, please get in touch: we are happy to share.
Request an On-Site Product Demonstration
The best way to truly understand the power of OpenSVC is to see it working. We would be happy to come out to your site for presentation and demonstration purposes. This is free and without obligation. Get in touch with us at firstname.lastname@example.org
Compliance documentation refresh
The compliance framework has evolved in the last year, and the documentation needed an update to cover all new features. Done. Have a look at http://docs.opensvc.com
Docker container support
The OpenSVC agent now has a container-type driver for docker micro-containers. This driver manages a private per-service docker daemon and registry, so that a service is still relocatable. Docker and OpenSVC are very complementary : OpenSVC handles resources needed by docker containers (public ips, vg, fs, scsi persistent reservations) and replication. Docker, handles application lifecycle and application dependencies. Documentation is available at http://docs.opensvc.com
HP 3par support
The excellent HP 3par arrays are now supported in the OpenSVC infrastructure. The agent now has a driver for async replication and an array configuration extractor. The collector has an array configuration parser. OpenSVC also provides a RESTful command proxy to allow drivers in a DMZ to access to 3par arrays through a command filtering proxy. Docs are available at http://docs.opensvc.com
Package versioning change
The windows package versioning rules dictate that the 3rd packet of the version vector must be an integer between 0 and 65534. To comply we decided to change the versioning of packages generated from the opensvc 'master' code branch. Before, 1.5-140102.1004 would read as "the package generated from the master branch up to the commit dated 2014/01/02 10:04". Now, 1.5-10256 reads "the package generated from the master branch up to the 256th commit since last stable branch opening". We realize versioning changes, especially those reverting to a lower version, can be painful. We apologize for the inconvenience.