Manipulating juju-gui upon running hooks of other charms

[Malshan Peiris]

Hi all,

I have juju-gui charm and other charm (A) deployed. Is it possible to do
following while running hook scripts of charm A:

1. Make configurations read only for charm A on juju-gui.

ex: We have a charm which should only allow configuration changes only once.

2. Pop up messages on juju-gui as called by hook scripts of charm A.

ex: We have certain info messages to be shown to the user while making
relationships on our charm using juju-gui.

Have a nice day.



-- 
Malshan Peiris,Implementation EngineerTel:
94-77-5525110 Head Office (Singapore)*P*: +65 65 332 140*M*: +65 00 000 000
*F*: +65 65 332 140 R&D (Sri Lanka)*P*: +94 11 268 3751*M*: +94 00 000 000
*F*: +94 11 268 3951 *www.hSenidMobile.com* 





 Disclaimer: This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to which they
are addressed. The content and opinions contained in this email are not
necessarily those of hSenid Mobile Solutions. If you have received this
email in error please contact the sender.
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Manipulating juju-gui upon running hooks of other charms

[Richard Harding]

On Mon, 03 Nov 2014, Malshan Peiris wrote:

> Hi all,
>
> I have juju-gui charm and other charm (A) deployed. Is it possible to do
> following while running hook scripts of charm A:
>
> 1. Make configurations read only for charm A on juju-gui.
>
> ex: We have a charm which should only allow configuration changes only once.

Not currently. We've wanted to do a read-only mode but wanted to wait for
Juju to gain the idea of users beyond admin so that some users have full
access and others have read-only access. With users work landing in Juju
1.21 (the next release) this is something we'll be looking to put into the
roadmap.

> 2. Pop up messages on juju-gui as called by hook scripts of charm A.
>
> ex: We have certain info messages to be shown to the user while making
> relationships on our charm using juju-gui.

Hmmm, so the GUI maintains a database of services, relations, machines, and
units (window.app.db). You'd have to add some JS to the page that watched
that database for changes. From there you can fire notifications like the
rest of the app using db.notifications.add().

Hope that helps. Feel free to let me know if you've got any other
questions.

--

Rick Harding

Juju UI Engineering
https://launchpad.net/~rharding
@mitechie

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

New trusty charms

[Matt Bruzek]

I was working in the review queue last week on moving some precise charms
to trusty.  For the trusty series we have the requirement for tests and the
Eco team worked hard to add tests to many precise charms.  If you know of a
precise charm without tests, adding tests (that must pass) into trusty
would be a way you can contribute to the Juju Ecosystem.

Here are the charms I looked at last week:

varnish - https://bugs.launchpad.net/charms/+bug/1387368 - landed in trusty
vsftpd - https://bugs.launchpad.net/charms/+bug/1387727 - landed in trusty
apache2 - https://bugs.launchpad.net/charms/+bug/1387844 - landed in trusty
statusnet - https://bugs.launchpad.net/charms/+bug/1387742 - landed in
trusty
python-moinmoin - https://bugs.launchpad.net/charms/+bug/1387833 - landed
in trusty

Thanks to the authors who took the time to write these tests Tim
Vansteenburgh, Kevin Monroe and Charles Butler!

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

Re: [Review Queue] Tez and Shoutcast

[Curtis Hovey-Canonical]

On Fri, Oct 31, 2014 at 3:48 PM, Whit Morriss
 wrote:
> Today I reviewed a bundle and a charm, both from our esteemed Chuck Butler.
>
> The tez bundle sets up a framework for doing realtime high volume data
> processing using Yarn and hadoop:
> https://bugs.launchpad.net/charms/+bug/1383903.
>
> Shoutcast is the venerable internet radio server:
> https://bugs.launchpad.net/charms/+bug/1374085
>
> Both worked great and got +1s from me.  I did run into a couple juju related
> bumps working on ec2.  First was forgetting to set my instance-type
> constraint and getting dinged for limited capacity on m1.smalls:
>
> agent-state-info: 'cannot run instances: We currently do not have
> sufficient m1.small
>   capacity in the Availability Zone you requested (us-east-1d). Our
> system will
>   be working on provisioning additional capacity. You can currently get
> m1.small
>   capacity by not specifying an Availability Zone in your request or
> choosing
>   us-east-1c, us-east-1a. (InsufficientInstanceCapacity)'

I have work around this my giving new constraints to select an
instance-type that is available.

Ideally, juju would try another AZ when the instance type is not available.

> The second was an error that popped up several times.  These machine hung
> around in status, but blocked deploy until destroyed.  Destroying service
> and machine cleared up the issue and allowed deployment.
>
> agent-state-info: 'cannot run instances: No default subnet for
> availability zone:
>   ''us-east-1e''. (InvalidInput)'

This is reported as
https://bugs.launchpad.net/juju-core/+bug/1388860
and I made it critical. If this is an intermittent aws issue that
resolves itself, we will lower the bug to high.



-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

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

[Review Queue] nfs, lamp, apache2, websphere-liberty

[Kevin Monroe]

Last week, I reviewed a few trusty charms with an eye on POWER!  I recently
started a 2 week trial with Site Ox and figured I'd put their p8 little
endian systems to good use.

- nfs:  needed 'sudo apt' versus 'apt' in the install hook.
- lamp:  needed updated webroot (/var/www/html) and apt tweaks in the
install hook.

I wrote a couple tests to get apache2 and websphere-liberty into the queue,
and if things pan out the way they should, cassandra, nginx, and sugarcrm
will hit the queue later this week.

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

Re: [Review Queue] Tez and Shoutcast

[Andrew Wilkins]

On Mon, Nov 3, 2014 at 11:16 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:

> On Fri, Oct 31, 2014 at 3:48 PM, Whit Morriss
>  wrote:
> > Today I reviewed a bundle and a charm, both from our esteemed Chuck
> Butler.
> >
> > The tez bundle sets up a framework for doing realtime high volume data
> > processing using Yarn and hadoop:
> > https://bugs.launchpad.net/charms/+bug/1383903.
> >
> > Shoutcast is the venerable internet radio server:
> > https://bugs.launchpad.net/charms/+bug/1374085
> >
> > Both worked great and got +1s from me.  I did run into a couple juju
> related
> > bumps working on ec2.  First was forgetting to set my instance-type
> > constraint and getting dinged for limited capacity on m1.smalls:
> >
> > agent-state-info: 'cannot run instances: We currently do not have
> > sufficient m1.small
> >   capacity in the Availability Zone you requested (us-east-1d). Our
> > system will
> >   be working on provisioning additional capacity. You can currently
> get
> > m1.small
> >   capacity by not specifying an Availability Zone in your request or
> > choosing
> >   us-east-1c, us-east-1a. (InsufficientInstanceCapacity)'
>
> I have work around this my giving new constraints to select an
> instance-type that is available.
>
> Ideally, juju would try another AZ when the instance type is not available.


We do that when zones are constrained; we should do the same here. I've
raised a bug:
https://bugs.launchpad.net/juju-core/+bug/1389037


> > The second was an error that popped up several times.  These machine hung
> > around in status, but blocked deploy until destroyed.  Destroying service
> > and machine cleared up the issue and allowed deployment.
> >
> > agent-state-info: 'cannot run instances: No default subnet for
> > availability zone:
> >   ''us-east-1e''. (InvalidInput)'
>
> This is reported as
> https://bugs.launchpad.net/juju-core/+bug/1388860
> and I made it critical. If this is an intermittent aws issue that
> resolves itself, we will lower the bug to high.
>
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> 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