Mail to the mailing lists is expected to work through the holiday break. JIRA is back and seems to work. Confluence is not starting and we have not yet diagnosed why. While we are diagnosing Confluence (when we have time...) we will probably have to bounce JIRA since they live in the same tomcat server.
Developers should feel free to commit to foresight-commits as before the migration started. Users should expect their repository access to continue to function as it did before the process started. Everyone with build accounts should have gotten email from me separately about the upgrade in build services. If not, you can always email me and ask, or just show up on IRC. On Fri, Dec 21, 2012 at 12:49:28PM -0500, Michael K. Johnson wrote: > Sending mail to the new mailing lists may or may not work during the > holiday break. If you have questions, please feel free to show up on > IRC and ask. > > On Thu, Dec 20, 2012 at 09:55:46PM -0500, Michael K. Johnson wrote: > > Update: As you can tell from the subscription email you got and > > from this mail, foresight mailing lists have been moved to the > > new infrastructure. So far we have moved only foresight-devel, > > foresight-commits, and foresight-distro. If you have an interest in > > other foresight lists, please respond to this email and let us know. > > > > foresight-commits, lists, fdev, the build cluster, and DNS are all > > being served from the new infrastructure now. JIRA and Confluence > > are expected to move tomorrow, and to experience a brief downtime > > during the move. > > > > Production repositories are next after JIRA and Confluence. > > > > SSH host keys were not preserved in the move. This means that > > the new instance of fdev.foresightlinux.org has a different SSH > > host key. If you previously used SSH to connect to fdev, please > > expect the host key fingerprint: > > > > RSA key fingerprint is 4a:0f:58:ad:1f:23:93:ce:0c:79:82:99:e2:f6:52:a0. > > > > > > On Tue, Dec 18, 2012 at 05:29:56PM -0500, Michael K. Johnson wrote: > > > Update: the production repositories are back and expected to remain > > > up. JIRA, Confluence, and build services are currently expected to > > > be up by some time tomorrow. > > > > > > We'll continue to work on transitioning to the new infrastructure > > > quickly. > > > > > > On Tue, Dec 18, 2012 at 09:51:49AM -0500, Michael K. Johnson wrote: > > > > The infrastructure changes that have been posted in the news section > > > > of the web site, on the planet, on G+, and discussed on IRC somehow > > > > never made it to this list, for which I apologize. > > > > > > > > We are in the process of deploying a new cluster of systems for both > > > > developer services and public repositories for Foresight and other > > > > related Conary repositories. We're making good progress though more > > > > slowly than we had anticipated. > > > > > > > > Yesterday, a network outage removed access to the existing build > > > > cluster which includes the foresight-commits repository. Early > > > > this morning, that outage extended to the production repositories > > > > failing to respond to queries properly. Therefore, at this time, > > > > system updates are not possible. Admins are investigating both of > > > > these problems. > > > > > > > > At this point, we're intending to just bring up new developer services > > > > as we can on the new cluster, and to set up production repositories > > > > on the new cluster as soon as practicable. Other services will follow > > > > shortly. > > > > > > > > Thanks for your patience. _______________________________________________ Foresight-devel mailing list [email protected] http://lists.foresightlinux.org/mailman/listinfo/foresight-devel
