** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
** Changed in: maas (Ubuntu)
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So this bit us again when trying to deploy LDS. The process there is:
Install/configure MAAs
Populate MAAS
on MAAS, install juju
Juju bootstrap
juju-deployer install LDS
then go to LDS and it does more stuff.
In this case it really caused pain in several cases where juju would say
bootstrap
So this bit us again when trying to deploy LDS. The process there is:
Install/configure MAAs
Populate MAAS
on MAAS, install juju
Juju bootstrap
juju-deployer install LDS
then go to LDS and it does more stuff.
In this case it really caused pain in several cases where juju would say
bootstrap
Maybe I misunderstand the region controller concept or my
understanding of the MAAS ecosystem is outdated.
AIUI there is a region controller that communicates with multiple
cluster controllers that further manage multiple nodes:
/-- cluster foo - node1.foo, node2.foo, node3.foo
Your case is but one possible configuration of a MAAS installation,
where you have the whole region on a single box.
The region is a collection of application server threads, PostgreSQL and
the soon-to-be-removed Celery. All of these components can be running
across varied hosts for HA reasons.
Maybe I misunderstand the region controller concept or my
understanding of the MAAS ecosystem is outdated.
AIUI there is a region controller that communicates with multiple
cluster controllers that further manage multiple nodes:
/-- cluster foo - node1.foo, node2.foo, node3.foo
Your case is but one possible configuration of a MAAS installation,
where you have the whole region on a single box.
The region is a collection of application server threads, PostgreSQL and
the soon-to-be-removed Celery. All of these components can be running
across varied hosts for HA reasons.
Additionally, do we not also use juju, region and cluster on the same
NUC inside the Orange Box? So it seems like it would be important from
the OB perspective to fix this as well. Just an additional use case.
--
You received this bug notification because you are a member of Ubuntu
Server
Hrmmm... it just bit me while trying to test out the checkbox charm on
bare metal from my private maas server. and it's not just a matter of
juju.
for example, MAAS is successfully updating the zone files:
npdxh IN CNAME 10-0-0-123
and I can't ssh to my node by hostname:
Bear in mind that there is no region controller as a single entity, it
is comprised of many discrete components. So far people have been
installing them all in the same place using the convenience of the
maas meta package, so if installing that package it could update
resolv.conf as well, but in
Additionally, do we not also use juju, region and cluster on the same
NUC inside the Orange Box? So it seems like it would be important from
the OB perspective to fix this as well. Just an additional use case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hrmmm... it just bit me while trying to test out the checkbox charm on
bare metal from my private maas server. and it's not just a matter of
juju.
for example, MAAS is successfully updating the zone files:
npdxh IN CNAME 10-0-0-123
and I can't ssh to my node by hostname:
Bear in mind that there is no region controller as a single entity, it
is comprised of many discrete components. So far people have been
installing them all in the same place using the convenience of the
maas meta package, so if installing that package it could update
resolv.conf as well, but in
So we have discussed this before and the reason why this hasn't been
addressed is:
1. resolv.conf gets updated automatically by network manager in some cases,
hence this will cause the change to be lost.
2. This is only required when juju is being used from the MAAS region
controller, meaning
So we have discussed this before and the reason why this hasn't been
addressed is:
1. resolv.conf gets updated automatically by network manager in some cases,
hence this will cause the change to be lost.
2. This is only required when juju is being used from the MAAS region
controller, meaning
15 matches
Mail list logo
