Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Support CCI instance resize #45

Open
bodenr opened this issue Feb 19, 2014 · 4 comments
Open

Support CCI instance resize #45

bodenr opened this issue Feb 19, 2014 · 4 comments

Comments

@bodenr
Copy link
Contributor

bodenr commented Feb 19, 2014

The ability to resize an instance (CCI) is an important aspect to managing compute. This feature is obviously supported in native nova instances, but no such support exists in jumpgate.

This issue/enhancement is intended to track that support -- adding the ability to resize a CCI a la jumpgate.

Related issues: softlayer py client upgrade

@swapnil90
Copy link

@bodenr :the CCI resize is implemented and am waiting for it to be merged in softlayer-client[1]
so upgrade/resize will support CPU and memory,
any thoughts on how should we proceed further on resize with respect to disk?
Can we let the user now for the time being as a note of some sort in doc block that disk will not be upgraded?[
1]softlayer/softlayer-python#299

@bodenr
Copy link
Contributor Author

bodenr commented Mar 31, 2014

@swapnil90 that's great news about mem/cpu resize...

yes I think you guys could consider adding a note to the jumpgate compatibility matrix about whats supported and what's not from a resize perspective.. I was looking at the nova code / docs trying to see if there was a way to return info about extensions to indicate from an API perspective this wasn't supported, but it's not entirely clear to me without more digging.

@swapnil90
Copy link

@bodenr : i had also looked into openstack API and such for passing/giving info to user, but didnt find it either.
I had a query regarding disks mentioned in flavor, they are all local right and not SAN?

@bodenr
Copy link
Contributor Author

bodenr commented Apr 2, 2014

@swapnil90 - If I understand your question you are asking jumpgate only supports LOCAL disk right now? If so the answer (last time I checked) is only LOCAL disks are supported at the present moment..

See: #27
and: #61

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants