cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Angus (JIRA)" <>
Subject [jira] [Assigned] (CLOUDSTACK-10237) L2 networks should be allowed to be shared and used in projects
Date Wed, 17 Jan 2018 21:55:00 GMT


Paul Angus reassigned CLOUDSTACK-10237:

    Assignee: Nicolas Vazquez

> L2 networks should be allowed to be shared and used in projects
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-10237
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions:
>         Environment: Centos7, KVM, advanced zones with vlan based isolation
>            Reporter: Jean-Francois Nadeau
>            Assignee: Nicolas Vazquez
>            Priority: Major
> Hi all,
> I'm testing 4.11-rc1 and the new L2 network type feature as shown at []
> I want to use this as a replacement to a shared network offering with no DHCP which works
to support an external DHCP server but still required to fill some CIDR information.
> I thought the intent was that L2 network type was to replace the previous approach when
required to integrate an existing network/DHCP.
> If I attempt to provision a VM in a project as the root admin using the L2 network I
get denied... apparently because they are not shared and I can't make them public.
> ('HTTP 531 response from CloudStack', <Response [531]>, \{u'errorcode': 531, u'uuidList':
[], u'cserrorcode': 4365, u'errortext': u'Unable to use network with id= 7712102b-bbdf-4c54-bdbf-9fddfa16de46,
permission denied'}) 
> Provisioning in the root project works just fine....  but really I want to use L2 networks
in user projects even if only the admin can do so.

This message was sent by Atlassian JIRA

View raw message