Re: Juju-gui only show localhost as the deployment option

2017-08-30 Thread Akshat Jiwan Sharma
Thank you Feng,

As I understand for now there is no way to use multiple providers with juju
either with a GUI or command line.

My goal is to be able to allow users to deploy charms (mostly
wordpress/drupal/ghost) on a cloud of their choice. Anything that allows me
to do this is acceptable. The only requirement is maximum cloud coverage.
So for a multi cloud setup what options do I have?

- Should I go for one controller per cloud setup?
- Can juju api  help me write
some custom code that'll allow me to do what I want? If so what should I be
looking for in the documentation?
- Since juju runs in an lxc  would it be a good idea to create clone
containers that can switch the cloud environment on demand? Or would this
cause more problems that it'll solve?

Thank you once more for being patient with the questions and for all the
answers! Much appreciated

Best,
Akshat

On Wed, Aug 30, 2017 at 7:56 AM, fengxia  wrote:

> Hi Akshat,
>
> Juju controller does not support multiple cloud/provider. It's like a
> switch board, juju can only talk to one controller at a time.
> However, I do think there are use case of supporting multiple clouds with
> one orchestrator. I'm not sure whether juju team has sth like that on its
> roadmap, or maybe using some other tools for the purpose?
> On 08/29/2017 09:59 AM, Akshat Jiwan Sharma wrote:
>
> Is there a way I can configure multiple providers using the Juju-GUI? Also
> is there a way I can configure cloud providers based on user access roles?
> For example a user with access to a particular model can deploy only to a
> specific cloud provider.
>
> If one controller can manage multiple clouds and one controller can have
> many users then what is the mapping of the relationship between the users
> and the clouds?
>
> Thanks,
> Akshat
>
>
>
> --
> Feng xia
> Engineer
> Lenovo USA
>
> Phone: 5088011794fx...@lenovo.com
>   
> Lenovo.com
> Twitter | Facebook | Instagram | Blogs | Forums
>
>
> --
> 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


Promulgate request: Grafana

2017-08-30 Thread Tom Haddon
Hi Folks,   

   
Could we get cs:~prometheus-charmers/grafana promulgated?

The code for the charm is https://code.launchpad.net/grafana-charm and there's
a team that maintains it https://launchpad.net/~prometheus-charmers. That team
already maintains a number of other promulgated charms (mtail, prometheus,
prometheus-alertmanager, prometheus-push-gateway and
prometheus-blackbox-exporter). The grafana charm supports trusty and xenial.

If anyone is interested in joining the team to help maintain grafana and those
other charms please let us know.

Thanks, Tom

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


Juju Charmer application

2017-08-30 Thread Frode Nordahl
Dear Juju community,

I would like to officially apply for membership of the Juju ~charmers team.

Through the course of the past year I have made contributions to the
OpenStack Charms and other Charm projects. I have also had the privilege of
meeting many of you in person, and have shared fruitful exchanges. I have
signed the Ubuntu Code of Conduct.

Before playing around with Juju I have had a long career in tech from which
I have experience with both operations and development of system level
code. I particularly like having my code well tested to make sure it keeps
on running in the future.

Some examples of my charm-related work:
https://github.com/openstack/charm-neutron-openvswitch/commit/4ffbc2fe25400abf55719a370f3a2cd37f90c99d
https://github.com/openstack/charm-rabbitmq-server/commit/08b10513c5725fb740382668c47fc769a6f2936c
https://github.com/marcoceppi/charm-mysql/commit/cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
https://github.com/marcoceppi/charm-mysql/commit/1a8277855be4020b26121cb9d573cd150b6aa882
https://github.com/openstack/charm-ceph-radosgw/commit/7fa6639ab3fde7dc89131fb204f018fd4339e82f
https://github.com/openstack/charm-keystone/commit/5de1770931e886732870da1909f08279a0b804b4
https://github.com/openstack/charm-nova-cloud-controller/commit/2eef644a5c1acb2675e94908c88182658fec4ac5
https://github.com/openstack/charm-openstack-dashboard/commit/8f3a93ac4e7102736da492a189144220312f93df
https://github.com/openstack/charm-swift-proxy/commit/7c24ae81283710c830ab03f240ec9cc10dccd975

Launchpad ID: fnordahl

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


Re: Elasticsearch Charm Promulgation

2017-08-30 Thread Haw Loeung
On Tue, Aug 22, 2017 at 08:54:14AM +0100, Tom Haddon wrote:
> On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote:
> [...]
> > I checked with some of the ~onlineservices-charmers team and they were happy
> > for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ to 
> > replace
> > the current promulgated charm (which only supports precise and trusty). We
> > should test that you can successfully charm upgrade from theirs to this 
> > charm
> > (on trusty) - I'm happy to take that on, and will update here once we've 
> > done
> > so.
>
> I've tested an upgrade on trusty from the existing upstream elasticsearch
> charm to cs:~elasticsearch-charmers/trusty/elasticsearch and it seems to work
> okay:
>
> https://pastebin.ubuntu.com/25368096/
>

I've confirmed that the existing charm also supports ElasticSearch 5.x
(thanks to all the hard work from Ante).

Any chance we could get cs:~elasticsearch-charmers/elasticsearch
promulgated to cs:elasticsearch now?


Thanks,

Haw


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


Re: Juju Charmer application

2017-08-30 Thread James Page
+1

On Wed, 30 Aug 2017 at 11:15 Frode Nordahl  wrote:

> Dear Juju community,
>
> I would like to officially apply for membership of the Juju ~charmers team.
>
> Through the course of the past year I have made contributions to the
> OpenStack Charms and other Charm projects. I have also had the privilege of
> meeting many of you in person, and have shared fruitful exchanges. I have
> signed the Ubuntu Code of Conduct.
>
> Before playing around with Juju I have had a long career in tech from
> which I have experience with both operations and development of system
> level code. I particularly like having my code well tested to make sure it
> keeps on running in the future.
>
> Some examples of my charm-related work:
>
> https://github.com/openstack/charm-neutron-openvswitch/commit/4ffbc2fe25400abf55719a370f3a2cd37f90c99d
>
> https://github.com/openstack/charm-rabbitmq-server/commit/08b10513c5725fb740382668c47fc769a6f2936c
>
> https://github.com/marcoceppi/charm-mysql/commit/cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
>
> https://github.com/marcoceppi/charm-mysql/commit/1a8277855be4020b26121cb9d573cd150b6aa882
>
> https://github.com/openstack/charm-ceph-radosgw/commit/7fa6639ab3fde7dc89131fb204f018fd4339e82f
>
> https://github.com/openstack/charm-keystone/commit/5de1770931e886732870da1909f08279a0b804b4
>
> https://github.com/openstack/charm-nova-cloud-controller/commit/2eef644a5c1acb2675e94908c88182658fec4ac5
>
> https://github.com/openstack/charm-openstack-dashboard/commit/8f3a93ac4e7102736da492a189144220312f93df
>
> https://github.com/openstack/charm-swift-proxy/commit/7c24ae81283710c830ab03f240ec9cc10dccd975
>
> Launchpad ID: fnordahl
>
> --
> Frode Nordahl
> --
> 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: Promulgate request: Grafana

2017-08-30 Thread Tim Van Steenburgh
Done, thanks!

On Wed, Aug 30, 2017 at 4:38 AM, Tom Haddon 
wrote:

> Hi Folks,
> Could we get cs:~prometheus-charmers/grafana promulgated?
>
> The code for the charm is https://code.launchpad.net/grafana-charm and
> there's
> a team that maintains it https://launchpad.net/~prometheus-charmers. That
> team
> already maintains a number of other promulgated charms (mtail, prometheus,
> prometheus-alertmanager, prometheus-push-gateway and
> prometheus-blackbox-exporter). The grafana charm supports trusty and
> xenial.
>
> If anyone is interested in joining the team to help maintain grafana and
> those
> other charms please let us know.
>
> Thanks, Tom
>
> --
> 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: Juju Charmer application

2017-08-30 Thread Alex Kavanagh
+1 from me too.

On Wed, Aug 30, 2017 at 11:14 AM, Frode Nordahl 
wrote:

> Dear Juju community,
>
> I would like to officially apply for membership of the Juju ~charmers team.
>
> Through the course of the past year I have made contributions to the
> OpenStack Charms and other Charm projects. I have also had the privilege of
> meeting many of you in person, and have shared fruitful exchanges. I have
> signed the Ubuntu Code of Conduct.
>
> Before playing around with Juju I have had a long career in tech from
> which I have experience with both operations and development of system
> level code. I particularly like having my code well tested to make sure it
> keeps on running in the future.
>
> Some examples of my charm-related work:
> https://github.com/openstack/charm-neutron-openvswitch/commit/
> 4ffbc2fe25400abf55719a370f3a2cd37f90c99d
> https://github.com/openstack/charm-rabbitmq-server/commit/
> 08b10513c5725fb740382668c47fc769a6f2936c
> https://github.com/marcoceppi/charm-mysql/commit/
> cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
> https://github.com/marcoceppi/charm-mysql/commit/
> 1a8277855be4020b26121cb9d573cd150b6aa882
> https://github.com/openstack/charm-ceph-radosgw/commit/
> 7fa6639ab3fde7dc89131fb204f018fd4339e82f
> https://github.com/openstack/charm-keystone/commit/
> 5de1770931e886732870da1909f08279a0b804b4
> https://github.com/openstack/charm-nova-cloud-controller/commit/
> 2eef644a5c1acb2675e94908c88182658fec4ac5
> https://github.com/openstack/charm-openstack-dashboard/commit/
> 8f3a93ac4e7102736da492a189144220312f93df
> https://github.com/openstack/charm-swift-proxy/commit/
> 7c24ae81283710c830ab03f240ec9cc10dccd975
>
> Launchpad ID: fnordahl
>
> --
> Frode Nordahl
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>


-- 
Alex Kavanagh - Software Engineer
Cloud Dev Ops - Solutions & Product Engineering - Canonical Ltd
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: Juju-gui only show localhost as the deployment option

2017-08-30 Thread fengxia

Akshat,

Just to chip in some of my thoughts on this since we (disclosure, I'm a 
researcher at Lenovo) have had extensive discussions on a similar use 
case and consequently come down to the same challenge as you are 
currently looking at.


1. Juju CLI allows user to select controller, which essentially leads to 
a particular cloud/provider (these two are 1-1 mapping). Therefore, in 
practice it already supports multi-cloud scenario (last time I counted 
12 clouds out of box including local LXD and manual). The catch is, of 
course, the manual step of selecting the proper controller.


2. There are two schools of thought -- whether to have Juju being more 
intelligent so to handle multiple clouds `automatically` (for example, 
in bundle YAML specify which cloud a charm should be deployed to, which 
is one step further than OS series), or using Juju as-is and utilize 
something else as a wrapper to facilitate such mixed-cloud automation. 
The former option minimize tech stack so there is one set of technology 
to learn and manage; the latter gives flexibility, mitigate vendor lock 
in... I think the theme is not new, so it's really a matter of design 
preference


Juju team has done 90% of the heavy liftings. The former will require 
more in-depth of Juju knowledge, the latter requires less. I think the 
requirements, however, is clear, that there is a higher level of 
abstraction required above the current Juju existence so to drive this.




On 08/30/2017 04:27 AM, Akshat Jiwan Sharma wrote:

Thank you Feng,

As I understand for now there is no way to use multiple providers with 
juju either with a GUI or command line.


My goal is to be able to allow users to deploy charms (mostly 
wordpress/drupal/ghost) on a cloud of their choice. Anything that 
allows me to do this is acceptable. The only requirement is maximum 
cloud coverage. So for a multi cloud setup what options do I have?


- Should I go for one controller per cloud setup?
- Can juju api  help me 
write some custom code that'll allow me to do what I want? If so what 
should I be looking for in the documentation?
- Since juju runs in an lxc  would it be a good idea to create clone 
containers that can switch the cloud environment on demand? Or would 
this cause more problems that it'll solve?


Thank you once more for being patient with the questions and for all 
the answers! Much appreciated


Best,
Akshat

On Wed, Aug 30, 2017 at 7:56 AM, fengxia > wrote:


Hi Akshat,

Juju controller does not support multiple cloud/provider. It's
like a switch board, juju can only talk to one controller at a time.

However, I do think there are use case of supporting multiple
clouds with one orchestrator. I'm not sure whether juju team has
sth like that on its roadmap, or maybe using some other tools for
the purpose?
On 08/29/2017 09:59 AM, Akshat Jiwan Sharma wrote:

Is there a way I can configure multiple providers using the
Juju-GUI? Also is there a way I can configure cloud providers
based on user access roles? For example a user with access to a
particular model can deploy only to a specific cloud provider.

If one controller can manage multiple clouds and one controller
can have many users then what is the mapping of the relationship
between the users and the clouds?

Thanks,
Akshat




-- 
Feng xia

Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com 

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums


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





--
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums

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


Re: Juju-gui only show localhost as the deployment option

2017-08-30 Thread fengxia

Akshat,

Just to chip in some of my thoughts on this since we (disclosure, I'm a 
researcher at Lenovo) have had extensive discussions on a similar use 
case and consequently come down to the same challenge as you are 
currently looking at.


1. Juju CLI allows user to select controller, which essentially leads to 
a particular cloud/provider (these two are 1-1 mapping). Therefore, in 
practice it already supports multi-cloud scenario (last time I counted 
12 clouds out of box including local LXD and manual). The catch is, of 
course, the manual step of selecting the proper controller.


2. There are two schools of thought -- whether to have Juju being more 
intelligent so to handle multiple clouds `automatically` (for example, 
in bundle YAML specify which cloud a charm should be deployed to, which 
is one step further than OS series), or using Juju as-is and utilize 
something else as a wrapper to facilitate such mixed-cloud automation. 
The former option minimize tech stack so there is one set of technology 
to learn and manage; the latter gives flexibility, mitigate vendor lock 
in... I think the theme is not new, so it's really a matter of design 
preference


Juju team has done 90% of the heavy liftings. The former will require 
more in-depth of Juju knowledge, the latter requires less. I think the 
requirements, however, is clear, that there is a higher level of 
abstraction required above the current Juju existence so to drive this.




On 08/30/2017 04:27 AM, Akshat Jiwan Sharma wrote:

Thank you Feng,

As I understand for now there is no way to use multiple providers with 
juju either with a GUI or command line.


My goal is to be able to allow users to deploy charms (mostly 
wordpress/drupal/ghost) on a cloud of their choice. Anything that 
allows me to do this is acceptable. The only requirement is maximum 
cloud coverage. So for a multi cloud setup what options do I have?


- Should I go for one controller per cloud setup?
- Can juju api  help me 
write some custom code that'll allow me to do what I want? If so what 
should I be looking for in the documentation?
- Since juju runs in an lxc  would it be a good idea to create clone 
containers that can switch the cloud environment on demand? Or would 
this cause more problems that it'll solve?


Thank you once more for being patient with the questions and for all 
the answers! Much appreciated


Best,
Akshat

On Wed, Aug 30, 2017 at 7:56 AM, fengxia > wrote:


Hi Akshat,

Juju controller does not support multiple cloud/provider. It's
like a switch board, juju can only talk to one controller at a time.

However, I do think there are use case of supporting multiple
clouds with one orchestrator. I'm not sure whether juju team has
sth like that on its roadmap, or maybe using some other tools for
the purpose?
On 08/29/2017 09:59 AM, Akshat Jiwan Sharma wrote:

Is there a way I can configure multiple providers using the
Juju-GUI? Also is there a way I can configure cloud providers
based on user access roles? For example a user with access to a
particular model can deploy only to a specific cloud provider.

If one controller can manage multiple clouds and one controller
can have many users then what is the mapping of the relationship
between the users and the clouds?

Thanks,
Akshat




-- 
Feng xia

Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com 

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums


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





--
Feng xia
Engineer
Lenovo USA

Phone: 5088011794
fx...@lenovo.com

Lenovo.com
Twitter | Facebook | Instagram | Blogs | Forums

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


juju deploy docker

2017-08-30 Thread Micheal B
Running juju vsphere cloud – current CDK

 

Test both

 

Juju deploy docker

And

juju deploy docker --series xenial –force

 

always get

hook failed: "config-changed"

 

Tested other installs

juju add-unit kubernetes-worker  --- install fine

 

check DNS / DHCP all of that appears fine

 

Trying to setup a registery pod if that help.

 

 

Thanks

 

Micheal

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


Re: juju deploy docker

2017-08-30 Thread Rick Harding
Can you check the juju debug-log or juju ssh docker/0 and sudo cat
/var/log/juju/unit-xxx to see what's failed?

It looks like the charm there is hitting an error and will have to debug
what's up by checking the logs.

On Wed, Aug 30, 2017 at 1:02 PM Micheal B  wrote:

> Running juju vsphere cloud – current CDK
>
>
>
> Test both
>
>
>
> Juju deploy docker
>
> And
>
> juju deploy docker --series xenial –force
>
>
>
> always get
>
> hook failed: "config-changed"
>
>
>
> Tested other installs
>
> juju add-unit kubernetes-worker  --- install fine
>
>
>
> check DNS / DHCP all of that appears fine
>
>
>
> Trying to setup a registery pod if that help.
>
>
>
>
>
> Thanks
>
>
>
> Micheal
> --
> 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: Juju-gui only show localhost as the deployment option

2017-08-30 Thread Rick Harding
Just to toss, out. JAAS [1] is built to be Juju as a Service across clouds
doing some of the extra work to enable users to have a single dashboard
across a wide array of clouds and regions. Give it a try and I'd love to
chat about any feedback on where JAAS does or doesn't fit for the needs
you're having.

1: https://jujucharms.com

On Wed, Aug 30, 2017 at 10:59 AM fengxia  wrote:

> Akshat,
>
> Just to chip in some of my thoughts on this since we (disclosure, I'm a
> researcher at Lenovo) have had extensive discussions on a similar use case
> and consequently come down to the same challenge as you are currently
> looking at.
>
> 1. Juju CLI allows user to select controller, which essentially leads to a
> particular cloud/provider (these two are 1-1 mapping). Therefore, in
> practice it already supports multi-cloud scenario (last time I counted 12
> clouds out of box including local LXD and manual). The catch is, of course,
> the manual step of selecting the proper controller.
>
> 2. There are two schools of thought -- whether to have Juju being more
> intelligent so to handle multiple clouds `automatically` (for example, in
> bundle YAML specify which cloud a charm should be deployed to, which is one
> step further than OS series), or using Juju as-is and utilize something
> else as a wrapper to facilitate such mixed-cloud automation. The former
> option minimize tech stack so there is one set of technology to learn and
> manage; the latter gives flexibility, mitigate vendor lock in... I think
> the theme is not new, so it's really a matter of design preference
>
> Juju team has done 90% of the heavy liftings. The former will require more
> in-depth of Juju knowledge, the latter requires less. I think the
> requirements, however, is clear, that there is a higher level of
> abstraction required above the current Juju existence so to drive this.
>
>
>
> On 08/30/2017 04:27 AM, Akshat Jiwan Sharma wrote:
>
> Thank you Feng,
>
> As I understand for now there is no way to use multiple providers with
> juju either with a GUI or command line.
>
> My goal is to be able to allow users to deploy charms (mostly
> wordpress/drupal/ghost) on a cloud of their choice. Anything that allows me
> to do this is acceptable. The only requirement is maximum cloud coverage.
> So for a multi cloud setup what options do I have?
>
> - Should I go for one controller per cloud setup?
> - Can juju api  help me write
> some custom code that'll allow me to do what I want? If so what should I be
> looking for in the documentation?
> - Since juju runs in an lxc  would it be a good idea to create clone
> containers that can switch the cloud environment on demand? Or would this
> cause more problems that it'll solve?
>
> Thank you once more for being patient with the questions and for all the
> answers! Much appreciated
>
> Best,
> Akshat
>
> On Wed, Aug 30, 2017 at 7:56 AM, fengxia  wrote:
>
>> Hi Akshat,
>>
>> Juju controller does not support multiple cloud/provider. It's like a
>> switch board, juju can only talk to one controller at a time.
>> However, I do think there are use case of supporting multiple clouds with
>> one orchestrator. I'm not sure whether juju team has sth like that on its
>> roadmap, or maybe using some other tools for the purpose?
>> On 08/29/2017 09:59 AM, Akshat Jiwan Sharma wrote:
>>
>> Is there a way I can configure multiple providers using the Juju-GUI?
>> Also is there a way I can configure cloud providers based on user access
>> roles? For example a user with access to a particular model can deploy only
>> to a specific cloud provider.
>>
>> If one controller can manage multiple clouds and one controller can have
>> many users then what is the mapping of the relationship between the users
>> and the clouds?
>>
>> Thanks,
>> Akshat
>>
>>
>>
>> --
>> Feng xia
>> Engineer
>> Lenovo USA
>>
>> Phone: 5088011794 <(508)%20801-1794>fx...@lenovo.com
>>  
>> Lenovo.com
>> Twitter | Facebook | Instagram | Blogs | Forums
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
> --
> Feng xia
> Engineer
> Lenovo USA
>
> Phone: 5088011794 <(508)%20801-1794>fx...@lenovo.com
>   
> Lenovo.com
> Twitter | Facebook | Instagram | Blogs | Forums
>
> --
> 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: Elasticsearch Charm Promulgation

2017-08-30 Thread Tim Van Steenburgh
On Wed, Aug 30, 2017 at 6:27 AM, Haw Loeung 
wrote:

> On Tue, Aug 22, 2017 at 08:54:14AM +0100, Tom Haddon wrote:
> > On Mon, Aug 21, 2017 at 02:53:10PM +0100, Tom Haddon wrote:
> > [...]
> > > I checked with some of the ~onlineservices-charmers team and they were
> happy
> > > for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch/ to
> replace
> > > the current promulgated charm (which only supports precise and
> trusty). We
> > > should test that you can successfully charm upgrade from theirs to
> this charm
> > > (on trusty) - I'm happy to take that on, and will update here once
> we've done
> > > so.
> >
> > I've tested an upgrade on trusty from the existing upstream elasticsearch
> > charm to cs:~elasticsearch-charmers/trusty/elasticsearch and it seems
> to work
> > okay:
> >
> > https://pastebin.ubuntu.com/25368096/
> >
>
> I've confirmed that the existing charm also supports ElasticSearch 5.x
> (thanks to all the hard work from Ante).
>
> Any chance we could get cs:~elasticsearch-charmers/elasticsearch
> promulgated to cs:elasticsearch now?
>

I checked with James Beedy and he's +1 on promulgating this one too.

Looks like there's no bugs-url or homepage set on the charm though. Please
add those (see `charm set -h`) and then I'll be happy to promulgate it.


>
>
> Thanks,
>
> Haw
>
> --
> 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: Juju Charmer application

2017-08-30 Thread David Ames
Huge +1

On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl  wrote:
> Dear Juju community,
>
> I would like to officially apply for membership of the Juju ~charmers team.
>
> Through the course of the past year I have made contributions to the
> OpenStack Charms and other Charm projects. I have also had the privilege of
> meeting many of you in person, and have shared fruitful exchanges. I have
> signed the Ubuntu Code of Conduct.
>
> Before playing around with Juju I have had a long career in tech from which
> I have experience with both operations and development of system level code.
> I particularly like having my code well tested to make sure it keeps on
> running in the future.
>
> Some examples of my charm-related work:
> https://github.com/openstack/charm-neutron-openvswitch/commit/4ffbc2fe25400abf55719a370f3a2cd37f90c99d
> https://github.com/openstack/charm-rabbitmq-server/commit/08b10513c5725fb740382668c47fc769a6f2936c
> https://github.com/marcoceppi/charm-mysql/commit/cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
> https://github.com/marcoceppi/charm-mysql/commit/1a8277855be4020b26121cb9d573cd150b6aa882
> https://github.com/openstack/charm-ceph-radosgw/commit/7fa6639ab3fde7dc89131fb204f018fd4339e82f
> https://github.com/openstack/charm-keystone/commit/5de1770931e886732870da1909f08279a0b804b4
> https://github.com/openstack/charm-nova-cloud-controller/commit/2eef644a5c1acb2675e94908c88182658fec4ac5
> https://github.com/openstack/charm-openstack-dashboard/commit/8f3a93ac4e7102736da492a189144220312f93df
> https://github.com/openstack/charm-swift-proxy/commit/7c24ae81283710c830ab03f240ec9cc10dccd975
>
> Launchpad ID: fnordahl
>
> --
> Frode Nordahl
>
> --
> 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: Juju Charmer application

2017-08-30 Thread Tim Van Steenburgh
Thanks Frode, welcome to ~charmers!

On Wed, Aug 30, 2017 at 4:10 PM, David Ames 
wrote:

> Huge +1
>
> On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl 
> wrote:
> > Dear Juju community,
> >
> > I would like to officially apply for membership of the Juju ~charmers
> team.
> >
> > Through the course of the past year I have made contributions to the
> > OpenStack Charms and other Charm projects. I have also had the privilege
> of
> > meeting many of you in person, and have shared fruitful exchanges. I have
> > signed the Ubuntu Code of Conduct.
> >
> > Before playing around with Juju I have had a long career in tech from
> which
> > I have experience with both operations and development of system level
> code.
> > I particularly like having my code well tested to make sure it keeps on
> > running in the future.
> >
> > Some examples of my charm-related work:
> > https://github.com/openstack/charm-neutron-openvswitch/commit/
> 4ffbc2fe25400abf55719a370f3a2cd37f90c99d
> > https://github.com/openstack/charm-rabbitmq-server/commit/
> 08b10513c5725fb740382668c47fc769a6f2936c
> > https://github.com/marcoceppi/charm-mysql/commit/
> cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
> > https://github.com/marcoceppi/charm-mysql/commit/
> 1a8277855be4020b26121cb9d573cd150b6aa882
> > https://github.com/openstack/charm-ceph-radosgw/commit/
> 7fa6639ab3fde7dc89131fb204f018fd4339e82f
> > https://github.com/openstack/charm-keystone/commit/
> 5de1770931e886732870da1909f08279a0b804b4
> > https://github.com/openstack/charm-nova-cloud-controller/commit/
> 2eef644a5c1acb2675e94908c88182658fec4ac5
> > https://github.com/openstack/charm-openstack-dashboard/commit/
> 8f3a93ac4e7102736da492a189144220312f93df
> > https://github.com/openstack/charm-swift-proxy/commit/
> 7c24ae81283710c830ab03f240ec9cc10dccd975
> >
> > Launchpad ID: fnordahl
> >
> > --
> > Frode Nordahl
> >
> > --
> > 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: Juju-gui only show localhost as the deployment option

2017-08-30 Thread Giuseppe Attardi
I have a slightly different requirement.
Currently in our OpenStack cloud, if a user wants to use Juju, it must install 
a Juju controller in his project.
It would be useful to use a single controller for the whole cloud and to just 
switch the project which the controller uses.
Juju already can deal with multiple models, so it would just need to 
distinguish which models exist in a given project.
It also should be possible to authenticate with OpenStack credentials in the 
Juju GUI.

— Beppe

> Date: Tue, 29 Aug 2017 19:29:14 +0530
> From: Akshat Jiwan Sharma 
> To: juju@lists.ubuntu.com
> Subject: Juju-gui only show localhost as the deployment option
> Message-ID:
>   
> Content-Type: text/plain; charset="utf-8"
> 
> Is there a way I can configure multiple providers using the Juju-GUI? Also
> is there a way I can configure cloud providers based on user access roles?
> For example a user with access to a particular model can deploy only to a
> specific cloud provider.
> 
> If one controller can manage multiple clouds and one controller can have
> many users then what is the mapping of the relationship between the users
> and the clouds?
> 
> Thanks,
> Akshat
> 



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


Re: Elasticsearch Charm Promulgation

2017-08-30 Thread Haw Loeung
On Wed, Aug 30, 2017 at 02:38:42PM -0400, Tim Van Steenburgh wrote:
> I checked with James Beedy and he's +1 on promulgating this one too.
>
> Looks like there's no bugs-url or homepage set on the charm though. Please
> add those (see `charm set -h`) and then I'll be happy to promulgate it.

I've updated the two:

| $ charm show cs:~elasticsearch-charmers/elasticsearch bugs-url homepage
| bugs-url: https://bugs.launchpad.net/elasticsearch-charm
| homepage: https://launchpad.net/elasticsearch-charm


Regards,

Haw


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


Re: Elasticseach Charm Promulgation - things to keep in mind

2017-08-30 Thread James Beedy
Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default
configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch
may break any bundles that have elasticsearch + kibana not pinned to a
specific charm store uri/rev upon promulgation.

This probably won't affect many, just thought I would put it out there.
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: Elasticseach Charm Promulgation - things to keep in mind

2017-08-30 Thread James Beedy
Also - https://bugs.launchpad.net/elasticsearch-charm/+bug/1714126

On Wed, Aug 30, 2017 at 6:47 PM, James Beedy  wrote:

> Elasticsearch >= 5.x is non-compat with kibana <= 5.x. The current default
> configs for https://jujucharms.com/u/elasticsearch-charmers/elasticsearch
> may break any bundles that have elasticsearch + kibana not pinned to a
> specific charm store uri/rev upon promulgation.
>
> This probably won't affect many, just thought I would put it out there.
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


We are pleased to announce the release of Juju 1.25.13

2017-08-30 Thread Chris Lee
Hi all,

Today we released Juju 1.25.13 which addressed some memory leak bugs.

For a list of all bugs fixed in these release see:
https://launchpad.net/juju-core/+milestone/1.25.13


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


Re: Juju Charmer application

2017-08-30 Thread Billy Olsen
It's a bit late, but I'd like to give an enthusiastic +1 as well

On Wed, Aug 30, 2017 at 1:50 PM Tim Van Steenburgh <
tim.van.steenbu...@canonical.com> wrote:

> Thanks Frode, welcome to ~charmers!
>
> On Wed, Aug 30, 2017 at 4:10 PM, David Ames 
> wrote:
>
>> Huge +1
>>
>> On Wed, Aug 30, 2017 at 3:14 AM, Frode Nordahl 
>> wrote:
>> > Dear Juju community,
>> >
>> > I would like to officially apply for membership of the Juju ~charmers
>> team.
>> >
>> > Through the course of the past year I have made contributions to the
>> > OpenStack Charms and other Charm projects. I have also had the
>> privilege of
>> > meeting many of you in person, and have shared fruitful exchanges. I
>> have
>> > signed the Ubuntu Code of Conduct.
>> >
>> > Before playing around with Juju I have had a long career in tech from
>> which
>> > I have experience with both operations and development of system level
>> code.
>> > I particularly like having my code well tested to make sure it keeps on
>> > running in the future.
>> >
>> > Some examples of my charm-related work:
>> >
>> https://github.com/openstack/charm-neutron-openvswitch/commit/4ffbc2fe25400abf55719a370f3a2cd37f90c99d
>> >
>> https://github.com/openstack/charm-rabbitmq-server/commit/08b10513c5725fb740382668c47fc769a6f2936c
>> >
>> https://github.com/marcoceppi/charm-mysql/commit/cefb77fafcd1ee36d4dc30c14d07aa857d5273a2
>> >
>> https://github.com/marcoceppi/charm-mysql/commit/1a8277855be4020b26121cb9d573cd150b6aa882
>> >
>> https://github.com/openstack/charm-ceph-radosgw/commit/7fa6639ab3fde7dc89131fb204f018fd4339e82f
>> >
>> https://github.com/openstack/charm-keystone/commit/5de1770931e886732870da1909f08279a0b804b4
>> >
>> https://github.com/openstack/charm-nova-cloud-controller/commit/2eef644a5c1acb2675e94908c88182658fec4ac5
>> >
>> https://github.com/openstack/charm-openstack-dashboard/commit/8f3a93ac4e7102736da492a189144220312f93df
>> >
>> https://github.com/openstack/charm-swift-proxy/commit/7c24ae81283710c830ab03f240ec9cc10dccd975
>> >
>> > Launchpad ID: fnordahl
>> >
>> > --
>> > Frode Nordahl
>> >
>> > --
>> > 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
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju