On 20/09/13 02:14, David Cheney wrote:
> See the "Deploying to specific machines" section of
> https://juju.ubuntu.com/docs/charms-deploying.html
>
> Please read the "Considerations" section below that one and understand
> that charm authors do not consider this method of deployment when
> writing
Pretty neat, Erlang might be a great fit for deployment tools that
monitor and respond to dynamic load or other influences, with Juju
providing the harness to act on scale.
Mark
On 16/09/13 11:08, Matthew Williams wrote:
> I've started work on an elixir library for using the juju api. It's
> ver
Are there good markdown renderers in JS? Should we aim for interface
documentation in MD?
On 30/09/13 12:32, Richard Harding wrote:
> On Wed, 25 Sep 2013, Luca Paulina wrote:
>
>> On Wed, Sep 25, 2013 at 3:06 PM, Jorge O. Castro wrote:
>>
>>> Hi everyone,
>>>
>>> I'd like to revise the charm qua
of a
>> charm's readme in JS. Jorge, how are we looking to have users document
>> their interfaces? As a description attribute in the yaml? Could that be
>> easy to write out as markdown?
>>
>> On Mon, 30 Sep 2013, Mark Shuttleworth wrote:
>>
n't it?
>
>
>
>
>
>
> On Thu, Oct 3, 2013 at 7:21 PM, Gary Poster <mailto:gary.pos...@canonical.com>> wrote:
>
> On 10/03/2013 01:50 PM, Mark Shuttleworth wrote:
> >
> > Are we talking about documentation of the config (lightweight) or
> >
On 07/10/13 07:29, Andrew Wilkins wrote:
> It may take a while to come up the first time, as the LXC template
> will need to debootstrap.
Are we downloading an image, or a set of packages? debootstrap would be
a lot slower than an image launch, seems like we could drop an image
there more easily.
We should really allow passing substrate-specific constraints like
instance types. No need for the voodoo in juju :)
On 09/10/13 20:16, Kapil Thangavelu wrote:
> Unfortunately without an ec2 constraint in juju-core around instance
> type, the overlap around capabilities within ec2 instance types
Good call Andrew. I do think we want to be able to manually provision
machines in environments that use other providers, though, so watch this
space for when we line that up properly.
Mark
On 10/10/13 03:11, Andrew Wilkins wrote:
> Hi Jorge,
>
> I was just watching the playback, and wanted to tr
On 10/10/13 14:18, Gustavo Niemeyer wrote:
> In a second moment, we can provide a mechanism for
> people to provide their own custom mappings tied to their environment
> ("in this environment t1.micro means 1 CPU and 512MB of memory").
Yes, I like this. I also like the idea that we might provide a
When we originally discussed this, the view was that versioning would be
handled directly in the name. So folks CAN if they want do an http-XYZ
and own that namespace henceforth. In general, I think we should
socialise convergence around common patterns, but allowing flexibility
encourages healthy
Please test Precise and, if there are issues:
* have Juju detect and warn/error out with guidance on how to address
the issue
* document it as such
I don't think we need to try and work around it for 12.04.0
compatibility, just recommend folks apt-get the newer kernel in precise,
it's fully sup
On 18/11/13 03:31, Vasiliy Tolstov wrote:
> My new question is - does it possible to have one state server for all
> customers? I don't need to spawn sepaate state server for each
> customer deploy, but want to provide to it some log/pass/key to acces
> state server and use it.
That capability is
On 20/11/13 12:06, Ramez Hanna wrote:
> I noticed there is a bug open for a charm for trac
> so i started working on it, to conytribute to charms and learn more
> about juju
> I would be glad if someone would help me out with requirements for the
> deployment of trac
> I am an experieced sys admin
On 28/11/13 14:58, Peter Waller wrote:
> I know in the 1.16 series we have an "addressupdater" worker that
> polls loop that polls every 15 minutes. I'm not sure what version
> you're using.
Hmm... is there not an inotify or similar equivalent for network interfaces?
Mark
signature.asc
Descrip
On 28/11/13 17:08, Kapil Thangavelu wrote:
> There is.. $ ip monitor will do it.. its using netlink to watch for
> changes.
In that case, event-driven with a sweeper process for platforms where
the monitor is unavailable or unreliable would be tighter.
--
Juju mailing list
Juju@lists.ubuntu.com
On 28/11/13 17:25, Peter Waller wrote:
> Is it safe to run that whilst my agents appear to be spinning as I
> described in my previous e-mail?
A very good question.
If updates are required to be applied in a sequence, surely Juju would
know that better than any given user of Juju, and either inst
On 04/12/13 17:34, Peter Waller wrote:
> This situation is now resolved with thanks to Roger, Gustavo and
> others in real time. There is no way we could have resolved it
> ourselves since there was corruption of the juju database caused by
> running out of disk space, which was unfortunate. We as
As a counter-proposal: a comprehensive set of tests will be needed to
get a 2-star rating.
This way, we let people get charms in that work-for-them-and-others, but
the limitations are reflected in our rating of the charm.
Mark
On 13/12/13 08:00, Vincent JOBARD wrote:
> Hi
>
> I'm totally agreed
Those are all good points. Our rating system is really good - it maps to
rigorous assessment of "what matters". My guess is people will strongly
prefer charms that have 3-star or more ratings. So that was why I was
suggesting that we make a few "trump" categories, in other words, even
if you score
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 the
> whole of the log so far execute "juju debug-log -n 1”, and then ^C
> out. (“-n 0” is invalid for some reason);
Nic
On 10/01/14 14:56, Richard Harding wrote:
> Steve, I believe that changing the release changes the source updates are
> fetched from during the normal apt-get install/upgrade process. It does not
> actually perform the upgrade itself. I also run a Jenkins install from the
> charm and have it runnin
On 14/02/14 14:37, Richard Harding wrote:
> I think we could easily reference external plugins with a readme type doc
> instead of a script to start out with. That way there's visibility, but
> they reference their own home for larger pluigins. We'd do this for
> quickstart for example.
>
How abou
On 11/03/14 16:14, Charles Butler wrote:
> Incoming thread necromancy
>
> Have we come to a general consensus on adding a new flag for
> "maintainers" to list multiple maintainers, and leave "maintainer" in
> place?
>
> What kind of implications does this have when someone adds themselves
> to "m
On 15/03/14 03:29, Joshua Strobl wrote:
>
> Just wanted to state that, while I obviously have no vote in the
> matter (since I am not part of the charmers team), it would really be
> in the best interest to accept Charles on the team.
>
> Charles is a great guy that has extremely helpful and patien
On 17/03/14 14:05, brian mullan wrote:
> Here are a couple of scenario's for openstack/lxc that I think are
> interesting.
>
> ARM x64 cpu are now available and use 1/8th the power of an intel cpu
> ... given its hard to compare apples to oranges here.
>
> Ubuntu & LXC can both be used on ARM x64 s
On 19/03/14 04:22, John Meinel wrote:
> Should I be filing a Critical bug on this? Because our release process
> doesn't seem to be getting streams.canonical.com properly updated,
> which seems pretty serious.
Yes, please do.
Let's treat any tools-related failure as a critical bug please; it's a
On 21/03/14 20:23, Brian Wawok wrote:
>
> Oh awesome.
>
> That is really neat the flexibility.
>
Well said :)
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
On 27/03/14 14:51, Stuart Bishop wrote:
> Correct. I think you are just fine with one relation per database and
> using the generated credentials, and using the granted roles to
> control database permissions.
As a sanity test - would per-relation config be useful in this scenario?
Mark
--
Juju
On 27/03/14 16:54, Sameer Zeidat wrote:
> Juju by design does not enforce parameter changes. It's basically up
> to the charm writer to apply the change or silently ignore it. Juju,
> and hence the GUI, will accept the change and store it regardless.
>
> Since juju has no notion of "read-only" para
On 02/04/14 00:20, Sebastian wrote:
> When I bootstrap, its all going well till the juju wants to upload the
> juju tools to the swift, gives me a time-out error, and all the other
> things I reported in this thread.
> ...
> Please, I'm asking for some kindly help! I really can't believe that
> you
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 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.
On 13/05/14 17:45, Joey STANFORD wrote:
>
>> Part of the problem is that each charm is given root access on the
>> machine
>> to configure whatever services are actually needed. And there isn't
>> part of
>> the spec that has them define where the configuration files are
>> going, what
>> things th
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 inclu
On 11/07/14 09:44, Tudor Rogoz wrote:
> Is it possible to access the juju environment properties directly from the
> hooks?
> More precisely, I want to have access to the AWS credentials (defined in the
> environments.yaml file) directly from the hooks, is this possible? I can
> workaround the s
On 11/07/14 13:14, Jorge Niedbalski wrote:
> Also related, but not directly implied, there is a lost-in-time
> mailing list thread regarding to secret configuration buckets (
> https://lists.ubuntu.com/archives/juju/2014-May/003885.html )
>
> I am not sure if somebody had a chance to work implement
On 16/07/14 06:12, Gaurav Pandit wrote:
> 1. Is it correct to say that each machine created by juju in the
> environment is basically an Ubuntu OS (most likely 14.04)?
> 2. If that's the case, then
> a. Does it mean that the commands executed in hooks, say, a basic bash
> script that installs a p
On 22/08/14 13:35, Tudor Rogoz wrote:
> Does anyone knows how to determine when a relation is establish (when the
> relation joined or relation changed hooks ended) ? The goal would be to be
> able to synchronously run the "juju add-relation" command.
Hi Tudor, we'll add an explicit feedback mec
On 27/08/14 00:10, Matt Bruzek wrote:
> First and most importantly the hpcc charm deploys according to the readme
> file! I had to increase the memory constraints on the HP-cloud to 4GB per
> machine (juju set-constraints mem=4GB) so all the services had enough
> memory to start up. After that I w
On 27/08/14 03:03, Sameer Zeidat wrote:
> About immutable configuration parameters. IMHO it'd make a better user
> experience if juju added support for them.
>
Yes, that's a good suggestion, we'll work it into the roadmap, patches
welcome!
Mark
--
Juju mailing list
Juju@lists.ubuntu.com
Modif
Rather cool as a telco-oriented PAAS, looking forward to giving it a spin!
When we review a charm do we bring it up on various clouds? Do we have
any way to verify that it works on, say, OpenStack and EC2?
Mark
On 04/09/14 14:05, Tim Van Steenburgh wrote:
> Yesterday I reviewed devspace-simulat
On 22/09/14 15:06, Mark Ramm-Christensen (Canonical.com) wrote:
> I think we need to make sure that we do the best error reporting we can, so
> if Juju isn't working because of Azure issues, we should find some way to
> let users know that so that they can try another cloud, contact microsoft,
> or
On 22/09/14 15:08, Michael Schwartz wrote:
> Agreed. There is only one page on Azure, so it would be nice if there
> was a note that said
> "Don't waste your time... Azure isn't working today."
Or better, Juju automatically checks a cloud weather report which we
publish that tells you this definit
On 22/09/14 19:40, Charles Butler wrote:
> It may be still in the ingest-o-tron, pending ~ 20 minutes from posting,
> but I've just landed 3 new big data bundles for our data scientists out
> there to consume for our new Hortonworks Hadoop stack.
>
> Deploy the base Hadoop Map/Reduce engine:
> juju
On 02/10/14 15:46, Robert Jennings wrote:
> Why not change the image-stream to 'daily' from 'release' rather than
> altering whether or not we update packages on an instance?
>
> The default environment configuration specifies that the image stream
> is 'releases' rather than 'daily'. This means t
Versions, versions, everywhere :)
To clarify this conversation, let's be more precise about the things
that are being upgraded:
Juju itself has three parts:
* the juju client (usually installed on your workstation from a package)
* the juju server (installed by the bootstrap process)
* the j
Hi Nate
Tagging services to networks is in the next cycle plan; for now what we
ourselves do is use some of the explicit charm config in the OpenStack
charms to achieve the same thing. I believe most of the OpenStack charms
will let you provide a CIDR and then bind to that network.
Separately, yo
On 24/10/14 15:28, Nate dell wrote:
> I'll look at binding specific cdrs to the openstack charms. It sounds like
> your suggesting using a configuration management system like salt, ansible,
> puppet, or chef in conjunction with juju. Ansible is setup at the client so
> will look to integrate the t
On 29/10/14 04:47, Chris Glass wrote:
> I think it makes a lot of sense to let people (or teams) who are
> particularly interested in a specific set of charms to become "real"
> maintainers, as is done for Ubuntu packages.
Agreed; the pattern is to identify teams and then give them rights for
cohe
On 25/10/14 18:26, Dimiter Naydenov wrote:
> In the mean-time, until Juju starts to provide this feature, you can
> consider a workaround.
>
> It looks like all openstack charms can have a subordinate unit (on the
> same machine) via the hacluster relation. If you write a shared
> subordinate charm
On 10/11/14 19:20, John McEleney wrote:
> Over the weekend I've been updating to Juno, and I naturally updated to
> the latest stable charms from the Charm store. Breaking changes have
> been introduced to these charms such that they no longer support my
> deployment. My Openstack cluster promptly
On 11/11/14 10:28, John McEleney wrote:
> From the perspective of someone using the charms, these changes seem
> to have come out of the blue, and the built-in Charm documentation
> (readme, config etc.) doesn't provide an overview of how this new
> multi-NIC HA is supposed to work.
>
> Maybe it's
On 11/11/14 16:20, John McEleney wrote:
> I think there's some blurring of lines between the roles played by MAAS,
> Juju and charms in this area. Thinking about it I think that Juju and
> Juju's driver for MAAS is the area where this mysterious multi-NIC HA
> set-up resides, rather than this being
On 12/11/14 15:57, Stein Myrseth wrote:
> With the latest versions the same process it is no more intuitive how to
> deploy anymore. I hit “confirm” and “commit” and nothing happens. I have
> create a machine first, or auto place, or add the constraints or as part of
> the unit configuration, or
On 13/11/14 14:43, Charles Butler wrote:
> I gave the MariaDB charm a review yesterday - and it landed! You can now
> deploy MariaDB on trusty via: juju deploy cs:trusty/mariadb and enjoy
> knowing you're getting the best practices from the MariaDB developers. big
> hat tip to dbart over @ mariadb
On 14/11/14 02:39, Sameer Zeidat wrote:
> Hello,
> I'm running juju 1.20.1 on a test maas cluster. Every now and then when I run
> juju add-machine the machine gets stuck at "pending" state (permanently).
> Maas shows status as "Failed deployment".
> Is there a way to force machine state to erro
Hi Sameer
No problem, this is the right place to ask. There was a thread on this
topic on this list a month or two back, so look there for more detail,
but in short:
* get cloud-init to run scripts on your behalf on install, or
* use a subordinate charm if the work can be done after the main
se
On 17/11/14 06:35, Sameer Zeidat wrote:
> Reporting back. The latest release from the archive fixed it. Thank you.
Great to hear. We'll SRU 1.20.latest to Trusty and Utopic shortly.
Mark
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mail
Elsewhere we have a need to treat all the interim releases as a
continuous rolling development series. I think the same is true here, we
should have a series "devel" which represents the current daily in the
development release, what ever that is, and allow charms to target that.
Those charms coul
On 15/01/15 15:25, Vahric Muhtaryan wrote:
> I m so new to juju and try to learn it.
> We are cloud provider and we would like to push our customers use it .
Welcome!
> My question is a bootstrap server is need but this means additional resource
> is needed , means customer need to pay more
>
> W
There are two distinct features aiming for 1.21 which address your needs:
* multiple environments in a single juju server
* multiple users in a single juju server
The combination will allow you to:
* bootstrap Juju once (perhaps across a few servers for HA)
* create several user accounts on
On 22/01/15 14:28, Mark Shuttleworth wrote:
> * those users can then create environments as and when they need them
>* each environment has its own cloud credentials
My mistake, looks like the multiple-environments-per-server option is
targeted to 1.22! Looking forward to it.
On 28/01/15 09:38, Sajith Vijesekara wrote:
> I got your point.So i followed this (
> http://askubuntu.com/questions/166102/how-do-i-configure-juju-for-deployment-on-rackspace-cloud)
> documentation to bootstrap openstack in rack-space. But documentation is
> not clear at all. If rackspace doesn't
On 28/01/15 10:17, Mark Shuttleworth wrote:
> On 28/01/15 09:38, Sajith Vijesekara wrote:
>> I got your point.So i followed this (
>> http://askubuntu.com/questions/166102/how-do-i-configure-juju-for-deployment-on-rackspace-cloud)
>> documentation to bootstrap opensta
On 30/01/15 19:12, Samuel Cozannet wrote:
> Yeah, the bundle fails because there is a race condition happening. Instead
> of quickstarting it, use the deploy script (00-deploy.sh) and you should be
> alright.
Today, all you can see is that a charm has finished doing all the things
that it expected
On 25/02/15 11:30, Rajendar K wrote:
> Quite new to this forum.
Welcome!
> I would like to know the details about the juju-API for communication to
> public clouds (Amazon, etc).(where i can download
> and start using)
There is code built into Juju that knows about each cloud; we call
I'd like to propose that we adopt a "minimum footprint by default"
guidance for charmers, with a convention for how you might say "in this
case, assume you're the dominant workload" or "feel free to use XYZ
resources".
By this I mean that a charm deployed with default config would adopt a
lowest-
Hi Dan, yes, we're very glad to have full cross-platform support for a
wide range of OS's and Alessandro cc'd would be the right person to
discuss Windows charms and features.
Mark
On 13/03/15 07:50, Dan Ports wrote:
> Hi guys,
>
> I've been following Juju for some time and I really like the way
On 13/03/15 12:34, James Beedy wrote:
> The issue I am having is
> that storage traffic on my compute and storage nodes seems to be routed
> through the 1G interfaces which are on the os-admin-network and my
> ceph-public-network(os-admin-network == ceph-public-network).
I believe there is a confi
On 07/03/15 00:16, Stuart Bishop wrote:
> So the configuration defaults would be automatic tuning disabled, and
> manual tuning defaults set for minimal usable? That can be done today.
>
> An alternative would be for charms to specify their minimal VM
> requirements, and have juju deploy provision
On 17/03/15 09:40, Matt Bruzek wrote:
> docker
>
> https://bugs.launchpad.net/charms/+bug/1413775
>
> This charm passed charm proof and all the tests passed! I promulgated this
> charm. Very excited to have a docker charm in the recommended section of
> the charm store!
I'll second that - great
On 25/03/15 20:01, Merlijn Sebrechts wrote:
> I'm interested in what the future of Juju is. From the small experience
> I've had with it, it seems like a product with a lot of potential. It fills
> a gap in our project that no other technology can fill. Its biggest
> strength is how relations betwe
On 27/03/15 17:13, Ali Saidi wrote:
> I'm trying to understand how multiple users can interact with MaaS and
> Juju.
>
> It seems like some support is now available [1,2], although I'm not certain
> what state it's in. Is there any documentation about the different use
> models for multiple users i
On 27/03/15 18:43, Sameer Zeidat wrote:
> Your nodes need to have their PXE boot NIC in the same subnet where MAAS is.
> PXE protocol isn't routable.
Well... DHCP isn't routable, and you DHCP before you PXE. DHCP can be
forwarded if you have special support for that setup in the network.
AFAIK,
Great to see both stories coming together - hyperscale hyper dense ARM
servers, and Juju!
Mark
On 02/04/15 14:26, Jorge O. Castro wrote:
> Hi everyone,
>
> Online Labs have launched Scaleway: https://www.scaleway.com/
>
> These are dedicated ARM bare metal machines with SSDs, official images, an
On 15/04/15 11:51, Robert Day wrote:
> I agree that not having juju-deployer handle the Git side of things, and just
> working locally from a Git checkout, would be simpler – but I don’t think
> that sort of bundle would work in the Juju GUI, because the extra steps
> needed mean that you can’t
On 03/05/15 10:37, Marco Ceppi wrote:
> Hello everyone,
>
> I'm excited to announce a small project I've been working which uses the
> jujusvg project from Juju to render bundles in to consumable SVG. The goal
> was to produce an image one might find in the GUI without having to load or
> deploy th
I think the absence of num_units is in fact an invitation to prompt the
user for this information. It corresponds to a shared description of the
*topology* independent of scale. With bundle composition, this allows us
to have a root bundle which describes the services and configuration and
relatio
On 15/05/15 13:08, roger peppe wrote:
> I like this take on it - it fits well with my intuition in the matter too.
> Unless I misunderstand, this "topology only" view would work well with a
> zero unit count as a default, because that way you can deploy the services
> to an environment, creating th
On 15/05/15 13:14, Matt Bruzek wrote:
> I spent some time in the review queue today. I reviewed an improvement
> that IBM charmers made to the websphere-liberty charm. This was a good fix
> and I was happy to merge this with the existing charm in the recommended
> section of the charm store.
Gre
On 11/05/15 11:39, Charles Butler wrote:
> There is however, a bit of work that needs to be done to finish this charm
> up, sand off the rough edges and make sure we're compatible with existing
> deployments on our upgrade path.
Just an FYI, a very interesting telco product from one of the larger
On 15/05/15 23:21, Samuel Cozannet wrote:
> Hi Mark,
>
> Along those lines, Logstash 1.5 just fresh out of dev is compliant with
> Kafka.
>
> it is now possible to build very powerful real time analytics solution on
> logs as Kafka can then plug into Spark or Storm.
>
> Would that be of interest in
On 25/05/15 18:57, Kapil Thangavelu wrote:
> That's super awesome, and very helpful for real world usage. A few
> suggestions, For users with multiple environments, seeing a bunch
> machine-0 in the ui, is rather confusing, i'd suggest prefixing with
> the env name. Potentially even more useful is
On 29/05/15 04:47, Andrew Wilkins wrote:
> I think going with a static name and adding the additional information in
> tags is the best way forward.
> It does mean that you have to click an extra level down, but that's going
> to be true of everything other
> than AWS anyway. This way we can reserv
Hi Vasiliy
We'd like to move bundle processing into Go, and actually build it
straight into Juju core. If you are interested to help with that,
William cc'd would be a good person to chat with, or could point you to
the right person.
Thank you!
Mark
On 04/06/15 00:37, Jeff Pihach wrote:
> Hi Va
On 21/06/15 08:43, Whit Morriss wrote:
> - docker/0: 52.27.4.236 (started) 3000/tcp, 49154/tcp
> - heka-agent/1: 52.27.4.236 (started)
> - registrator/1: 52.27.4.236 (started)
> - docker/1: 52.24.16.120 (started)
> - heka-agent/0: 52.24.16.120 (started)
> - reg/0: 52.24.16.120 (started)
>
On 02/07/15 06:50, dinesh.senap...@wipro.com wrote:
> Hi,
> I have been trying to bootstrap juju for 'openstack' environment. The
> instance being created and floating ip is also associated and also I am able
> to ping that instance but later bootstrap fails when it is "attempting to
> connect"
This will improve with the move to LXD, which manages images and will
include code to ensure that your system always has up-to-date images.
Then, when you ask for a container, it can be virtually instantaneous :)
Mark
On 03/07/15 08:44, Andrew Wilkins wrote:
> Hi Suchitra,
>
> The first time you
Looks great Charles, thank you! Are the colours significant?
Mark
On 20/07/15 11:49, Samuel Cozannet wrote:
> Good one, thanks!
>
> Best,
> Samuel
>
> --
> Samuel Cozannet
> Cloud, Big Data and IoT Strategy Team
> Business Development - Cloud and ISV Ecosystem
> Changing the Future of Cloud
> Ub
On 30/07/15 17:36, ed bond wrote:
> Being able to place a bundle’s units is awesome, but being able to upload a
> single config for all of the bundles configs. Things like ceph resilience and
> ceph devices have to be set on the first deploy of the unit and can’t be
> changed afterwards.
Hi Ed
In the case of OpenStack, most of the charms support config options to
bind specific services to specific networks.
So, you can:
* run a base script to bind the network interfaces you need to the
networks / vlans you want
* set the config per charm manually
... which works, and it's how we do
On 14/08/15 04:56, Stuart Bishop wrote:
> I've discussed similar things with regard to the PostgreSQL charm and
> autotuning, with the decision being that charm defaults should be set
> so things 'just work' in a development environment.
Yes, charm defaults should be efficient for rapid iteration
On 17/08/15 06:03, Simon Davy wrote:
> I think maybe there is a distinction between performance defaults and
> security defaults, and defaults can be dev on the former, and
> production on the latter, maybe?
Agreed, defaults should be "correct and secure".
Mark
--
Juju mailing list
Juju@lists.u
On 21/08/15 04:28, Charles Butler wrote:
> I took a look at the plumgrid stack which after an architectural
> refactoring is very close to being accepted. There are simple nitpick final
> round revisions to the project meta that need to be cleaned up so we ensure
> they have a good segway into the
Hi Bruno
HPC is interesting to us. For 16.04 LTS one of the goals is diskless
MAAS, which is in part driven by a desire to drive large-scale
automation in some of the super-computers where Ubuntu is in heavy use
already. That would dovetail nicely with your interests, by the look of
it, if there w
On 25/08/15 14:20, Bruno Pereira wrote:
> Diskless is tricky using the current structure of MAAS (at least on the
> stage I last tested it around 1 year ago), its fairly simple to do, but not
> if you follow a install with a reboot in to OS, similar to kickstart
> installations, structure.
>
> For
Thanks for the background, Peter.
On 26/08/15 21:36, Peter Grandi wrote:
>
>> We never made it an official release in Trusty so clearly you
>> were informed about our PPA.
> That PPA gets mentioned on the mailing list and IRC channel
> occasionally, plus some "unofficial" pages mention it too, bu
On 28/08/15 11:30, Liam Young wrote:
> Fwiw I raised Bug #1240431 a while ago because I also felt that it wasn't
> intuitive that the
constraints passed when bootstrapping refereed to the whole environment.
The shift to have multiple environments in a single juju server means
that we obviously h
On 01/09/15 13:44, Peter Grandi wrote:
>> https://bugs.launchpad.net/juju-core/+bug/1447899 The bug is
>> fixed in the recently released 1.25-alpha1. What you can try on
>> your system is to explicitly specify the version you want to
>> upgrade to:
> Had a look and forgot to mention that I tried t
On 07/09/15 17:32, Tom Barber wrote:
> By default the thrift server doesn't run and port 1 isn't exposed.
>
> Do I need to fork and change the charm or is there a work around I can
> employ for now?
I'm not the expert, but perhaps a subordinate charm could be glommed in
to do just what you nee
On 17/09/15 13:09, Kapil Thangavelu wrote:
> The network support listed in the 1.25 alpha release notes ( >
> https://lists.ubuntu.com/archives/juju-dev/2015-August/004721.html )
looks > pretty good, i'll give it a whirl.
Hey rockstar, nice to see you around again! Thanks for any feedback.
Mark
1 - 100 of 320 matches
Mail list logo
