Feature #1556
Allow update action for VMs
| Status: | Closed | Start date: | 10/16/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.0 | |||
| Resolution: | Pull request: |
Description
Allow update action for VMs.
An example use case is the following:
- VM boots and contacts a server to generate a password
- The server writes the generated password to context and returns it to the VM
- Users can see the password from Sunstone or onevm, by looking at the CONTEXT var
Currently, it is impossible for the server to update the CONTEXT or the VM template
Related issues
Associated revisions
feature #1556: Add a new user template to the VM to store user defined variables. Add OCA Ruby & JAVA bindings for the new update method. Add command option for onevm tool.
Feature #1556: Add new elem to migrator, and xsd
Feature #1556: Remove help formatting, just in case it breaks something in the manpages later
Feature #1556: Move all the attributes used in the code to the internal template
Feature #1556: The parser for context & requirements looks for variables in both VM templates
feature #1556: upload new parser for vm_var
Feature #1556: onevm update does not allow users to change restricted attributes
History
#1
Updated by Ruben S. Montero over 8 years ago
- Tracker changed from Request to Feature
- Category set to Core & System
- Target version set to Release 4.0
This feature will be implemented by including a user template for the VMs, that can be updated and used to store custome data
#2
Updated by Ruben S. Montero over 8 years ago
- Assignee set to Ruben S. Montero
Needs to include a a DB migrator to add the user template to existing VMs
#3
Updated by Carlos Martín over 8 years ago
Needs API documentation, and compatibility guide entry
#4
Updated by Ruben S. Montero over 8 years ago
- Status changed from New to Closed