People aren't required to set up the awsapi, right? Many won't need it.
Just wondering if it should be reflected as optional.
For #2, we should tell them to add the lines to their db.properties, but
also save the example db.properties. I've pushed a commit to save the
example one for RPM installat
@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: Re: [DISCUSS] Upgrade from 4.0 -> 4.1 ( components.xml and
db.propetries)
People aren't required to set up the awsapi, right? Many won't need it.
Just wondering if it should be reflected as optional.
For #2, we should tel
ent: Wednesday, April 03, 2013 10:06 AM
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: RE: [DISCUSS] Upgrade from 4.0 -> 4.1 ( components.xml and
db.propetries)
Yes awsapi is optional. But if someone wants to use the EC2 api query feature
then there is a dependenc
3 10:06 AM
To: dev@cloudstack.apache.org
Cc: cloudstack-...@incubator.apache.org
Subject: RE: [DISCUSS] Upgrade from 4.0 -> 4.1 ( components.xml and
db.propetries)
Yes awsapi is optional. But if someone wants to use the EC2 api query feature
then there is a dependency that db.awsapi.* are se
