i think the issue he is mentioning is that you can use the GUI to set the
password to "", but that doesn't actually unset the password in the
application.
John
=:->
On Wed, Mar 26, 2014 at 9:33 PM, Richard Harding wrote:
> On Wed, 26 Mar 2014, Anant wrote:
>
> > Hello Everyone,
> >
> > I am ne
You got me right John, I am saying the same. It allows me to set
password "" , but that doesn't actually unset the password in the
application.
On Thursday 27 March 2014 12:55 PM, John Meinel wrote:
you can
--
Anant Saraswat
System Admin (RHCVA,RHCE,RHCSA)
FOR AND ON BEHALF OF:
Techblue So
>From the log file
1. ==> /var/log/apache2/proxy-server <==
2. [Wed Mar 26 23:41:28 2014] [error] [client x.x.x.x] Requested
content-length of 9223372036854775807 is larger than the configured limit
of 5368709122
9223372036854775807 is MAX_INT for an int64 value
Further down in tha
On 27/03/14 14:51, Stuart Bishop wrote:
> Correct. I think you are just fine with one relation per database and
> using the generated credentials, and using the granted roles to
> control database permissions.
As a sanity test - would per-relation config be useful in this scenario?
Mark
--
Juju
Anant,
Juju by design does not enforce parameter changes. It's basically up to the
charm writer to apply the change or silently ignore it. Juju, and hence the
GUI, will accept the change and store it regardless.
Since juju has no notion of "read-only" parameters, it's the charm writer's job
to
On 27/03/14 16:54, Sameer Zeidat wrote:
> Juju by design does not enforce parameter changes. It's basically up
> to the charm writer to apply the change or silently ignore it. Juju,
> and hence the GUI, will accept the change and store it regardless.
>
> Since juju has no notion of "read-only" para
On 27 March 2014 15:33, Mark Shuttleworth wrote:
> On 27/03/14 14:51, Stuart Bishop wrote:
>> Correct. I think you are just fine with one relation per database and
>> using the generated credentials, and using the granted roles to
>> control database permissions.
>
> As a sanity test - would per-r
On Thu, Mar 27, 2014 at 3:51 AM, Stuart Bishop
wrote:
>> In effect it looks like I don't need to share the credentials among
>> the services?
>
> Correct. I think you are just fine with one relation per database and
> using the generated credentials, and using the granted roles to
> control databa
On 27 March 2014 19:13, Andreas Hasenack wrote:
> On Thu, Mar 27, 2014 at 3:51 AM, Stuart Bishop
> wrote:
>>> In effect it looks like I don't need to share the credentials among
>>> the services?
>>
>> Correct. I think you are just fine with one relation per database and
>> using the generated cr
On Thu, Mar 27, 2014 at 11:37 AM, Stuart Bishop
wrote:
> I've just looked at the code, and if you are using a db-admin relation
> you can already connect to any database as any user. You can connect
> using the credentials you are given and create the additional users
> you need in the db-admin-re
juju-core 1.17.7
A new development release of Juju, juju-core 1.17.7, is now available.
Getting Juju
juju-core 1.17.7 is available for trusty and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Upgrading from stable releases to development rele
This has been a focus of the charm audit that we have been performing.
Charms are getting flagged for a multitude of reasons that include:
- immutable configuration parameters
- ppa's that don't adopt trusty support
- general practices we would want to see changed.
All these findings
And after further reading I realized I scanned the last few emails on the
thread and did not read the thread originators core problem they wanted to
solve.
I apologize for my haste in response, and will graciously remove myself
from the conversation.
On Thu, Mar 27, 2014 at 7:15 PM, Charles Bu
Hey David! thanks for the tips.
I did another search trying to find something about this or someone else
having this problem, but nothing founded yet.
The strange thing is that I can upload through the command line, so must be
related only with the proxy server, right?
So now Im going to log capt
Hi juju community,
I hit en error when using juju plus OpenStack provider, below is the
environment and what I found, please give me a help to let me move on.
OpenStackļ¼ Havana(deployed with devstack)
juju : 1.16.6-precise-amd64
swift works well:
ubuntu@havana:~$ swift list
dfc9e845-
Hey Hui! I'm struggling with problems between Juju and Openstack too,
there's a thread already with almost the same subject, search for
"Openstack and Juju not working", jump in! :)
Abs,
Sebas.
2014-03-28 1:24 GMT-03:00 Hui Xiang :
> Hi juju community,
>
> I hit en error when using juju plus
Hi Sebastian,
I have seen your thread "Openstack and Juju not working", but my swift is
working, seems your swift is ill? so I am a little hesitate to put my error
with yours together, I am afraid to make them confused, thoughts ? : )
Regards.
Hui.
On Fri, Mar 28, 2014 at 12:28 PM, Sebastian
Hey Sebas,
Can you use the command of "swift list"?
At lease now I have the swift result as below, check yours, and you can
move on and help each other .
ubuntu@havana:~$ swift list
2ae43fe4-eb72-4402-9c5c-4a42749cfee3
dfc9e845-2d67-4be4-892a-648a7a13e881
Regards.
Hui
On Fri, Mar 28
On Fri, Mar 28, 2014 at 12:24 PM, Hui Xiang wrote:
> Hi juju community,
>
> I hit en error when using juju plus OpenStack provider, below is the
> environment and what I found, please give me a help to let me move on.
>
> OpenStackļ¼ Havana(deployed with devstack)
> juju : 1.16.6-precise-amd
yeah, maybe you are right, well at least Im not the only one suffering from
swift and juju relationship, hehe.
Seems to me juju is getting a wrong url for their tools, as Andrew noticed.
Abs,
Sebas.
2014-03-28 1:39 GMT-03:00 Andrew Wilkins :
> On Fri, Mar 28, 2014 at 12:24 PM, Hui Xiang wrote
Hi Andrew,
I didn't set tools-url and tools-metadata-url, looks like you find the
root cause, what it should be like, I failed to find info of it except :
# tools-url: https://you-tools-url
I am not sure what tools url is, juju tool?
Thanks for your great help : )
Sebas,
Try to rede
Hui yes swift is working!, actually, I did an upload using the swift
command, and even appeared in the havana dashboard.
The problem seems to be in the proxy-server i think.
thanks!!
Abs,
Sebas.
2014-03-28 1:37 GMT-03:00 Hui Xiang :
> Hey Sebas,
>
> Can you use the command of "swift list"?
On Fri, Mar 28, 2014 at 12:49 PM, Hui Xiang wrote:
> Hi Andrew,
>
> I didn't set tools-url and tools-metadata-url, looks like you find the
> root cause, what it should be like, I failed to find info of it except :
> # tools-url: https://you-tools-url
>
> I am not sure what tools url is, ju
maybe I'm with the same problem, because i'm not setting those.
What are that urls? theres a real example for better understanding?
Sebas.
2014-03-28 1:57 GMT-03:00 Andrew Wilkins :
> On Fri, Mar 28, 2014 at 12:49 PM, Hui Xiang wrote:
>
>> Hi Andrew,
>>
>> I didn't set tools-url and tools-m
On Fri, Mar 28, 2014 at 1:03 PM, Sebastian wrote:
> maybe I'm with the same problem, because i'm not setting those.
>
> What are that urls? theres a real example for better understanding?
>
The URL must point to a location that contains the tools tarballs and tools
metadata. For OpenStack, this
25 matches
Mail list logo
