RE: Size of the snapshots volume

[Yordan Kostov]

You are correct.
Snapshots remain visible in the GUI and can be removed.

Thanks, that explains it.

Best Regards,
Jordan 

-Original Message-
From: Slavka Peleva  
Sent: Thursday, October 21, 2021 3:42 PM
To: users@cloudstack.apache.org
Subject: Re: Size of the snapshots volume


[X] This message came from outside your organization


Unfortunately, I'm not familiar with XCP-NG. I rechecked your steps, and there 
isn't a call to delete a volume snapshot. I think that destroying a VM works 
almost the same for all hypervisors, and the volume snapshots won't be deleted 
automatically. Can you check if they are visible in the UI?

On Thu, Oct 21, 2021 at 3:03 PM Yordan Kostov  wrote:

> Hey Slavka,
>
> Deployment is 4.15.2 + XCP-NG 8.2 utilizing fiber channel SAN 
> as primary storage.
>
> Regards,
> Jordan
>
> -Original Message-
> From: Slavka Peleva 
> Sent: Thursday, October 21, 2021 2:54 PM
> To: users@cloudstack.apache.org
> Subject: Re: Size of the snapshots volume
>
>
> [X] This message came from outside your organization
>
>
> Hi Yordan,
>
> can you share what are you using for primary storage? In some cases, 
> the deletion of snapshots on secondary isn't implemented. According to 
> the code, the cleanup of the snapshots is only for the DB, not for 
> cleaning the secondary storage.
>
> Best regards,
> Slavka
>
> On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar  .invalid>
> wrote:
>
> > Hello,
> >
> > You can check the the snapshot status in - snapshots table in DB. 
> > You can also verify the status in  table called - 
> > snapshot_store_ref. Yes cloudStack runs a cleanup job, timings 
> > depends what you have defined in global setting  -
> >
> > storage.cleanup.delay   Determines how long (in seconds) to wait before
> > actually expunging destroyed volumes. The default value = the 
> > default
> value
> > of storage.cleanup.interval.Advanced
> > 86400
> >
> > storage.cleanup.enabled Enables/disables the storage cleanup thread.
> > Advanced
> > true
> >
> > storage.cleanup.intervalThe interval (in seconds) to wait before
> > running the storage cleanup thread.Advanced
> > 86400
> >
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > IndiQus Technologies
> > M +91 7503460090
> > https://urldefense.com/v3/__http://www.indiqus.com__;!!A6UyJA!3CYjCk
> > -6 
> > l_RJxlZSVAgmTqt2LJFeWODa5bdiKclS7xGT1weD16tUBUGwVHeDrYKQpLoahZ_meJ1V
> > $
> >
> >
> >
> >
> > > On 21-Oct-2021, at 4:38 PM, Yordan Kostov 
> wrote:
> > >
> > > Here is another thing I noticed.
> > > - have a VM with a volume snapshots
> > > - Expunge the VM so the disk is removed also
> > > - check the Secondary Storage - backup still remains.
> > >
> > > Does anyone knows if Cloudstack does a cleanup later or the 
> > > orphaned
> > backups will remain?
> > >
> > > Regards,
> > > Jordan
> > >
> > > -Original Message-
> > > From: benoit lair 
> > > Sent: Tuesday, October 19, 2021 1:22 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Re: Size of the snapshots volume
> > >
> > >
> > > [X] This message came from outside your organization
> > >
> > >
> > > Hello Yordan,
> > >
> > > I had same results with xcp-ng 8.2 and ACS 4.15.1
> > >
> > > The max filled during the life of the disk will be the size of the
> > snapshot
> > >
> > > That's why i looking towards SDS with a solution giving me 
> > > possibility
> > to do some thin provisionning with XCP-NG I was thinking about an 
> > SDS which could give me block storage or at least file storage and 
> > acting as a proxy between my iscsi array and my xcp-ng
> > >
> > > Linstor could be a solution, but for the moment i don't know if 
> > > the
> > plugin will be compatible with xcp-ng
> > >
> > > Regards, Benoit
> > >
> > > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  
> > > a
> > écrit :
> > >
> > >> Hello Benoit,
> > >>
> > >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from 
> > >> template - Centos 7, 46 GB hdd, 4% full
> > >>- VM1 - root disk is as full as template.
> > >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero 
> > >> >
> > >> test_file1 )then the file was removed so the used space is again 4%.
> > >>- scheduled backup goes through both VMs. First snapshot 
> > >> size
> is
> > >>- VM1 -  2.3G
> > >>- VM2 -  41G
> > >>- Then on VM2 this script was run to fill and empty the 
> > >> disk again
> > >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> > >>- scheduled backup goes through both VMs. All snapshots 
> > >> size
> is:
> > >>- VM1 - 2.3G
> > >>- VM2 - 88G
> > >>
> > >>Once the disk is filled you will get a snapshot with size 
> > >> no less than the size of the whole disk.
> > >>May be there is a way to shrink it but I could not find it.
> > >>
> > >> Best regards,
> > >> Jordan
> > >>
> > >> -Original Message-
> > >> From: Yordan Kostov 
> > >> 

Re: Size of the snapshots volume

[Slavka Peleva]

Unfortunately, I'm not familiar with XCP-NG. I rechecked your steps, and
there isn't a call to delete a volume snapshot. I think that destroying a
VM works almost the same for all hypervisors, and the volume snapshots
won't be deleted automatically. Can you check if they are visible in the UI?

On Thu, Oct 21, 2021 at 3:03 PM Yordan Kostov  wrote:

> Hey Slavka,
>
> Deployment is 4.15.2 + XCP-NG 8.2 utilizing fiber channel SAN as
> primary storage.
>
> Regards,
> Jordan
>
> -Original Message-
> From: Slavka Peleva 
> Sent: Thursday, October 21, 2021 2:54 PM
> To: users@cloudstack.apache.org
> Subject: Re: Size of the snapshots volume
>
>
> [X] This message came from outside your organization
>
>
> Hi Yordan,
>
> can you share what are you using for primary storage? In some cases, the
> deletion of snapshots on secondary isn't implemented. According to the
> code, the cleanup of the snapshots is only for the DB, not for cleaning the
> secondary storage.
>
> Best regards,
> Slavka
>
> On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar  .invalid>
> wrote:
>
> > Hello,
> >
> > You can check the the snapshot status in - snapshots table in DB. You
> > can also verify the status in  table called - snapshot_store_ref. Yes
> > cloudStack runs a cleanup job, timings depends what you have defined
> > in global setting  -
> >
> > storage.cleanup.delay   Determines how long (in seconds) to wait before
> > actually expunging destroyed volumes. The default value = the default
> value
> > of storage.cleanup.interval.Advanced
> > 86400
> >
> > storage.cleanup.enabled Enables/disables the storage cleanup thread.
> > Advanced
> > true
> >
> > storage.cleanup.intervalThe interval (in seconds) to wait before
> > running the storage cleanup thread.Advanced
> > 86400
> >
> >
> >
> > Vivek Kumar
> > Sr. Manager - Cloud & DevOps
> > IndiQus Technologies
> > M +91 7503460090
> > https://urldefense.com/v3/__http://www.indiqus.com__;!!A6UyJA!3CYjCk-6
> > l_RJxlZSVAgmTqt2LJFeWODa5bdiKclS7xGT1weD16tUBUGwVHeDrYKQpLoahZ_meJ1V$
> >
> >
> >
> >
> > > On 21-Oct-2021, at 4:38 PM, Yordan Kostov 
> wrote:
> > >
> > > Here is another thing I noticed.
> > > - have a VM with a volume snapshots
> > > - Expunge the VM so the disk is removed also
> > > - check the Secondary Storage - backup still remains.
> > >
> > > Does anyone knows if Cloudstack does a cleanup later or the orphaned
> > backups will remain?
> > >
> > > Regards,
> > > Jordan
> > >
> > > -Original Message-
> > > From: benoit lair 
> > > Sent: Tuesday, October 19, 2021 1:22 PM
> > > To: users@cloudstack.apache.org
> > > Subject: Re: Size of the snapshots volume
> > >
> > >
> > > [X] This message came from outside your organization
> > >
> > >
> > > Hello Yordan,
> > >
> > > I had same results with xcp-ng 8.2 and ACS 4.15.1
> > >
> > > The max filled during the life of the disk will be the size of the
> > snapshot
> > >
> > > That's why i looking towards SDS with a solution giving me
> > > possibility
> > to do some thin provisionning with XCP-NG I was thinking about an SDS
> > which could give me block storage or at least file storage and acting
> > as a proxy between my iscsi array and my xcp-ng
> > >
> > > Linstor could be a solution, but for the moment i don't know if the
> > plugin will be compatible with xcp-ng
> > >
> > > Regards, Benoit
> > >
> > > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a
> > écrit :
> > >
> > >> Hello Benoit,
> > >>
> > >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from
> > >> template - Centos 7, 46 GB hdd, 4% full
> > >>- VM1 - root disk is as full as template.
> > >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> > >> test_file1 )then the file was removed so the used space is again 4%.
> > >>- scheduled backup goes through both VMs. First snapshot size
> is
> > >>- VM1 -  2.3G
> > >>- VM2 -  41G
> > >>- Then on VM2 this script was run to fill and empty the disk
> > >> again
> > >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> > >>- scheduled backup goes through both VMs. All snapshots size
> is:
> > >>- VM1 - 2.3G
> > >>- VM2 - 88G
> > >>
> > >>Once the disk is filled you will get a snapshot with size no
> > >> less than the size of the whole disk.
> > >>May be there is a way to shrink it but I could not find it.
> > >>
> > >> Best regards,
> > >> Jordan
> > >>
> > >> -Original Message-
> > >> From: Yordan Kostov 
> > >> Sent: Tuesday, October 12, 2021 3:58 PM
> > >> To: users@cloudstack.apache.org
> > >> Subject: RE: Size of the snapshots volume
> > >>
> > >>
> > >> [X] This message came from outside your organization
> > >>
> > >>
> > >> Hello Benoit,
> > >>
> > >>Unfortunately no.
> > >>When I do it I will make sure to drop a line here.
> > >>
> > >> Best regards,
> > >> Jordan
> > >>
> > >> -Original Message-

RE: Size of the snapshots volume

[Yordan Kostov]

Hey Slavka,

Deployment is 4.15.2 + XCP-NG 8.2 utilizing fiber channel SAN as 
primary storage.

Regards,
Jordan

-Original Message-
From: Slavka Peleva  
Sent: Thursday, October 21, 2021 2:54 PM
To: users@cloudstack.apache.org
Subject: Re: Size of the snapshots volume


[X] This message came from outside your organization


Hi Yordan,

can you share what are you using for primary storage? In some cases, the 
deletion of snapshots on secondary isn't implemented. According to the code, 
the cleanup of the snapshots is only for the DB, not for cleaning the secondary 
storage.

Best regards,
Slavka

On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar 
wrote:

> Hello,
>
> You can check the the snapshot status in - snapshots table in DB. You 
> can also verify the status in  table called - snapshot_store_ref. Yes 
> cloudStack runs a cleanup job, timings depends what you have defined 
> in global setting  -
>
> storage.cleanup.delay   Determines how long (in seconds) to wait before
> actually expunging destroyed volumes. The default value = the default value
> of storage.cleanup.interval.Advanced
> 86400
>
> storage.cleanup.enabled Enables/disables the storage cleanup thread.
> Advanced
> true
>
> storage.cleanup.intervalThe interval (in seconds) to wait before
> running the storage cleanup thread.Advanced
> 86400
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> IndiQus Technologies
> M +91 7503460090
> https://urldefense.com/v3/__http://www.indiqus.com__;!!A6UyJA!3CYjCk-6
> l_RJxlZSVAgmTqt2LJFeWODa5bdiKclS7xGT1weD16tUBUGwVHeDrYKQpLoahZ_meJ1V$
>
>
>
>
> > On 21-Oct-2021, at 4:38 PM, Yordan Kostov  wrote:
> >
> > Here is another thing I noticed.
> > - have a VM with a volume snapshots
> > - Expunge the VM so the disk is removed also
> > - check the Secondary Storage - backup still remains.
> >
> > Does anyone knows if Cloudstack does a cleanup later or the orphaned
> backups will remain?
> >
> > Regards,
> > Jordan
> >
> > -Original Message-
> > From: benoit lair 
> > Sent: Tuesday, October 19, 2021 1:22 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Size of the snapshots volume
> >
> >
> > [X] This message came from outside your organization
> >
> >
> > Hello Yordan,
> >
> > I had same results with xcp-ng 8.2 and ACS 4.15.1
> >
> > The max filled during the life of the disk will be the size of the
> snapshot
> >
> > That's why i looking towards SDS with a solution giving me 
> > possibility
> to do some thin provisionning with XCP-NG I was thinking about an SDS 
> which could give me block storage or at least file storage and acting 
> as a proxy between my iscsi array and my xcp-ng
> >
> > Linstor could be a solution, but for the moment i don't know if the
> plugin will be compatible with xcp-ng
> >
> > Regards, Benoit
> >
> > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a
> écrit :
> >
> >> Hello Benoit,
> >>
> >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from 
> >> template - Centos 7, 46 GB hdd, 4% full
> >>- VM1 - root disk is as full as template.
> >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> >> test_file1 )then the file was removed so the used space is again 4%.
> >>- scheduled backup goes through both VMs. First snapshot size is
> >>- VM1 -  2.3G
> >>- VM2 -  41G
> >>- Then on VM2 this script was run to fill and empty the disk 
> >> again
> >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> >>- scheduled backup goes through both VMs. All snapshots size is:
> >>- VM1 - 2.3G
> >>- VM2 - 88G
> >>
> >>Once the disk is filled you will get a snapshot with size no 
> >> less than the size of the whole disk.
> >>May be there is a way to shrink it but I could not find it.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: Yordan Kostov 
> >> Sent: Tuesday, October 12, 2021 3:58 PM
> >> To: users@cloudstack.apache.org
> >> Subject: RE: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Benoit,
> >>
> >>Unfortunately no.
> >>When I do it I will make sure to drop a line here.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: benoit lair 
> >> Sent: Tuesday, October 12, 2021 3:40 PM
> >> To: users@cloudstack.apache.org
> >> Subject: Re: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Jordan,
> >>
> >> Could you proceed to your tests ? Have you got the same results ?
> >>
> >> Regards, Benoit Lair
> >>
> >> Le lun. 4 oct. 2021 à 17:59, Yordan Kostov  a 
> >> écrit
> >> :
> >>
> >>> Here are a few considerations:
> >>>
> >>> - First snapshot of volume is always full snap.
> >>> - XenServer/XCP-NG backups are always thin.
> >>> - Thin provisioning calculations never go down. Even 

Re: Size of the snapshots volume

[Slavka Peleva]

Hi Yordan,

can you share what are you using for primary storage? In some cases, the
deletion of snapshots on secondary isn't implemented. According to the
code, the cleanup of the snapshots is only for the DB, not for cleaning the
secondary storage.

Best regards,
Slavka

On Thu, Oct 21, 2021 at 2:37 PM Vivek Kumar 
wrote:

> Hello,
>
> You can check the the snapshot status in - snapshots table in DB. You can
> also verify the status in  table called - snapshot_store_ref. Yes
> cloudStack runs a cleanup job, timings depends what you have defined in
> global setting  -
>
> storage.cleanup.delay   Determines how long (in seconds) to wait before
> actually expunging destroyed volumes. The default value = the default value
> of storage.cleanup.interval.Advanced
> 86400
>
> storage.cleanup.enabled Enables/disables the storage cleanup thread.
> Advanced
> true
>
> storage.cleanup.intervalThe interval (in seconds) to wait before
> running the storage cleanup thread.Advanced
> 86400
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> IndiQus Technologies
> M +91 7503460090
> www.indiqus.com
>
>
>
>
> > On 21-Oct-2021, at 4:38 PM, Yordan Kostov  wrote:
> >
> > Here is another thing I noticed.
> > - have a VM with a volume snapshots
> > - Expunge the VM so the disk is removed also
> > - check the Secondary Storage - backup still remains.
> >
> > Does anyone knows if Cloudstack does a cleanup later or the orphaned
> backups will remain?
> >
> > Regards,
> > Jordan
> >
> > -Original Message-
> > From: benoit lair 
> > Sent: Tuesday, October 19, 2021 1:22 PM
> > To: users@cloudstack.apache.org
> > Subject: Re: Size of the snapshots volume
> >
> >
> > [X] This message came from outside your organization
> >
> >
> > Hello Yordan,
> >
> > I had same results with xcp-ng 8.2 and ACS 4.15.1
> >
> > The max filled during the life of the disk will be the size of the
> snapshot
> >
> > That's why i looking towards SDS with a solution giving me possibility
> to do some thin provisionning with XCP-NG I was thinking about an SDS which
> could give me block storage or at least file storage and acting as a proxy
> between my iscsi array and my xcp-ng
> >
> > Linstor could be a solution, but for the moment i don't know if the
> plugin will be compatible with xcp-ng
> >
> > Regards, Benoit
> >
> > Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a
> écrit :
> >
> >> Hello Benoit,
> >>
> >>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from
> >> template - Centos 7, 46 GB hdd, 4% full
> >>- VM1 - root disk is as full as template.
> >>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> >> test_file1 )then the file was removed so the used space is again 4%.
> >>- scheduled backup goes through both VMs. First snapshot size is
> >>- VM1 -  2.3G
> >>- VM2 -  41G
> >>- Then on VM2 this script was run to fill and empty the disk
> >> again
> >> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> >>- scheduled backup goes through both VMs. All snapshots size is:
> >>- VM1 - 2.3G
> >>- VM2 - 88G
> >>
> >>Once the disk is filled you will get a snapshot with size no
> >> less than the size of the whole disk.
> >>May be there is a way to shrink it but I could not find it.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: Yordan Kostov 
> >> Sent: Tuesday, October 12, 2021 3:58 PM
> >> To: users@cloudstack.apache.org
> >> Subject: RE: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Benoit,
> >>
> >>Unfortunately no.
> >>When I do it I will make sure to drop a line here.
> >>
> >> Best regards,
> >> Jordan
> >>
> >> -Original Message-
> >> From: benoit lair 
> >> Sent: Tuesday, October 12, 2021 3:40 PM
> >> To: users@cloudstack.apache.org
> >> Subject: Re: Size of the snapshots volume
> >>
> >>
> >> [X] This message came from outside your organization
> >>
> >>
> >> Hello Jordan,
> >>
> >> Could you proceed to your tests ? Have you got the same results ?
> >>
> >> Regards, Benoit Lair
> >>
> >> Le lun. 4 oct. 2021 à 17:59, Yordan Kostov  a
> >> écrit
> >> :
> >>
> >>> Here are a few considerations:
> >>>
> >>> - First snapshot of volume is always full snap.
> >>> - XenServer/XCP-NG backups are always thin.
> >>> - Thin provisioning calculations never go down. Even if you delete
> >>> data from disk.
> >>>
> >>> As you filled the disk of the VM to top the thin provisioning
> >>> threats it as full VM from that moment on even if data is deleted.
> >>> So the full snap that will be migrated to NFS will always be of max
> size.
> >>>
> >>> I am not 100% certain as I am yet to start running backup tests.
> >>>
> >>> Best regards,
> >>> Jordan
> >>>
> >>> -Original Message-
> >>> From: Florian Noel 
> >>> Sent: Monday, October 4, 2021 6:22 

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Дикевич Евгений Александрович]

Thank you all very much!

I figured out this question :)

I asked another question -  Can I dedicate Physical Network (some new PN with 
for example GRE isolation method) to some 1 Pod or Cluster?


-Original Message-
From: Cristian Ciobanu [mailto:cristian.c@istream.today]
Sent: Thursday, October 21, 2021 2:34 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Understanding of Physical Network

If you want to use 2 bond networks as you described, you can have 2 or more, 
you can use the same NIC/bond for multiple "physical networks"

Example:

2XNICs - Bond1
2XNICs - Bond2

You can create 2 or more physical networks, if the traffic label you are using 
in these networks is  "bond1 or bond2" .

You can have 2 "Physical networks" with the same network label but different 
traffic type.  (Management, Guest, Public, Storage)



Regards,
Cristian


On Thu, Oct 21, 2021, 11:58 Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Can someone explain me concept of Physical Networks?
>
> Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1
> bond I have Management, Guest and Public VLANs. On other - Storage VLANs.
>
> When I deploy ZONE should I create 2 Physical Networks? Or I can
> create 3
> (1?) network for example?
>
> I want to deploy Advanced Zone (without SG)
>
> I read article from ShapeBlue (
> https://www.shapeblue.com/understanding-cloudstacks-physical-networkin
> g-architecture/)
> but it doesn't help me:)
>
> Best regards, Evgeniy.
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования
> лицом (лицами), которому (которым) оно предназначено. Если Вы не
> являетесь лицом (лицами), которому (которым) предназначено это письмо,
> не копируйте и не разглашайте его содержимое и удалите это сообщение и
> все вложения из Вашей почтовой системы. Любое несанкционированное
> использование, распространение, раскрытие, печать или копирование
> этого электронного письма и прикрепленных к нему файлов, кроме как
> лицом (лицами) которому (которым) они предназначены, является
> незаконным и запрещено. Принимая во внимание, что передача данных
> посредством Интернет не является безопасной, мы не несем никакой
> ответственности за любой потенциальный ущерб, причиненный в результате
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as
> the intended recipient (recipients). If you are not the intended
> recipient of this email, do not copy or disclose its contents and
> delete the message and any attachments to it from your e-mail system.
> Any unauthorized use, dissemination, disclosure, printing or copying
> of this e-mail and files attached to it, except by the intended
> recipient, is illegal and is prohibited. Taking into account that data
> transmission via Internet is not secure, we assume no responsibility
> for any potential damage caused by data transmission errors or this message 
> and the files attached to it.
>
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: Size of the snapshots volume

[Vivek Kumar]

Hello, 

You can check the the snapshot status in - snapshots table in DB. You can also 
verify the status in  table called - snapshot_store_ref. Yes cloudStack runs a 
cleanup job, timings depends what you have defined in global setting  - 

storage.cleanup.delay   Determines how long (in seconds) to wait before 
actually expunging destroyed volumes. The default value = the default value of 
storage.cleanup.interval.Advanced
86400

storage.cleanup.enabled Enables/disables the storage cleanup thread.
Advanced
true

storage.cleanup.intervalThe interval (in seconds) to wait before 
running the storage cleanup thread.Advanced
86400



Vivek Kumar
Sr. Manager - Cloud & DevOps 
IndiQus Technologies
M +91 7503460090 
www.indiqus.com




> On 21-Oct-2021, at 4:38 PM, Yordan Kostov  wrote:
> 
> Here is another thing I noticed.
> - have a VM with a volume snapshots
> - Expunge the VM so the disk is removed also
> - check the Secondary Storage - backup still remains.
> 
> Does anyone knows if Cloudstack does a cleanup later or the orphaned backups 
> will remain?
> 
> Regards,
> Jordan 
> 
> -Original Message-
> From: benoit lair  
> Sent: Tuesday, October 19, 2021 1:22 PM
> To: users@cloudstack.apache.org
> Subject: Re: Size of the snapshots volume
> 
> 
> [X] This message came from outside your organization
> 
> 
> Hello Yordan,
> 
> I had same results with xcp-ng 8.2 and ACS 4.15.1
> 
> The max filled during the life of the disk will be the size of the snapshot
> 
> That's why i looking towards SDS with a solution giving me possibility to do 
> some thin provisionning with XCP-NG I was thinking about an SDS which could 
> give me block storage or at least file storage and acting as a proxy between 
> my iscsi array and my xcp-ng
> 
> Linstor could be a solution, but for the moment i don't know if the plugin 
> will be compatible with xcp-ng
> 
> Regards, Benoit
> 
> Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a écrit :
> 
>> Hello Benoit,
>> 
>>Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from 
>> template - Centos 7, 46 GB hdd, 4% full
>>- VM1 - root disk is as full as template.
>>- VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
>> test_file1 )then the file was removed so the used space is again 4%.
>>- scheduled backup goes through both VMs. First snapshot size is
>>- VM1 -  2.3G
>>- VM2 -  41G
>>- Then on VM2 this script was run to fill and empty the disk 
>> again
>> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
>>- scheduled backup goes through both VMs. All snapshots size is:
>>- VM1 - 2.3G
>>- VM2 - 88G
>> 
>>Once the disk is filled you will get a snapshot with size no 
>> less than the size of the whole disk.
>>May be there is a way to shrink it but I could not find it.
>> 
>> Best regards,
>> Jordan
>> 
>> -Original Message-
>> From: Yordan Kostov 
>> Sent: Tuesday, October 12, 2021 3:58 PM
>> To: users@cloudstack.apache.org
>> Subject: RE: Size of the snapshots volume
>> 
>> 
>> [X] This message came from outside your organization
>> 
>> 
>> Hello Benoit,
>> 
>>Unfortunately no.
>>When I do it I will make sure to drop a line here.
>> 
>> Best regards,
>> Jordan
>> 
>> -Original Message-
>> From: benoit lair 
>> Sent: Tuesday, October 12, 2021 3:40 PM
>> To: users@cloudstack.apache.org
>> Subject: Re: Size of the snapshots volume
>> 
>> 
>> [X] This message came from outside your organization
>> 
>> 
>> Hello Jordan,
>> 
>> Could you proceed to your tests ? Have you got the same results ?
>> 
>> Regards, Benoit Lair
>> 
>> Le lun. 4 oct. 2021 à 17:59, Yordan Kostov  a 
>> écrit
>> :
>> 
>>> Here are a few considerations:
>>> 
>>> - First snapshot of volume is always full snap.
>>> - XenServer/XCP-NG backups are always thin.
>>> - Thin provisioning calculations never go down. Even if you delete 
>>> data from disk.
>>> 
>>> As you filled the disk of the VM to top the thin provisioning 
>>> threats it as full VM from that moment on even if data is deleted. 
>>> So the full snap that will be migrated to NFS will always be of max size.
>>> 
>>> I am not 100% certain as I am yet to start running backup tests.
>>> 
>>> Best regards,
>>> Jordan
>>> 
>>> -Original Message-
>>> From: Florian Noel 
>>> Sent: Monday, October 4, 2021 6:22 PM
>>> To: 'users@cloudstack.apache.org' 
>>> Subject: Size of the snapshots volume
>>> 
>>> 
>>> [X] This message came from outside your organization
>>> 
>>> 
>>> Hi,
>>> 
>>> I've a question about the snapshots volume in Cloudstack
>>> 
>>> When we take a snapshot of a volume, this create a VHD file on the 
>>> secondary storage.
>>> Snapshot size doesn't match volume size used.
>>> 
>>> Imagine a volume of 20GB, we fill the volume and empty it just after.
>>> We take a snapshot of the volume from Cloudstack frontend and 

Re: Understanding of Physical Network

[Cristian Ciobanu]

If you want to use 2 bond networks as you described, you can have 2 or
more, you can use the same NIC/bond for multiple "physical networks"

Example:

2XNICs - Bond1
2XNICs - Bond2

You can create 2 or more physical networks, if the traffic label you are
using in these networks is  "bond1 or bond2" .

You can have 2 "Physical networks" with the same network label but
different traffic type.  (Management, Guest, Public, Storage)



Regards,
Cristian


On Thu, Oct 21, 2021, 11:58 Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Can someone explain me concept of Physical Networks?
>
> Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1 bond I
> have Management, Guest and Public VLANs. On other - Storage VLANs.
>
> When I deploy ZONE should I create 2 Physical Networks? Or I can create 3
> (1?) network for example?
>
> I want to deploy Advanced Zone (without SG)
>
> I read article from ShapeBlue (
> https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/)
> but it doesn't help me:)
>
> Best regards, Evgeniy.
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as the
> intended recipient (recipients). If you are not the intended recipient of
> this email, do not copy or disclose its contents and delete the message and
> any attachments to it from your e-mail system. Any unauthorized use,
> dissemination, disclosure, printing or copying of this e-mail and files
> attached to it, except by the intended recipient, is illegal and is
> prohibited. Taking into account that data transmission via Internet is not
> secure, we assume no responsibility for any potential damage caused by data
> transmission errors or this message and the files attached to it.
>

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Alex Mattioli]

And bear in mind that this storage network will be used for your secondary 
storage, it will have traffic when templates are copied to primary storage and 
snapshots are copied to secondary storage.  If you are already segregating your 
primary storage traffic it is a good idea to then place this traffic on the 
same network. And as Dahn mentioned, if you want to segregate customer from 
platform traffic then you can place management on this same network.

Cheers
Alex

 


-Original Message-
From: Daan Hoogland  
Sent: 21 October 2021 11:25
To: users 
Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network

A reason to keep management with storage is not perse to keep it with storage 
but because you want it to be private, while guests and public are exposed.

On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Thx for the answer!
>
> What benefits will I get if I use more than 1 network?
>
> Somewhere I read than is better to use Management and Storage traffic 
> types on same Physical Network. Is it true?
>
> I forgot some information - we will use Presetup Storage for clusters. 
> We will use more than 1 public networks and MB (if possible) more than 
> 1 Guest for some Pods.
>
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:12 PM
> To: users 
> Subject: [!!Mass Mail]Re: Understanding of Physical Network
>
> yes evgenly,
> I think you are describing two physical networks.
>
> On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович < 
> evgeniy.dikev...@becloud.by> wrote:
>
> > Hi all!
> >
> > Can someone explain me concept of Physical Networks?
> >
> > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1 
> > bond I have Management, Guest and Public VLANs. On other - Storage VLANs.
> >
> > When I deploy ZONE should I create 2 Physical Networks? Or I can 
> > create 3
> > (1?) network for example?
> >
> > I want to deploy Advanced Zone (without SG)
> >
> > I read article from ShapeBlue (
> > https://www.shapeblue.com/understanding-cloudstacks-physical-network
> > in
> > g-architecture/)
> > but it doesn't help me:)
> >
> > Best regards, Evgeniy.
> > Внимание!
> > Это электронное письмо и все прикрепленные к нему файлы являются 
> > конфиденциальными и предназначены исключительно для использования 
> > лицом (лицами), которому (которым) оно предназначено. Если Вы не 
> > являетесь лицом (лицами), которому (которым) предназначено это 
> > письмо, не копируйте и не разглашайте его содержимое и удалите это 
> > сообщение и все вложения из Вашей почтовой системы. Любое 
> > несанкционированное использование, распространение, раскрытие, 
> > печать или копирование этого электронного письма и прикрепленных к 
> > нему файлов, кроме как лицом (лицами) которому (которым) они 
> > предназначены, является незаконным и запрещено. Принимая во 
> > внимание, что передача данных посредством Интернет не является 
> > безопасной, мы не несем никакой ответственности за любой 
> > потенциальный ущерб, причиненный в результате ошибок при передаче 
> > данных или этим сообщением и прикрепленными к нему
> файлами.
> >
> > Attention!
> > This email and all attachments to it are confidential and are 
> > intended solely for use by the person (or persons) referred to 
> > (mentioned) as the intended recipient (recipients). If you are not 
> > the intended recipient of this email, do not copy or disclose its 
> > contents and delete the message and any attachments to it from your e-mail 
> > system.
> > Any unauthorized use, dissemination, disclosure, printing or copying 
> > of this e-mail and files attached to it, except by the intended 
> > recipient, is illegal and is prohibited. Taking into account that 
> > data transmission via Internet is not secure, we assume no 
> > responsibility for any potential damage caused by data transmission 
> > errors or this
> message and the files attached to it.
> >
>
>
> --
> Daan
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются 
> конфиденциальными и предназначены исключительно для использования 
> лицом (лицами), которому (которым) оно предназначено. Если Вы не 
> являетесь лицом (лицами), которому (которым) предназначено это письмо, 
> не копируйте и не разглашайте его содержимое и удалите это сообщение и 
> все вложения из Вашей почтовой системы. Любое несанкционированное 
> использование, распространение, раскрытие, печать или копирование 
> этого электронного письма и прикрепленных к нему файлов, кроме как 
> лицом (лицами) которому (которым) они предназначены, является 
> незаконным и запрещено. Принимая во внимание, что передача данных 
> посредством Интернет не является безопасной, мы не несем никакой 
> ответственности за любой потенциальный ущерб, причиненный в результате 
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> Attention!
> This 

RE: Understanding of Physical Network

[Alex Mattioli]

Hi Evgeniy,

Physical networks consist of a mapping between a certain ACS type of networks 
(guest, management, storage, public) and the physical NICS.
You can very well have just one physical network for all types of networks, and 
many do that, but ideally you would segregate, let me give you a few examples.

Hosts with 2 NICs:   one physical network for everything.
Hosts with 4 NICs:   two physical networks, one for front end (Public, 
Guest, Management) and another for back end (storage).
Host with 6 NICs:three physical networks,  one for Public and Guest, one 
for Management and another for back end (storage).
Host with 8 NICs:as above, but you can then segregate different types of 
Guest networks in different NICs

Your case is clearly the second one, so you have to create two physical 
networks and set them with traffic labels which match the name of the network 
on Xen (that's how ACS knows on which NICs to deploy which network)

Hope that helps you to understand it.

Cheers
Alex

 


-Original Message-
From: Дикевич Евгений Александрович  
Sent: 21 October 2021 10:59
To: users@cloudstack.apache.org
Subject: Understanding of Physical Network

Hi all!

Can someone explain me concept of Physical Networks?

Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1 bond I have 
Management, Guest and Public VLANs. On other - Storage VLANs.

When I deploy ZONE should I create 2 Physical Networks? Or I can create 3 (1?) 
network for example?

I want to deploy Advanced Zone (without SG)

I read article from ShapeBlue 
(https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/)
 but it doesn't help me:)

Best regards, Evgeniy.
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

RE: Size of the snapshots volume

[Yordan Kostov]

Here is another thing I noticed.
- have a VM with a volume snapshots
- Expunge the VM so the disk is removed also
- check the Secondary Storage - backup still remains.

Does anyone knows if Cloudstack does a cleanup later or the orphaned backups 
will remain?

Regards,
Jordan 

-Original Message-
From: benoit lair  
Sent: Tuesday, October 19, 2021 1:22 PM
To: users@cloudstack.apache.org
Subject: Re: Size of the snapshots volume


[X] This message came from outside your organization


Hello Yordan,

I had same results with xcp-ng 8.2 and ACS 4.15.1

The max filled during the life of the disk will be the size of the snapshot

That's why i looking towards SDS with a solution giving me possibility to do 
some thin provisionning with XCP-NG I was thinking about an SDS which could 
give me block storage or at least file storage and acting as a proxy between my 
iscsi array and my xcp-ng

Linstor could be a solution, but for the moment i don't know if the plugin will 
be compatible with xcp-ng

Regards, Benoit

Le mar. 19 oct. 2021 à 11:46, Yordan Kostov  a écrit :

> Hello Benoit,
>
> Here are some results - 4.15.2 + XCP-NG. I made 2 VMs from 
> template - Centos 7, 46 GB hdd, 4% full
> - VM1 - root disk is as full as template.
> - VM2 - root disk is made full up to ~90%  ( cat /dev/zero >
> test_file1 )then the file was removed so the used space is again 4%.
> - scheduled backup goes through both VMs. First snapshot size is
> - VM1 -  2.3G
> - VM2 -  41G
> - Then on VM2 this script was run to fill and empty the disk 
> again
> - cat /dev/zero > /opt/test_file1; sync; rm /opt/ test_file1.
> - scheduled backup goes through both VMs. All snapshots size is:
> - VM1 - 2.3G
> - VM2 - 88G
>
> Once the disk is filled you will get a snapshot with size no 
> less than the size of the whole disk.
> May be there is a way to shrink it but I could not find it.
>
> Best regards,
> Jordan
>
> -Original Message-
> From: Yordan Kostov 
> Sent: Tuesday, October 12, 2021 3:58 PM
> To: users@cloudstack.apache.org
> Subject: RE: Size of the snapshots volume
>
>
> [X] This message came from outside your organization
>
>
> Hello Benoit,
>
> Unfortunately no.
> When I do it I will make sure to drop a line here.
>
> Best regards,
> Jordan
>
> -Original Message-
> From: benoit lair 
> Sent: Tuesday, October 12, 2021 3:40 PM
> To: users@cloudstack.apache.org
> Subject: Re: Size of the snapshots volume
>
>
> [X] This message came from outside your organization
>
>
> Hello Jordan,
>
> Could you proceed to your tests ? Have you got the same results ?
>
> Regards, Benoit Lair
>
> Le lun. 4 oct. 2021 à 17:59, Yordan Kostov  a 
> écrit
> :
>
> > Here are a few considerations:
> >
> > - First snapshot of volume is always full snap.
> > - XenServer/XCP-NG backups are always thin.
> > - Thin provisioning calculations never go down. Even if you delete 
> > data from disk.
> >
> > As you filled the disk of the VM to top the thin provisioning 
> > threats it as full VM from that moment on even if data is deleted. 
> > So the full snap that will be migrated to NFS will always be of max size.
> >
> > I am not 100% certain as I am yet to start running backup tests.
> >
> > Best regards,
> > Jordan
> >
> > -Original Message-
> > From: Florian Noel 
> > Sent: Monday, October 4, 2021 6:22 PM
> > To: 'users@cloudstack.apache.org' 
> > Subject: Size of the snapshots volume
> >
> >
> > [X] This message came from outside your organization
> >
> >
> > Hi,
> >
> > I've a question about the snapshots volume in Cloudstack
> >
> > When we take a snapshot of a volume, this create a VHD file on the 
> > secondary storage.
> > Snapshot size doesn't match volume size used.
> >
> > Imagine a volume of 20GB, we fill the volume and empty it just after.
> > We take a snapshot of the volume from Cloudstack frontend and its 
> > size is 20GB on the secondary storage while the volume is empty.
> >
> > We've made the same test with volume provisioning in thin, sparse 
> > and
> fat.
> > The results are the same.
> >
> > We use Cloudstack 4.15.1 with XCP-NG 8.1. The LUNs are connected in 
> > iSCSI on the hypervisors XCP.
> >
> > Thanks for your help.
> >
> > Best regards.
> >
> >
> > [Logo Web et Solutions]<
> > https://urldefense.com/v3/__https://cloud.letsignit.com/collect/bc/6
> > 0e 
> > 5c62f48323abd316580a3?p=NCQXXscJv3N-mDjmqdZzYH59ppVbYP3afFkR7SxQ1JaS
> > _e 
> > v9TYs06R5yG_cSPe6tLuS3Bgn1EjTO39P6hIWtNhqUZ5n-wh878kG0mKc-TDzCgMKxZA
> > oq 
> > vlt4NqCVlovo0bn9PcMUWFMak1jGIGRgGg==__;!!A6UyJA!zYKJBkzZPANfqT6kPkY_
> > Mf o8xu_hnCJDzEIYjPMOvqs3MwyZUs0N9FX1Ln1zICtHKJKHCye42DjJ$
> > >
> >
> > [Facebook]<
> > https://urldefense.com/v3/__https://cloud.letsignit.com/collect/bc/6
> > 0e 
> > 5c62f48323abd316580a3?p=NCQXXscJv3N-mDjmqdZzYH59ppVbYP3afFkR7SxQ1JaS
> > _e 
> > 

RE: Local simulation of Apache Cloudstack instances/API endpoints: state of the art, target groups and use cases

[Paul Angus]

Hi Peter,

I need to get round to polishing a dockerfile that would create an image to
be run as a CloudStack simulator in a container (or if there's enough
interest I could share it's current state for others to finish).

But. If you want to work on real world integrations, I'd guess that you
would likely to need real hosts to create VMs on. Trillian
(https://github.com/shapeblue/trillian) was created for the exact purpose
that you are describing.   In fact it runs most of the automated testing
done on CloudStack. And can support 10s even 100s of concurrent
environments.

I'm not going to lie - it takes a bit of setting up (and isn't local) - but
it's run thousands of times creating environments for testing business logic
and integrations


Regards

Paul Angus


-Original Message-
From: Muryshkin, Peter  
Sent: Thursday, October 21, 2021 11:30 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Local simulation of Apache Cloudstack instances/API endpoints:
state of the art, target groups and use cases

Hi all,

from what I can find, there are  three more or less established/already well
elaborated approaches to simulate a CloudStack instance locallly.
Depending on the target group and their goals, they can have different
levels of fidelity and usability.

1. Obviously CloudStack developers confgure a KVM development environment to
work inside it, this is part of the Apache CloudStack Hackerbook kindly
shared by ShapeBlue. [1] 2. For test scenarios, Hackerbook describes a
mocked simulator approach [2] 3. For users for whom the whole cloud system
is just a "black box", especially cloud beginners, there is a single
integrated Docker container. [3]

With the rise of CI/CD and infrastructure as code automation practices,
where you just need more or less on demand one or even many versions of the
CloudStack API,  [3] appears to be a crucial building block in the cloud
userspace before just "trying out CloudStack".

So it appears that there might be much demand on a Apache CloudStack
containerized instance:

1. Demand from potential new adopters, for their "Apache CloudStack to go"
demos 2. Demand from DevOps/GitOps/SRE/you-name-it enabled teams who
implement their virtual infrastructure for example with Terraform and the
CloudStack provider plugin and want to simulate rollout scenarios.

However, is this true?

* the container simulator hasn't been updated on DockerHub since a couple of
years; is there another place in meantime or will this approach dumped for
some reason?
* there is not so much discussion about this asset on mailing lists; so
there is not so much demand as one might assume?

What do you think?

kind regards

--

Peter Muryshkin
Fraunhofer Gesellschaft
https://www.linkedin.com/in/muryshkin/

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Дикевич Евгений Александрович]

THX A LOT!!!

Now I think I understand :)

MB you can answer another question? :) Can I dedicate Physical Network (some 
new PN with for example GRE isolation method) to some 1 Pod or Cluster?

-Original Message-
From: Wei ZHOU [mailto:ustcweiz...@gmail.com]
Sent: Thursday, October 21, 2021 1:12 PM
To: users 
Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network

It is better that the physical networks in cloudstack zone are the same as the 
bonds/nics on hypervisors.
but if they are not the same, it is not a problem - please set correct traffic 
labels on Traffic Types (The traffic types in a cloudstack physical network can 
use different traffic labels).

-Wei

On Thu, 21 Oct 2021 at 12:01, Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Then Physical Network in CS == bonds in hypervisors? And we should
> place traffic labels on Physical Network (bond) where are presented?
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:48 PM
> To: users 
> Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
>
> I would use one for storage and management and one for public and guest.
> This is a security consideration. You would also need to take into
> account how mucg traffic you generate; if you have a lot of hardly
> ever changing VMs you won't have much management traffic and this is probably 
> the best.
> If you have a lot of changes in you VMs and also a lot of IO, you
> might want to go for your initial setup: management gues and public on
> one bond and storage on the other. This is the default and good for
> most cases.as you have four nics and if you don't expect any
> congestion you might go for no bonds and have a physical network for
> each traffic type. I can't really give a definite answer there. You'll have 
> to do your architecture work.
>
> On Thu, Oct 21, 2021 at 11:41 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > If I correctly understand you in my case is better use 2 Physical
> > Networks
> > - 1 with Management traffic (and Management traffic label) and
> > another with Guest and Public (Guest and Public traffic labels). But
> > I have this 3 traffic types on 1 bond - It somehow affects?
> >
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Thursday, October 21, 2021 12:25 PM
> > To: users 
> > Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
> >
> > A reason to keep management with storage is not perse to keep it
> > with storage but because you want it to be private, while guests and
> > public are exposed.
> >
> > On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович <
> > evgeniy.dikev...@becloud.by> wrote:
> >
> > > Thx for the answer!
> > >
> > > What benefits will I get if I use more than 1 network?
> > >
> > > Somewhere I read than is better to use Management and Storage
> > > traffic types on same Physical Network. Is it true?
> > >
> > > I forgot some information - we will use Presetup Storage for clusters.
> > > We will use more than 1 public networks and MB (if possible) more
> > > than
> > > 1 Guest for some Pods.
> > >
> > >
> > >
> > > -Original Message-
> > > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > > Sent: Thursday, October 21, 2021 12:12 PM
> > > To: users 
> > > Subject: [!!Mass Mail]Re: Understanding of Physical Network
> > >
> > > yes evgenly,
> > > I think you are describing two physical networks.
> > >
> > > On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> > > evgeniy.dikev...@becloud.by> wrote:
> > >
> > > > Hi all!
> > > >
> > > > Can someone explain me concept of Physical Networks?
> > > >
> > > > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds.
> > > > On
> > > > 1 bond I have Management, Guest and Public VLANs. On other -
> > > > Storage
> > VLANs.
> > > >
> > > > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > > > create 3
> > > > (1?) network for example?
> > > >
> > > > I want to deploy Advanced Zone (without SG)
> > > >
> > > > I read article from ShapeBlue (
> > > > https://www.shapeblue.com/understanding-cloudstacks-physical-net
> > > > wo
> > > > rk
> > > > in
> > > > g-architecture/)
> > > > but it doesn't help me:)
> > > >
> > > > Best regards, Evgeniy.
> > > > Внимание!
> > > > Это электронное письмо и все прикрепленные к нему файлы являются
> > > > конфиденциальными и предназначены исключительно для
> > > > использования лицом (лицами), которому (которым) оно
> > > > предназначено. Если Вы не являетесь лицом (лицами), которому
> > > > (которым) предназначено это письмо, не копируйте и не
> > > > разглашайте его содержимое и удалите это сообщение и все
> > > > вложения из Вашей почтовой системы. Любое несанкционированное
> > > > использование, распространение, раскрытие, печать или
> > > > копирование этого электронного письма и прикрепленных 

Local simulation of Apache Cloudstack instances/API endpoints: state of the art, target groups and use cases

[Muryshkin, Peter]

Hi all,

from what I can find, there are  three more or less established/already well 
elaborated approaches to simulate a CloudStack instance locallly.
Depending on the target group and their goals, they can have different levels 
of fidelity and usability.

1. Obviously CloudStack developers confgure a KVM development environment to 
work inside it, this is part of the Apache CloudStack Hackerbook kindly shared 
by ShapeBlue. [1]
2. For test scenarios, Hackerbook describes a mocked simulator approach [2]
3. For users for whom the whole cloud system is just a "black box", especially 
cloud beginners, there is a single integrated Docker container. [3]

With the rise of CI/CD and infrastructure as code automation practices,  where 
you just need more or less on demand one or even many versions of the 
CloudStack API,
 [3] appears to be a crucial building block in the cloud userspace before just 
"trying out CloudStack".

So it appears that there might be much demand on a Apache CloudStack 
containerized instance:

1. Demand from potential new adopters, for their "Apache CloudStack to go" demos
2. Demand from DevOps/GitOps/SRE/you-name-it enabled teams who implement their 
virtual infrastructure for example with Terraform and the CloudStack provider 
plugin and want to simulate rollout scenarios.

However, is this true?

* the container simulator hasn't been updated on DockerHub since a couple of 
years; is there another place in meantime or will this approach dumped for some 
reason?
* there is not so much discussion about this asset on mailing lists; so there 
is not so much demand as one might assume?

What do you think?

kind regards

--

Peter Muryshkin
Fraunhofer Gesellschaft
https://www.linkedin.com/in/muryshkin/

Re: [!!Mass Mail]Re: Understanding of Physical Network

[Wei ZHOU]

It is better that the physical networks in cloudstack zone are the same as
the bonds/nics on hypervisors.
but if they are not the same, it is not a problem - please set correct
traffic labels on Traffic Types (The traffic types in a cloudstack physical
network can use different traffic labels).

-Wei

On Thu, 21 Oct 2021 at 12:01, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Then Physical Network in CS == bonds in hypervisors? And we should place
> traffic labels on Physical Network (bond) where are presented?
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:48 PM
> To: users 
> Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
>
> I would use one for storage and management and one for public and guest.
> This is a security consideration. You would also need to take into account
> how mucg traffic you generate; if you have a lot of hardly ever changing
> VMs you won't have much management traffic and this is probably the best.
> If you have a lot of changes in you VMs and also a lot of IO, you might
> want to go for your initial setup: management gues and public on one bond
> and storage on the other. This is the default and good for most cases.as
> you have four nics and if you don't expect any congestion you might go for
> no bonds and have a physical network for each traffic type. I can't really
> give a definite answer there. You'll have to do your architecture work.
>
> On Thu, Oct 21, 2021 at 11:41 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > If I correctly understand you in my case is better use 2 Physical
> > Networks
> > - 1 with Management traffic (and Management traffic label) and another
> > with Guest and Public (Guest and Public traffic labels). But I have
> > this 3 traffic types on 1 bond - It somehow affects?
> >
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Thursday, October 21, 2021 12:25 PM
> > To: users 
> > Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
> >
> > A reason to keep management with storage is not perse to keep it with
> > storage but because you want it to be private, while guests and public
> > are exposed.
> >
> > On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович <
> > evgeniy.dikev...@becloud.by> wrote:
> >
> > > Thx for the answer!
> > >
> > > What benefits will I get if I use more than 1 network?
> > >
> > > Somewhere I read than is better to use Management and Storage
> > > traffic types on same Physical Network. Is it true?
> > >
> > > I forgot some information - we will use Presetup Storage for clusters.
> > > We will use more than 1 public networks and MB (if possible) more
> > > than
> > > 1 Guest for some Pods.
> > >
> > >
> > >
> > > -Original Message-
> > > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > > Sent: Thursday, October 21, 2021 12:12 PM
> > > To: users 
> > > Subject: [!!Mass Mail]Re: Understanding of Physical Network
> > >
> > > yes evgenly,
> > > I think you are describing two physical networks.
> > >
> > > On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> > > evgeniy.dikev...@becloud.by> wrote:
> > >
> > > > Hi all!
> > > >
> > > > Can someone explain me concept of Physical Networks?
> > > >
> > > > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On
> > > > 1 bond I have Management, Guest and Public VLANs. On other -
> > > > Storage
> > VLANs.
> > > >
> > > > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > > > create 3
> > > > (1?) network for example?
> > > >
> > > > I want to deploy Advanced Zone (without SG)
> > > >
> > > > I read article from ShapeBlue (
> > > > https://www.shapeblue.com/understanding-cloudstacks-physical-netwo
> > > > rk
> > > > in
> > > > g-architecture/)
> > > > but it doesn't help me:)
> > > >
> > > > Best regards, Evgeniy.
> > > > Внимание!
> > > > Это электронное письмо и все прикрепленные к нему файлы являются
> > > > конфиденциальными и предназначены исключительно для использования
> > > > лицом (лицами), которому (которым) оно предназначено. Если Вы не
> > > > являетесь лицом (лицами), которому (которым) предназначено это
> > > > письмо, не копируйте и не разглашайте его содержимое и удалите это
> > > > сообщение и все вложения из Вашей почтовой системы. Любое
> > > > несанкционированное использование, распространение, раскрытие,
> > > > печать или копирование этого электронного письма и прикрепленных к
> > > > нему файлов, кроме как лицом (лицами) которому (которым) они
> > > > предназначены, является незаконным и запрещено. Принимая во
> > > > внимание, что передача данных посредством Интернет не является
> > > > безопасной, мы не несем никакой ответственности за любой
> > > > потенциальный ущерб, причиненный в результате ошибок при передаче
> > > > данных или этим сообщением и прикрепленными к нему
> > > 

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Дикевич Евгений Александрович]

Then Physical Network in CS == bonds in hypervisors? And we should place 
traffic labels on Physical Network (bond) where are presented?

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Thursday, October 21, 2021 12:48 PM
To: users 
Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network

I would use one for storage and management and one for public and guest.
This is a security consideration. You would also need to take into account how 
mucg traffic you generate; if you have a lot of hardly ever changing VMs you 
won't have much management traffic and this is probably the best.
If you have a lot of changes in you VMs and also a lot of IO, you might want to 
go for your initial setup: management gues and public on one bond and storage 
on the other. This is the default and good for most cases.as you have four nics 
and if you don't expect any congestion you might go for no bonds and have a 
physical network for each traffic type. I can't really give a definite answer 
there. You'll have to do your architecture work.

On Thu, Oct 21, 2021 at 11:41 AM Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> If I correctly understand you in my case is better use 2 Physical
> Networks
> - 1 with Management traffic (and Management traffic label) and another
> with Guest and Public (Guest and Public traffic labels). But I have
> this 3 traffic types on 1 bond - It somehow affects?
>
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:25 PM
> To: users 
> Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
>
> A reason to keep management with storage is not perse to keep it with
> storage but because you want it to be private, while guests and public
> are exposed.
>
> On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > Thx for the answer!
> >
> > What benefits will I get if I use more than 1 network?
> >
> > Somewhere I read than is better to use Management and Storage
> > traffic types on same Physical Network. Is it true?
> >
> > I forgot some information - we will use Presetup Storage for clusters.
> > We will use more than 1 public networks and MB (if possible) more
> > than
> > 1 Guest for some Pods.
> >
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Thursday, October 21, 2021 12:12 PM
> > To: users 
> > Subject: [!!Mass Mail]Re: Understanding of Physical Network
> >
> > yes evgenly,
> > I think you are describing two physical networks.
> >
> > On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> > evgeniy.dikev...@becloud.by> wrote:
> >
> > > Hi all!
> > >
> > > Can someone explain me concept of Physical Networks?
> > >
> > > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On
> > > 1 bond I have Management, Guest and Public VLANs. On other -
> > > Storage
> VLANs.
> > >
> > > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > > create 3
> > > (1?) network for example?
> > >
> > > I want to deploy Advanced Zone (without SG)
> > >
> > > I read article from ShapeBlue (
> > > https://www.shapeblue.com/understanding-cloudstacks-physical-netwo
> > > rk
> > > in
> > > g-architecture/)
> > > but it doesn't help me:)
> > >
> > > Best regards, Evgeniy.
> > > Внимание!
> > > Это электронное письмо и все прикрепленные к нему файлы являются
> > > конфиденциальными и предназначены исключительно для использования
> > > лицом (лицами), которому (которым) оно предназначено. Если Вы не
> > > являетесь лицом (лицами), которому (которым) предназначено это
> > > письмо, не копируйте и не разглашайте его содержимое и удалите это
> > > сообщение и все вложения из Вашей почтовой системы. Любое
> > > несанкционированное использование, распространение, раскрытие,
> > > печать или копирование этого электронного письма и прикрепленных к
> > > нему файлов, кроме как лицом (лицами) которому (которым) они
> > > предназначены, является незаконным и запрещено. Принимая во
> > > внимание, что передача данных посредством Интернет не является
> > > безопасной, мы не несем никакой ответственности за любой
> > > потенциальный ущерб, причиненный в результате ошибок при передаче
> > > данных или этим сообщением и прикрепленными к нему
> > файлами.
> > >
> > > Attention!
> > > This email and all attachments to it are confidential and are
> > > intended solely for use by the person (or persons) referred to
> > > (mentioned) as the intended recipient (recipients). If you are not
> > > the intended recipient of this email, do not copy or disclose its
> > > contents and delete the message and any attachments to it from
> > > your
> e-mail system.
> > > Any unauthorized use, dissemination, disclosure, printing or
> > > copying of this e-mail and files attached to it, except by the
> > > intended recipient, is illegal and is prohibited. Taking 

Re: [!!Mass Mail]Re: Understanding of Physical Network

[Daan Hoogland]

I would use one for storage and management and one for public and guest.
This is a security consideration. You would also need to take into account
how mucg traffic you generate; if you have a lot of hardly ever changing
VMs you won't have much management traffic and this is probably the best.
If you have a lot of changes in you VMs and also a lot of IO, you might
want to go for your initial setup: management gues and public on one bond
and storage on the other. This is the default and good for most cases.as
you have four nics and if you don't expect any congestion you might go for
no bonds and have a physical network for each traffic type. I can't really
give a definite answer there. You'll have to do your architecture work.

On Thu, Oct 21, 2021 at 11:41 AM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> If I correctly understand you in my case is better use 2 Physical Networks
> - 1 with Management traffic (and Management traffic label) and another with
> Guest and Public (Guest and Public traffic labels). But I have this 3
> traffic types on 1 bond - It somehow affects?
>
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:25 PM
> To: users 
> Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network
>
> A reason to keep management with storage is not perse to keep it with
> storage but because you want it to be private, while guests and public are
> exposed.
>
> On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > Thx for the answer!
> >
> > What benefits will I get if I use more than 1 network?
> >
> > Somewhere I read than is better to use Management and Storage traffic
> > types on same Physical Network. Is it true?
> >
> > I forgot some information - we will use Presetup Storage for clusters.
> > We will use more than 1 public networks and MB (if possible) more than
> > 1 Guest for some Pods.
> >
> >
> >
> > -Original Message-
> > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> > Sent: Thursday, October 21, 2021 12:12 PM
> > To: users 
> > Subject: [!!Mass Mail]Re: Understanding of Physical Network
> >
> > yes evgenly,
> > I think you are describing two physical networks.
> >
> > On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> > evgeniy.dikev...@becloud.by> wrote:
> >
> > > Hi all!
> > >
> > > Can someone explain me concept of Physical Networks?
> > >
> > > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1
> > > bond I have Management, Guest and Public VLANs. On other - Storage
> VLANs.
> > >
> > > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > > create 3
> > > (1?) network for example?
> > >
> > > I want to deploy Advanced Zone (without SG)
> > >
> > > I read article from ShapeBlue (
> > > https://www.shapeblue.com/understanding-cloudstacks-physical-network
> > > in
> > > g-architecture/)
> > > but it doesn't help me:)
> > >
> > > Best regards, Evgeniy.
> > > Внимание!
> > > Это электронное письмо и все прикрепленные к нему файлы являются
> > > конфиденциальными и предназначены исключительно для использования
> > > лицом (лицами), которому (которым) оно предназначено. Если Вы не
> > > являетесь лицом (лицами), которому (которым) предназначено это
> > > письмо, не копируйте и не разглашайте его содержимое и удалите это
> > > сообщение и все вложения из Вашей почтовой системы. Любое
> > > несанкционированное использование, распространение, раскрытие,
> > > печать или копирование этого электронного письма и прикрепленных к
> > > нему файлов, кроме как лицом (лицами) которому (которым) они
> > > предназначены, является незаконным и запрещено. Принимая во
> > > внимание, что передача данных посредством Интернет не является
> > > безопасной, мы не несем никакой ответственности за любой
> > > потенциальный ущерб, причиненный в результате ошибок при передаче
> > > данных или этим сообщением и прикрепленными к нему
> > файлами.
> > >
> > > Attention!
> > > This email and all attachments to it are confidential and are
> > > intended solely for use by the person (or persons) referred to
> > > (mentioned) as the intended recipient (recipients). If you are not
> > > the intended recipient of this email, do not copy or disclose its
> > > contents and delete the message and any attachments to it from your
> e-mail system.
> > > Any unauthorized use, dissemination, disclosure, printing or copying
> > > of this e-mail and files attached to it, except by the intended
> > > recipient, is illegal and is prohibited. Taking into account that
> > > data transmission via Internet is not secure, we assume no
> > > responsibility for any potential damage caused by data transmission
> > > errors or this
> > message and the files attached to it.
> > >
> >
> >
> > --
> > Daan
> > Внимание!
> > Это электронное письмо и все прикрепленные к нему файлы являются
> > конфиденциальными и предназначены 

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Дикевич Евгений Александрович]

If I correctly understand you in my case is better use 2 Physical Networks - 1 
with Management traffic (and Management traffic label) and another with Guest 
and Public (Guest and Public traffic labels). But I have this 3 traffic types 
on 1 bond - It somehow affects?



-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Thursday, October 21, 2021 12:25 PM
To: users 
Subject: Re: [!!Mass Mail]Re: Understanding of Physical Network

A reason to keep management with storage is not perse to keep it with storage 
but because you want it to be private, while guests and public are exposed.

On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Thx for the answer!
>
> What benefits will I get if I use more than 1 network?
>
> Somewhere I read than is better to use Management and Storage traffic
> types on same Physical Network. Is it true?
>
> I forgot some information - we will use Presetup Storage for clusters.
> We will use more than 1 public networks and MB (if possible) more than
> 1 Guest for some Pods.
>
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:12 PM
> To: users 
> Subject: [!!Mass Mail]Re: Understanding of Physical Network
>
> yes evgenly,
> I think you are describing two physical networks.
>
> On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > Hi all!
> >
> > Can someone explain me concept of Physical Networks?
> >
> > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1
> > bond I have Management, Guest and Public VLANs. On other - Storage VLANs.
> >
> > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > create 3
> > (1?) network for example?
> >
> > I want to deploy Advanced Zone (without SG)
> >
> > I read article from ShapeBlue (
> > https://www.shapeblue.com/understanding-cloudstacks-physical-network
> > in
> > g-architecture/)
> > but it doesn't help me:)
> >
> > Best regards, Evgeniy.
> > Внимание!
> > Это электронное письмо и все прикрепленные к нему файлы являются
> > конфиденциальными и предназначены исключительно для использования
> > лицом (лицами), которому (которым) оно предназначено. Если Вы не
> > являетесь лицом (лицами), которому (которым) предназначено это
> > письмо, не копируйте и не разглашайте его содержимое и удалите это
> > сообщение и все вложения из Вашей почтовой системы. Любое
> > несанкционированное использование, распространение, раскрытие,
> > печать или копирование этого электронного письма и прикрепленных к
> > нему файлов, кроме как лицом (лицами) которому (которым) они
> > предназначены, является незаконным и запрещено. Принимая во
> > внимание, что передача данных посредством Интернет не является
> > безопасной, мы не несем никакой ответственности за любой
> > потенциальный ущерб, причиненный в результате ошибок при передаче
> > данных или этим сообщением и прикрепленными к нему
> файлами.
> >
> > Attention!
> > This email and all attachments to it are confidential and are
> > intended solely for use by the person (or persons) referred to
> > (mentioned) as the intended recipient (recipients). If you are not
> > the intended recipient of this email, do not copy or disclose its
> > contents and delete the message and any attachments to it from your e-mail 
> > system.
> > Any unauthorized use, dissemination, disclosure, printing or copying
> > of this e-mail and files attached to it, except by the intended
> > recipient, is illegal and is prohibited. Taking into account that
> > data transmission via Internet is not secure, we assume no
> > responsibility for any potential damage caused by data transmission
> > errors or this
> message and the files attached to it.
> >
>
>
> --
> Daan
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования
> лицом (лицами), которому (которым) оно предназначено. Если Вы не
> являетесь лицом (лицами), которому (которым) предназначено это письмо,
> не копируйте и не разглашайте его содержимое и удалите это сообщение и
> все вложения из Вашей почтовой системы. Любое несанкционированное
> использование, распространение, раскрытие, печать или копирование
> этого электронного письма и прикрепленных к нему файлов, кроме как
> лицом (лицами) которому (которым) они предназначены, является
> незаконным и запрещено. Принимая во внимание, что передача данных
> посредством Интернет не является безопасной, мы не несем никакой
> ответственности за любой потенциальный ущерб, причиненный в результате
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as
> the intended recipient (recipients). If you are not the intended

Re: Default firewall and egress rule

[Wei ZHOU]

Hi Irvin,

To access a vm in an isolated network, you need to use static nat, port
forwarding or load balancer.

Please refer to
http://docs.cloudstack.apache.org/en/4.15.2.0/adminguide/networking/ip_forwarding_and_firewalling.html

-Wei

On Thu, 21 Oct 2021 at 11:09, SVI  wrote:

> Thanks Wei! Another thing, can I set a default firewall rule? For egress,
> I’ll check the networking offering
>
> Thanks,
> Irvin
>
> > On Oct 21, 2021, at 4:44 PM, Wei ZHOU  wrote:
> >
> > Hi SVI,
> >
> > It looks like you do use an advanced zone.
> >
> > If your users create vm on isolated networks, please see my first reply.
> > If your users create vm on shared networks, firewall/ingress/egress rule
> is not supported in cloudstack. You need to configure the firewall in vms.
> >
> > -Wei
> >
> > On Thu, 21 Oct 2021 at 10:15, SVI  jcapagc...@svi.com.ph>> wrote:
> > I’m currently using 4.15.2, Zone and cluster is XenServer, XCP-NG 8.2.0.
> >
> > Additional details:
> >
> > Zone:
> > Network Type: Advanced
> > Security Groups: Disabled
> > 2 Physical Networks
> > 
> >
> > Pod:
> > 
> >
> > Cluster:
> > 
> >
> > Host:
> >
> >
> > Thanks,
> > Irvin
> >
> >> On Oct 21, 2021, at 3:59 PM, Wei ZHOU  ustcweiz...@gmail.com>> wrote:
> >>
> >> Hi,
> >>
> >> As I said, please give more details. Otherwise, it is hard to answer
> >> your questions.
> >>
> >> for example, zone type, network type, hypervisor ...
> >>
> >> -Wei
> >>
> >>
> >>
> >> On Thu, 21 Oct 2021 at 09:49, SVI  jcapagc...@svi.com.ph>> wrote:
> >>
> >>> Hi Wei,
> >>>
> >>> Unfortunately, I am not using advanced zone. And yes, the Cloudstack UI
> >>> (4.15.2) is exposed to users.
> >>>
> >>> Thanks.
> >>>
>  On Oct 21, 2021, at 2:37 PM, Wei ZHOU  ustcweiz...@gmail.com>> wrote:
> 
>  Hi,
> 
>  I assume you use isolated networks in advanced zone.
>  the firewall rule list is empty by default, egress rule can be "allow
> >>> all"
>  or "deny all" per network(check 'default egress policy' of network
> >>> offering)
> 
>  Do you expose cloudstack api/ui to users ? It's better to give more
> >>> details.
> 
>  -Wei
> 
>  On Thu, 21 Oct 2021 at 02:52, SVI  jcapagc...@svi.com.ph>> wrote:
> 
> > Hi,
> >
> > I need help in setting up default networking for new users that will
> > create an instance. I wanted it to have a default firewall rule and
> >>> default
> > egress rule so they don’t need to set it up on initial creation of
> > instance. How can I do this?
> >
> > Thanks.
> >>>
> >>>
> >
>
>

Re: [!!Mass Mail]Re: Understanding of Physical Network

[Daan Hoogland]

A reason to keep management with storage is not perse to keep it with
storage but because you want it to be private, while guests and public are
exposed.

On Thu, Oct 21, 2021 at 11:22 AM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Thx for the answer!
>
> What benefits will I get if I use more than 1 network?
>
> Somewhere I read than is better to use Management and Storage traffic
> types on same Physical Network. Is it true?
>
> I forgot some information - we will use Presetup Storage for clusters. We
> will use more than 1 public networks and MB (if possible) more than 1 Guest
> for some Pods.
>
>
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, October 21, 2021 12:12 PM
> To: users 
> Subject: [!!Mass Mail]Re: Understanding of Physical Network
>
> yes evgenly,
> I think you are describing two physical networks.
>
> On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
> evgeniy.dikev...@becloud.by> wrote:
>
> > Hi all!
> >
> > Can someone explain me concept of Physical Networks?
> >
> > Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1
> > bond I have Management, Guest and Public VLANs. On other - Storage VLANs.
> >
> > When I deploy ZONE should I create 2 Physical Networks? Or I can
> > create 3
> > (1?) network for example?
> >
> > I want to deploy Advanced Zone (without SG)
> >
> > I read article from ShapeBlue (
> > https://www.shapeblue.com/understanding-cloudstacks-physical-networkin
> > g-architecture/)
> > but it doesn't help me:)
> >
> > Best regards, Evgeniy.
> > Внимание!
> > Это электронное письмо и все прикрепленные к нему файлы являются
> > конфиденциальными и предназначены исключительно для использования
> > лицом (лицами), которому (которым) оно предназначено. Если Вы не
> > являетесь лицом (лицами), которому (которым) предназначено это письмо,
> > не копируйте и не разглашайте его содержимое и удалите это сообщение и
> > все вложения из Вашей почтовой системы. Любое несанкционированное
> > использование, распространение, раскрытие, печать или копирование
> > этого электронного письма и прикрепленных к нему файлов, кроме как
> > лицом (лицами) которому (которым) они предназначены, является
> > незаконным и запрещено. Принимая во внимание, что передача данных
> > посредством Интернет не является безопасной, мы не несем никакой
> > ответственности за любой потенциальный ущерб, причиненный в результате
> > ошибок при передаче данных или этим сообщением и прикрепленными к нему
> файлами.
> >
> > Attention!
> > This email and all attachments to it are confidential and are intended
> > solely for use by the person (or persons) referred to (mentioned) as
> > the intended recipient (recipients). If you are not the intended
> > recipient of this email, do not copy or disclose its contents and
> > delete the message and any attachments to it from your e-mail system.
> > Any unauthorized use, dissemination, disclosure, printing or copying
> > of this e-mail and files attached to it, except by the intended
> > recipient, is illegal and is prohibited. Taking into account that data
> > transmission via Internet is not secure, we assume no responsibility
> > for any potential damage caused by data transmission errors or this
> message and the files attached to it.
> >
>
>
> --
> Daan
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as the
> intended recipient (recipients). If you are not the intended recipient of
> this email, do not copy or disclose its contents and delete the message and
> any attachments to it from your e-mail system. Any unauthorized use,
> dissemination, disclosure, printing or copying of this e-mail and files
> attached to it, except by the intended recipient, is illegal and is
> prohibited. Taking into account that data transmission via Internet is not
> secure, we assume no responsibility for any potential damage caused by data
> transmission errors or this 

RE: [!!Mass Mail]Re: Understanding of Physical Network

[Дикевич Евгений Александрович]

Thx for the answer!

What benefits will I get if I use more than 1 network?

Somewhere I read than is better to use Management and Storage traffic types on 
same Physical Network. Is it true?

I forgot some information - we will use Presetup Storage for clusters. We will 
use more than 1 public networks and MB (if possible) more than 1 Guest for some 
Pods.



-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Thursday, October 21, 2021 12:12 PM
To: users 
Subject: [!!Mass Mail]Re: Understanding of Physical Network

yes evgenly,
I think you are describing two physical networks.

On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Can someone explain me concept of Physical Networks?
>
> Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1
> bond I have Management, Guest and Public VLANs. On other - Storage VLANs.
>
> When I deploy ZONE should I create 2 Physical Networks? Or I can
> create 3
> (1?) network for example?
>
> I want to deploy Advanced Zone (without SG)
>
> I read article from ShapeBlue (
> https://www.shapeblue.com/understanding-cloudstacks-physical-networkin
> g-architecture/)
> but it doesn't help me:)
>
> Best regards, Evgeniy.
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования
> лицом (лицами), которому (которым) оно предназначено. Если Вы не
> являетесь лицом (лицами), которому (которым) предназначено это письмо,
> не копируйте и не разглашайте его содержимое и удалите это сообщение и
> все вложения из Вашей почтовой системы. Любое несанкционированное
> использование, распространение, раскрытие, печать или копирование
> этого электронного письма и прикрепленных к нему файлов, кроме как
> лицом (лицами) которому (которым) они предназначены, является
> незаконным и запрещено. Принимая во внимание, что передача данных
> посредством Интернет не является безопасной, мы не несем никакой
> ответственности за любой потенциальный ущерб, причиненный в результате
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as
> the intended recipient (recipients). If you are not the intended
> recipient of this email, do not copy or disclose its contents and
> delete the message and any attachments to it from your e-mail system.
> Any unauthorized use, dissemination, disclosure, printing or copying
> of this e-mail and files attached to it, except by the intended
> recipient, is illegal and is prohibited. Taking into account that data
> transmission via Internet is not secure, we assume no responsibility
> for any potential damage caused by data transmission errors or this message 
> and the files attached to it.
>


--
Daan
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Experience with clustered/shared filesystems based on SAN storage on KVM?

[Brussk, Michael]

Hello community,

today I need your experience and knowhow about clustered/shared filesystems 
based on SAN storage to be used with KVM.
We need to consider about a clustered/shared filesystem based on SAN storage 
(no NFS or iSCSI), but do not have any knowhow or experience with this.
Those I would like to ask if there any productive used environments out there 
based on SAN storage on KVM?
If so, which clustered/shared filesystem you are using and how is your 
experience with that (stability, reliability, maintainability, performance, 
useability,...)?
Furthermore, if you had already to consider in the past between SAN storage or 
CEPH, I would also like to participate on your considerations and results :)

Regards,
Michael

Re: Understanding of Physical Network

[Daan Hoogland]

yes evgenly,
I think you are describing two physical networks.

On Thu, Oct 21, 2021 at 10:58 AM Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Can someone explain me concept of Physical Networks?
>
> Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1 bond I
> have Management, Guest and Public VLANs. On other - Storage VLANs.
>
> When I deploy ZONE should I create 2 Physical Networks? Or I can create 3
> (1?) network for example?
>
> I want to deploy Advanced Zone (without SG)
>
> I read article from ShapeBlue (
> https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/)
> but it doesn't help me:)
>
> Best regards, Evgeniy.
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> Attention!
> This email and all attachments to it are confidential and are intended
> solely for use by the person (or persons) referred to (mentioned) as the
> intended recipient (recipients). If you are not the intended recipient of
> this email, do not copy or disclose its contents and delete the message and
> any attachments to it from your e-mail system. Any unauthorized use,
> dissemination, disclosure, printing or copying of this e-mail and files
> attached to it, except by the intended recipient, is illegal and is
> prohibited. Taking into account that data transmission via Internet is not
> secure, we assume no responsibility for any potential damage caused by data
> transmission errors or this message and the files attached to it.
>


-- 
Daan

Re: Default firewall and egress rule

[SVI]

Thanks Wei! Another thing, can I set a default firewall rule? For egress, I’ll 
check the networking offering

Thanks,
Irvin

> On Oct 21, 2021, at 4:44 PM, Wei ZHOU  wrote:
> 
> Hi SVI,
> 
> It looks like you do use an advanced zone.
> 
> If your users create vm on isolated networks, please see my first reply.
> If your users create vm on shared networks, firewall/ingress/egress rule is 
> not supported in cloudstack. You need to configure the firewall in vms.
> 
> -Wei
> 
> On Thu, 21 Oct 2021 at 10:15, SVI  > wrote:
> I’m currently using 4.15.2, Zone and cluster is XenServer, XCP-NG 8.2.0. 
> 
> Additional details:
> 
> Zone:
> Network Type: Advanced
> Security Groups: Disabled
> 2 Physical Networks
> 
> 
> Pod:
> 
> 
> Cluster:
> 
> 
> Host:
> 
> 
> Thanks,
> Irvin
> 
>> On Oct 21, 2021, at 3:59 PM, Wei ZHOU > > wrote:
>> 
>> Hi,
>> 
>> As I said, please give more details. Otherwise, it is hard to answer
>> your questions.
>> 
>> for example, zone type, network type, hypervisor ...
>> 
>> -Wei
>> 
>> 
>> 
>> On Thu, 21 Oct 2021 at 09:49, SVI > > wrote:
>> 
>>> Hi Wei,
>>> 
>>> Unfortunately, I am not using advanced zone. And yes, the Cloudstack UI
>>> (4.15.2) is exposed to users.
>>> 
>>> Thanks.
>>> 
 On Oct 21, 2021, at 2:37 PM, Wei ZHOU >>> > wrote:
 
 Hi,
 
 I assume you use isolated networks in advanced zone.
 the firewall rule list is empty by default, egress rule can be "allow
>>> all"
 or "deny all" per network(check 'default egress policy' of network
>>> offering)
 
 Do you expose cloudstack api/ui to users ? It's better to give more
>>> details.
 
 -Wei
 
 On Thu, 21 Oct 2021 at 02:52, SVI >>> > wrote:
 
> Hi,
> 
> I need help in setting up default networking for new users that will
> create an instance. I wanted it to have a default firewall rule and
>>> default
> egress rule so they don’t need to set it up on initial creation of
> instance. How can I do this?
> 
> Thanks.
>>> 
>>> 
> 

Understanding of Physical Network

[Дикевич Евгений Александрович]

Hi all!

Can someone explain me concept of Physical Networks?

Now I have Xen hosts with 4 NICs. They are grouped in 2 bonds. On 1 bond I have 
Management, Guest and Public VLANs. On other - Storage VLANs.

When I deploy ZONE should I create 2 Physical Networks? Or I can create 3 (1?) 
network for example?

I want to deploy Advanced Zone (without SG)

I read article from ShapeBlue 
(https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/)
 but it doesn't help me:)

Best regards, Evgeniy.
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended solely 
for use by the person (or persons) referred to (mentioned) as the intended 
recipient (recipients). If you are not the intended recipient of this email, do 
not copy or disclose its contents and delete the message and any attachments to 
it from your e-mail system. Any unauthorized use, dissemination, disclosure, 
printing or copying of this e-mail and files attached to it, except by the 
intended recipient, is illegal and is prohibited. Taking into account that data 
transmission via Internet is not secure, we assume no responsibility for any 
potential damage caused by data transmission errors or this message and the 
files attached to it.

Re: Default firewall and egress rule

[Wei ZHOU]

Hi,

As I said, please give more details. Otherwise, it is hard to answer
your questions.

for example, zone type, network type, hypervisor ...

-Wei



On Thu, 21 Oct 2021 at 09:49, SVI  wrote:

> Hi Wei,
>
> Unfortunately, I am not using advanced zone. And yes, the Cloudstack UI
> (4.15.2) is exposed to users.
>
> Thanks.
>
> > On Oct 21, 2021, at 2:37 PM, Wei ZHOU  wrote:
> >
> > Hi,
> >
> > I assume you use isolated networks in advanced zone.
> > the firewall rule list is empty by default, egress rule can be "allow
> all"
> > or "deny all" per network(check 'default egress policy' of network
> offering)
> >
> > Do you expose cloudstack api/ui to users ? It's better to give more
> details.
> >
> > -Wei
> >
> > On Thu, 21 Oct 2021 at 02:52, SVI  wrote:
> >
> >> Hi,
> >>
> >> I need help in setting up default networking for new users that will
> >> create an instance. I wanted it to have a default firewall rule and
> default
> >> egress rule so they don’t need to set it up on initial creation of
> >> instance. How can I do this?
> >>
> >> Thanks.
>
>

Re: Default firewall and egress rule

[SVI]

Hi Wei,

Unfortunately, I am not using advanced zone. And yes, the Cloudstack UI 
(4.15.2) is exposed to users.

Thanks.

> On Oct 21, 2021, at 2:37 PM, Wei ZHOU  wrote:
> 
> Hi,
> 
> I assume you use isolated networks in advanced zone.
> the firewall rule list is empty by default, egress rule can be "allow all"
> or "deny all" per network(check 'default egress policy' of network offering)
> 
> Do you expose cloudstack api/ui to users ? It's better to give more details.
> 
> -Wei
> 
> On Thu, 21 Oct 2021 at 02:52, SVI  wrote:
> 
>> Hi,
>> 
>> I need help in setting up default networking for new users that will
>> create an instance. I wanted it to have a default firewall rule and default
>> egress rule so they don’t need to set it up on initial creation of
>> instance. How can I do this?
>> 
>> Thanks.

RE: New Terraform artifacts published for testing

[Piotr Pisz]

Hi Harikrishna!

I test this provider strongly and so far I have not found any errors (eg
work as expected).
But I have a question, do you plan to adapt this provider's capabilities to
the new CS 4.16 and kubernetes plugin?
I am very interested in setting up a K8S cluster using CS (preferably with
kubernetes plugin) with terraform (or CS + kubespray + terraform without
plugin).
Will this privider be published (along with the documentation) in
registry.terraform.io?
Any roadmap? :-)

Regards,
Piotr


-Original Message-
From: Harikrishna Patnala  
Sent: Wednesday, October 20, 2021 4:12 PM
To: 'users@cloudstack.apache.org' 
Cc: d...@cloudstack.apache.org
Subject: New Terraform artifacts published for testing

Hi All,

We have published the new artifacts to the Terraform registry
https://registry.terraform.io/providers/cloudstack/cloudstack/latest. These
are created only for testing purposes with tag v0.4.0-pre.

May I ask the terraform users to help in testing it and report if you find
any issues here at on
https://github.com/apache/cloudstack-terraform-provider/issues? We have
already fixed some issues and done some testing. If everything goes well we
can create RC1 in the next week or so.

Regards,
Harikrishna


 

Re: Default firewall and egress rule

[Wei ZHOU]

Hi,

I assume you use isolated networks in advanced zone.
the firewall rule list is empty by default, egress rule can be "allow all"
or "deny all" per network(check 'default egress policy' of network offering)

Do you expose cloudstack api/ui to users ? It's better to give more details.

-Wei

On Thu, 21 Oct 2021 at 02:52, SVI  wrote:

> Hi,
>
> I need help in setting up default networking for new users that will
> create an instance. I wanted it to have a default firewall rule and default
> egress rule so they don’t need to set it up on initial creation of
> instance. How can I do this?
>
> Thanks.