Hi Lengyue,
I'm going to reply a couple of the items here, so I'm copying some of your original text from the original thread below. > > I am kinda confused about what we are seeking for in the new method. > I believe from our discussion this morning, the concern is that the current implementation introduces some unnecessary complexity, as Kacper mentioned last week, as well as creating some points of fragility that are either extra edge cases that we need to account for, or functionality that we actively have to build out support for, such as custom parsing of the messages that would be passed back from the other process. The goal with refactoring at this stage is to simplify by removing those edge cases and eliminating the extra custom work. In the near term, I think the decision was to go ahead and leverage the work that we have started and refactor to use pkgcloud or some other existing SDK. > > It seems like there are no suspend and resume instance api in pkgcloud. > I believe you are correct, from what I have seen so far. I have done a bit of digging, and can't seem to find if there was a design decision made, or if it was a decision due to commonality, or if it is simply just not implemented yet. If we need the extra functionality, we have several options, including simply directly calling the REST endpoint ourselves. http://developer.openstack.org/api-ref-compute-v2.1.html#os-multiple-create-v2.1 My $0.02. Hope that helps! Mario- From: owner-discuss@xxxxxxxxxxxxxxxxxxxxxxx [owner-discuss@xxxxxxxxxxxxxxxxxxxxxxx] on behalf of Lengyue Chen [lchen95@xxxxxxxxxxxx]
Sent: Monday, July 20, 2015 5:15 PM To: discuss@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: Changing way to invoke novaclient api in nds-webservice rest api It seems like there are no suspend and resume instance api in pkgcloud.
On Mon, Jul 20, 2015 at 4:08 PM, Lengyue Chen
<lchen95@xxxxxxxxxxxx> wrote:
|