parallelvirtualcluster
/
pvc
1
0
Fork 0
Code Issues 11 Pull Requests Projects Releases 111 Wiki Activity
pvc/debian/pvc-daemon.postinst

18 lines
803 B
Plaintext
Raw Normal View History

Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
#!/bin/sh
Add node autoflush service and target Add a systemd service to manage node flush/unflush, useful during system startup and shutdown to avoid requiring administrator intervention for this to occur. This is optional and the service is not enabled by default, and the postinst script informs the administrator of this. Also adds a systemd target to collect the two service units together and provide an easy way to flush+shutdown or startup+unflush the entire PVC system. Closes #28
2019-05-23 22:38:45 -04:00
# Enable the service and target
Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
systemctl enable /lib/systemd/system/pvcd.service
Add node autoflush service and target Add a systemd service to manage node flush/unflush, useful during system startup and shutdown to avoid requiring administrator intervention for this to occur. This is optional and the service is not enabled by default, and the postinst script informs the administrator of this. Also adds a systemd target to collect the two service units together and provide an easy way to flush+shutdown or startup+unflush the entire PVC system. Closes #28
2019-05-23 22:38:45 -04:00
systemctl enable /lib/systemd/system/pvcd.target
Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
Add node autoflush service and target Add a systemd service to manage node flush/unflush, useful during system startup and shutdown to avoid requiring administrator intervention for this to occur. This is optional and the service is not enabled by default, and the postinst script informs the administrator of this. Also adds a systemd target to collect the two service units together and provide an easy way to flush+shutdown or startup+unflush the entire PVC system. Closes #28
2019-05-23 22:38:45 -04:00
# Inform administrator of the autoflush daemon if it is not enabled
if ! systemctl is-active --quiet pvc-flush.service; then
echo "The PVC autoflush daemon (pvc-flush.service) is not enabled by default; enable it to perform automatic flush/unflush actions on host shutdown/startup."
fi
# Inform administrator of the service restart/startup not occurring automatically
Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
if systemctl is-active --quiet pvcd.service; then
Add node autoflush service and target Add a systemd service to manage node flush/unflush, useful during system startup and shutdown to avoid requiring administrator intervention for this to occur. This is optional and the service is not enabled by default, and the postinst script informs the administrator of this. Also adds a systemd target to collect the two service units together and provide an easy way to flush+shutdown or startup+unflush the entire PVC system. Closes #28
2019-05-23 22:38:45 -04:00
echo "The PVC node daemon (pvcd.service) has not been restarted; this is up to the administrator."
Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
else
Add node autoflush service and target Add a systemd service to manage node flush/unflush, useful during system startup and shutdown to avoid requiring administrator intervention for this to occur. This is optional and the service is not enabled by default, and the postinst script informs the administrator of this. Also adds a systemd target to collect the two service units together and provide an easy way to flush+shutdown or startup+unflush the entire PVC system. Closes #28
2019-05-23 22:38:45 -04:00
echo "The PVC node daemon (pvcd.service) has not been started; create a config file at /etc/pvc/pvcd.yaml then start it."
Massive rejigger into single daemon Completely restructure the daemon code to move the 4 discrete daemons into a single daemon that can be run on every hypervisor. Introduce the idea of a static list of "coordinator" nodes which are configured at install time to run Zookeeper and FRR in router mode, and which are allowed to take on client network management duties (gateway, DHCP, DNS, etc.) while also allowing them to run VMs (i.e. no dedicated "router" nodes required).
2018-10-14 02:01:35 -04:00
fi