[SAC] Vote request to extend Sysadmin Contract 2019-I amount for another $5000

[Alex M]

Yes, based on the vote we can move ahead with this. I checked and we
actually budgeted for 3 contracts this year, the 3rd was expected to
deal with the main website, not sure if optimization should go to that one.

Regina, want to use the previous contract as a template? Then we just
need to make the new list of tickets to cover under Contract II using
the list you already made as the starting point, we should suggest
additions and removals from that list.

Thanks,
Alex

On 6/13/19 09:51, Sandro Santilli wrote:
> Can we move this forward ?
> We really need more maintainance (I agree with "urgent response" planning). 
> Let's use some trust and not get stuck with this.
> 
> I'm +1 for next contract (2019-II, I'd call it) to Regina.
> 
> --strk;
> 
> On Thu, Jun 06, 2019 at 12:47:06PM -0700, Alex M wrote:
>> I'm +1, pending discussion of specific tickets to target - I don't think
>> all the ones listed are important enough to go on the contract. But that
>> we have other tasks which might be.
>>
>> Just a few notes:
>> * This will us up the rest of our 2019 contract budget, we can ask the
>> board for more if we feel it's necessary.
>> * I also think we should discuss if want to reserve a % of these hours
>> for "urgent response" tasks or if it should all be pre-determined tickets.
>>
>> Based on the vote we should move forward drawing up the exact contract
>> for signing.
>>
>> Thanks,
>> Alex
>>
>> On 5/30/19 09:50, Markus Neteler wrote:
>>> +1 & big thanks,
>>>
>>> Markus
>>>
>>> On Fri, May 24, 2019 at 12:15 AM Regina Obe <lr at pcorp.us> wrote:
>>>>
>>>> The Sysadmin Contract I  had a  Service completion date of September 30th, 2019 and capped at $5000.
>>>>
>>>> I have already reached the cap limit and am requesting an extension of budget, which I will submit formally if all are in agreement.
>>>>
>>>>
>>>>
>>>> What I’d like to accomplish in next round, which I hope to do in a new $5000 budget
>>>>
>>>> https://trac.osgeo.org/osgeo/query?status=new&status=reopened&milestone=Sysadmin+Contract+2019-I
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 1)      Once osgeo4 has got some new drives in it (plan is to replace with 6 new SATA drives and throw out all the drives (only 2 are still good)  and reformatted, firmware upgrade – set it up as a secondary LXD host to use for non-mission critical stuff (like adhoc, buildbots, etc) and also to mirror osgeo7 containers in stopped state for redundancy.
>>>>
>>>> 2)      Setup file and database backup for osgeo7 containers – which will get pushed to bacula
>>>>
>>>> 3)      Speed up website – with configuring caching of static content like css and images first and then database content  if that proves insufficient.
>>>>
>>>> 4)      Upgrade Nextcloud to latest version
>>>>
>>>> 5)      Create a new wiki with latest Debian, MariaDb and MediaWiki, PHP – right now our wiki everything is EOL’d – the OS, MySQL, and PHP
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> What  was accomplished in the first round is itemized here:
>>>>
>>>> https://trac.osgeo.org/osgeo/query?status=closed&milestone=Sysadmin+Contract+2019-I
>>>>
>>>>
>>>>
>>>> With key highlights being
>>>>
>>>>
>>>>
>>>> 1)      Create new ldap.osgeo.or g ( now on osgeo7) running debian 9
>>>>
>>>> 2)      Create new download.osgeo.org (on osgeo7) running debian 9 / nginx
>>>>
>>>> 3)      Install letsencrypt on all servers that need it replacing the SSL.com star cert that expired May 1st
>>>>
>>>> 4)      Migrate VMS projects, adhoc, web (still need to do some final checks) as is to LXD containers now on osgeo7
>>>>
>>>> 5)      Setup 30 day retention lxd image snapshots of key osgeo7 vms
>>>>
>>>> 6)      Upgrade LXD to snap 3.12 so always at the latest stable LXD offering
>>>>
>>>> 7)      Decommission osgeo4 so it’s ready to be reformatted/firmware upgraded (all old vms have either been rebuilt as new lxd containers or migrated as is using lxd-p2c tool to osgeo7)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Regina