You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/09/16 19:33:53 UTC

[jira] [Updated] (CLOUDSTACK-4679) createVPCOffering does not provide a way to supply service providers

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alena Prokharchyk updated CLOUDSTACK-4679:
------------------------------------------

    Fix Version/s:     (was: 4.2.1)
                   Future

Not required for 4.2.1, the fix should be submitted to the next big release (would go to master branch)
                
> createVPCOffering does not provide a way to supply service providers
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4679
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4679
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.2.0
>         Environment: 4.2
>            Reporter: Sowmya Krishnan
>            Assignee: Alena Prokharchyk
>             Fix For: Future
>
>
> createVPCOffering API doesn't provide a way to specify service providers. We can only choose the list of services that a VPC offers. Provider will be VPC VR by default and it remains VPC VR for any new VPC offering since we have no way of specifying a provider.
> Today we have 2 more possible providers apart from VPC VR viz, Netscaler and Internal LB. So if I want to create a VPC Offering with Netscaler as LB and only the following services: DHCP, DNS, SourceNAT, it is not possible today. The only option is to choose the Default VPC Offering with all services.
> We should allow createVPCOffering API to be able to accept service providers as well.

--
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