Skip to content

[LIBCLOUD-537] Added support for generic image management at Rackspace and EC2#277

Closed
ghost wants to merge 4 commits into
trunkfrom
unknown repository
Closed

[LIBCLOUD-537] Added support for generic image management at Rackspace and EC2#277
ghost wants to merge 4 commits into
trunkfrom
unknown repository

Conversation

@ghost

@ghost ghost commented Apr 17, 2014

Copy link
Copy Markdown

I was planning to take care of GCE in this first push as well. However, Google presents an interesting challenge with their persistent disk model and their use of the snapshot and image terms. We could use snapshots as a replacement for images. However, this would then limit our ability to use the default images provided by Google. It seems like we actually need a factory for evaluating both the images and snapshots in order to fold in GCE. I completed the _supported_methods_image_management.rst as well in case we want to include it in the documentation. I did submit an email regarding this effort to the dev mail list but I didn't hear anything back so I just went ahead and made the change.

@ghost

ghost commented Apr 17, 2014

Copy link
Copy Markdown
Author

Fixed docstring errors

@Kami

Kami commented Apr 21, 2014

Copy link
Copy Markdown
Member

Sorry for the delay, I will look some time in the next couple of days.

@ghost

ghost commented Apr 22, 2014

Copy link
Copy Markdown
Author

No worries I'm just running off of my branch.

@ghost

ghost commented Apr 24, 2014

Copy link
Copy Markdown
Author

Also noticing we need to add a generic state attribute to NodeImage in compute/base.py and have a statemap for NodeImage in compute/types.py. I'm primarily working to EC2/Rackspace so once we get an initial patch in place I can extend that to support a state on NodeImage for at least those drivers but specify it as None by default so it doesn't interfere with other drivers.

Comment thread libcloud/compute/base.py

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does the reboot argument does?

Also, is this available across all the providers or is it provider specific?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For Amazon it makes sure the instance reboots in order to guarantee file system integrity. I looked into Amazon, Rackspace, Google, and even Azure. It does appear that this is an Amazon specific argument and it is not needed as the default should be okay. I will remove it from the base and put back the original implementation in the ec2.py file.

@Kami

Kami commented Apr 24, 2014

Copy link
Copy Markdown
Member

This pull request mostly looks good to be, but it would be nice if it can also get reviwed by a couple of other people - /cc @mahendra @Jc2k

@ghost

ghost commented Apr 24, 2014

Copy link
Copy Markdown
Author

Is there anything specific I need to do to trigger another Travis CI build?

@Kami

Kami commented Apr 24, 2014

Copy link
Copy Markdown
Member

Nope, it should be triggered manually but it might take a while.

@Kami

Kami commented Apr 28, 2014

Copy link
Copy Markdown
Member

Sorry for the delay, I've merged your changes into trunk.

I've noticed you manually created the supported methods rst file. Those files
are generated by ./contrib/generate_provider_feature_matrix_table.py script which I updated (08d7d95) to also support generating this file for image management API.

@asfgit asfgit closed this in d2604af Apr 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants