from:"David Shier"

Re: fedora-infrastructure#7267: "fedora-packager and statscache sunset" patch review.

2018-10-02 Thread David Shier

The git tagger references were not, in fact, missed. I saw those, and 
decided to ask about them as they did n't look related to me. Nirik 
indicated they were something else and needed to reamain, so I left 
them.


Am Di, 2. Okt, 2018 um 10:15 A. M. schrieb Mikolaj Izdebski 
:

On 10/02/2018 02:22 AM, David Shier wrote:

 All/sysadmin-main -

 Could someone please review the attached patch file for the removal 
of
 tagger and statscache from the ansible repos/proxy lists/ etc.? I 
was
 going to attach to issue, but pagure is only letting me do 
pictures, and

 this one is large and gnarly as a picture.


1. Commit subject is way too long and not well formed. There are many
guidelines on writing commit messages, eg. [1]
2. Ideally there should be one service removed per commit, not both 
in a

single commit
3. You missed multiple references to tagger, see "git grep tagger"

[1] https://chris.beams.io/posts/git-commit/



 Thanks,

 Dave Shier/odin



 ___
 infrastructure mailing list -- 
infrastructure@lists.fedoraproject.org
 To unsubscribe send an email to 
infrastructure-le...@lists.fedoraproject.org

 Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
 List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
 List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org




--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to 
infrastructure-le...@lists.fedoraproject.org

Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

fedora-infrastructure#7267: "fedora-packager and statscache sunset" patch review.

2018-10-01 Thread David Shier


All/sysadmin-main -

Could someone please review the attached patch file for the removal of 
tagger and statscache from the ansible repos/proxy lists/ etc.? I was 
going to attach to issue, but pagure is only letting me do pictures, 
and this one is large and gnarly as a picture.


Thanks,

Dave Shier/odin
>From 3d1f36130a77fc5230d7c9089d9e4b1afa9e8ffe Mon Sep 17 00:00:00 2001
From: David Shier 
Date: Tue, 2 Oct 2018 02:01:03 +0200
Subject: [PATCH] Removed all traces i could fild of the tagger and statscache
 (and stats_cache for databases) in ansible, proxy configs, and the nagios
 config. Pursuant to request in pagzre issue
 https://pagure.io/fedora-infrastructure/issue/7267 . - Odin2016

---
 inventory/group_vars/statscache-backend   |  16 ---
 inventory/group_vars/statscache-backend-stg   |  13 --
 inventory/group_vars/statscache-web   |  12 --
 inventory/group_vars/statscache-web-stg   |  12 --
 inventory/group_vars/tagger   |  36 -
 inventory/group_vars/tagger-stg   |  36 -
 .../host_vars/db01.phx2.fedoraproject.org |   4 -
 ...tatscache-backend01.phx2.fedoraproject.org |  14 --
 ...cache-backend01.stg.phx2.fedoraproject.org |  14 --
 .../statscache-web01.phx2.fedoraproject.org   |  14 --
 ...tatscache-web01.stg.phx2.fedoraproject.org |  14 --
 .../statscache-web02.phx2.fedoraproject.org   |  14 --
 ...tatscache-web02.stg.phx2.fedoraproject.org |  14 --
 .../host_vars/tagger01.phx2.fedoraproject.org |  14 --
 .../tagger01.stg.phx2.fedoraproject.org   |  14 --
 .../host_vars/tagger02.phx2.fedoraproject.org |  14 --
 inventory/inventory   |  35 -
 master.yml|   2 -
 playbooks/fedmsgupdate.yml|   1 -
 playbooks/groups/statscache.yml   |  66 --
 playbooks/groups/tagger.yml   |  70 --
 playbooks/include/proxies-reverseproxy.yml|  15 ---
 playbooks/manual/rebuild/fedora-packages.yml  |   4 +-
 playbooks/manual/upgrade/statscache.yml   | 100 --
 playbooks/manual/upgrade/tagger.yml   |  57 
 roles/apps-fp-o/files/apps.yaml   |  15 ---
 roles/base/templates/syncHttpLogs.sh.j2   |  19 ---
 roles/haproxy/templates/haproxy.cfg   |  22 
 ...backend01.stg.phx2.fedoraproject.org-hosts |  11 --
 .../tagger01.phx2.fedoraproject.org-hosts |   7 -
 .../tagger02.phx2.fedoraproject.org-hosts |   7 -
 roles/ipsilon/templates/configuration.conf|   2 +-
 .../templates/nagios/services/websites.cfg.j2 |   8 --
 .../notifs/backend/templates/fmn.consumer.py  |   1 -
 .../statscache-web01.phx2.fedoraproject.org   |   2 -
 .../statscache-web02.phx2.fedoraproject.org   |   2 -
 .../files/ccd/tagger01.phx2.fedoraproject.org |   2 -
 .../files/ccd/tagger02.phx2.fedoraproject.org |   2 -
 roles/packages3/web/tasks/main.yml|   2 +-
 .../web/templates/packages-app.ini.j2 |   3 -
 roles/statscache/backend/tasks/main.yml   |  43 --
 .../statscache/backend/templates/alembic.ini  |  53 
 .../backend/templates/statscache.py   |  55 
 .../statscache/frontend/files/statscache.wsgi |   8 --
 roles/statscache/frontend/tasks/main.yml  |  75 ---
 .../frontend/templates/statscache.cfg |   2 -
 .../frontend/templates/statscache.conf|  18 ---
 .../frontend/templates/statscache.py  |  37 --
 roles/tagger/files/cron-tagger-remove-retired |   2 -
 roles/tagger/files/cron-tagger-update-db  |   2 -
 roles/tagger/tasks/main.yml   | 123 --
 roles/tagger/templates/alembic.ini|  53 
 roles/tagger/templates/fedoratagger-app.conf  |  48 ---
 roles/tagger/templates/fedoratagger.cfg.j2|  30 -
 roles/varnish/templates/proxies.vcl.j2|  12 --
 55 files changed, 4 insertions(+), 1267 deletions(-)
 delete mode 100644 inventory/group_vars/statscache-backend
 delete mode 100644 inventory/group_vars/statscache-backend-stg
 delete mode 100644 inventory/group_vars/statscache-web
 delete mode 100644 inventory/group_vars/statscache-web-stg
 delete mode 100644 inventory/group_vars/tagger
 delete mode 100644 inventory/group_vars/tagger-stg
 delete mode 100644 inventory/host_vars/statscache-backend01.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/statscache-backend01.stg.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/statscache-web01.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/statscache-web01.stg.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/statscache-web02.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/statscache-web02.stg.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/tagger01.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/tagger01.stg.phx2.fedoraproject.org
 delete mode 100644 inventory/host_vars/tagger02.phx2.fedoraproject.

Re: The trouble with torrents

2018-09-29 Thread David Shier

So, I was reading the other day that aria2 also has control over 
xmlrpc, and a web ui (iirc it is no packaged with aria, but another bit 
o the project.). So that could be an option as well. aria is my go 
to when I torrent, and has always seemed solid.


Am So, 30. Sep, 2018 um 1:27 A. M. schrieb Mikolaj Izdebski 
:

On 09/29/2018 01:24 AM, Kevin Fenzi wrote:

 On 09/26/2018 10:59 PM, Pablo Iranzo Gómez wrote:

 Hi Kevin,

 What about using transmission-daemon which is available in Fedora?

 (also console with optional Web UI)


 Yeah, we looked at it the last time, but it there were issues...

 I think the daemon version still pulled in the entire gtk stack or 
you

 couldn't
 manage it via config files. Looks like it might be better now...


I've been successfully using transmission-daemon since January. It can
definitely be managed via config files, but it expects to own config
files - it overwrites them when the process terminates. This can be
worked around easily, eg. by updating config files when the deamon is
not running:

- name: Create transmission config directory
  file: dest=/var/lib/transmission/.config/transmission-daemon/
state=directory owner=transmission group=transmission

- name: Copy transmission config file
  template: src=settings.json.j2
dest=/var/lib/transmission/.config/transmission-daemon/settings.json
  register: settings_j2

- name: Stop transmission-daemon
  service: name=transmission-daemon state=stopped
  when: settings_j2.changed

- name: Copy transmission config file again
  template: src=settings.json.j2
dest=/var/lib/transmission/.config/transmission-daemon/settings.json
  when: settings_j2.changed

- name: Start and enable transmission-daemon
  service: name=transmission-daemon state=started enabled=true

--
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to 
infrastructure-le...@lists.fedoraproject.org

Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: 
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Meeting Agenda Item: Introduction David Shier

2018-09-27 Thread David Shier


Just gonna resend this with all the variables plugged.


Hello all,

My name is David Shier and I am coming back to fedora admin after a 
year or two away. My iRC nick is odin2016. Up until about a month and 
a half ago, I worked for Jackson in the US as a number of things, but 
most relevant to this is my last two positions, as an admin on their 
UNIX team, supported our RHEL (5,6,7) and AIX estates, and working in 
on the more or less server operations team as a senior associate with 
root access to the production environment. I am familiar with bash, 
python, and perl, as well as Ansible, which I used at work and at 
home.  I'd like to improve my Ansible and python skills, as well as 
just keeping my self sharp while I search for a job after my recent 
move to Germany. As would be expected I am a linux user at home, 
having used redhat/centos, Debian/ubuntu, and Archlinux, as well as a 
number of forks of each, Fedora included, but I am also a distro 
hopper and am currently messing around with elementary on my laptop, 
and once the rest of my stuff gets here... whenever that is i'll 
be reimaging the raspberry pi and tossing awx on there. At my last 
job I worked a good bit with RHDS, and passing data into it from 
Active Directory, as I have experience on both sides of that fence as 
well. I'm sure there things here I could say, and probably should, 
but i've also blocked out large bits of the last year or so, so there 
is that.


There are a number of tickets that I would *like * to work on, but 
before i get to deep into that I need to go and read up on how 
thiings int eh infra have changed since I last took a look, clone the 
ansible repo and read though there, and so on. I also think I saw 
something about updating somethings to python 3, or making sure they 
will work. I may take a look at those as well.  I thought I saw 
something about the bots as well, but now I don't so may be I am 
crazy. I have worked with them before, so if I see it I may just grab 
it.


I should be at the meeting Thursday (I have a thing at 17:00 CEST), 
unless I did the math on time offset really wrong or something, and 
will get myself added to the goby doc in the next little bit here.


If someone could pop me back into fi-apprentice, that would be 
great.. fas is odin2016 as well.


Thanks,

Dave Shier





___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Meeting Agenda Item: Introduction Your Name

2018-09-25 Thread David Shier


Hello all,

My name is David Shier and I am coming back to fedora admin after a 
year or two away. My iRC nick is odin2016. Up until about a month and a 
half ago, I worked for Jackson in the US as a number of things, but 
most relevant to this is my last two positions, as an admin on their 
UNIX team, supported our RHEL (5,6,7) and AIX estates, and working in 
on the more or less server operations team as a senior associate with 
root access to the production environment. I am familiar with bash, 
python, and perl, as well as Ansible, which I used at work and at home. 
I'd like to improve my Ansible and python skills, as well as just 
keeping my self sharp while I search for a job after my recent move to 
Germany. As would be expected I am a linux user at home, having used 
redhat/centos, Debian/ubuntu, and Archlinux, as well as a number of 
forks of each, Fedora included, but I am also a distro hopper and am 
currently messing around with elementary on my laptop, and once the 
rest of my stuff gets here... whenever that is i'll be reimaging 
the raspberry pi and tossing awx on there. At my last job I worked a 
good bit with RHDS, and passing data into it from Active Directory, as 
I have experience on both sides of that fence as well. I'm sure there 
things here I could say, and probably should, but i've also blocked out 
large bits of the last year or so, so there is that.


There are a number of tickets that I would *like * to work on, but 
before i get to deep into that I need to go and read up on how thiings 
int eh infra have changed since I last took a look, clone the ansible 
repo and read though there, and so on. I also think I saw something 
about updating somethings to python 3, or making sure they will work. I 
may take a look at those as well.  I thought I saw something about the 
bots as well, but now I don't so may be I am crazy. I have worked with 
them before, so if I see it I may just grab it.


I should be at the meeting Thursday (I have a thing at 17:00 CEST), 
unless I did the math on time offset really wrong or something, and 
will get myself added to the goby doc in the next little bit here.


If someone could pop me back into fi-apprentice, that would be great.. 
fas is odin2016 as well.


Thanks,

Dave Shier


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org

Re: Moving meeting time?

2018-04-20 Thread David Shier

Crap, none of those work really well for me. But that is my Thursdays with
my current situation. If I get lucky I will pop in to some.

On Thu, Apr 19, 2018 at 3:24 PM, Kevin Fenzi <ke...@scrye.com> wrote:

> On 04/19/2018 05:32 AM, Pierre-Yves Chibon wrote:
> > On Wed, Apr 18, 2018 at 02:31:31PM -0700, Kevin Fenzi wrote:
> >> Greetings.
> >>
> >> It was noted recently that our current meeting time (thursdays at 18UTC)
> >> is a bit late/poorly timed for several of our European colleagues.
> >>
> >> Additionally, we sometimes have the go/no-go meeting at the same time
> >> which can be inconvenient.
> >>
> >> What would everyone think of moving the meeting to 16UTC?
> >> Or is there a better time for anyone?
> >
> > To be truthful, I think 14UTC would be best for me, it would basically
> allow me
> > to attend the meeting before the end of my working hours and without
> impact on
> > the family time.
> > But that does move the meeting up into your family time, so not ideal
> there :(
>
> Yeah, thats 7am for me... I can do it, but I can't promise I will be
> awake. ;)
>
> Anyhow, we decided in the meeting today to do a poll.
>
> Please vote for the time (In UTC) that you like best:
>
> https://framadate.org/VnfFPCae5wRKZuc3
>
> Thanks!
>
> kevin
>
>
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave@lists.
> fedoraproject.org
>
>


-- 
David Shier

"Mann muss dass Leben eben nehmen, wie das Leben eben ist."
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: June status update for Fedora Infrastructure Apprentices

2017-06-05 Thread David Shier

Responses in line.

On Thu, 2017-06-01 at 17:55 -0600, Kevin Fenzi wrote:
> You are getting this email because you are in the 'fi-apprentice'
> group
> in the fedora account system (or are reading this on the
> infrastructure
> list).
> 
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on.
> 
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
> 
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going
> for
> you. I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help
> us
> make the apprentice program more useful.
> 
> 0. Whats your fedora account system login?

odin2016

> 1. Have you logged in and used your fi-apprentice membership to look
> at
> our machines/setup in the last month? Do you plan to?

Not in the last months... trying to get back to it.

> 2. Has it helped you decide any area you wish to focus on or
> contribute
> to more?

Nope. Funny how lack of time and focus does that. :(

> 3. Have you looked at or been able to work on any of the fi-
> apprentice
> 'easyfix' tickets?
> https://pagure.io/fedora-infrastructure/issues?status=Open=easyf
> ix

Negative.

> 4. Do you still wish to be a member of the group? If not (for
> whatever
> reason) could you provide any hints to help others down the road?

Yes, please.

> 5. Is there any help or communication or ideas you have that would
> help
> you do any of the above?

Nope, I think on the whole we have it covered, as I always have.

> 6. What do you find to be the hardest part of getting involved?
> Finding
> things to work on? Getting attention from others to help you? Finding
> tickets in your interest area?

Time/ Focus, per number 2.
> 
> 7. Have you been able to make any weekly irc meetings? Do you find
> them
> helpful or interesting? Do you have any suggestions for changing
> them?

I was in one recently.. puiterwick ran it... (sorry for killing the
spelling, sir).

> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby

Not recently, no.

> 9. Whats your favorite thing to smell?

Coffee!

> Any other general feedback is also quite welcome, including
> improvements
> to this email, the wiki page, etc. Note that we recently revamped the
> getting started and other pages. Please do take a minute to re-read
> them
> and let me know if they are more clear or need further adjustments.
> 
> Any folks I do not hear from in the next week will be removed from
> the
> group. (Note that it's easy to be readded when you have time or
> whatever
> and it's nothing at all personal, we just want to keep the group up
> to
> date with active folks).
> 
> Thanks, and looking forward to your feedback!
> 
> kevin
> 
> 
> 
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-leave@lists.fedoraproj
> ect.org
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

2017-02-06 Thread David Shier


Responses  in line.



在 2017年2月2日，00:24，Kevin Fenzi  写道：

You are getting this email because you are in the 'fi-apprentice' 
group

in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going 
for

you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help 
us

make the apprentice program more useful.

0. Whats your fedora account system login?

odin2016


1. Have you logged in and used your fi-apprentice membership to look 
at

our machines/setup in the last month? Do you plan to?
No, but I am hoping to do so either this month or next, as I'm going to 
have significantly more down time now that I have gone back to  the 
team I used to be on, working 3 12's.


2. Has it helped you decide any area you wish to focus on or 
contribute

to more?

N/A at this stage.


3. Have you looked at or been able to work on any of the 
fi-apprentice

'easyfix' tickets?
https://pagure.io/fedora-infrastructure/issues?status=Open=easyfix
Nope,  just thinking about coming back. It's likely I will shortly 
though.


4. Do you still wish to be a member of the group? If not (for 
whatever

reason) could you provide any hints to help others down the road?

Yes.


5. Is there any help or communication or ideas you have that would 
help

you do any of the above?

N/A


6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?

Historically it's been time, but I hope that is a non issue now.


7. Have you been able to make any weekly irc meetings? Do you find 
them

helpful or interesting?

Not recently, but they are almost always interesting.


8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

Not recently.


9. What's the best software documentation you have read?
Outside the docs I write for people on the team I am going back to 
(written so my five year old could execute given the access, things 
like extending a vg and then filesystem after passing an LV from a vg 
on a hypervisor) probably the Ansible docs over at docs.ansible.com . 
For what it is worth, some of worst, if not the worst, is the purescale 
and GPFS docs out of IBM...


Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Note that we recently revamped the getting started and other pages.
Please do take a minute to re-read them and let me know if they are
more clear or need further adjustments.

Any folks I do not hear from in the next week will be removed from 
the

group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!

kevin
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to 
infrastructure-le...@lists.fedoraproject.org


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: October status update for Fedora Infrastructure Apprentices

2016-10-06 Thread David Shier


Answers in line.


On 10/01/2016 04:50 PM, Kevin Fenzi wrote:

You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.

0. Whats your fedora account system login?

odin2016

1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
No. The work I have done not required me to get on any of the boxes 
directly.

2. Has it helped you decide any area you wish to focus on or contribute
to more?
Not so much, but I am easig back in... or more accurately, easing tha 
family back in to me doing this.

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://pagure.io/fedora-infrastructure/issues?status=Open=easyfix
Yeah, I've looked at the tickets in the pretty new pagure interface. 
Didn't help that I was on and working on one whilst nirik was migrating us.

4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

Yes, please.

5. Is there any help or communication or ideas you have that would help
you do any of the above?

Not at this moment.

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
Lately,not being exhausted after I get done with day job. Everything 
else is there.

7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

Not recently. Maybe next week.

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

Not recently, but I have in the past.

9. Whats your favorite Halloween food?
https://en.wikipedia.org/wiki/Halloween#Food

My kids candy but seriously, I just like the Halloween themed wrappers.

Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.

Nothing yet, sir.


Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!

kevin


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org


___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: September status update for Fedora Infrastructure Apprentices

2016-09-09 Thread David Shier


Reply's in line.

On 09/07/2016 04:15 PM, Bryan Teague wrote:

Hi Kevin -

0. Whats your fedora account system login?

odin2016


1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
No, For that matter, this is the first time i've opened a traditional 
computer outside of work in a month.


2. Has it helped you decide any area you wish to focus on or contribute
to more?

NA


3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14

No, but probably tomorrow.


4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

Yes.


5. Is there any help or communication or ideas you have that would help
you do any of the above?
Nope, unless you have pointers on getting non RedHat vendors to stop 
lying to you about what their code does. ;)


6. What do you find to be the hardest part of getting involved?

Not being constanty mentally exhuasted by $dayjob


7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
I think I made one this month, I've had a meeting around that time most 
recent weeks, and people are not so conducive to me staring at my phone 
in a meeting.


8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

Not recently. But I have before.



9. What is the furthest place you have ever traveled from your home?

Italy. When I was visiting cousins in Germany 10 years back, we went to 
Lake Como, Milan and Venice for a week.


On Tue, Sep 6, 2016 at 9:48 AM, Kevin Fenzi  wrote:

You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.

0. Whats your fedora account system login?

1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?

2. Has it helped you decide any area you wish to focus on or contribute
to more?

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14

4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

5. Is there any help or communication or ideas you have that would help
you do any of the above?

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?

7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

9. What is the furthest place you have ever traveled from your home?

Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.

Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!

kevin

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Aug status update for Fedora Infrastructure Apprentices

2016-08-12 Thread David Shier


Answers inline.

Dave

On 08/08/2016 09:28 PM, Tammy Miller wrote:



Date: Sun, 7 Aug 2016 09:01:55 -0600
From: ke...@scrye.com
To: fi-apprentice-memb...@fedoraproject.org; 
infrastructure@lists.fedoraproject.org

Subject: Aug status update for Fedora Infrastructure Apprentices

  
You are getting this email because you are in the 'fi-apprentice' group

in the fedora account system (or are reading this on the
infrastructure list).
  
Feel free to reply just directly to me, or cc the infrastructure list

for everyone to see and comment on.
  
https://fedoraproject.org/wiki/Infrastructure_Apprentice
  
At the first of every month(or so), I am going to be sending out an

email like this one. I would like feedback on how things are going for
you.
  
I'd like to ask for everyone to send me a quick reply with the

following data or anything related you can think of that might help us
make the apprentice program more useful.
  
0. Whats your fedora account system login?


odin2016
  
1. Have you logged in and used your fi-apprentice membership to look at

our machines/setup in the last month? Do you plan to?


Not recently.. but I  plan on on poking around more this month.


2. Has it helped you decide any area you wish to focus on or contribute
to more?


No, since i've been scare.

  
3. Have you looked at or been able to work on any of the fi-apprentice

'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14


No.

  
4. Do you still wish to be a member of the group? If not (for whatever

reason) could you provide any hints to help others down the road?

Yes.
  
5. Is there any help or communication or ideas you have that would help

you do any of the above?

Not at this time.

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?


Getting sapped by the day job.
  
7. Have you been able to make any weekly irc meetings? Do you find them

helpful or interesting?
  


I was at the one this week. Need to re-read the fas/ IPA discussion. Had 
to start pushing things into satellite.

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda?https://fedoraproject.org/wiki/Gobby


Not recently, no.
  
9. when was the last plane trip you took?



9 years ago.

Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
  
Any folks I do not hear from in the next week will be removed from the

group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
  
Thanks, and looking forward to your feedback!
  
kevin


___ infrastructure mailing 
list infrastructure@lists.fedoraproject.org 
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: June status update for Fedora Infrastructure Apprentices

2016-07-03 Thread David Shier


Responses in line.


On 07/02/2016 01:01 PM, Kevin Fenzi wrote:

You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.

0. Whats your fedora account system login?

odin2016

1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?

Not this month. Hopefully again soon (r)

2. Has it helped you decide any area you wish to focus on or contribute
to more?

See #1.

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14

Not this month.

4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

Yes.

5. Is there any help or communication or ideas you have that would help
you do any of the above?

None.

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?

Lately, time. I blame $dayjob.

7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

One or two.

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

Not recently, but I have in the past.

9. When was the last time it rained where you are?
I guess that depends what you call  rain. It spat a little bit a couple 
nights ago, but real rain, probably about three weeks ago or so. The 
upside here is I have not had a need to mow my lawn

Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.

Nope.

Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!

kevin


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: June status update for Fedora Infrastructure Apprentices

2016-06-01 Thread David Shier

Answers in line.


On 06/01/2016 01:32 PM, Kevin Fenzi wrote:
> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list). 
>
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on. 
>
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
>
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> you.
>
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
>
> 0. Whats your fedora account system login?
odin2016
> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
Not in the last month or so. $dayjob and reimaging things at home have
kept me busy, but I hope to get back at it soon.
> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
n/a
> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14
I've looked once or twice, just not had a ton of extra time lately. See #1.
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
yes.
> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
Nothing at the moment.
> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
> Finding tickets in your interest area? 
>
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting? 
Lately it's been time. See #1. Hoping that changes soon.
> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
Not recently, but soon. I was actually lurking at the last meeting.
> 9. Is there any movies you are looking forward to in the coming year? 
Not really. I get tired of all the comic rebooted reboots of
re-architected reboots of sequels.
> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
Nothing here.
> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
>
> Thanks, and looking forward to your feedback!
>
> kevin
>
>
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: url shorteners

2016-04-20 Thread David Shier

Links that are not a mile long are always cool in my book, so I guess I am all
for this. It would be nice to keep it open source if we can do maybe openshift
is a good way to go for it.

Odin

On Apr 20, 2016 19:43, Chaoyi Zha wrote:

Oops -- didn't see the "php (bah)" comment. We could host it on OpenShift the
same way we host Magazine, or we could try polr.me (which is also open source).

On Wed, 20 Apr 2016 at 18:30 Chaoyi Zha wrote:

You can take a look at http://github.com/cydrobolt/polr. It's been used by many
high volume sites for over the past couple of years.

(full disclosure: I wrote Polr)

On Wed, Apr 20, 2016, 5:58 PM Kevin Fenzi wrote:

Greetings.

I thought I would start a bit of discussion on url shorteners.

In the past we had paste.fedoraproject.org output a short url for every
paste using the 'ur1.ca' service. ur1.ca is nice because they are 100%
open source. However, at some point they became very slow, so the
command line 'fpaste' tool would take a long time and then eventually
timeout. So, we disabled that and haven't been doing any short urls for
pastes.

There are however some places where people have requested we use url
shorteners over the years:

* https://fedorahosted.org/fedora-infrastructure/ticket/5173

The mailman3 archived-at header link (which is a link to the
hyperkitty archive of a specific post). It's long and ugly like:
http://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/EOIQM6E32PSGAHVYBY5OSFXKDHE33ZCQ/

* https://fedorahosted.org/fedora-infrastructure/ticket/4450
Short redirects to LiveCD images (including spins)

This could apply to any of the common media we point people to.

* https://fedorahosted.org/fedora-infrastructure/ticket/4931
fpaste using ur1.ca.
(The use case here is if you have a machine barely on the net so you
can use the fpaste command to paste something, but need to retype that
url into another computer to get someone else to help you look at it,
the short url is much easier to type.

* Other service that uses urls that might be nice to shorten for some
reason. I'm sure we could think of more places they might be handy.

So, options:

1. Just punt and keep going the way we are. We have lived without them
this long.

2. See if we can help ur1.ca and/or if they are fast enough for us now
and just use them for everything. However, if we do, I would like to
talk with them and make sure it's all good, as we might generate a lot
of links if we do every email post.

3. Pick some other url shortener. Personally, I like using one thats
open source and shares our values, but we would just be using it as an
external service, so perhaps we don't care so much. If we pick some
other one we should make sure they can handle our volume, etc.

4. Run one ourself. Note: this is "run" NOT "write". I do not want us
spending developer time writing something like this. There's tons of
them out there. The popular ones are in php (bah), but I am sure we can
pick one that meets our needs if we look. There's even some flask based
ones out there. ( like https://github.com/ugcoder/Py-URL-Shortener )

Thoughts?

kevin
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Hello to the Fedora Infrastructure!

2016-04-20 Thread David Shier

Welcome to the group.

Sent using Boxer

On Apr 20, 2016 12:00, Kevin Fenzi  wrote:

On Tue, 19 Apr 2016 20:40:34 -0400
"Miguel M."  wrote:

> Sending this email as my Hello, world introduction post.
> 
> Name: Miguel Moll
> IRC and FAS handle: radioact1ve
> Skills: Software development with Go, Python, Ruby and C#. Also an
> intermediate level sysadmin.
> 
> I want to help give back to the community that has given me so much
> already. Think it's a good time to start contributing where ever I
> can be of most value. I'm here shadowing the mailing list and IRC.
> 
> As a side note, would anyone be able to add my FAS account to
> the 'fi-apprentice' group? That way I can keep looking around without
> breaking anything.
> 
> Thanks for your time and looking forward to contributing!

Welcome!

I can get you added to the apprentice group... 

Enjoy!

kevin

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: April status update for Fedora Infrastructure Apprentices

2016-04-02 Thread David Shier

Answers in line.

On Fri, Apr 1, 2016 at 10:49 AM, Kevin Fenzi  wrote:

> You are getting this email because you are in the 'fi-apprentice' group
> in the fedora account system (or are reading this on the
> infrastructure list).
>
> Feel free to reply just directly to me, or cc the infrastructure list
> for everyone to see and comment on.
>
> https://fedoraproject.org/wiki/Infrastructure_Apprentice
>
> At the first of every month(or so), I am going to be sending out an
> email like this one. I would like feedback on how things are going for
> you.
>
> I'd like to ask for everyone to send me a quick reply with the
> following data or anything related you can think of that might help us
> make the apprentice program more useful.
>
> 0. Whats your fedora account system login?
>

odin2016


> 1. Have you logged in and used your fi-apprentice membership to look at
> our machines/setup in the last month? Do you plan to?
>
> I've attempted to and found out the ones that I wanted to look around
where higher security that i have access to. Mostly around SOP work I doing
for others.


> 2. Has it helped you decide any area you wish to focus on or contribute
> to more?
>
>  Not really more than I already have.


> 3. Have you looked at or been able to work on any of the fi-apprentice
> 'easyfix' tickets?
> https://fedorahosted.org/fedora-infrastructure/report/14


I've looked about, and i've found some SOP creation tickets that I am going
to work on knocking out. I've a draft for the ipsilon SOP. I need to have
Patrick look over before I commit it.

>
>
> 4. Do you still wish to be a member of the group? If not (for whatever
> reason) could you provide any hints to help others down the road?
>
> Yes.


> 5. Is there any help or communication or ideas you have that would help
> you do any of the above?
>
>
Not at this time.


> 6. What do you find to be the hardest part of getting involved?
> Finding things to work on? Getting attention from others to help you?
>

Nothing that is on the Project. Almost done transitioning to a normal type
of job. Which will help.


> Finding tickets in your interest area?
>
> 7. Have you been able to make any weekly irc meetings? Do you find them
> helpful or interesting?
>
>
Not recently. Mostly due to seanding meetings at $day_job


> 8. Have you logged into our Gobby instance and read/seen/added to our
> meeting agenda? https://fedoraproject.org/wiki/Gobby
>
>
In the past, yet.


> 9. What was the last song you listened to? (Live or recorded)
>
>

Disturbed's cover of 'Song of Silence.'


> Any other general feedback is also quite welcome, including
> improvements to this email, the wiki page, etc.
>
>
None.


> Any folks I do not hear from in the next week will be removed from the
> group. (Note that it's easy to be readded when you have time or
> whatever and it's nothing at all personal, we just want to keep the
> group up to date with active folks).
>
> Thanks, and looking forward to your feedback!
>
> kevin
>



-- 
---
Dave Shier
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: zodbot documentation?

2016-03-14 Thread David Shier

I've done the following this evening.

Expanded the #startmeeting, #meetingname, #meetingtopic, and #endmeeting
calls description.

Dropped the #help reference (it would be seen with #commands now anyway).

Added notation that this, as we use it, is a fedpkg package and that you
would need fedpkg to work with the source that we have deployed. Maybe not
so required, but if someone that's not worked with our packages before
wants to try something it could be helpful.

Added notation that to install the plugin on your own system you would need
to run 'su -c dnf install supybot-meetbot' or similar, and that this will
also install the main supybot code as needed.


Please review when you have time and let me know if I missed something,
opened a new can of worms somewhere, or could still go deeper on something
still.

On Mon, Mar 14, 2016 at 3:08 PM, Kevin Fenzi  wrote:

> On Mon, 14 Mar 2016 11:52:01 -0400
> Matthew Miller  wrote:
>
> > On Mon, Mar 14, 2016 at 09:41:07AM -0600, Kevin Fenzi wrote:
> > > The reason for the #help vs #halp was that the upstream folks
> > > wanted a distinction between asking for help about the meeting
> > > commands and asking in a meeting for help on some task or thing.
> >
> > I'm not clear which is which. Maybe change the ask-for-help thing to
> > #helpwanted, and have #help tell you help? I dunno. I don't think
> > either are heavily used. Ralph implemented my idea of collecting #help
> > for feeding into some sort of global list, but I didn't follow through
> > on the "doing something with that" part, and there's a chicken-and-egg
> > problem with people using it.
>
> Yeah, #help was supposed to be the plugin help and #halp was supposed
> to be the "I want to ask for help in the logs" one. But I agree this is
> confusing and we should probibly just drop it. ;)
>
> > > We made meeting name required in startmeeting because some people
> > > were not setting it and we wanted to require it so meetings would be
> > > organized better.
> >
> > Yeah. I'm just not sure if #meetingname is still required or useful,
> > and what happens when for example one does
> >
> >   #startmeeting FESCO (2016-03-18)
> >   #meetingname fesco
>
> It overrides the meetingname passed on the startmeeting call. You can
> change the name anytime during the meeting with #meetingname.
>
> >
> > > #meetingtopic is a higher level topic. All #topics after that would
> > > fall under it. So, it's not really needed/user much. An example
> > > might be a special meeting on a specific topic might use it and
> > > have sub #topics for various parts of the discussion.
> >
> > Ah that makes sense. I'm gonna start using that for Council meetings,
> > where we rotate between
> >
> > #meetingtopic Open Floor
> > #meetingtopic Tickets & Ongoing
> > #meetingtopic Subproject Report ($nameofteam)
> >
> > and
> >
> > #meetingtopic $somespecialthing
> >
> > like
> >
> > #meetingtopic Objective Review
>
> Sure, that should be valid I think.
>
> kevin
>
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
>
> http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org
>
>


---
Dave Shier
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: zodbot documentation?

2016-03-12 Thread David Shier

I can work on updating this sometime this coming week. I am heading out of
town for the remainder of the weekend soon.

We did make  the meeting name with #startmeeting a requirement so that people
coiuld find their logs, and it is a parameter. I thought I had added that tot
he document when I did that, evidently not.  #meetingname is not required, but
if you want to change the name in the herald of the room you are in during a
meeting, #meetingname will do it, it just won't change the name of the logs,
which is set with the name you give with #startmeeting.

#meetingtopic will change the topic of the meeting as well, but I believe
there  are other ways to do that as well these days.

Like I said above, I will plug away at this during the week.

Thanks,

Dave Shier

(odin)

> On Mar 12 2016, at 9:48 am, Matthew Miller mat...@fedoraproject.org
wrote:  

>

> We have https://fedoraproject.org/wiki/Zodbot, but it doesn't seem very  
complete around the meetbot plugin., and I can't find the source we're  
using for that. The docs say "#help" instead of "#halp" (which the bot  
itself tells you to use), for example. And, I think we changed it to  
that you need to provide a meeting name -- except we seem to do it as a  
parameter to #startmeeting, although the FESCo meeting template calls  
for also setting #meetingname. This is confusing to me — what are  
people _supposed_ to do?

>

> Oh, and there's #meetingtopic, which seems to be in no one's meeting  
SOP. Should it be???

>

> \--  
Matthew Miller  
mat...@fedoraproject.org  
Fedora Project Leader  
___  
infrastructure mailing list  
infrastructure@lists.fedoraproject.org  

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Support levels and RFR adjustments

2016-03-08 Thread David Shier

I think this is a good idea, maybe add a sub header similar to 'technical
project sites in this region' to differentiate between something that is a
more or less general community forum and the ones where you've got
development types that likely want more focused conversation related to
their projects.
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: March status update for Fedora Infrastructure Apprentices

2016-03-08 Thread David Shier

Apologies on the late response, I've been pre-occupied this week with
convincing a director that he wants me on his team. It worked by the
way Answers in-line

You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.

0. Whats your fedora account system login?

odin2016

1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?

I've looked around a bit, but have been a bit more focused on getting
transferred to a new team at work. I was planning on working on the
technical debt/ documentation work this week, since i've also got a more
free weekend than usual.

2. Has it helped you decide any area you wish to focus on or contribute
to more?

Yes.

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14

I've looked, though not in the last week.

4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

I do, was just a little tardy on this email, as stated above.

5. Is there any help or communication or ideas you have that would help
you do any of the above?

Nope.

6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?

Usually it's things to work on that are not the same thing, like CSI vars,
but I hear there are some more things in the easy-fix boat, documentation
this week, etc.

7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

I was at the two weeks ago.

8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby

Not this month, but most months.

9. What was the very last package you installed on your
Fedora/RHEL/whatever machine? 'rpm -qa --last | head -1'

libXi-1.7.6-1.fc23.i686. (On my former chromebook that doesn't like 64
fedora these days...  22 ran fin on x64 for some reason though.)

Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.

Nope.

Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!
Thanks,


Dave Shier
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: February status update for Fedora Infrastructure Apprentices

2016-02-02 Thread David Shier

0. odin2016
1. Yes.
2. I think so.
3. Yes.
4. Yes.
5. No.
6. Finding tickets that are not already being worked.
7. Yes, yes.
8. Yes.
9. Sleeping, running, hopefully doing some things around here. if my young kids 
will allow it. :)
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: December status update for Fedora Infrastructure Apprentices

2015-12-03 Thread David Shier


Kevin,

Comments are in line.

On 12/03/2015 03:03 PM, Kevin Fenzi wrote:

Greetings.

You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).

Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.

https://fedoraproject.org/wiki/Infrastructure_Apprentice

At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you.

I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.

0. Whats your fedora account system login?

odin2016


1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?

Yes

2. Has it helped you decide any area you wish to focus on or contribute
to more?

I think so.

3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14
I've looked at the easyfix tickets, but it appears they are mostly 
waiting on internal tickets, or other decisions. Instead I added a 
requirement in the meetbot plug-in to require a meeting topic to 
#startmeeting per a ticket from Remy and have been working on csi 
group_vars.



4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?

Yes.


5. Is there any help or communication or ideas you have that would help
you do any of the above?
I do not believe so, but I am also able to make the weekly meetings 
regularly, so I may be better communicated to that some.



6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
Probably finding things that I can do as a lot of the tickets at this 
point require a little but more than I have as most are in the bigger 
queue and a lot of the things I have found in the larger queue are taken 
care of at this time. Out side of that the remaining is just a learning 
curve thing, which will sort itself out.




7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?

Yes, I have, and I find them helpful, insightful and interesting.



8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby


Yes.


9. Did you know that we are going to be doing a 'technical debt
cleanup' week on 2016-01-06 to 2016-01-09? See:
https://fedoraproject.org/wiki/Infrastructure/Debt
and come join us.
I do. I am looking forward to these starting as it will help me in the 
learning curve area and I should be able to be more useful as the people 
I need to do things will be right there at the time I need them and 
likely will not need to wait on them to check their email for something 
I've sent to the list as much. :)



Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.


No additional feedback at this time. If I come across something I will 
mention it on the list or in #fedora-admin.

Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).

Thanks, and looking forward to your feedback!

kevin


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org



Thanks,

Dave Shier / Odin

___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Group vars for tasktotron- prod stg and dev

2015-12-02 Thread David Shier


Tim-

Thanks for the detailed reply! I will review and make the adjustments.

In the list there are entries for the below that are flagged as needing 
group vars updates:


taskotron-dev
taskotron-dev-client-hosts
taskotron-dev-clients
taskotron-prod
taskotron-prod-clients
taskotron-stg
taskotron-stg-clients

I planned on updating all of those, but figured I would start with this 
piece. If there are other pieces that are not in the list let me know 
and I will add them to my list of vars to update.


Dave Shier / odin2016


On 12/02/2015 10:14 AM, Tim Flink wrote:

On Thu, 26 Nov 2015 17:17:46 -0500
David Shier <davidjsh...@gmail.com> wrote:

Comments inline for the dev patch, stg and prod have similar comments.

+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin infrastruct...@fedoraproject.org
+csi_purpose: Run automated tasks, such as builds on fedora components
and report results of those task runs.

Taskotron does not run builds. I suppose it could but that would likely
overlap with Koji and/or copr.

A better way to put it would be:
Runs automated tasks against Fedora components triggered by fedmsgs and
reports results of those tasks to resultsdb.

The difference between the three systems is:

  * dev is where we try out new features, often before they're ready for
general consumption

  * stg is very close to prod and is used to verify that changes work
before they're deployed to prod

  * prod is the production system which most folks interface with

+csi_relationship: |
+
+The system is made up of several components:
+
+- trigger
+
+- task execution system
+  this is a master/slave system, currently using buildbot
+
+- results storage (in resultsdb)
+
+- mirror task git repos

I'm a little fuzzy on what's supposed to be in this field. The
taskotron-{dev,stg,prod} playbooks are responsible for the following
parts of the Taskotron system:

  * run the trigger program which listens for fedmsgs which kick off
tasks

  * run the buildmaster

  * host the static landing page at taskotron.fp.o

+- requires access to the git mirror(s), builders (koji, copr) and
+resultsdb

This is not quite right. A more accurate description of the
dependencies would be:

requires access to kojihub, bodhi, fedmsg hub, dist-git and the
upstream task repositories.

Are we planning to fill in the CSI vars for the other Taskotron related
playbooks or is this meant to describe the system in its entirety?

Thanks for getting this started,

Tim


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org


___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Updated group_vars for value (prod)

2015-11-29 Thread David Shier

Attached are updated group for value in response to some malcontent 
expressed about them this past week. Please review and commit as deemed 
appropriate. The same can likely be sued to value-stg, but I've not 
reviewed those at all yet. If the general feeling is that they can be 
used in stg as well go ahead and push them there as well and let me know 
so I don't fiddle with those when I could move on to another set.



Thanks,

Dave Shier


--- value.orig	2015-11-18 16:43:26.777262118 -0500
+++ value	2015-11-29 20:33:42.634607682 -0500
@@ -45,10 +45,13 @@
 # For the MOTD
 csi_security_category: Moderate
 csi_primary_contact: mote admins - sysadmin-mote-memb...@fedoraproject.org
-csi_purpose:  IRC stuff -- "value added"
+csi_purpose: Hosts services which help facilitate communication over IRC and related mediums, such as Supybot and mote.
 csi_relationship: |
-There are a couple things running here.
 
-* zodbot, a supybot instance.  See the zodbot SOP for more info.
-* fedmsg-irc, our fedmsg to IRC relay.  'journalctl -u fedmsg-irc'
-* mote, a webapp running behind httpd that serves meetbot log files.
+If this server is down supybot, and thus all of the IRC bots, fail. Additionally, logs will not be available in mote, and mote itself will be unavailable.
+
+Applications that run here:
+
+- Supybot, which runs Zodbot and meetbot as plugins. See https://infrastructure.fedoraproject.org/infra/docs/zodbot.rst for detailed information and troubleshooting.
+- fedmsg-irc, our fedmsg to IRC relay.  'journalctl -u fedmsg-irc'.
+- mote, a webapp running behind httpd which serves meeting logs generated by the meetbot supybot plugin at https://meetbot.fedoraproject.org/
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Group vars for tasktotron- prod stg and dev

2015-11-26 Thread David Shier


 Patches attached.


Thanks,

Dave Shier
--- taskotron-dev.orig	2015-11-18 16:43:26.776262150 -0500
+++ taskotron-dev	2015-11-26 16:49:51.783309938 -0500
@@ -15,6 +15,29 @@
 # extra_enablerepos: 'infrastructure-testing'
 extra_enablerepos: ''
 
+# These variables are pushed into /etc/system_identification by the base role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin infrastruct...@fedoraproject.org
+csi_purpose: Run automated tasks, such as builds on fedora components and report results of those task runs. 
+csi_relationship: | 
+
+The system is made up of several components:
+ 
+- trigger
+
+- task execution system
+  this is a master/slave system, currently using buildbot
+
+- results storage (in resultsdb)
+
+- mirror task git repos
+
+- requires access to the git mirror(s), builders (koji, copr) and
+resultsdb
+
 
 
 # task repo details
--- taskotron-prod.orig	2015-11-18 16:43:26.777262118 -0500
+++ taskotron-prod	2015-11-26 16:44:31.199306734 -0500
@@ -30,3 +30,28 @@
 execdb_server: http://resultsdb01.qa.fedoraproject.org/execdb
 execdb_statuspush: http://resultsdb01.qa.fedoraproject.org/execdb/buildbottest
 robots_path: /var/www/html
+
+
+# These variables are pushed into /etc/system_identification by the base role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin infrastruct...@fedoraproject.org
+csi_purpose: Run automated tasks, such as builds on fedora components and report results of those task runs.
+csi_relationship: |
+
+The system is made up of several components:
+ 
+- trigger
+
+- task execution system
+  this is a master/slave system, currently using buildbot
+
+- results storage (in resultsdb)
+
+- mirror task git repos
+
+- requires access to the git mirror(s), builders (koji, copr) and resultsdb
+
+
--- taskotron-stg.orig	2015-11-18 16:43:26.777262118 -0500
+++ taskotron-stg	2015-11-26 16:49:14.907344817 -0500
@@ -15,6 +15,29 @@
 # extra_enablerepos: 'infrastructure-testing'
 extra_enablerepos: ''
 
+# These variables are pushed into /etc/system_identification by the base role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin infrastruct...@fedoraproject.org
+csi_purpose: Run automated tasks, such as builds on fedora components and report results of those task runs. 
+csi_relationship: | 
+
+The system is made up of several components:
+ 
+- trigger
+
+- task execution system
+  this is a master/slave system, currently using buildbot
+
+- results storage (in resultsdb)
+
+- mirror task git repos
+
+- requires access to the git mirror(s), builders (koji, copr) and
+resultsdb
+
 
 
 # task repo details
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Updated Group Vars for torrent

2015-11-23 Thread David Shier

Attached and below.

--- torrent.orig2015-11-21 08:06:28.981136020 -0500
+++ torrent 2015-11-23 21:33:43.759875093 -0500
@@ -14,3 +14,16 @@
csi_security_category: Low
csi_primary_contact: Fedora Admins - ad...@fedoraproject.org
csi_purpose: Torrent master server for Fedora distribution
+csi_relationship: |
+
+torrent01 is the master torrent server for Fedora releases
+
+This host relies on:
+- The virthost it's hosted on (ibiblio03.fedoraproject.org)
+- FAS to authenticate users
+- VPN connectivity
+
+Things that rely on this host:
+- If this host is down, Fedora will lose a release distribution channel
+- The Apache that displays the torrent website
+- This server also has opentracker+ running to gather statistics for our
torrent
s



---
Dave Shier

“Diplomacy is the art of telling people to go to hell in such a way that
they ask for directions.” -Winston Churchill
--- torrent.orig	2015-11-21 08:06:28.981136020 -0500
+++ torrent	2015-11-23 21:33:43.759875093 -0500
@@ -14,3 +14,16 @@
 csi_security_category: Low
 csi_primary_contact: Fedora Admins - ad...@fedoraproject.org
 csi_purpose: Torrent master server for Fedora distribution
+csi_relationship: |
+
+torrent01 is the master torrent server for Fedora releases
+
+This host relies on:
+- The virthost it's hosted on (ibiblio03.fedoraproject.org)
+- FAS to authenticate users
+- VPN connectivity
+
+Things that rely on this host:
+- If this host is down, Fedora will lose a release distribution channel
+- The Apache that displays the torrent website
+- This server also has opentracker+ running to gather statistics for our torrents
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Group vars update for wiki (production)

2015-11-23 Thread David Shier

Below and attached are the diff for updates to the group vars for wiki.

--- wiki.orig   2015-11-23 22:06:37.551441866 -0500
+++ wiki2015-11-23 22:57:52.441270349 -0500
@@ -30,3 +30,13 @@
nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,nfsvers=3"


+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin
+csi_purpose:  Provides our wiki
+csi_relationship: |
+
+There are multiple servers that this service requires. Proxy 1,2 and 3 and
Wiki
1 and 2.
+
+- Wiki requires the proxy servers in order for traffic to pass to them
+- If the Apache processes stop on wiki01 and wiki02 the wiki will not
display
+- The wiki also requires fas for log in purposes. If fas is down, the wiki
will
not become unavailable; however, no on will be able to authenticate



---
Dave Shier

“Diplomacy is the art of telling people to go to hell in such a way that
they ask for directions.” -Winston Churchill
--- wiki.orig	2015-11-23 22:06:37.551441866 -0500
+++ wiki	2015-11-23 22:57:52.441270349 -0500
@@ -30,3 +30,13 @@
 nfs_mount_opts: "rw,hard,bg,intr,noatime,nodev,nosuid,nfsvers=3"
 
 
+csi_security_category: Moderate
+csi_primary_contact: #fedora-admin 
+csi_purpose:  Provides our wiki
+csi_relationship: |
+
+There are multiple servers that this service requires. Proxy 1,2 and 3 and Wiki 1 and 2.
+
+- Wiki requires the proxy servers in order for traffic to pass to them
+- If the Apache processes stop on wiki01 and wiki02 the wiki will not display
+- The wiki also requires fas for log in purposes. If fas is down, the wiki will not become unavailable; however, no on will be able to authenticate
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Some notes on CSI variables

2015-11-20 Thread David Shier

Noted. In triplicate. :)

On Fri, 2015-11-20 at 13:42 -0700, Kevin Fenzi wrote:
> Just some quick notes on CSI variables as may people are submitting
> them. ;) 
> 
> They can't contain : in them as thats used as a variable seperator. 
> 
> If you want to do multiple lines, thats ok, but you have to do: 
> 
> variablename: |
> one
> two
> three
> 
> (the | is important there, it tells jinja that there's mutiple lines
> there). 
> 
> Also, you can't use * in the multiline ones, use - instead as a
> bullet). 
> 
> Thanks, 
> 
> kevin
> ___
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedor
> aproject.org
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: group_vars csi patch for virthost_ updated

2015-11-20 Thread David Shier

Updated in light of Kevin's oh so timely gentle nudge. ;) Preserved
copy attached. Nasty whitspace...


Odin, Destroyer of Ice Giants.

--- virthost.orig   2015-11-19 13:18:42.781783307 -0500
+++ virthost    2015-11-20 16:38:13.350610366 -0500

@@ -1,5 +1,5 @@

-

-scsi initiator for netapp iscsi volume

+---

+# iscsi initiator for netapp iscsi volume

 netapp_nfs01_iscsi_name: iqn.1992-
08.com.netapp:sn.1573980325:vf.f88732f4-106e-11e2-bc86-00a098162
a28

 # iscsi portal for netapp iscsi volume

 netapp_nfs01_iscsi_portal: 10.5.88.36

@@ -8,3 +8,15 @@

 nrpe_procs_warn: 900

 nrpe_procs_crit: 1000



+

+# These variables are pushed into /etc/system_identification by the
base role.

+# Groups and individual hosts should override them with specific info.


+# See http://infrastructure.fedoraproject.org/csi/security-policy/

+

+csi_security_category: High

+csi_primary_contact: Fedora Admins - ad...@fedoraproject.org

+csi_purpose: Host guest virtual machines.

+csi_relationship: |

+   - Guests on this host will be inaccessible if the host is down.

+   - This host will be required by any application with a virtual
machine running on it, therefore
, if this host is down those applications will be impacted.

"virthost.patch" [readonly] 26L, 1071C


On Thu, 2015-11-19 at 13:28 -0500, David Shier wrote:
> Below and attached is a patch to add group vars for csi compliance
> for virthost. As I did not find much in the way of documentation, and
> cannot currently log on to any of the virthost servers I have left
> them pretty general.
> 
> - virthost.orig   2015-11-19 13:18:42.781783307 -0500 
> +++ virthost    2015-11-19 13:18:18.305474418 -0500 
> @@ -1,5 +1,5 @@ 
> - 
> -scsi initiator for netapp iscsi volume 
> +--- 
> +# iscsi initiator for netapp iscsi volume 
> netapp_nfs01_iscsi_name: iqn.1992-
> 08.com.netapp:sn.1573980325:vf.f88732f4-106e-1
> 1e2-bc86-00a098162a28 
> # iscsi portal for netapp iscsi volume 
> netapp_nfs01_iscsi_portal: 10.5.88.36 
> @@ -8,3 +8,15 @@ 
> nrpe_procs_warn: 900 
> nrpe_procs_crit: 1000 
> 
> + 
> +# These variables are pushed into /etc/system_identification by the
> base role. 
> +# Groups and individual hosts should override them with specific
> info. 
> +# See http://infrastructure.fedoraproject.org/csi/security-policy/ 
> + 
> +csi_security_category: High 
> +csi_primary_contact: Fedora Admins - ad...@fedoraproject.org 
> +csi_purpose: Host guest virtual machines. 
> +csi_relationship: | 
> +    * Guests on this host will be inaccessible if the host is down. 
> +    * This host will be required by any application with a virtual
> machine running on it, therefore, if this host is down those
> applications will be impacted. 
> +
> 
> 
> ---
> Dave Shier
> --- virthost.orig	2015-11-19 13:18:42.781783307 -0500
+++ virthost	2015-11-20 16:38:13.350610366 -0500
@@ -1,5 +1,5 @@
-
-scsi initiator for netapp iscsi volume
+---
+# iscsi initiator for netapp iscsi volume
 netapp_nfs01_iscsi_name: iqn.1992-08.com.netapp:sn.1573980325:vf.f88732f4-106e-11e2-bc86-00a098162a28
 # iscsi portal for netapp iscsi volume
 netapp_nfs01_iscsi_portal: 10.5.88.36
@@ -8,3 +8,15 @@
 nrpe_procs_warn: 900
 nrpe_procs_crit: 1000
 
+
+# These variables are pushed into /etc/system_identification by the base role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: High
+csi_primary_contact: Fedora Admins - ad...@fedoraproject.org
+csi_purpose: Host guest virtual machines.
+csi_relationship: |
+   - Guests on this host will be inaccessible if the host is down.
+   - This host will be required by any application with a virtual machine running on it, therefore, if this host is down those applications will be impacted.
+
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

group_vars csi patch for virthost

2015-11-19 Thread David Shier

Below and attached is a patch to add group vars for csi compliance for
virthost. As I did not find much in the way of documentation, and cannot
currently log on to any of the virthost servers I have left them pretty
general.

- virthost.orig   2015-11-19 13:18:42.781783307 -0500
+++ virthost2015-11-19 13:18:18.305474418 -0500
@@ -1,5 +1,5 @@
-
-scsi initiator for netapp iscsi volume
+---
+# iscsi initiator for netapp iscsi volume
netapp_nfs01_iscsi_name:
iqn.1992-08.com.netapp:sn.1573980325:vf.f88732f4-106e-1
1e2-bc86-00a098162a28
# iscsi portal for netapp iscsi volume
netapp_nfs01_iscsi_portal: 10.5.88.36
@@ -8,3 +8,15 @@
nrpe_procs_warn: 900
nrpe_procs_crit: 1000

+
+# These variables are pushed into /etc/system_identification by the base
role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: High
+csi_primary_contact: Fedora Admins - ad...@fedoraproject.org
+csi_purpose: Host guest virtual machines.
+csi_relationship: |
+* Guests on this host will be inaccessible if the host is down.
+* This host will be required by any application with a virtual machine
running on it, therefore, if this host is down those applications will be
impacted.
+


---
Dave Shier
--- virthost.orig	2015-11-19 13:18:42.781783307 -0500
+++ virthost	2015-11-19 13:18:18.305474418 -0500
@@ -1,5 +1,5 @@
-
-scsi initiator for netapp iscsi volume
+---
+# iscsi initiator for netapp iscsi volume
 netapp_nfs01_iscsi_name: iqn.1992-08.com.netapp:sn.1573980325:vf.f88732f4-106e-11e2-bc86-00a098162a28
 # iscsi portal for netapp iscsi volume
 netapp_nfs01_iscsi_portal: 10.5.88.36
@@ -8,3 +8,15 @@
 nrpe_procs_warn: 900
 nrpe_procs_crit: 1000
 
+
+# These variables are pushed into /etc/system_identification by the base role.
+# Groups and individual hosts should override them with specific info.
+# See http://infrastructure.fedoraproject.org/csi/security-policy/
+
+csi_security_category: High
+csi_primary_contact: Fedora Admins - ad...@fedoraproject.org
+csi_purpose: Host guest virtual machines.
+csi_relationship: |
+* Guests on this host will be inaccessible if the host is down.
+* This host will be required by any application with a virtual machine running on it, therefore, if this host is down those applications will be impacted.
+
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Update to python path in zodbot.rst

2015-11-18 Thread David Shier

While updating Zodbot to require a meeting topic to start I noted that the
document references /usr/lib/python2.6, which no longer exists.. it's
python2.7 at this time. Below is the diff with my changes, and an updated
version of the rst is attached.


--- zodbot.rst.orig 2015-11-18 18:04:55.152124621 -0500
+++ zodbot.rst  2015-11-18 18:08:35.848942876 -0500
@@ -80,7 +80,7 @@
of the log uploaded to Trac (don't worry too much about formatting;
meeting.py works well with irssi- and XChat-like logs), then run::

-  sudo python
/usr/lib/python2.6/site-packages/supybot/plugins/MeetBot/meeting.p
y replay /path/to/fixed.log.txt
+  sudo python
/usr/lib/python2.7/site-packages/supybot/plugins/MeetBot/meeting.p
y replay /path/to/fixed.log.txt

Close the Trac ticket, letting the user know that the logs are processed
in the same directory as the URL they gave you.
~


Dave Shier


zodbot_updated.rst
Description: Binary data
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Meeting Agenda Item: Introduction David Shier

2015-11-01 Thread David Shier

IRC Handles: 

odin2016, odin2016_mobile

Skills and what I would like to learn:

I'd like to learn how to administer Linux systems as a whole from end to end; 
building machines to storage management and naturally the administration of the 
pieces that ride on the servers. I've moved from being primarily a windows 
admin at work to the primary unix admin on my team at work (i've been the 
primary contact for level 2 unix for about six months), and while i've learned 
a great deal in a short time the knowledge is split between Linux (specifically 
Red Hat) and AIX. Additionally I work three long days, so the extra exposure to 
the Linux environment and other administrators is appealing and beneficial. 
From reading the tickets it appears that docker is used, which is something 
that I also find interesting and would like to learn more about how it actually 
used, set up and administered as well. I understand shell scripting, 
specifically bash and loops, i'd like to get  better with those. I've also done 
some work with python scripts via code academy and would like to learn 
 more about how that applies to an administration. As far as skilled I am told 
by my co-workers that I am good and troubleshooting and tracking down what is 
causing an issue and when I ask questions they are usually the well thought out 
and relevant to solving the problem at hand. I am also told that I am a quick 
learner. 

What you would like to work on.: 

I've seen some scripting tickets in the queue that would be of interest to me, 
also a docker related ticket. Additionally I am interested in the  apprentice 
group and will likely also situate myself with the documentation group after a 
bit as it seems to me that a person working on a system and at some stage 
making changes, or close to those doing so,  would be a prime candidate to 
document it.



Dave Shier
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/infrastructure@lists.fedoraproject.org

Re: fedora-infrastructure#7267: "fedora-packager and statscache sunset" patch review.

fedora-infrastructure#7267: "fedora-packager and statscache sunset" patch review.

Re: The trouble with torrents

Re: Meeting Agenda Item: Introduction David Shier

Meeting Agenda Item: Introduction Your Name

Re: Moving meeting time?

Re: June status update for Fedora Infrastructure Apprentices

Re: February status update for Fedora Infrastructure Apprentices

Re: October status update for Fedora Infrastructure Apprentices

Re: September status update for Fedora Infrastructure Apprentices

Re: Aug status update for Fedora Infrastructure Apprentices

Re: June status update for Fedora Infrastructure Apprentices

Re: June status update for Fedora Infrastructure Apprentices

Re: url shorteners

Re: Hello to the Fedora Infrastructure!

Re: April status update for Fedora Infrastructure Apprentices

Re: zodbot documentation?

Re: zodbot documentation?

Re: Support levels and RFR adjustments

Re: March status update for Fedora Infrastructure Apprentices

Re: February status update for Fedora Infrastructure Apprentices

Re: December status update for Fedora Infrastructure Apprentices

Re: Group vars for tasktotron- prod stg and dev

Updated group_vars for value (prod)

Group vars for tasktotron- prod stg and dev

Updated Group Vars for torrent

Group vars update for wiki (production)

Re: Some notes on CSI variables

Re: group_vars csi patch for virthost_ updated

group_vars csi patch for virthost

Update to python path in zodbot.rst

Meeting Agenda Item: Introduction David Shier

32 matches

Site Navigation

Mail list logo

Footer information