Re: juju as a web service

2014-10-23 Thread Sebastian
Hey folks!

I think that Juju can bring a hole new era for devs and ops, but devs need
something more than charms, they need a bridge between Juju and their
automation (Continues Integration / Delivery) tools in order to deploy
their applications, like a PaaS does.

We are working to deliver Juju and StriderCD to empower people to innovate.

*JaaS: *http://unbouncepages.com/jaas

Cheers,
Sebas.

2014-07-09 12:15 GMT-03:00 Sebastian :

> Juju as a service is a real need, i started that project some months ago.
>
> we are planning to release an MVP in the next two months :)
>
> Abs,
> Sebas.
> Em 09/07/2014 11:47, "Adam Stokes"  escreveu:
>
> We also have a python3 version hosted at:
>>
>> https://github.com/Ubuntu-Solutions-Engineering/macumba
>>
>> It's what Ubuntu Openstack Installer is switching to for its internal
>> juju communication.
>>
>> On Wed, Jul 9, 2014 at 9:28 AM, Mark Shuttleworth 
>> wrote:
>> > On 09/07/14 13:52, Andrew Wilkins wrote:
>> >> Juju has a websocket API that you can use to perform the same
>> operations as
>> >> the CLI can.
>> >>
>> >> There are Go and Python client APIs. The Go one is in the core
>> repository,
>> >> and the Python one is here: https://launchpad.net/python-jujuclient
>> >
>> > Batteries included. No extra charge :)
>> >
>> > Mark
>> >
>> > --
>> > Juju mailing list
>> > Juju@lists.ubuntu.com
>> > Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>>
>> --
>> [ Adam Stokes ]
>>
>> --
>> 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 devel 1.21-alpha2 is available

2014-10-23 Thread Tim Penhey
On 24/10/14 13:37, Curtis Hovey-Canonical wrote:
> A new development release of Juju, juju-core 1.21-alpha2, is now
> available. This release replaces 1.21-alpha1.
> Multiple-user Support
> 
> Juju now supports multiple people connecting to the environment with
> their own identity and credentials.
> 
> When an environment is bootstrapped the “admin” user is created (this
> will change with 1.22 to reflect the name of the logged in user).
> 
> Even though we have multiple users, we do not yet support fine grain
> permissions.  These will come in time, and do depend on this work. The
> only permission checked at this stage is that it is only the state
> server administrator user that was created during bootstrap that is
> able to create or disable other users. Any user is now able to change
> their own password.
> 
> The user commands are grouped under the 'juju user' command:
> 
> juju user
> usage: juju user  ...
> purpose: manage user accounts and access control
> 
> "juju user" is used to manage the user accounts and access control
> in the Juju environment.
> 
> commands:
> add - adds a user
> change-password - changes the password of the current user
> disable - disable a user to stop the user logging in
> enable  - reenables a disabled user to allow the user
>   to log in
> help- show help on a command or other topic
> info- shows information on a user
> list- shows all users

These notes were written while the list command was approved but not yet
landed.  I'm not entirely sure if the 'juju user list' command made it
into the -alpha2 release or not.  If not, never fear, it will be in
-alpha3 (and the 1.21 full release).

Tim

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


Juju devel 1.21-alpha2 is available

2014-10-23 Thread Curtis Hovey-Canonical
A new development release of Juju, juju-core 1.21-alpha2, is now
available. This release replaces 1.21-alpha1.


Getting Juju

juju-core 1.21-alpha2 is available for utopic and backported to earlier
series in the following PPA:

https://launchpad.net/~juju/+archive/devel

Upgrading from stable releases to devel releases is not
supported. You can upgrade test environments to development releases
to test new features and fixes, but it is not advised to upgrade
production environments to 1.21-alpha2.

The devel packages in this archive use the devel simple-streams.
You must configure the 'agent-metadata-url' option in your
environments.yaml to use the matching juju tools.

agent-metadata-url: https://streams.canonical.com/juju/devel/tools

'tools-metadata-url' was renamed to 'agent-metadata-url'.


Notable Changes

* Provider storage is no longer mandatory (for new providers)
* AWS now defaults to using images with SSD storage
* The juju ensure-availability command now supports placement directive
* Automatic placement using MAAS zones
* Various apt improvements
* Improved use of availability zones on Openstack
* The api-info command shows the settings used to connect to juju
* state-server Multiple users are now supported.


Provider storage is no longer mandatory (for new providers)

Storage associated with a particular cloud (S3 for AWS, Swift for
Openstack etc) was a mandatory requirement when developing a provider to
allow Juju to deploy workloads to any particular cloud platform. This
requirement is no longer necessary. Although existing providers still
use cloud storage (to some extent), new providers can be written without
needing to provide a storage implementation.

Upgrading existing environments will take longer than normal because
the state-server will migrate data from the old storage location. During
this time status will report that the upgrade will be retried over many
minutes:

Upgrade to 1.21-alpha2 failed (will retry): migrate tools into
environment storage: cannot find tools in provider storage: no tools
available


AWS now defaults to using images with SSD storage

When deploying workloads onto AWS, images with SSD volumes are now
preferred. If no such image are available, an image using EBS storage
will be used as a fallback.


The juju ensure-availability command now supports placement directive

Just as 'juju bootstrap' supports the ability to specify a particular
node using '--to' placement directives, so too can
'juju ensure-availability' specify a comma separate list of machine to
use for any newly required state servers.
For example:

juju ensure-availability -n 3 --to name1,name2


Automatic placement using MAAS zones

The MAAS provider is now on par with AWS and Openstack providers in
supporting automatic placement using zones.


Various apt improvements

You can now configure 'apt-mirror' in environments.yaml to specify the
mirror used by all the machines provisioned in the environment.

apt-mirror: http://my.archive.ubuntu.com

On precise, the cloud tools archive is now pinned before calling apt
upgrade to ensure its packages are a lower priority than the default
precise archives. Charms developed on precise will see the same packages
when deployed into a juju provisioned machine. If your precise charm
requires packages from the cloud tool's archive, you can use the
'target-release' option to specify the archive to select.

apt-get --target-release precise-updates/cloud-tools my-package

The local-provider skips apt updates and upgrades by default for faster
provisioning. 1.21-alpha1 introduced the ability to disable apt upgrades
and updates for faster provisioning. The default for local provider
were both false. This release introduces a default of true for apt
update operations for local provider. If you wish to enable updates and
upgrades in your local development, update your environments.yaml.

enable-os-upgrade: true
enable-os-refresh-update: true


Improved use of availability zones on Openstack

The Openstack provider now attempts to start instances in all available
zones until it finds one that succeeds, rather than trying just the
first zone and failing. This aligns Openstack behavior with what was
already done for AWS.


The api-info command shows the settings used to connect to juju
state-server.

The 'juju api-info' command shows the settings used to connect to the
juju state-server's API. You can see the settings for all the fields
(except for password) like so:

juju api-info

If you want to see the password being used, you need to either use the
'--password' option

juju api-info --password

Or specify the password field as the only field to show

juju api-info password

You can learn the value of any field by including it in the command
line. For example, to learn the name of user created during bootstrap,
type

juju api-info user


Multiple-user Support

Juju now supports multiple people connecti

Re: [Review Queue] hpcc

2014-10-23 Thread Antonio Rosales
On Thu, Oct 23, 2014 at 5:22 PM, Charles Butler
 wrote:
> I've been watching this one develop, and it was indeed a long road to
> promulgation.
>
> Congrats on the win Xiaoming Wang!

+1, well done charm Xiaoming Wang.

-Antonio

>
> Go Big Data indeed!
>
> On Thu, Oct 23, 2014 at 2:06 PM, Matt Bruzek 
> wrote:
>>
>> I spent some time reviewing the High Performance Computing Cluster (HPCC)
>> charm today.  For those that do not know HPCC is a player in Big Data as an
>> alternative platform to Hadoop.
>>
>> The review passed and hpcc is the newest charm in the charm store!
>>
>> https://bugs.launchpad.net/charms/+bug/1272083
>>
>> This charm requires a minimum of 4GB nodes to deploy all the thor and
>> roxie processes so you will have to use the constraints flag to deploy it
>> from juju on a cloud properly.  All this is documented in the well written
>> README.md file inside the charm.
>>
>> Thanks to the developer Xiaoming Wang for all the work and the patience
>> with the review process!
>>
>> Go big data!
>>
>>- Matt Bruzek 
>>
>> --
>> 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
>



-- 
Antonio Rosales
Juju Ecosystem
Canonical

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


Re: [Review Queue] hpcc

2014-10-23 Thread Charles Butler
I've been watching this one develop, and it was indeed a long road to
promulgation.

Congrats on the win Xiaoming Wang!

Go Big Data indeed!

On Thu, Oct 23, 2014 at 2:06 PM, Matt Bruzek 
wrote:

> I spent some time reviewing the High Performance Computing Cluster (HPCC)
> charm today.  For those that do not know HPCC 
> is a player in Big Data as an alternative platform to Hadoop.
>
> The review passed and hpcc is the newest charm in the charm store!
>
> https://bugs.launchpad.net/charms/+bug/1272083
>
> This charm requires a minimum of 4GB nodes to deploy all the thor and
> roxie processes so you will have to use the constraints flag to deploy it
> from juju on a cloud properly.  All this is documented in the well written
> README.md file inside the charm.
>
> Thanks to the developer Xiaoming Wang for all the work and the patience
> with the review process!
>
> Go big data!
>
>- Matt Bruzek 
>
> --
> 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] hpcc

2014-10-23 Thread Matt Bruzek
I spent some time reviewing the High Performance Computing Cluster (HPCC)
charm today.  For those that do not know HPCC 
is a player in Big Data as an alternative platform to Hadoop.

The review passed and hpcc is the newest charm in the charm store!

https://bugs.launchpad.net/charms/+bug/1272083

This charm requires a minimum of 4GB nodes to deploy all the thor and roxie
processes so you will have to use the constraints flag to deploy it from
juju on a cloud properly.  All this is documented in the well written
README.md file inside the charm.

Thanks to the developer Xiaoming Wang for all the work and the patience
with the review process!

Go big data!

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


Charm School Tomorrow: Relationships / Interfaces

2014-10-23 Thread José Antonio Rey
Hey guys!

Just as a heads up, we will be having a Charm School tomorrow about
Relationships / Interfaces and how to pass information inbetween charms.
You will be able to see the livestream at ubuntuonair.com and ask all your
questions at #ubuntu-on-air on irc.freenode.net. If you have any questions,
feel free to ask.

See you there!

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


Re: bzr | No such source package

2014-10-23 Thread saurabh
It's so good to be among you guys. I have resolved most of my queries 
here so I would like to thank you all.

Have pushed my charms, just waiting for the reviewers and charmers.

Thanks again,
Saurabh
On Thursday 23 October 2014 05:51 PM, Matthew Williams wrote:

saurabh,

No problem at all, Please feel free to come back to the list if you 
have any more questions/ problems. We're here to help


Thanks

Matty

On Thu, Oct 23, 2014 at 1:08 PM, saurabh > wrote:


I figured it out, sorry for the noise.


On Thursday 23 October 2014 05:15 PM, saurabh wrote:

Hi People,

I am getting this strange error when I am trying to push my
charm to launchpad.
"bzr: ERROR: Invalid url supplied to transport:
"lp:~jhasaurabh/charms/trusty/myCharm/trunk": No such source
package myChram.

I have followed all the steps from
https://juju.ubuntu.com/docs/authors-charm-store.html.

bzr whoami gives this output "jhasaurabh
saurabh.ku...@techblue.co.uk
".
What am I doing wrong?

TIA


-- 
Saurabh Kumar

System Admin


-- 
Juju mailing list

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




--
Saurabh Kumar
System Admin

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


Re: bzr | No such source package

2014-10-23 Thread Matthew Williams
saurabh,

No problem at all, Please feel free to come back to the list if you have
any more questions/ problems. We're here to help

Thanks

Matty

On Thu, Oct 23, 2014 at 1:08 PM, saurabh 
wrote:

> I figured it out, sorry for the noise.
>
>
> On Thursday 23 October 2014 05:15 PM, saurabh wrote:
>
>> Hi People,
>>
>> I am getting this strange error when I am trying to push my charm to
>> launchpad.
>> "bzr: ERROR: Invalid url supplied to transport:
>> "lp:~jhasaurabh/charms/trusty/myCharm/trunk": No such source package
>> myChram.
>>
>> I have followed all the steps from https://juju.ubuntu.com/docs/
>> authors-charm-store.html.
>>
>> bzr whoami gives this output "jhasaurabh saurabh.ku...@techblue.co.uk".
>> What am I doing wrong?
>>
>> TIA
>>
>>
> --
> Saurabh Kumar
> System Admin
>
>
> --
> 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: bzr | No such source package

2014-10-23 Thread saurabh

I figured it out, sorry for the noise.

On Thursday 23 October 2014 05:15 PM, saurabh wrote:

Hi People,

I am getting this strange error when I am trying to push my charm to 
launchpad.
"bzr: ERROR: Invalid url supplied to transport: 
"lp:~jhasaurabh/charms/trusty/myCharm/trunk": No such source package 
myChram.


I have followed all the steps from 
https://juju.ubuntu.com/docs/authors-charm-store.html.


bzr whoami gives this output "jhasaurabh saurabh.ku...@techblue.co.uk".
What am I doing wrong?

TIA



--
Saurabh Kumar
System Admin


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


bzr | No such source package

2014-10-23 Thread saurabh

Hi People,

I am getting this strange error when I am trying to push my charm to 
launchpad.
"bzr: ERROR: Invalid url supplied to transport: 
"lp:~jhasaurabh/charms/trusty/myCharm/trunk": No such source package 
myChram.


I have followed all the steps from 
https://juju.ubuntu.com/docs/authors-charm-store.html.


bzr whoami gives this output "jhasaurabh saurabh.ku...@techblue.co.uk".
What am I doing wrong?

TIA

--
Saurabh Kumar
System Admin


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