History

Giannelos Roadmap

Okeanos & Fedcloud testbed Roadmap

EGI Fedcloud testbed consists of the following Scenarios:

  • VM management
  • Data management
  • Information Systems
  • Accounting
  • Monitoring
  • Notification
  • Federated AAi
  • VM Marketplace
  • Brokering
  • VM management

By now okeanos progress regarding fedcloud is limited to VM Management.
We can provide an OCCI interface which is fully compatible with our Compute
service (cyclades). This means that we can provision VMs with predefined Resource
Templates and OS Templates as described in OCCI infrastructure specs.

  • Data management

This mainly refers to CDMI (Cloud Data Management Interface).
There is no progress in this part of the testbed requirements.

Archipelagos our block storage service is still under development
and its not yet production ready. So, the first steps for okeanos to be compatible
with this scenario are:

  • Wait until Archipelagos API is ready and stable
  • Wait until Archipelagos is ready for production deployment

The next steps are:

  • Pithos (object storage) integration with CDMI
  • Archipelagos integration with CDMI
  • Develop a CDMI endpoint for okeanos

Estimated time for the CDMI part: 2 months (except of the time needed for the Archipelagos development)

  • Information systems

For the storage part: As long as okeanos storage is ready, the storage info
can easily be exposed using OCCI.

For the compute part: All the required data are available in the OS and Resource Templates provided by OCCI.
For the compute endpoint: Okeanos can use OCCI as an endpoint. We still need to implement the authentication in order to be compatible.
For the information system: We need to integrate LDAP with GLUE 2.0 capabilites to provide the info to fedcloud.

Estimated time: 3 weeks

Okeanos cannot provide lots of attributes required such as:

Storage:
  • Max Storage installed in the site
  • Storage throughput
Network:
  • Internal Bandwith
  • Outbound bandwith
  • Average latency
  • Accounting
    Lots of the accounting info could be derived from Aquarium, our billing service which is under development.
    Accounting middleware: We have to implement a driver to send accounting information from okeanos, compatible with what it is implemented from other members of the testbed

Roadmap:

  • By the time Aquarium is ready for production we have first to see the extra information that we need and make available those queries.
  • Implement the okeanos accounting middleware for the testbed.

Estimated time: 3 weeks (except of the work needed in the Aquarium part)

  • Monitoring

For the current demo a simple Nagios script can trigger an OK/ERROR status for the provisioned VM.
There are no details available for this scenario in the wiki, and it is still under construction.

  • Notification

This scenario is still being designed. Not enough info provided in the wiki
What is is being proposed is an AMQP based software, publishing messages with VM state changes.

Okeanos uses message queues for its internal notification, so the integration to fedcloud can be achieved with
a driver listening to our queues and publishing messages only for the fedcloud VMs and fedcloud users.

Estimated time: 3 weeks

  • Federated AAI
Roadmap:
  • X.509 Authentication in astakos (our Identity Management)
  • Implement X.509 feature in all components needed for the demo (OCCI, CDMI, Accounting, VM Marketplace)
  • VOMS integration is now needed.

Estimated time: 2 weeks

  • VM Marketplace

Authentication: needs X.509
OCCI: Current scenario requires the VMs to be exposed as OCCI storage instances. Our implementation uses the
Resource Template (flavour) OS Template (image) to provision VMs. So the marketplace needs to make available
to OCCI implementations like okeanos (pyssf-openstack) to register images the way it is describes in the OCCI
infrastructure spec.

Estimated time: If the VM marketplace is compatible with our implementation, we should be able to register images without any changes to our interface.

  • Brokering

This scenario refers to the goal of the fedcloud to provide the testbed with a unified abstracted view.
We cannot provide a roadmap from a technical scope, as it is the integration of all the above and its real life use.

Estimated work:

  • VM management
  • Data management: 2 months
  • Information Systems: 2-3 weeks
  • Accounting: 2-3 weeks
  • Monitoring
  • Notification: 2-3 weeks
  • Federated AAI: 2-3 weeks
  • VM Marketplace
  • Brokering

Fedcould-tf