保持应用程序和基础设施连接
我在一个 IT 部门工作，该部门分为两个小组。 一组负责开发和管理应用程序，另一组负责管理公司的基础设施和服务器。 我们面临的问题之一是沟通中断。 我在应用程序组工作，我遇到的问题之一是当基础设施关闭服务器或刷新数据库时没有收到通知。
有没有人对如何改善两个组之间的沟通有建议，或者对如何跨多个系统（Linux 和 Windows）保留轻量级日志有任何想法？ 理想情况下，如果我们可以让我们的盒子只发布它们的状态或其他内容，那就太好了。
谢谢你的帮助，
本
I work in an IT department that is divided into two groups. One group develops and manages applications, the other manages the company's infrastructure and servers. One of the problems we face is a break down in communication. I work for the application group and one of the problems I have is not being notified when a server is taken down by infrastructure, or a database is being refreshed.
Does anyone have suggestions on how to improve communications between the two groups or any ideas on how to keep a light-weight log across multiple systems (both linux and windows)? Ideally it would be nice if we could have our boxes just tweet their statuses or something.
Thanks for the help,
Ben
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
要传达服务器状态，您可以做的一件事是让我们的基础设施小组设置一个网络监控系统，例如 Nagios。 这将使应用程序组中的每个人都能够获取系统中每个服务器状态的快照视图。 当你进行开发时，拥有这种状态是非常宝贵的。
Nagios 为您提供网络监控，还允许您显示系统中特定服务器的计划停机时间。
为了促进与基础设施的沟通，您的团队可以做的另一件事是让您的构建系统报告当前正在使用哪些服务器来构建和测试您的产品。
此外，在两个群体的利益相关者之间建立定期会议可能也是一个好主意。 如果你们都互相交谈，即使每周只有 15 分钟，您也可能会看到像您上面描述的那样的事件会减少很多。
One thing you could do to communicate server status is to have our Infrastructure group setup a network monitoring system like Nagios. This will give everyone in your application group the ability to get a snapshot view of the status of every server in the system. Having this kind of status is invaluable when you are doing development.
Nagios gives you network monitoring, but also allows you to show scheduled down time for a particular server in the system.
Another thing your group could do to foster communication with the Infrastructure is to have your build system report which servers it is currently using for building and testing your products.
Also, setting up regular meeting between stakeholders of both groups is probably a good idea too. If you all are talking to each other, even for 15 minute a week, you'll probably see incidents like the one you described above go down quite a bit.
我认为这是变更控制的一个更大的问题。
您应该拥有硬件和软件变更控制以及批准流程。
最终，基础设施为您服务 - IT 基础设施的目的是运行应用程序。
在我目前的大型金融数据公司中，未经客户端和应用程序组的适当授权，服务器不会被触及。 这似乎是一个巨大的痛苦，但每台服务器的存在都是有原因的 - 满足特定的业务目标并运行特定的应用程序。 基础设施团队没有理由自行改变事物或扰乱服务器。
对严重硬件故障的响应可能是一个例外。
所需的软件和操作系统更新通过计划的维护时段和批准的变更流程进行处理。
I think this is a bigger issue of change control.
You should have hardware and software change control and an approval process.
Ultimately, infrastructure serves you - the purpose for IT infrastructure is to run applications.
In my current large financial data company, servers are not TOUCHED without proper authorization through the client and application groups. It seems like a huge pain, but every single server is there for a reason - to meet a specific business goal and run a specific application. There is simply no excuse for the infrastructure group to be changing things or upsetting servers on their own volition.
Response to critical hardware failure might be an exception.
Needed software and OS updates are handled through scheduled maintenance windows and an approved change process.
我也喜欢 Nagios 的想法。 如果您想设置更多的通信工具，我会推荐像 Drupal 这样的内容管理系统。
我们在内部使用 Drupal 在团队之间进行沟通。 当一个团队关闭一台服务器时，他们会在 Drupal 中添加一个事件。 我们其他人要么以电子邮件、RSS 项目的形式获取它，要么只是通过刷新页面来获取它。
I like the Nagios idea as well. If you want to setup something that's more of a communication tool, I would recommend a content management system like Drupal.
We use Drupal internally to communicate between teams. When one team takes a server down, they would add an event into Drupal. The rest of us would either get it as an email, an RSS item or just by refreshing the page.
实施变更控制流程，为两个组提交、批准和安排变更。 这让每个人都知道发生了什么事。 这个过程可以是轻量级的，也可以是重量级的，取决于您的需要。
Implement a change control process where changes are submitted, approved and scheduled for BOTH groups. This lets everyone know what is going on. This process can be as light or heavy-weight as you want.