I think what you'd actually want to do is a layer for that. If you create
configuration in the charm, then you'd have a generic charm, and not expose
what is actually into it.
As Juju wants to model, what actually runs must be explicitly described.
With a layer, you could enable people to use a
Ney,
If you want, I am available on IRC to discuss the idea. It's definitely
doable, specially with config-get parameters, and it would be great to
have it! You can find us on #juju on irc.freenode.net. My nick is `jose`
in there.
On 03/01/2016 12:23 PM, Ney Moura wrote:
Hi Samuel!
Well!
Hi Samuel!
Well! It's a good idea! But since I'm to new in shell scripting I don't
think I could handle such thing. On the other hand I think I could create a
template charm that, with minimal effort, the community would be able to
use it on another bitnami stacks. Since stack commands should be
Hi Ney,
I've got myself in the same issue in the past, and found this pretty
useful: dos2unix. You can apt-get install it, then you get a dos2unix and a
unix2dos commands.
If you succeed with the bitnami -> charm, do you think you could create a
generic bitnami converter? That would be
I was thinking that i missed some configurations to ran those commands
properly only.
Since I use nano, I wasn't able to see those.
Thanks for the tip about hook environment and the command!
Mainly for the quick response =D
2016-02-29 21:31 GMT-03:00 José Antonio Rey :
> Glad
Glad that was it! When I opened it on vim, it said [dos] at the bottom, and
after googling the error I saw what it was.
About the command, what happens is right. You should not be able to execute
any of those commands. The commands are only executable in a 'hook
environment', meaning only hooks
Thanks everyone!
José Antonio, you were right!
How did you discover that?
But let me challenge you guys even more!
I need to install something in the VM before using the juju commands, like
status-set? I'm asking this because I wasn't able to run these commands in
there.
Thanks again!
This is because you are using Windows line breaks instead of Linux/Unix
line breaks. Try saving your file with Linux/Unix line breaks and give
it a go.
On 02/29/2016 05:12 PM, David Britton wrote:
On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
But I keep having erros with the
On Mon, Feb 29, 2016 at 07:02:08PM -0300, Ney Moura wrote:
>
> But I keep having erros with the install hook. It says file not found.
>
Maybe I missed it in the tarball -- could you attach a juju debug-log
capture while you deploy it?
Or, /var/log/all-machines.log from the bootstrap node is