GitHub user bernardodemarco added a comment to the discussion: In Cloudstack
same VPC across different Projects
Hello, @chunkyen
> Can a VPC network tier be assigned to a project post creation?
No. As far as I know, the tierβs ownership can only be defined at creation time.
> Does it mean that the project members cannot manage the VPC related settings
> such as ACL?
VPC management is the responsibility of its owner. Regarding ACL lists
specifically, they are managed at the tier scope. Therefore, tier owners can
manage them. The ACS GUI does not currently support this operation; it is only
available via API calls or CloudMonkey. For example:
<details>
<summary>Examples of API calls to <code>replaceNetworkACLList</code></summary>
```
(u1) π > list networkacllists
{
"count": 2,
"networkacllist": [
{
"description": "Default Network ACL Allow All",
"id": "31f04b13-a510-11ef-8a39-9a34acb639ea",
"name": "default_allow"
},
{
"description": "Default Network ACL Deny All",
"id": "31f01731-a510-11ef-8a39-9a34acb639ea",
"name": "default_deny"
}
]
}
(u1) πΏ > replace networkacllist aclid=31f01731-a510-11ef-8a39-9a34acb639ea
networkid=eb35d1ba-e591-4191-93b7-1e972f95d779
{
"success": true
}
(u1) π¦ > replace networkacllist aclid=31f04b13-a510-11ef-8a39-9a34acb639ea
networkid=eb35d1ba-e591-4191-93b7-1e972f95d779
{
"success": true
}
(u1) π > replace networkacllist aclid=31f04b13-a510-11ef-8a39-9a34acb639ea
networkid=2f3ba57c-caf2-4a5d-b179-26f2cfd5a330
{
"success": true
}
(u1) π > replace networkacllist aclid=31f01731-a510-11ef-8a39-9a34acb639ea
networkid=2f3ba57c-caf2-4a5d-b179-26f2cfd5a330
{
"success": true
}
```
</details>
GitHub link:
https://github.com/apache/cloudstack/discussions/12818#discussioncomment-16284655
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
