Github user milamberspace commented on the issue:
https://github.com/apache/cloudstack/pull/1621
Jira ticket done.
CLOUDSTACK-6671
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fea
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1621
We dont need a PR for master. It will be forward merged.
If you can create a jira ticket for this (even better would be to reuse the
one used in PR1610), it will be useful.
---
If your pr
Github user wido commented on the issue:
https://github.com/apache/cloudstack/pull/1621
LGTM!
Thanks for the fix. Could you also open one for master? It needs to be
fixed there as well.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1621
LGTM thanks @milamberspace
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
r script as part of
> cloudstack upgrade procedure i.e. create backups before start!
>
>
> CloudStack DB Backup Script - Fetching mysql details from db.properties
>
>
>
> #!/bin/bash
> DBNAMES="cloud cloud_usage cloudbridge"
> DATE=$(date +%m%d%y-%H%M%S)
It would be ideal if we can make this or similar script as part of
cloudstack upgrade procedure i.e. create backups before start!
CloudStack DB Backup Script - Fetching mysql details from db.properties
#!/bin/bash
DBNAMES="cloud cloud_usage cloudbridge"
DATE=$(date +%m%d%y-%H%M
5 at 6:28 AM, Laszlo Hornyak
> wrote:
> > Hi,
> >
> > After cloudstack-setup (4.6, latest) I looked into the db.properties file
> > and I have found that the comment lines got mixed into the actual
> content.
> > Anyone met this problem?
> >
> >
Laszlo, I didn't think twice about this but we had that in a prior
version as well. It is not specific to 4.6. Did you upgrade this
environment?
On Fri, Mar 6, 2015 at 6:28 AM, Laszlo Hornyak wrote:
> Hi,
>
> After cloudstack-setup (4.6, latest) I looked into the db.properties fil
Hi,
After cloudstack-setup (4.6, latest) I looked into the db.properties file
and I have found that the comment lines got mixed into the actual content.
Anyone met this problem?
# Licensed to the Apache Software Foundation (ASF) under one
db.usage.maxActive=100
# or more contributor
ed to update the db.properties file to set the db password and host to
something other than localhost.
the host is actually in a env variable.
I can do it with a dirty hack like this:
sed -i "s/db.root.password=/db.root.password=$MYSQL_ENV_MYSQL_ROOT_PASSWORD/"
utils/conf/db.properties
Hi,
I am dockering with cloudstack.
I need to update the db.properties file to set the db password and host to
something other than localhost.
the host is actually in a env variable.
I can do it with a dirty hack like this:
sed -i "s/db.root.password=/db.root.pas
m> wrote:
> Hi Mike,
>
> If when installing your mysql server, you set a password for the mysql
> root user, you will need to specify that here. If you haven't encountered
> errors in your deploydb, you probably haven't set the mysql root user
> password and so you don&
Hi Mike,
If when installing your mysql server, you set a password for the mysql root
user, you will need to specify that here. If you haven't encountered errors in
your deploydb, you probably haven't set the mysql root user password and so you
don't have to change the db.
Hi,
I was looking at my db.properties file and noticed I didn't fill in a value
for the db.root.password key.
Can someone tell me what filling in this value will change behavior wise in
CloudStack?
Thanks!
Mike
# CloudStack database settings
db.cloud.username=cloud
db.cloud.password=
14 matches
Mail list logo
