This short chapter explains how you, the platform operator, deal with the essential platform management issues. Operators act upon the platform using only four essential commands. This is depicted next:
Where the yellow server is the administration server.
By now you already know the
We will now have a look at
punchctl configuration command.
The principles are quite simple to understand. A first good news: there are almost no difference in managing a standalone platform (as the one you have now running on your machine) and a full fledge-distributed production platform.
To save or load configurations, you can use respectively
configuration pull and
The punch relies on zookeeper for maintaining configuration information.
Loading or saving the configuration is as simple as executing getconf and putconf:
It cannot be simpler. Let us see this in action on the standalone.
The first thing you should do is to save your tenant configuration. The configuration
is a set of files stored both in your
$PUNCHPLATFORM_CONF_DIR folder and in ZooKeeper.
Saving it is important for two reasons:
- it will be saved and replicated within ZooKeeper. ZooKeeper is used to ensure configuration high-availability. In other words, losing a server configured with some specifics parameters does not matter anymore as you will be able to easily start a new one with the exact same configurations.
- once the configuration are stored in ZooKeeper, it will be available to all platform servers and components that requires it.
Go for it, simply type in:
punchctl configuration --push
This command flushes the content of the
$PUNCHPLATFORM_CONF_DIR/tenants/mytenant folder to ZooKeeper.
In order to fetch the saved configuration you simply execute:
punchctl configuration --pull
That will simply fetch from ZooKeeper the saved configuration and write it back into