May 20

VEP-S released

VEP-S is a trustworthy platform that uses the Virtual Execution Platform (VEP) cloud middleware software to interface multiple Infrastructure as a Service (IaaS) clouds. It has the following additional features to previous release:

  • OCCI support for IaaS interaction
  • OCCI SLAs: definition and negotiation of machine readable agreements which are “linked” with the associated cloud resources
  • Monitoring usage of the resources

Watch the demo here: VEP-S demo

Dec 03

VEP-S team is attending the Result Day Helsinki 2014

Come and ask the VEP-S to show you the demo!

Download the Poster and Flyer.

Nov 20

VEP integrates the SLA OCCI extension

Now VEP integrates the SLA OCCI extension, a new standard draft proposed to the OCCI community.
The draft describes how to link resources with Service Level Agreement (SLA) agreements negotiated between users and cloud providers.
Stay tuned for the next release!

Nov 01

VEP supports OCCI from OGF

VEP has integrated the support for OCCI cloud management standard!
This enables supporting new cloud IaaS implementing OCCI.

Oct 03

VEP 2.2 released

Virtual Execution Platform is a cloud middleware software that interfaces multiple Infrastructure as a Service (IaaS) clouds. VEP offers two types of services:

1 – management of data centres for a Cloud administrator allowing greater control on the physical resources;
2 – management of end-user distributed applications made up of several inter-networked virtual machines on a Cloud with an interface facilitating the deployment and application life-cycle management.

The VEP team is proud to announce VEP v2.2, a new version replacing the old one (v2.1) correcting bugs and offer a more stable experience.
The supported features are:

Openstack: VEP allows to manage a OpenStack Cloud System offering a completely transparent interface;
OpenNebula: VEP allows to manage a OpenNebula Cloud System offering a completely transparent interface;
Open Standard support: VEP respects the DTMF OVF and CIMI v1 standards;
Data centre representation: VEP stores the provider datacenter layout to enforce some SLA requirements;
Physical resource allocation and resource provisioning for end user’s applications;
SLA-awareness: Cloud administrators and users can specify constraints for the resources associated to an application;
Easy interfaces: easy browser based cloud administrator and end-user application management interfaces;
VM Scheduling: the new VEP scheduler is independent from the IaaS Scheduler to allow placement constraints on the resources;
Advance Reservation: VEP allows to reserves a number of VMs from a start date to an end date to guarantee the deployment (in addition to run an application in best effort mode);
Web User Interface: VEP provides an easy web interface where the user can improve his experience using our tool;
Remote Storage: VEP allows to create remote storage using GAFS or to mount an already existing storage;
OAuth Support: VEP includes an OAuth client to retrieve delegated certificate to use inside the created VMs;

VEP aims at offering the full management of IaaS cloud while shielding the administrators the complexity of managing heterogeneous resources. VEP is designed to provide interoperability by offering a uniform way of representing and managing the resources of a cloud provider. VEP could also easily enable the participation of a Cloud provider to a federation seamlessly and it does proper VM contextualization and application lifecycle management. Additionally it publishes application events and metrics for application’s monitoring and SLA enforcement.
VEP enables interoperability through its RESTful interface based on the DMTF’s Cloud Infrastructure Management Interface (CIMI) standard v1. The CIMI model defines a framework for the application life cycle management on a cloud provider infrastructure, with applications generated from an Open Virtualization Format (OVF) document. VEP extends the CIMI API to support the deployment of applications under SLA terms.

VEP RESTful interface allows cloud administrators to manage and control numerous aspect of the service offering. For VM scheduling to work properly, the datacenter topology information is desired in VEP. The software has a simple and intuitive interface to allow administrators input topology information about their datacenter. This interface also permits the administrator to selectively permit hosts to be managed via the VEP software. VEP never schedules a VM on a host not permitted for use by the administrator.

Try the new release!

An Installation Guide and a User Guide is available at the VEP project site (https://project.inria.fr/vep/documentation/).
The VEP team is working hard to make VEP an even better system; the OCCI support is around the corner.
Stay tuned for the the next releases!

Feb 18

A new EIT ICT Labs activity built on VEP

EIT ICT Labs has just financed a new activity in the Future Cloud Action line to mature the VEP technology and transfer it to industry. Partners are Intel and Reply.

Dec 02

OFFLINE – Maintenance Host

We apologize, but we will be offline on Thursday 5 December from 12:00pm to 3:00 pm due to maintenance work.

 

Cheers,

VEP team

Nov 19

VEP at Supercomputing 2013

VEP team will be present at Supercomputing 2013, November 18-21
Visit us at SC13 in Denver on Inria booth #2116

Here it is the related poster.

Nov 19

VEP 2.1 available

Virtual Execution Platform is a cloud middleware software that interfaces multiple Infrastructure as a Service (IaaS) clouds. VEP offers two types of services:

1 – management of data centres for a Cloud administrator allowing greater control on the physical resources;
2 – management of end-user distributed applications made up of several inter-networked virtual machines on a Cloud with an interface facilitating the deployment and application life-cycle management.

The VEP team is proud to announce VEP v2.1 (download link here ), a new version replacing the old one (v2.0) adding new features and fixing the known bugs.
The supported features are:

OpenNebula: VEP allows to manage a OpenNebula Cloud System offering a completely transparent interface
Open Standard support: VEP respects the DTMF OVF and CIMI standards;
Data centre representation: VEP stores the provider datacenter layout to enforce some SLA requirements
Physical resource allocation and resource provisioning for end user’s applications
Easy interfaces: easy browser based cloud administrator and end-user application management interfaces
VM Scheduling: the new VEP scheduler is independent from the IaaS Scheduler to allow placement constraints on the resources;
Advance Reservation: VEP allows to reserves a number of VMs from a start date to an end date to guarantee the deployment (in addition to run an application in best effort mode).
Web User Interface: VEP provides an easy web interface where the user can improve his experience using our tool
Remote Storage: VEP allows to create remote storage using GAFS or to mount an already existing storage.
OAuth Support: VEP includes an OAuth client to retrieve delegated certificate to use inside the created VMs

VEP aims at offering the full management of IaaS cloud while shielding the administrators the complexity of managing heterogeneous resources. VEP is designed to provide interoperability by offering a uniform way of representing and managing the resources of a cloud provider. VEP could also easily enable the participation of a Cloud provider to a federation seamlessly and it does proper VM contextualization and application lifecycle management. Additionally it publishes application events and metrics for application’s monitoring and SLA enforcement.
VEP enables interoperability through its RESTful interface based on the DMTF’s Cloud Infrastructure Management Interface (CIMI) standard. The CIMI model defines a framework for the application life cycle management on a cloud provider infrastructure, with applications generated from an Open Virtualization Format (OVF) document. VEP extends the CIMI API to support the deployment of applications under SLA terms.

VEP RESTful interface allows cloud administrators to manage and control numerous aspect of the service offering. For VM scheduling to work properly, the datacenter topology information is desired in VEP. The software has a simple and intuitive interface to allow administrators input topology information about their datacenter. This interface also permits the administrator to selectively permit hosts to be managed via the VEP software. VEP never schedules a VM on a host not permitted for use by the administrator.

Try the new release!

An Installation Guide and a User Guide is available at the VEP project site (https://project.inria.fr/vep/documentation/).
The VEP team is working hard to make VEP an even better system; the Openstack support is around the corner.
Stay tuned for the the next releases!

Feb 18

VEP 2.0 release

Virtual Execution Platform is a cloud middleware software that interfaces multiple Infrastructure as a Service (IaaS) clouds. VEP offers two types of services:

  1. management of data centres for a Cloud administrator allowing greater control on the physical resources;
  2. management of end-user distributed applications made up of several inter-networked virtual machines on a Cloud with an interface facilitating the deployment and application life-cycle management.

The VEP team is proud to announce VEP v2.0 (download link here), a new version replacing the old one (v1.1). The supported features are:

  • OpenNebula: VEP allows to manage a OpenNebula Cloud System offering a completely transparent interface
  • Open Standard support: VEP respects the DTMF OVF and CIMI standards;
  • Data centre representation: VEP stores the provider datacenter layout to enforce some SLA requirements
  •  Physical resource allocation and resource provisioning for end user’s applications
  • Easy interfaces: easy browser based cloud administrator and end-user application management interfaces
  • VM Scheduling: the new VEP scheduler is independent from the IaaS Scheduler to allow placement constraints on the resources;
  • Advance Reservation: VEP allows to reserves a number of VMs from a start date to an end date to guarantee the deployment (in addition to run an application in best effort mode).

VEP aims at offering the full management of IaaS cloud while shielding the administrators the complexity of managing heterogeneous resources. VEP is designed to provide interoperability by offering a uniform way of representing and managing the resources of a cloud provider. VEP could also easily enable the participation of a Cloud provider to a federation seamlessly and it does proper VM contextualization and application lifecycle management. Additionally it publishes application events and metrics for application’s monitoring and SLA enforcement.
VEP enables interoperability through its RESTful interface based on the DMTF’s Cloud Infrastructure Management Interface (CIMI) standard. The CIMI model defines a framework for the application life cycle management on a cloud provider infrastructure, with applications generated from an Open Virtualization Format (OVF) document. VEP extends the CIMI API to support the deployment of applications under SLA terms.

VEP RESTful interface allows cloud administrators to manage and control numerous aspect of the service offering. For VM scheduling to work properly, the datacenter topology information is desired in VEP. The software has a simple and intuitive interface to allow administrators input topology information about their datacenter. This interface also permits the administrator to selectively permit hosts to be managed via the VEP software. VEP never schedules a VM on a host not permitted for use by the administrator.

Try the new release!

An Installation Guide and a User Guide is availabe at the VEP project site (https://project.inria.fr/vep/documentation/).

The VEP team is working hard to make VEP an even better system; the Openstack support is around the corner.
Stay tuned for the the next releases!
>