Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux VM (ubuntu or similar)

      Description

      The Bloodhound (incubator) project wishes to have a VM upon which to put demo instances of Bloodhound.

      Any instances of demos run here would not be production in any sense and we are not expecting particularly expecting heavy use at this point so at the moment I would suggest the following resources:

      1CPU core
      512 MB RAM
      50GB Disk

      The users who would require access to this would be (at least initially) gjm and mpoole (both with sudo and shell)

      The bloodhound instances will be installed in a python-virtualenv to run as a non-privileged user through mod_wsgi with a PostgreSQL database backend. We expect to have up to three demo instances running depending to an extent on how much demand they see in use. Each demo instance is expected to be reverted to a known state once a day - these will be staggered in time in an attempt to ensure that the reset avoids taking up excessive resources.

        Activity

        Gary Martin created issue -
        Gary Martin made changes -
        Field Original Value New Value
        Description The Bloodhound (incubator) project wishes to have a VM upon which to put demo instances of Bloodhound.

        Any instances of demos run here would not be production in any sense and we are not expecting particularly expecting heavy use at this point so at the moment I would suggest the following resources:

        1CPU core
        512 MB RAM
        50GB Disk

        The users who would require access to this would be (at least initially) gjm and mpoole (both with sudo and shell)

        The bloodhound instances will be installed in a python-virtualenv to run as a non-privileged user through mod_wsgi with a PostgreSQL database backend. We expect to have up to three demo instances running depending to an extent on how much demand they see in use. Each demo instance is expected to be reverted to a known state once a day - these will be staggered in time in an attempt to ensure that the reset avoids taking up excessive resources.

        Given that one of the instances is expected to be a nightly-build type I was also wondering if it may be appropriate to be running a buildbot (possibly just buildslaves with the master running within an existing buildbot infrastructure?) in order to allow for a conditional svn up and look after reverting the databases to a known state.
        The Bloodhound (incubator) project wishes to have a VM upon which to put demo instances of Bloodhound.

        Any instances of demos run here would not be production in any sense and we are not expecting particularly expecting heavy use at this point so at the moment I would suggest the following resources:

        1CPU core
        512 MB RAM
        50GB Disk

        The users who would require access to this would be (at least initially) gjm and mpoole (both with sudo and shell)

        The bloodhound instances will be installed in a python-virtualenv to run as a non-privileged user through mod_wsgi with a PostgreSQL database backend. We expect to have up to three demo instances running depending to an extent on how much demand they see in use. Each demo instance is expected to be reverted to a known state once a day - these will be staggered in time in an attempt to ensure that the reset avoids taking up excessive resources.
        Hide
        Gary Martin added a comment -
        Would it be possible to get such a VM created for the Bloodhound project?

        I have just removed an additional side question from the description to focus the ticket a little, leaving only what we require and the last paragraph stating some of the details of what we will be expecting to set up for ourselves once a VM is available.
        Show
        Gary Martin added a comment - Would it be possible to get such a VM created for the Bloodhound project? I have just removed an additional side question from the description to focus the ticket a little, leaving only what we require and the last paragraph stating some of the details of what we will be expecting to set up for ourselves once a VM is available.
        Gavin made changes -
        Assignee Gavin [ ipv6guru ]
        Hide
        Gavin added a comment -
        just to inform, the VM is created, Im just setting up LDAP and a few other bits, you should get access shortly.
        Show
        Gavin added a comment - just to inform, the VM is created, Im just setting up LDAP and a few other bits, you should get access shortly.
        Hide
        Gavin added a comment -
        gjm and mpoole along with myself should have access, please test.
        As an aside, I'll help from within the project dev list to set up the demos.
        Show
        Gavin added a comment - gjm and mpoole along with myself should have access, please test. As an aside, I'll help from within the project dev list to set up the demos.
        Hide
        Gavin added a comment -
        Done.
        Show
        Gavin added a comment - Done.
        Gavin made changes -
        Status Waiting for Infra [ 10011 ] Closed [ 6 ]
        Assignee Gavin [ ipv6guru ]
        Resolution Fixed [ 1 ]
        Gavin made changes -
        Fix Version/s Initial Clearing [ 12325964 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Waiting for Infra Waiting for Infra Closed Closed
        47d 10h 38m 1 Gavin 20/Jan/13 04:51

          People

          • Assignee:
            Unassigned
            Reporter:
            Gary Martin
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development