So this morning openstack.org is down, returning 500 errors. This
remains one of the few pieces of openstack infrastructure that is not
hosted and run by the openstack-infra team. It means that fixing
openstack.org is not possible by the global development team on
openstack-infra.
I really think that needs to stop. We have a world class infrastructure
team in the community that hosts nearly everything else in
*.openstack.org. It does so across multiple openstack clouds. It does so
using the best practices of devops, with nearly everything under puppet
control. And it does so with a global team which means pretty extensive
TZ coverage (not perfect yet, but growing).
Can someone explain why openstack.org is run separately from the
openstack-infra effort, and what the plan is going forward?
-Sean
--
Sean Dague
http://dague.net
remains one of the few pieces of openstack infrastructure that is not
hosted and run by the openstack-infra team. It means that fixing
openstack.org is not possible by the global development team on
openstack-infra.
I really think that needs to stop. We have a world class infrastructure
team in the community that hosts nearly everything else in
*.openstack.org. It does so across multiple openstack clouds. It does so
using the best practices of devops, with nearly everything under puppet
control. And it does so with a global team which means pretty extensive
TZ coverage (not perfect yet, but growing).
Can someone explain why openstack.org is run separately from the
openstack-infra effort, and what the plan is going forward?
-Sean
--
Sean Dague
http://dague.net
Attached Files:
-
signature.asc (0.47 KB)