Dear All,
Yesterday we released an alpha of a new Ubuntu image on MS Azure VM Depot:
https://vmdepot.msopentech.com/Vhd/Show?vhdId=50248
If you use that image and spin a VM with it, you'll be able to upload your
Azure .publishsettings file to its web interface. From that moment, the VM
will
Hey Andrew,
I agree with you on the feedback, since it's an HTML page at the moment
it's hard to incorporate those items, but I've forked the repo and started
building a lightweight Python app to provide that feedback to the user.
Marco
On Tue Feb 10 2015 at 9:37:48 PM Andrew Wilkins
Hi Samuel,
Looks neat. A few things:
1. Once the VM is ready, the entire landing page keeps refreshing at 1s
intervals. That doesn't leave a lot of time to add the .publishsettings
file and upload.
2. There's no feedback to say whether or not the .publishsetttings file
has been uploaded, and
Hi,
I'm trying to deploy a basic hadoop cluster on Amazon (AWS).
It should have just 10 nodes to simply run hadoop map-reduce
jobs and just store data on hdfs. Nothing else. No hive or
spark or anything.
These are the commands I enter.
juju quickstart
juju deploy
Hi all,
Anastasia raised an issue in http://reviews.vapour.ws/r/885/ about how to
cut down on struct conversions between params, state, and domain packages.
In this case we're talking about storage. The following API server facades
currently participate in storage:
- client
- storage
-
So, I think you *do* need conversion code specific to state -- the
methods exported from state should be in terms of the storage types,
because they're the language we've chosen to model storage, so there
needs to be conversion code in state (or possibly in an internal
package -- but either way
On Tue, Feb 10, 2015 at 12:13 PM, William Reade
william.re...@canonical.com wrote:
really ought to include a bunch more mechanism for finding out
*precisely* what should have been assigned to what
To be clear: I do not think we should do this, because the
interpretation of those entities would
On Tue, Feb 10, 2015 at 6:16 PM, roger peppe roger.pe...@canonical.com
wrote:
On 10 February 2015 at 10:06, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
On Tue, Feb 10, 2015 at 5:57 PM, roger peppe roger.pe...@canonical.com
wrote:
On 10 February 2015 at 08:55, Andrew Wilkins
I think that the danger here is one of backwards incompatibility,
and that's a danger that's possible to alleviate with some tooling
support.
Writing tons of boilerplate code to manually convert between types at different
levels has always seemed like a poor use of developer resources to
me (and
On Tue, Feb 10, 2015 at 5:57 PM, roger peppe roger.pe...@canonical.com
wrote:
On 10 February 2015 at 08:55, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi all,
Ian raised a good point in http://reviews.vapour.ws/r/885/ (caution
advised,
may cause eyebleed) about a change I made
On Tue, Feb 10, 2015 at 5:44 PM, William Reade william.re...@canonical.com
wrote:
So, I think you *do* need conversion code specific to state -- the
methods exported from state should be in terms of the storage types,
because they're the language we've chosen to model storage, so there
needs
On 10 February 2015 at 08:55, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi all,
Ian raised a good point in http://reviews.vapour.ws/r/885/ (caution advised,
may cause eyebleed) about a change I made to errors:
https://github.com/juju/errors/pull/17
The NotAssigned error, which
I think that NotAssigned is *too* generic. UnitNotAssignedToMachineErr
is one thing, and VolumeNotAssignedToStorageInstance is another; if we
use the same error type to represent those distinct situations, we
really ought to include a bunch more mechanism for finding out
*precisely* what should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.02.2015 11:57, roger peppe wrote:
On 10 February 2015 at 08:55, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi all,
Ian raised a good point in http://reviews.vapour.ws/r/885/
(caution advised, may cause eyebleed) about a change I
I reviewed the Dell OpenManageServerAdministrator charm which is a
brilliant use of a localized juju charm for deploying some added zing to
dell servers.
https://bugs.launchpad.net/charms/+bug/1325700
This landed today and was +1'd thanks to mwennings hard work.
MariaDB had an ISV Maintainer
# juju-core 1.21.2
A new stable release of Juju, juju-core 1.21.2, is proposed.
This release may replace 1.21.1 on 2015-02-12 after a period
of evaluation.
## Getting Juju
juju-core 1.21.2 is available for utopic and backported to earlier
series in the following PPA:
Ken,
Unfortunately, this is due to an upstream change in the openjdk
package. A bug has been filed[1] and it has been noted that this
breaks all of the Big Data charms in the store. Please indicate on
that bug that this is affecting you.
There is a symlink work-around mentioned on the bug, but
Hello,
Can someone direct me to the design documents for the enigmatic
'block' functionality which is showing up in the review queue.
Thanks
Dave
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
For my time in the review queue I did another round on the Talligent
Openbook charm. The previous problem was fixed, but it had another
configuration related problem.
https://bugs.launchpad.net/charms/+bug/1411402
- Matt Bruzek matthew.bru...@canonical.com
--
Juju mailing list
# juju-core 1.22-beta3
A new development release of Juju, juju-core 1.22-beta3, is now available.
This release replaces 1.22-beta2.
## Getting Juju
juju-core 1.22-beta3 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
20 matches
Mail list logo
