Jeff,
Everyone's network setup can be different and MAAS tries not to be
prescriptive at all but does assume that anyone setting this stuff up
will know a bit about networks. If you are hiding your nodes from the
internet behind your MAAS server then I don't think I'd say that MAAS is
actively
Jeff,
Everyone's network setup can be different and MAAS tries not to be
prescriptive at all but does assume that anyone setting this stuff up
will know a bit about networks. If you are hiding your nodes from the
internet behind your MAAS server then I don't think I'd say that MAAS is
actively
Hi Julian,
I've got several MAAS servers that seem to suffer the same fate,
depending on what your definition of Access the internet is.
We first saw this at the Orange Box sprint in london where nodes could
be deployed via d-i which was pulling packages from MAAS's squid-deb-
proxy, IIRC,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1304613
Then again, perhaps something as simple as a 'maas-enable-nat' command
for these simple cases would be sufficient so new users don't have to
also understand iptables... and makes it optional on the maas server so
you can or can not enable it... maybe it is a per-cluster-controller
thing, as my
As for your question about the region... I don't know... that's
operating at scale. The question there is probably one of hierarchy...
for example, would you have multiple, linked region controllers, or more
like a few region controllers and several cluster controllers under
each?
And in that
To add to this, as I also am experiencing this problem:
My maas has 2 nics and 2 networks:
Outbound eth1: talks to the world (or in thsi case my partner OEM's lab
network
Private eth0: talks only to maas-create nodes. Call it 10.0.0.0/24 .
I've set up maas as DHCP DNS manager for eth0. I
Actually, my last comment encompasses a different problem (that of
isolation), so ignore it.
But do count this as a vote to some kind of NAT on/off tooling in
MAAS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304613
Title:
nodes
Hi Julian,
I've got several MAAS servers that seem to suffer the same fate,
depending on what your definition of Access the internet is.
We first saw this at the Orange Box sprint in london where nodes could
be deployed via d-i which was pulling packages from MAAS's squid-deb-
proxy, IIRC,
As for your question about the region... I don't know... that's
operating at scale. The question there is probably one of hierarchy...
for example, would you have multiple, linked region controllers, or more
like a few region controllers and several cluster controllers under
each?
And in that
Then again, perhaps something as simple as a 'maas-enable-nat' command
for these simple cases would be sufficient so new users don't have to
also understand iptables... and makes it optional on the maas server so
you can or can not enable it... maybe it is a per-cluster-controller
thing, as my
To add to this, as I also am experiencing this problem:
My maas has 2 nics and 2 networks:
Outbound eth1: talks to the world (or in thsi case my partner OEM's lab
network
Private eth0: talks only to maas-create nodes. Call it 10.0.0.0/24 .
I've set up maas as DHCP DNS manager for eth0. I
Actually, my last comment encompasses a different problem (that of
isolation), so ignore it.
But do count this as a vote to some kind of NAT on/off tooling in
MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jeff,
My nodes can access the Internet perfectly well, which demonstrates that
your problem is entirely dependent on each kind of network set up.
This is partly why there is a proxy setting on the region controller,
but this is not used after the node is installed.
So I think MAAS can do
Hi Jeff,
My nodes can access the Internet perfectly well, which demonstrates that
your problem is entirely dependent on each kind of network set up.
This is partly why there is a proxy setting on the region controller,
but this is not used after the node is installed.
So I think MAAS can do
16 matches
Mail list logo
