I like the addon approach. To set up a amazon web services account you need a credit card for the account. You then can set up user with just the privileges that are needed. That way the user's privileges can be revoked at any time and you don't expose any more access to the account than needed. With AWS this is all very easy. We should be able to also set up monitoring (at least I think we can) for these services so that if someone uses them outside of the project team and sends volumes of transactions through the service at least you will be notified. I will look into that.
Whoever tests the appenders will need to load the AWS SDK for php. They support pear and composer for that. Currently the 1.5x SDK has an api for SNS, SQS and Smimple DB. The new SDK 2.0 is not full featured yet but when it starts to support there 3 services I will extend the appenders for that very. The 2.0 version is much better for error handling and detection but the world is using just the 1.5 version for the most part now. Eric Palmer Director of Web Services University of Richmond ________________________________________ From: Christian Grobmeier [[email protected]] Sent: Sunday, January 06, 2013 1:46 PM To: Log4PHP Dev Subject: Re: Interest in Appenders for Amazon Cloud Services? On Sat, Jan 5, 2013 at 11:17 AM, Palmer, Eric <[email protected]> wrote: > You would have to have an account with a que name, db name and topic name to > test it. In reality these are ARN like URLs. The cost is minimal. You can > send like 100,000 SQS messages for pennies. > > But there is no easy way to fake it. Good to know. In my opinon we (the log4php project) should ask if we have such a testing account in cooperation with Amazon (infra should know). If there is not such a chance, we might be able to set up an log4php account. The problem is that the project members need to able to access that account. Therefore it is most likely not possible to use f.e. my personal account. We must look into setting up a "log4php" account. I think the few bucks is not the problem; its more the "process". That said, we maybe should think if we should create some "add-on" package. I think it will take a while until we get CI running for the new appenders. Until we manage that, we should not include them into the main repository but in an "add on" repository, which needs to be created. It would give us the chance to put some other appenders to "add ons" like mongodb appender. That one is not so easy ot test too. Ivan, what is your take on that (others please comment too :-))? Cheers Christian > I know this makes the testing hard to do. I could use one of my accounts for > that but we could not let the acount ARN URLs into the wild for security and > cost reasons. > > Eric Palmer > Director of Web Services > University of Richmond > ________________________________________ > From: Ivan Habunek [[email protected]] > Sent: Saturday, January 05, 2013 3:39 AM > To: Log4PHP Dev > Subject: Re: Interest in Appenders for Amazon Cloud Services? > > Hi Eric, > > Glad to have you on board! > > I'm currently in the process of writing some git guidelines. We > migrated from SVN just very recently. Hope to have that finished soon, > so you'll have some reference. > > Regarding unit tests, what would be the requirements for running some > tests which actually log to SQS/simple db/SNS? Is it possible to > either have some local "fake" service or have a free instance which > can be used for testing? > > Regards, > Ivan > > > On 5 January 2013 01:40, Palmer, Eric <[email protected]> wrote: >> Christian, >> >> Thanks for the fast response. >> >> ICLA - I need to get my boss (CIO) and the University Attorney to approve. I >> don't see problems other than getting the Attorney's time. She is very busy. >> I can work on the code locally in the meantime. >> >> 1) coding sytle - yes can follow what you have established >> 2) license - yes apache 2 which is my preferred license anyway >> 3) git - pretty new to it as well but have maybe 10 local projects in git at >> work and am starting to understand it. As long as everyone can be patient >> with me on that front. >> 4) php unit test cases - sure no problem >> 5) documentation no problem >> 6) ASF - I am very familiar with ASF - I use lucense, httpd, many java >> libraries and am getting ready to use apache camel and activemq >> >> I will work on the sqs appender first as that is my immediate need anyway. >> I will make sure it works with AWS SFK 1.5x and 2.0X (which are very >> different). Once the code is accepted in released then I can prompt it with >> AWS forums and with our amazon representative. >> >> I suspect that doing the SNS (Simple Notification Services - like email and >> text messages but AWS encapsulated) will be very easy and Simple DB will >> follow after that. >> >> I will post back here when I get ICLA approval. >> >> Thanks again for the details and fast response. >> >> Eric Palmer >> Director of Web Services >> University of Richmond >> ________________________________________ >> From: Christian Grobmeier [[email protected]] >> Sent: Friday, January 04, 2013 6:19 PM >> To: Log4PHP Dev >> Subject: Re: Interest in Appenders for Amazon Cloud Services? >> >> Hello Eric, >> >> I would love to see such cool appenders in log4php. >> >> In log4php we usually accept donations like that when we have your >> ICLA on file (smaller patches are accepted without). >> Its here: http://www.apache.org/licenses/icla.txt >> >> Basically the ICLA tells us we can really take your code, because you >> are allowed to give it to us. I am not a lawyer of course, but if you >> have questions around it I will try to answer. Please don't be afraid >> before it. >> >> Once we have it, it is the easy way to get an contribution in when it >> is already having the Apache License 2.0. If it is GPL code we cannot >> accept it unfortunately until you have relicensed it. If it is >> something else we would need to dig a little deeper. Really the >> easiest way is: AL 2.0. Again, if I can help you with that, just >> shout. >> >> Then finally we'll gladly look at your code and hopefully accept it! :-) >> >> Usually we hope that contributors send phpunit tests along and >> document the code a little bit. In best case the contributor is >> sticking with the project, helping to maintain a little bit (and >> hopefully become a full-fledged committer one day). It would be good >> if you could use the coding style we have used for the rest of >> log4php. >> >> log4php uses GIT meanwhile (not only the mirror) so you should somehow >> be able to fork it to github, do modifications and send back a patch >> to us. We are all pretty new with GIT and this will be a good chance >> to check out how it all would work. >> >> Here is link on "how the asf works": >> http://apache.org/foundation/how-it-works.html >> >> That said: thank you for using log4php and for working on appenders. I >> am really looking forward to them. >> >> Cheers >> Christian >> >> >> >> >> >> On Fri, Jan 4, 2013 at 11:20 PM, Palmer, Eric <[email protected]> wrote: >>> Hello all, this is my first email to the list. >>> >>> I mostly code in Java but do some php. I got log4php from pear today and >>> like it a lot. I have a need for appenders for amazon web services SQS >>> (simple que service) and simple db. Maybe as well their notification >>> service (SNS). I have written an appender today for SQS that works but needs >>> some additional work to be ready for project submission. >>> >>> Is there interest in a submission for a AWS SQS appender and maybe other AWS >>> appenders? >>> >>> I also noticed that the git repo may be a mirror so how would I submit a >>> suggested addition. Of course the autoloader needs the class name entry as >>> well. >>> >>> Let me know if there is interest. >>> >>> Thanks for log4php >>> >>> Eric Palmer >>> Web Services >>> U of Richmond >>> Richmond, VA >>> >>> >> >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de
