You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Aaron Peeler (Created) (JIRA)" <ji...@apache.org> on 2012/03/29 19:10:28 UTC

[jira] [Created] (VCL-571) EC2 API provisioning module

EC2 API provisioning module
---------------------------

                 Key: VCL-571
                 URL: https://issues.apache.org/jira/browse/VCL-571
             Project: VCL
          Issue Type: New Feature
          Components: database, vcld (backend), web gui (frontend)
            Reporter: Aaron Peeler
             Fix For: 2.4


To provide a provisioning method for cloud platforms that use EC2 api interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (VCL-571) EC2 API provisioning module

Posted by "Cameron Mann (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/VCL-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Mann reassigned VCL-571:
--------------------------------

    Assignee: Cameron Mann
    
> EC2 API provisioning module
> ---------------------------
>
>                 Key: VCL-571
>                 URL: https://issues.apache.org/jira/browse/VCL-571
>             Project: VCL
>          Issue Type: New Feature
>          Components: database, vcld (backend), web gui (frontend)
>            Reporter: Aaron Peeler
>            Assignee: Cameron Mann
>             Fix For: 2.4
>
>
> To provide a provisioning method for cloud platforms that use EC2 api interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (VCL-571) EC2 API provisioning module

Posted by "Cameron Mann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/VCL-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Mann updated VCL-571:
-----------------------------

    Attachment: EC2.pm

I’ve attached the code for our prototype EC2 API module.

1. My main focus right now is on implementing the capture subroutine.  Linux will be relatively simple.  I mentioned before that it looked like bundling a Windows instance would require external access to the disk image, but having investigated further, I’m not sure if that’s actually the case.  If anyone has experience here it would be great to pick your brain.

2. Right now the config file that contains the connection info for the endpoint and the machine types is just a Perl file that gets imported by the provisioning module.  Is there a preferred format?

3. Networking.  We talked about this problem at ICA CON: instances have one private NIC and use NAT for public IPs while VCL expects one public and one private NIC.  It was mentioned that VCL wants to be more flexible here and support a variable number of NICs which would solve the problem.  There wasn’t a very firm schedule for this feature though, so the question is would a short term solution be worth it?  The simplest solution is likely custom OS modules for Linux and Windows.
                
> EC2 API provisioning module
> ---------------------------
>
>                 Key: VCL-571
>                 URL: https://issues.apache.org/jira/browse/VCL-571
>             Project: VCL
>          Issue Type: New Feature
>          Components: database, vcld (backend), web gui (frontend)
>            Reporter: Aaron Peeler
>            Assignee: Cameron Mann
>             Fix For: 2.4
>
>         Attachments: EC2.pm
>
>
> To provide a provisioning method for cloud platforms that use EC2 api interface.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira