That sounds great. I look forward to trying it out.
John
=:->
On Nov 1, 2013 5:44 AM, "Gary Poster" wrote:
> Hi all. The GUI team has a tool in alpha that we think is useful now.
> It is an opinionated way to start a great Juju experience quickly.
> We're looking for users and feedback from ea
Non released streams was only supported in Azure for a time when there
weren't stable releases. It would be possible to implement and make it work
elsewhere, but it was underutilized and did cause some bugs.
The main workaround is to do "custom" stream data and reference the built
images (juju me
Pinging is already suppressed in the 1.17 codebase.
John
=:->
On Jan 9, 2014 7:30 PM, "Mark Shuttleworth" wrote:
> On 09/01/14 14:36, Steve Powell wrote:
> > 1) the `debug-log` command is not documented very well: executing it
> > without parameters tails the log (forever) until ^C’d out. To see
You generally don't have to specify a control bucket manually anymore as
Juju will fill in that value with a random value. We may need to make our
default random value shorter, though it does seem unrelated to what you're
seeing.
John
=:->
On Feb 7, 2014 2:29 AM, "Andreas Hasenack" wrote:
> On T
We also ended up with an instance updater that makes a request on a pretty
fast poll when you bring new instances up. It should be changed to poll for
all unknown instances in a single bulk request. Possibly the poll instance
should also be decreased. (I triggered it with just deploy -n 15, and as
Unfortunately the MaaS controller doesn't expose itself as a place that you
can deploy services, so having that machine as the only public machine
would make it difficult.
If you can put another machine on the public network, then you should be
able to put haproxy on it as a reverse proxy.
John
=:
I'm pretty sure Quantum can't be deployed in LXC because it needs direct
access to block devices. I could be wrong.
John
=:->
On Mar 15, 2014 2:08 PM, "brian mullan" wrote:
> I thought I'd try using some of the "cool new stuff".. so with latest lxc
> 1.0 JuJu & JuJu-gui installed I decided to lo
s problem
> exists w/other environments?
>
>
>
> On Sat, Mar 15, 2014 at 4:00 PM, Adam Stokes wrote:
>>
>> I also think that nova and lxc do not mingle well either. I've
>> typically deployed nova in a kvm instance instead
>>
>> On Sat, Mar 15, 2014 a
On Sat, Mar 15, 2014 at 1:11 AM, Curtis Hovey-Canonical
wrote:
> juju-core 1.17.5
>
> A new development release of Juju, juju-core 1.17.5, is now available.
>
>
> Getting Juju
>
> juju-core 1.17.5 is available for trusty and backported to earlier
> series in the following PPA:
> https://launch
have thought we would publish on streams.canonical.com first,
and then sync the rest from there.
John
=:->
On Mon, Mar 17, 2014 at 12:18 PM, John Meinel wrote:
> On Sat, Mar 15, 2014 at 1:11 AM, Curtis Hovey-Canonical
> wrote:
>> juju-core 1.17.5
>>
>> A new develo
ar 17, 2014 at 12:14 PM, Curtis Hovey-Canonical
> wrote:
> > On Mon, Mar 17, 2014 at 5:01 AM, John Meinel
> wrote:
> >
> >> nor are they in HP:
> >>
> https://region-a.geo-1.objects.hpcloudsvc.com/v1/11289530460295/tools/streams/v1/com.ubuntu.juju:releas
As of right now (2014-05-19 11:20 UTC) streams.canonical.com no longer
lists 1.17.[1-5] as available. At least if I go here:
http://streams.canonical.com/juju/streams/v1/com.ubuntu.juju:released:tools.json
vs going here:
http://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju:released:to
Fantastic! Looks like streams.canonical.com is also nice and updated.
John
=:->
On Fri, Mar 21, 2014 at 5:03 AM, Curtis Hovey-Canonical
wrote:
> juju-core 1.17.6
>
> A new development release of Juju, juju-core 1.17.6, is now available.
>
>
> Getting Juju
>
> juju-core 1.17.6 is available for tru
Notice that volume which is attached is a *new* volume. The reason is
because we are booting the images that use elastic block storage,
rather than only local temp files.
So yes, when you create new instances, you will see new volumes that
are mounted automatically. When those instances are destroy
I would actually just use MaaS + LXC or KVM virtualization.
You should be able to bring up a MaaS environment, and then do:
juju deploy NEWSERVICE --to lxc:10
And Juju will create a new LXC container on machine 10 and deploy the
NEWSERVICE into it.
That gives you all the "give me baremetal" when
One of the easiest ways to do it today would be to use manual
provisioning. So you would spin up your instances using whatever
cloudstack interface you have available (such as the dashboard), and
then you would register those machines with juju (juju add-machine
ssh:user@host), and then you could d
al as we can get? What is the
> performance implications of a single KVM vm on a bare metal (vs if we had
> done a direct to metal install).
>
> Brian
>
>
> On Thu, Mar 20, 2014 at 11:24 PM, John Meinel
> wrote:
>>
>> I would actually just use MaaS + LXC or KVM
i think the issue he is mentioning is that you can use the GUI to set the
password to "", but that doesn't actually unset the password in the
application.
John
=:->
On Wed, Mar 26, 2014 at 9:33 PM, Richard Harding wrote:
> On Wed, 26 Mar 2014, Anant wrote:
>
> > Hello Everyone,
> >
> > I am ne
I'm pretty sure you can do the opposite (I'm running trusty host and see
precise containers show up). Maybe there is a hard coded precise somewhere
that needs to be fixed.
John
=:->
On Apr 5, 2014 12:45 AM, "Andreas Hasenack" wrote:
> On Fri, Apr 4, 2014 at 5:32 PM, Andreas Hasenack
> wrote:
>
All hooks are run sequentially (we explicitly take out a lock across all
hooks that want to run on a machine), just so that charms can do whatever
they want with apt without stepping on each other's toes.
I would think "install" is the most likely hook to actually do update and
install. I'm not su
"apt-get install" was the
answer I found.
John
=:->
On Thu, Apr 10, 2014 at 5:45 PM, Mark Shuttleworth wrote:
> On 10/04/14 12:00, Stuart Bishop wrote:
> > On 10 April 2014 17:42, John Meinel wrote:
> >> All hooks are run sequentially (we explicitly take out a
Known bug, though I thought the fix made it into 1.19.1.
To work around it, you use
juju bootstrap --upload-tools --series precise, trusty
John
=:->
On Apr 25, 2014 9:35 PM, "Asif Iqbal" wrote:
> I am using 1.19.1-trusty-amd64, installed from ppa:juju/devel
>
> I am failing start hadoop unit, sh
The peergrouper thing is a non fatal problem with the local provider (it is
only used for HA which is currently disabled for local). The problem with
default series is the local provider defaults to only making tools for your
host available (trusty). Which is why you specify the extra tools series
Also check that you have "juju-local" installed.
John
=:->
On Apr 27, 2014 2:00 PM, "José Antonio Rey" wrote:
> Maybe you haven't destroyed your environment and re-bootstrapped?
>
> On 04/27/2014 03:55 PM, Asif Iqbal wrote:
> >
> >
>
There is work being done this cycle to switch from using storage from the
Provider to instead using our own internal storage. I don't know that the
work will be done for another few months, though. I believe Tim Penhey is
going to be leading up that work as part of exposing Resources for charms
to
(If
you think about it, all of them are just sending requests to some other
long-lived process over a socket, but I'd rather not have to run a full
service for every system we want to interact with.)
John
=:->
On Tue, May 6, 2014 at 8:33 AM, John Meinel wrote:
> There is work bein
We certainly welcome more provider implementations to be part of core.
We've been working with a couple of other people in doing just that (Joyent
support was recently contributed by them, and there are a few others being
worked on today).
Most of the provider implementations we have today are spl
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1304407
It should be fixed in 1.18.3.
John
=:->
On Mon, May 12, 2014 at 9:36 PM, Henning Eggers wrote:
> Hi!
>
> I just noticed that I now have specify the arch constraint if I want amd64
> instances. Without it, I get i386 instances. "
I actually think this isn't about someone doing "juju set-env" but someone
just ssh'ing into the machine and changing things with a text editor.
Joey is the type of guy to be very concerned about people making changes
out of band that we wouldn't know about even if we had audit logging.
(Which we s
You might be running into this:
http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
John
=:->
On Mon, May 12, 2014 at 4:47 PM, boyd yang wrote:
> Hello,
>
> I got juju bootstrap error.
> I used Ubuntu 14.04 LTS.
> How to fix this?
> Thanks!
>
> r
FWIW, I've gotten bug requests from a user that did a regular bootstrap and
then was trying to "juju upgrade-juju --upload-tools" and was confused that
his local machine wasn't able to upgrade tools for his environment. (he was
running i386 locally, and bootstrap created an amd64 machine).
And whil
FWIW, I think the byArch did a plain sort.Strings() which happens to pick
amd64 because it is before all other in a typographical fashion. IIRC, it
may have mutated a lot over time because the sorting was blocking bootstrap
from working on ppc64 which was why it was removed. Also, on MaaS, MaaS
doe
I would generally think to model this as part of the relation data. Since
you want the individual units of your charm to connect to different units
of Mongo, then it sounds like you want a peer relation in your charm, and
each unit could then report what unit of mongo it is connecting to on the
pee
Stub is certainly the guy who has written most (all?) of the postgres
charm. So I'm happy to point you his way. I don't personally know how to
answer these questions.
John
=:->
On Wed, May 28, 2014 at 11:23 AM, Tim Penhey wrote:
> Hi folks,
>
> I'm writing not as a canonical core developer, but
Sounds great.
John
=:->
On Mon, Jun 2, 2014 at 1:34 PM, James Page wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Folks
>
> As part of ongoing work to improve and sustain the quality of the
> OpenStack Charms, we are going to start enforcing the linked policy on
> charm dev
Stuart-
There was a discussion we had a year ago about possibly changing the design
of how proxies worked. I believe it is something that can be done entirely
in charm space if people want to give it a try. You can certainly think
about it and whether it works better for you or not.
In our curren
...
> 1. Is it correct to say that each machine created by juju in the
> environment is basically an Ubuntu OS (most likely 14.04)?
>
There is work being done now to enable alternative platforms for deployment
(IIRC both Windows and CentOS support is currently under development).
However, for th
There are ways to do an upgrade manually if you take a lot of care.
However, I think if you did "juju upgrade-juju --version=1.18.4" you'll
provide yourself more of the sanity and safety around the upgrade than
trying to reproduce all of the steps that we recorded inside of juju.
If you really wan
When you do "juju add-machine" it should print out a line like:
created machine 10
You should be able to then do:
juju add-unit SERVICE --to 10
John
=:->
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
My understanding was that some of this was possibly buggy charms, where you
don't want to start relating a charm to X until it is already related to Y
(front end vs backend sort of stuff).
John
=:->
On Mon, Aug 25, 2014 at 9:05 PM, Marco Ceppi
wrote:
> My question is why do you need to run add
Given CAP theorem any message can really only be "at most once" or "at
least once". You can never guarantee "exactly only once".
I'm sure juju is biased to the "at least once" for hooks (hence why it runs
at agent restart because it hasn't been around to know for sure that
nothing changed in the in
My understanding is that the proposed Leader spec is likely to help with
this, as a leader unit could coordinate between its peers which one should
work next. Otherwise, it is just up to the charm peer relation to
coordinate anything like this. So in peer-relation-changed you could say
that you wan
So there is the question of what is the "user experience", and people
trying out Juju and it seems slow. Though if it is slow, doesn't that mean
that images are out of date?
I just bootstrapped a fresh Ubuntu from Amazon's web interface today, and I
noticed that apt-get upgrade on there installed
You could probably edit the /var/lib/juju/agents/unit-*/agent.conf and
/var/lib/juju/agents/machine-*/agent.conf to change the IP addresses stored
there (everyone needs to know how to get back to the API server).
Generally the API server filters out 127.0.0.1 when reporting its possible
addresses
might require 1.21, but I thought the IP address update changes
landed in 1.20)
John
=:->
On Wed, Oct 15, 2014 at 4:21 PM, Vasiliy Tolstov
wrote:
> 2014-10-15 11:08 GMT+04:00 John Meinel :
> > You could probably edit the /var/lib/juju/agents/unit-*/agent.conf and
> > /var/
As mentioned, a peer-relation is the way to go about this. It gives you a
hook path for the units to communicate to each other.
John
=:->
On Fri, Oct 17, 2014 at 2:44 PM, saurabh
wrote:
>
> On Friday 17 October 2014 02:51 PM, Simon Davy wrote:
>
>> On 17 October 2014 10:13, saurabh wrote:
>>
>
On Mon, Oct 20, 2014 at 12:53 PM, Malshan Peiris
wrote:
> Hi all,
>
> When i deployed a bundle to an AWS instance, it had created an AWS
> instance per charm, which is costly for the user.
>
> 1. Is it possible to deploy all charms of bundle to a single AWS instance
> without creating many insta
If you get config-changed can you use that to update your host field
causing relation-changed where you need it?
John
=:->
On Dec 9, 2014 7:02 AM, "Stuart Bishop" wrote:
> On 9 December 2014 at 09:53, Andrew Wilkins
> wrote:
> > On Tue, Dec 9, 2014 at 10:31 AM, Stuart Bishop <
> stuart.bis...@c
Stub- AFAIK there isn't something today, though William might know better.
William, does your Active/Goal proposal address this? Having a Goal of 0
units would be a pretty clear indication that the service is shutting down.
John
=:->
On Wed, Dec 17, 2014 at 7:01 PM, Stuart Bishop
wrote:
>
> Hi
...
> 9. If you want to cancel a deployment that just started you need to keep
running remove-service forever. Juju will simply ignore you if it's still
running some special bits of the charm or if you have previously asked it
to cancel the deployment during its setting up. No erro
So the main caveats as I see them are:
1) since it didn't come from an official source we flag it as such (the
mechanism was originally developed to allow developers to test out their
in-progress code changes). So your version numbers I "juju status" won't
exactly match
2) if you ever need to depl
Unfortunately the Openstack that Rackspace exposes is not quite the same as
the official openstack releases. (I believe they don't expose storage, and
a couple of the other APIs aren't the same.)
John
=:->
On Wed, Jan 28, 2015 at 10:11 AM, Sajith Vijesekara <
saji...@hsenidmobile.com> wrote:
> H
You also need the CA certificate and the API server addresses.
I might recommend trying a new "juju bootstrap" of say a simple LXC
container (for manual) and then you can see what content we depend upon. I
don't think the GUI authenticates the HTTPS certificate that we present,
but definitely the j
On Fri, Apr 3, 2015 at 7:47 AM, Richard Harding
wrote:
>
> tl;dr
>
> The new v4 API is out there go migrate to it. v3 API will be EOL'd at the
> end of the year.
>
Doesn't that EOL the version of Juju that is in trusty? Yes we'll release a
new version, but people won't be able to deploy with the
upgrade step "set AvailZone in instanceData" failed: no instances found
seems suspicious.
What version of MAAS are you running?
It is possible that it would come before MAAS availability zones?
Certainly we couldn't really find 0 instances in MAAS because the machine
this is running on has to be a
On Mon, May 4, 2015 at 8:49 PM, Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:
> Thanks for reaching out, Dinesh!
>
> I have opened two bugs for these issues:
>
> 1.In *juju bootstrap. *It is *not downloading the disc image* itself.
>> But when I check juju status, it is showing
I think I remember that keystone needs to be set up with its database
relation before anything else is related to keystone, as the charm doesn't
implement db migration.
John
=:->
On Mon, Jun 15, 2015 at 1:51 PM, wrote:
> Hi ,
>
>
> We have been trying to deploy keystone charm using ju
ng to relate from juju ?
>
> ------
> *From:* John Meinel
> *Sent:* Tuesday, June 16, 2015 1:17 PM
> *To:* Dinesh Kumar Senapaty (WT01 - Global Media & Telecom)
> *Cc:* juju
> *Subject:* Re: Keystone error
>
> I think I remember that ke
I would guess the point is that there is nothing wrong but he's showing
orchestrating docker containers in docker/* services.
Either that or there is a problem that the containers aren't getting TCP
ports opened.
John
=:->
On Sun, Jun 21, 2015 at 1:48 PM, Mark Shuttleworth wrote:
> On 21/06/15
I believe there is work being done so that you can do "juju get" and send
that output directly into "juju set" or even "juju deploy --config". And I
think that's a much better story around repeatable deployments than trying
to make sure the defaults never change. If they really care about
repeatabl
Would this just be config on the charm that would eventually become config
on the relation?
John
=:->
On Aug 19, 2015 7:05 AM, "Samuel Cozannet"
wrote:
> Hi All!
>
> Our friends at Engineering are working on the SpagoBI charm set and it's
> going very well.
>
> They are facing an issue that I co
Juju 1.23 has some known issues with Lease operations. All of those have
been fixed in the 1.24.4 (5?) release. It is good practice to take a backup
before upgrading, and if you want we can try to help sort out the specific
growth to make sure it gets cleaned out after the upgrade. (Even just
getti
I think his issue is that he can "juju bootstrap --constraints" and then
immediately "juju set-env" to remove the constraints. But "juju quickstart
--constraints" does a bootstrap and then immediately starts deploying the
services without a way to unset the constraints that don't apply to all
mach
I don't know the concrete details here, but I do believe there are a few
files that are shared in one JUJU_HOME. There is only one environments.yaml
and the new multi-environment code means there is another shared file that
holds the list of known servers and environments.
I would hope that the cod
Although given https://pad.lv/1467331 it would seem that we can easily
leave it stale if the client doesn't exit cleanly. This does sounds like a
case where using a lock file means we're going to need to provide some sort
of "break-lock" functionality. We could do something like inspect the lock
an
Are you looking for the user to 'ssh' as or the user to connect to the Juju
API?
After bootstrap there should be a ~/.juju/environments/ENV.jenv file.
There should be a user and password in there for the API. For SSH, you use
the "ubuntu" user with the ssh key that was found during bootstrap.
John
It does feel like a good fit for resources, with the one caveat that he
wants to maintain a lock-step version of the resource across services.
There is slightly more work with the current designs for resources, in that
each charm will think about its version of the resource independently. But
we wi
Generally the [A]GPL applies when you are modifying the actual object.
For example, if you have to modify the "juju" binary to add another
command, or support different hardware, then likely that would need to be
exposed.
If you are just using Juju to deploy some other program, then AGPL doesn't
a
02/16 09:25, John Meinel wrote:
> > The more edge case is that charmhelpers itself is AGPL, so if your charm
> > imported charmhelpers, then that is more of a grey area. You likely need
> to
> > open source the actual charm, which sets up configuration, etc of the
> > pro
...
>
> And now I think of it, can I stream resources? I don't want to
> provision a machine with 8TB of storage just so I can restore a 4TB
> dump. Maybe this is just a terrible example, since I probably couldn't
> be bothered uploading the 4TB dump in the first place, and would
> instead setup t
Looks like the changes to Login broke compatibility. We are adding a Login
v3, but it looks like the new code will refuse to try to Login to v2. I'm a
bit surprised, but it means you'll need to bootstrap again if you want to
test it out with current trunk.
John
=:->
On Thu, Feb 18, 2016 at 2:47
u, Feb 18, 2016 at 2:49 PM, John Meinel wrote:
> Looks like the changes to Login broke compatibility. We are adding a Login
> v3, but it looks like the new code will refuse to try to Login to v2. I'm a
> bit surprised, but it means you'll need to bootstrap again if you wan
This is the other way around. The code you linked is an old Juju contacting
a new server. The error he saw is a new "juju" contacting an older "jujud".
John
=:->
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber
wrote:
lains why the connection refused
> error appears.
>
> Tom
>
> On 27 Feb 2016 11:56, "John Meinel" wrote:
>
>> Connection refused isn't the error you would be getting if it was the
>> current incompatibilities. What you're seeing looks more like you aren
aiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
> goal, but you can always help by sponsoring the project
> <http://www.meteorit
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
On Sat, Feb 27, 2016 at 4:55 PM, John Meinel wrote:
> That doe
:~#
>>>
>>>
>>> Seems alright if I just launch an instance. Also inside the juju
>>> bootstrapped containers you can see some ssh related stuff where it sets
>>> keys etc in the logs so its logging in and doing something.
>>>
>>> I've compil
Is 10.0.3.94 the correct IP for the LXD container? Did you let it sit a
while so it had a chance to keep trying until maybe SSH came up on its own?
And yet again, if you just do "lxc create" a container from exactly the
same image, is SSH running on it?
I'm recompiling my own work here making sure
One thing you could try, "juju bootstrap test-lxd lxd --debug
--upload-tools --bootstrap-series trusty". It may be a difference based on
what the target series is.
John
=:->
On Sat, Feb 27, 2016 at 6:50 PM, John Meinel wrote:
> Is 10.0.3.94 the correct IP for the LXD container
Is there a reason to tell people to look at "controllers.yaml" rather than
having the official mechanism be something like "juju list-controllers
--format=yaml" ? I'd really like to avoid tying 3rd party scripts to our
on-disk configuration. We can keep CLI compatibility, but on-disk
structures are
At the moment I don't believe we do. We just use your access key and secret
key to identify you to EC2 when we make requests. We don't support using
temporary credentials via Assume role
For those of us wanting to know more here is AWS page
http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_c
...
>
> > 3) Downloading from the internet. This issue has been common in
> > charmstore charms, and is discouraged, AIUI. But the same issue
> > applies for layers, and possibly with more effect, due to a layer's
> > composibility. We simply can not utilise any layer that downloads
> > things f
If the subnets have logical differences, then they should be in different
spaces.
Examples for and against:
1) 2 network switches, one is 1GB for admin traffic, other is 10GB for
storage traffic, these should be different spaces
2) 2 racks, each configured identically. each rack has 2 switches as
Does that mean master is unblocked?
John
=:->
On Sat, Mar 26, 2016 at 6:08 AM, Cheryl Jennings <
cheryl.jenni...@canonical.com> wrote:
> Hi Everyone,
>
> The release team has been working to get 2.0-beta3 released today, but due
> to some packaging issues, the release will be delayed until earl
On Mar 29, 2016 3:47 AM, "William (Will) Forsyth" <
william.fors...@liferay.com> wrote:
> A feature that I think would clean up the deployment of multi-charm
> bundles would be the ability to deploy directly to lxc containers without
> specifying or pre-adding a machine.
>
I'm not sure of the de
Did you run dpkg-reconfigure lxd ? That's what I ran once I installed the
new lxd package and it seemed to get things working. Tycho added some
helpful prompts as part of "juju bootstrap" to point users in the right
direction if LXD looks to be improperly configured.
https://github.com/juju/juju/p
I'm curious if we've looked into throttling to improve things. I've done
some parallel testing in the past, and I've seen a few times where just
adding units sequentially was actually faster than parallel because of
contention.
I wonder if we might want to introduce some sort of rate limiting acro
I believe --config can take a file rather than just a 'key=value' pairing.
So you can save all your config to a file and pass it in with '--config
myconf.yaml'
There was discussion of having a default search path for some of the
config, but I'm not sure if that got implemented, nor if it is actual
On Tue, Apr 26, 2016 at 10:41 PM, Andreas Hasenack
wrote:
> On Tue, Apr 26, 2016 at 3:11 PM, John Meinel
> wrote:
>
>> I believe --config can take a file rather than just a 'key=value'
>> pairing. So you can save all your config to a file and pass it i
...
>
>> As noted, the number of times you have to bootstrap should be going down,
>> and if you are bootstrapping different-but-similar, then you again have a
>> single config that can be reused.
>>
>
> I'd love to be able to share a controller node with my colleagues. I tried
> setting that up
...
> But where did the settings for scapestack get set up in the first place.
>> You're missing some of the original "edit ~/.juju/environment.yaml" to
>> insert the right information.
>>
>>
> The scenario is starting from an already configured cloud in both juju1
> and juju2, and my use case is
On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack
wrote:
> On Wed, Apr 27, 2016 at 10:59 AM, John Meinel
> wrote:
>
>> ...
>>
>>
>>>
>>>> As noted, the number of times you have to bootstrap should be going
>>>> down, and if you are boo
>
> ...
>
> (*) It is called Synnefo ( synnefo.org ) and is an opensource IaaS
> developed by the Greek Research Network of Technology (GRNET). It powers
> ~okeanos ( okeanos.grnet.gr ), a large IaaS providing resources to the
> Greek and other European academic communities. Synnefo is OpenStack
Using the workload message as a single location to convey information to
the outside world was certainly never intended. Generally those messages
were meant to convey information to a human who would be looking at them.
We've actually had quite a few conversations about opening up more avenues
for
I think the question is whether it is available by default. Not whether it
could be installed. But as mentioned, if the answer is a short bash script
that ensures "apt-get install python3" and then everything else in Python3
that sounds like an answer.
John
=:->
On Mon, Jun 6, 2016 at 3:55 PM, M
I believe 'push' gives you a revision number, which the bundle can then
request. But that would need to recreate the bundle after each push. I
don't believe there is a handle for "latest unpublished version".
John
=:->
On Wed, Jun 15, 2016 at 5:02 PM, Merlijn Sebrechts <
merlijn.sebrec...@gmail.c
Near the end of this is a line that says it couldn't find your region.
Generally Juju will need to know what region your cloud is in order to
determine what image is "trusty" or "xenial". It sounds like we need to get
the descriptions of your images. You can look at:
https://Jujucharms.com/docs/1.2
I thought in MAAS 2 they have a way to generate a file appropriate for
being a .maasrc file which Juju will use as a source for 'juju
autoload-credentials'. That doesn't do the steps of creating the MAAS user
itself, but it should help the 'configure juju' part. Though this will also
only be suppor
>
> ...
>
> Sure, an example:
>
> A web application needs creds (secrets) in order to access a 3rd party
> api. These creds need to exist in a config file on the webserver/instance.
> As a user, you/I know what the secrets are, but now we need to share them
> with the web application, and only th
1 - 100 of 210 matches
Mail list logo
