To Do List for New MOC Intern and Member¶
Things to do¶
For everyone¶
- Be able to run IRC and Slack
#moc,#openinfralabs,#openinfralabs-monitoringon freenode.
(usually folks use ZNC bouncer, some of us use irccloud which as a built in bouncer - #openinfralabs is archived so a bouncer may not be needed.)
- Checkout docs.massopen.cloud If you find things which may be improved you are encouraged to do a pull request and fix them. Understand how to use SSH and generate their public keys.
- Share contact info and subscribe to the team mailing list.
- Add your name and contact information at this URL
- Subscribe to the team mailing lists
- Trello: Send mail to msd@bu.edu with your Trello user name and you will be added to the appropriate organization.
For Support Types¶
Some of the items below require levels of access that must be earned over time, based on proving knowledge and judgement. Leveling Up is encouraged!
Please familiarize yourself with the following topics:
- OSTicket
- Look at the knowledgebase to know what’s already covered.
- Terminology
- Kaizen
- The MOC team tutorial on how to use our production system can be found at (here)[https://example.com]
- Openshift
- Kubernetes
- Engage1
- Openstack
- Getting started guide can be helpful.
- Version of SW
- How to tell which Openstack
- How to tell which Openshift
- Ceph
- Object Store
- [Block Storage](https://en.wikipedia.org/wiki/Block_(data_storage)
- Flavors
- RHEV
- MOC’s deployment of RHEV is also called oVirt.
- oVirt is the upstream project.
- PRB ovirt deployment
- Kaizen
- Openstack Tools
- Horizon
- Watch online tutorials, read up documentation. Would recommend creating instances, routers, security groups etc at least once.
- Command Line
- How to configure on your computer
- Horizon
- Monitoring System
- Zabbix Dashboard navigation
- Which zabbix URL for which information
- MAAS
- Our deployment is at https://maas.massopen.cloud
- HIL/BMI
- HIL: https://github.com/cci-moc/hil
- BMI/M2: https://github.com/cci-moc/m2
- How to: https://docs.massopen.cloud/en/latest/clusters/kaizen/Kaizen-Bare-Metal.html
- FreeIPA
- Our deployment is at https://freeipa.infra.massopen.cloud/ipa/ui/
- Access to RH MOC account
- How to research for existing bugs
- How to open a ticket
For Software Developers¶
- Python: You may want to consider using iPython or other interactive Python tool to learn to code in Python.
- Start by reviewing pull requests - if you click approve you are equally guilty as the person who wrote bad code that you approved
- Suggestion: if writing python code, use some static analysis tools (e.g. pylint, black). Helpful in highlighting unused imports, variables, functions, bad return types etc before you submit your code for review.
- Familiarize yourself with GitHub and git.
- Automated testing (unit/integration tests) to confirm that your project works:
- Python: pytest
- TravisCI, Jenkins, CircleCI
MOC Individual Contributor License Agreement (ICLA)¶
Contributors to the MOC are required to sign the Individual Contributor Agreement. Send Jennifer Stacy (jstacy@bu.edu) a quick note when you are done with this step. Note that you will not be allowed to contribute to any code base unless you sign the agreement.
Team Communication¶
- Standup - : the MOC team is an Agile team. Twice a week, Tues. and Thur., we have standup in the MOC team room. Face-to-face communication is best. However, if you cannot attend in person, you can dial in
- Team Slack room - : For private team conversation, a good alternative channel of communication is the massopencloud.slack.com. Please If you don’t have a slack account, go to slack.com and create one. If you do have a slack account already, you can access the massopencloud - room as you wish. Contact msd@bu.edu if you have any problem.
- MOC team email mailing list - : Go to the following the following URL to subscribe yourself to the MOC team mailing list
Contact msd@bu.edu if you have any question/problem.
MOC Community¶
We want everyone that has a strong engagement with the MOC to be visible to and engaged with our users. The goal is to keep the time commitment modest and spread across the entire team of developers, postdocs, visiting scientists, faculty and students, while maintaining a high level of service to Kaizen users.
What we are asking each MOCer is to take on one day of the help desk per month. That is, you will be responsible for answering questions that come to the ticketing system for one day (as well as any follow up).
The expectation isn’t that you a-priori know an answer, but that a smart person with insider access to the project team can quickly figure out an answer, put together a response and where it makes sense expand on our FAQ list.
To be part of the MOC community and participate in the help desk/ticketing system:
- send an email to admin@lists.massopen.cloud and ask to be added to both the signup sheet for the helpdesk and the MOC ticketing system.
- signup for your help desk coverage here
- subscribe to the kaizen mailing list
This mailing list is where you can ask the experts or share your knowledge in anything related to the MOC infrastructure including but not limited to OpenStack, Ceph and general networking topology in our production Kaizen.
For part-time interns, i.e., those that work 10-15 hours a week, this task is optional. You are encouraged to volunteer if this activity will not interfere with your class schedule.
You can expect at most a couple of questions in a day, and likely less. If you get more than that, then contact admin@lists.massopen.cloud and we will get you more help. We think this will be a great learning experience for everyone, and help increase the engagements across the team.
