Changes

stoney backup: prov-backup-rsnapshot

294 bytes added, 15:43, 1 November 2019
= Overview =
This pages contains all necessary information one needs to know about the prov-backup-rsnapshot provisioning daemon. This daemon provisions the stoney backup account according to what was requested in the selfcare self-service web interface. Changes performed on the web interface (for example creating a new stoney backup account) will be written to the LDAP directory. The changes in the LDAP directory are spotted by the prov-backup-rsnapshot daemon , which then can set up executes the appropriate action (for example creating directories and setting quota values for the new stoney backup account) and change the LDAP again. This change in the LDAP will then can be made visible in the web interface. Like that This way the user can see, that the new stoney backup account it requested is now ready to for use.@PAT= Source Code =The source code is located in our GitHub Repository: What's the purpose of the '' https://github.com/stepping-stone/prov-backup-rsnapshot daemon''? Please write a short introduction == Exit Codes ==The following list defines the return codes and their meaning for the ... --[[User:Chrigu|Chrigu]] ([[User talk:Chrigu|talk]]) 10:02<pre>use constant{ SUCCESS => 0, 19 June 2014 (CEST) UNDEFINED_ERROR => 1, USER_NOT_PRESENT_IN_BACKEND => 2, PERL_VERSION_NOT_STATISFIED => 3, CANNOT_CHECK_HOME_DIR_PRESENCE => 4, CANNOT_CREATE_HOME_DIR => 5, CANNOT_SET_QUOTA => 6, CANNOT_CREATE_RSNAPSHOT_CONFIGURATION => 7,};</pre>
= Configuration =
...
</source>
 
= Source Code =
The source code is located in our GitHub Repository:
 
https://github.com/stepping-stone/prov-backup-rsnapshot
 
== Exit Codes ==
The following list defines the return codes and their meaning for the ...:
<pre>
use constant
{
SUCCESS => 0,
UNDEFINED_ERROR => 1,
USER_NOT_PRESENT_IN_BACKEND => 2,
PERL_VERSION_NOT_STATISFIED => 3,
CANNOT_CHECK_HOME_DIR_PRESENCE => 4,
CANNOT_CREATE_HOME_DIR => 5,
CANNOT_SET_QUOTA => 6,
CANNOT_CREATE_RSNAPSHOT_CONFIGURATION => 7,
};
</pre>
= Testing =
** Load the generated LDIF (you find them under /root/data) step by step into the LDAP and observe what the deamon is doing in the first terminal:
*** <pre>/root/loadOpenLDAPsingleLDIF.sh /root/data/01_add_3724300.ldif</pre>
**** After this step, the account with the given uid should be created and you should be able to login via ssh using the uid and the password "gugus":
***** <pre>ssh <UID>@<Server></pre>
*** <pre>/root/loadOpenLDAPsingleLDIF.sh /root/data/02_modify_3724300.ldif</pre>
**** After this step, the quota should be reduced by 50% (from 1GB to 500MB)
***** To verify use the report_xfs quota command as mentioned in [[stoney_backup:_Server_set-up#Modifying_a_Project_.28Directory.29_Quota | server setup]]
*** <pre>/root/loadOpenLDAPsingleLDIF.sh /root/data/03_delete_3724300.ldif</pre>
**** After this step, the account should be removed, the login via ssh should no longer be possible. The LDAP entry however is still present.
***** <pre>ssh <UID>@<Server></pre>
*** <pre>/root/loadOpenLDAPsingleLDIF.sh /root/data/04_remove_3724300.ldif</pre>
 @PAT: What are the expected results of **** After this teststep, how can one verify if it is working correctly? --[[User:Chrigu|Chrigu]] ([[User talk:Chrigu|talk]]) 10:09, 19 June 2014 (CEST)the LDAP entry should be removed
= Links =
[[Category:stoney backup]][[Category:Provisioning Modules]]
SLB, editor, reviewer
3,368
edits