Re: Create Juju Charms from your browser!

2017-02-05 Thread Andrew Wilkins
On Fri, Feb 3, 2017 at 10:14 PM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi all
>
>
> I've been looking at Eclipse Che for a while, it is a cloud Workspace and
> IDE from the Eclipse Foundation. An IDE that runs in your browser, with
> docker containers as workspaces.
>
> It's a great way to lower the barrier for new developers. Open Che in your
> browser, choose the stack you want, and start coding.
>
> I've created a Charm that deploys Eclipse Che and creates a stack that has
> everything you need to start Charming. The stack is based on the `charmbox`
> Docker container.
>
> Eclipse Che Charm: https://jujucharms.com/u/tengu-team/eclipse-che/
> Eclipse Che Layer: https://github.com/IBCNServices/layer-eclipse-che
>
> Check it out and let me know what you think of it!
>

Very cool, thanks for sharing.

A few things which I think would make this even better:
 - integration with Ubuntu SSO (or GitHub OAuth, etc.)
 - with above: inject macaroon/token into the charmbox container, so that
the juju CLI would be automatically logged in (would only work with
external identity management)
 - with above: Right-click "Deploy to Juju", with detection of changes to
deployed code and an option to update.

... in case anyone has spare time ;)

Cheers,
Andrew


> Kind regards
> Merlijn
> --
> 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: I still can't upload resources to the Charm store.

2017-02-05 Thread Merlijn Sebrechts
Ok, thanks for the info!

2017-02-05 19:09 GMT+01:00 Adam Stokes :

> I think your issue is the one that Cory reported on about the resource
> being to big of a blob for the charm store to process. I think his resource
> was at 90M while yours is 720M. See here: https://github.com/
> CanonicalLtd/jujucharms.com/issues/332
>
> According to the bug it doesn't seem like a trivial fix so it may take
> some time but the right people are aware of it and will get it addressed.
>
> On Sun, Feb 5, 2017 at 10:58 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Update: Specified the specific revision in my push command and now it
>> fails in a different way:
>>
>>
>> $charm attach ~tengu-team/apache-nifi-1 apache-nifi=./nifi-1.1.1-bin.
>> tar.gz
>> ERROR can't upload resource: cannot post resource: cannot unmarshal error
>> response "> 2.0//EN\">\n\n502 Proxy 
>> Error\n\nProxy
>> Error\nThe proxy server received an invalid\r\nresponse from an
>> upstream server.\r\nThe proxy server could not handle the request
>> > apache-nifi\">POST /charmstore/v5/~tengu-team/
>> apache-nifi-1/resource/apache-nifi.\nReason: Error
>> reading from remote server\n\nApache/2.4.7
>> (Ubuntu) Server at api.jujucharms.com Port 443\n\n":
>> invalid character '<' looking for beginning of value
>>
>>
>>
>> 2017-02-05 15:51 GMT+01:00 Adam Stokes :
>>
>> https://github.com/juju/charmstore-client/issues/96
>>
>> No one from that team has provided any additional input, even though I've
>> been asking and this is obviously a huge problem for users in general.
>>
>> On Sun, Feb 5, 2017, 8:13 AM Merlijn Sebrechts <
>> merlijn.sebrec...@gmail.com> wrote:
>>
>> Hi all
>>
>>
>> Uploading resources to the Charm store still fails for me. It seems this
>> is still the same error that I had back in Juli:
>> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.
>>
>> What I run:
>>
>> wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
>> charm attach ~tengu-team/apache-nifi apache-nifi=./nifi-1.1.1-bin.tar.gz
>>
>> What I get:
>>
>> ERROR can't upload resource: cannot post resource: cannot unmarshal error
>> response "> 2.0//EN\">\n\n502 Bad 
>> Gateway\n\nBad
>> Gateway\nThe proxy server received an invalid\r\nresponse from an
>> upstream server.\r\n\n\nApache/2.4.7 (Ubuntu)
>> Server at api.jujucharms.com Port 443\n\n":
>> invalid character '<' looking for beginning of value
>>
>>
>> --
>> 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: I still can't upload resources to the Charm store.

2017-02-05 Thread Adam Stokes
I think your issue is the one that Cory reported on about the resource
being to big of a blob for the charm store to process. I think his resource
was at 90M while yours is 720M. See here:
https://github.com/CanonicalLtd/jujucharms.com/issues/332

According to the bug it doesn't seem like a trivial fix so it may take some
time but the right people are aware of it and will get it addressed.

On Sun, Feb 5, 2017 at 10:58 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Update: Specified the specific revision in my push command and now it
> fails in a different way:
>
>
> $charm attach ~tengu-team/apache-nifi-1
> apache-nifi=./nifi-1.1.1-bin.tar.gz
> ERROR can't upload resource: cannot post resource: cannot unmarshal error
> response " 2.0//EN\">\n\n502 Proxy
> Error\n\nProxy Error\nThe proxy server
> received an invalid\r\nresponse from an upstream server.\r\nThe proxy
> server could not handle the request  href=\"/charmstore/v5/~tengu-team/apache-nifi-1/resource/apache-nifi\">POST /charmstore/v5/~tengu-team/apache-nifi-1/resource/apache-nifi.\nReason:
> Error reading from remote
> server\n\nApache/2.4.7 (Ubuntu) Server at
> api.jujucharms.com Port 443\n\n": invalid
> character '<' looking for beginning of value
>
>
>
> 2017-02-05 15:51 GMT+01:00 Adam Stokes :
>
> https://github.com/juju/charmstore-client/issues/96
>
> No one from that team has provided any additional input, even though I've
> been asking and this is obviously a huge problem for users in general.
>
> On Sun, Feb 5, 2017, 8:13 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
> Hi all
>
>
> Uploading resources to the Charm store still fails for me. It seems this
> is still the same error that I had back in Juli:
> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.
>
> What I run:
>
> wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
> charm attach ~tengu-team/apache-nifi apache-nifi=./nifi-1.1.1-bin.tar.gz
>
> What I get:
>
> ERROR can't upload resource: cannot post resource: cannot unmarshal error
> response " 2.0//EN\">\n\n502 Bad
> Gateway\n\nBad Gateway\nThe proxy server
> received an invalid\r\nresponse from an upstream server. />\r\n\n\nApache/2.4.7 (Ubuntu) Server at
> api.jujucharms.com Port 443\n\n": invalid
> character '<' looking for beginning of value
>
>
> --
> 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: I still can't upload resources to the Charm store.

2017-02-05 Thread Merlijn Sebrechts
Update: Specified the specific revision in my push command and now it fails
in a different way:


$charm attach ~tengu-team/apache-nifi-1 apache-nifi=./nifi-1.1.1-bin.tar.gz
ERROR can't upload resource: cannot post resource: cannot unmarshal error
response "\n\n502 Proxy
Error\n\nProxy Error\nThe proxy server
received an invalid\r\nresponse from an upstream server.\r\nThe proxy
server could not handle the request POST /charmstore/v5/~tengu-team/apache-nifi-1/resource/apache-nifi.\nReason:
Error reading from remote
server\n\nApache/2.4.7 (Ubuntu) Server at
api.jujucharms.com Port 443\n\n": invalid character
'<' looking for beginning of value



2017-02-05 15:51 GMT+01:00 Adam Stokes :

> https://github.com/juju/charmstore-client/issues/96
>
> No one from that team has provided any additional input, even though I've
> been asking and this is obviously a huge problem for users in general.
>
> On Sun, Feb 5, 2017, 8:13 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Hi all
>>
>>
>> Uploading resources to the Charm store still fails for me. It seems this
>> is still the same error that I had back in Juli:
>> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.
>>
>> What I run:
>>
>> wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
>> charm attach ~tengu-team/apache-nifi apache-nifi=./nifi-1.1.1-bin.tar.gz
>>
>> What I get:
>>
>> ERROR can't upload resource: cannot post resource: cannot unmarshal error
>> response "> 2.0//EN\">\n\n502 Bad 
>> Gateway\n\nBad
>> Gateway\nThe proxy server received an invalid\r\nresponse from an
>> upstream server.\r\n\n\nApache/2.4.7 (Ubuntu)
>> Server at api.jujucharms.com Port 443\n\n":
>> invalid character '<' looking for beginning of value
>>
>>
>> --
>> 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: I still can't upload resources to the Charm store.

2017-02-05 Thread Mark Shuttleworth

Thanks for the reminder, will ask the store team to root cause it this time.

Mark

On 05/02/17 13:12, Merlijn Sebrechts wrote:
> Hi all
>
>
> Uploading resources to the Charm store still fails for me. It seems
> this is still the same error that I had back in Juli:
> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.
>
> What I run:
>
> wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
> charm attach ~tengu-team/apache-nifi
> apache-nifi=./nifi-1.1.1-bin.tar.gz
>
> What I get:
>
> ERROR can't upload resource: cannot post resource: cannot
> unmarshal error response " HTML 2.0//EN\">\n\n502 Bad
> Gateway\n\nBad Gateway\nThe proxy
> server received an invalid\r\nresponse from an upstream server. />\r\n\n\nApache/2.4.7 (Ubuntu) Server at
> api.jujucharms.com  Port
> 443\n\n": invalid character '<' looking
> for beginning of value
>
>
>
>

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


Re: I still can't upload resources to the Charm store.

2017-02-05 Thread Adam Stokes
https://github.com/juju/charmstore-client/issues/96

No one from that team has provided any additional input, even though I've
been asking and this is obviously a huge problem for users in general.

On Sun, Feb 5, 2017, 8:13 AM Merlijn Sebrechts 
wrote:

> Hi all
>
>
> Uploading resources to the Charm store still fails for me. It seems this
> is still the same error that I had back in Juli:
> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.
>
> What I run:
>
> wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
> charm attach ~tengu-team/apache-nifi apache-nifi=./nifi-1.1.1-bin.tar.gz
>
> What I get:
>
> ERROR can't upload resource: cannot post resource: cannot unmarshal error
> response " 2.0//EN\">\n\n502 Bad
> Gateway\n\nBad Gateway\nThe proxy server
> received an invalid\r\nresponse from an upstream server. />\r\n\n\nApache/2.4.7 (Ubuntu) Server at
> api.jujucharms.com Port 443\n\n": invalid
> character '<' looking for beginning of value
>
>
> --
> 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


I still can't upload resources to the Charm store.

2017-02-05 Thread Merlijn Sebrechts
Hi all


Uploading resources to the Charm store still fails for me. It seems this is
still the same error that I had back in Juli:
https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822.

What I run:

wget http://apache.belnet.be/nifi/1.1.1/nifi-1.1.1-bin.tar.gz
charm attach ~tengu-team/apache-nifi apache-nifi=./nifi-1.1.1-bin.tar.gz

What I get:

ERROR can't upload resource: cannot post resource: cannot unmarshal error
response "\n\n502 Bad
Gateway\n\nBad Gateway\nThe proxy server
received an invalid\r\nresponse from an upstream server.\r\n\n\nApache/2.4.7 (Ubuntu) Server at
api.jujucharms.com Port 443\n\n": invalid character
'<' looking for beginning of value
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju


Re: Juju 2.1-beta5 is here

2017-02-05 Thread Narinder Gupta
Thank you john "": internal-api option help me putting my application with
lxd in internal-api network. In that way i can control the applications
interface where i want to. I am hoping we will be documenting this
knowledge somewhere?

Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Sun, Feb 5, 2017 at 1:21 AM, John Meinel  wrote:

> You're using local charms (./xenial/mongodb) so it's hard to know for sure
> exactly what you're deploying without having the full set of files.
>
> If it is the same as the "official" mongodb: https://jujucharms.
> com/mongodb/
> Then it has several bindings that aren't listed in your bundle. Your
> bundle states:
>
>   bindings:
> internal: internal-api
> shared-db: internal-api
> public: internal-api
> admin: internal-api
>
> However, the upstream charm https://api.jujucharms.
> com/charmstore/v5/mongodb/archive/metadata.yaml has:
>   nrpe-external-master
>   database
>   configsvr
>   data
>   benchmark
>
>   mongos-cfg
>   mongos
>
>   replica-set
>
> Now, these clearly are slightly different, as the upstream mongodb doesn't
> have an "internal", "public", or "admin", and those all look very
> suspiciously like very generic bindings on Openstack charms (which may or
> may not be relevant on the mongdb charm.)
>
> I'll also note that "juju deploy" appears to not be strict about
> "bindings". If a value listed in bindings matches an endpoint, we will use
> it, but we don't warn or fail if a name listed in bundle.yaml doesn't exist.
>
> However, you can bind all endpoints of a service using "" as the binding
> name. So you should be able to do:
>
> mongodb:
>   charm: ./xenial/mongodb
>   num_units: 1
>   bindings:
> "": internal-api
>   to:
> - "lxd:nodes/0"
>
> The "" binding will set a default binding for all endpoints in the
> application. You should be able to mix it with concrete bindings as well,
> so if you wanted to change one of them, you should be able to do (eg):
>
> mongodb:
>   charm: ./xenial/mongodb
>   num_units: 1
>   bindings:
> "": internal-api
> shared-db: admin-api
>   to:
> - "lxd:nodes/0"
>
> John
> =:->
>
>
> On Sat, Feb 4, 2017 at 2:14 PM, Narinder Gupta <
> narinder.gu...@canonical.com> wrote:
>
>> Hi Nicholas,
>> I am finding issues when do the deployment. Bundle i used to deploy with
>> juju 2.1-beta4 does not get deployed with juju-2.1-beta5.
>>
>> Reason of that is mongodb lxd container still waiting to get machine
>> which was not the case for juju 2.1-beta4
>> mongodb/0 waiting  allocating  0/lxd/3
>>   waiting for machine
>>
>> You can see here http://pastebin.ubuntu.com/23924329/ all services came
>> up except mongodb and openfv-promise. I can confirm that if I switch to
>> beta4 everything works. Here is the bundle i am deploying
>> http://paste.ubuntu.com/23924334/
>>
>>
>>
>> Thanks and Regards,
>> Narinder Gupta (PMP)   narinder.gu...@canonical.com
>> Canonical, Ltd.narindergupta 
>> [irc.freenode.net]+1.281.736.5150 <(281)%20736-5150> 
>>narindergupta2007[skype]
>>
>> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
>>
>>
>> On Fri, Feb 3, 2017 at 5:54 PM, Nicholas Skaggs <
>> nicholas.ska...@canonical.com> wrote:
>>
>>> The Juju team would like to introduce Juju and conjure-up 2.1-beta5! The
>>> most visible changes are to container networking and that juju controllers
>>> now expose Prometheus metrics over an HTTPS endpoint. Finally, conjure-up
>>> is also a snap, provides juju, and can be installed on trusty as a snap as
>>> well!
>>>
>>> We would especially like feedback on the container networking changes.
>>> Do let us know of your experiences, and feel free to open bugs and threads
>>> to discuss.
>>>
>>> ## What’s New in Beta 5
>>>
>>> [conjure-up] Now snapped for Trusty and Xenial.
>>> [conjure-up] Support for Canonical Kubernetes 1.5.2.
>>> [conjure-up] Ability to teardown models with the new `conjure-down`
>>> command.
>>> [juju] Container networking improvements:
>>> - LXD and KVM guests no longer join all spaces on the host
>>> machine, but use constraints and bindings to determine what spaces should
>>> be used
>>> - Bridges are not created during provisioning, but only created on
>>> demand for containers that will use them.
>>> - For clouds other than MAAS, we continue to put containers onlocal
>>> bridges (lxdbr0)
>>>[juju] Juju ssh/scp now selects correct address to use to connect to
>>> the controller.
>>> [juju] Model config now supports an "extra-info" field for holding
>>> additional metadata.
>>> [juju] More m