Lots of CI emails end up in spam for me unless I specifically tell
gmail not to. You can do this by creating a filter and ticking the
never send to spam box, so for internal lists you could trust them.
People in your contacts are trusted more than those who aren't for
spam filtering purposes, but
Hi Stephen,
MAAS would be your first node, if configured robustly enough, it can also
run Ubuntu Infrastructure services such as Juju and LandScape. The MAAS
server should be on bare metal and separate from any of your OpenStack
services.
Regards,
Rafael O. Gonzalez
Canonical, Solutions
Hi,
I’m running MAAS and able to hard code the
Nodes in, but when I try to PXE boot, they
hang and cannot connect to MAAS.
Prior to PXE, I confirmed by ICMP that machines
were getting responses VIA internal routing
address.
Could I be missing a config file in MAAS
main controller?
Cheers,
Also noting that running MAAS in a vm has worked fine in my experience. Are
there any pitfalls with using a vm?
Matt
On Fri, Mar 27, 2015 at 8:22 AM, Rafael Gonzalez
rafael.gonza...@canonical.com wrote:
Hi Stephen,
MAAS would be your first node, if configured robustly enough, it can also
On 03/27/2015 10:08 AM, Matt Rae wrote:
Also noting that running MAAS in a vm has worked fine in my experience. Are
there any pitfalls with using a vm?
Nope - that should work just fine as long as you're using a bridged
interface for the network you want to manage.
I typically run MAAS in an
Hi Stephen, typically you shouldn't need to manually add nodes to MAAS. The
first time the nodes successfully PXE, they should appear in MAAS if the
connectivity is correct. If the nodes aren't able to PXE from MAAS, I think
that is the problem.
If you run 'dhcpdump' on the MAAS server, do you
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 between
On Thu, Mar 26, 2015 at 7:53 PM, Nate Finch nate.fi...@canonical.com wrote:
tl;dr: godeps overrides gopkg.in, so you can have godeps pin a commit from a
different branch than gopkg.in is retrieving (i.e. make a release-number
branch, like 1.22 and use godeps to pin commits from there, even if
That's great to hear that we're addressing issues that our community hasn't
been very vocal about yet.
I feel that the isolation story we're developing with this docker image is
really going to help the developer/testing story. Cory Johns has put in
some work and instructions on how to leverage
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 interacting with Juju? Is there a roadmap of
I just finished building a docker image for anyone who wants to test
juju 1.23-beta2 in a clean environment. By default, it'll setup a new,
persistent environment:
docker run -ti adamisrael/juju-1.23 -v
$HOME/.juju-1.23:/home/ubuntu/.juju
I intend to maintain images for each released version
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
Sorry everyone, the starting date will be _16_ April, thanks!
On Fri, Mar 27, 2015 at 10:44 AM, Jorge O. Castro jo...@ubuntu.com wrote:
We'll be starting on 26 April and I'll be scheduling the recurring
events into the website over the next few days as well as post regular
announcements to
I'm working on juju local/LXC support, in the hopes of improving the
developer workflow cross-platform.
On 2015-03-27 10:50 AM, sheila miguez wrote:
On Fri, Mar 27, 2015 at 10:49 AM, Jorge O. Castro jo...@ubuntu.com
mailto:jo...@ubuntu.com wrote:
let's you just try Juju, with the
Hi everyone,
Over the past few months we've had a surge of interest in Juju,
resulting in lots of great peer-to-peer instruction and knowledge
sharing. Now it's time to add-unit. :)
We're going to now do a recurring Juju Office Hours twice a month
for users to ask us any questions directly,
What does this do that just using the juju binary on your local system
doesn't do?
On Fri, Mar 27, 2015 at 11:49 AM, Jorge O. Castro jo...@ubuntu.com wrote:
Hi everyone,
First, if you haven't seen this yet, this is a docker container that
let's you just try Juju, with the limitation that you
It seems Jorge omitted why this is useful. When doing charm reviews or
performing charm testing (while developing) you can use the docker
container to quickly spin up an isolated environment so the charm can
execute it's testing dependencies without dirtying the testers system.
We're also now
Hi everyone,
First, if you haven't seen this yet, this is a docker container that
let's you just try Juju, with the limitation that you can't do the
local provider.
- https://registry.hub.docker.com/u/whitmo/jujubox/
- https://github.com/whitmo/jujubox
And here's the new bits, Cory Johns has
Just an FYI:
As you've probably heard, code.google.com is going away. It'll be
read-only for a year IIRC and then *poof*.
Most of the packages from the go authors lived there (crypto, etc), but now
will be maintained at golang.org/x. We'll be changing our imports to point
at the new repos, so
Using the docker box is a complete isolation from your local system. We're
building docker images to scratch some itches:
- Run latest juju in full isolation so we can test the new features as they
land
- Isolate dependencies during charm reviews. (00-setup as sudo on your
system leaves WHAT
And here's a docker image of juju trunk:
docker run -ti -v $HOME/.juju-trunk:/home/ubuntu/.juju
adamisrael/juju-trunk
This is a nightly build of trunk, for those of us who want to explore
the bleeding edge. The image contains the go compiler, git, and the
source installed under ~/.go/. It
On Fri, Mar 27, 2015 at 9:59 AM, Nate Finch nate.fi...@canonical.com wrote:
Just an FYI:
As you've probably heard, code.google.com is going away. It'll be read-only
for a year IIRC and then poof.
Most of the packages from the go authors lived there (crypto, etc), but now
will be maintained
Addendum: the actual command to run is:
docker run -ti -v $HOME/.juju-1.23:/home/ubuntu/.juju
adamisrael/juju-1.23
On 2015-03-27 11:43 AM, Adam Israel wrote:
I just finished building a docker image for anyone who wants to test
juju 1.23-beta2 in a clean environment. By default, it'll
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,
So it doesn't seem terrible for something that is just a copyright fix.
*but* Having go get give you something very different than what we build
with is just going to bite us in the future.
John
=:-
On Mar 27, 2015 7:08 PM, Eric Snow eric.s...@canonical.com wrote:
On Thu, Mar 26, 2015 at 7:53
25 matches
Mail list logo
