revi-archive/phorge-phorge
1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-12-24 14:30:56 +01:00
Code Issues Releases Wiki Activity

Cleanup some clustering rough edges

Browse source 
Summary: Suppress an unhelpful Almanac transaction and document the location of the secret clustering management capability. I thought maybe implementing `shouldHide` and checking for `isCreate` would work, but the binding apparently gets created before an interface is bound to it.

Test Plan: Looked at a fresh binding and didn't see "Unknown Object(??)", ran bin/diviner and saw expected output.

Reviewers: epriestley

Reviewed By: epriestley

Subscribers: Korvin

Differential Revision: https://secure.phabricator.com/D19917
This commit is contained in:
Austin McKinley 2018-12-19 16:24:12 -08:00
parent 979187132d
commit c72d29f401
2 changed files with 28 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
src/applications/almanac/xaction/AlmanacBindingInterfaceTransaction.php
View file

@ -55,11 +55,22 @@ final class AlmanacBindingInterfaceTransaction
} }
public function getTitle() { public function getTitle() {
return pht( if ($this->getOldValue() === null) {
'%s changed the interface for this binding from %s to %s.', return pht(
$this->renderAuthor(), '%s set the interface for this binding to %s.',
$this->renderOldHandle(), $this->renderAuthor(),
$this->renderNewHandle()); $this->renderNewHandle());
} else if ($this->getNewValue() == null) {
return pht(
'%s removed the interface for this binding.',
$this->renderAuthor());
} else {
return pht(
'%s changed the interface for this binding from %s to %s.',
$this->renderAuthor(),
$this->renderOldHandle(),
$this->renderNewHandle());
}
} }
public function validateTransactions($object, array $xactions) { public function validateTransactions($object, array $xactions) {

13
src/docs/user/cluster/cluster_repositories.diviner
View file

@ -98,7 +98,7 @@ repository to retrieve the data it needs. It will use the result of this query
to respond to the user. to respond to the user.
Setting up a Cluster Services Setting up Cluster Services
============================= =============================
To set up clustering, first register the devices that you want to use as part To set up clustering, first register the devices that you want to use as part
@ -107,6 +107,17 @@ of the cluster with Almanac. For details, see @{article:Cluster: Devices}.
NOTE: Once you create a service, new repositories will immediately allocate NOTE: Once you create a service, new repositories will immediately allocate
on it. You may want to disable repository creation during initial setup. on it. You may want to disable repository creation during initial setup.
NOTE: To create clustered services, your account must have the "Can Manage
Cluster Services" capability. By default, no accounts have this capability,
and you must enable it by changing the configuration of the Almanac
application. Navigate to the Alamanc application configuration as follows:
{nav icon=home, name=Home >
Applications >
Almanac >
Configure >
Edit Policies >
Can Manage Cluster Services }
Once the hosts are registered as devices, you can create a new service in Once the hosts are registered as devices, you can create a new service in
Almanac: Almanac: