Proposal GSIP-176 ready for review.
···
–
Jody Garnett
With no feedback incoming, I would like to ask the PSC to vote on this proposal.
···
–
Jody Garnett
Hi Jody,
I don’t think it’s possible to vote right now as the proposal lack clarity and focus.
The page does not include what kind of approach should be used to automate the tests
and links to some approaches that are years old, having no reality check against what
the CITE engine does and how it works today.
At one point we talked about using the Team Engine REST interface for example,
but it’s still missing for a number of protocols, see the last comments in these issues:
https://github.com/opengeospatial/teamengine-docker/issues/11
I guess the bidder can propose a plan, but in this case, do we want to setup some
requirements? Is it OK to run only against official releases, waiting for whatever
time it takes to get them fixed in case they are buggy, or working around their eventual
limitations?
Or do we want to also setup our forks of the test suites? (more manageable, but
we won’t get certification that way).
It’s also not clear what relationship should be setup with Planet, if someone that’s not
Planet wants to bid, what is the context? Planet is going to offer a set amount of time
to help with setting up things in their locked down node execution environment?
(no one but Planet employees can access the worker nodes and the build server
outside of the Jenkins admin GUI).
Or should the company/individual try to setup a sub-contract with Planet?
Cheers
Andrea
···
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Okay I have revised the page based on your feedback, with a section for applications, requirements and discussion.
···
–
Jody Garnett
Some comments on the Planet portion:
It’s also not clear what relationship should be setup with Planet, if someone that’s not
Planet wants to bid, what is the context? Planet is going to offer a set amount of time
to help with setting up things in their locked down node execution environment?
(no one but Planet employees can access the worker nodes and the build server
outside of the Jenkins admin GUI).
Or should the company/individual try to setup a sub-contract with Planet?
It may be possible to make the master node accessible to PSC/Whomever ends up setting up the CITE tests - I will see if I can get a solid yes/no answer and report back. (And as an aside, I don’t even have access to the worker nodes, just the startup script that creates them).
An optimal solution would be to determine a reproducible set of steps to create an environment the CITE tests can run in, and then apply that in Jenkins - this would make future debugging / updates a lot easier (that might be something worthwhile to add to the proposal, although the delivery requirements mostly cover it).
The proposal itself looks good to me.
Torben
Follow-up:
On Tue, Jul 16, 2019 at 2:49 PM Torben Barsballe <tbarsballe@anonymised.com> wrote:
Some comments on the Planet portion:
It’s also not clear what relationship should be setup with Planet, if someone that’s not
Planet wants to bid, what is the context? Planet is going to offer a set amount of time
to help with setting up things in their locked down node execution environment?
(no one but Planet employees can access the worker nodes and the build server
outside of the Jenkins admin GUI).
Or should the company/individual try to setup a sub-contract with Planet?It may be possible to make the master node accessible to PSC/Whomever ends up setting up the CITE tests - I will see if I can get a solid yes/no answer and report back. (And as an aside, I don’t even have access to the worker nodes, just the startup script that creates them).
We (Planet) can provide the exact configuration used to create the worker nodes (OS + startup script; there’s not a whole lot that goes into them - its Ubuntu 18 and a 10-line bash script). The implementor could use that to set up a dev environment while developing the CITE test configuration. Once something is working, we (Planet) can apply any required changes to the AWS configuration. Does that sound like a workable solution?
Torben
Sounds good, still would like a private repo to store Jenkins configuration (including that 10-lin bash script).
Thanks for the response Torben, do you need to modify the note I put in there about deliverable requirements?
···
–
Jody Garnett
I would also love to have a private repo for Jenkins config, I’ve been collecting a whole lot of it.
I could add a requirement line along the lines of
“Delivery is required to include the system prerequisites and environment setup in the form of a bash script executable on Ubuntu 18”
Does that wording sound alright?
Torben
On Tue, Jul 16, 2019 at 9:32 PM Jody Garnett <jody.garnett@anonymised.com> wrote:
Sounds good, still would like a private repo to store Jenkins configuration (including that 10-lin bash script).
Thanks for the response Torben, do you need to modify the note I put in there about deliverable requirements?
–
Jody GarnettOn Tue, 16 Jul 2019 at 16:12, Torben Barsballe <tbarsballe@anonymised.com> wrote:
Follow-up:
On Tue, Jul 16, 2019 at 2:49 PM Torben Barsballe <tbarsballe@anonymised.com> wrote:
Some comments on the Planet portion:
It’s also not clear what relationship should be setup with Planet, if someone that’s not
Planet wants to bid, what is the context? Planet is going to offer a set amount of time
to help with setting up things in their locked down node execution environment?
(no one but Planet employees can access the worker nodes and the build server
outside of the Jenkins admin GUI).
Or should the company/individual try to setup a sub-contract with Planet?It may be possible to make the master node accessible to PSC/Whomever ends up setting up the CITE tests - I will see if I can get a solid yes/no answer and report back. (And as an aside, I don’t even have access to the worker nodes, just the startup script that creates them).
We (Planet) can provide the exact configuration used to create the worker nodes (OS + startup script; there’s not a whole lot that goes into them - its Ubuntu 18 and a 10-line bash script). The implementor could use that to set up a dev environment while developing the CITE test configuration. Once something is working, we (Planet) can apply any required changes to the AWS configuration. Does that sound like a workable solution?
Torben
That line sounds fine, please capitalize REQUIRED, to match the rest 
I had a couple more inquires about supporting this activity offline, and have worked with the osgeo treasurer to add:
- GSIP-176 now has cut and paste email to send to the treasurer, a paypal donate button specifically donating to the GeoServer project
- Sponsor has the same information (in case we want to reuse the instructions later)
···
–
Jody Garnett
Hi Jody,
thanks, that looks much better.
I’d add a clarification, that the setup of the tests should allow them to run,
but does not require them to pass.
Now, it should be evident in that you are setting up a second phase, code sprint, to make the tests pass,
however, it’s just there at the beginning and might be easily lost while reading the rest of the document.
So, I’d be clear about it while enumerating the requirements for the RFP.
Cheers
Andrea
···
Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
I have added this requirement.
If the proposal is now acceptable please vote
···
–
Jody Garnett
I have updated the proposal to make it very clear that the tests are not expected to run (in both the requirements and clarification section).
If the proposal is now acceptable to you please vote!
···
–
Jody Garnett
Brad you asked online about the 10k budget limit, I have changed it to a range between 10k and 20k, and updated the section on sponsoring.
If the proposal is now acceptable to you please vote
···
–
Jody Garnett