VIFIB DESCENTRALIZED CLOUD COMPUTING

SlapOS is a decentralized Cloud Computing technology that can automate the deployment and configuration of applications in a heterogeneous environment.
1 - 4 of 4 records
Summary

Hi,

when requesting many instances by a script then sometimes I have a list of instances and I would like to know the partition_reference of each instance. But there is no getPartitionReference(), there is only getInstanceGuid(). With instance_guid I cannot request the instance. So at the moment I have to keep a dict or tuple when requestion many instance to not forget partition_reference. Is this by design or might an getPartitionReference() method be added in the future ?

Regards,

Klaus

From: Unknown User

Hi,

when requesting many instances by a script then sometimes I have a list of instances and I would like to know the partition_reference of each instance. But there is no getPartitionReference(), there is only getInstanceGuid(). With instance_guid I cannot request the instance. So at the moment I have to keep a dict or tuple when requestion many instance to not forget partition_reference. Is this by design or might an getPartitionReference() method be added in the future ?

Regards,

Klaus

Hello Klaus,

Long story short :

1/ I am writing a way to get all informations of a partition without having to use request. It will be used as a getter (on the contrary of request() which is more of a setter).

2/ In this new getter, I will include partition reference.

This should be done in the next days, but may require a bit more time to be put in production. I am using a new version of the REST HATEOAS API to do this.

There are currently no plans to include partition_reference in request(), but I am also introducing a way to get ALL services of a user (either from bash/CLI or from SLAP python library). Does it sounds OK for your use case? 

Regards,

Cedric 

From: Cédric De saint Martin
From: Unknown User

Hi,

when requesting many instances by a script then sometimes I have a list of instances and I would like to know the partition_reference of each instance. But there is no getPartitionReference(), there is only getInstanceGuid(). With instance_guid I cannot request the instance. So at the moment I have to keep a dict or tuple when requestion many instance to not forget partition_reference. Is this by design or might an getPartitionReference() method be added in the future ?

Regards,

Klaus

Hello Klaus,

Long story short :

1/ I am writing a way to get all informations of a partition without having to use request. It will be used as a getter (on the contrary of request() which is more of a setter).

2/ In this new getter, I will include partition reference.

This should be done in the next days, but may require a bit more time to be put in production. I am using a new version of the REST HATEOAS API to do this.

There are currently no plans to include partition_reference in request(), but I am also introducing a way to get ALL services of a user (either from bash/CLI or from SLAP python library). Does it sounds OK for your use case? 

Regards,

Cedric 

Hi Cedric,

sorry for late reply. Yes a getter with all partition information will make my use case much easier. I am very happy that you work on this. It will also help to reduce errors (sometimes I accidentally requested more instances because I used wrong reference when trying to get partition information).

Regards,

Klaus

From: Unknown User
From: Cédric De saint Martin
From: Unknown User

Hi,

when requesting many instances by a script then sometimes I have a list of instances and I would like to know the partition_reference of each instance. But there is no getPartitionReference(), there is only getInstanceGuid(). With instance_guid I cannot request the instance. So at the moment I have to keep a dict or tuple when requestion many instance to not forget partition_reference. Is this by design or might an getPartitionReference() method be added in the future ?

Regards,

Klaus

Hello Klaus,

Long story short :

1/ I am writing a way to get all informations of a partition without having to use request. It will be used as a getter (on the contrary of request() which is more of a setter).

2/ In this new getter, I will include partition reference.

This should be done in the next days, but may require a bit more time to be put in production. I am using a new version of the REST HATEOAS API to do this.

There are currently no plans to include partition_reference in request(), but I am also introducing a way to get ALL services of a user (either from bash/CLI or from SLAP python library). Does it sounds OK for your use case? 

Regards,

Cedric 

Hi Cedric,

sorry for late reply. Yes a getter with all partition information will make my use case much easier. I am very happy that you work on this. It will also help to reduce errors (sometimes I accidentally requested more instances because I used wrong reference when trying to get partition information).

Regards,

Klaus

 ah, and getting all the services of my user from bash/CLI will also help a lot because I now have so many services that I loose the overview.

Regards,

Klaus