Uh oh!
There was an error while loading. Please reload this page.
ipv6: support for isolated nw, vpc tiers - #262
Conversation
Feature PR: apache/cloudstack#5786 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
blueorangutan
commented
Feb 1, 2022
Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. (SL-JID 184) |
| .. |add-guest-ipv6-prefix-form.png| image:: /_static/images/cadd-guest-ipv6-prefix-form.png | ||
| :alt: Add Guest IPv6 Prefix form. | ||
| .. |add-public-ipv6-range-form.png| image:: /_static/images/add-public-ipv6-range-form.png | ||
| :alt: Add Public IPv6 Range form. | ||
| .. |add-ipv6-network-offering-form.png| image:: /_static/images/dd-ipv6-network-offering-form.png | ||
| :alt: Add IPv6 supported Network Offering form. No newline at end of file |
There was a problem hiding this comment.
some typos/c&p errors here. only one pic shows in the page.
shwstppr
commented
Feb 21, 2022
@blueorangutan docbuild |
blueorangutan
commented
Feb 21, 2022
@shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
blueorangutan
commented
Feb 21, 2022
Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. (SL-JID 202) |
| ##################### | ||
| Currently, CloudStack supports IPv6 isolated networks and VPC tiers only with **static** routes and therefore the administrator needs to add upstream IPv6 routes once a network is successfully deployed. | ||
| To facilitate the automation, *CloudStack Event Notification* can be used. CloudStack will generate appropriate events on network creation or deletion and while assigning or releasing a public IPv6 address for a network. Based on the events the corresponding network can be queried for the IPv6 routes that it needs configured in upstream network. |
There was a problem hiding this comment.
is cloudstack api also an option ?
I think few cloudstack users use event bus. it would be better to provide more resolutions.
There was a problem hiding this comment.
@weizhouapache on event bus, currently it just sends assigned IPv6, the event consumer will still have to call listNetworks API for getting the subnet,
> list networks id=d147f48c-69ee-4733-a7f9-6096e3e07a3f filter=id,name,ip6cidr,ip6gateway,ip6routes
{
"count": 1,
"network": [
{
"id": "d147f48c-69ee-4733-a7f9-6096e3e07a3f",
"ip6cidr": "2a00:1728:23:1000::/64",
"ip6gateway": "2a00:1728:23:1000::",
"ip6routes": [
{
"gateway": "2a00:1728:23:1140:1c00:30ff:fe00:9",
"subnet": "2a00:1728:23:1000::/64"
}
],
"name": "net6"
}
]
}
| |network-details-upstream-ipv6-routes.png| | ||
| IPv6 Firewall |
There was a problem hiding this comment.
Do we have firewall enabled/disabled option in network offerings ?
what's the default policy ?
There was a problem hiding this comment.
@weizhouapache no separate option right now. It will depend on Firewall service enabled for the network.
Also, default policy for egress requests will be governed by egressdefaultpolicy of the offering. Ingress it is deny
| Guest VMs in an isolated network or VPC tier can obtain both IPv4 and IPv6 IP addresses by using a supported network offering and appropriate configurations for IPv6 support by the administrator. | ||
| Both VR for such networks and the guest VMs using these networks obtain a SLAAC based IPv6 address. While VR is assigned an IPv6 address from the public IPv6 range, guest VMs get their IPv6 addresses from the IPv6 subnet assinged to the network. | ||
| Here's the sequence of events when IPv6 is used: |
There was a problem hiding this comment.
Is the "VLAN/VNI" supported in ipv6 range ?
If it is currently not supported, it is better to point it out.
There was a problem hiding this comment.
@weizhouapache will sync offline about this.
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
shwstppr
commented
Mar 15, 2022
@blueorangutan docbuild |
blueorangutan
commented
Mar 15, 2022
@shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
blueorangutan
commented
Mar 15, 2022
Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. (SL-JID 206) |
nvazquez
commented
Apr 26, 2022
Hi @shwstppr is this PR ready for review? |
shwstppr
commented
Apr 27, 2022
@nvazquez will mark ready once @weizhouapache LGTM it. |
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
shwstppr
commented
Apr 27, 2022
@blueorangutan docbuild |
blueorangutan
commented
Apr 27, 2022
@shwstppr a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
blueorangutan
commented
Apr 27, 2022
Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262. (SL-JID 233) |
* ipv6: support for isolated nw, vpc tiers Feature PR: apache/cloudstack#5786 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * typo fix Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * more typo Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * changes Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * change Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * public ip range note Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * vpc offering, global setting change Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * missing changes from previous commit Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * add detail about firewall and acl Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * typo Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Feature PR: apache/cloudstack#5786