cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6276) Affinity Groups within projects
Date Sun, 29 Nov 2015 18:51:11 GMT


ASF GitHub Bot commented on CLOUDSTACK-6276:

Github user pdube commented on the pull request:
    @DaanHoogland I was talking about the implementation of APIs. Example, let's say you create
a new module, call it Exampe. So we can list, create and delete Example. What are the classes
that we expect someone to create? ExampleService, ExampleDoa, ExampleVO, etc.? That is what
I was refering to. That way, if we decide that the best way to write modules is to have a
service that is self contained, then we can phase out the use of the QueryService

> Affinity Groups within projects
> -------------------------------
>                 Key: CLOUDSTACK-6276
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Ingo Jochim
> Hello,
> I like to have the features "Affinity Group" and "Project" combined.
> As far as I know I cannot use Affinity Groups within Projects.
> Thanks and regards,
> Ingo

This message was sent by Atlassian JIRA

View raw message