Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

`infrastructure` label and a corresponding subject-matter expert #17

Closed
AlexDaniel opened this issue Apr 24, 2019 · 6 comments

Comments

Projects
None yet
4 participants
@AlexDaniel
Copy link
Member

commented Apr 24, 2019

Looking at #9, it is clear that we need a new infrastructure label in this repository. However, it is unclear who would act as a subject-matter expert for that label.

If you want to volunteer, please leave a relatively short comment describing your expertise, the amount of effort/time you are ready to provide for resolving issues, and your initial plan as to what has to be changed.

For more info, see some docs here: https://github.com/perl6/infrastructure-doc/, as well as a discussion on #9.

@kawaii

This comment has been minimized.

Copy link
Member

commented Apr 25, 2019

A few points/things we should do:

  • move domain nameservers over to Cloudflare, they allow for shared-access to DNS records and other related configuration all on their free plan, @jnthn could be the primary account holder and grant others access as and when needed, we'd also benefit from their global CDN (related).
  • dockerize Rakudo website, Perl 6 website and Perl 6 docs site

Will add more to this thread as ideas come to me. I'm able to recommend hosting providers too that would be more cost effective for the project if needed.

@rba

This comment has been minimized.

Copy link
Collaborator

commented Apr 27, 2019

To start, I'm currently collecting information, about what is around, and what is it used for, and more important, what all broke.

Then we have to make sure to get the site back online. This happened mostly already, as there don't seem to be to much panic in IRC during the last few days. Yet it seems that past releases are only on the hard drive of the p2c server.

For the foreseeable future we need a plan how to go ahead. This should include documentation, automation, monitoring and (oh surprise) backup. Setup redundancy for the important services will be one of our core targets.

I'm a long term perl(5) programmer and started last century with it using CGI on AIX.
In my day-to-day job I work as contractor/freelancer for mostly for banks and the swiss government in the last few years. I manly do infrastructure and programming work. I'v started doing devops even before the term was formed. I have in deep knowledge of Linux in different flavors and have worked with Solaris, AIX and Windows and Mac too.
During the last two years I'm trying to bring a 20 year old perl5 written software to a modern style level. Doing CI/CD stuff using Jenkins and Puppet and support applications in area of Identity Management to gain production access (a product like sudo, but for remote access; allows > 1000 persons access > 10'000 hosts). I've recently participated in the POC with openshift/kubernetes. And I'm eager to go ahead .

For the perl6 community we (together with maettu) organised a hackathon on the Swiss Perl Workshop 2015 (remember, before xmas :-)).

I have some time currently, to get things done, and as the goal must be to get things automated. I expect that now, some effort is necessary, to get the sites back to online, and to do automation. For me, this is a longer term engagement, yet I think keeping the infrastructure alive, will not be a time consuming task.

As can see I have limited history of what happened in the infrastructure are in the past, and it would be really helpful if someone would give me some more information.

@AlexDaniel

This comment has been minimized.

Copy link
Member Author

commented Apr 27, 2019

@rba I'm pleased with that. Can you submit a PR with some changes to the README?

  • Basically, add an infrastructure label to the document and list yourself under it.

  • Then probably also add yourself to the list of reviewers.

  • After that there'd be 2 weeks when devs can object, and if everything goes right it'll be merged exactly after two weeks (or earlier if everyone approves ahead of time).

  • I've sent you an invite to perl6 organization which you can accept on https://github.com/perl6. However, that doesn't give you many privileges (most people have these anyway, it just happened that you didn't).

  • It'll also help if you sign a CLA (let us know if you have already done that in the past):

    https://www.perlfoundation.org/contributor-license-agreement print it out, sign it, scan it in (resize your scan to 250KB or less). Email to trademark -at- perlfoundation.org (please scan and email if you can, it's so much more efficient)

  • You will probably have to ask for access to specific things in the infrastructure yourself because I simply don't know what we have and where.

If somebody else wants to apply, you are still free to do so. If there's more than one candidate, current reviewers will vote.

@maettu

This comment has been minimized.

Copy link
Collaborator

commented Apr 28, 2019

Thanks @rba for summarizing what we discussed, yesterday.
I would like to add that it is probably important to know if there are any tools (automation / monitoring / deployment) that should be used, e.g. because they are written in Perl or because they are already in use by contributors.

I don't have tons of time in the coming months, but I am willing to put in some hours per week.

I am working for oetiker.ch, a Switzerland based IT consultancy. We do software projects and system management. Here is my page https://www.oetiker.ch/home/unternehmen/team/mb/.

@rba

This comment has been minimized.

Copy link
Collaborator

commented May 1, 2019

@AlexDaniel See the PR #23.
And I've sent the signded/scanned CLA to the perlfoundation as well.

@AlexDaniel

This comment has been minimized.

Copy link
Member Author

commented May 8, 2019

This was resolved in #23.

@AlexDaniel AlexDaniel closed this May 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.