date:20160129

Re: Overlay network for Juju LXC containers?

2016-01-29 Thread Rick Harding

Thanks Andrew.

On Fri, Jan 29, 2016, 8:18 AM Andrew McDermott <
andrew.mcderm...@canonical.com> wrote:

> I will look into this this afternoon for you.
>
> On 29 January 2016 at 13:16, Rick Harding 
> wrote:
>
>> Sorry dimiter, I know Andrew is out. Can you investigat please?
>>
>>
>> On Fri, Jan 29, 2016, 8:13 AM Merlijn Sebrechts <
>> merlijn.sebrec...@gmail.com> wrote:
>>
>>> Any follow up to this? I'm also interested in using fan with lxc and
>>> Juju.
>>>
>>> 2016-01-07 19:19 GMT+01:00 Andrew McDermott <
>>> andrew.mcderm...@canonical.com>:
>>>
 Hi Patrik,

 I will look into this tomorrow. Apologies for the delay.

 On 7 January 2016 at 14:39, Patrik Karisch 
 wrote:

> Hi Andrew,
>
> Thanks for the answer.
>
> According to AWS, all the instances must be created inside a VPC to
> bind the lxcbr0 to the AWS network and get an IP allocated?
>
> Since Digital Ocean provider is a simple plugin and basically based on
> manual provsioning the best solution would be to activate Fan networking 
> on
> my machines manually? Are there any docs how I can point Juju to get a Fan
> IP address for the containers? Mark Shuttleworths blog post says it's 
> super
> easy for LXD, Docker and Juju but shows only a Docker cli example.
>
> Best regards
> Patrik
>
> Andrew McDermott  schrieb am Do., 7.
> Jan. 2016 um 14:14 Uhr:
>
>> Hi Patrik,
>>
>> There is no current solution for Digital Ocean.
>>
>> On AWS a container gets an IP address on the lxcbr0 network. We then
>> add iptable rules that make the container visible on the hosts network -
>> the host can see the container, the container can see the host.
>>
>> On MAAS (for 16.04) we create a bridge per NIC and the container,
>> depending on how many interfaces are configured, will get an address on
>> each subnet. Please note that all of this is currently work in progress 
>> and
>> is only available on a feature branch (maas-spaces).
>>
>> AWS and MAAS do not use the fan.
>>
>> We are currently working on Juju's network model to make it easier to
>> do what you are asking for. My colleague Dimiter Naydenov has been 
>> blogging
>> about this recently:
>>
>>
>> https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/
>>
>> So for DO we don't have any transparent Juju solution for you, but we
>> are actively developing the capabilities of Juju's networking model.
>>
>> HTH
>>
>> On 6 January 2016 at 17:29, Patrik Karisch 
>> wrote:
>>
>>> Hi,
>>>
>>> I'm wondering what Juju does to make services deployed into LXC
>>> containers on different machines reachable within the whole environment?
>>> Does it use Fan or something?
>>>
>>> Currently I'm trying Juju on Digital Ocean, where a machine has only
>>> one private IP and can't get more. I don't have the budget to run every
>>> service in a new machine, so they must reside in containers on a limited
>>> bunch of machines.
>>>
>>> Best regards
>>> Patrik
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>>
>>
>> --
>> Andrew McDermott 
>> Juju Core Sapphire team 
>>
>


 --
 Andrew McDermott 
 Juju Core Sapphire team 

 --
 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
>>>
>>
>
>
> --
> Andrew McDermott 
> Juju Core Sapphire team 
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Overlay network for Juju LXC containers?

2016-01-29 Thread Rick Harding

Sorry dimiter, I know Andrew is out. Can you investigat please?

On Fri, Jan 29, 2016, 8:13 AM Merlijn Sebrechts 
wrote:

> Any follow up to this? I'm also interested in using fan with lxc and Juju.
>
> 2016-01-07 19:19 GMT+01:00 Andrew McDermott <
> andrew.mcderm...@canonical.com>:
>
>> Hi Patrik,
>>
>> I will look into this tomorrow. Apologies for the delay.
>>
>> On 7 January 2016 at 14:39, Patrik Karisch 
>> wrote:
>>
>>> Hi Andrew,
>>>
>>> Thanks for the answer.
>>>
>>> According to AWS, all the instances must be created inside a VPC to bind
>>> the lxcbr0 to the AWS network and get an IP allocated?
>>>
>>> Since Digital Ocean provider is a simple plugin and basically based on
>>> manual provsioning the best solution would be to activate Fan networking on
>>> my machines manually? Are there any docs how I can point Juju to get a Fan
>>> IP address for the containers? Mark Shuttleworths blog post says it's super
>>> easy for LXD, Docker and Juju but shows only a Docker cli example.
>>>
>>> Best regards
>>> Patrik
>>>
>>> Andrew McDermott  schrieb am Do., 7.
>>> Jan. 2016 um 14:14 Uhr:
>>>
 Hi Patrik,

 There is no current solution for Digital Ocean.

 On AWS a container gets an IP address on the lxcbr0 network. We then
 add iptable rules that make the container visible on the hosts network -
 the host can see the container, the container can see the host.

 On MAAS (for 16.04) we create a bridge per NIC and the container,
 depending on how many interfaces are configured, will get an address on
 each subnet. Please note that all of this is currently work in progress and
 is only available on a feature branch (maas-spaces).

 AWS and MAAS do not use the fan.

 We are currently working on Juju's network model to make it easier to
 do what you are asking for. My colleague Dimiter Naydenov has been blogging
 about this recently:

 https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/

 So for DO we don't have any transparent Juju solution for you, but we
 are actively developing the capabilities of Juju's networking model.

 HTH

 On 6 January 2016 at 17:29, Patrik Karisch 
 wrote:

> Hi,
>
> I'm wondering what Juju does to make services deployed into LXC
> containers on different machines reachable within the whole environment?
> Does it use Fan or something?
>
> Currently I'm trying Juju on Digital Ocean, where a machine has only
> one private IP and can't get more. I don't have the budget to run every
> service in a new machine, so they must reside in containers on a limited
> bunch of machines.
>
> Best regards
> Patrik
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>

 --
 Andrew McDermott 
 Juju Core Sapphire team 

>>>
>>
>>
>> --
>> Andrew McDermott 
>> Juju Core Sapphire team 
>>
>> --
>> 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 mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Overlay network for Juju LXC containers?

2016-01-29 Thread Andrew McDermott

I will look into this this afternoon for you.

On 29 January 2016 at 13:16, Rick Harding 
wrote:

> Sorry dimiter, I know Andrew is out. Can you investigat please?
>
>
> On Fri, Jan 29, 2016, 8:13 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Any follow up to this? I'm also interested in using fan with lxc and Juju.
>>
>> 2016-01-07 19:19 GMT+01:00 Andrew McDermott <
>> andrew.mcderm...@canonical.com>:
>>
>>> Hi Patrik,
>>>
>>> I will look into this tomorrow. Apologies for the delay.
>>>
>>> On 7 January 2016 at 14:39, Patrik Karisch 
>>> wrote:
>>>
 Hi Andrew,

 Thanks for the answer.

 According to AWS, all the instances must be created inside a VPC to
 bind the lxcbr0 to the AWS network and get an IP allocated?

 Since Digital Ocean provider is a simple plugin and basically based on
 manual provsioning the best solution would be to activate Fan networking on
 my machines manually? Are there any docs how I can point Juju to get a Fan
 IP address for the containers? Mark Shuttleworths blog post says it's super
 easy for LXD, Docker and Juju but shows only a Docker cli example.

 Best regards
 Patrik

 Andrew McDermott  schrieb am Do., 7.
 Jan. 2016 um 14:14 Uhr:

> Hi Patrik,
>
> There is no current solution for Digital Ocean.
>
> On AWS a container gets an IP address on the lxcbr0 network. We then
> add iptable rules that make the container visible on the hosts network -
> the host can see the container, the container can see the host.
>
> On MAAS (for 16.04) we create a bridge per NIC and the container,
> depending on how many interfaces are configured, will get an address on
> each subnet. Please note that all of this is currently work in progress 
> and
> is only available on a feature branch (maas-spaces).
>
> AWS and MAAS do not use the fan.
>
> We are currently working on Juju's network model to make it easier to
> do what you are asking for. My colleague Dimiter Naydenov has been 
> blogging
> about this recently:
>
>
> https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/
>
> So for DO we don't have any transparent Juju solution for you, but we
> are actively developing the capabilities of Juju's networking model.
>
> HTH
>
> On 6 January 2016 at 17:29, Patrik Karisch 
> wrote:
>
>> Hi,
>>
>> I'm wondering what Juju does to make services deployed into LXC
>> containers on different machines reachable within the whole environment?
>> Does it use Fan or something?
>>
>> Currently I'm trying Juju on Digital Ocean, where a machine has only
>> one private IP and can't get more. I don't have the budget to run every
>> service in a new machine, so they must reside in containers on a limited
>> bunch of machines.
>>
>> Best regards
>> Patrik
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
>
> --
> Andrew McDermott 
> Juju Core Sapphire team 
>

>>>
>>>
>>> --
>>> Andrew McDermott 
>>> Juju Core Sapphire team 
>>>
>>> --
>>> 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
>>
>


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

Re: Leadership layer released

2016-01-29 Thread Stuart Bishop

On 28 January 2016 at 21:42, Cory Johns  wrote:

> I also very much like the pattern of having states that notify of changes to
> the leadership settings and think this pattern could apply well to config
> settings.  One addition I would suggest to that pattern would be to also

On config, yes, a similar pattern could be applied. It is somewhat
more complex than leadership though. The three different states I'm
thinking of are:

- config.set.{name}. The configuration option 'name' exists and is set
to a value. It is not set to null or the empty string.

- config.default.{name}. The configuration option 'name' exists, and
its value is unchanged from the default defined in config.yaml.

- config.changed.{name}. The configuration option 'name' exists and
its value has been changed since the previous hook was run. This state
will not be set in the next hook, unless the configuration option was
changed yet again.

(The wording specifically mentions the options existing, to be
specific about what will happen in upgrade-charm when config options
are dropped and no longer exist)

The very first hook invoked (be it the install hook or a storage hook)
will have interesting behaviour. What options get the
config.changed.{name} state set? None of them? All of them? All that
have values changed from the default? I'm unsure of the best answer,
which is why the layer doesn't exist yet :) Should handlers waiting on
the config.changed.foo state always be invoked in the first hook,
never invoked in the first hook, or possibly be invoked in the first
hook?

> have a blanket `leadership.changed` state that would be set when *any* value
> was changed.  This is mostly to handle the case where you need to react to
> any of a set of multiple values changing.  Thoughts?

I've added this.

-- 
Stuart Bishop 

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

Re: Overlay network for Juju LXC containers?

2016-01-29 Thread Merlijn Sebrechts

Any follow up to this? I'm also interested in using fan with lxc and Juju.

2016-01-07 19:19 GMT+01:00 Andrew McDermott 
:

> Hi Patrik,
>
> I will look into this tomorrow. Apologies for the delay.
>
> On 7 January 2016 at 14:39, Patrik Karisch 
> wrote:
>
>> Hi Andrew,
>>
>> Thanks for the answer.
>>
>> According to AWS, all the instances must be created inside a VPC to bind
>> the lxcbr0 to the AWS network and get an IP allocated?
>>
>> Since Digital Ocean provider is a simple plugin and basically based on
>> manual provsioning the best solution would be to activate Fan networking on
>> my machines manually? Are there any docs how I can point Juju to get a Fan
>> IP address for the containers? Mark Shuttleworths blog post says it's super
>> easy for LXD, Docker and Juju but shows only a Docker cli example.
>>
>> Best regards
>> Patrik
>>
>> Andrew McDermott  schrieb am Do., 7.
>> Jan. 2016 um 14:14 Uhr:
>>
>>> Hi Patrik,
>>>
>>> There is no current solution for Digital Ocean.
>>>
>>> On AWS a container gets an IP address on the lxcbr0 network. We then add
>>> iptable rules that make the container visible on the hosts network - the
>>> host can see the container, the container can see the host.
>>>
>>> On MAAS (for 16.04) we create a bridge per NIC and the container,
>>> depending on how many interfaces are configured, will get an address on
>>> each subnet. Please note that all of this is currently work in progress and
>>> is only available on a feature branch (maas-spaces).
>>>
>>> AWS and MAAS do not use the fan.
>>>
>>> We are currently working on Juju's network model to make it easier to do
>>> what you are asking for. My colleague Dimiter Naydenov has been blogging
>>> about this recently:
>>>
>>>
>>> https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/
>>>
>>> So for DO we don't have any transparent Juju solution for you, but we
>>> are actively developing the capabilities of Juju's networking model.
>>>
>>> HTH
>>>
>>> On 6 January 2016 at 17:29, Patrik Karisch 
>>> wrote:
>>>
 Hi,

 I'm wondering what Juju does to make services deployed into LXC
 containers on different machines reachable within the whole environment?
 Does it use Fan or something?

 Currently I'm trying Juju on Digital Ocean, where a machine has only
 one private IP and can't get more. I don't have the budget to run every
 service in a new machine, so they must reside in containers on a limited
 bunch of machines.

 Best regards
 Patrik

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


>>>
>>>
>>> --
>>> Andrew McDermott 
>>> Juju Core Sapphire team 
>>>
>>
>
>
> --
> Andrew McDermott 
> Juju Core Sapphire team 
>
> --
> 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

[Review Queue] Tomcat, SpagoBi, xl c/c++, Minecraft, postgresql, ibm-db2

2016-01-29 Thread Andrew Mcleod

Hello!

Yesterday, Corry, Kevin, Konstantinos and I had our combined review queue
session, and here are the notes:


   -

   tomcat
   -

  https://bugs.launchpad.net/charms/+source/tomcat/+bug/1538715
  -

  Community request to have a webapp-container subordinate relation.
  This keeps subs from having to relate using juju-info, and it offers
  additional data (like webapp install path) that wouldn’t be
available over
  juju-info.
  -

  +1 and pushed. Updated tomcat charms for precise/trusty that offer
  this relation are now available in the store.
  -

   spagobi
   -

  https://bugs.launchpad.net/charms/+bug/1534497
  -

  We cannot proceed with this charm at the moment because of the
  following reasons
  -

 there are no tests validating the operational aspects of the charm
 -

 charm proof test is failing since some required items are missing
 (eg copyright file)
 -

  We deployed the charm using the instructions in the README but we
  couldn't reach to a web interface. We spotted a number of errors in the
  logs and we asked the charm author to review them.


   -

   xl c/c++
   -

  https://bugs.launchpad.net/charms/+bug/1489829
  -

  Recent code changes look great, but we are unable to test this charm
  at the moment while we wait for our ppc64le hardware to become available.
  -

   Minecraft charm
   -

  https://bugs.launchpad.net/charms/+bug/1523896
  -

  This is the second round of reviewing this charm. The author
  addressed the comments we had.
  -

 all tests pass
 -

 the layer that builds the charm is provided here:
 https://github.com/mattyw/minecraft-charm
 -

  +1 with moving forward with this charm
  -

   postgresql (fix max connections)
   -


  
https://code.launchpad.net/~stub/charms/trusty/postgresql/fix-max-connections/+merge/282974
  -

  Had some issues with tests due to tester running juju 1.26 alpha3 -
  downgraded and all tests passed, +1 approved.
  -

   ibm-db2
   -

  https://bugs.launchpad.net/charms/+bug/1477057
  - All review items have been addressed and the charm has been
  promulgated.



have a great weekend!
Andrew
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Charm wish(todo) list

2016-01-29 Thread Tom Barber

Hello folks

We're working on a data management platform and I want Juju to "run" it,
but we have a bunch of stuff which looks not to be in the charm store and I
wanted to know if anyone has any of it in the pipeline, wants to
collaborate etc.

Our todo list is:

Pentaho Data Integration
Apache Drill
Google Data Flow (this is just being accepted into the ASF incubator as
Apache Beam)
Apache Ignite
Tachyon


I've not drilled down into Tachyon and Data Flow to figure out how generic
we could make it, but I think the others suit Juju-ification, and now we
have some dev credits it will make building this stuff a whole lot easier
(Thanks Marco etc for that)

at the end of it all, we can then deploy our Quarkmatter app over the top
of it all to add a data management platform to Juju.

Let me know your thoughts.

Regards,

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Error in jujuclient with python3

2016-01-29 Thread Philip Joseph

Hi,

I am seeing an error in jujuclient when using python3:

Traceback (most recent call last):
  File "./juju-ctrl.py", line 579, in 
api.execute()
  File "./juju-ctrl.py", line 476, in execute
self.deploy_service(service, details)
  File "./juju-ctrl.py", line 289, in deploy_service
result = self.env.add_local_charm_dir(deploy['directory'], series)
  File "/usr/lib/python3.4/site-packages/jujuclient.py", line 578, in
add_local_charm_dir
fh, series, os.stat(fh.name).st_size)
  File "/usr/lib/python3.4/site-packages/jujuclient.py", line 586, in
add_local_charm
conn, headers, path_prefix = self._http_conn()
  File "/usr/lib/python3.4/site-packages/jujuclient.py", line 561, in
_http_conn
'%(user)s:%(password)s' % (self._creds))}
  File "/usr/lib64/python3.4/base64.py", line 62, in b64encode
encoded = binascii.b2a_base64(s)[:-1]
TypeError: 'str' does not support the buffer interface

The error is seen when charm is to be downloaded to juju using HTTP
connection. The script works correctly with python 2. I am using
jujuclient (0.50.4) on fedora.

Anyone workaround for this.

Regards,
Philip

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

Re: Error in jujuclient with python3

2016-01-29 Thread Adam Israel

Hi Philip,

Is it possible for you to pastebin or send the code you’re using that triggers 
this error? I’d like to track this down and get a fix out for you ASAP.

Thanks!
--
Adam Israel - Software Engineer
Canonical Ltd.
http://juju.ubuntu.com/ - Automate your Cloud Infrastructure

> On Jan 29, 2016, at 8:31 PM, Philip Joseph  wrote:
> 
> Hi,
> 
> I am seeing an error in jujuclient when using python3:
> 
> Traceback (most recent call last):
>   File "./juju-ctrl.py", line 579, in 
> api.execute()
>   File "./juju-ctrl.py", line 476, in execute
> self.deploy_service(service, details)
>   File "./juju-ctrl.py", line 289, in deploy_service
> result = self.env.add_local_charm_dir(deploy['directory'], series)
>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 578, in 
> add_local_charm_dir
> fh, series, os.stat(fh.name).st_size)
>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 586, in 
> add_local_charm
> conn, headers, path_prefix = self._http_conn()
>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 561, in 
> _http_conn
> '%(user)s:%(password)s' % (self._creds))}
>   File "/usr/lib64/python3.4/base64.py", line 62, in b64encode
> encoded = binascii.b2a_base64(s)[:-1]
> TypeError: 'str' does not support the buffer interface
> 
> The error is seen when charm is to be downloaded to juju using HTTP 
> connection. The script works correctly with python 2. I am using jujuclient 
> (0.50.4) on fedora.
> 
> Anyone workaround for this.
> 
> Regards,
> Philip
> 
> -- 
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/juju



smime.p7s
Description: S/MIME cryptographic signature
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Error in jujuclient with python3

2016-01-29 Thread Adam Israel

Hi Philip,

Could you also confirm which version of juju (`juju version`) and jujuclient 
(pip3 list|grep jujuclient)

Thanks!

Adam Israel - Software Engineer
Canonical Ltd.
http://juju.ubuntu.com/ - Automate your Cloud Infrastructure

> On Jan 29, 2016, at 9:06 PM, Adam Israel  wrote:
> 
> Hi Philip,
> 
> Is it possible for you to pastebin or send the code you’re using that 
> triggers this error? I’d like to track this down and get a fix out for you 
> ASAP.
> 
> Thanks!
> --
> Adam Israel - Software Engineer
> Canonical Ltd.
> http://juju.ubuntu.com/  - Automate your Cloud 
> Infrastructure
> 
>> On Jan 29, 2016, at 8:31 PM, Philip Joseph > > wrote:
>> 
>> Hi,
>> 
>> I am seeing an error in jujuclient when using python3:
>> 
>> Traceback (most recent call last):
>>   File "./juju-ctrl.py", line 579, in 
>> api.execute()
>>   File "./juju-ctrl.py", line 476, in execute
>> self.deploy_service(service, details)
>>   File "./juju-ctrl.py", line 289, in deploy_service
>> result = self.env.add_local_charm_dir(deploy['directory'], series)
>>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 578, in 
>> add_local_charm_dir
>> fh, series, os.stat(fh.name).st_size)
>>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 586, in 
>> add_local_charm
>> conn, headers, path_prefix = self._http_conn()
>>   File "/usr/lib/python3.4/site-packages/jujuclient.py", line 561, in 
>> _http_conn
>> '%(user)s:%(password)s' % (self._creds))}
>>   File "/usr/lib64/python3.4/base64.py", line 62, in b64encode
>> encoded = binascii.b2a_base64(s)[:-1]
>> TypeError: 'str' does not support the buffer interface
>> 
>> The error is seen when charm is to be downloaded to juju using HTTP 
>> connection. The script works correctly with python 2. I am using jujuclient 
>> (0.50.4) on fedora.
>> 
>> Anyone workaround for this.
>> 
>> Regards,
>> Philip
>> 
>> -- 
>> Juju mailing list
>> Juju@lists.ubuntu.com 
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/juju
> 



smime.p7s
Description: S/MIME cryptographic signature
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Overlay network for Juju LXC containers?

Re: Overlay network for Juju LXC containers?

Re: Overlay network for Juju LXC containers?

Re: Leadership layer released

Re: Overlay network for Juju LXC containers?

[Review Queue] Tomcat, SpagoBi, xl c/c++, Minecraft, postgresql, ibm-db2

Charm wish(todo) list

Error in jujuclient with python3

Re: Error in jujuclient with python3

Re: Error in jujuclient with python3

10 matches

Site Navigation

Mail list logo

Footer information