Hi Greg/Dammina, I have been looking at how to get a working version of the Bloodhound instance locally from a backup file I made on August 1st 2017. I have asked Gary for some help with instructions on the correct way to do this. However if anyone else has the details then please let me know. I am unsure at the moment if the backup I have has everything in it needed to restore the issues and wiki to the state it was previously. Also I am not aware of any other backups of the system.
My plan is to create a working 0.4 version of Bloodhound from this backup and then upgrade it to 0.8. Then take another backup which can then be used to create our new instance of the official site on a new VM. Once I can get to this point I will publish the instructions here along with the backup file for others to try. Then once the process has been verified I will put my name forward as the second person to manage the new official VM and work with Dammina to get it operational and maintained going forward. I will try and report my progress here as often as I can. Cheers John. On 23 October 2017 at 10:55, Dammina Sahabandu <[email protected]> wrote: > Hi Greg, > > I’m very glad to here that we have an infra member among us. As I mentioned > earlier I will take the responsibility of taking care of VMS. However, at > start I might need some guidance from you. I would like to learn how this > works rather than just raising an ticket to infra. > > So if it is possible I would like to have a Skype call with you where other > interested contributors are also welcome to join and learn. > > Please let me know how to proceed. > > Thanks, > Dammina > > On Mon, Oct 23, 2017 at 1:28 PM Greg Stein <[email protected]> wrote: > > > Hey Dammina, > > > > Short answer: Infra turned off the service because it wasn't being > > maintained. More below: > > > > On Mon, Oct 23, 2017 at 1:59 AM, Dammina Sahabandu < > [email protected]> > > wrote: > > >... > > > > > Hi All, > > > > > > The public hosted instance of bloodhound is down again for some time > now. > > > We need to come up with a sustainable methodology to keep this up and > > > running. At least we should activate a different health check > monitoring > > > service. > > > > > > > Infra has ample monitoring. No worries there. But a couple things got > > broken on it, and never fixed. There were also a couple VMs running for > > Bloodhound demos, but those weren't worked on either. ... So Infra just > > shut it all down. > > > > > > > As I remember last time we have reported this to infra team and get > > > resolved. Is this the method that we have following all along? Or else > do > > > we have any control to the VM that this instance is running. > > > > > > I would like to take the responsibility of keeping the instance up and > > > running in the future, but first I need some guidance from our senior > > > members. > > > > > > > Speaking for Infra now: we would like an additional person to make a > > similar commitment, before we spin up a VM for Apache Bloodhound. We've > > been going back/forth on these VMs for a while now, and have yet to > > succeed. > > > > I'm reachable here (as a PMC Member) or on users@infra or via a Jira > > ticket. Happy to help, but Infra needs some assurances of assistance for > > your VM(s). > > > > Cheers, > > Greg Stein > > Infrastructure Administrator, ASF > > (and a Bloodhound PMC member) > > > -- > Dammina Sahabandu > Associate Tech Lead, AdroitLogic > Committer, Apache Software Foundation > AMIE (SL) > Bsc Eng Hons (Moratuwa) > +94716422775 >
