Re: Agent LB for CloudStack failed

[Nicolas Vazquez]

Thanks,

I suspect the culprit is the background task trying to reconnect to the 
preferred host (which runs every 60 seconds).

I would suggest disabling the background task by setting the interval to 0. As 
you do not want to change your 'host' global configuration to propagate a new 
list to the agents, you should do it this way:

- Add this line to agent.properties: host.lb.check.interval=0
- Restart the agent

Please let me know if this fixes your issue.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Thursday, July 18, 2019 12:00 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
Subject: 答复: Agent LB for CloudStack failed

Hi Nicolas

test-ceph-node01

[root@test-ceph-node01 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:39:18 CST 2019
workers=5
guest.network.device=br0
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=88ca642a-e319-3369-b2c9-39c2b2bddc7c
public.network.device=br0
cluster=1
local.storage.uuid=ec28176f-a3db-4383-90c8-6dcdbc45c3e0
keystore.passphrase=O8VdcZqBwWMMxwk2
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=1
host=172.17.1.141,172.17.1.142@roundrobin

this is test-ceph-node02

[root@test-ceph-node02 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:58:23 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
guid=649cbe62-dcac-36ae-a62c-699f0e0b8af1
hypervisor.type=kvm
cluster=1
public.network.device=br0
local.storage.uuid=2fc2f796-0614-40cf-bfdf-37a9429520fb
domr.scripts.dir=scripts/network/domr/kvm
keystore.passphrase=vB48rgCk58vNJC6N
host=172.17.1.142,172.17.1.141@roundrobin
LibvirtComputingResource.id=4

test-ceph-node03

[root@test-ceph-node03 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:39:18 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=4d3742c4-8678-3f21-a841-c1ffa32d0a8d
public.network.device=br0
cluster=1
local.storage.uuid=31ee15cf-b3b2-4387-b081-7c47971b9e68
keystore.passphrase=ACgs24DnBgYkORvh
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=5
host=172.17.1.141,172.17.1.142@roundrobin

test-ceph-node04
[root@test-ceph-node04 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:58:22 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=bfd4b7ba-fd5f-365d-b4d8-a6e8e7c78c0c
public.network.device=br0
cluster=1
local.storage.uuid=2d5004ff-37b1-4f66-bff0-e71ac211f1da
keystore.passphrase=r3D4upcAOdWbwE9p
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=6
host=172.17.1.142,172.17.1.141@roundrobin

发件人: Nicolas Vazquez
发送时间: 2019年7月18日 10:56
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: Agent LB for CloudStack failed

Hi Jerry,

I'll request some additional information. Can you provide me with the value 
stored on agent.properties for 'host' property on each KVM host? I suspect that 
the global setting has not been propagated to the agents, as it is trying to 
reconnect instead of connecting to the next management server once it is down.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Monday, July 15, 2019 10:20 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Agent LB for CloudStack failed

Hello everyone

My kvm Agent LB on 4.11.2/4.11.3 failed. When the preferred managment node is 
forced to power off, the agent will not immediately connect to the second 
management node.After 15 minutes, the agent issues a "No route to host" error 
and connects to the second management node.

management node:
acs-mn01,172.17.1.141
acs-mn02,172.17.1.142

mysql db node:
acs-db01

kvmm agent node:
test-ceph-node01
test-ceph-node02
test-ceph-node03
test-ceph-node04


global seting

host=172.17.1.142,172.17.1.141
indirect.agent.lb.algorithm=roundrobin
indirect.agent.lb.check.interval=60


Partial agnet logs:

2019-07-15 23:22:39,340 DEBUG [cloud.agent.Agent] (UgentTask-5:null) (logid:) 
Sending ping: Seq 1-19: { Cmd , MgmtId: -1, via: 1, Ver : v1, Flags: 11, 
[{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_hostVmStateReport":{},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType
 ":"Routing","hostId":1,"wait":0}}] }
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport= 34854] closed on 

答复: Agent LB for CloudStack failed

[li jerry]

Hi Nicolas

test-ceph-node01

[root@test-ceph-node01 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:39:18 CST 2019
workers=5
guest.network.device=br0
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=88ca642a-e319-3369-b2c9-39c2b2bddc7c
public.network.device=br0
cluster=1
local.storage.uuid=ec28176f-a3db-4383-90c8-6dcdbc45c3e0
keystore.passphrase=O8VdcZqBwWMMxwk2
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=1
host=172.17.1.141,172.17.1.142@roundrobin

this is test-ceph-node02

[root@test-ceph-node02 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:58:23 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
guid=649cbe62-dcac-36ae-a62c-699f0e0b8af1
hypervisor.type=kvm
cluster=1
public.network.device=br0
local.storage.uuid=2fc2f796-0614-40cf-bfdf-37a9429520fb
domr.scripts.dir=scripts/network/domr/kvm
keystore.passphrase=vB48rgCk58vNJC6N
host=172.17.1.142,172.17.1.141@roundrobin
LibvirtComputingResource.id=4

test-ceph-node03

[root@test-ceph-node03 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:39:18 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=4d3742c4-8678-3f21-a841-c1ffa32d0a8d
public.network.device=br0
cluster=1
local.storage.uuid=31ee15cf-b3b2-4387-b081-7c47971b9e68
keystore.passphrase=ACgs24DnBgYkORvh
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=5
host=172.17.1.141,172.17.1.142@roundrobin

test-ceph-node04
[root@test-ceph-node04 ~]# cat /etc/cloudstack/agent/agent.properties
#Storage
#Wed Jul 17 10:58:22 CST 2019
guest.network.device=br0
workers=5
private.network.device=br0
port=8250
resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
pod=1
zone=1
hypervisor.type=kvm
guid=bfd4b7ba-fd5f-365d-b4d8-a6e8e7c78c0c
public.network.device=br0
cluster=1
local.storage.uuid=2d5004ff-37b1-4f66-bff0-e71ac211f1da
keystore.passphrase=r3D4upcAOdWbwE9p
domr.scripts.dir=scripts/network/domr/kvm
LibvirtComputingResource.id=6
host=172.17.1.142,172.17.1.141@roundrobin

发件人: Nicolas Vazquez
发送时间: 2019年7月18日 10:56
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: Agent LB for CloudStack failed

Hi Jerry,

I'll request some additional information. Can you provide me with the value 
stored on agent.properties for 'host' property on each KVM host? I suspect that 
the global setting has not been propagated to the agents, as it is trying to 
reconnect instead of connecting to the next management server once it is down.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Monday, July 15, 2019 10:20 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Agent LB for CloudStack failed

Hello everyone

My kvm Agent LB on 4.11.2/4.11.3 failed. When the preferred managment node is 
forced to power off, the agent will not immediately connect to the second 
management node.After 15 minutes, the agent issues a "No route to host" error 
and connects to the second management node.

management node:
acs-mn01,172.17.1.141
acs-mn02,172.17.1.142

mysql db node:
acs-db01

kvmm agent node:
test-ceph-node01
test-ceph-node02
test-ceph-node03
test-ceph-node04


global seting

host=172.17.1.142,172.17.1.141
indirect.agent.lb.algorithm=roundrobin
indirect.agent.lb.check.interval=60


Partial agnet logs:

2019-07-15 23:22:39,340 DEBUG [cloud.agent.Agent] (UgentTask-5:null) (logid:) 
Sending ping: Seq 1-19: { Cmd , MgmtId: -1, via: 1, Ver : v1, Flags: 11, 
[{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_hostVmStateReport":{},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType
 ":"Routing","hostId":1,"wait":0}}] }
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport= 34854] closed on read. Probably 
-1 returned: No route to host
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket 
Socket[addr=/172.17.1.142,port=8250,localport=34854]
2019-07-15 23:23:09,961 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null) 
(logid:a4e4de49) Clearing watch list: 2
2019-07-15 23:23:09,962 INFO [cloud.agent.Agent] (Agent-Handler-4:null) 
(logid:a4e4de49) Lost connection to host: 172.17.1.142. Attempting reconnection 
while we still have 0 commands in Progress.
2019-07-15 23:23:09,963 INFO [utils.nio.NioClient] (Agent-Handler-4:null) 
(logid:a4e4de49) NioClient connection closed
2019-07-15 23:23:09,964 INFO 

Re: Agent LB for CloudStack failed

[Nicolas Vazquez]

Hi Jerry,

I'll request some additional information. Can you provide me with the value 
stored on agent.properties for 'host' property on each KVM host? I suspect that 
the global setting has not been propagated to the agents, as it is trying to 
reconnect instead of connecting to the next management server once it is down.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Monday, July 15, 2019 10:20 PM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: Agent LB for CloudStack failed

Hello everyone

My kvm Agent LB on 4.11.2/4.11.3 failed. When the preferred managment node is 
forced to power off, the agent will not immediately connect to the second 
management node.After 15 minutes, the agent issues a "No route to host" error 
and connects to the second management node.

management node:
acs-mn01,172.17.1.141
acs-mn02,172.17.1.142

mysql db node:
acs-db01

kvmm agent node:
test-ceph-node01
test-ceph-node02
test-ceph-node03
test-ceph-node04


global seting

host=172.17.1.142,172.17.1.141
indirect.agent.lb.algorithm=roundrobin
indirect.agent.lb.check.interval=60


Partial agnet logs:

2019-07-15 23:22:39,340 DEBUG [cloud.agent.Agent] (UgentTask-5:null) (logid:) 
Sending ping: Seq 1-19: { Cmd , MgmtId: -1, via: 1, Ver : v1, Flags: 11, 
[{"com.cloud.agent.api.PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_hostVmStateReport":{},"_gatewayAccessible":true,"_vnetAccessible":true,"hostType
 ":"Routing","hostId":1,"wait":0}}] }
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport= 34854] closed on read. Probably 
-1 returned: No route to host
2019-07-15 23:23:09,960 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket 
Socket[addr=/172.17.1.142,port=8250,localport=34854]
2019-07-15 23:23:09,961 DEBUG [cloud.agent.Agent] (Agent-Handler-4:null) 
(logid:a4e4de49) Clearing watch list: 2
2019-07-15 23:23:09,962 INFO [cloud.agent.Agent] (Agent-Handler-4:null) 
(logid:a4e4de49) Lost connection to host: 172.17.1.142. Attempting reconnection 
while we still have 0 commands in Progress.
2019-07-15 23:23:09,963 INFO [utils.nio.NioClient] (Agent-Handler-4:null) 
(logid:a4e4de49) NioClient connection closed
2019-07-15 23:23:09,964 INFO [cloud.agent.Agent] (Agent-Handler-4:null) 
(logid:a4e4de49) Reconnecting to host:172.17.1.142
2019-07-15 23:23:09,964 INFO [utils.nio.NioClient] (Agent-Handler-4:null) 
(logid:a4e4de49) Connecting to 172.17.1.142:8250
2019-07-15 23:23:12,972 ERROR [utils.nio.NioConnection] (Agent-Handler-4:null) 
(logid:a4e4de49) Unable to initialize the threads.
java.net.NoRouteToHostException: No route to host
 At sun.nio.ch.Net.connect0(Native Method)
 At sun.nio.ch.Net.connect(Net.java:454)
 At sun.nio.ch.Net.connect(Net.java:446)
 At sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
 At com.cloud.utils.nio.NioClient.init(NioClient.java:56)
 At com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
 At com.cloud.agent.Agent.reconnect(Agent.java:517)
 At com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1091)
 At com.clo

nicolas.vazq...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

[GitHub] [cloudstack-documentation] PaulAngus commented on a change in pull request #55: Network offering scopes

[GitBox]

PaulAngus commented on a change in pull request #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#discussion_r304547130
 
 

 ##
 File path: source/adminguide/networking.rst
 ##
 @@ -422,5 +421,20 @@ To create a network offering:
   this case, when you configure an egress rules for an isolated
   guest network, rules are added to allow the specified traffic.
 
+- **Public**: Indicate whether the network offering should be available to
 
 Review comment:
   formatting fixed


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #55: Network offering scopes

[GitBox]

ACSGitBot commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512401814
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr55
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #55: Network offering scopes

[GitBox]

ACSGitBot commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512398437
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] PaulAngus commented on issue #55: Network offering scopes

[GitBox]

PaulAngus commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512398243
 
 
   request docbuild
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [ANNOUNCE] Andrija Panic has joined the PMC

[Simon Weller]

Congrats Andrija!!


From: Paul Angus 
Sent: Saturday, July 13, 2019 10:02 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; 
priv...@cloudstack.apache.org
Subject: [ANNOUNCE] Andrija Panic has joined the PMC

Fellow CloudStackers,



It gives me great pleasure to say that Adrija has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Andrija!




Kind regards,



Paul Angus

CloudStack PMC

Re: [ANNOUNCE] Sven Vogel has joined the PMC

[Simon Weller]

Congrats Sven!


From: Boris Stoyanov 
Sent: Tuesday, July 16, 2019 2:08 AM
To: us...@cloudstack.apache.org; priv...@cloudstack.apache.org; 
dev@cloudstack.apache.org
Subject: Re: [ANNOUNCE] Sven Vogel has joined the PMC

Congrats Sven!

On 13.07.19, 18:45, "Paul Angus"  wrote:

Fellow CloudStackers,



It gives me great pleasure to say that Sven has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC



boris.stoya...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

[Simon Weller]

Congrats Gabriel!


From: Paul Angus 
Sent: Saturday, July 13, 2019 11:00 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; 
priv...@cloudstack.apache.org
Subject: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

Fellow CloudStackers,


Its non-stop today!



It gives me great pleasure to say that Gabriel has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC

Re: [ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

[Simon Weller]

Congrats Bobby!!



From: Paul Angus 
Sent: Tuesday, July 16, 2019 4:12 AM
To: priv...@cloudstack.apache.org; dev@cloudstack.apache.org; 
us...@cloudstack.apache.org
Subject: [ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

Fellow CloudStackers,



It gives me great pleasure to say that Bobby has been invited to join the
PMC and has gracefully accepted.



Please join me in congratulating  Bobby!





Kind regards,





Paul Angus

CloudStack PMC

Re: Using S3/Minio as the only secondary storage

[Will Stevens]

If Syed can't fill in the blanks sufficiently for you when you talk to him
later today, let me know and I will set up a call and loop in the team on
our side who have more details and we can walk through our experience and
knowledge on the topic.

Cheers,

*Will Stevens*
Chief Technology Officer
c 514.826.0190




On Wed, Jul 17, 2019 at 9:30 AM Jean-Francois Nadeau 
wrote:

> Thanks Will,
>
> I remember having the discussion with Pierre-Luc on his use of Swift for
> templates.  I was curious about the differences on S3 vs Swift for SS since
> looking at the CS UI when it comes to setting up an S3 image store... the
> NFS staging is optional.  And this make sense to me if your object storage
> is fast and accessible locally,  why the need for staging/caching.The
> documentation could mention if it is possible to use S3 secondary and
> nothing else,  starting with if SSVM templates can be uploaded to a
> bucket.I will certainly ask Syed later today :)
>
> best
>
> Jfn
>
> On Wed, Jul 17, 2019 at 6:59 AM Will Stevens 
> wrote:
>
> > Hey JF,
> > We use the Swift object store as the storage backend for secondary
> > storage.  I have not tried the S3 integration, but the last time I looked
> > at the code for this (admittedly, a long time ago) the Swift and s3 logic
> > was more intertwined than I liked. The CloudOps/cloud.ca team had to do
> a
> > lot of work to get the Swift integration to a reasonable working state. I
> > believe all of our changes have been upstreamed quite some time ago. I
> > don't know if anyone is doing this for the S3 implementation.
> >
> > I can't speak to the S3 implementation because I have not looked at it
> in a
> > very long time, but the Swift implementation requires a "temporary NFS
> > staging area" that essentially acts kind of like a buffer between the
> > object store and primary storage when templates and such are used by the
> > hosts.
> >
> > I think Pierre-Luc and Syed have a clearer picture of all the moving
> > pieces, but that is a quick summary of what I know without digging in.
> >
> > Hope that helps.
> >
> > Cheers,
> >
> > Will
> >
> > On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau <
> > the.jfnad...@gmail.com>
> > wrote:
> >
> > > Hello Everyone,
> > >
> > > I was wondering if it was common or even recommended to use an S3
> > > compatible storage system as the only secondary storage provider ?
> > >
> > > The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1
> storage
> > > solution also provides an S3 compatible object store (apparently Minio
> > > under the hood).
> > >
> > > I have always used NFS to install the SSVM templates and the install
> > script
> > > (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> > > would I proceed with S3 only storage ?
> > >
> > > best,
> > >
> > > Jean-Francois
> > >
> >
>

Re: Using S3/Minio as the only secondary storage

[Jean-Francois Nadeau]

Thanks Will,

I remember having the discussion with Pierre-Luc on his use of Swift for
templates.  I was curious about the differences on S3 vs Swift for SS since
looking at the CS UI when it comes to setting up an S3 image store... the
NFS staging is optional.  And this make sense to me if your object storage
is fast and accessible locally,  why the need for staging/caching.The
documentation could mention if it is possible to use S3 secondary and
nothing else,  starting with if SSVM templates can be uploaded to a
bucket.I will certainly ask Syed later today :)

best

Jfn

On Wed, Jul 17, 2019 at 6:59 AM Will Stevens  wrote:

> Hey JF,
> We use the Swift object store as the storage backend for secondary
> storage.  I have not tried the S3 integration, but the last time I looked
> at the code for this (admittedly, a long time ago) the Swift and s3 logic
> was more intertwined than I liked. The CloudOps/cloud.ca team had to do a
> lot of work to get the Swift integration to a reasonable working state. I
> believe all of our changes have been upstreamed quite some time ago. I
> don't know if anyone is doing this for the S3 implementation.
>
> I can't speak to the S3 implementation because I have not looked at it in a
> very long time, but the Swift implementation requires a "temporary NFS
> staging area" that essentially acts kind of like a buffer between the
> object store and primary storage when templates and such are used by the
> hosts.
>
> I think Pierre-Luc and Syed have a clearer picture of all the moving
> pieces, but that is a quick summary of what I know without digging in.
>
> Hope that helps.
>
> Cheers,
>
> Will
>
> On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau <
> the.jfnad...@gmail.com>
> wrote:
>
> > Hello Everyone,
> >
> > I was wondering if it was common or even recommended to use an S3
> > compatible storage system as the only secondary storage provider ?
> >
> > The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1 storage
> > solution also provides an S3 compatible object store (apparently Minio
> > under the hood).
> >
> > I have always used NFS to install the SSVM templates and the install
> script
> > (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> > would I proceed with S3 only storage ?
> >
> > best,
> >
> > Jean-Francois
> >
>

Re: Using S3/Minio as the only secondary storage

[Will Stevens]

Hey JF,
We use the Swift object store as the storage backend for secondary
storage.  I have not tried the S3 integration, but the last time I looked
at the code for this (admittedly, a long time ago) the Swift and s3 logic
was more intertwined than I liked. The CloudOps/cloud.ca team had to do a
lot of work to get the Swift integration to a reasonable working state. I
believe all of our changes have been upstreamed quite some time ago. I
don't know if anyone is doing this for the S3 implementation.

I can't speak to the S3 implementation because I have not looked at it in a
very long time, but the Swift implementation requires a "temporary NFS
staging area" that essentially acts kind of like a buffer between the
object store and primary storage when templates and such are used by the
hosts.

I think Pierre-Luc and Syed have a clearer picture of all the moving
pieces, but that is a quick summary of what I know without digging in.

Hope that helps.

Cheers,

Will

On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau 
wrote:

> Hello Everyone,
>
> I was wondering if it was common or even recommended to use an S3
> compatible storage system as the only secondary storage provider ?
>
> The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1 storage
> solution also provides an S3 compatible object store (apparently Minio
> under the hood).
>
> I have always used NFS to install the SSVM templates and the install script
> (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> would I proceed with S3 only storage ?
>
> best,
>
> Jean-Francois
>

[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #55: Network offering scopes

[GitBox]

ACSGitBot commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512198137
 
 
   Build finished.  You can review it at:   
https://acs-www.shapeblue.com/docs/pr55
   
   Build Log Output:
   
   
   No log errors found to report.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] ACSGitBot commented on issue #55: Network offering scopes

[GitBox]

ACSGitBot commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512197678
 
 
   Your request had been received, i'll go and build the documentation and 
check the output log for errors.
   
   This shouldn't take long.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] PaulAngus commented on issue #55: Network offering scopes

[GitBox]

PaulAngus commented on issue #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#issuecomment-512197655
 
 
   request docbuild
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] PaulAngus merged pull request #53: Constrained custom offerings update for 4.13

[GitBox]

PaulAngus merged pull request #53: Constrained custom offerings update for 4.13
URL: https://github.com/apache/cloudstack-documentation/pull/53
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Using S3/Minio as the only secondary storage

[Riepl, Gregor (SWISS TXT)]

Hi Jean-François

> I have always used NFS to install the SSVM templates and the install
> script (cloud-install-sys-tmplt) only takes a mount point.  How, if
> possible, would I proceed with S3 only storage ?

CloudStack doesn't support object storage as a backend for the
secondary storage. You'd have to use something like s3fs-fuse[1],
ObjectiveFS[2] or RioFS[3].

But I have no idea how well that will work... Take into consideration
that secondary storage will be mounted on at least the Management
Server and the SSVMs.

I think NFS is your only option for now.
What you can do, however, is mounting the S3 object store on one
machine and exporting it as an NFS share to the other hosts.

Regards,
Gregor

[1] https://github.com/s3fs-fuse/s3fs-fuse
[2] https://objectivefs.com/
[3] https://github.com/skoobe/riofs

[GitHub] [cloudstack-documentation] PaulAngus commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

PaulAngus commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304282304
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -69,14 +74,20 @@ available offerings when they create a new VM. Based on 
the user’s
 selected offering, CloudStack emits usage records that can be integrated
 with billing systems.
 
-Some characteristics of service offerings must be defined by the CloudStack
-administrator, and others can be left undefined so that the end-user can
-enter their own desired values. This is useful to reduce the number of
-offerings the CloudStack administrator has to define. Instead of defining a
-compute offering for every imaginable combination of values that a user
+Compute offerings may be "fixed", "custom constrained" or "custom 
unconstrained".
+
+In fixed offering the Number of CPUs, Memory and CPU frequecy in each service
+offerings are predefined by the CloudStack administrator, in custom 
unconstrained
+offerings they are left undefined so that the end-user can enter their own 
desired
+values when creating a guest instance. Since 4.13 custom constrained offerings 
have
+been introduced to allow the end-user to enter the number of CPUs and memory
+required within constraints set by the administrator.  The constraints can be 
 
 Review comment:
   a double space after a full stop is the 'proper' way to write.  but a lot of 
markup languages were written by Americans [TIC] so they ignore them.  - please 
send any complaints to:
   The Queen
   England.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] PaulAngus commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

PaulAngus commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304281266
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -169,65 +163,75 @@ To create a new compute offering:
   system VM is running. Shared allocates from storage accessible via
   NFS.
 
-   -  **Custom**: Custom compute offerings can be used in following
-  cases: deploying a VM, changing the compute offering of a stopped
-  VM and running VMs, which is nothing but scaling up.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+  Local
 
-  If the Custom field is checked, the end-user must fill in the
-  desired values for number of CPU, CPU speed, and RAM Memory when
-  using a custom compute offering. When you check this box, those
-  three input fields are hidden in the dialog box.
+
+   -  **Compute Offering Type**: The amount of freedom that the end user
+  has to customise the compute power that their instance has when using 
this
+  compute offering.  The options are; Fixed offering - user has no 
+  ability to customise, Custom constrained - user has some latitude
+  to customise the compute within parameters set by the offering, 
+  Custom unconstrained - user can set any values that they wish.
+  'Custom constrained' is recommended over 'Custom unconstrained'
+  
 
-  **# of CPU cores**: The number of cores which should be allocated
-  to a system VM with this offering. If Custom is checked, this
-  field does not appear.
+  to a system VM with this offering. If 'Custom unconstrained' is checked, 
this
+  field does not appear. If 'Custom constrained' is checked, the admin will
+  be asked to enter the minimum and maximum number of CPUs that a user
+  can request.
 
-   -  **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+   -  **CPU (in MHz)**: The CPU speed of the cores that the guest instance is
   allocated. For example, “2000” would provide for a 2 GHz clock. If
-  Custom is checked, this field does not appear.
+  Custom is checked, this field does not appear (only enforced if CPU 
+  cap is selected).  This value is also used as a share value to give VMs
+  relative priority when a hypervisor host is over-provisioned.
 
-  **Memory (in MB)**: The amount of memory in megabytes that the
   system VM should be allocated. For example, “2048” would provide
-  for a 2 GB RAM allocation. If Custom is checked, this field does
-  not appear.
+  for a 2 GB RAM allocation. If 'Custom unconstrained' is checked, this 
field does
 
 Review comment:
   done


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] PaulAngus commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

PaulAngus commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304281218
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -169,65 +163,75 @@ To create a new compute offering:
   system VM is running. Shared allocates from storage accessible via
   NFS.
 
-   -  **Custom**: Custom compute offerings can be used in following
-  cases: deploying a VM, changing the compute offering of a stopped
-  VM and running VMs, which is nothing but scaling up.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+  Local
 
-  If the Custom field is checked, the end-user must fill in the
-  desired values for number of CPU, CPU speed, and RAM Memory when
-  using a custom compute offering. When you check this box, those
-  three input fields are hidden in the dialog box.
+
+   -  **Compute Offering Type**: The amount of freedom that the end user
+  has to customise the compute power that their instance has when using 
this
+  compute offering.  The options are; Fixed offering - user has no 
+  ability to customise, Custom constrained - user has some latitude
+  to customise the compute within parameters set by the offering, 
+  Custom unconstrained - user can set any values that they wish.
+  'Custom constrained' is recommended over 'Custom unconstrained'
+  
 
-  **# of CPU cores**: The number of cores which should be allocated
-  to a system VM with this offering. If Custom is checked, this
-  field does not appear.
+  to a system VM with this offering. If 'Custom unconstrained' is checked, 
this
+  field does not appear. If 'Custom constrained' is checked, the admin will
+  be asked to enter the minimum and maximum number of CPUs that a user
+  can request.
 
-   -  **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+   -  **CPU (in MHz)**: The CPU speed of the cores that the guest instance is
   allocated. For example, “2000” would provide for a 2 GHz clock. If
-  Custom is checked, this field does not appear.
+  Custom is checked, this field does not appear (only enforced if CPU 
 
 Review comment:
   done


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304263336
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -169,65 +163,75 @@ To create a new compute offering:
   system VM is running. Shared allocates from storage accessible via
   NFS.
 
-   -  **Custom**: Custom compute offerings can be used in following
-  cases: deploying a VM, changing the compute offering of a stopped
-  VM and running VMs, which is nothing but scaling up.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+  Local
 
-  If the Custom field is checked, the end-user must fill in the
-  desired values for number of CPU, CPU speed, and RAM Memory when
-  using a custom compute offering. When you check this box, those
-  three input fields are hidden in the dialog box.
+
+   -  **Compute Offering Type**: The amount of freedom that the end user
+  has to customise the compute power that their instance has when using 
this
+  compute offering.  The options are; Fixed offering - user has no 
+  ability to customise, Custom constrained - user has some latitude
+  to customise the compute within parameters set by the offering, 
+  Custom unconstrained - user can set any values that they wish.
+  'Custom constrained' is recommended over 'Custom unconstrained'
+  
 
-  **# of CPU cores**: The number of cores which should be allocated
-  to a system VM with this offering. If Custom is checked, this
-  field does not appear.
+  to a system VM with this offering. If 'Custom unconstrained' is checked, 
this
+  field does not appear. If 'Custom constrained' is checked, the admin will
+  be asked to enter the minimum and maximum number of CPUs that a user
+  can request.
 
-   -  **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+   -  **CPU (in MHz)**: The CPU speed of the cores that the guest instance is
   allocated. For example, “2000” would provide for a 2 GHz clock. If
-  Custom is checked, this field does not appear.
+  Custom is checked, this field does not appear (only enforced if CPU 
 
 Review comment:
   `If 'Custom constrained' or 'Custom unconstrained'` will be better to avoid 
confusion.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304263336
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -169,65 +163,75 @@ To create a new compute offering:
   system VM is running. Shared allocates from storage accessible via
   NFS.
 
-   -  **Custom**: Custom compute offerings can be used in following
-  cases: deploying a VM, changing the compute offering of a stopped
-  VM and running VMs, which is nothing but scaling up.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+  Local
 
-  If the Custom field is checked, the end-user must fill in the
-  desired values for number of CPU, CPU speed, and RAM Memory when
-  using a custom compute offering. When you check this box, those
-  three input fields are hidden in the dialog box.
+
+   -  **Compute Offering Type**: The amount of freedom that the end user
+  has to customise the compute power that their instance has when using 
this
+  compute offering.  The options are; Fixed offering - user has no 
+  ability to customise, Custom constrained - user has some latitude
+  to customise the compute within parameters set by the offering, 
+  Custom unconstrained - user can set any values that they wish.
+  'Custom constrained' is recommended over 'Custom unconstrained'
+  
 
-  **# of CPU cores**: The number of cores which should be allocated
-  to a system VM with this offering. If Custom is checked, this
-  field does not appear.
+  to a system VM with this offering. If 'Custom unconstrained' is checked, 
this
+  field does not appear. If 'Custom constrained' is checked, the admin will
+  be asked to enter the minimum and maximum number of CPUs that a user
+  can request.
 
-   -  **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+   -  **CPU (in MHz)**: The CPU speed of the cores that the guest instance is
   allocated. For example, “2000” would provide for a 2 GHz clock. If
-  Custom is checked, this field does not appear.
+  Custom is checked, this field does not appear (only enforced if CPU 
 
 Review comment:
   `If 'Custom constrained' or 'Custom unconstrained'` will be better to avoid 
confusion,


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304262516
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -169,65 +163,75 @@ To create a new compute offering:
   system VM is running. Shared allocates from storage accessible via
   NFS.
 
-   -  **Custom**: Custom compute offerings can be used in following
-  cases: deploying a VM, changing the compute offering of a stopped
-  VM and running VMs, which is nothing but scaling up.
+   -  **Provisioning type**: The type of disk that should be allocated. 
+  Local
 
-  If the Custom field is checked, the end-user must fill in the
-  desired values for number of CPU, CPU speed, and RAM Memory when
-  using a custom compute offering. When you check this box, those
-  three input fields are hidden in the dialog box.
+
+   -  **Compute Offering Type**: The amount of freedom that the end user
+  has to customise the compute power that their instance has when using 
this
+  compute offering.  The options are; Fixed offering - user has no 
+  ability to customise, Custom constrained - user has some latitude
+  to customise the compute within parameters set by the offering, 
+  Custom unconstrained - user can set any values that they wish.
+  'Custom constrained' is recommended over 'Custom unconstrained'
+  
 
-  **# of CPU cores**: The number of cores which should be allocated
-  to a system VM with this offering. If Custom is checked, this
-  field does not appear.
+  to a system VM with this offering. If 'Custom unconstrained' is checked, 
this
+  field does not appear. If 'Custom constrained' is checked, the admin will
+  be asked to enter the minimum and maximum number of CPUs that a user
+  can request.
 
-   -  **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+   -  **CPU (in MHz)**: The CPU speed of the cores that the guest instance is
   allocated. For example, “2000” would provide for a 2 GHz clock. If
-  Custom is checked, this field does not appear.
+  Custom is checked, this field does not appear (only enforced if CPU 
+  cap is selected).  This value is also used as a share value to give VMs
+  relative priority when a hypervisor host is over-provisioned.
 
-  **Memory (in MB)**: The amount of memory in megabytes that the
   system VM should be allocated. For example, “2048” would provide
-  for a 2 GB RAM allocation. If Custom is checked, this field does
-  not appear.
+  for a 2 GB RAM allocation. If 'Custom unconstrained' is checked, this 
field does
 
 Review comment:
   Should we have selected instead of checked,
   `If 'Custom unconstrained' offering type is selected`


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304259986
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -69,14 +74,20 @@ available offerings when they create a new VM. Based on 
the user’s
 selected offering, CloudStack emits usage records that can be integrated
 with billing systems.
 
-Some characteristics of service offerings must be defined by the CloudStack
-administrator, and others can be left undefined so that the end-user can
-enter their own desired values. This is useful to reduce the number of
-offerings the CloudStack administrator has to define. Instead of defining a
-compute offering for every imaginable combination of values that a user
+Compute offerings may be "fixed", "custom constrained" or "custom 
unconstrained".
+
+In fixed offering the Number of CPUs, Memory and CPU frequecy in each service
+offerings are predefined by the CloudStack administrator, in custom 
unconstrained
+offerings they are left undefined so that the end-user can enter their own 
desired
+values when creating a guest instance. Since 4.13 custom constrained offerings 
have
+been introduced to allow the end-user to enter the number of CPUs and memory
+required within constraints set by the administrator.  The constraints can be 
 
 Review comment:
   Double space here, `administrator.  The constraints`. Also in the line below.
   Although not showing in the docs html


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304259986
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -69,14 +74,20 @@ available offerings when they create a new VM. Based on 
the user’s
 selected offering, CloudStack emits usage records that can be integrated
 with billing systems.
 
-Some characteristics of service offerings must be defined by the CloudStack
-administrator, and others can be left undefined so that the end-user can
-enter their own desired values. This is useful to reduce the number of
-offerings the CloudStack administrator has to define. Instead of defining a
-compute offering for every imaginable combination of values that a user
+Compute offerings may be "fixed", "custom constrained" or "custom 
unconstrained".
+
+In fixed offering the Number of CPUs, Memory and CPU frequecy in each service
+offerings are predefined by the CloudStack administrator, in custom 
unconstrained
+offerings they are left undefined so that the end-user can enter their own 
desired
+values when creating a guest instance. Since 4.13 custom constrained offerings 
have
+been introduced to allow the end-user to enter the number of CPUs and memory
+required within constraints set by the administrator.  The constraints can be 
 
 Review comment:
   Double space here, `administrator.  The constraints`. Also in the line below.
   Although not showing in the docs html


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #53: Constrained custom offerings update for 4.13

[GitBox]

shwstppr commented on a change in pull request #53: Constrained custom 
offerings update for 4.13
URL: 
https://github.com/apache/cloudstack-documentation/pull/53#discussion_r304259986
 
 

 ##
 File path: source/adminguide/service_offerings.rst
 ##
 @@ -69,14 +74,20 @@ available offerings when they create a new VM. Based on 
the user’s
 selected offering, CloudStack emits usage records that can be integrated
 with billing systems.
 
-Some characteristics of service offerings must be defined by the CloudStack
-administrator, and others can be left undefined so that the end-user can
-enter their own desired values. This is useful to reduce the number of
-offerings the CloudStack administrator has to define. Instead of defining a
-compute offering for every imaginable combination of values that a user
+Compute offerings may be "fixed", "custom constrained" or "custom 
unconstrained".
+
+In fixed offering the Number of CPUs, Memory and CPU frequecy in each service
+offerings are predefined by the CloudStack administrator, in custom 
unconstrained
+offerings they are left undefined so that the end-user can enter their own 
desired
+values when creating a guest instance. Since 4.13 custom constrained offerings 
have
+been introduced to allow the end-user to enter the number of CPUs and memory
+required within constraints set by the administrator.  The constraints can be 
 
 Review comment:
   Double space here, `administrator.   The constraints`. Also in the line 
below.
   Although not showing in the docs html


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [cloudstack-documentation] shwstppr commented on a change in pull request #55: Network offering scopes

[GitBox]

shwstppr commented on a change in pull request #55: Network offering scopes
URL: 
https://github.com/apache/cloudstack-documentation/pull/55#discussion_r304257341
 
 

 ##
 File path: source/adminguide/networking.rst
 ##
 @@ -422,5 +421,20 @@ To create a network offering:
   this case, when you configure an egress rules for an isolated
   guest network, rules are added to allow the specified traffic.
 
+- **Public**: Indicate whether the network offering should be available to
 
 Review comment:
   Some formatting issue here?
   ![Screenshot from 2019-07-17 
13-03-15](https://user-images.githubusercontent.com/153340/61356122-4e5eb800-a893-11e9-99b1-07880623955c.png)
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services