perfsonar-user - Re: [perfsonar-user] pScheduler and postgres
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Mark Feit <>
- To: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>, "" <>
- Subject: Re: [perfsonar-user] pScheduler and postgres
- Date: Mon, 13 Feb 2017 19:33:02 +0000
- Accept-language: en-US
- Authentication-results: nasa.gov; dkim=none (message not signed) header.d=none;nasa.gov; dmarc=none action=none header.from=internet2.edu;
- Ironport-phdr: 9a23:MVVtix9757W9df9uRHKM819IXTAuvvDOBiVQ1KB21OIcTK2v8tzYMVDF4r011RmSDNmduqkP0rCJ+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZPebgFHiTanZb5/Ihq6oRjPusQUnIBvNrs/xhzVr3VSZu9Y33loJVWdnxb94se/4ptu+DlOtvwi6sBNT7z0c7w3QrJEAjsmNXs15NDwuhnYUQSP/HocXX4InRdOHgPI8Qv1Xpb1siv9q+p9xCyXNtD4QLwoRTiv6bpgRQT2gykbKTE27GDXitRxjK1FphKhuwd/yJPQbI2MKfZyYr/RcdYcSGFcXMheSjZBD5u8YYUREuQBIehWoYr8p1QSohSzHhOjCP/qyjJSmnP6wa833uI8Gg/GxgwgGNcOvWzTotrvLqcSUv2+wqnWwjXCc/NdxDDw6I3Gch8/oPGMQal9ccvXyUkzCQzFlFOQppL5Pz+LzOgCrXWU7/d5WO+plmUpqBlxryCxysg2loXFm4cYxk3Z+SlkxYs1K9K1RFJnbdOhEpZfqS6XO5VzT84nXW1kpDs2xqUbtZKnfyUG0ooryh3FZ/CZfIWF5gjvWPuMLTtlgn9uZaixiAyo8Ue6z+3xTsm030hOripCitTCrmwA2RvP5sSaU/dw40Wu1SiW2wDU8e5LP1o4la3GK5492bEwkYcTsULeESPsgEX2lqiWdlk69ee09+TnY7LmppmGO49zlwH+LqAumsu4AeQ7KAQBQ2+b+eGk2L3i+032XqlKg+UonqbDrJzWOMEWqrOkDwNI14sj5RmyAyu63Nkdn3QIMl1IdAyCgoXsJV3CPO30Ae+6g1u2kTdrw/7GPqfmApXINnXDlbnhcqh8605A0wczzNZf545KBbEbJvL8RFPxuMLCAhAnLgO03v7rCM9h2YMGRWKPHqiZPbvKsVCW/OIvLfKMZIgTuDnnMfgp/uPujWQnll8HZqSp2ZoXaGukHvR9PUmVe3vsgtEdEWgUpAo+SvLliEGcXTJJeXm9Qr88tXkHD9fsMIfHAsiCjbub0yrzMtseJk99JHvJTS2zMd3FaMwjVGqzBORU2HRQWrWmUYAskx3oqQ/+47xuNeOS9SoG49arnsB4/ePIkhc773lpFMmH+2CLU2xumG4UHXk70L016Rhlx02Nyq9+iuYdCMde/dtIVBs3L5jR07Y8BtzvDFHvZNCMHXOvWNbuLzwwUpplxtEDYlpVGtO+gwrF0jbwRbIZiurYV9QP7qvA0i2pdI5GwHHc2fxk1gF+Tw==
- Spamdiagnosticoutput: 1:0
Uhl, George D. (GSFC-423.0)[SGT INC] writes: Does pScheduler require postgres to function if it’s installed as part of the perfsonar-tools package? Yes, it does. All of the persistent data storage and many of the processing functions are done in the database. Taking that route cut development time considerably and gave us a lot of sophistication, reliability and integrity we wouldn’t
have had with hand-rolled code. The footprint isn’t very big. All of the development was done in an environment much smaller than our minimum recommended configuration, and its use of resources has been watched carefully. If you’re concerned about security, no use of PostgreSQL leaves the host and the pScheduler database is configured not to accept connections from anywhere other than locally. Authentication is done with a long, random password that’s unique
to every installation, changed whenever the software is updated and stashed away in a place where the few processes that need it can see it. HTH. --Mark |
- [perfsonar-user] pScheduler and postgres, Uhl, George D. (GSFC-423.0)[SGT INC], 02/13/2017
- <Possible follow-up(s)>
- Re: [perfsonar-user] pScheduler and postgres, Mark Feit, 02/13/2017
- Re: [perfsonar-user] pScheduler and postgres, Andrew Lake, 02/13/2017
- Re: [perfsonar-user] pScheduler and postgres, Uhl, George D. (GSFC-423.0)[SGT INC], 02/14/2017
- Re: [perfsonar-user] pScheduler and postgres, Uhl, George D. (GSFC-423.0)[SGT INC], 02/14/2017
- Re: [perfsonar-user] pScheduler and postgres, Mark Feit, 02/14/2017
- Re: [perfsonar-user] pScheduler and postgres, Andrew Lake, 02/13/2017
Archive powered by MHonArc 2.6.19.