Doc for cluster registration is wrong

Bug #1348341 reported by Nicolas Thomas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Medium
Unassigned

Bug Description

http://maas.ubuntu.com/docs/development/cluster-registration.html

Say to put region manually, looks to work but then RabbitMQ is not connecting.

 sudo dpkg-reconfigure maas-cluster-controller

To the contrary "after answering debconf" works !! ..

Please update

Tags: doc trivial
Revision history for this message
Nicolas Thomas (thomnico) wrote :
Revision history for this message
Nicolas Thomas (thomnico) wrote :

On Trusty.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'm sorry I don't understand which piece of the document is wrong. Could you be more specific than "Say to put region manually"

Thank you.

Changed in maas:
status: New → Incomplete
Revision history for this message
Nicolas Thomas (thomnico) wrote : Re: [Bug 1348341] Re: Doc for cluster registration is wrong

The piece of doc is the URL provided in the initial bug report

On Fri, Jul 25, 2014 at 9:54 AM, Julian Edwards
<email address hidden> wrote:
> I'm sorry I don't understand which piece of the document is wrong.
> Could you be more specific than "Say to put region manually"
>
> Thank you.
>
> ** Changed in: maas
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1348341
>
> Title:
> Doc for cluster registration is wrong
>
> Status in MAAS:
> Incomplete
>
> Bug description:
> http://maas.ubuntu.com/docs/development/cluster-registration.html
>
> Say to put region manually, looks to work but then RabbitMQ is not
> connecting.
>
>
> sudo dpkg-reconfigure maas-cluster-controller
>
> To the contrary "after answering debconf" works !! ..
>
> Please update
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1348341/+subscriptions

--
Best Regards,
       Nicolas Thomas
http://insights.ubuntu.com/?p=889
EMEA Sales Engineer Canonical
GPG FPR: D592 4185 F099 9031 6590 6292 492F C740 F03A 7EB9

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Friday 25 Jul 2014 08:34:09 you wrote:
> The piece of doc is the URL provided in the initial bug report

Yes and I can't see which part of it you mean. Can you please be specific.

Revision history for this message
Nicolas Thomas (thomnico) wrote :

You should replace this :
Cluster configuration file
This config file generally contains two items like this:

MAAS_URL=http://0.0.0.0:5240/
CLUSTER_UUID="adfd3977-f251-4f2c-8d61-745dbd690bf2"
The values here are the defaults in the development environment. MAAS_URL tells the cluster controller where to find the region controller, and is sourced as a shell script by services/cluster-worker/run.

CLUSTER_UUID is what the region uses to tell clusters apart when they connect. Each cluster is free to generate its own UUID but the development environment fixes it in advance. The Ubuntu packaging generates a new UUID for a cluster controller each time it is installed.

Warning
The format of this config file is very sensitive due to the code that parses it. It will not accept quoting, or any kind of comments.

By:

Configure Cluster:

sudo dpkg-reconfigure maas-cluster-controller

Give the IP or name of the region-controller.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Thank you for replying with the details.

The existing text is meant to be a technical explanation, but adding the packaging shortcut which does the reconfiguration for you would be a nice change, thank you for the suggestion.

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: doc trivial
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.