Yes but this is not ideal as as a cloud provider we have literally hundreds of 
subnets so creating hundreds of networks for a single subnet is not 
ideal....maybe for a home user yes but we will be using cloudstack in a 
production evironment with thousands of instances.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, April 16, 2021 6:40 PM, Hean Seng <heans...@gmail.com> wrote:

> I think you just proceed on one Network one subnet and it work perfectly
>
> On Fri, Apr 16, 2021 at 4:32 PM anonymousjones666 
> <anonymousjones...@protonmail.com.invalid> wrote:
>
>> Seems I have made some headway.
>>
>> I added the second subnet to the defaultnetwork via thelagacy interface. 
>> While using Primate I cannot assign an IP from the new subnet....only the 
>> original subnet but with the legacy interface I can manaully enter the IP 
>> when deploying and the IP gets assigned.
>>
>> However, there is no routing to the virtual router for cloudinit.See 
>> screenshot.
>> https://ibb.co/6BrV6MV
>>
>> Sent with ProtonMail Secure Email.
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Thursday, April 15, 2021 2:23 PM, anonymousjones666 
>> <anonymousjones...@protonmail.com.INVALID> wrote:
>>
>>> Hi Alex.
>>>
>>> Please see the images using these links.
>>>
>>> The first image has the subnet at the top that was added when the inital 
>>> network was added. The second of the subnet added via the legacy interface 
>>> after the network was setup.
>>>
>>> The second image is where you can see we can only the inital subnet can be 
>>> used. I tried to enter an IP of the second subnet but as you can see it 
>>> says we should use an IP from the subnet the was intially added.
>>>
>>> https://ibb.co/N997chT
>>> https://ibb.co/VxfwD8c
>>>
>>> Sent with ProtonMail Secure Email.
>>>
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Thursday, April 15, 2021 2:10 PM, Alex Mattioli 
>>> alex.matti...@shapeblue.com wrote:
>>>
>>> > Hi,
>>> > Unfortunately I can't see the attachments. Would be good if you could 
>>> > upload it somewhere and send the link :)
>>> > Cheers,
>>> > Alex
>>> > alex.matti...@shapeblue.com
>>> > www.shapeblue.com
>>> > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> > @shapeblue
>>> > -----Original Message-----
>>> > From: anonymousjones666 anonymousjones...@protonmail.com.INVALID
>>> > Sent: 15 April 2021 12:59
>>> > To: users@cloudstack.apache.org
>>> > Subject: RE: Multiple Guest Subnets Default Network
>>> > Yes you are right. We are using the legacy interface to add but when 
>>> > trying to use the subnet we can only use the subnet that was added during 
>>> > the network setup. See screenshot.
>>> > Sent with ProtonMail Secure Email.
>>> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> > On Thursday, April 15, 2021 11:58 AM, anonymousjones666 
>>> > anonymousjones...@protonmail.com.INVALID wrote:
>>> >
>>> > > Hi Alex.
>>> > > To clarify:-
>>> > > Right now we have a single /28 assigned to the DefaultGuestNetwork 
>>> > > which we can assign to instances.
>>> > > What we want is to add another public subnet ( different to our initial 
>>> > > /28 ) and also use this subnet in the DefaultGuestNetwork so we have 
>>> > > multiple IP subnets to assign to any instance deployed using this 
>>> > > network.
>>> > > To answer your question - we dont want to assign 2 IPs to instances 
>>> > > rather assign a single IP to any instance from multiple public subnets. 
>>> > > From what I see now we can only use the subnet ( /28 ) that was 
>>> > > initially added when setting up the guestnetwork.
>>> > > I have attached a screenshot of what we did but the second IP range
>>> > > cannot be used when deploying an instance
>>> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> > > On Thursday, April 15, 2021 11:58 AM, anonymousjones666 
>>> > > anonymousjones...@protonmail.com wrote:
>>> > >
>>> > > > Hi Alex.
>>> > > > To clarify:-
>>> > > > Right now we have a single /28 assigned to the DefaultGuestNetwork 
>>> > > > which we can assign to instances.
>>> > > > What we want is to add another public subnet ( different to our 
>>> > > > initial /28 ) and also use this subnet in the DefaultGuestNetwork so 
>>> > > > we have multiple IP subnets to assign to any instance deployed using 
>>> > > > this network.
>>> > > > To answer your question - we dont want to assign 2 IPs to instances 
>>> > > > rather assign a single IP to any instance from multiple public 
>>> > > > subnets. From what I see now we can only use the subnet ( /28 ) that 
>>> > > > was initially added when setting up the guestnetwork.
>>> > > > I have attached a screenshot of what we did but the second IP range
>>> > > > cannot be used when deploying an instance Sent with ProtonMail Secure 
>>> > > > Email.
>>> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> > > > On Thursday, April 15, 2021 11:09 AM, Alex Mattioli 
>>> > > > alex.matti...@shapeblue.com wrote:
>>> > > >
>>> > > > > Hi Mr 666.
>>> > > > > Let me see if I got it right. You have two /28s with Public IPs and 
>>> > > > > want your VM to have one IP from each?
>>> > > > > Cheers
>>> > > > > Alex
>>> > > > > alex.matti...@shapeblue.com
>>> > > > > www.shapeblue.com
>>> > > > > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK
>>> > > > > @shapeblue -----Original Message-----
>>> > > > > From: anonymousjones666 anonymousjones...@protonmail.com.INVALID
>>> > > > > Sent: 15 April 2021 12:00
>>> > > > > To: users@cloudstack.apache.org
>>> > > > > Subject: Multiple Guest Subnets Default Network Hello Is it
>>> > > > > possible to add multiple guest subnets to one guest network with CS 
>>> > > > > 4.15 ?
>>> > > > > As an example we have a /28 subnet ( public ) and can deploy 
>>> > > > > instances from this however, we can add another subnet to the 
>>> > > > > defaultGuestNetwork ( using the legacy dashbaord ) but when 
>>> > > > > deploying an instance we can only add an IP address from the 
>>> > > > > initial /28 subnet and not the other we added.
>>> > > > > Are there any options to add multiple public subnets to one single 
>>> > > > > guest network ?
>>> > > > > Thank You
>
> --
> Regards,
> Hean Seng

Reply via email to