org.jclouds.openstack.nova.options
Class CreateServerOptions
java.lang.Object
org.jclouds.openstack.nova.options.CreateServerOptions
- All Implemented Interfaces:
- Binder, MapBinder
public class CreateServerOptions
- extends Object
- implements MapBinder
- Author:
- Adrian Cole
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
CreateServerOptions
public CreateServerOptions()
bindToRequest
public <R extends HttpRequest> R bindToRequest(R request,
Map<String,String> postParams)
- Description copied from interface:
MapBinder
- creates and binds the POST payload to the request using parameters specified.
- Specified by:
bindToRequest
in interface MapBinder
- See Also:
PayloadParam
withFile
public CreateServerOptions withFile(String path,
byte[] contents)
- You may further customize a cloud server by injecting data into the file system of the cloud
server itself. This is useful, for example, for inserting ssh keys, setting configuration
files, or storing data that you want to retrieve from within the instance itself. It is
intended to provide a minimal amount of launch-time personalization. If significant
customization is required, a custom image should be created. The max size of the file path
data is 255 bytes while the max size of the file contents is 10KB. Note that the file contents
should be encoded as a Base64 string and the 10KB limit refers to the number of bytes in the
decoded data not the number of characters in the encoded data. The maximum number of file
path/content pairs that can be supplied is 5. Any existing files that match the specified file
will be renamed to include the extension bak followed by a time stamp. For example, the file
/etc/passwd will be backed up as /etc/passwd.bak.1246036261.5785. All files will have root and
the root group as owner and group owner, respectively and will allow user and group read
access only (-r--r-----).
withMetadata
public CreateServerOptions withMetadata(Map<String,String> metadata)
- Custom cloud server metadata can also be supplied at launch time. This metadata is stored in
the API system where it is retrievable by querying the API for server status. The maximum size
of the metadata key and value is each 255 bytes and the maximum number of key-value pairs that
can be supplied per server is 5.
bindToRequest
public <R extends HttpRequest> R bindToRequest(R request,
Object input)
- Specified by:
bindToRequest
in interface Binder
Copyright © 2009-2011 jclouds. All Rights Reserved.