[ 
https://issues.apache.org/jira/browse/LIBCLOUD-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771026#comment-13771026
 ] 

Chris Krough commented on LIBCLOUD-402:
---------------------------------------

{quote}
13:00 <@pquerna> Kami_: the method of this working is defaintely adding new 
UUIDs of iages
                 with the same string names
13:01 <@pquerna> so, people in libcloud commonly do the string find for Ubuntu 
12.04 or
                 whatevr
13:01 <@pquerna> would get the new images
{quote}

So, this ticket should probably just introduce the ability to specify an 
OS-DCF:diskConfig of AUTO or MANUAL, but default behavior should do whatever 
the disk image defaults to. Users who are resolving their image id from an OS 
string on each deploy may be surprised.



                
> Handle default partitioning change in Rackspace driver
> ------------------------------------------------------
>
>                 Key: LIBCLOUD-402
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-402
>             Project: Libcloud
>          Issue Type: Task
>          Components: Compute
>            Reporter: Tomaz Muraus
>
> http://developer.rackspace.com/blog/new-features-in-cloud-servers-key-pairs-and-manual-disk-partitioning.html
> http://www.rackspace.com/knowledge_center/article/understanding-and-using-automatic-and-manual-disk-partitioning-in-the-rackspace-cloud
> https://gist.github.com/ckrough/6b1f4de4901fc7965f6c#file-gistfile1-txt-L20-L21
> {quote}
> [16:05] <     ckrough> | how are people dealing with the upcoming rackspace 
> default partitioning change? (auto->manual)
> [16:18] <       Kami_> | ckrough: i haven't heard anyone talking about it 
> here yet, but should be relatively easy for us to update the 
>           driver to default to auto to preserve backward compatibility
> {quote}
> Edit: Added more links since the FAQ entry is vague and not really clear.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to