Can't select network offerings in new shared networks

2021-07-14 Thread Joshua Schaeffer
ACS: 4.15.0.0
Hypervisor: KVM
OS: Ubuntu 20.04

In creating a shared network I'm only given one network offering option and 
trying to figure out how to make the other offerings that are included with the 
base install available. I'm creating the shared network in the UI and the only 
network offering I can choose from is "QuickCloudNoServices". I can see in the 
list of network offerings that there are others defined and they are just the 
defaults included with the base install. Below are some screenshots of what I'm 
seeing:

https://drive.google.com/file/d/1Y5G8J2-mfj68K0MoLIROHVfuziZIqq_m/view?usp=sharing
https://drive.google.com/file/d/1Fz2NRM3ZssN3IGQ_Ju1FJJtGyM-Q1hSb/view?usp=sharing

I think this is because the "VirtualRouter" network service provided for my 
guest network is disabled, but I get an error when I try to enable it. Under 
the physical network I click on the network, go to the "Network Service 
Providers' tab, select the "VirtualRouter" provider, and click "Enable 
provider". Afterwards I get the following message in the UI:

Enable provider
(VirtualRouter) Provider is not ready, cannot Enable the provider, please 
configure the provider first

And I see the following in the management-server logs (I don't see anything 
relevant from the compute logs):

2021-07-14 16:08:54,090 DEBUG [c.c.a.ApiServlet] 
(qtp1644231115-6023:ctx-b12d46cd) (logid:4beba9f7) ===START===  172.16.44.18 -- 
GET  
id=a6bca386-7a6a-410b-aaa2-fe15c8f422d4=Enabled=updateNetworkServiceProvider=json
2021-07-14 16:08:54,134 DEBUG [c.c.a.ApiServer] 
(qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) CIDRs from 
which account 'Acct[f8d6949d-cd74-11eb-b1da-5254008f72d5-admin]' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2021-07-14 16:08:54,372 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-4:ctx-975d9732 job-324) (logid:b295210b) Add job-324 into job 
monitoring
2021-07-14 16:08:54,389 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) submit async 
job-324, details: AsyncJobVO {id:324, userId: 2, accountId: 2, instanceType: 
PhysicalNetworkServiceProvider, instanceId: null, cmd: 
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
 cmdInfo: 
{"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId":"812","id":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","state":"Enabled","ctxDetails":"{\"interface
 
com.cloud.network.PhysicalNetworkServiceProvider\":\"a6bca386-7a6a-410b-aaa2-fe15c8f422d4\"}","ctxAccountId":"2","uuid":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","cmdEventType":"SERVICE.PROVIDER.UPDATE"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 90520733511963, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null, removed: null}
2021-07-14 16:08:54,393 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] 
(API-Job-Executor-4:ctx-975d9732 job-324) (logid:321ad13e) Executing AsyncJobVO 
{id:324, userId: 2, accountId: 2, instanceType: PhysicalNetworkServiceProvider, 
instanceId: null, cmd: 
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd,
 cmdInfo: 
{"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId":"812","id":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","state":"Enabled","ctxDetails":"{\"interface
 
com.cloud.network.PhysicalNetworkServiceProvider\":\"a6bca386-7a6a-410b-aaa2-fe15c8f422d4\"}","ctxAccountId":"2","uuid":"a6bca386-7a6a-410b-aaa2-fe15c8f422d4","cmdEventType":"SERVICE.PROVIDER.UPDATE"},
 cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: 
null, initMsid: 90520733511963, completeMsid: null, lastUpdated: null, 
lastPolled: null, created: null, removed: null}
2021-07-14 16:08:54,394 DEBUG [c.c.a.ApiServlet] 
(qtp1644231115-6023:ctx-b12d46cd ctx-23ad5938) (logid:4beba9f7) ===END===  
172.16.44.18 -- GET  
id=a6bca386-7a6a-410b-aaa2-fe15c8f422d4=Enabled=updateNetworkServiceProvider=json
2021-07-14 16:08:54,473 DEBUG [c.c.a.ApiServlet] 
(qtp1644231115-6056:ctx-331a4fdf) (logid:c108be52) ===START===  172.16.44.18 -- 
GET  
jobId=321ad13e-d97b-46e8-9e04-25100f52e2b0=queryAsyncJobResult=json
2021-07-14 16:08:54,483 DEBUG [c.c.n.NetworkServiceImpl] 
(API-Job-Executor-4:ctx-975d9732 job-324 ctx-831a584b) (logid:321ad13e) trying 
to update the state of the service provider id=37 on physical network: 206 to 
state: Enabled
2021-07-14 16:08:54,512 DEBUG [c.c.a.ApiServer] 
(qtp1644231115-6056:ctx-331a4fdf ctx-61090299) (logid:c108be52) CIDRs from 
which account 'Acct[f8d6949d-cd74-11eb-b1da-5254008f72d5-admin]' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2021-07-14 16:08:54,556 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-4:ctx-975d9732 job-324) (logid:321ad13e) Unexpected exception 
while executing 
org.apache.cloudstack.api.command.admin.network.UpdateNetworkServiceProviderCmd
com.cloud.utils.exception.CloudRuntimeException: Provider is not ready, cannot 
Enable the 

Re: IPV6 in Isolated/VPC networks

2021-07-14 Thread Hean Seng
Yes, sorry for that, can use NAT 6 also .I mentiioned DHCP6 , and you
can point the gateway to /48 gw, and this does not need any BGP.  Maintain
BGP or OSPF is good, but is a lot more complicated ,

On Wed, Jul 14, 2021 at 10:57 PM Alex Mattioli 
wrote:

> Hi Hean,
> Do you mean using NAT66?  Or did I miss something?
>
> Regards,
> Alex
>
>
>
>
> -Original Message-
> From: Hean Seng 
> Sent: 14 July 2021 16:44
> To: users@cloudstack.apache.org
> Cc: Wido den Hollander ; d...@cloudstack.apache.org; Wei
> Zhou ; Rohit Yadav ;
> Gabriel Beims Bräscher 
> Subject: Re: IPV6 in Isolated/VPC networks
>
> Hi
>
> I replied in another thread, i think do not need implement BGP or OSPF,
> that would be complicated .
>
> We only need assign  IPv6 's /64 prefix to Virtual Router (VR) in NAT
> zone, and the VR responsible to deliver single IPv6 to VM via DHCP6.
>
> In VR, you need to have Default IPv6 route to  Physical Router's /48. IP as
> IPv6 Gateway.  Thens should be done .
>
> Example :
> Physical Router Interface
>  IPv6 IP : 2000:::1/48
>
> Cloudstack  virtual router : 2000::200:201::1/64 with default ipv6
> route to router ip 2000:::1 and Clodustack Virtual router dhcp allocate
> IP to VM , and  VM will have default route to VR. IPv6 2000::200:201::1
>
> So in cloudstack need to allow  user to enter ,  IPv6 gwateway , and the
> /48 Ipv6 prefix , then it will self allocate the /64 ip to the VR , and
> maintain make sure not ovelap allocation
>
>
>
>
>
>
>
> On Wed, Jul 14, 2021 at 8:55 PM Alex Mattioli  >
> wrote:
>
> > Hi Wido,
> > That's pretty much in line with our thoughts, thanks for the input.  I
> > believe we agree on the following points then:
> >
> > - FRR with BGP (no OSPF)
> > - Route /48 (or/56) down to the VR
> > - /64 per network
> > - SLACC for IP addressing
> >
> > I believe the next big question is then "on which level of ACS do we
> > manage AS numbers?".  I see two options:
> > 1) Private AS number on a per-zone basis
> > 2) Root Admin assigned AS number on a domain/account basis
> > 3) End-user driven AS number on a per network basis (for bring your
> > own AS and IP scenario)
> >
> > Thoughts?
> >
> > Cheers
> > Alex
> >
> >
> >
> >
> > -Original Message-
> > From: Wido den Hollander 
> > Sent: 13 July 2021 15:08
> > To: d...@cloudstack.apache.org; Alex Mattioli
> > 
> > Cc: Wei Zhou ; Rohit Yadav <
> > rohit.ya...@shapeblue.com>; Gabriel Beims Bräscher
> > 
> > Subject: Re: IPV6 in Isolated/VPC networks
> >
> >
> >
> > On 7/7/21 1:16 PM, Alex Mattioli wrote:
> > > Hi all,
> > > @Wei Zhou @Rohit Yadav > rohit.ya...@shapeblue.com> and myself are investigating how to enable
> > IPV6 support on Isolated and VPC networks and would like your input on
> it.
> > > At the moment we are looking at implementing FRR with BGP (and
> > > possibly
> > OSPF) on the ACS VR.
> > >
> > > We are looking for requirements, recommendations, ideas, rants,
> > etc...etc...
> > >
> >
> > Ok! Here we go.
> >
> > I think that you mean that the VR will actually route the IPv6 traffic
> > and for that you need to have a way of getting a subnet routed to the VR.
> >
> > BGP is probably you best bet here. Although OSPFv3 technically
> > supports this it is very badly implemented in Frr for example.
> >
> > Now FRR is a very good router and one of the fancy features it
> > supports is BGP Unnumered. This allows for auto configuration of BGP
> > over a L2 network when both sides are sending Router Advertisements.
> > This is very easy for flexible BGP configurations where both sides have
> dynamic IPs.
> >
> > What you want to do is that you get a /56, /48 or something which is
> > >/64 bits routed to the VR.
> >
> > Now you can sub-segment this into separate /64 subnets. You don't want
> > to go smaller then a /64 is that prevents you from using SLAAC for
> > IPv6 address configuration. This is how it works for Shared Networks
> > now in Basic and Advanced Zones.
> >
> > FRR can now also send out the Router Advertisements on the downlinks
> > sending out:
> >
> > - DNS servers
> > - DNS domain
> > - Prefix (/64) to be used
> >
> > There is no need for DHCPv6. You can calculate the IPv6 address the VM
> > will obtain by using the MAC and the prefix.
> >
> > So in short:
> >
> > - Using BGP you routed a /48 to the VR
> > - Now you split this into /64 subnets towards the isolated networks
> >
> > Wido
> >
> > > Alex Mattioli
> > >
> > >
> > >
> > >
> >
> >
>
> --
> Regards,
> Hean Seng
>


-- 
Regards,
Hean Seng


RE: IPV6 in Isolated/VPC networks

2021-07-14 Thread Alex Mattioli
Hi Hean,
Do you mean using NAT66?  Or did I miss something?

Regards,
Alex

 


-Original Message-
From: Hean Seng  
Sent: 14 July 2021 16:44
To: users@cloudstack.apache.org
Cc: Wido den Hollander ; d...@cloudstack.apache.org; Wei Zhou 
; Rohit Yadav ; Gabriel 
Beims Bräscher 
Subject: Re: IPV6 in Isolated/VPC networks

Hi

I replied in another thread, i think do not need implement BGP or OSPF, that 
would be complicated .

We only need assign  IPv6 's /64 prefix to Virtual Router (VR) in NAT zone, and 
the VR responsible to deliver single IPv6 to VM via DHCP6.

In VR, you need to have Default IPv6 route to  Physical Router's /48. IP as
IPv6 Gateway.  Thens should be done .

Example :
Physical Router Interface
 IPv6 IP : 2000:::1/48

Cloudstack  virtual router : 2000::200:201::1/64 with default ipv6 route to 
router ip 2000:::1 and Clodustack Virtual router dhcp allocate IP to VM , 
and  VM will have default route to VR. IPv6 2000::200:201::1

So in cloudstack need to allow  user to enter ,  IPv6 gwateway , and the
/48 Ipv6 prefix , then it will self allocate the /64 ip to the VR , and 
maintain make sure not ovelap allocation







On Wed, Jul 14, 2021 at 8:55 PM Alex Mattioli 
wrote:

> Hi Wido,
> That's pretty much in line with our thoughts, thanks for the input.  I 
> believe we agree on the following points then:
>
> - FRR with BGP (no OSPF)
> - Route /48 (or/56) down to the VR
> - /64 per network
> - SLACC for IP addressing
>
> I believe the next big question is then "on which level of ACS do we 
> manage AS numbers?".  I see two options:
> 1) Private AS number on a per-zone basis
> 2) Root Admin assigned AS number on a domain/account basis
> 3) End-user driven AS number on a per network basis (for bring your 
> own AS and IP scenario)
>
> Thoughts?
>
> Cheers
> Alex
>
>
>
>
> -Original Message-
> From: Wido den Hollander 
> Sent: 13 July 2021 15:08
> To: d...@cloudstack.apache.org; Alex Mattioli 
> 
> Cc: Wei Zhou ; Rohit Yadav < 
> rohit.ya...@shapeblue.com>; Gabriel Beims Bräscher 
> 
> Subject: Re: IPV6 in Isolated/VPC networks
>
>
>
> On 7/7/21 1:16 PM, Alex Mattioli wrote:
> > Hi all,
> > @Wei Zhou @Rohit Yadav rohit.ya...@shapeblue.com> and myself are investigating how to enable
> IPV6 support on Isolated and VPC networks and would like your input on it.
> > At the moment we are looking at implementing FRR with BGP (and 
> > possibly
> OSPF) on the ACS VR.
> >
> > We are looking for requirements, recommendations, ideas, rants,
> etc...etc...
> >
>
> Ok! Here we go.
>
> I think that you mean that the VR will actually route the IPv6 traffic 
> and for that you need to have a way of getting a subnet routed to the VR.
>
> BGP is probably you best bet here. Although OSPFv3 technically 
> supports this it is very badly implemented in Frr for example.
>
> Now FRR is a very good router and one of the fancy features it 
> supports is BGP Unnumered. This allows for auto configuration of BGP 
> over a L2 network when both sides are sending Router Advertisements. 
> This is very easy for flexible BGP configurations where both sides have 
> dynamic IPs.
>
> What you want to do is that you get a /56, /48 or something which is
> >/64 bits routed to the VR.
>
> Now you can sub-segment this into separate /64 subnets. You don't want 
> to go smaller then a /64 is that prevents you from using SLAAC for 
> IPv6 address configuration. This is how it works for Shared Networks 
> now in Basic and Advanced Zones.
>
> FRR can now also send out the Router Advertisements on the downlinks 
> sending out:
>
> - DNS servers
> - DNS domain
> - Prefix (/64) to be used
>
> There is no need for DHCPv6. You can calculate the IPv6 address the VM 
> will obtain by using the MAC and the prefix.
>
> So in short:
>
> - Using BGP you routed a /48 to the VR
> - Now you split this into /64 subnets towards the isolated networks
>
> Wido
>
> > Alex Mattioli
> >
> >
> >
> >
>
>

--
Regards,
Hean Seng


Re: IPV6 in Isolated/VPC networks

2021-07-14 Thread Hean Seng
Hi

I replied in another thread, i think do not need implement BGP or OSPF,
that would be complicated .

We only need assign  IPv6 's /64 prefix to Virtual Router (VR) in NAT zone,
and the VR responsible to deliver single IPv6 to VM via DHCP6.

In VR, you need to have Default IPv6 route to  Physical Router's /48. IP as
IPv6 Gateway.  Thens should be done .

Example :
Physical Router Interface
 IPv6 IP : 2000:::1/48

Cloudstack  virtual router : 2000::200:201::1/64 with default ipv6
route to router ip 2000:::1
and Clodustack Virtual router dhcp allocate IP to VM , and  VM will have
default route to VR. IPv6 2000::200:201::1

So in cloudstack need to allow  user to enter ,  IPv6 gwateway , and the
/48 Ipv6 prefix , then it will self allocate the /64 ip to the VR , and
maintain make sure not ovelap allocation







On Wed, Jul 14, 2021 at 8:55 PM Alex Mattioli 
wrote:

> Hi Wido,
> That's pretty much in line with our thoughts, thanks for the input.  I
> believe we agree on the following points then:
>
> - FRR with BGP (no OSPF)
> - Route /48 (or/56) down to the VR
> - /64 per network
> - SLACC for IP addressing
>
> I believe the next big question is then "on which level of ACS do we
> manage AS numbers?".  I see two options:
> 1) Private AS number on a per-zone basis
> 2) Root Admin assigned AS number on a domain/account basis
> 3) End-user driven AS number on a per network basis (for bring your own AS
> and IP scenario)
>
> Thoughts?
>
> Cheers
> Alex
>
>
>
>
> -Original Message-
> From: Wido den Hollander 
> Sent: 13 July 2021 15:08
> To: d...@cloudstack.apache.org; Alex Mattioli 
> Cc: Wei Zhou ; Rohit Yadav <
> rohit.ya...@shapeblue.com>; Gabriel Beims Bräscher 
> Subject: Re: IPV6 in Isolated/VPC networks
>
>
>
> On 7/7/21 1:16 PM, Alex Mattioli wrote:
> > Hi all,
> > @Wei Zhou @Rohit Yadav rohit.ya...@shapeblue.com> and myself are investigating how to enable
> IPV6 support on Isolated and VPC networks and would like your input on it.
> > At the moment we are looking at implementing FRR with BGP (and possibly
> OSPF) on the ACS VR.
> >
> > We are looking for requirements, recommendations, ideas, rants,
> etc...etc...
> >
>
> Ok! Here we go.
>
> I think that you mean that the VR will actually route the IPv6 traffic and
> for that you need to have a way of getting a subnet routed to the VR.
>
> BGP is probably you best bet here. Although OSPFv3 technically supports
> this it is very badly implemented in Frr for example.
>
> Now FRR is a very good router and one of the fancy features it supports is
> BGP Unnumered. This allows for auto configuration of BGP over a L2 network
> when both sides are sending Router Advertisements. This is very easy for
> flexible BGP configurations where both sides have dynamic IPs.
>
> What you want to do is that you get a /56, /48 or something which is
> >/64 bits routed to the VR.
>
> Now you can sub-segment this into separate /64 subnets. You don't want to
> go smaller then a /64 is that prevents you from using SLAAC for IPv6
> address configuration. This is how it works for Shared Networks now in
> Basic and Advanced Zones.
>
> FRR can now also send out the Router Advertisements on the downlinks
> sending out:
>
> - DNS servers
> - DNS domain
> - Prefix (/64) to be used
>
> There is no need for DHCPv6. You can calculate the IPv6 address the VM
> will obtain by using the MAC and the prefix.
>
> So in short:
>
> - Using BGP you routed a /48 to the VR
> - Now you split this into /64 subnets towards the isolated networks
>
> Wido
>
> > Alex Mattioli
> >
> >
> >
> >
>
>

-- 
Regards,
Hean Seng


Re: CloudStack billing GUI. Is there any one?

2021-07-14 Thread Kalil de Albuquerque Carvalho

Hello all.

Thanks Rafael, I think that will help a lot.

But a need a new help. Where can I change the values of the billing?

I was on Quota Tarrif, try to change the values but it is like it is not 
enabled, nothing happened. Any  one can tell me, or send my any 
documentation where show me how and where can change the tarrif values?


Best regards.


Em 12/07/2021 10:15, Rafael Weingärtner escreveu:

Tu podes utilizar o quota plugin para esse fim :)

On Mon, Jul 12, 2021 at 9:35 AM Kalil de Albuquerque Carvalho 
> wrote:


Hello all.

Studying CloudStack I knew that Usage service has the goal of
create a
billing service. Mi doubt is, because I didn't found, if there is any
GUI that we can use to send to yours "costumers" see and
understand what
they are using and paying for.

Is there any free GUI billing service that I can use with
CloudStack/Usage?

Best regards.



--
Rafael Weingärtner


RE: IPV6 in Isolated/VPC networks

2021-07-14 Thread Alex Mattioli
Hi Wido,
That's pretty much in line with our thoughts, thanks for the input.  I believe 
we agree on the following points then:

- FRR with BGP (no OSPF)
- Route /48 (or/56) down to the VR
- /64 per network
- SLACC for IP addressing

I believe the next big question is then "on which level of ACS do we manage AS 
numbers?".  I see two options:
1) Private AS number on a per-zone basis
2) Root Admin assigned AS number on a domain/account basis
3) End-user driven AS number on a per network basis (for bring your own AS and 
IP scenario)

Thoughts?

Cheers
Alex

 


-Original Message-
From: Wido den Hollander  
Sent: 13 July 2021 15:08
To: d...@cloudstack.apache.org; Alex Mattioli 
Cc: Wei Zhou ; Rohit Yadav ; 
Gabriel Beims Bräscher 
Subject: Re: IPV6 in Isolated/VPC networks



On 7/7/21 1:16 PM, Alex Mattioli wrote:
> Hi all,
> @Wei Zhou @Rohit 
> Yadav and myself are investigating how to 
> enable IPV6 support on Isolated and VPC networks and would like your input on 
> it.
> At the moment we are looking at implementing FRR with BGP (and possibly OSPF) 
> on the ACS VR.
> 
> We are looking for requirements, recommendations, ideas, rants, etc...etc...
> 

Ok! Here we go.

I think that you mean that the VR will actually route the IPv6 traffic and for 
that you need to have a way of getting a subnet routed to the VR.

BGP is probably you best bet here. Although OSPFv3 technically supports this it 
is very badly implemented in Frr for example.

Now FRR is a very good router and one of the fancy features it supports is BGP 
Unnumered. This allows for auto configuration of BGP over a L2 network when 
both sides are sending Router Advertisements. This is very easy for flexible 
BGP configurations where both sides have dynamic IPs.

What you want to do is that you get a /56, /48 or something which is
>/64 bits routed to the VR.

Now you can sub-segment this into separate /64 subnets. You don't want to go 
smaller then a /64 is that prevents you from using SLAAC for IPv6 address 
configuration. This is how it works for Shared Networks now in Basic and 
Advanced Zones.

FRR can now also send out the Router Advertisements on the downlinks sending 
out:

- DNS servers
- DNS domain
- Prefix (/64) to be used

There is no need for DHCPv6. You can calculate the IPv6 address the VM will 
obtain by using the MAC and the prefix.

So in short:

- Using BGP you routed a /48 to the VR
- Now you split this into /64 subnets towards the isolated networks

Wido

> Alex Mattioli
> 
>  
> 
> 



RE: [!!Mass Mail]Re: Extend Public IP Range

2021-07-14 Thread Yordan Kostov
It should not be a problem. Unique IDs in the IP table doesn’t care for the 
order of the IPs they are holding.
I will suggest to fire up 5-10 new test vms just to test how IPs are assigned 
afterwards.

Best regards,
Jordan

-Original Message-
From: Дикевич Евгений Александрович  
Sent: 14 юли 2021 г. 14:46
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range


[X] This message came from outside your organization


Thx.
In mail chain they are extend network from XXX.XXX.XXX.10 - XXX.XXX.XXX.11 ---> 
XXX.XXX.XXX.10 - XXX.XXX.XXX.12 but I want to XXX.XXX.XXX.150 - XXX.XXX.XXX.254 
---> XXX.XXX.XXX.130 - XXX.XXX.XXX.254 (I want to add addresses Before existing 
pool) It's problem for this method or not?

-Original Message-
From: Yordan Kostov [mailto:yord...@nsogroup.com]
Sent: Wednesday, July 14, 2021 2:23 PM
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range

Hey Evgeny,

Check mail chain from June with subject  "Alter Shared Guest Network?" 
it has all you need in terms of DB editing and considerations that should be 
taken under account when editing the DB.

Best regards,
Jordan

-Original Message-
From: Дикевич Евгений Александрович 
Sent: 14 юли 2021 г. 14:11
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range


[X] This message came from outside your organization


HI. Thx for answer.
How I can fix It in DB?

-Original Message-
From: Alexey Samarin [mailto:nrg3...@gmail.com]
Sent: Wednesday, July 14, 2021 1:55 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Extend Public IP Range

 Evgeny, hi!
you can fix it in two ways:
1 - fix it directly in the database (assuming it's not a production system)
2 - try to add another subnet of external addresses

ср, 14 июл. 2021 г. в 13:47, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by>:

> Hi All!
> How I can extend Public IP Range?
> I have network XXX.XXX.XXX.128/25 but when I configured public ip 
> range I made a mistake and used only XXX.XXX.XXX.160  -
> XXX.XXX.XXX.254 I want to use all my addresses.
> How I can correct this?
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются 
> конфиденциальными и предназначены исключительно для использования 
> лицом (лицами), которому (которым) оно предназначено. Если Вы не 
> являетесь лицом (лицами), которому (которым) предназначено это письмо, 
> не копируйте и не разглашайте его содержимое и удалите это сообщение и 
> все вложения из Вашей почтовой системы. Любое несанкционированное 
> использование, распространение, раскрытие, печать или копирование 
> этого электронного письма и прикрепленных к нему файлов, кроме как 
> лицом (лицами) которому (которым) они предназначены, является 
> незаконным и запрещено. Принимая во внимание, что передача данных 
> посредством Интернет не является безопасной, мы не несем никакой 
> ответственности за любой потенциальный ущерб, причиненный в результате 
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> 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 

RE: [!!Mass Mail]Re: Extend Public IP Range

2021-07-14 Thread Дикевич Евгений Александрович
Thx.
In mail chain they are extend network from XXX.XXX.XXX.10 - XXX.XXX.XXX.11 ---> 
XXX.XXX.XXX.10 - XXX.XXX.XXX.12 but I want to XXX.XXX.XXX.150 - XXX.XXX.XXX.254 
---> XXX.XXX.XXX.130 - XXX.XXX.XXX.254 (I want to add addresses Before existing 
pool)
It's problem for this method or not?

-Original Message-
From: Yordan Kostov [mailto:yord...@nsogroup.com] 
Sent: Wednesday, July 14, 2021 2:23 PM
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range

Hey Evgeny,

Check mail chain from June with subject  "Alter Shared Guest Network?" 
it has all you need in terms of DB editing and considerations that should be 
taken under account when editing the DB.

Best regards,
Jordan 

-Original Message-
From: Дикевич Евгений Александрович  
Sent: 14 юли 2021 г. 14:11
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range


[X] This message came from outside your organization


HI. Thx for answer.
How I can fix It in DB?

-Original Message-
From: Alexey Samarin [mailto:nrg3...@gmail.com]
Sent: Wednesday, July 14, 2021 1:55 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Extend Public IP Range

 Evgeny, hi!
you can fix it in two ways:
1 - fix it directly in the database (assuming it's not a production system)
2 - try to add another subnet of external addresses

ср, 14 июл. 2021 г. в 13:47, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by>:

> Hi All!
> How I can extend Public IP Range?
> I have network XXX.XXX.XXX.128/25 but when I configured public ip 
> range I made a mistake and used only XXX.XXX.XXX.160  -
> XXX.XXX.XXX.254 I want to use all my addresses.
> How I can correct this?
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются 
> конфиденциальными и предназначены исключительно для использования 
> лицом (лицами), которому (которым) оно предназначено. Если Вы не 
> являетесь лицом (лицами), которому (которым) предназначено это письмо, 
> не копируйте и не разглашайте его содержимое и удалите это сообщение и 
> все вложения из Вашей почтовой системы. Любое несанкционированное 
> использование, распространение, раскрытие, печать или копирование 
> этого электронного письма и прикрепленных к нему файлов, кроме как 
> лицом (лицами) которому (которым) они предназначены, является 
> незаконным и запрещено. Принимая во внимание, что передача данных 
> посредством Интернет не является безопасной, мы не несем никакой 
> ответственности за любой потенциальный ущерб, причиненный в результате 
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> 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 

RE: XCP-ng HA with cloudstack.

2021-07-14 Thread Yordan Kostov
Hey Abishek,

There is HA for pool and HA for VMs:
- HA for pool should be done this way - 
https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/_xenserver_upg.html?highlight=ha
- to HA a VM do it from cloudstack GUI, it is the ACS that keep track of what 
is up and what is not, instead of the XenServer. 
https://docs.cloudstack.apache.org/en/latest/adminguide/reliability.html#ha-enabled-virtual-machines

Best regards,
Jordan

-Original Message-
From: Abishek Budhathoki  
Sent: 14 юли 2021 г. 14:18
To: users@cloudstack.apache.org
Subject: XCP-ng HA with cloudstack.


[X] This message came from outside your organization


Can we achieve HA in XCP-ng host via cloudstack 4.15.1?
If its posssible I will be very grateful if someone can point me to any kind of 
documentation regarding HA with xcp-ng.

Thank You.



XCP-ng HA with cloudstack.

2021-07-14 Thread Abishek Budhathoki
Can we achieve HA in XCP-ng host via cloudstack 4.15.1?
If its posssible I will be very grateful if someone can point me to any kind of 
documentation regarding HA with xcp-ng.

Thank You.



RE: [!!Mass Mail]Re: Extend Public IP Range

2021-07-14 Thread Yordan Kostov
Hey Evgeny,

Check mail chain from June with subject  "Alter Shared Guest Network?" 
it has all you need in terms of DB editing and considerations that should be 
taken under account when editing the DB.

Best regards,
Jordan 

-Original Message-
From: Дикевич Евгений Александрович  
Sent: 14 юли 2021 г. 14:11
To: users@cloudstack.apache.org
Subject: RE: [!!Mass Mail]Re: Extend Public IP Range


[X] This message came from outside your organization


HI. Thx for answer.
How I can fix It in DB?

-Original Message-
From: Alexey Samarin [mailto:nrg3...@gmail.com]
Sent: Wednesday, July 14, 2021 1:55 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Extend Public IP Range

 Evgeny, hi!
you can fix it in two ways:
1 - fix it directly in the database (assuming it's not a production system)
2 - try to add another subnet of external addresses

ср, 14 июл. 2021 г. в 13:47, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by>:

> Hi All!
> How I can extend Public IP Range?
> I have network XXX.XXX.XXX.128/25 but when I configured public ip 
> range I made a mistake and used only XXX.XXX.XXX.160  -
> XXX.XXX.XXX.254 I want to use all my addresses.
> How I can correct this?
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются 
> конфиденциальными и предназначены исключительно для использования 
> лицом (лицами), которому (которым) оно предназначено. Если Вы не 
> являетесь лицом (лицами), которому (которым) предназначено это письмо, 
> не копируйте и не разглашайте его содержимое и удалите это сообщение и 
> все вложения из Вашей почтовой системы. Любое несанкционированное 
> использование, распространение, раскрытие, печать или копирование 
> этого электронного письма и прикрепленных к нему файлов, кроме как 
> лицом (лицами) которому (которым) они предназначены, является 
> незаконным и запрещено. Принимая во внимание, что передача данных 
> посредством Интернет не является безопасной, мы не несем никакой 
> ответственности за любой потенциальный ущерб, причиненный в результате 
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> 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: Secondary storage doesn't work

2021-07-14 Thread Darrin Hüsselmann
Hi Andy,

I agree with Ed.

The error you are receiving means the Secondary Storage System VM has not 
started and is not in the correct state to download the iso.

Cloudstack needs to start two System VMs for it to be operational, Console 
Proxy VM and Secondary Storage VM. But before it can do that, it needs a 
template to build the VMs from.

You must execute the script from the management server that will upload the 
correct system VM template to your secondary storage first before the SSVM and 
CPVM can be started. Only then will you be able to register an iso.

https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#prepare-the-system-vm-template

You can find the Cloudstack logs under

/var/log/cloudstack/

Regards
Darrin

From: Edward St Pierre 
Sent: Wednesday, July 14, 2021 12:38 PM
To: users@cloudstack.apache.org 
Subject: Re: Secondary storage doesn't work

Hi Andy,

Have you prepared the system VM template?

Ed


 

On Wed, 14 Jul 2021 at 11:32, Andy Nguyen  wrote:

> Short version: identical nfs export for primary and secondary. Primary
> works fine, secondary mounts but doesn't write.
>
> Long version:
> I asked this on reddit
> https://www.reddit.com/r/cloudstack/comments/o8rbsb/secondary_storage_help_please/
> but didn't get much light on the matter.
> Hypervisor host: Alma Linux + QEMU KVM + Cloudstack Agent + nfsd
> Start a VM, also run Alma Linux + Cloudstack Management.
>
> Mount both primary and secondary via the web interface, that completed
> without error.
> Went and add ISO and I got "Request Failed (530) There is no secondary
> storage VM for downloading template to image store Secondary"
>
> I can manually mount the NFS shares and read/write to it from inside the
> VM without problem, so it's clearly not NFS nor permission problem.
>
> Any help on where I may start with troubleshooting? What log should I be
> looking at?
>


RE: [!!Mass Mail]Re: Extend Public IP Range

2021-07-14 Thread Дикевич Евгений Александрович
HI. Thx for answer.
How I can fix It in DB?

-Original Message-
From: Alexey Samarin [mailto:nrg3...@gmail.com]
Sent: Wednesday, July 14, 2021 1:55 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Extend Public IP Range

 Evgeny, hi!
you can fix it in two ways:
1 - fix it directly in the database (assuming it's not a production system)
2 - try to add another subnet of external addresses

ср, 14 июл. 2021 г. в 13:47, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by>:

> Hi All!
> How I can extend Public IP Range?
> I have network XXX.XXX.XXX.128/25 but when I configured public ip
> range I made a mistake and used only XXX.XXX.XXX.160  -
> XXX.XXX.XXX.254 I want to use all my addresses.
> How I can correct this?
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования
> лицом (лицами), которому (которым) оно предназначено. Если Вы не
> являетесь лицом (лицами), которому (которым) предназначено это письмо,
> не копируйте и не разглашайте его содержимое и удалите это сообщение и
> все вложения из Вашей почтовой системы. Любое несанкционированное
> использование, распространение, раскрытие, печать или копирование
> этого электронного письма и прикрепленных к нему файлов, кроме как
> лицом (лицами) которому (которым) они предназначены, является
> незаконным и запрещено. Принимая во внимание, что передача данных
> посредством Интернет не является безопасной, мы не несем никакой
> ответственности за любой потенциальный ущерб, причиненный в результате
> ошибок при передаче данных или этим сообщением и прикрепленными к нему 
> файлами.
>
> 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: Extend Public IP Range

2021-07-14 Thread Alexey Samarin
 Evgeny, hi!
you can fix it in two ways:
1 - fix it directly in the database (assuming it's not a production system)
2 - try to add another subnet of external addresses

ср, 14 июл. 2021 г. в 13:47, Дикевич Евгений Александрович <
evgeniy.dikev...@becloud.by>:

> Hi All!
> How I can extend Public IP Range?
> I have network XXX.XXX.XXX.128/25 but when I configured public ip range I
> made a mistake and used only XXX.XXX.XXX.160  - XXX.XXX.XXX.254
> I want to use all my addresses.
> How I can correct this?
> Внимание!
> Это электронное письмо и все прикрепленные к нему файлы являются
> конфиденциальными и предназначены исключительно для использования лицом
> (лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом
> (лицами), которому (которым) предназначено это письмо, не копируйте и не
> разглашайте его содержимое и удалите это сообщение и все вложения из Вашей
> почтовой системы. Любое несанкционированное использование, распространение,
> раскрытие, печать или копирование этого электронного письма и прикрепленных
> к нему файлов, кроме как лицом (лицами) которому (которым) они
> предназначены, является незаконным и запрещено. Принимая во внимание, что
> передача данных посредством Интернет не является безопасной, мы не несем
> никакой ответственности за любой потенциальный ущерб, причиненный в
> результате ошибок при передаче данных или этим сообщением и прикрепленными
> к нему файлами.
>
> 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.
>


Extend Public IP Range

2021-07-14 Thread Дикевич Евгений Александрович
Hi All!
How I can extend Public IP Range?
I have network XXX.XXX.XXX.128/25 but when I configured public ip range I made 
a mistake and used only XXX.XXX.XXX.160  - XXX.XXX.XXX.254
I want to use all my addresses.
How I can correct this?
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

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: Secondary storage doesn't work

2021-07-14 Thread Edward St Pierre
Hi Andy,

Have you prepared the system VM template?

Ed

On Wed, 14 Jul 2021 at 11:32, Andy Nguyen  wrote:

> Short version: identical nfs export for primary and secondary. Primary
> works fine, secondary mounts but doesn't write.
>
> Long version:
> I asked this on reddit
> https://www.reddit.com/r/cloudstack/comments/o8rbsb/secondary_storage_help_please/
> but didn't get much light on the matter.
> Hypervisor host: Alma Linux + QEMU KVM + Cloudstack Agent + nfsd
> Start a VM, also run Alma Linux + Cloudstack Management.
>
> Mount both primary and secondary via the web interface, that completed
> without error.
> Went and add ISO and I got "Request Failed (530) There is no secondary
> storage VM for downloading template to image store Secondary"
>
> I can manually mount the NFS shares and read/write to it from inside the
> VM without problem, so it's clearly not NFS nor permission problem.
>
> Any help on where I may start with troubleshooting? What log should I be
> looking at?
>


Secondary storage doesn't work

2021-07-14 Thread Andy Nguyen
Short version: identical nfs export for primary and secondary. Primary works 
fine, secondary mounts but doesn't write.

Long version:
I asked this on reddit 
https://www.reddit.com/r/cloudstack/comments/o8rbsb/secondary_storage_help_please/
 but didn't get much light on the matter.
Hypervisor host: Alma Linux + QEMU KVM + Cloudstack Agent + nfsd
Start a VM, also run Alma Linux + Cloudstack Management.

Mount both primary and secondary via the web interface, that completed without 
error.
Went and add ISO and I got "Request Failed (530) There is no secondary storage 
VM for downloading template to image store Secondary"

I can manually mount the NFS shares and read/write to it from inside the VM 
without problem, so it's clearly not NFS nor permission problem.

Any help on where I may start with troubleshooting? What log should I be 
looking at?