Submission of sme-1 for charm store

[Steven Sweeting]

Hi,

 

I’d like to respectively request that our new charm sme be considered for 
promulgation to the charm store.

 

https://jujucharms.com/u/storage-made-easy/sme/xenial/1

 

Thanks,

Steven

 

Steven Sweeting. Director, Product Management
Storage Made Easy | Twitter: Storage Made Easy | +1 510.213.0965
Email: Steven Sweeting | Blog: blog.storagemadeeasy.com | Skype 


The information in this e-mail and any files transmitted with it are 
confidential and are intended solely for the use of the addressee. Access to 
this e-mail by anyone else is unauthorized. If you are not the intended 
recipient any disclosure, copying and distribution of the information contained 
in this e-mail is prohibited. Although this e-mail has been checked for all 
known viruses, Vehera LTD cannot accept responsibility for any loss or damage 
arising from the use of this e-mail or its attachments. We keep personal data 
to be able to communicate with you. This can  include your name, email address, 
contact number, and may document the nature of any interactions we have had. If 
you wish to, unsubscribe from further emails from Storage Made Easy. Please be 
aware that unsubscribing may generate a further email acknowledging your 
removal. Vehera Limited is a company registered in England. Registered Number: 
07079346. The Registered address is Mulgrave Chambers, 26-28 Mulgrave Road, 
Sutton, Surrey SM2 6LE.

 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Trouble adding IPv6 to installed Keystone charm.

[Ken D'Ambrosio]

Hey, all.  Looking to enable IPv6 endpoints on our Newton cloud.  "juju 
config keystone" shows this:


 prefer-ipv6:
description: |
  If True enables IPv6 support. The charm will expect network 
interfaces
  to be configured with an IPv6 address. If set to False (default) 
IPv4

  is expected.
  .
  NOTE: these charms do not currently support IPv6 privacy 
extension. In
  order for this charm to function correctly, the privacy extension 
must be
  disabled and a non-temporary address must be configured/available 
on

  your network interface.
type: boolean
value: true

It had originally been false.  I manually added 2004::100 to eth0 on my 
keystone host, and changed the value to true.  The Juju log on the 
Keystone host comes back with this:


2017-12-04 19:16:06 INFO config-changed Exception: Interface 'eth0' does 
not have a scope global non-temporary ipv6 address.


eth0 looks like this:
eth0  Link encap:Ethernet  HWaddr 00:16:3e:7f:eb:70
  inet addr:172.23.248.38  Bcast:172.23.248.63  
Mask:255.255.255.192

  inet6 addr: 2004::100/64 Scope:Global
[...]

I've googled like crazy, and can't find anything that really seems to 
fit the bill for "non-temporary ipv6 address", except in a different 
charm 
(https://api.jujucharms.com/v5/~sdn-charmers/trusty/contrail-analytics-31/archive/hooks/charmhelpers/contrib/network/ip.py) 
which says:


We currently only support scope global IPv6 addresses i.e. 
non-temporary
addresses. If no global IPv6 address is found, return the first one 
found

in the ipv6 address list.

Which seems to imply that a global IPv6 address *is* non-temporary by 
definition, which confuses me even more as to what's broken.


Any pointers here?

Thanks kindly,

-Ken

--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Deploying a charm with t's & c's

[Tom Barber]

Thanks chaps,

I'll try elsewhere.

Tom

On 04/12/17 18:17, Rick Harding wrote:
Thanks for this Tom, for some reason the controller in the region 
there isn't running 2.2.6, we're looking into it and will try to get 
it updated as soon as possible.


On Mon, Dec 4, 2017 at 9:22 AM Tom Barber > wrote:


mymodel jaas    aws/us-east-1  2.2.2    unsupported


Tom


On 04/12/17 14:08, Matthew Williams wrote:

Hi Tom,

What version of the controller are you using (show in juju
status). Is this your own controller or are you using jimm?

Thanks

Matty

On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber mailto:t...@spicule.co.uk>> wrote:

Hi Casey

https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll
see here. #45 works for me also but #47 fails. I don't think
we changed anything massively but clearly something in there
is sad, the problem is that, the error thrown gives me no
indication of where we've messed up.

On a side note I wanted to grab the zip archive of #45 and
#47 and do a diff to see if it was obvious but both give me a
404 from the charm store.

juju list-agreements
Term     Agreed on
isrg-lets-encrypt/2      2017-04-26 09:43:38 + UTC
canonical/sla-terms/3        2017-08-31 21:19:16 + UTC
spiculecharms/pdi-terms/1    2017-11-27 23:24:11 + UTC

Tom


On 04/12/17 02:54, Casey Marshall wrote:

Tom,
With 2.2.6, I cannot reproduce any problems with deploying
your charm. See https://paste.ubuntu.com/26109617/

Please send me more information about your installation:

- How you installed Juju (snap, deb from PPA, compiled from
source, etc.)
- Platform information on the machine you're running the
Juju client on, OS, etc. Is it on a physical host, in a VM,
in a container?
- What cloud you're trying to deploy into

If you type `juju list-agreements`, does that show terms
you've agreed to?

-Casey

On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

Just as a quick update, I get the same if I deploy the
charm directly and from the charm store ie not in a bundle.

But removing the terms in the metadata.yaml removes the
error.

Tom


On 28/11/17 18:36, Stephen Downie wrote:

Thanks for looking into this Casey. The version of Juju
I'm running is 2.2.6-xenial-amd64


Spicule Ltd

Tel: 01603 327762



www.spicule.co.uk 


On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

hey Casey

if you have no models and try and deploy a
bundle with terms it shows you the deploy
screen them hangs. if you go back you see the
model with 0 units deployed.

this is a local bundle we were testing, just
exported from the gui, Ste can provide it if
you need it.


Thanks for clarifying. One last question, what
version of Juju was used on the command line when
trying to deploy the exported bundle?


Tom


On 28 Nov 2017 6:00 pm, "Casey Marshall"
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 10:50 AM, Stephen
Downie mailto:step...@spicule.co.uk>> wrote:

Thanks. I have tried running juju agree
spiculecharms/pdi-terms/1 and it states
terms already agreed?

When trying to deploy in the GUI it
returns the error message cannot create
bundle: already exists. It appears that
it creates the model but does't
actually deploy anything? I know I'm a
bit new to this but something seems a
bit broken.


Is it possible that the model name in the
GUI (the drop down in the upper-left of the
canvas) matched an already-created model
name? You might need to type in a new model
name there.

Or does this happen for new models with
this bundle no matter what?

Was 

Re: Deploying a charm with t's & c's

[Rick Harding]

Thanks for this Tom, for some reason the controller in the region there
isn't running 2.2.6, we're looking into it and will try to get it updated
as soon as possible.

On Mon, Dec 4, 2017 at 9:22 AM Tom Barber  wrote:

> mymodel  jaasaws/us-east-1  2.2.2unsupported
>
>
> Tom
>
>
> On 04/12/17 14:08, Matthew Williams wrote:
>
> Hi Tom,
>
> What version of the controller are you using (show in juju status). Is
> this your own controller or are you using jimm?
>
> Thanks
>
> Matty
>
> On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber  wrote:
>
>> Hi Casey
>>
>> https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here.
>> #45 works for me also but #47 fails. I don't think we changed anything
>> massively but clearly something in there is sad, the problem is that, the
>> error thrown gives me no indication of where we've messed up.
>>
>> On a side note I wanted to grab the zip archive of #45 and #47 and do a
>> diff to see if it was obvious but both give me a 404 from the charm store.
>>
>> juju list-agreements
>> Term Agreed on
>> isrg-lets-encrypt/2  2017-04-26 09:43:38 + UTC
>> canonical/sla-terms/32017-08-31 21:19:16 + UTC
>> spiculecharms/pdi-terms/12017-11-27 23:24:11 + UTC
>>
>> Tom
>>
>>
>> On 04/12/17 02:54, Casey Marshall wrote:
>>
>> Tom,
>> With 2.2.6, I cannot reproduce any problems with deploying your charm.
>> See https://paste.ubuntu.com/26109617/
>>
>> Please send me more information about your installation:
>>
>> - How you installed Juju (snap, deb from PPA, compiled from source, etc.)
>> - Platform information on the machine you're running the Juju client on,
>> OS, etc. Is it on a physical host, in a VM, in a container?
>> - What cloud you're trying to deploy into
>>
>> If you type `juju list-agreements`, does that show terms you've agreed to?
>>
>> -Casey
>>
>> On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber  wrote:
>>
>>> Just as a quick update, I get the same if I deploy the charm directly
>>> and from the charm store ie not in a bundle.
>>>
>>> But removing the terms in the metadata.yaml removes the error.
>>>
>>> Tom
>>>
>>>
>>> On 28/11/17 18:36, Stephen Downie wrote:
>>>
>>> Thanks for looking into this Casey. The version of Juju I'm running is
>>> 2.2.6-xenial-amd64
>>>
>>>
>>> Spicule Ltd
>>>
>>> Tel: 01603 327762
>>>
>>>
>>>
>>> www.spicule.co.uk
>>>
>>> On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall <
>>> casey.marsh...@canonical.com> wrote:
>>>
 On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber  wrote:

> hey Casey
>
> if you have no models and try and deploy a bundle with terms it shows
> you the deploy screen them hangs. if you go back you see the model with 0
> units deployed.
>
> this is a local bundle we were testing, just exported from the gui,
> Ste can provide it if you need it.
>

 Thanks for clarifying. One last question, what version of Juju was used
 on the command line when trying to deploy the exported bundle?


>
> Tom
>
>
> On 28 Nov 2017 6:00 pm, "Casey Marshall" 
> wrote:
>
> On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie <
> step...@spicule.co.uk> wrote:
>
>> Thanks. I have tried running juju agree spiculecharms/pdi-terms/1 and
>> it states terms already agreed?
>>
>> When trying to deploy in the GUI it returns the error message cannot
>> create bundle: already exists. It appears that it creates the model but
>> does't actually deploy anything? I know I'm a bit new to this but 
>> something
>> seems a bit broken.
>>
>
> Is it possible that the model name in the GUI (the drop down in the
> upper-left of the canvas) matched an already-created model name? You might
> need to type in a new model name there.
>
> Or does this happen for new models with this bundle no matter what?
>
> Was this in the GUI in JAAS (jujucharms.com)? Did you try deploying a
> bundle from the charmstore, or did you try importing a bundle.yaml file?
>
>
>>
>> Thanks all for your help.
>>
>> Spicule Ltd
>>
>> Tel: 01603 327762
>>
>>
>>
>> www.spicule.co.uk
>>
>> On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber 
>> wrote:
>>
>>> stupid question, but I assume the bundles should handle t&c's better?
>>>
>>> On 28 Nov 2017 12:29, "Ales Stimec" 
>>> wrote:
>>>
 Hi,

 Could you please try
juju agree spiculecharms/pdi-terms/1

 This is these are the terms that require agreement in order to
 deploy cs:~spiculecharms/pentaho-data-integration-45.
 To get a list of terms i used:
curl "
 https://api.jujucharms.com/charmstore/v5/~spiculecharms/pentaho-data-integration-45/meta/any?include=id&include=terms
 "

 Best regards,
 Ales Stimec

>

Re: juju status ERROR current model controller devlocal not found

[Rick Harding]

Hi Feng, did you get anywhere with this? It looks like you're running
status on the controller itself. That's not a model to run status on. I'd
check out what juju list-models shows and run juju status on those.

I think what you need to do is to switch into the controller/model you want
to status or use the -m flag to specify it manually. Some helpful commands.

juju models
juju show-controller -c devlocal
juju status -m devlocal:controller
juju status -m devlocal:default
juju switch devlocal
juju models

On Mon, Dec 4, 2017 at 10:33 AM fengxia  wrote:

> Hi Juju,
>
> I had a localhost controller bootstrapped and deployed 8 machines (LXDs)
> to it. Host is a KVM vm of Ubuntu 16.04 amd64.
>
> Now for some strange reason, `juju status` reports error as if it lost
> its model? `list-controllers` showed the controller looks fine. `lxc
> list` shows all the machines are up and running.
>
> Any idea of what this error is about, and how to debug it?
>
> 
>
> (dev) fengxia@ubuntu:~$ juju status
> ERROR current model for controller devlocal not found
> (dev) fengxia@ubuntu:~$ juju list-controllers
> Use --refresh flag with this command to see the latest information.
>
> Controller  Model  User   Access Cloud/Region Models
> MachinesHA  Version
> devlocal*   -  admin  superuser  localhost/localhost 2 1
> none  2.2.6
>
> (dev) fengxia@ubuntu:~$ juju status
> ERROR current model for controller devlocal not found
> (dev) fengxia@ubuntu:~$ lxc list
>
> +---+-+---+--++---+
> | NAME  |  STATE  | IPV4  | IPV6 | TYPE|
> SNAPSHOTS |
>
> +---+-+---+--++---+
> | juju-6f4281-0 | RUNNING | 10.175.135.196 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-0 | RUNNING | 10.175.135.253 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-1 | RUNNING | 10.175.135.247 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-2 | RUNNING | 10.175.135.191 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-3 | RUNNING | 10.175.135.116 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-4 | RUNNING | 10.175.135.106 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-5 | RUNNING | 10.175.135.128 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-6 | RUNNING | 10.175.135.83 (eth0)  |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
> | juju-7031bf-7 | RUNNING | 10.175.135.223 (eth0) |  | PERSISTENT |
> 0 |
>
> +---+-+---+--++---+
>
> (dev) fengxia@ubuntu:~$ juju list-models
> Controller: devlocal
>
> Model   Cloud/Region Status Machines  Cores Access  Last
> connection
> controller  localhost/localhost  available 1  - admin   just
> now
> default localhost/localhost  available 8  - admin   11
> hours ago
>
> --
> Feng Xia
>
> Advisory Engineer
> Datacenter Group (DCG), Lenovo US
> 8000 Development Dr, Morrisiville, NC 27509
> W: http://www.lenovo.com
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Deploying a charm with t's & c's

[Matthew Williams]

Hi Tom,

This appears to be a problem with the 2.2.2 controller which has been fixed
in later versions. If you try a different aws region you should get a more
up to date controller and it should work as expected.

e.g. $ juju add-model mymodel aws/eu-west-1

Hope this helps

Matty

On Mon, Dec 4, 2017 at 2:22 PM, Tom Barber  wrote:

> mymodel  jaasaws/us-east-1  2.2.2unsupported
>
> Tom
>
>
> On 04/12/17 14:08, Matthew Williams wrote:
>
> Hi Tom,
>
> What version of the controller are you using (show in juju status). Is
> this your own controller or are you using jimm?
>
> Thanks
>
> Matty
>
> On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber  wrote:
>
>> Hi Casey
>>
>> https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here.
>> #45 works for me also but #47 fails. I don't think we changed anything
>> massively but clearly something in there is sad, the problem is that, the
>> error thrown gives me no indication of where we've messed up.
>>
>> On a side note I wanted to grab the zip archive of #45 and #47 and do a
>> diff to see if it was obvious but both give me a 404 from the charm store.
>>
>> juju list-agreements
>> Term Agreed on
>> isrg-lets-encrypt/2  2017-04-26 09:43:38 + UTC
>> canonical/sla-terms/32017-08-31 21:19:16 + UTC
>> spiculecharms/pdi-terms/12017-11-27 23:24:11 + UTC
>>
>> Tom
>>
>>
>> On 04/12/17 02:54, Casey Marshall wrote:
>>
>> Tom,
>> With 2.2.6, I cannot reproduce any problems with deploying your charm.
>> See https://paste.ubuntu.com/26109617/
>>
>> Please send me more information about your installation:
>>
>> - How you installed Juju (snap, deb from PPA, compiled from source, etc.)
>> - Platform information on the machine you're running the Juju client on,
>> OS, etc. Is it on a physical host, in a VM, in a container?
>> - What cloud you're trying to deploy into
>>
>> If you type `juju list-agreements`, does that show terms you've agreed to?
>>
>> -Casey
>>
>> On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber  wrote:
>>
>>> Just as a quick update, I get the same if I deploy the charm directly
>>> and from the charm store ie not in a bundle.
>>>
>>> But removing the terms in the metadata.yaml removes the error.
>>>
>>> Tom
>>>
>>>
>>> On 28/11/17 18:36, Stephen Downie wrote:
>>>
>>> Thanks for looking into this Casey. The version of Juju I'm running is
>>> 2.2.6-xenial-amd64
>>>
>>>
>>> Spicule Ltd
>>>
>>> Tel: 01603 327762
>>>
>>>
>>>
>>> www.spicule.co.uk
>>>
>>> On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall <
>>> casey.marsh...@canonical.com> wrote:
>>>
 On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber  wrote:

> hey Casey
>
> if you have no models and try and deploy a bundle with terms it shows
> you the deploy screen them hangs. if you go back you see the model with 0
> units deployed.
>
> this is a local bundle we were testing, just exported from the gui,
> Ste can provide it if you need it.
>

 Thanks for clarifying. One last question, what version of Juju was used
 on the command line when trying to deploy the exported bundle?


>
> Tom
>
>
> On 28 Nov 2017 6:00 pm, "Casey Marshall" 
> wrote:
>
> On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie <
> step...@spicule.co.uk> wrote:
>
>> Thanks. I have tried running juju agree spiculecharms/pdi-terms/1 and
>> it states terms already agreed?
>>
>> When trying to deploy in the GUI it returns the error message cannot
>> create bundle: already exists. It appears that it creates the model but
>> does't actually deploy anything? I know I'm a bit new to this but 
>> something
>> seems a bit broken.
>>
>
> Is it possible that the model name in the GUI (the drop down in the
> upper-left of the canvas) matched an already-created model name? You might
> need to type in a new model name there.
>
> Or does this happen for new models with this bundle no matter what?
>
> Was this in the GUI in JAAS (jujucharms.com)? Did you try deploying a
> bundle from the charmstore, or did you try importing a bundle.yaml file?
>
>
>>
>> Thanks all for your help.
>>
>> Spicule Ltd
>>
>> Tel: 01603 327762
>>
>>
>>
>> www.spicule.co.uk
>>
>> On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber 
>> wrote:
>>
>>> stupid question, but I assume the bundles should handle t&c's better?
>>>
>>> On 28 Nov 2017 12:29, "Ales Stimec" 
>>> wrote:
>>>
 Hi,

 Could you please try
juju agree spiculecharms/pdi-terms/1

 This is these are the terms that require agreement in order to
 deploy cs:~spiculecharms/pentaho-data-integration-45.
 To get a list of terms i used:
curl "https://api.jujucharms.com/ch
 armstore/v5/~spiculecharms/pentaho-data-integration-

Re: Juju bootstrap fails

[Rick Harding]

Hi Deepa. When Juju boostrap it provisions a node and then uses an ssh
connection to communicate with that provisioned node. It looks like your
client machine isn't able to communicate with the newly provisioned MAAS
node without the proxy config you've setup to help with it. I personally
use a tool sshuttle [1]to enable me to create a tunnel to the MAAS managed
network from my client network so that I can work with the bootstrapped
controllers on MAAS.

1: https://sshuttle.readthedocs.io/en/stable/


On Tue, Nov 28, 2017 at 12:35 AM Deepa K R  wrote:

> Hello Team
>
>
>
>   I am trying to bootstrap a VM machine in order to deploy Openstack cloud
>  and it hangs as below
>
>
>
> maasadmin@FGSUSSUMAAS01:~$ juju bootstrap stagingmaas
>
> Creating Juju controller "stagingmaas" on stagingmaas
>
> Looking for packaged Juju agent version 2.2.6 for amd64
>
> Launching controller instance(s) on stagingmaas...
>
> - qrdf8y (arch=amd64 mem=10G cores=10)
>
> Fetching Juju GUI 2.10.2
>
> Waiting for address
>
> Attempting to connect to 10.x.0.10:22  <<<
>
>
>
> maasadmin@FGSUSSUMAAS01:~/openstack-stg$ juju --version
>
> 2.2.6-xenial-amd64
>
>
>
> Is there any way to fix this out .
>
>
>
> Also please note if I use below details in bootstrap.config file ,boot
> strap succeeds. 10.139.0.50 is the private IP of maas server  .
>
>
>
> default-series: xenial
>
> no-proxy: localhost
>
> http-proxy: http://10.x.0.50:8000
>
> https-proxy: http://10.x.0.50:8000
>
> ftp-proxy: http://10.x.0.50:8000
>
>
>
> If I use public IP of maas server in config file ,bootstrap fails
>
>
>
> As you see 10.x.0.50 is the private IP of maas server and Openstack
> deployment fails with
>
>
>
> Machine  StateDNS  Inst id  Series  AZ   Message
>
> 0down 10.x.0.17  4rc3n3   xenial  default  Failed deployment:
> Power state queried: on
>
> 0/lxd/0  pending   pending  xenial
>
> 0/lxd/1  pending   pending  xenial
>
> 0/lxd/2  pending   pending  xenial
>
> 0/lxd/3  pending   pending  xenial
>
> 0/lxd/4  pending   pending  xenial
>
> 1down 10.x.0.18  gst3at   xenial  default  Failed deployment:
> Power state queried: on
>
> 1/lxd/0  pending   pending  xenial
>
> 1/lxd/1  pending   pending  xenial
>
> 1/lxd/2  pending   pending  xenial
>
> 1/lxd/3  pending   pending  xenial
>
> 2down 10.x.0.19  s8pct4   xenial  default  Failed deployment:
> Power state queried: on
>
> 3down 10.x.0.20  7nrsab   xenial  default  Failed deployment:
> Power state queried: on
>
> 4down 10.x.0.21  7pqsdy   xenial  default  Failed deployment:
> Power state queried: on
>
>
>
> Please see the attachment also .
>
>
>
> So in order to get deployment going I need bootstrap issue to get resolve .
>
> Kindly suggest
>
>
>
> Regards,
>
> Deepa K R
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

juju status ERROR current model controller devlocal not found

[fengxia]

Hi Juju,

I had a localhost controller bootstrapped and deployed 8 machines (LXDs) 
to it. Host is a KVM vm of Ubuntu 16.04 amd64.


Now for some strange reason, `juju status` reports error as if it lost 
its model? `list-controllers` showed the controller looks fine. `lxc 
list` shows all the machines are up and running.


Any idea of what this error is about, and how to debug it?



(dev) fengxia@ubuntu:~$ juju status
ERROR current model for controller devlocal not found
(dev) fengxia@ubuntu:~$ juju list-controllers
Use --refresh flag with this command to see the latest information.

Controller  Model  User   Access Cloud/Region Models 
Machines    HA  Version
devlocal*   -  admin  superuser  localhost/localhost 2 1  
none  2.2.6


(dev) fengxia@ubuntu:~$ juju status
ERROR current model for controller devlocal not found
(dev) fengxia@ubuntu:~$ lxc list
+---+-+---+--++---+
| NAME  |  STATE  | IPV4  | IPV6 | TYPE    | 
SNAPSHOTS |

+---+-+---+--++---+
| juju-6f4281-0 | RUNNING | 10.175.135.196 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-0 | RUNNING | 10.175.135.253 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-1 | RUNNING | 10.175.135.247 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-2 | RUNNING | 10.175.135.191 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-3 | RUNNING | 10.175.135.116 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-4 | RUNNING | 10.175.135.106 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-5 | RUNNING | 10.175.135.128 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-6 | RUNNING | 10.175.135.83 (eth0)  |  | PERSISTENT | 
0 |

+---+-+---+--++---+
| juju-7031bf-7 | RUNNING | 10.175.135.223 (eth0) |  | PERSISTENT | 
0 |

+---+-+---+--++---+

(dev) fengxia@ubuntu:~$ juju list-models
Controller: devlocal

Model   Cloud/Region Status Machines  Cores Access  Last 
connection

controller  localhost/localhost  available 1  - admin   just now
default localhost/localhost  available 8  - admin   11 
hours ago


--
Feng Xia

Advisory Engineer
Datacenter Group (DCG), Lenovo US
8000 Development Dr, Morrisiville, NC 27509
W: http://www.lenovo.com


--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Debug logs

[Tom Barber]

Thanks Corey,

Its pretty unfriendly in terms of usability, I currently have to find 
this thread every time I want to debug something. Maybe I'll stick it as 
a bash alias or something.


I do remember the discussion about the noise, it does make sense, but 
being able to change the levels more intuitively I think would help.


Tom


On 04/12/17 14:36, Cory Johns wrote:
It seems that the default logging level for models was reduced some 
time back.  This makes the logs much less noisy and saves quite a bit 
of space, but it has the unfortunate side effect of making debugging 
charm failures from logs more difficult, as most failure messages only 
show up as stderr output.  It would probably be worth adding explicit 
logging of uncaught exceptions to the reactive framework so that they 
are clearly visible in the logs.


I've opened this as an issue against reactive here: 
https://github.com/juju-solutions/charms.reactive/issues/147


On Sun, Nov 26, 2017 at 2:47 PM, Tim Penhey > wrote:


What is the logging level for the model?

The output from the hooks are logged at debug level.

Tim

On 26/11/17 13:25, Tom Barber wrote:
> Maybe its just me, I dunno.
>
> Has the amount of detail in debug-logs decreased?
>
> I'm  not seeing failure causes for example:
>
> 2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104
found queued
> "install" hook
> 2017-11-26 00:12:26 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:12:32 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:12:43 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:13:05 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:13:44 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:15:02 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:17:40 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
> 2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting
> error resolution for "install" hook
> 2017-11-26 00:22:41 ERROR juju.worker.uniter.operation
runhook.go:107
> hook "install" failed: exit status 1
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135
Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
> All engagements are subject to Spicule Terms and Conditions of
Business.
> This email and its contents are intended solely for the
individual to
> whom it is addressed and may contain information that is
confidential,
> privileged or otherwise protected from disclosure, distributing or
> copying. Any views or opinions presented in this email are
solely those
> of the author and do not necessarily represent those of Spicule
Limited.
> The company accepts no liability for any damage caused by any virus

Re: Debug logs

[Cory Johns]

It seems that the default logging level for models was reduced some time
back.  This makes the logs much less noisy and saves quite a bit of space,
but it has the unfortunate side effect of making debugging charm failures
from logs more difficult, as most failure messages only show up as stderr
output.  It would probably be worth adding explicit logging of uncaught
exceptions to the reactive framework so that they are clearly visible in
the logs.

I've opened this as an issue against reactive here:
https://github.com/juju-solutions/charms.reactive/issues/147

On Sun, Nov 26, 2017 at 2:47 PM, Tim Penhey 
wrote:

> What is the logging level for the model?
>
> The output from the hooks are logged at debug level.
>
> Tim
>
> On 26/11/17 13:25, Tom Barber wrote:
> > Maybe its just me, I dunno.
> >
> > Has the amount of detail in debug-logs decreased?
> >
> > I'm  not seeing failure causes for example:
> >
> > 2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104 found queued
> > "install" hook
> > 2017-11-26 00:12:26 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:12:32 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:12:43 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:13:05 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:13:44 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:15:02 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:17:40 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> > 2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting
> > error resolution for "install" hook
> > 2017-11-26 00:22:41 ERROR juju.worker.uniter.operation runhook.go:107
> > hook "install" failed: exit status 1
> >
> >
> >
> >
> > Spicule Limited is registered in England & Wales. Company Number:
> > 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> > Road, Brighton, England, BN1 6AF. VAT No. 251478891.
> >
> >
> > All engagements are subject to Spicule Terms and Conditions of Business.
> > This email and its contents are intended solely for the individual to
> > whom it is addressed and may contain information that is confidential,
> > privileged or otherwise protected from disclosure, distributing or
> > copying. Any views or opinions presented in this email are solely those
> > of the author and do not necessarily represent those of Spicule Limited.
> > The company accepts no liability for any damage caused by any virus
> > transmitted by this email. If you have received this message in error,
> > please notify us immediately by reply email before deleting it from your
> > system. Service of legal notice cannot be effected on Spicule Limited by
> > email.
> >
> >
> >
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Deploying a charm with t's & c's

[Tom Barber]

mymodel  jaas    aws/us-east-1 2.2.2    unsupported

Tom

On 04/12/17 14:08, Matthew Williams wrote:

Hi Tom,

What version of the controller are you using (show in juju status). Is 
this your own controller or are you using jimm?


Thanks

Matty

On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber > wrote:


Hi Casey

https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB
 As you'll see
here. #45 works for me also but #47 fails. I don't think we
changed anything massively but clearly something in there is sad,
the problem is that, the error thrown gives me no indication of
where we've messed up.

On a side note I wanted to grab the zip archive of #45 and #47 and
do a diff to see if it was obvious but both give me a 404 from the
charm store.

juju list-agreements
Term         Agreed on
isrg-lets-encrypt/2      2017-04-26 09:43:38 + UTC
canonical/sla-terms/3        2017-08-31 21:19:16 + UTC
spiculecharms/pdi-terms/1    2017-11-27 23:24:11 + UTC

Tom


On 04/12/17 02:54, Casey Marshall wrote:

Tom,
With 2.2.6, I cannot reproduce any problems with deploying your
charm. See https://paste.ubuntu.com/26109617/


Please send me more information about your installation:

- How you installed Juju (snap, deb from PPA, compiled from
source, etc.)
- Platform information on the machine you're running the Juju
client on, OS, etc. Is it on a physical host, in a VM, in a
container?
- What cloud you're trying to deploy into

If you type `juju list-agreements`, does that show terms you've
agreed to?

-Casey

On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber mailto:t...@spicule.co.uk>> wrote:

Just as a quick update, I get the same if I deploy the charm
directly and from the charm store ie not in a bundle.

But removing the terms in the metadata.yaml removes the error.

Tom


On 28/11/17 18:36, Stephen Downie wrote:

Thanks for looking into this Casey. The version of Juju I'm
running is 2.2.6-xenial-amd64


Spicule Ltd

Tel: 01603 327762



www.spicule.co.uk 


On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

hey Casey

if you have no models and try and deploy a bundle
with terms it shows you the deploy screen them
hangs. if you go back you see the model with 0 units
deployed.

this is a local bundle we were testing, just
exported from the gui, Ste can provide it if you
need it.


Thanks for clarifying. One last question, what version
of Juju was used on the command line when trying to
deploy the exported bundle?


Tom


On 28 Nov 2017 6:00 pm, "Casey Marshall"
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie
mailto:step...@spicule.co.uk>> wrote:

Thanks. I have tried running juju agree
spiculecharms/pdi-terms/1 and it states
terms already agreed?

When trying to deploy in the GUI it returns
the error message cannot create bundle:
already exists. It appears that it creates
the model but does't actually deploy
anything? I know I'm a bit new to this but
something seems a bit broken.


Is it possible that the model name in the GUI
(the drop down in the upper-left of the canvas)
matched an already-created model name? You might
need to type in a new model name there.

Or does this happen for new models with this
bundle no matter what?

Was this in the GUI in JAAS (jujucharms.com
)? Did you try deploying
a bundle from the charmstore, or did you try
importing a bundle.yaml file?


Thanks all for your help.

Spicule Ltd

Tel: 01603 327762



www.spicule.co.uk 


On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

stupid question, but I assume the

Re: Deploying a charm with t's & c's

[Matthew Williams]

Hi Tom,

What version of the controller are you using (show in juju status). Is this
your own controller or are you using jimm?

Thanks

Matty

On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber  wrote:

> Hi Casey
>
> https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here. #45
> works for me also but #47 fails. I don't think we changed anything
> massively but clearly something in there is sad, the problem is that, the
> error thrown gives me no indication of where we've messed up.
>
> On a side note I wanted to grab the zip archive of #45 and #47 and do a
> diff to see if it was obvious but both give me a 404 from the charm store.
>
> juju list-agreements
> Term Agreed on
> isrg-lets-encrypt/2  2017-04-26 09:43:38 + UTC
> canonical/sla-terms/32017-08-31 21:19:16 + UTC
> spiculecharms/pdi-terms/12017-11-27 23:24:11 + UTC
>
> Tom
>
>
> On 04/12/17 02:54, Casey Marshall wrote:
>
> Tom,
> With 2.2.6, I cannot reproduce any problems with deploying your charm. See
> https://paste.ubuntu.com/26109617/
>
> Please send me more information about your installation:
>
> - How you installed Juju (snap, deb from PPA, compiled from source, etc.)
> - Platform information on the machine you're running the Juju client on,
> OS, etc. Is it on a physical host, in a VM, in a container?
> - What cloud you're trying to deploy into
>
> If you type `juju list-agreements`, does that show terms you've agreed to?
>
> -Casey
>
> On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber  wrote:
>
>> Just as a quick update, I get the same if I deploy the charm directly and
>> from the charm store ie not in a bundle.
>>
>> But removing the terms in the metadata.yaml removes the error.
>>
>> Tom
>>
>>
>> On 28/11/17 18:36, Stephen Downie wrote:
>>
>> Thanks for looking into this Casey. The version of Juju I'm running is
>> 2.2.6-xenial-amd64
>>
>>
>> Spicule Ltd
>>
>> Tel: 01603 327762
>>
>>
>>
>> www.spicule.co.uk
>>
>> On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall <
>> casey.marsh...@canonical.com> wrote:
>>
>>> On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber  wrote:
>>>
 hey Casey

 if you have no models and try and deploy a bundle with terms it shows
 you the deploy screen them hangs. if you go back you see the model with 0
 units deployed.

 this is a local bundle we were testing, just exported from the gui, Ste
 can provide it if you need it.

>>>
>>> Thanks for clarifying. One last question, what version of Juju was used
>>> on the command line when trying to deploy the exported bundle?
>>>
>>>

 Tom


 On 28 Nov 2017 6:00 pm, "Casey Marshall" 
 wrote:

 On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie >>> > wrote:

> Thanks. I have tried running juju agree spiculecharms/pdi-terms/1 and
> it states terms already agreed?
>
> When trying to deploy in the GUI it returns the error message cannot
> create bundle: already exists. It appears that it creates the model but
> does't actually deploy anything? I know I'm a bit new to this but 
> something
> seems a bit broken.
>

 Is it possible that the model name in the GUI (the drop down in the
 upper-left of the canvas) matched an already-created model name? You might
 need to type in a new model name there.

 Or does this happen for new models with this bundle no matter what?

 Was this in the GUI in JAAS (jujucharms.com)? Did you try deploying a
 bundle from the charmstore, or did you try importing a bundle.yaml file?


>
> Thanks all for your help.
>
> Spicule Ltd
>
> Tel: 01603 327762
>
>
>
> www.spicule.co.uk
>
> On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber 
> wrote:
>
>> stupid question, but I assume the bundles should handle t&c's better?
>>
>> On 28 Nov 2017 12:29, "Ales Stimec" 
>> wrote:
>>
>>> Hi,
>>>
>>> Could you please try
>>>juju agree spiculecharms/pdi-terms/1
>>>
>>> This is these are the terms that require agreement in order to
>>> deploy cs:~spiculecharms/pentaho-data-integration-45.
>>> To get a list of terms i used:
>>>curl "https://api.jujucharms.com/charmstore/v5/~spiculecharms/pen
>>> taho-data-integration-45/meta/any?include=id&include=terms"
>>>
>>> Best regards,
>>> Ales Stimec
>>>
>>> PS: fyi: the terms service issues short-lived macaroons (auth
>>> tokens) that are valid for 5 minutes…
>>>
>>>
>>>
>>> On 28 Nov 2017, at 12:59, John Meinel 
>>> wrote:
>>>
>>> Do you know what terms you need to accept? You should be able to
>>> 'juju accept termname'.
>>> The other thing to check is if your local clock time is fairly
>>> accurate.
>>> I believe we filed a bug recently that the term server gives out
>>> temporary auth tokens that are only valid for 1 

Re: Deploying a charm with t's & c's

[Tom Barber]

Hi Casey

https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here. 
#45 works for me also but #47 fails. I don't think we changed anything 
massively but clearly something in there is sad, the problem is that, 
the error thrown gives me no indication of where we've messed up.


On a side note I wanted to grab the zip archive of #45 and #47 and do a 
diff to see if it was obvious but both give me a 404 from the charm store.


juju list-agreements
Term         Agreed on
isrg-lets-encrypt/2      2017-04-26 09:43:38 + UTC
canonical/sla-terms/3        2017-08-31 21:19:16 + UTC
spiculecharms/pdi-terms/1    2017-11-27 23:24:11 + UTC

Tom

On 04/12/17 02:54, Casey Marshall wrote:

Tom,
With 2.2.6, I cannot reproduce any problems with deploying your charm. 
See https://paste.ubuntu.com/26109617/


Please send me more information about your installation:

- How you installed Juju (snap, deb from PPA, compiled from source, etc.)
- Platform information on the machine you're running the Juju client 
on, OS, etc. Is it on a physical host, in a VM, in a container?

- What cloud you're trying to deploy into

If you type `juju list-agreements`, does that show terms you've agreed to?

-Casey

On Sat, Dec 2, 2017 at 4:55 PM, Tom Barber > wrote:


Just as a quick update, I get the same if I deploy the charm
directly and from the charm store ie not in a bundle.

But removing the terms in the metadata.yaml removes the error.

Tom


On 28/11/17 18:36, Stephen Downie wrote:

Thanks for looking into this Casey. The version of Juju I'm
running is 2.2.6-xenial-amd64


Spicule Ltd

Tel: 01603 327762



www.spicule.co.uk 


On Tue, Nov 28, 2017 at 6:30 PM, Casey Marshall
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 12:09 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

hey Casey

if you have no models and try and deploy a bundle with
terms it shows you the deploy screen them hangs. if you
go back you see the model with 0 units deployed.

this is a local bundle we were testing, just exported
from the gui, Ste can provide it if you need it.


Thanks for clarifying. One last question, what version of
Juju was used on the command line when trying to deploy the
exported bundle?


Tom


On 28 Nov 2017 6:00 pm, "Casey Marshall"
mailto:casey.marsh...@canonical.com>> wrote:

On Tue, Nov 28, 2017 at 10:50 AM, Stephen Downie
mailto:step...@spicule.co.uk>> wrote:

Thanks. I have tried running juju agree
spiculecharms/pdi-terms/1 and it states terms
already agreed?

When trying to deploy in the GUI it returns the
error message cannot create bundle: already
exists. It appears that it creates the model but
does't actually deploy anything? I know I'm a bit
new to this but something seems a bit broken.


Is it possible that the model name in the GUI (the
drop down in the upper-left of the canvas) matched an
already-created model name? You might need to type in
a new model name there.

Or does this happen for new models with this bundle
no matter what?

Was this in the GUI in JAAS (jujucharms.com
)? Did you try deploying a
bundle from the charmstore, or did you try importing
a bundle.yaml file?


Thanks all for your help.

Spicule Ltd

Tel: 01603 327762



www.spicule.co.uk 


On Tue, Nov 28, 2017 at 12:33 PM, Tom Barber
mailto:t...@spicule.co.uk>> wrote:

stupid question, but I assume the bundles
should handle t&c's better?

On 28 Nov 2017 12:29, "Ales Stimec"
mailto:ales.sti...@canonical.com>> wrote:

Hi,

Could you please try
   juju agree spiculecharms/pdi-terms/1

This is these are the terms that require
agreement in order to deploy
cs:~spiculecharms/pentaho-data-integration-45.
To get a list of terms i used:
   curl

"https://api.jujucharms.com/charmstore/v5/~spiculecharms/pentaho-data-integration-45/meta/any?include=id&include=terms
 

Re: Getting the exposed ports

[Merlijn Sebrechts]

Hm, I wonder why the iptables charm is doing that.

from charms.reactive.bus import State

class states(StateList):
connected = State('{relation_name}.connected')
joined = State('{relation_name}.joined')
departed = State('{relation_name}.departed')


The internals of charms.reactive have changed quite a bit in the last few
releases. We kept the public API backwards-compatible, but preventing
breakages when charms dig into the charms.reactive internals is hard..

2017-12-02 23:14 GMT+01:00 Tom Barber :

> So I did take a look at the iptables charm
>
> https://api.jujucharms.com/charmstore/v5/~majduk/iptables-3/archive/hooks/
> relations/peer-discovery/peers.py
>
> is sad on my setup.
>
> unit-iptables-0: 22:08:53 DEBUG unit.iptables/0.install   File
> "/var/lib/juju/agents/unit-iptables-0/charm/hooks/
> relations/peer-discovery/peers.py", line 8, in 
> unit-iptables-0: 22:08:53 DEBUG unit.iptables/0.install from
> charms.reactive.bus import State
> unit-iptables-0: 22:08:53 DEBUG unit.iptables/0.install ImportError:
> cannot import name 'State'
>
> I'm not sure whats changed in charms.reactive but I can't find the State.
> Also I dont' know where the upstream source is so if I do figure it out I
> can't submit a patch.
>
> Cheers
>
> Tom
>
>
> On 01/12/17 16:58, Michał Ajduk wrote:
>
> Hello,
>
> You can take a look at iptables charm. It does the "easy part", that is
> admin defined ruleset.
>
> I was actually thinking of making it also use the open ports. I'm pretty
> sure juju-info relation has the open ports data, but I can take a look.
>
> BR,
> Michal
>
>
> 01.12.2017 16:52 "Tom Barber"  napisał(a):
>
> Hello folks
>
> I want to write a firewall charm for those deployments that aren't in the
> cloud. The "easy" thing to do is provide a config block and have admins
> write in rules and just apply them. I was wondering though, if I wrote a
> subordinate charm on juju-info to attach to anything, is there any
> mechanism for me to find the exposed port of the parent charm? and whether
> its exposed or not?
>
>
> Ta
>
> Tom
>
>
> --
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
> All engagements are subject to Spicule Terms and Conditions of Business.
> This email and its contents are intended solely for the individual to whom
> it is addressed and may contain information that is confidential,
> privileged or otherwise protected from disclosure, distributing or copying.
> Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of Spicule Limited. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email. If you have received this message in error, please notify us
> immediately by reply email before deleting it from your system. Service of
> legal notice cannot be effected on Spicule Limited by email.
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
>
>
>
> Spicule Limited is registered in England & Wales. Company Number:
> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston
> Road, Brighton, England, BN1 6AF. VAT No. 251478891.
>
>
> All engagements are subject to Spicule Terms and Conditions of Business.
> This email and its contents are intended solely for the individual to whom
> it is addressed and may contain information that is confidential,
> privileged or otherwise protected from disclosure, distributing or copying.
> Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of Spicule Limited. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email. If you have received this message in error, please notify us
> immediately by reply email before deleting it from your system. Service of
> legal notice cannot be effected on Spicule Limited by email.
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju