new cloud facade API

[mkasztelnik]

We are currently working on new Cloud Facade API. You can see current status (it is still WIP) of this API here: http://149.156.10.137/help/api (please use MI token to login).

As a conclusion https://github.com/b3c/vphshare/blob/master/masterinterface/cyfronet/cloudfacade.py should be updated.

We are planning to have RC1 version ready at the end of next week (on 99.99% rest interface for security proxies and security policies will not be changed). It will stay on development environment until all other VPH-Share components will be compatible with new CF API. After that we will install this atmosphere version on production.

Please let me know when you will be able to take a look at this API and decide when it can be updated in MI.

[ecoto]

Hi Marek,

Last week I asked Daniel If we could have a little document instructing us about the naming changes. Basically, what would be the equivalence between the old names and the new names. This would help us changing/checking to the new API

I was wondering if this could be provided before the actual API update.

Thanks,

Ernesto Coto Scientific Software Developer Center for Computational Imaging & Simulation Technologies in Biomedicine (CISTIB) INSIGNEO Institute for In silico Medicine The University of Sheffield Room B85 - Portobello Centre Pitt St. Sheffield S1 4ET United Kingdom T: +44 (0) 114 222 0166 E: e.coto@sheffield.ac.uk

On 25 November 2013 11:15, Marek Kasztelnik notifications@github.comwrote:

We are currently working on new Cloud Facade API. You can see current status (it is still WIP) of this API here: http://149.156.10.137/help/api(please use MI token to login).

As a conclusion https://github.com/b3c/vphshare/blob/master/masterinterface/cyfronet/cloudfacade.pyshould be updated.

We are planning to have RC1 version ready at the end of next week (on 99.99% rest interface for security proxies and security policies will not be changed). It will stay on development environment until all other VPH-Share components will be compatible with new CF API. After that we will install this atmosphere version on production.

Please let me know when you will be able to take a look at this API and decide when it can be updated in MI.

— Reply to this email directly or view it on GitHubhttps://github.com/b3c/vphshare/issues/49 .

[mkasztelnik]

@ecoto please take a look at #50

[mkasztelnik]

@asaglimbeni is it possible to set deadline for this issue?

[asaglimbeni]

We are planing when working on it, I let you know soon.

[mkasztelnik]

@asaglimbeni any deadline for this issue? We are planning to migrate cloud facade into new one in the middle of January.

[asaglimbeni]

Hi Marek, I already working on I could set the deadline on 10 January.

[asaglimbeni]

Hi Marek, I updated the Masterinterface with the new cloud facade API. https://github.com/b3c/vphshare/commit/8095c9997159a162ab2e84468200f83c4db4a487 But during the test if I try to edit an existing policy or create a new one I recive every time the same error 401 unautorized. Maybe now do I need some new roles in my ticket? Please test it and let me know if everything is ok. Thank you

[mkasztelnik]

@asaglimbeni unfortunately it does not work for me as well. Most probably because header name is not correct. Please change it into MI-TICKET instead of mi_ticket. The second one should be used when ticket is included in request url as a query param. See http://149.156.10.137/help/api for details and examples.

[asaglimbeni]

Thank you, with MI-TICKET it works fine . https://github.com/b3c/vphshare/commit/189364b779a4ee30512f6c681a39525c40f44972 For me we can close this issue. Alfredo

[mkasztelnik]

:+1: