A community is a logical set of servers being managed by a single logical Community Controller (there might be multiple/redundant controllers, but they work as one). A Community Controller is a Prophecy instance responsible for managing other servers in a community. The community controller is the only Prophecy instance running the Prophecy Management console. A Community Member Server is a server in a community managed by the Community Controller (Note: the Community Controller can also be a community member; in fact, that is the default for any new installation).
The Controller is not a critical element for performing calls in a community because the call-dependent/critical data on the controller is replicated to every member server. A community will still be able to handle calls even when the controller is down.
Becoming a Controller
Every new installation of Prophecy is, by default, a Controller and a member belonging to itself. By default, the controller's IP address is 127.0.0.1, which works fine when there is only one (local) member; however, before adding additional Prophecy servers as members of this controller, you need to update the controller's configured IP address to its external. To do this, select the Community Manager link on the Prophecy Home Page, enter the server section, and update the IP address.
Joining an Existing Community
To join an existing community select the Community Manager link on the Prophecy Home Page, which opens the Community Manager. Depending on whether the server you are on is a controller or already belongs to an different controller, you will see different options. If you are on a controller, you will have the option to join a different controller; if you already belong to a controller, you will have the option to switch controllers. In either case, enter the IP address of the new controller and enter valid credentials.
When a member joins a community, it will automatically be added to the list of servers in the new community; however, it will not be added to any groups and its resources will not be made available to any (existing) virtual platforms. After the member has joined a community, the community administrator will have to add the server to the relevant groups in order to make the member's services available to applications. Once a member has joined a another controller, it will stop the local controller services (Note: no data is actually deleted when this occurs – if the member leaves a controller at a future date, local controller services/data will be restored to the state it was in prior to joining the external controller.
Leaving a community
You will find an option to leave a community within the Community Manager. When a member leaves a community, the controller will be notified of this so it can update the community's data to reflect the member's removal of associated resources. There is, of course, always the possibility the external controller no longer exists – in this scenario, choose the option to forcefully leave a controller/community; however, be careful selecting this option. A forceful removal from a live, operational community when the controller is temporarily down means the community at-large will not be properly informed of the loss of a member. That server's services will still be considered available by the remaining community members.
After a server has left a community, it will bring up its own controller services and become a member and controller on its own. This will restore the controller to the state it was in when it last was a controller and no configuration from the previous community will be migrated.
ANNOTATIONS: EXISTING POSTS
0 posts - click the button below to add a note to this page
