Re: Introduction

[Nicolas Vazquez]

Welcome Jamie!

Regards,
Nicolas Vazquez


From: Nux 
Date: Thursday, 12 May 2022 at 12:10
To: dev@cloudstack.apache.org 
Cc: Jamie Pell 
Subject: Re: Introduction
Welcome, Jamie!

---
Nux!
www.nux.ro

On 2022-05-12 15:23, Jamie Pell wrote:
> Hi all,
>
> I've recently started working with Ivet and helping her out with some
> of the community marketing for the CloudStack community - so just
> wanted to say hi to everybody.
>
> Ivet has recently gone on maternity leave so I'm going to be
> interacting on the mailing lists regularly now. I'm very much looking
> forward to getting to know some of the great members of the community
> and am open to any guidance anybody may have for me. I'm going to be
> picking up organising of CCC this year amongst other tasks.
>
> Kind regards,

 

Re: Introduction

[Nux]

Welcome, Jamie!

---
Nux!
www.nux.ro

On 2022-05-12 15:23, Jamie Pell wrote:

Hi all,

I've recently started working with Ivet and helping her out with some
of the community marketing for the CloudStack community - so just
wanted to say hi to everybody.

Ivet has recently gone on maternity leave so I'm going to be
interacting on the mailing lists regularly now. I'm very much looking
forward to getting to know some of the great members of the community
and am open to any guidance anybody may have for me. I'm going to be
picking up organising of CCC this year amongst other tasks.

Kind regards,

Re: Introduction

[Sven Vogel]

Hi Jamie,

welcome to the community.


Cheers,

Sven Vogel
Apache CloudStack PMC member



Am Donnerstag, den 05/12/2022 um 16:23 schrieb Jamie Pell:



Hi all,

I've recently started working with Ivet and helping her out with some
of the community marketing for the CloudStack community - so just
wanted to say hi to everybody.

Ivet has recently gone on maternity leave so I'm going to be
interacting on the mailing lists regularly now. I'm very much looking
forward to getting to know some of the great members of the community
and am open to any guidance anybody may have for me. I'm going to be
picking up organising of CCC this year amongst other tasks.

Kind regards,

Re: Introduction

[Ian Rae]



On Thu, May 12, 2022 at 10:35 AM Daman Arora  wrote:

> That's great to hear. Welcome Jamie!
>
>
>
>
>
> On Thu., May 12, 2022, 10:24 a.m. Jamie Pell, 
> wrote:
>
> > Hi all,
> >
> > I've recently started working with Ivet and helping her out with some of
> > the community marketing for the CloudStack community - so just wanted to
> > say hi to everybody.
> >
> > Ivet has recently gone on maternity leave so I'm going to be interacting
> > on the mailing lists regularly now. I'm very much looking forward to
> > getting to know some of the great members of the community and am open to
> > any guidance anybody may have for me. I'm going to be picking up
> organising
> > of CCC this year amongst other tasks.
> >
> > Kind regards,
> >
> >
> >
> >
>

Re: Introduction

[Daman Arora]

That's great to hear. Welcome Jamie!





On Thu., May 12, 2022, 10:24 a.m. Jamie Pell, 
wrote:

> Hi all,
>
> I've recently started working with Ivet and helping her out with some of
> the community marketing for the CloudStack community - so just wanted to
> say hi to everybody.
>
> Ivet has recently gone on maternity leave so I'm going to be interacting
> on the mailing lists regularly now. I'm very much looking forward to
> getting to know some of the great members of the community and am open to
> any guidance anybody may have for me. I'm going to be picking up organising
> of CCC this year amongst other tasks.
>
> Kind regards,
>
>
>
>

RE: Introduction

[Giles Sirett]

Welcome Jamie !!

Kind Regards
Giles

 


-Original Message-
From: Will Stevens  
Sent: 12 May 2022 15:33
To: dev@cloudstack.apache.org
Subject: Re: Introduction

Great to have you supporting.  Welcome Jamie...

Cheers,

*Will Stevens*
Chief Technology Officer
t 514.447.3456 x1301




On Thu, May 12, 2022 at 10:23 AM Jamie Pell 
wrote:

> Hi all,
>
> I've recently started working with Ivet and helping her out with some 
> of the community marketing for the CloudStack community - so just 
> wanted to say hi to everybody.
>
> Ivet has recently gone on maternity leave so I'm going to be 
> interacting on the mailing lists regularly now. I'm very much looking 
> forward to getting to know some of the great members of the community 
> and am open to any guidance anybody may have for me. I'm going to be 
> picking up organising of CCC this year amongst other tasks.
>
> Kind regards,
>
>
>
>

Re: Introduction

[Will Stevens]

Great to have you supporting.  Welcome Jamie...

Cheers,

*Will Stevens*
Chief Technology Officer
t 514.447.3456 x1301




On Thu, May 12, 2022 at 10:23 AM Jamie Pell 
wrote:

> Hi all,
>
> I've recently started working with Ivet and helping her out with some of
> the community marketing for the CloudStack community - so just wanted to
> say hi to everybody.
>
> Ivet has recently gone on maternity leave so I'm going to be interacting
> on the mailing lists regularly now. I'm very much looking forward to
> getting to know some of the great members of the community and am open to
> any guidance anybody may have for me. I'm going to be picking up organising
> of CCC this year amongst other tasks.
>
> Kind regards,
>
>
>
>

Introduction

[Jamie Pell]

Hi all,

I've recently started working with Ivet and helping her out with some of the 
community marketing for the CloudStack community - so just wanted to say hi to 
everybody.

Ivet has recently gone on maternity leave so I'm going to be interacting on the 
mailing lists regularly now. I'm very much looking forward to getting to know 
some of the great members of the community and am open to any guidance anybody 
may have for me. I'm going to be picking up organising of CCC this year amongst 
other tasks.

Kind regards,

 

RE: IPV6 in Isolated/VPC networks

[Alex Mattioli]

> ipv6 route fd23:313a:2f53:3cbf::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4

That's correct

> Or a larger subnet:
> ipv6 route fd23:313a:2f53:3c00::/56 fd23:313a:2f53:3000:1c00:baff:fe00:4

Not really, the subnets for isolated/VPC networks are always /64.  Which means 
also no real need to include subnets as well.

Cheers
Alex


 


-Original Message-
From: Wido den Hollander  
Sent: 12 May 2022 16:04
To: Abhishek Kumar ; dev@cloudstack.apache.org
Subject: Re: IPV6 in Isolated/VPC networks



On 5/12/22 09:55, Abhishek Kumar wrote:
> Hi Wido,
> 
> I do not understand what you mean by WAB address but

WAB was a type. I meant WAN.

> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the public IP of the network
> (IPv6 of the public NIC of the network VR) in the sample.
> Yes, route for fd23:313a:2f53:3cbf::/64 need to be added to this IP.
> fd23:313a:2f53:3cbf::/64 is guest IPv6 CIDR of the network here.
> 

So that means that I would need to run this command on my upstream router:

ipv6 route fd23:313a:2f53:3cbf::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4

Or a larger subnet:

ipv6 route fd23:313a:2f53:3c00::/56 fd23:313a:2f53:3000:1c00:baff:fe00:4

> Currently, the message on event bus does not include subnet. Should 
> that be included?

Yes, because then you can pickup those messages and inject the route via ExaBGP 
into a routing table right away.

> In case of VPCs, there could be multiple tiers which will need 
> multiple routes to be added. Will that be an issue if we include 
> current network/tier subnet in the event message?

No, as long as it points to the same VR you simply have multiple subnets being 
routed to the same VR.

I do wonder what happens if you destroy the VR and create a new one. The WAN 
address then changes (due to SLAAC) and thus the routes need to be 
re-programmed.

Wido

> 
> Regards,
> Abhishek
> 
> 
>   
> 
>   
> 
> --
> --
> *From:* Wido den Hollander 
> *Sent:* 10 May 2022 19:01
> *To:* dev@cloudstack.apache.org ; Abhishek 
> Kumar 
> *Subject:* Re: IPV6 in Isolated/VPC networks
>  
> Hi,
> 
> Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
>> Yes. When a public IPv6 is assigned or released, CloudStack will publish 
>> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
>> These event notifications can be tracked. And with improvements in events 
>> framework, these event messages will have network uuid as entityuuid and 
>> Network as entitytype. Using this network can be queried using to list IPv6 
>> routes that need to be added.
>> 
>> Sample event message,
>> 
>> {"eventDateTime":"2022-05-10 09:32:12 
>> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":
>> "14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned public 
>> IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID: 
>> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":
>> "bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-
>> af19-1e00320001f3","entity":"Network","status":"Completed"}
>> 
>> 
>> ?Sample API call,
>>> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98 
>>> filter=id,name,ip6routes
>> {
>>    "count": 1,
>>    "network": [
>>  {
>>    "id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
>>    "ip6routes": [
>>  {
>>    "gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
>>    "subnet": "fd23:313a:2f53:3cbf::/64"
>>  }
> 
> Looking at this JSON, does this mean that
> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?
> 
> And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 
> to that IP?
> 
> The event message does not include the subnet, that makes it a bit 
> more difficult as you would then also need to do a API-call to gather 
> that information.
> 
> Wido
> 
> P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an 
> -record for IPv6!
> 
>>    ],
>>    "name": "routing_test"
>>  }
>>    ]
>> }
>> 
>> 
>> 
>> 
>> 
>> From: Wido den Hollander 
>> Sent: 10 May 2022 13:59
>> To: dev@cloudstack.apache.org ; Abhishek 
>> Kumar 
>> Subject: Re: IPV6 in Isolated/VPC networks
>> 
>> Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
>>> Hi all,
>>>
>>> IPv6 Support in Isolated Network and VPC with Static Routing based on the 
>>> design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
>>> while testing 4.17.0 RC2 you will also try to test it ?
>>> Documentation for it is available at 
>>> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.htm
>>> l#isolated-network-and-vpc-tier
>  #isolated-network-and-vpc-tier> (will be available in the official 
> docs once 4.17.0 version of docs is built).
>>>
>> 
>> Great work!
>> 
>> I see only static routing is supported. But do we publish something 
>> on the message bus once a new VR/VPC is 

Re: IPV6 in Isolated/VPC networks

[Wido den Hollander]

On 5/12/22 09:55, Abhishek Kumar wrote:
> Hi Wido,
> 
> I do not understand what you mean by WAB address but

WAB was a type. I meant WAN.

> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the public IP of the network
> (IPv6 of the public NIC of the network VR) in the sample.
> Yes, route for fd23:313a:2f53:3cbf::/64 need to be added to this IP.
> fd23:313a:2f53:3cbf::/64 is guest IPv6 CIDR of the network here.
> 

So that means that I would need to run this command on my upstream router:

ipv6 route fd23:313a:2f53:3cbf::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4

Or a larger subnet:

ipv6 route fd23:313a:2f53:3c00::/56 fd23:313a:2f53:3000:1c00:baff:fe00:4

> Currently, the message on event bus does not include subnet. Should that
> be included?

Yes, because then you can pickup those messages and inject the route via
ExaBGP into a routing table right away.

> In case of VPCs, there could be multiple tiers which will need multiple
> routes to be added. Will that be an issue if we include current
> network/tier subnet in the event message?

No, as long as it points to the same VR you simply have multiple subnets
being routed to the same VR.

I do wonder what happens if you destroy the VR and create a new one. The
WAN address then changes (due to SLAAC) and thus the routes need to be
re-programmed.

Wido

> 
> Regards,
> Abhishek
> 
> 
>   
> 
>   
> 
> 
> *From:* Wido den Hollander 
> *Sent:* 10 May 2022 19:01
> *To:* dev@cloudstack.apache.org ; Abhishek
> Kumar 
> *Subject:* Re: IPV6 in Isolated/VPC networks
>  
> Hi,
> 
> Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
>> Yes. When a public IPv6 is assigned or released, CloudStack will publish 
>> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
>> These event notifications can be tracked. And with improvements in events 
>> framework, these event messages will have network uuid as entityuuid and 
>> Network as entitytype. Using this network can be queried using to list IPv6 
>> routes that need to be added.
>> 
>> Sample event message,
>> 
>> {"eventDateTime":"2022-05-10 09:32:12 
>> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
>>  public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID: 
>> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}
>> 
>> 
>> ?Sample API call,
>>> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98 
>>> filter=id,name,ip6routes
>> {
>>    "count": 1,
>>    "network": [
>>  {
>>    "id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
>>    "ip6routes": [
>>  {
>>    "gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
>>    "subnet": "fd23:313a:2f53:3cbf::/64"
>>  }
> 
> Looking at this JSON, does this mean that
> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?
> 
> And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 to
> that IP?
> 
> The event message does not include the subnet, that makes it a bit more
> difficult as you would then also need to do a API-call to gather that
> information.
> 
> Wido
> 
> P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an
> -record for IPv6!
> 
>>    ],
>>    "name": "routing_test"
>>  }
>>    ]
>> }
>> 
>> 
>> 
>> 
>> 
>> From: Wido den Hollander 
>> Sent: 10 May 2022 13:59
>> To: dev@cloudstack.apache.org ; Abhishek Kumar 
>> 
>> Subject: Re: IPV6 in Isolated/VPC networks
>> 
>> Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
>>> Hi all,
>>>
>>> IPv6 Support in Isolated Network and VPC with Static Routing based on the 
>>> design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
>>> while testing 4.17.0 RC2 you will also try to test it ?
>>> Documentation for it is available at 
>>> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
> 
> (will be available in the official docs once 4.17.0 version of docs is
> built).
>>>
>> 
>> Great work!
>> 
>> I see only static routing is supported. But do we publish something on
>> the message bus once a new VR/VPC is created?
>> 
>> This way you could pick up these messages and have the network create a
>> (static) route based on those.
>> 
>> ExaBGP for example could be used to inject such routes.
>> 
>> Wido
>> 
>>> [1] 
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
> 
>>>
>>> Regards,
>>> Abhishek
>>>
>>> 
>>> From: Rohit Yadav 

Re: IPV6 in Isolated/VPC networks

[Wei ZHOU]

Hi Wido,

In Abhishek's example, `fd23:313a:2f53:3000:1c00:baff:fe00:4` (gateway) is
used for communication between CloudStack VR and the upstream router.
In current implementation, it uses the same VLAN as the public IPv4 address
of the network, it is associated with the public NIC in CloudStack VR.
it can be a public or private IPv6 address. the upstream router should have
an Ipv6 in the network (e.g. upstream router has IP
fd23:313a:2f53:3000::1/64)

the guest vms are reachable when a static route is added in upstream
router, similar as `ip -6 route add  via "

-Wei

On Tue, 10 May 2022 at 15:31, Wido den Hollander  wrote:

> Hi,
>
> Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
> > Yes. When a public IPv6 is assigned or released, CloudStack will publish
> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
> > These event notifications can be tracked. And with improvements in
> events framework, these event messages will have network uuid as entityuuid
> and Network as entitytype. Using this network can be queried using to list
> IPv6 routes that need to be added.
> >
> > Sample event message,
> >
> > {"eventDateTime":"2022-05-10 09:32:12
> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
> public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID:
> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}
> >
> >
> > ?Sample API call,
> >> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98
> filter=id,name,ip6routes
> > {
> >"count": 1,
> >"network": [
> >  {
> >"id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
> >"ip6routes": [
> >  {
> >"gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
> >"subnet": "fd23:313a:2f53:3cbf::/64"
> >  }
>
> Looking at this JSON, does this mean that
> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?
>
> And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 to
> that IP?
>
> The event message does not include the subnet, that makes it a bit more
> difficult as you would then also need to do a API-call to gather that
> information.
>
> Wido
>
> P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an
> -record for IPv6!
>
> >],
> >"name": "routing_test"
> >  }
> >]
> > }
> >
> >
> >
> >
> > 
> > From: Wido den Hollander 
> > Sent: 10 May 2022 13:59
> > To: dev@cloudstack.apache.org ; Abhishek
> Kumar 
> > Subject: Re: IPV6 in Isolated/VPC networks
> >
> > Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
> >> Hi all,
> >>
> >> IPv6 Support in Isolated Network and VPC with Static Routing based on
> the design doc [1] has been implemented and is available in 4.17.0 RC2. I
> hope while testing 4.17.0 RC2 you will also try to test it ?
> >> Documentation for it is available at
> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
> (will be available in the official docs once 4.17.0 version of docs is
> built).
> >>
> >
> > Great work!
> >
> > I see only static routing is supported. But do we publish something on
> > the message bus once a new VR/VPC is created?
> >
> > This way you could pick up these messages and have the network create a
> > (static) route based on those.
> >
> > ExaBGP for example could be used to inject such routes.
> >
> > Wido
> >
> >> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
> >>
> >> Regards,
> >> Abhishek
> >>
> >> 
> >> From: Rohit Yadav 
> >> Sent: 13 September 2021 14:30
> >> To: dev@cloudstack.apache.org 
> >> Subject: Re: IPV6 in Isolated/VPC networks
> >>
> >> Thanks Alex, Wei. I've updated the docs here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
> >>
> >> I'll leave the thread open for futher discussion/ideas/feedback. I
> think we've completed the phase1 design doc including all feedback comments
> for adding IPv6 support in CloudStack and some initial poc/work can be
> started. My colleagues and I will keep everyone posted on this thread
> and/or on a Github PR as and when we're able to start our work on the same
> (after 4.16, potentially towards 4.17).
> >>
> >>
> >> Regards.
> >>
> >> 
> >> From: Wei ZHOU 
> >> Sent: Friday, September 10, 2021 20:22
> >> To: dev@cloudstack.apache.org 
> >> Subject: Re: IPV6 in Isolated/VPC networks
> >>
> >> Agree with Alex.
> >> We only need to know how many /64 are allocated. We do not care how many
> >> ipv6 addresses are used by VMs.
> >>
> >> -Wei
> >>
> >> On Fri, 10 Sept 2021 at 16:36, Alex Mattioli <
> alex.matti...@shapeblue.com>
> >> wrote:

Re: IPV6 in Isolated/VPC networks

[Wei ZHOU]

Hi Ahbishek,

Yes, the message should include the subnet.

The message should be sent when the IPv6 subnets are allocated or released,
right ? If so, there will not be multiple subnets/routes in the message.

-Wei

On Thu, 12 May 2022 at 09:56, Abhishek Kumar 
wrote:

> Hi Wido,
>
> I do not understand what you mean by WAB address but
> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the public IP of the network (IPv6
> of the public NIC of the network VR) in the sample.
> Yes, route for fd23:313a:2f53:3cbf::/64 need to be added to this IP.
> fd23:313a:2f53:3cbf::/64 is guest IPv6 CIDR of the network here.
>
> Currently, the message on event bus does not include subnet. Should that
> be included?
> In case of VPCs, there could be multiple tiers which will need multiple
> routes to be added. Will that be an issue if we include current
> network/tier subnet in the event message?
>
> Regards,
> Abhishek
> 
> From: Wido den Hollander 
> Sent: 10 May 2022 19:01
> To: dev@cloudstack.apache.org ; Abhishek Kumar
> 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Hi,
>
> Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
> > Yes. When a public IPv6 is assigned or released, CloudStack will publish
> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
> > These event notifications can be tracked. And with improvements in
> events framework, these event messages will have network uuid as entityuuid
> and Network as entitytype. Using this network can be queried using to list
> IPv6 routes that need to be added.
> >
> > Sample event message,
> >
> > {"eventDateTime":"2022-05-10 09:32:12
> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
> public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID:
> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}
> >
> >
> > ?Sample API call,
> >> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98
> filter=id,name,ip6routes
> > {
> >"count": 1,
> >"network": [
> >  {
> >"id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
> >"ip6routes": [
> >  {
> >"gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
> >"subnet": "fd23:313a:2f53:3cbf::/64"
> >  }
>
> Looking at this JSON, does this mean that
> fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?
>
> And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 to
> that IP?
>
> The event message does not include the subnet, that makes it a bit more
> difficult as you would then also need to do a API-call to gather that
> information.
>
> Wido
>
> P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an
> -record for IPv6!
>
> >],
> >"name": "routing_test"
> >  }
> >]
> > }
> >
> >
> >
> >
> > 
> > From: Wido den Hollander 
> > Sent: 10 May 2022 13:59
> > To: dev@cloudstack.apache.org ; Abhishek
> Kumar 
> > Subject: Re: IPV6 in Isolated/VPC networks
> >
> > Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
> >> Hi all,
> >>
> >> IPv6 Support in Isolated Network and VPC with Static Routing based on
> the design doc [1] has been implemented and is available in 4.17.0 RC2. I
> hope while testing 4.17.0 RC2 you will also try to test it ?
> >> Documentation for it is available at
> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
> (will be available in the official docs once 4.17.0 version of docs is
> built).
> >>
> >
> > Great work!
> >
> > I see only static routing is supported. But do we publish something on
> > the message bus once a new VR/VPC is created?
> >
> > This way you could pick up these messages and have the network create a
> > (static) route based on those.
> >
> > ExaBGP for example could be used to inject such routes.
> >
> > Wido
> >
> >> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
> >>
> >> Regards,
> >> Abhishek
> >>
> >> 
> >> From: Rohit Yadav 
> >> Sent: 13 September 2021 14:30
> >> To: dev@cloudstack.apache.org 
> >> Subject: Re: IPV6 in Isolated/VPC networks
> >>
> >> Thanks Alex, Wei. I've updated the docs here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
> >>
> >> I'll leave the thread open for futher discussion/ideas/feedback. I
> think we've completed the phase1 design doc including all feedback comments
> for adding IPv6 support in CloudStack and some initial poc/work can be
> started. My colleagues and I will keep everyone posted on this thread
> and/or on a Github PR as and when we're able to start our work on the same
> (after 4.16, potentially towards 4.17).
> >>
> >>
> 

Re: IPV6 in Isolated/VPC networks

[Abhishek Kumar]

Hi Wido,

I do not understand what you mean by WAB address but 
fd23:313a:2f53:3000:1c00:baff:fe00:4 is the public IP of the network (IPv6 of 
the public NIC of the network VR) in the sample.
Yes, route for fd23:313a:2f53:3cbf::/64 need to be added to this IP. 
fd23:313a:2f53:3cbf::/64 is guest IPv6 CIDR of the network here.

Currently, the message on event bus does not include subnet. Should that be 
included?
In case of VPCs, there could be multiple tiers which will need multiple routes 
to be added. Will that be an issue if we include current network/tier subnet in 
the event message?

Regards,
Abhishek

From: Wido den Hollander 
Sent: 10 May 2022 19:01
To: dev@cloudstack.apache.org ; Abhishek Kumar 

Subject: Re: IPV6 in Isolated/VPC networks

Hi,

Op 10-05-2022 om 11:42 schreef Abhishek Kumar:
> Yes. When a public IPv6 is assigned or released, CloudStack will publish 
> event with type NET.IP6ASSIGN, NET.IP6RELEASE.
> These event notifications can be tracked. And with improvements in events 
> framework, these event messages will have network uuid as entityuuid and 
> Network as entitytype. Using this network can be queried using to list IPv6 
> routes that need to be added.
>
> Sample event message,
>
> {"eventDateTime":"2022-05-10 09:32:12 
> +","entityuuid":"14658b39-9d20-4783-a1bc-12fb58bcbd98","Network":"14658b39-9d20-4783-a1bc-12fb58bcbd98","description":"Assigned
>  public IPv6 address: fd23:313a:2f53:3000:1c00:baff:fe00:4 for network ID: 
> 14658b39-9d20-4783-a1bc-12fb58bcbd98","event":"NET.IP6ASSIGN","user":"bde866ba-c600-11ec-af19-1e00320001f3","account":"bde712c9-c600-11ec-af19-1e00320001f3","entity":"Network","status":"Completed"}
>
>
> ?Sample API call,
>> list networks id=14658b39-9d20-4783-a1bc-12fb58bcbd98 
>> filter=id,name,ip6routes
> {
>"count": 1,
>"network": [
>  {
>"id": "14658b39-9d20-4783-a1bc-12fb58bcbd98",
>"ip6routes": [
>  {
>"gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4",
>"subnet": "fd23:313a:2f53:3cbf::/64"
>  }

Looking at this JSON, does this mean that
fd23:313a:2f53:3000:1c00:baff:fe00:4 is the WAB address of the VR?

And that I would need to (statically) route fd23:313a:2f53:3cbf::/64 to
that IP?

The event message does not include the subnet, that makes it a bit more
difficult as you would then also need to do a API-call to gather that
information.

Wido

P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an
-record for IPv6!

>],
>"name": "routing_test"
>  }
>]
> }
>
>
>
>
> 
> From: Wido den Hollander 
> Sent: 10 May 2022 13:59
> To: dev@cloudstack.apache.org ; Abhishek Kumar 
> 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Op 10-05-2022 om 10:19 schreef Abhishek Kumar:
>> Hi all,
>>
>> IPv6 Support in Isolated Network and VPC with Static Routing based on the 
>> design doc [1] has been implemented and is available in 4.17.0 RC2. I hope 
>> while testing 4.17.0 RC2 you will also try to test it ?
>> Documentation for it is available at 
>> http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/262/plugins/ipv6.html#isolated-network-and-vpc-tier
>>  (will be available in the official docs once 4.17.0 version of docs is 
>> built).
>>
>
> Great work!
>
> I see only static routing is supported. But do we publish something on
> the message bus once a new VR/VPC is created?
>
> This way you could pick up these messages and have the network create a
> (static) route based on those.
>
> ExaBGP for example could be used to inject such routes.
>
> Wido
>
>> [1] 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>>
>> Regards,
>> Abhishek
>>
>> 
>> From: Rohit Yadav 
>> Sent: 13 September 2021 14:30
>> To: dev@cloudstack.apache.org 
>> Subject: Re: IPV6 in Isolated/VPC networks
>>
>> Thanks Alex, Wei. I've updated the docs here: 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Routing
>>
>> I'll leave the thread open for futher discussion/ideas/feedback. I think 
>> we've completed the phase1 design doc including all feedback comments for 
>> adding IPv6 support in CloudStack and some initial poc/work can be started. 
>> My colleagues and I will keep everyone posted on this thread and/or on a 
>> Github PR as and when we're able to start our work on the same (after 4.16, 
>> potentially towards 4.17).
>>
>>
>> Regards.
>>
>> 
>> From: Wei ZHOU 
>> Sent: Friday, September 10, 2021 20:22
>> To: dev@cloudstack.apache.org 
>> Subject: Re: IPV6 in Isolated/VPC networks
>>
>> Agree with Alex.
>> We only need to know how many /64 are allocated. We do not care how many
>> ipv6 addresses are used by VMs.
>>
>> -Wei
>>
>> On Fri, 10 Sept 2021 at 16:36, Alex Mattioli 
>> wrote:
>>
>>> Hi Rohit,
>>>
>>> I'd go for option 2,